Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
#1 2021-11-27 12:00:40
- herrep
- Member
- From: Munich
- Registered: 2019-07-08
- Posts: 106
XSIBackup-DC 1.5.1.4: Error code 1522 at file common.c, line 1522
Hi,
when executing XSIBackup-DC 1.5.1.4 for a number VMs in one command with the options --replica=cbt --options=R --quiesce --config-backup --backup-how=hot , I received the following error message for one of the replicated VMs:
Error code 1522 at file common.c, line 1522 | Error description: error running command, returned: 1
The error log did not report any additional information than that available in the regular output of XSIBackup-DC.
When having a look into the replicated directory, I can see that the files of the VM reporting the error have been replicated. However, I noticed that additional snapshot files (extension .vmsn) were present in the replicated directory from a previous replication. These superfluous files were not present in the original directory.
Could it be that XSIBackup-DC tried to delete these files, but had some issues with deleting them?
In any case, I wonder what the meaning of error code 1522 is. Furthermore, I suggest to add some information to XSIBackup-DC so that it is clear what the meaning of the error.
Best regards,
Peter
Offline
#2 2021-11-27 14:47:43
- admin
- Administrator
- Registered: 2017-04-21
- Posts: 2,055
Re: XSIBackup-DC 1.5.1.4: Error code 1522 at file common.c, line 1522
Some remote command is failing and returning 1 instead of 0.
Run with --debug-print to find out which is the last command that is failing and use
ssh -vvv root@1.2.3.4 "failing command" To debug the exact remote bash command.
Offline
#3 2021-11-27 14:51:12
- herrep
- Member
- From: Munich
- Registered: 2019-07-08
- Posts: 106
Re: XSIBackup-DC 1.5.1.4: Error code 1522 at file common.c, line 1522
Thank you very much for providing a hint as how to debug this scenario.
Unfortunately, I cannot reproduce this error again. I had some issues with extended permission settings on the NFS mounted target directory. After repairing the permissions I could execute the replication without any errors.
Offline