How to move FileFly stubs to a new Migration Agent

When there is more than one migration agent, changing or consolidating migration agents requires migrating the file stubs to the target agent.

This is a 3-step process done from the FileFly Admin Tools server:

In this example, there are two existing migration agents. Although this shows a cloudscaler target, the method is the same for swarm targets. The goal is to move all stubs from filefly.ecorp.com to filefly2.ecorp.com and have one source, which is win://filefly.ecorp.com

Open

Creating the DrTool file

When a task is run to create a DrTool file from source, a text file is generated containing all mappings between the file URIs and the Swarm objects.

1. Under Sources, note the one source, which is win://filefly.ecorp.com:
   
   

   Open

   

2. Under Tasks, run a DrTool from source task to generate a text file that contains all mappings between file URIs and Swarm objects. The sources for the DrTool job are below. 
   
   

   
   If there are more sources to be retargeted, those can be added to the same DrTool job.

3. Run the task, allowing time for the job to run.
   The DrTool operation does a file walk for every source, checking the stub file and its destination URI. The more files and folder levels, the longer this takes.

4. Once the task is completed, download the DrTool text file directly from the Task tab. From the Recent Task History list, select Go to task for the run:
   
   

5. From the Task Details, select Download DrTool Files. This shows the last 5 DrTool file runs (or more, if the value in the settings is changed ).
   

6. The task's downloads page displays the last 5 DrTool file runs by default:
   
   

   
   Tip: Navigate to the Settings panel to change how many DrTool files to keep and for how long:
   
   

7. Select the latest file, which is listed first:
   
   

8. Download the DrTool file by clicking on the bold timestamp link. Use the browser's Save File option to download the file.
   
   

Running the DrTool file

To apply the DrTool file, open the DrTool via command line to change both the destination server that the stubfiles are restored to and also the migration agent that controls the stubs.

1. On the Admin tools server, open up an elevated PowerShell or command prompt, running as an Administrator.
   
   

2. Note the switches needed to migrate the files:

   • -csu — changes the source, which is used to change the server from filefly.ecorp.com to filefly2.ecorp.com

   • -cmu — changes the migrated URL; use this if the destination has changed.

   • -recreateStubs — recreates the pointer files in bulk.
     

   • Move the DrTool file directly to the DrTool folder. First, set the -csu switch:
     
     This opens the DrTool file with substitutions for the hostnames.

   • Add the switch -recreateStubs to create the stubfiles on the alternate filename.
     

   • Change the migrated agent FQDN on the destination when decommissioning a migration agent:
     

3. Run the command with line breaks for easy reading:
   
   

Changing the Destination

Change the destination once the stubs are migrated.

1. Open the Admin Portal.

2. Select the Destinations tab and edit the destination that moved.

3. Update the URI for the new location, then Save.