Error message generated from vRanger during backups:
"Object reference not set to an instance of an object."
One possible cause is:
Nvram file missing the vm_name ( example nvram instead of vm_name.nvram)
There are some cases where nvram file is missing the vm_name, causing backup jobs to fail with error – "object reference not set to an instance of an object".
The VM will boot and shutdown without errors but Ranger will not perform the backup.
Step 1: Power down the VM and Remove from Inventory.
Step 2: Putty into the host
run: vmware-cmd –l (to list VMs)
Step 3: cd to the VM in question:
run: ls –lah (to view its folder contents)
Step 4: Notice all the files have the vm_name.file extension, except nvram. If this is true proceed to step 5.
Step 5: run: mv nvram vm_name.nvram (here we are renaming the file to vm_name.nvram)
Now we want to tell the vmx file of the change made.
Step 6: nano vm_name.vmx
Step 7: search for nvram,( usually the line below floppy0.present), and add nvram = “vm_name.nvram” (here we are adding the location of the nvram file)
Step 8: CNTRL X, y, Enter to save changes
Now we need to register the VM into VCenter
Step 1: Login VIClient
Step 2: Find the host in Inventory view
Step 3: Select summary Tab
Step 4: Right click the datastore.
Step 5: Find the VMs directory
Step 6: Find the vmx file
Step 7: Right click and add to inventory.
Step 8: Now power on the VM, and Run the backup job.