You are not logged in.
Hi guys,
I have setup the new Free version (11.2.9) to backup two VMs, after they upgraded their ESXi to 6.5 (build-17167537). I setup a job (001) and ran that job manually, to see whether it is working. The manual run, had no issues and backed up both VMs perfectly fine. I installed the cron ability of XSIBackup, so we can run the backup job automated at a specified time and waited for the next day, to look into the log.
In the log I noticed that the backup job finished but with an error for one of the VMs:
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/Datastore/o2e-staging/o2e-staging_2.vmdk'...
Clone: 10% done.
---------------------------------------------------------------------------------------------------------------------------------
2020-12-09T04:08:14| [o2e-staging] CLVMKFS1 error: Failed to clone disk: The file specified is not a virtual disk (15).
---------------------------------------------------------------------------------------------------------------------------------
It's totally weird to me, since the manual run is always working fine. Could this be an issue with the cronjob? Although I set that up as all our other XSIBackup instances, and they work as well.
I'm clueless what else it could be and would be grateful for any help I can get with this.
Thanks in advance
Last edited by HigH_HawK (2020-12-09 09:34:18)
Offline
Hi again,
I think I have found the culprit causing this issue. After rechecking the XSIBackup log, I noticed the following line and the mentioned filesystem:
2020-12-09T04:00:06| --backup-point found at /vmfs/volumes/Backup_NFS (filesystem: NFS41)
As your website ([url=https://33hops.com/xsibackup-most-common-issues.html](c)XSIBackup most common issues[/url]) states, there are common issues with NFS 4.1, so this is probably the cause of my issue. I will now try to remove the attached data storage and reattach it with NFS3 and try the procedure again.
I will report back, once I have changed it and the backup ran in the morning via cronjob.
Offline
Yes, there use to be problems with NFS 4 in some ESXi versions.
Just switch down to NFS 3, you don't have any advantage in using NFS 4
Offline
I can confirm, that reattaching the datastore as NFS 3 solved my problem.
Offline
Thank you for your feedback.
Offline