Move CIFS shares to another cabinet

virtual provisioning is merely auto-extension plus telling the client the max size instead of the actual size

you need to look at the current actually size

since nas_copy or Replicator works block-based the destination has to be at least the same current actual size

I havent tried it - but it should be possible to change the dst fs to virtual provisioning or creating it manually before the nas_copy

worst case you would have to temp. change the max size for the src to the current size

(I'm not sure if nas_copy looks at the current size - I believe it should but dont have time to test right now)

Rainer

Just tried it...destination has to be the same size  :-(

On to robocopy it looks like

you could use ndmpcopy if you dare :-)

GlennMonogram schrieb: Just tried it...destination has to be the same size  :-(

since you are saying you use virtual provisioning the question is which size - actual or max size ?

I have looked at this and come to the same conclusion. We will be attempting to move data to a smaller fs this weekend using emcopy, and I will let you know how we got on.

OK I did a test this morning after the new DAE got installed and the main problem I see is that if the source file system is marked with virtual provisioning, the new file system that is created durign the one time copy is not set to virtual provision.

Is this a bug or by design?

A few of my file systems are bigger than they need to be and I was hoping to not use more than necessary when I moved the file system to the new DAE.  It seems I will need to manually create the file system and use xcopy or robocopy to move the files to'shrink' the file systems.

Any input?

Thanks

GlennMonogram schrieb: Is the 'actual' size the dedup'd size or the full data size?

since nas_copy works block based dedupe doesnt matter there - the destination will have the exact same dedupe as the src

actual size is usual the smallest number - the one thats listed in the GUI fs properties as "Storage Capacity (MB)"

GlennMonogram schrieb: actual was 150mb (deduped)

that would be used capacity and not the size of the file system :-)

I tried with actual size. max was 300gb, actual was 150mb (deduped)

Rainer,

what is the path to ndmpcopy ?

Thanks

unfortunately there is no Celerra ndmpcopy command - you would have to use 3rd party or open source like ndmp.org

note that in 5.6 it isn't explicitly supported but it should work

Rainer,

what use cases would benefit from ndmpcopy versus server_archive ? If i read ndmpcopy description correctly it can use NDMP stream to copy data from one filer/datamover to another without invloving a "proxy" server.  Could one use ndmpcopy utility to migrate data between two different Celerras (if one does not have replicator license).

Thanks

yes - between Celerra's which server_archive can't do

unlike Replicator or nas_copy the dst fs can be smaller than the src fs

unlike client copy it preserves the multi-protocol attributes and there is no access problems

Rainer

thanks, i assume it can be used to go from one vendor NAS to another as long as they support NDMP protocol ?