You are not logged in.
VMkernel vmhost01.mtka.eu 6.5.0 #1 SMP Release build-17477841 Jan 17 2021 19:24:58 x86_64 x86_64 x86_64 ESXi
In --replica jobs with --config-backup, replication is performed and logged correctly, config backup, instead, is logged, but no directory/file/archive is found in the target path.
Offline
We'll check this. Thank you for your feedback.
Offline
We have checked this feature and it's working fine. The configuration is saved to the cfgbak folder in the same folder as the replica VM directory.
Offline
I created the [b]cfgbak[/b] directory and, after last run of xsibackup, at least one replication job created the compressed archive with ESXi configuration data.
Offline
That is weird. That directory should be created automatically. Maybe somehow you asigned full permissions on the replica folder, but not on the relative root. This can happen if you use some other user than root.
Offline
I double checked permissions, but they seem OK.
Replication target path is on a VMFS datastore connected to a multipathed iSCSI target.
Offline
Maybe multipathing is the culprit, not an expert, but some round robin splitting system calls could be an issue. There should be some option for this in the iSCSI client configuration.
Offline
I guess not. We moved PB of VM-related data for years between multiple 2- or 4-pathed iSCSI backed datastores and never lost a byte.
Offline
This issue is not something obscure. It's a simple system call (mkdir) that creates that dir. You can run some job with strace (just prepend 'strace' to it) to detect the exact reason why the system call fails. It will produce a lot of output though, and will be slower.
Are you using some kind of Async option maybe?
Offline
Probably related to [url=https://33hops.com/forum/viewtopic.php?id=944]this issue[/url]?
Offline
As stated, we are talking about a simple atomic mkdir system call, not any complicated set of commands. Strace will offer you all the details on the issue. It could be that some DS in async mode would not create the folder in time for the subsequent commands to be able to copy to it. If that was the case, switching to Sync mode would solve the issue.
We could add a helper to wait until we detect the folder, but that would be misleading, as the rest of the program works in Sync mode. Could be some other thing, we'll keep investigating, we haven't been able to reproduce the issue though.
Offline
Could you give some hints as how to switch to sync mode?
Could you briefly explain why the mentioned helper to wait until the folder is created would be misleading? Besides, the folder does not appear to be created at all - at least at my system, cfgbak is simply not there. I only succeed when manually creating the folder and restarting the replica operation again. So I wonder why waiting for the folder to be created would be an option.
Offline
If you can steadily reproduce your error, you should first prepend strace to your job, run it and post at least the end of the output.
strace ./xsibackup --backup ....
Offline