We have a customer who needs to restore a large VM (multiple disk and TB’s).
This job runs for days and than ends with Failure Reason: Unable to modify the VMX file for restore of virtual machine [vm-name].
Attempt start error: [The parameter is incorrect., Port passed is not valid. [0/0]. (W32.87)]
We did not find out why, but customer would like to see that the disks restored are not automatically deleted. Is there a way in Commvault?
Does the additional setting SkipDeleteVm also apply on “regular” VM restore or only on Virtualize Me?
And would an Service account with no delete be an outcome or does this have to many side effects?
Already my thank in advance.
Best answer by Gopinath
That key is not applicable for regular Full VM restore from VSiDA.
In general, full VM restore has restart ability. its resumes from where it left part of previous attempt. Hence will not delete VM and its files in that. After reaching max attempts and if still fails then VM gets deleted and job fails.
Can you check VM and VMX file accessibility in vSphere client. Also please cross check, free space on destination datastore and disk types used in restore of that VM, if any disk occupying whole space on DS.
If logs over rolled,re-try with fresh job and raise a ticket with CV support with complete logs of VSA proxy to check it in that case.