What are the Robocopy options to use for DX server to server migration?

The instructions I have gave me the server to server migration utility as the next step AFTER I have copied the files using Robocopy. I am migrating files to a VM machine from a physical box but not using the P2V utility from VMware.

here are the instructions (abbreviated) from EMC. What are the Robocopy options I should use for step 4?

****************
1) If license server will be moved, call licensing to get an updated license with the new machine ID (Vol ID for the C drive). The number is provided below. If a new license cannot be obtained at this time, just chose the 30 day evaluation period when installing DX.

2) Install DX and LS 6.2 SP1 on the target server.

3) Copy over your Centera PEA file from the source to the target server if applicable. Make sure the file path is the same on the target as it was on the source. If you were using an environment variable to point DX to the PEA file, you will need to create the variable on the target server. The variable would be: CENTERA_PEA_LOCATION , the value would be the file path of the PEA file.

4) Copy all file tags form the source to the target server using RoboCopy. We have agreed that RoboCopy is the best method to get just the DX file tags and unmanaged DX data over to the target server. Before copying over the data, please add the RoboCopy service executable and any others it may use to the DX Special Application Filtering List. This will avoid the files from being fetched back to the drive.

5) Stop the DX service on the Target server.

6) On the source server (preferred/active node), stop writes to the Extended Drive(s).

7) On the source server, disable all media activities (except for fetches), and disable drive/background scans.

8) Stop the DX service on the Source server.

9) If using Centera media, enable the dx_emcservice.log and SDK log (instructions below) on the target server. Incase something were to go wrong, this will log all the clips on the Centera getting updated.

10) Confirm you can see all drives on the new server.

11) On the source server (preferred/active node), run the Server to Server Migration utility (link to the utility provided below) using the Configuration option. If this is a cluster, you want to use the VS name as your target computer name. You will need to map all extended drives you¿re migrating, regardless if you¿re only using the configuration option.

12) Once the migration is complete, confirm the DX service on the Source server is stopped.

13) Start the DX service on the new server and set all the Media Services online.

14) Confirm all media is online (Centera Media can take quite a while to come online, depending on media count. This is due to the clips being updated).

15) On the Target server, disable the dx_emcservice.log and SDK log. (instructions provided below)

16) Reset all media activities and enable the background scan. Do not run more than one at a time. Please set the schedule for once a week after the initial scan.

17) Run a drive/background scan. Do not run more than one at a time. Please set the schedule for once a week after the initial scan.

18) Remap users from the Source Extended Drive(s) to the Target Extended Drive(s).

19) If you need to continue using the Source server, make sure the DX service is always disable.

20) After the service starts, the GUI connects to the extended drive, and files have been tested for fetching, replicated deletes can be re-enabled.

The server-to-server migration utility has the options to:
¿ To migrate the File System Manager configuration, select Transfer
Configuration Settings.
¿ To migrate the extended drive data, select Copy Extended Drive Data.
¿ To migrate both the File System Manager configuration and the extended
drive data, select both checkboxes.

Should you require the server-2-server migration utility, please log a support call and request for this utility.

You should not put robocopy in the Dx Special Application filtering list as this will cause data loss.

I've done 5 or so migrations this year for several different clients with varying media. The migration utility did everything including the copying of the file stubs. I used the latest guide that came with the server migration utility.

I guess, if Robocopy works, you could get a better feel for what was copied. The migration utility doesn't give you a status of which files were copied like robocopy can but the robocopy method you describe below isn't the supported migration method.