|
Forum ©XSIBackup: ©VMWare ©ESXi Backup Software©XSIBackup-Free: Free Backup Solution for ©VMWare ©ESXi©XSIBackup-DC & Pro: ©VMWare ©ESXi Backup Professional Tools |
![]() |
You are not logged in.
Pages: 1
I have the problem that that the xsibackup tmp folder is not being cleaned up
correctly after a backup.
This is my job command:
/vmfs/volumes/xxx/xsi/xsibackup \
--backup \
"VMs(VM1, VM2, VM3)" \
"root@my_ip:22:/srv/xsibackup_repo/" \
--remote-path=/my_home/xsi/xsibackup \
--rotate=25 \
--compression=yes \
--mail-to=backups@jes.be \
>> /vmfs/volumes/xxx/xsi/var/log/xsibackup.log 2>&1
Xsibackup is installed in the /scratch directory. Xsibackup is running as root.
When the job has finished, it leaves stuff in the /scratch/xsi/tmp directory,
and after a while the backups fail because it is full.
I emptied the directory three days ago, and now it looks like this:
# ls -ld /scratch/xsi/tmp/*
drwxr-xr-x 1 root root 8 Apr 28 10:15 /scratch/xsi/tmp/2923915
drwxr-xr-x 1 root root 8 Apr 29 10:14 /scratch/xsi/tmp/2981378
du -sh /scratch/xsi/tmp/*
322.8M /scratch/xsi/tmp/2923915
325.1M /scratch/xsi/tmp/2981378
This is the from the log file. It shows the end of the backup that left behind
the folder 2923915
Backup end date: 2020-04-28 11:36:43
-----------------------------------------------------------------------------------------------------------
Time taken: 4849 sec.
-----------------------------------------------------------------------------------------------------------
Total time: 45274 sec.
-----------------------------------------------------------------------------------------------------------
Full file speed: 35.06 mb/s
-----------------------------------------------------------------------------------------------------------
Real data speed: 21.10 mb/s
-----------------------------------------------------------------------------------------------------------
Item backup completed
-----------------------------------------------------------------------------------------------------------
Differential blocks were added to the .blocklog database
-----------------------------------------------------------------------------------------------------------
Data processing completed successfully
-----------------------------------------------------------------------------------------------------------
Could not find SMTP -1, falling back to SMTP 1
-----------------------------------------------------------------------------------------------------------
Sending e-mail to my_email...
-----------------------------------------------------------------------------------------------------------
E-mail was sent OK
-----------------------------------------------------------------------------------------------------------
--rotate option was detected, retrieving backups to prune...
-----------------------------------------------------------------------------------------------------------
Nothing to prune as per the rotation figure
-----------------------------------------------------------------------------------------------------------
Removed <tmp> dir OK
-----------------------------------------------------------------------------------------------------------
Unlocked backup OK
-----------------------------------------------------------------------------------------------------------
SSH session was closed OK
-----------------------------------------------------------------------------------------------------------
Removed PID OK
Thanks for your help,
Greetings,
lieven
Offline
If (c)XSIBackup-DC is installed in the /scratchXSI/XSIBackup-DC default location, why does your job point to some xsibackup binary in a different place:
/vmfs/volumes/xxx/xsi/xsibackup
The job also points to some xsibackup.log file in a different place.
>> /vmfs/volumes/xxx/xsi/var/log/xsibackup.log 2>&1
Offline
Well, it's not a different place, but another name for the same place.
The xxx was used to hide the scratch volume id.
Offline
This bug will be solved in next version 1.3.0.0, sorry about the inconvenience.
Offline
Pages: 1