#1 2019-03-20 10:46:17

Vincentf
Member
Registered: 2019-03-20
Posts: 4

ERROR (MKROOM01), details Error: cannot make 498G of room

Hello,
I'm using xsibackup pro version 11.2.3.
I'm doing this onediff job:
/vmfs/volumes/datastore1/xsi-dir/xsibackup \
--backup-prog=onediff \
--backup-point="/vmfs/volumes/backup/hotbackups" \
--backup-type=all \
--mail-to=contact@adhocexpert.com \
--use-smtp=1 \
--on-success="backupId->002" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"

chained to this xsitools job:

/vmfs/volumes/datastore1/xsi-dir/xsibackup \
--date-dir=yes \
--backup-room=2400 \
--backup-prog=xsitools:z \
--override=xsibakfilter \
--backup-point="/vmfs/volumes/backup/deduped-backups/xsit" \
--backup-type=custom \
--backup-vms="Uniflow_SD_XSIBAK,serveur2.INTRANET.local_XSIBAK,Pfsense_XSIBAK" \
--mail-to=contact@adhocexpert.com \
--use-smtp=1 \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"

The destination room is limited to 2400Gb for production purpose but there is about 800Gb more free.
Last night during backup I've received the error "ERROR (MKROOM01), details Error: cannot make 498G of room, only 454G can be made available"
I've checked that the job have a correct --date-dir option and checked that the format xsiopts is correct (by default).
It looks good and I don't understand why space have not been found by deleting some oldest backup. May someone help me please ?

here is the full mail received:Tue Mar 19 17:07:58 UTC 2019
XSIBACKUP-PRO 11.2.3 AT HOST:
ESX
    IP v4: 192.168.88.9/ 255.255.248.0
VMware ESXi 6.0.0 build-2494585


Done hot backup (id: unknown) using xsitools (compression enabled)
Backing up to folder /vmfs/volumes/backup/deduped-backups/xsit/20190319170756
The backup room has been limited to 2400 Gb.
Available room in device /vmfs/volumes/backup/deduped-backups/xsit before backup: 467 Gb.
Sparse size on disk of the selected virtual machines: 797 Gb.
Needed room in device /vmfs/volumes/backup/deduped-backups/xsit for backup: 534 Gb.
(Id)VM Name     State     Size (Gb)     Stop     Copy     Start     Time (min:sec)     Speed (mb/s)
(38) Uniflow_SD_XSIBAK    OFF    45.74/ 160.00    Off yet    OK    -     58:17     13/ 46
(39) serveur2.INTRANET.local_XSIBAK    OFF    486.42/ 607.54    Off yet    OK    -     231:57     35/ 44
The eldest folders were deleted to make room:
Error MKROOM01: cannot make 498G of room, only 454G can be made available
(40) Pfsense_XSIBAK    OFF    2.10/ 30.00    Off yet    OK    -     08:42     5/ 58
Available space in device /vmfs/volumes/backup/deduped-backups/xsit after backup: 370 Gb.
Complete backup elapsed time: 298 min
The ESXi configuration was saved to /vmfs/volumes/backup/deduped-backups/xsit/20190319170756
• [ Tue Mar 19 18:06:44 UTC 2019 ] ERROR (MKROOM01), details Error: cannot make 498G of room, only 454G can be made available

many thanks for your help !

Offline

#2 2019-03-20 14:44:21

admin
Administrator
Registered: 2017-04-21
Posts: 781

Re: ERROR (MKROOM01), details Error: cannot make 498G of room

Automatic deletion will only consider folders that meet the datedirmask as defined in the conf/xsiopts file

# The following variable holds the directory mask XSIBackup will use when
# deleting older dirs at the time to make room, you do not need to change it
# the pattern below is not a REGEX, but a regular Linux search pattern, it
# checks YYYYMMDDhhmmss strings. Bounds are not checked, just type/length
datedirmask=20[1-3][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]

Offline

#3 2019-03-20 16:20:36

Vincentf
Member
Registered: 2019-03-20
Posts: 4

Re: ERROR (MKROOM01), details Error: cannot make 498G of room

Thanks for your reply.

--date-dir is set to yes, and the directory name of each daily backup is seems to be ok accrding to what mentionned in the xsiopts file.
let see the destination backup directory
ls /vmfs/volumes/backup/deduped-backups/xsit/ -al
total 4
drwxrwxrwx    1 1024     users          446 Mar 19 22:06 .
drwxrwxrwx    1 1024     users            8 Feb 27 16:36 ..
-rwxrwxrwx    1 1024     users           63 Mar 19 22:06 .xsitools
drwxrwxrwx    1 1024     users          122 Feb 28 01:57 20190227163356
drwxrwxrwx    1 1024     users          190 Feb 28 21:14 20190228170729
drwxrwxrwx    1 1024     users          190 Mar  1 21:11 20190301170622
drwxrwxrwx    1 1024     users          190 Mar  4 22:20 20190304171002
drwxrwxrwx    1 1024     users          190 Mar  5 22:00 20190305170758
drwxrwxrwx    1 1024     users          190 Mar  6 22:18 20190306171439
drwxrwxrwx    1 1024     users          190 Mar  7 22:11 20190307170851
drwxrwxrwx    1 1024     users          190 Mar  8 22:15 20190308170847
drwxrwxrwx    1 1024     users          190 Mar 11 22:23 20190311171332
drwxrwxrwx    1 1024     users          190 Mar 12 22:17 20190312171400
drwxrwxrwx    1 1024     users          190 Mar 13 22:05 20190313170805
drwxrwxrwx    1 1024     users          190 Mar 14 22:01 20190314170814
drwxrwxrwx    1 1024     users          190 Mar 15 22:13 20190315170756
drwxrwxrwx    1 1024     users          190 Mar 18 22:16 20190318171052
drwxrwxrwx    1 1024     users          190 Mar 19 22:07 20190319170756
drwxrwxrwx    1 1024     users           32 Feb 27 16:35 data

looks good, no ?

thanks

Offline

#4 2019-03-20 17:05:27

admin
Administrator
Registered: 2017-04-21
Posts: 781

Re: ERROR (MKROOM01), details Error: cannot make 498G of room

Sorry, we had all the information in the backup job, our previous answer is not very precise, just generic.

That is an (c)XSITools repository, it's not a regular set of backup folders, but a deduplicated repository.
Timestamped folders do not contain actual data, but the hash maps to rebuild the virtual disks from the chunks stored in the data folder.
The --date-dir argument is useless in this case, as (c)XSITools automatically creates one recovery point per backup.

The message in the e-mail report seems clear, it looks like you only have 454G available, but we would need the full output to have access to all details. Take on account that the process will remove the older folders at the end of the backup process. I know it sounds weird, but it's to prevent data loss in case the backup fails. So you will always need some extra room to maneuver, depending on the size of your VMs. Tweak the --backup-room to accomodate the number of backups you can fit.

Offline

#5 2019-03-20 17:32:13

Vincentf
Member
Registered: 2019-03-20
Posts: 4

Re: ERROR (MKROOM01), details Error: cannot make 498G of room

Ok, well understood.
I'll try with --backup-room set at 2200Go and see if it going well.
Thanks.

Offline

#6 2019-03-21 09:13:12

Vincentf
Member
Registered: 2019-03-20
Posts: 4

Re: ERROR (MKROOM01), details Error: cannot make 498G of room

Hello,
On the existing backup disk, where there is not enought free space, how to free enought room to backup work again ?
if I launch it again with --backup-room set at 2000Gb, as it delete at the end, it will tell me that there is not enought room to process, doesn't it ?

Offline

#7 2019-03-21 10:13:45

admin
Administrator
Registered: 2017-04-21
Posts: 781

Re: ERROR (MKROOM01), details Error: cannot make 498G of room

You can use the --prune-xsitoolsrepo argument to manually prune a repository folder.

Offline

Board footer