#1 2019-01-04 00:45:37

cuchillo
Member
Registered: 2019-01-03
Posts: 36

backup-room option and prune. Size misunderstood

XSITools in version 11.2.0 should purge the repositories according to the specified parameter with the backup-room option. The backup-room option is specified in GB but the purge considers the value specified in MB.

The backup command is this:
"/vmfs/volumes/SYSTEM/xsi-dir/xsibackup" \
--backup-prog=xsitools:z \
--backup-point="/vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/" \
--backup-type=custom \
--backup-vms="GESTION2003" \
--backup-how=warm \
--backup-room=300000 \
--smart-info=yes \
--backup-id=001 \
--description="WL GESTION2003" \
--exec=yes >> "/vmfs/volumes/SYSTEM/xsi-dir/var/logs/xsibackup.log"


Here the logs …

** with backup-room=300

2019-01-04T00:06:04|  Needed room: 38 Gb.
2019-01-04T00:06:04|  Sparse size: 38 Gb.
2019-01-04T00:06:04|  Available room: 299 Gb.

* so far so good, but then

2019-01-04T00:17:31|  Checking the size of the (c)XSITools repository...
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:17:39|  The (c)XSITools repository is 99615Mb in size
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:17:39|  Prune round 1: (c)XSITools repository size: 99615 exceeds --backup-room=300

Pruning exclusive blocks of backup </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190103201154>
1/2190 blocks | freed 43 Mb | Processed 0% [0K
2/2190 blocks | freed 58 Mb | Processed 0% [0K
3/2190 blocks | freed 87 Mb | Processed 0% [0K

2189/2190 blocks | freed 81775 Mb | Processed 99% [0K
2190/2190 blocks | freed 81813 Mb | Processed 100% [0K
Deleting </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190103201154> directory (0 Mb)
Blocks deleted: 2190
Space saved: 81813 Mb
2019-01-04T00:21:22|  The (c)XSITools repo </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS> was pruned, 81813 Mb were made available
2019-01-04T00:21:22|  The size of the repo was reduced to 17802
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:21:22|  Prune round 2: (c)XSITools repository size: 17802 exceeds --backup-room=300
---------------------------------------------------------------------------------------------------------------------------------
Pruning exclusive blocks of backup </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190104000539>
2019-01-04T00:21:22|  -- Nothing to prune
2019-01-04T00:21:44|  The ESXi configuration was saved to "/vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190104000539"
---------------------------------------------------------------------------------------------------------------------------------

** As U can see the older backup was removed and the exclusive blocks has been transferred to the current, but there was room yet. That was not necessary yet.

** Now I set backup-room=300000. XSIBackup take all the available space on my disk as room.
2019-01-04T00:26:17|  Needed room: 138 Gb.
2019-01-04T00:26:17|  Sparse size: 138 Gb.
2019-01-04T00:26:17|  Available room: 3467 Gb.

** It says more needed room because I add a VM to this backup… ignore it.
**The thing is when the first VM backup is ended…
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:38:56|  Checking the size of the (c)XSITools repository...
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:39:02|  The (c)XSITools repository is 21456Mb in size
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:39:02|  There's still 278544 Mb available, no need to prune the repo
---------------------------------------------------------------------------------------------------------------------------------

** As U can see the 278544 MB available are the result of 300000 – 21456. It the set backup room but considered in MB – the repo size.

Offline

#2 2019-01-04 19:58:07

admin
Administrator
Registered: 2017-04-21
Posts: 1,363

Re: backup-room option and prune. Size misunderstood

Read the last post in this thread:
https://33hops.com/forum/viewtopic.php?id=380

Offline

Board footer