Problem:

ShadowCrontrol ImageManager lists an Error or Warning that it cannot clean up the chain because of Migration files.

Cause:

Migration files are created when a chain has been virtually booted. The files created during the virtual boot are not always removed after deleting the virtual machine from the VirtualBox console.

Migration files consist of the following examples in the managed folder:

• C_VOL-B010_MachineName_VM_{7779c58d-48ba-4451-a336-a11e9e3bddbd}.spi
• MachineName_Disk_0_VM_{7779c58d-48ba-4451-a336-a11e9e3bddbd}_HD_{dc3e0487-0fbc-4211-b9fb-a9c30afe2cb6}.XSP

NOTE:

The file names are also quite a bit longer than normal for files in the managed folder directory.

Resolution:

To remove te migration files or files created for a Virtual Machine (VM) in VirtualBoot, use the main VirtualBox management GUI and perform these steps:

1. If the VM is running, stop it
2. In the VM's storage settings, detach any .XSP drives (these drives represent the images, and have very large filenames).
3. In the VirtualBox "Virtual Media Manager" GUI (from the File menu choose "Virtual Media Manager") on the Hard Disks tab locate any .XSP disks whose name includes the exact name of the VM that is being deleting, and then if any child items expand those child items in the tree and Remove each child (.vdi) item, selecting "Delete" rather than "Keep" when prompted.
4. In the VM's settings, under the Snapshots tab, right-click on the VirtualBoot snapshot and delete it.
5. Close the main VirtualBox management GUI and wait about ten seconds and then reopen it to let the above changes take. 
6. Back in the Virtual Media Manager, on the Hard Disks tab, remove all .XSP disks whose name includes the *exact* name of the VM being removed. When prompted, delete the backing files rather than keep them. If there were any .SPI incremental files created within the VM, then selecting the delete option will not break the chain because the plugin will only delete the .XSP files but will keep the migration incremental and any of the .SPIs that depend on it. If no .SPI incremental files were created within the VM, then selecting the delete option at this point will cause the .XSP, migration incremental (.spi) to be deleted.
7. Now delete the VM itself