You are not logged in.
Pages: 1
That was duplicate crond process !
thanks for your fast support by mail for Registered users.
.locked doesn't exist before Scheduled Job so I can't delete it.
Never error with manually started jobs.
I have only error if started from Scheduler.
The error is displayed but backup continue and final report success by mail is sent.
Job run without error when running from GUI
From Scheduled/Cron, error is in xsibackup.log :
*** Remote directory is locked ***
Lock file: /vmfs/volumes/c8c8b8a5-821a12d9/vm-RDS/20211024130101/RDS/.locked
-------------------------------------------------------------------------------------------------------------
The remote repository or replication directory is locked
you may delete it manually to allow new operations
-------------------------------------------------------------------------------------------------------------
2021-10-24T13:01:03 | Error code 3682 at file xsibackup.c, line 3682 | Error description: failed to lock the repo /vmfs/volumes/c8c8b8a5-821a12d9/vm-RDS/20211024130101a first mail is sent with that error , but backup continue
then second mail is sent with success backup without error.
I notice in first mail with the error time is displayed "UTC | Thu, 01 Jan 1970 00:00:00" instead real date/time.
sorry for my poor english (french here ...)
thanks I get it : dedup works on aligned blocks , so even with my same windows "base" , dedup cannot be done at that level.
incremental backup per vm works really nice , speed & delta size.
so 1 repo per vm is prefered for my head
while testing, backup 3 windows server 2016 , same windows update level. total size was equal to the total size of 1 repo per VM.
repo which share multi VM, is only prune operation dedup the blocks ?
is repo share blocks between VMs ?
Pages: 1