Hyper-V – Incorrect function when trying to move files

Since we couldn't move, convert machine, creating new machine just by attaching old files didn't solve anything and there was no backup made there must be some corruption in the file itself causing the problem. We've decided to simply replace VHD drive with another drive by copying data. Since the drive had several folders, files with different folders and had some shared directories we had to do couple of steps:

Stop Server (LanmanServer) service (disable for peace of mind so that this setting survives reboots) to block access of file shares by users.

Run robocopy to copy all files and folders with permissions properly.

Our command of choice:

robocopy E: F: /E /ZB /DCOPY:T /COPYALL /R:1 /W:1 /V /TEE /LOG:Robocopy.log

Where:
E: is source drive (can be drive:\path or \\server\share\path).
F: is destination drive (can be drive:\path or \\server\share\path).
switch /E         copy subdirectories, including Empty ones.
switch /ZB        use restartable mode; if access denied use Backup mode.
switch /DCOPY:T   copies directory timestamps.
switch /COPYALL   copies all file information (equivalent to /COPY:DATSOU). 
                  Copies the Data, Attributes, Timestamps, Owner, Permissions and Auditing info.
switch /R:n       number of retries on failed copies. Default is 1 million.We recommend only 1. 
switch /W:n       wait time between retries. Default is 30 seconds, we set it to only 1 second.
switch /V         produce verbose output, showing skipped files.
switch /TEE       output to console window, as well as the log file.
switch /LOG:file  output status to LOG file (overwrite existing log).

It seems one of the fails has failed to copy. But that was expected.

Next step was to remove drive letter from the old drive, and assign that drive letter to new drive we just copied files to

Shutdown server and remove old drive

Start SERVER back up

When it's back up and running, Start Server (LanmanServer) service and verify shares functionality. 

And that's it. After that action we were able to make proper backups.

For the sake of additional verification we tried to use Test-VHD PowerShell command.

The command should return “True” if Test-VHD PowerShell cmdlets does not find any issues with the virtual hard disk file. In our case it shows everything is fine, so it must be something different. But since backup works, move works our job is done and we can go back to other tasks.