How to restore stubs to alternate paths with DrTool

Restoring FileFly stubs to alternate paths is a three-step process:

  1. Create a DrTool file from source in the Admin Portal.

  2. Run the file in DrTool.

  3. Clean up stubs in the old location.

To create the DrTool file

Choose source and not destination because the source takes in to account the current location of the stub files for restoring stubs.

  1. Navigate to the Policies tab and create a new policy unless a DrTool job already exists.

    1. Provide the DrTool job a helpful name.

    2. Select "Create DrTool from Source".

    3. Choose the sources and rules the new policy covers and select Save.

  2. Assign the DrTool policy to a Task. Schedule it or leave it unscheduled for manual runs.

  3. Run the task.

  4. Select Go to task when the task run completes.

  5. Select Download DrTool Files from the Task Details

  6. Locate the latest generated file on Download DrTool Files, which appears first:

  7. Right-click and download this text file using browser commands. 

Using the DrTools file

The next part is to use the generated DrTools file.

Note

Launch drtools.exe in UI mode and then open the drtools.txt file downloaded if restoring to the original location is desired.

  1. Open the DrTool using an administrative command prompt to change the location a stub is to be restored.
    By default the location for the drtools.exe is C:\Program Files\Caringo FileFly\AdminTools\DrTool\

  2. Opening the drtool.bat with the -help flag displays all options:

  3. Specify the -csu flag to change the source location. Use this format: win:\\FQDN\path in FileFly syntax

    • Same Server — Moving a stub from a dead disk or to a new, preferred partition on the same server:

      drtool.bat -csu win://fileflyagent.testdomain.com/E/share1/example%20directory%20with%20spaces/ win://fileflyagent.testdomain.com/E/restoredhere/ "C:\drtools\drtool.txt"
    • New Server — Change the FQDN to change the server the stubs are restored to.

      drtool.bat -csu win://fileflyagent.testdomain.com/E/share1/example%20directory%20with%20spaces/ win://fileshare.testdomain.com/E/restoredhere/ "C:\drtools\drtool.txt"

  4. Press return if the path substitutions are correct and the DrTool UI opens.

  5. The URI substitutions appear highlighted in blue. Hover over an entry to check the details, and check Show Full URIs to view the paths where the stubs restore to:

  6. Right-click and select Create Stub... to restore the links to the files in the new location if the path looks correct.

  7. Choose the Create Stub Option:

    • Update source URLs in secondary storage files — This default option updates the object in Swarm so the new path is reflected.

    • Force destination to use Write Once Read Many — This excludes the recreated file from scrub policies.

  8. Select OK. The stub files are created in the new location and linked to the storage files.

  9. Shift-click individual files in the DrTool if a small subset of stubs needs to be re-created; otherwise, run the DrTool.bat command with the -recreateStubs option before the DrTool file.
    Create the stubs automatically without performing steps 6-8:

    drtool.bat -csu win://fileflyagent.testdomain.com/E/share1/example%20directory%20with%20spaces/ win://fileshare.testdomain.com/E/restoredhere/ -recreateStubs "C:\drtools\drtool.txt"

    Best practice

    1. Verify the process/path with steps 6-8 for a single file.

    2. Run the DrTool.bat command again with the flag to re-create all stubs once verified.

  10. IMPORTANT: Update the Sources tab to reflect this new location if the source location (where your content lives on the migration agent server) changes. The Source is broken (assuming the root folder is deleted when performing step 11) if this is not performed.
    Change the Source from "win://fileflyagent.testdomain.com/E/share1/example%20directory%20with%20spaces/" to "win://fileflyagent.testdomain.com/E/restoredhere/" In the example above.

  11. Delete stubs from the original source location if present.

Important

If stub files have not been deleted, they remain active in the original location also, which can be problematic, as a deletion of one stub may mean that the other becomes inactive unexpectedly due to a scrub policy being run.

 

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.