Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

my_33hops

Member

Registered: 2017-06-04

Posts: 9

XSIBACKUP errors detected

Hello,

I´using ESXi 6.5 with XSIBACKUP-FREE 9.0.2 since several month.

Since about one week I get the following errors:

Tue Jun 6 02:00:03 UTC 2017
XSIBACKUP-FREE 9.0.2 AT HOST:
esx    IP v4: 192.168.100.249/ 255.255.255.0
VMware ESXi 6.5.0 build-5310538

Done hot backup, using vmkfstools.
Backing up to folder /vmfs/volumes/backup/20170606020002
The backup room has been limited to 500 Gb.
Available room in device /vmfs/volumes/backup before backup: 381 Gb.
Needed room in device /vmfs/volumes/backup for backup: 70 Gb.

VM Name    State    Size    Stop    Copy    Start    Time (min)    Speed (mb/s)
Sophos    ON    13G    NO (hot backup)    KO!    -    2    89
Last notice raised for the above VM:
[ Tue Jun 6 02:00:02 UTC 2017 ] ERROR CLDELSN3, details: [Sophos] error: cannot delete snapshot, details: Skipping invalid VM '6' Skipping invalid VM '6'

UCS    ON    22G    NO (hot backup)    KO!    -    3    110
Last notice raised for the above VM:
[ Tue Jun 6 02:00:02 UTC 2017 ] ERROR CLDELSN3, details: [UCS] error: cannot delete snapshot, details: Skipping invalid VM '6' Skipping invalid VM '6'

win10x64-desktop    ON    34G    NO (hot backup)    KO!    -    6    85
Last notice raised for the above VM:
[ Tue Jun 6 02:00:02 UTC 2017 ] ERROR CLDELSN3, details: [win10x64-desktop] error: cannot delete snapshot, details: Skipping invalid VM '6' Skipping invalid VM '6'

Available space in device /vmfs/volumes/backup after backup: 321 Gb.
Complete backup elapsed time: 13 min
The ESXi configuration was saved to /vmfs/volumes/backup/20170606020002

What does the copy status KO! mean?
What must I change to fix it?

Thanks

Frank

garyc

Member

Registered: 2017-06-05

Posts: 9

Re: XSIBACKUP errors detected

KO is just OK reversed meaning it didn't work.

Use the ESXi client and go into the Snapshot Manager for the relevant VM and delete any snapshots.  If you run the command again it should then work.

Daniel

Guest

Re: XSIBACKUP errors detected

Even though VMWare ESXi is probably the most stable virtualization hypervisor, the snapshotting subsystem is its most unstable part. How often you run into snapshots not being created or deleted kind of problems, will greatly depend on the type of OS you are running, your hardware and also and most important, how often you check the event viewer and consolidate your snapshot chains as requested by the ESXi system.

Also, install VMWare Tools in Windows systems and open-vm-tools in Linux OSs, use GPT instead of MBR and try to use well proven chipsets in your hardware, that will help minimize problems.

In regards to K.O., it's just an acronym that stands for "knocked out" in opposition to O.K. (zero killed).

Last edited by Daniel (2017-06-06 15:42:38)