Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: © XSITools » Issue with pruning » 2020-06-03 16:03:27
Thank you for the pointers, I will log a support ticket instead
#2 Re: © XSITools » Issue with pruning » 2020-06-02 18:48:06
Because I do not want to add more room ? The total size of the VM's i want to backup is about 400Gb. My understanding was , but correct me if am wrong, that with pruning, XSIBackup would never exceed that space.
#3 Re: © XSITools » Issue with pruning » 2020-05-27 06:58:07
That works for job 3 indeed, in job 2 however I did not use the --host argument. I can see pruning starting, but it then just stops. :
---------------------------------------------------------------------------------------------------------------------------------
2020-05-27T02:23:47| Excluded disks removed from backup .vmx file
---------------------------------------------------------------------------------------------------------------------------------
2020-05-27T02:23:47| Checking the size of the (c)XSITools repository...
---------------------------------------------------------------------------------------------------------------------------------
2020-05-27T02:24:15| The (c)XSITools repository is 518129Mb in size
---------------------------------------------------------------------------------------------------------------------------------
2020-05-27T02:24:15| Prune round 1: (c)XSITools repository size: 518129 exceeds --backup-room=512000
---------------------------------------------------------------------------------------------------------------------------------
-e -- Pruning exclusive blocks of backup </backup/vmware/20200502150451>
---------------------------------------------------------------------------------------------------------------------------------
--- and then nothing anymore
#4 © XSITools » Issue with pruning » 2020-05-26 07:27:45
- handude
- Replies: 6
I have 3 backup jobs running. Yesterday the first one came back with a warning about pruning, but concluded successfully.
The second backup job is identical to the first one, albeit it to another host. The logs show again that the pruning process was started, but after that nothing anymore.
Job number 3 will not run now and comes back with an error code.
Although it looks like that XSIBackup is hanging or waiting for something, there is no reference at all to xsibackup in the server's process list.
Notifications and errors from the log file:
Job 2 pruning started and seems to be hanging (the job at the bottom is Job 3 that is starting later on):
2020-05-26T02:21:29| The (c)XSITools repository is 513726Mb in size
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T02:21:29| Prune round 1: (c)XSITools repository size: 513726 exceeds --backup-room=512000
---------------------------------------------------------------------------------------------------------------------------------
-e -- Pruning exclusive blocks of backup </backup/vmware/20200502150451>
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T07:00:10| ###############################################################################
2020-05-26T07:00:10| XSIBACKUP-PRO 11.2.19: new execution request
2020-05-26T07:00:10| ###############################################################################
error code for job 3:
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T07:03:31| Remote backup job exit status was:
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T07:03:31| Original Unique Id (OUID):
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T07:03:31| Cannot match current Session Id to parsed OUID var
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T07:04:12| Remote backup job exit status was:
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T07:04:12| Original Unique Id (OUID):
---------------------------------------------------------------------------------------------------------------------------------
2020-05-26T07:04:12| Cannot match current Session Id to parsed OUID var
Pages: 1