I don't have an answer, but more of an observation. I tend to try and keep one volume per project, assuming they're as big as you say they are. Since you can grow/shrink volumes, it's an easier way to keep things balanced.

It's not perfect of course... nothing is.

And as for moving CIFS shares, can you do symlinks in CIFS? Robocopy the data to a new volume, turn off CIFS share, finish the copy, then re-create the share pointing to the new location.

You will probably have to kill sessions though... CIFS sucks that way....

Peter> Background: we have 20 odd volumes for fileshares. We limit the Peter> size of the volumes to 10T. When a volume gets near full, we Peter> need to shuffle shares to new volumes or volumes with plenty of Peter> space.

Peter> Does anybody have a magical solution for moving fileshares Peter> between volumes? With minimal but not necessarily zero downtime?

Peter> Obvious solutions are:

Peter> 1) Down share, copy share to new volume, up share Peter> 2) Down share, clone volume, up share on new volume, split volume, cleanup mess.

Peter> I was wondering if anybody has seen a system to proxy the share and move Peter> it in the background. I have seen this work with NFS shares Peter> but not with CIFS.

Peter> Any magicians out there?

Peter> Regards, Peter> pdg

Peter> _______________________________________________ Peter> Toasters mailing list Peter> Toasters@teaparty.net Peter> http://www.teaparty.net/mailman/listinfo/toasters

No magic. I used robocopy (back in the day). I would robocopy to the destination (to seed the data), and when ready to cut over, stop the source share (to kick everyone off or make changes while cutting over. Run robocopy with /MIR (DANGEROUS) and /e/b/z/ (make sure you understand and use the correct switches)... whatever switches you want. Make sure you copy security/ownership. Offline original, bring new share online. There is also an AD component so be aware of that requirement as well (NETBIOS workstation reset, file server name redirection/DNS/WINS requirements if needed). When I would cut over, it was a whole file server (namespace). Impossible to do individual shares unless using a global name space. So, move all the shares at once for \server1\share1 \\server1\share2 etc.. all at the same time.

You can also snapmirror; that worked very well, especially for larger, or many file volumes. Its what I used for the larger datasets. Maybe you can ask your Netapp/VAR for a temp key if you don’t have it. Love snapmirror.

You can pay and use StorageX or some others solutions. Komprise is an up-and-come'er but does not support CIFS moves/migrations until end of this month.. I like Komrpise..

PM me if you want me to forward some instructions I used when I used to manage 7-mode. I would assume it's still relevant. Nothing I know about a proxy the share move. Robocopy can seed the data, and MIR option, which can be dangerous, mirrors source/destination.

Hope this was of some value.

-Steve

On 5/7/18, 6:23 PM, "toasters-bounces@teaparty.net on behalf of Peter D. Gray" <toasters-bounces@teaparty.net on behalf of pdg@uow.edu.au> wrote:

Hi people,

Background: we have 20 odd volumes for fileshares. We limit the size of the volumes to 10T. When a volume gets near full, we need to shuffle shares to new volumes or volumes with plenty of space.

Does anybody have a magical solution for moving fileshares between volumes? With minimal but not necessarily zero downtime?

Obvious solutions are:

1) Down share, copy share to new volume, up share 2) Down share, clone volume, up share on new volume, split volume, cleanup mess.

I was wondering if anybody has seen a system to proxy the share and move it in the background. I have seen this work with NFS shares but not with CIFS.

Any magicians out there?

Regards, pdg

_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters