You are not logged in.
Pages: 1
While I'm almost sure that it wasn't any other job running, but I'll check tonight, this is the log. My thought i that the software should had to send the mail, but it didn't.
ssh root@myremotehost 'cd /scratch/XSI/XSIBackup-DC;./xsibackup --replica "VMs(myVM)" root@remoterepo.com:22:/vmfs/volumes/datastore1/bkp --options=L --remote-path=/scratch/XSI/XSIBackup-DC/xsibackup --use-smtp=2 --mail-to=user@somemail.com --subject="subject"' | /scratch/XSI/XSIBackup-DC/ansi2txt > "/vmfs/volumes/datastore1/xsi-dir/var/logs/DCxsibackup.log"
"ansi2txt" is just to strip formatting escape sequences.
Obviously the same command was running previously, before switching to 1.4.0.0, my point is about the mail not the behavior, relaunching from command line it started, but I didn't check previously for the ".locked" file.
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
||| (c)XSIBackup-DC 1.4.0.0: Backup & Replication Software |||
||| (c)33HOPS, Sistemas de Informacion y Redes, S.L. | All Rights Reserved |||
||-------------------------------------------------------------------------------||
|---------------------------------------------------------------------------------|
(c)Daniel J. Garcia Fidalgo | info@33hops.com
|---------------------------------------------------------------------------------|
System Information: ESXi, Kernel 5 Major 5 Minor 0 Patch 0
-----------------------------------------------------------------------------------------------------------
License: purchasedxxxxxxxxxxxxxxxx
-----------------------------------------------------------------------------------------------------------
SSH: Tue Aug 25 13:12:53 UTC 2020
-----------------------------------------------------------------------------------------------------------
Remote system: vmkernel
-----------------------------------------------------------------------------------------------------------
Less Secure Ciphers enabled: arcfour,blowfish-cbc,aes128-ctr
-----------------------------------------------------------------------------------------------------------
PID: 84854724, Running job as: root
-----------------------------------------------------------------------------------------------------------
(c)XSIBackup-DC replicating data to /vmfs/volumes/datastore1/bkp
-----------------------------------------------------------------------------------------------------------
Performing --replica action
-----------------------------------------------------------------------------------------------------------
Item number 1 in this job
-----------------------------------------------------------------------------------------------------------
*** Remote directory is locked ***
-----------------------------------------------------------------------------------------------------------
The remote repository or replication directory is locked
This usually means that there's some process writing data
to it at this moment, or that some process was interrupted
Check for a file named .locked in the root of it and if
you believe it has been left there by some unfinished process,
you may delete it manually to allow new operations
-----------------------------------------------------------------------------------------------------------
2020-08-25T13:13:02 | Error code 2778 at file xsibackup.c, line 2778 | Error description: failed to lock the repo /vmfs/
volumes/datastore1/bkp
-----------------------------------------------------------------------------------------------------------
Removed <tmp> dir OK
-----------------------------------------------------------------------------------------------------------
Unlocked backup OK
-----------------------------------------------------------------------------------------------------------
SSH session was closed OK
-----------------------------------------------------------------------------------------------------------
Offline
Also, since yuu requested feedback, I launched it again from command line and progress is very inaccurate:
Backup start date: 2020-08-25 13:28:24
-----------------------------------------------------------------------------------------------------------
2020-08-25 13:28:24 | Backing up 15 files, total size is 190.00 GB
-----------------------------------------------------------------------------------------------------------
NUMBER FILE SIZE PROGRESS
-----------------------------------------------------------------------------------------------------------
1/15 .vmx 3.73 KB | Done 0.00%
-----------------------------------------------------------------------------------------------------------
2/15 .vmsd 45.00 B | Done 0.00%
-----------------------------------------------------------------------------------------------------------
3/15 .vmxf 4.26 KB | Done 0.00%
-----------------------------------------------------------------------------------------------------------
4/15 .nvram 8.48 KB | Done 0.00%
-----------------------------------------------------------------------------------------------------------
5/15 -flat.vmdk 40.00 GB | Done 0.00%
-----------------------------------------------------------------------------------------------------------
6/15 .vmdk 524.00 B | Done 21.05%
-----------------------------------------------------------------------------------------------------------
7/15 -flat.vmdk 150.00 GB | Done 21.05%
file 5/15 was 0.00% while copying, 6/15 started from 21.05, lasting same, 7/15 started from 21.05 and after 5 minutes is still at 21.05
Noticed that there there's no more "Details" row with real time progress.
Offline
You don't need ansi2txt with 1.4.0.0
Remove that pipe processing and try again.
The remote repo was locked, that means that previous process was interrupted, you should restart the replica or run --check on the remote side.
As per our tests progress is indeed accurate and shows detail, please remove the unneeded part and try again.
Offline
Pages: 1