Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a new Policy, and select for the Operation to Create DrTool File From Source.

    Image RemovedImage Added
  2. Select which Rules and Sources the DrTool covers.

    Image RemovedImage Added
  3. Run the DrTool job, so there is a recent copy of the data.

    Image RemovedImage Added
  4. Open the job to get a recent DrTool file after the job completes: Open the task and select Download DrTool Files.

    Image RemovedImage Added
  5. Download the generated text file.

    Image RemovedImage Added
  6. Open the DrTool on the server where the stubs are migrated.

  7. Use the -csu option to redirect stub restores. This example takes a DrTool file for the fileflyagent.testdomain.com machine and changes the folder (E:\restored here\) where the stubs are restored.

    Image RemovedImage Added
  8. The files with the URL substituted are highlighted if the DrTool file has multiple URLs in it.

    Image RemovedImage Added
  9. Right-click and select Create Stub for the files which you want to recover. These will then be are restored to a different directory.

    Image RemovedImage Added
  10. When prompted, select whether to update the path information on Swarm also.

    Image RemovedImage Added

    If there is a large amount of files being recovered, the DrTool file will show displays a progress indicator. There will also be a A log file generated generates for each restoration job.

  11. Update the DrTool file to point to the new destination and agent to restore stubs to a server they did not originate from.
    In this example, the migration agent win://fileshare.testdomain.com/C/share1/ is the new path:

    Image RemovedImage Added
Info

Important

To restore a stub to a different agent, that migration agent must have connection to the source Swarm cluster, because it needs to read the files from Swarm and then update the information.