Moving DiskXtender to new server...recommendations?

You can use the MetaData Export feature in DX to transfer the existing stub files to the new partition. Simply export the data from the existing box to a unc path. Once you've installed the base DiskXtender product on the new server you can use the Repair Log (Called Repair Disk in 5.x) to reset all the configuration settings (see help for more details). You can then import the metadata from the old box. Unfortunately you must use the the same servername on the new hardware for this to work. Hope this helps.

There's also a new DiskXtender utility called the Dx Server-to-Server Migration utility that will allow you to move all of your Dx configurations and the data on your Extended Drive to a new server.

You will need to contact Dx Support to get this utility, but it is much easier than the Repair Disk/Meta Data Export method of moving to a new server. The new server doesn't even need to have the same server name anymore.

mike,
thnx for your fast respons. we will contact dx support to get some documentation about this utilily.
regards,
andre

Yes it is. You will need to install Dx 6.1 on the new server, but do not configure anything. Then, use the 6.1 version of the server-to-server migration utility. Run that on your 5.6 server and point it to your new 6.1 server. It will handle upgrading everything from 5.6 to 6.1 for you.

Hope this helps.

-Mike

we want to move our w2k with dx5.60 to a new w2k3 with dx6.1 server. our dx data is on emc disk. and we want to detach the emc disk from the old server and attach them to the new server.

is dx server2server utility capable of doing this job ? or .......

thnx,
andre walvius

You're welcome.

You can download the utility and the documentation here:

ftp://OTGSOFT:OPTICAL@ftp2.documentum.com/incoming/DX_6.10.040_Server_Migration_Utility.zip

Hi Michael,

Can't access the link anymore. Any other option?

Regards,
kamal

Try the link again. Should be working now. You'll need to grab the utility within 24 hours of this message, or it will be removed.

Thanks!

-Mike

You cannot use the utility to upgrade from 5.2. You'll need to contact Support and obtain DiskXtender 5.5. You'll need to upgrade from 5.2 to 5.5, and then use the 6.1 Server Migration utility to migrate from your 5.5 server to a 6.1 server.

Thanks,

-Mike

Micheal,

I need to upgrade from 5.20 to 6.10 can you please put ftp://OTGSOFT:OPTICAL@ftp2.documentum.com/incoming/DX_6.10.040_Server_Migration_Utility.zip
online again ?

Tx,
Geert Vandenbussche

I have a query, moving data and DX related

I've a W2K file system which is 390GB in size. The data set has a reserved Celerra NAS file system of 350GB to which it is to be migrated to. There is approx 100GB which can be archived to Centera.

My understanding is that Stubs are not compatible between Windows and NAS DiskExtender. If they were then I'd be able to DX the file system while it was on W2K and then Robocopy the data from Windows to NAS.

One option I was thinking of trying while the Windows server remained the live file system was to Robocopy 350GB of data from Windows to NAS. DX the NAS file system which would hopefully replace a large percentage of data and free up space on NAS. Rerun Robocopy from Windows to NAS. Rerun the policy to ensure the additional 40GB of data added to NAS can also be stubbed.

My question is, will Robocopy see the stub as an amended file and replace it with the original file? I guess if Robocopy does see the file as amended, I 'll need to rethink my migration plan.

Thanks in advance

you need to exclude robocopy.exe from the "special application list" and configure it with "no recall". after this robocopy wil only copy the stubs.

good luck,
andre

We need a indication how long our migration will take. We are going to move the SAN disk with the extended drives to the new DX server and run only the DiskXtender Data Migration - Transfer Configuration Settings.

We got a total of 5 extended drives with 342 VM's and 31.12 M files on the Centera. We need to know how long it takes for the rename of the virtual media and/or c-clips as mentioned on page 22 of the DX2000 Server-to_server Migration Guide.

Does anybody done this before ? And could you give us a indication how long it takes to rename a virtual media ? Hours, days, weeks, months, years ??

Thnx,
Andre

Many thanks Andre. In the end I staged the migration of Windows data to Celerra. Set up seperate source paths and stubbed those folders and repeated unitl I had all the data on Celerra.

Hello,

we do the DX managed drive and also Server relocation for our customers as a professional service task. We can do this for you.
Are you interested?