9 Legend

 • 

20.4K Posts

August 18th, 2008 12:00

you have two options ..fs_copy or server_archive. Search this forum and you will find some interesting discussions :)

August 18th, 2008 12:00

you have two options ..fs_copy or server_archive.
Search this forum and you will find some interesting
discussions :)


Thanks, Having some keywords will help with the search.

Christian

674 Posts

August 18th, 2008 22:00

Depending on your configuration you do not need to migrate data.
F.e. you could move a whole VDM to another datamover.

If the data is not in a VDM, then you could mount a whole FS to another datamover, create a compname and migrate the shares (sharedup) and localgroups (lgdup).

But if it is realy only a part of a FS, then you have to copy the data from a client or use server_archieve

4 Operator

 • 

8.6K Posts

August 18th, 2008 23:00

actually if you want to move a complete file system, all you have to do is unmount it on the old data mover and mount it on the new data mover.

of course it wouldnt be available through the CIFS server on the old data mover then and you would need to create new share(s) on the new DM

no need to use fs_copy there, which also only works on complete file systems

For moving just portions of a file system you would have to copy it.
Either through server_archive or external tools like emcopy or robocopy

If you need to this more often look into Rainfinity - it can do this transparently while users are accessing the data

9 Legend

 • 

20.4K Posts

August 19th, 2008 03:00

if you are trying to move the whole VDM ..can you unload VDM on one DM and load it on another ?

674 Posts

August 19th, 2008 05:00

You can do it manualy, but you can also use the -move option:

Moving VDMs (nas_server -vdm vdm_name -move server_X)
When you move a VDM from one physical Data Mover to another using the -move command, the Control Station performs the following internal operations transparent to users:

Unloads the VDM from the source Data Mover.
Unmounts all file systems mounted on that VDM.
Loads that VDM and mounts all file systems on the target Data Mover.
Moving a VDM from one physical Data Mover to another requires:

Interfaces with the same name on both physical Data Movers.
IP addresses for both interfaces.
Name resolution configurations on both Data Movers.

9 Legend

 • 

20.4K Posts

August 19th, 2008 06:00

haha ..automagically ?

674 Posts

August 19th, 2008 06:00

Not magically, but as designed :-)

9 Legend

 • 

20.4K Posts

August 19th, 2008 06:00

Thanks Peter ..so things like tree quotas, ABE ..will be magically migrated as well ?

4 Operator

 • 

8.6K Posts

August 19th, 2008 08:00

well, everthing that kept either on the data file system (like quotas) or the CIFS server or VDM level (like share, localgroups, ...) will move with it

There are some things that are set at the level of a physical data mover, like options, DNS settings, NTP and AV settings ... that will not move.

Take a look at the VDM manual - it has some explanations what config info is kept at what level.

4 Operator

 • 

8.6K Posts

August 19th, 2008 08:00

that actually what Celerra Replicator will do when you fail over a VDM

August 19th, 2008 12:00

If the data is not in a VDM, then you could mount a
whole FS to another datamover, create a compname and
migrate the shares (sharedup) and localgroups
(lgdup).


Since I'm not familiar with VDMs I'm going to guess it isn't in one. It is it's own FS. Do you just use mount, or is there a seperate command for mounting FSs to a DM?

9 Legend

 • 

20.4K Posts

August 19th, 2008 14:00

you would use server_umount / server_mount commands.

4 Operator

 • 

8.6K Posts

August 20th, 2008 00:00

to see if you are using a VDM just do a

nas_server -list -all
or
server_mount server_2 | grep root_vdm_

take a look at the attached for VDM concepts

1 Attachment

No Events found!

Top