You are not logged in.
Pages: 1
Hi
This day, the backup is stuck.
The backup as not finished since about 10 hours, and the job logs dont have new line in here.
The ps aux in vmware show lines like this :
21942809 21942809 sh 21942809 User WAIT UWAIT 0-19 0.4195 /bin/sh -c "/vmfs/volumes/DATASTORE1/XSIBACKUPPRO/XSIBackup-Pro/jobs/1"
21942812 21942812 busybox 21942812 User WAIT UWAIT 0-19 0.2419 ash /vmfs/volumes/DATASTORE1/XSIBACKUPPRO/XSIBackup-Pro/jobs/1
21942815 21942815 sh 21942815 User RUN NONE 0-19 48047.649032 /bin/sh /vmfs/volumes/DATASTORE1/XSIBACKUPPRO/XSIBackup-Pro/xsibackup --backup-prog=XSITools:z --snapshot=doquiesce --backup-point=/vmfs/volumes/Q18AI15841_S4AUE736_Backup0/BACKUP/FULLDEDUPLZO --backup-type=All --backup-how=Hot --del-dirs=+15d --use-smtp=2 --mail-to=xxx --backup-id=1 --description=xxx --subject=xxx --exec=yes
Is it linked with the rotation "--del-dirs=+15d" or something else ?
What can i do for debug ?
At this time i must kill the process.
Thanks for your reply.
Offline
Please, do not name jobs outside its naming scheme 000-999
Depending on the amount of data you are storing, rotating data can take a long time.
You should inspect what's going on in the log before actually killing the process:
tail -f /scratch/XSI/XSIBackup-Pro/var/logs/xsibackup.log
Offline
"Outside is naming scheme"?
Can you detail please, i have followed the wizard UI since i had the pro version.
Here i the result :
[root@S4AUE736:/vmfs/volumes/5e99e293-82496ade-eeee-7cd30a6a4330/XSIBACKUPPRO/XSIBackup-Pro] tail -f /vmfs/volumes/DATASTORE1/XSIBACKUPPRO/XSIBackup-Pro/var/
logs/xsibackup.log
sent 407 bytes received 35 bytes 884.00 bytes/sec
total size is 310 speedup is 0.70
---------------------------------------------------------------------------------------------------------------------------------
sending incremental file list
PGT-EBP-000002-sesparse.vmdk
189,800,448 100% 22.59MB/s 0:00:08 (xfr#1, to-chk=0/1)
sent 189,846,887 bytes received 35 bytes 19,983,886.53 bytes/sec
total size is 189,800,448 speedup is 1.00
---------------------------------------------------------------------
Last edited by drubio@365it.fr (2020-07-01 11:02:42)
Offline
You published this URL in your first post:
/vmfs/volumes/DATASTORE1/XSIBACKUPPRO/XSIBackup-Pro/jobs/1
Which shows some job named "1" instead of "001"
Your log shows that the program halted, you may be low of memory or be experiencing some network problem.
Try to look for some possible cause in the logs of your ESXi host and the backup host too.
Offline
Thanks for your reply.
At this time, how can i stop the job "properly" ?
Will be a specific command to test the deduped data ?
Last edited by drubio@365it.fr (2020-07-01 11:15:22)
Offline
You said to have already stopped it.
The only way to stop a process is through Linux signalling:
kill -9 PID # To stop it immediately
kill -15 PID # to request a gentle shutdown
As (c)XSIBackup just reads data, you may stop it forcefully, the backup won't be good though.
Offline
Thanks.
Must we check the deduped repository after that ?
With wich command ?
Offline
If you interrupt an XSITools:z backup, you will generate half written block manifests at the YYYYMMDDhhmmss timestamped directory, thus you should remove that folder. When you do that you will leave some orphan blocks (blocks which were only present in the backup that was halted). This is not crucial, as will only occupy some MBs and they will be pruned next time you prune the repository.
To check a repository at any time:
./xsibackup --check-xsitoolsrepo=/path/to/repo
Offline
ok thanks
Offline
Please, note this thread corresponds to an old software edition - (c)XSIBackup Classic - which has been deprecated. Use our latest software edition: [b](c)XSIBackup-DC[/b] and refer to [url=https://33hops.com/xsibackup-dc-full-manual-home.html]its manual[/url] to [url=https://33hops.com/xsibackup-vmware-esxi-backup.html#prodchart]backup your (c)ESXi VMs[/url] as of 2021
Offline
Pages: 1