Unsolved
This post is more than 5 years old
4 Posts
0
854
May 20th, 2015 07:00
Error restoring VM from XtremIO snapshot
Environment is AppSync 2.1, ESX 5.5, vcenter 6.0, XtremIO 3.0.2. I've configured AppSync to take daily snapshots of the datastores which is working. However, I can't restore a VM. The error messages don't give enough information to be useful. This is what I get:
Any suggestions?
No Events found!
bheeth
4 Posts
0
May 20th, 2015 12:00
I figured it out after finding this error in the executive.log:
05-20-2015 13:30:03.115 WARN [XIOServiceBean] Source snapshot 20150519_124910.snap.Xtremio-ds1_2015-05-18_22-22-48-062 would exceed snapshot name length of 64 using derived snap name 20150519_124910.snap.Xtremio-ds1_2015-05-18_22-22-48-062.CopySnap. Using: .snap.î¿å–¹å¢¶îƒŸî•Žê›§
My original mistake was creating the Xtremio-ds1 datastore using VSI vSphere plugin. This tacks on date and time to the volume name in XtremIO so the name becomes Xtremio-ds1_2015-05-18_22-22-48-062. Then when I snapshot it in AppSync, date and time got added to the snapshot, so the snapshot name was 20150519_124910.snap.Xtremio-ds1_2015-05-18_22-22-48-062. Then when I was trying to restore the VM, it does this by creating a snapshot of the snapshot to mount back to the host. By then the name became too long and the operation failed. The fix was to rename the original datastore in XtremIO gui back to Xtremio-ds1. Then I made another snapshot and a VM restore worked.
Suggestion to VSI dev team: Don't tack on date and time to volume name for datastore. Just error if we try duplicate an existing name. Or, if you must add a value to make name unique, add a shorter value.
Another suggestion: Have an option in VSI to force AppSync to rediscover the datastores after you use VSI to create a datastore. If you create a datastore in VSI and then try to subscribe it to a service plan using VSI, the plan will fail until you go to the AppSync GUI and rediscover the datastores.