Symptoms
Virtual Machine recovery that is performed through the NVP vProxy appliance fails with the following error in the recovery output
153335:nsrvproxy_recover: Virtual machine recovery failed: Unable to find a usable volume for recovery of saveset ####
180579:nsrmm: SSID#/CloneID# is not in the media index.
Cause
The NetWorker VM saveset needed for restore is expired (fl = cE, ssflags = vrEF) mminfo -kot -q vmname=VM_NAME -r volume,name,savetime,ssid,cloneid,ssflags
root@linux1:~# mminfo -kot -q vmname=winclient02 -r volume,name,savetime,ssid,cloneid,ssflags
volume name date ssid clone id ssflags
VMBackupPool.001 vm:502153fa-fe79-c07e-ff8a-79dbf166e66f:vcsa.amer.lan 11/13/2022 594652987 1668394811 vrEF
Resolution
1. Run the following commands to change expired saveset to recoverable.
Option 1. If the saveset is still present in Data Domain, we can scan it back into the media database.
scanner -m -S VM_backup_SSID device_name
Option 2. Change the saveset to notrecyclable and then change expiration accordingly.a. Get the ssid and cloneid of the backup:
mminfo -kot -q vmname=VM_NAME -r volume,name,savetime,ssid,cloneid,ssflags
b. Using the ssid and cloneid, set the save set to notrecyclable
nsrmm -o notrecyclable -S SSID/Cloneid
root@linux1:~# nsrmm -o notrecyclable -S 594652987/1668394811
Mark save set copy 594652987/1668394811 as not recyclable? yes
c. Set the retention to a date of your choosing:
nsrmm -e "mm/dd/yy" -S SSID/cloneid
root@linux1:~# nsrmm -e "12/16/2022" -S 594652987/1668394811
If this saveset has dependents with longer retention periods, the dependent savesets will not be browsable after the retention policy expiration date `Fri Dec 16 00:00:00 2022'.
Are you sure you want to change the retention policy expiration of this saveset to `Fri Dec 16 00:00:00 2022'? (yes/no) [no] yes
The retention time for the save set name 'vm:502153fa-fe79-c07e-ff8a-79dbf166e66f:vcsa.amer.lan' with save set ID '594652987' has been changed to 'Fri Dec 16 00:00:00 2022'.
2. Validated the flags showing cr
mminfo -avot -q ssid=VM_data_SSID
volume type client date time size ssid fl lvl name
VMBackupPool.001 Data Domain vcsa.amer.lan 11/13/2022 07:00:12 PM 188 GB 594652987 cr full vm:502153fa-fe79-c07e-ff8a-79dbf166e66f:vcsa.amer.lan
VMClonePool.001 Data Domain vcsa.amer.lan 11/13/2022 07:00:12 PM 188 GB 594652987 cr full vm:502153fa-fe79-c07e-ff8a-79dbf166e66f:vcsa.amer.lan
3. Run VM Restore from NMC (Under monitoring tab > recover rate should show up the speed to confirm the restore).NOTE: VM savesets always appear as "cb" and never as "cr" because they hold no indexes. The way FLR recovery works is similar to BBB, and different from traditional file system backups. No indexes are needed in order to do FLR, just a saveset in a Data Domain device.
