VM restore features with Veeam after migration to NSX-T
During the migration process your Virtual Datacenter will obtain a new internal identifier from VCloud Director. As a result, VM restores will require the disk restore process for backups created prior to migration.
You cannot run ‘Restore VM’ from a restore point which had been created before the migration to NSX-T. You will need to use the ‘Disk Restore’ process via ‘Virtual Disks’ from the top-menu or raise a ticket with Zettagrid if you have concerns and we will assist with the process if required.
New restore points after the migration can be restored as per the normal ‘Restore VM’ process.
Detailed example
Before the migration to NSX-T we have 2 restore points for the VM with name ‘VM001’, created by JOB with name my_backup
After the migration to NSX-T, if you try to ‘Restore VM’ from those restore points which had been created before migration to NSX-T. You will be faced with the following error.
To work around this error you can use Disk Level restore for early created restore points. Select ‘Virtual Disks' on the top menu.
NOTE: Each restore point created after the NSX-T migration will operate correctly again with the ‘Restore VM’ process and the VM restoration will work as expected.