Environment
PlateSpin Migrate 12.1
Situation
During the configuration of a migration job, "Argument Exception: targetVolumesToCreate" error is thrown. This error is usually caused by having multiple entries for the same mount point and same FSUUID. An example is shown below.
<q1:volume>
<q1:id>5a6eb1d0-481d-4e02-9a2f-54c6fc3ce8e6</q1:id>
<q1:fileSystem>EXT3</q1:fileSystem>
<q1:size>52840493056</q1:size>
<q1:freeSpace>49967661056</q1:freeSpace>
<q1:label />
<q1:fsuuid>5a6eb1d0-481d-4e02-9a2f-54c6fc3ce8e6</q1:fsuuid>
<q1:mountPoints>/app/domains/logs</q1:mountPoints>
<q1:partitions>/dev/cloudvg/app_domains_logs</q1:partitions>
<q1:isDynamic>false</q1:isDynamic>
<q1:isCompressed>false</q1:isCompressed>
<q1:NTFSBootSector xsi:nil="true" />
<q1:vssParticipant>false</q1:vssParticipant>
</q1:volume>
<q1:volume>
<q1:id>5a6eb1d0-481d-4e02-9a2f-54c6fc3ce8e6</q1:id>
<q1:fileSystem>EXT3</q1:fileSystem>
<q1:size>52840493056</q1:size>
<q1:freeSpace>49967661056</q1:freeSpace>
<q1:label />
<q1:fsuuid>5a6eb1d0-481d-4e02-9a2f-54c6fc3ce8e6</q1:fsuuid>
<q1:mountPoints>/app/domains/logs</q1:mountPoints>
<q1:partitions>/dev/cloudvg/app_domains_logs</q1:partitions>
<q1:isDynamic>false</q1:isDynamic>
<q1:isCompressed>false</q1:isCompressed>
<q1:NTFSBootSector xsi:nil="true" />
<q1:vssParticipant>false</q1:vssParticipant>
</q1:volume>
Resolution
To workaround this issue, kindly refer to the troubleshooting steps below.
- Locate this directory on your Migrate Server: C:\Program Files\PlateSpin Migrate Server\bin
- Inside this directory, search for PlateSpin.Browser.exe and run it as an administrator
- A new window will be opened then proceed on clicking the "Connect" button
- Once you are connected expand "https://localhost/PlateSpinMigrate" > "Networks" > "Default" > "Machines"
- Right click on the problematic server found under "Machines" then choose "View Source"
- Copy the contents of the XML file on a separate notepad
- Remove the duplicate entry from the volume section and keep only one entry for the mountpoint then save it as an XML file
- Open Migrate Client then delete the problematic source workload
- After the workload is deleted, click on "File" > "Import Machines" then import the modified XML file
- Once imported, please configure the job and see if the issue is resolved