when I use the --backup option with a VM that has been renamed (it is not named the same as the folder that contains it in the datastore) the bakcup is performed but I get errors like this
· VM: 2021-07-27T20:12:09 | Error code 4054 at file xsibackup.c, line 4054 | Error description: could not rename .vmx.tmp file to .vmx, error:
· VM: 2021-07-27T20:12:11 | Error code 4063 at file xsibackup.c, line 4063 | Error description: could not rename .vmsd.tmp file to .vmsd, error:
· VM: 2021-07-27T20:12:14 | Error code 4294 at file xsibackup.c, line 4294 | Error description: some error/s were raised while backing up: VMs(VM), error count is: 2
I understand that XSIBackup-DC somehow uses a combination of interpretation of the directory structure and the existence and content of the .vmx file to determine whether or not it is a VM and in the positive case to determine which files to copy.
It seems to me that it would be much less susceptible to errors in cases of particular configurations if, when using VMs (....), it based the decision of what to make a backup by interpreting the .vmx and that if you use a folder as a source it is limited to copying whatever is inside. (links with my post XSIBackup-Pro and XSIBackup-DC combination)
Always post the output when requesting help, otherwise we have to guess all the data that is not there.
We can't reproduce your issue. Renaming the VM does not affect detecting and renaming files associated to the VM.
We just fixed a problem triggered by some faulty versions of OpenSSL in some older versions of (c)ESXi in branch 5 and early 6
Download 184.108.40.206 and try again. Let us know if that fixed your issue.
a VM that has been renamed (it is not named the same as the folder that contains it in the datastore)
I recognized a behaviour when a VM has been renamed. XSIBackup-DC then creates two folders for the VM in the repo. One folder is named like the new VM name, the other is named like the folder.
The folder named like the new VM name is always empty, the actual backup data (map files) are placed the other folder which is named like the VMs folder.
Is this behaviour intentional?
Would it be possible not to create a empty folder named like the new VM name? I think it's just confusing to have two folders.
Yes, we know that. It's due to the fact that up until some point in the job, the folder name is used versus the VM name at some other points. We will fix this behaviour.
Still, until we do (this does not affect the backups) try to rename things to keep a coherent naming convention: i.e. if your VM is named MY-VM, name the folder where it resides as MY-VM too, as well as the VHD files.