#1 2018-12-13 07:20:28

paulee
Member
Registered: 2018-12-10
Posts: 13

No space

Hello please how i can manage disk space on jobs?
Last error raised for the above VM:
ERROR CLVMKFS1, details: [server] error: vmkfstools error, details: Failed to clone disk: There is not enough space on the file system for the selected operation (13).

i have this jobs

"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--certify-backup=yes \
--backup-point=/vmfs/volumes/synology/zalohy/$( date +%Y%m%d-%H%M ) \
--backup-type=Custom \
--backup-vms="voip-ustredna,server" \
--backup-how=Hot \
--remote-xsipath=/vmfs/volumes/datastore1/xsi-dir \
--use-smtp=1 \
--backup-room=690 \
this backup-room dont work sad

Offline

#2 2018-12-31 09:37:06

paulee
Member
Registered: 2018-12-10
Posts: 13

Re: No space

Why backup room dont work? sad where i can manage backup room? thank you

Offline

#3 2019-01-02 13:24:16

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

Re: No space

--backup-room argument is useless if your disk is already full. Free some space manually.
The --backup-room value is expressed in Mb., thus 690 means: use 690 Mb. to store my backups.

CORRECTION 2019-01-03:

--backup-room is expressed in Gb., not Mb.

Offline

#4 2019-01-02 23:09:41

Random Thoughts
Member
Registered: 2018-03-12
Posts: 19

Re: No space

admin wrote:

The --backup-room value is expressed in Mb., thus 690 means: use 690 Mb. to store my backups.

Are you sure?

From my backup job -

--backup-room=500

From the confirmation email (received after backup) -

The backup room has been limited to 500 Gb

Offline

#5 2019-01-03 08:22:28

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

Re: No space

Yes, we meant Gb. not Mb.

Offline

#6 2019-01-14 09:59:19

paulee
Member
Registered: 2018-12-10
Posts: 13

Re: No space

When I enter this report from the limit, it is 690GB and it will not be able to erase the capacity so that it frees up additional capacity. Why can not you clear it? Where can you make a mistake?

Offline

#7 2019-01-14 16:54:41

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

Re: No space

I'm sorry sir, we don't undertand your question, would you be so kind to reformulate it.

Offline

#8 2019-01-15 07:19:38

paulee
Member
Registered: 2018-12-10
Posts: 13

Re: No space

Ok i receive this email.
----------------------------------
Done hot backup (id: 001) using vmkfstools (no compression)
The backup room has been limited to 690 Gb.
Available room in device /vmfs/volumes/synology/zalohy/20190114-1554 before backup: 132 Gb.
Sparse size on disk of the selected virtual machines: 160 Gb.
Needed room in device /vmfs/volumes/synology/zalohy/20190114-1554 for backup: 160 Gb.
(Id)VM Name    State    Size (Gb)    Stop    Copy    Start    Time (min)    Speed (mb/s)
(1) voip-ustredna    ON    10/ 10    NO (hot backup)    OK    -    1    97/ 97
(3) server    ON    150/ 150    NO (hot backup)    KO!    -    63    40/ 40
The eldest folders were deleted to make room:
Error MKROOM01: cannot make 162G of room, only 130G can be made available
Last error raised for the above VM:
ERROR CLVMKFS1, details: [server] error: vmkfstools error, details: Failed to clone disk: There is not enough space on the file system for the selected operation (13).
Available space in device /vmfs/volumes/synology/zalohy/20190114-1554 after backup: 130 Gb.
Complete backup elapsed time: 65 min
Backup of ESXi configuration is not available in XSIBACKUP-FREE
Get XSIBACKUP-PRO at http://33hops.com
• [ Mon Jan 14 15:56:03 UTC 2019 ] ERROR (MKROOM01), details Error: cannot make 162G of room, only 130G can be made available

• [ Mon Jan 14 16:59:34 UTC 2019 ] ERROR (CLVMKFS1), details [server] error: vmkfstools error, details: Failed to clone disk: There is not enough space on the file system for the selected operation (13).
--------------------------------------------------


and i have cron job

----------------------------------
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=vmkfstools \
--certify-backup=yes \
--backup-point=/vmfs/volumes/synology/zalohy/$( date +%Y%m%d-%H%M ) \
--backup-type=Custom \
--backup-vms="voip-ustredna,server" \
--backup-how=Hot \
--remote-xsipath=/vmfs/volumes/datastore1/xsi-dir \
--use-smtp=1 \
--mail-to=admin@gmail.com \
--backup-id=001 \
--backup-room=690 \
--description="Zalohovanie" \
--override=xsibakfilter \
--on-success="backupId->001" \
--on-error="backupId->001" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
---------------------------------------

I have a backup room but the script can not delete the old backup and I do not know why. When I manually delete them all goes further. But the script can not delete the old one.

Offline

#9 2019-01-15 13:24:57

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

Re: No space

The message is clear:

Error MKROOM01: cannot make 162G of room, only 130G can be made available

Only folders matching the YYYYMMDDhhmmss mask are considered for deletion, this is clearly stated in the posts covering this topic.

Offline

#10 2019-01-16 10:43:33

paulee
Member
Registered: 2018-12-10
Posts: 13

Re: No space

Now backup file is 201901160924  this is correct name folder? or bad?
--backup-point=/vmfs/volumes/synology/zalohy/$( date +%Y%m%d%H%M ) \

Offline

Board footer