to copy a whole file system the best way would be fs_copy or Replicator

However I understand you want to copy on a per-file level (i.e. into a file system that already contains data)

You can use server_archive for that (the syntax is a bit awkward so make sure to read the man page twice )

be aware that server_archive will not copy NTFS acl's ... You can search for some tools that can backup ACLs or copy with host based utilities like robocopy, secure copy ..emcopy. On my CFS14 server_archive was copying at 30MB/s (DMX3 backend).

Are you sure about that ?

I thought thats what the -J option is for ?

P.S.: I woulndt be a bad idea to file a Product Enhancement Request and ask for ndmpcopy to be supported ...

Message was edited by:
Rainer

Thanks for the advice guys. I'm looking at server_archive and it seems ideal for my purpose.

Excuse my ignorance (I've just returned from the NAS Admin course last week) but wouldn't I need to mount the two file systems via the Control Station in order to use them as paths in the server_archive command?

As we have no need for NFS in our environment, this is currently disabled but I could enable this temporarily to export the two file systems for server_archive - or am I over-elaborating the solution?

it's much easier than you think

server_archive works at the datamover level, so when you run server_df server_2 ...or whatever, those are the mount points you will use for your commands. I have never tried but i assume you can specify sub directories under your root mount point, something like:

server_archive server_2 /HR/internal_audit /NewHR/Internal_audit

i did not see -J as an option when doing fs to fs copy ..only when doing fs to tape copy, bummer ..i should have tried this. Do you have a lab to test this ?

yes, just use the full path that server_df or server_mount tells you.

To copy data do something like

server_archive server_2 -r -w -J /fs1/old /new_fs/new

no, server_archive is running on the data mover and doesnt involve the Control Station or NFS

Dont use the Control Station for data copying/migration - it has other important tasks to do and most external systems are better suited for NFS copy.

actually we are talking fs_archive here.



dont have to test - I have it on very good authority that it does work

what's fs_archive ? undocumented utility ?

sorry I meant server_archive of course

you got me confused saying fs to fs copy and I was reading it quickly as "fs_copy"

hahah ..ok ..i wanted to know what that wonderful utility was ?

[Q1] How do you prepare the local dstfs prior to fs_copy - just manually create it just like the source only same size or larger ?

[Q2] Does anyone have a sterling example of a local fs_copy command ? i.e. do you reference say, server_2 ?

pmail also if you can please ...

1) create file system to be exactly the same as the source, it this example i am creating file system fs_target to be exact same size as fs_source (my source)

nas_fs -name fs_target -type rawfs -create samesize=fs_source pool=symm_std storage=000290100123

2) create mountpoint and mount target file system as read-only

server_mountpoint server_3 -create /target_filesystem

server_mount server_3 -option ro fs_target /target_filesystem

3) Create checkpiont of source file system

fs_ckpt fs_source -name fs_source_ckpt1 -Create

4) Copy checkpoint to target file system

fs_copy -start fs_source_ckpt1 fs_target

5) When fs_copy is finished you can delete checkpoint created in step 4

nas_fs -delete fs_source_ckpt1 -o umount=yes

6) Mount target file system read/write

server_mount server_3 -option rw fs_target /target_filesystem

attached is the syntax for fs_copy

Of course if your source file system has changed while you were doing the copy you could
create another checkpoint and then do an incremental fs_copy update

like this:

fs_ckpt fs_source -name fs_source_ckpt2 -Create

fs_copy -start fs_source_ckpt2 fs_target -fromfs fs_source_ckpt1


If you are using NFS exports for that file system you want to re-export them after you switched file systems