Veritas CloudPoint Release Notes
- Getting help
- Known issues
- Fixed issues
Disk-level snapshot restore to the same location fails if an application was previously added and removed on the same disk (13196)
If you create and remove an application from a disk and then use the same disk to create a new application, then when you try to restore disk-level snapshots of the new application to the same location, the restore operation fails.
For example, consider a disk
Disk1 on which you created an application
MyApp1. Now remove
MyApp1 and create another application
MyApp2 on the same disk (
Disk1) and then take disk-level snapshots of that disk. When you try to restore the new application (
MyApp2) disk-level snapshot to the same location, the restore operation fails.
flexsnap-coordinator logs contain the following:
flexsnap-coordinator: <ID> flexsnap-coordinator Thread-26113 flexsnap.connectors.base: ERROR - Request failed unexpectedly flexsnap-coordinator: File "/opt/VRTScloudpoint/lib/flexsnap/coordinator.py" , line 5542, in verify_single_leaf_child flexsnap-coordinator: therefore, cannot do original location restore" % asset_type) flexsnap-coordinator: GenericError: Another application would be affected therefore, cannot do original location restore
This issue occurs because references of the application (
MyApp1) that was deleted from the disk (
Disk1) are retained in the CloudPoint assets database. A restore of the new application (
MyApp2) disk-level snapshot fails to overwrite the old references on the same disk (
There is no known workaround for this issue. As an alternative, you can try performing the disk-level restore to a new location.