Environment
PlateSpin Forge 3.x
PlateSpin Protect 10.x
Situation
Target virtual machines created by Platespin forge/Protect when protecting Windows workloads.
Resolution
PlateSpin Forge 3.0.x/PlateSpin Protect 10.0.x
* When protecting a Windows Workload, PlateSpin Forge and PlateSpin Protect will create the target drives on separate virtual disks (VMDK/PKG) for each drive, except when the Workload is a Windows Cluster.
* When protecting a Windows Cluster workload with PlateSpin Forge or PlateSpin Protect, the target drives on the virtual disks (VMDK/PKG) will be created the same way as they are on the source.
* When protecting a Windows Cluster workload with PlateSpin Forge or PlateSpin Protect, the target drives on the virtual disks (VMDK/PKG) will be created the same way as they are on the source.
PlateSpin Forge 3.1/PlateSpin Protect 10.1 and later
*When protecting a Windows workload, PlateSpin Forge and PlateSpin Protect will create the target VM with a all drives on a single virtual disk.
*When creating target virtual disks on different datastores, one virtual disk is created for all partions being protected to each datastore.
*When protecting a Windows Cluster workload with PlateSpin Forge or PlateSpin Protect, the target drives on the virtual disks (VMDK/PKG) will be created the same way as they are on the source.
*When creating target virtual disks on different datastores, one virtual disk is created for all partions being protected to each datastore.
*When protecting a Windows Cluster workload with PlateSpin Forge or PlateSpin Protect, the target drives on the virtual disks (VMDK/PKG) will be created the same way as they are on the source.
Additional Information
When protecting a Windows Cluster Workload, changing drive assignments will potentially cause issues with the Windows Clustering service.