Group: Forum Members
Congrats! Although I know firsthand how frustrating it is to end up having had to chase down a problem cause that shouldn't have been causing a problem in the first place.
In terms of the clone setup, it just now occurred to me that I'm not entirely sure that USBDLM will work in this specific scenario. The reason is that I think -- but am not certain -- that USBDLM looks at drives when they are physically attached, e.g. plugged into a USB port (or whatever). In the Reflect clone scenario, the target volume is taken offline to other access so that Reflect can clone onto it and then brought back online -- but that of course isn't technically the same as a device becoming completely disconnected and reconnected. However, it's possible that USBDLM will look at the volume when Windows mounts it again, even if the underlying device remained connected the entire time, in which case this will work fine. Again, this will just be something you'll have to test.
On that note, the first order of business is in fact to make sure that USBDLM works as desired before modifying a Reflect clone script, because if USBDLM isn't reliably assigning the cloned partition a specific drive letter, then the script won't reliably be able to find it. So here's what I would suggest:
- Set up USBDLM to assign whatever drive letter you want based on whatever condition(s) you want, per our earlier discussion.
- Test that configuration by manually changing the cloned partition to some OTHER drive letter in Windows Disk Management, then running another clone to that disk. Does USBDLM switch the cloned partition back to the desired drive letter when the Reflect clone finishes and the volume reappears in Windows? You may also want to ensure that USBDLM does NOT alter the source partition's drive letter unexpectedly when the device hosting that partition is disconnected and reconnected.
If you've got USBDLM working as desired outside of Reflect, then here's what you'd do for the clone:
In Reflect, go to the Backup Definition Files tab, right-click the definition file for your clone job, and select "Generate PowerShell script".
- Click OK in the wizard that appears since you don't need to make any customizations there.
- You'll now have a script file under the PowerShell Files tab in Reflect. Right-click that and select Edit. That should open the script in PowerShell ISE.
- Search for a line that reads "# Handle backup success..."
- Directly below that line, add these two lines:
Start-Sleep -Seconds 5
Set-Volume -DriveLetter "X" -NewFileSystemLabel "MyClone"
- Change the "X" above to the drive letter you're using for your clone destination, and change "MyClone" to whatever volume label you want to use. The 5-second delay beforehand is intended to give Windows time to remount the volume and for USBDLM to look at it first. It may or may not be necessary, but it should be more than enough time.
- To test this all out, deliberately change your clone target's drive letter to something else AND change its volume label to something else. Then in Reflect, right-click the clone script -- under the PowerShell Files tab -- and select Run Now > Full (the backup type submenu is pointless for a clone job, but it works). See what happens within a few seconds after the clone job completes.
- If all goes well and you want to schedule this, then make sure you associate your schedules with the script, not the definition file -- although you will still need to keep that definition file under the Backup Definition Files tab because the script refers to it.