Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

Pas98

Member

Registered: 2020-05-14

Posts: 13

CLVMKFS1 error: Failed to clone disk: File too large (1769481)(SOLVED)

I have XSIBackup FREE installed on an ESXi 6.5 System. Now i want take a backup to a NAS Storage. In the NAS Storage, there is a 4 TB HDD with 3.4 TB available space. The virtual disk from the VM has a space from 25 GB.
When i start the Backup, it says:

Could not get available backup room in backup datastore
Needed room: 0 Gb.
Sparse size: 0 Gb.
Available room: 0 Gb.

At the end of the backup it says:

[VS001] CLVMKFS1 error: Failed to clone disk: File too large (1769481).

Can anyone help me to solve this problem?

LG
Pascal

Last edited by Pas98 (2020-05-19 12:08:11)

admin

Administrator

Registered: 2017-04-21

Posts: 2,055

Re: CLVMKFS1 error: Failed to clone disk: File too large (1769481)(SOLVED)

Maybe that disk was created with an older version of ESXi and has not yet been cloned to a more recent format?
It could also be corrupt. Clone it manually using vmkfstools and reattach it to the VM.

vmkfstools -i olddisk.vmdk newdisk.vmdk -d thin

Pas98

Member

Registered: 2020-05-14

Posts: 13

Re: CLVMKFS1 error: Failed to clone disk: File too large (1769481)(SOLVED)

OK thanks for the help.
I think I found the problem.
The problem with the error:

[VS001] CLVMKFS1 error: Failed to clone disk: File too large (1769481).

was that the host server allowed incoming communication with SSH but not outgoing.
With the problem with the error:

Could not get available backup room in backup datastore
Needed room: 0 Gb.
Sparse size: 0 Gb.
Available room: 0 Gb.

was that I put a "/" in front of the backup point, so:

backup-point=/ip:port:/path/to/backup

correct would be:

backup-point=ip:port:/path/to/backup

Thanks 4 ur help.

Last edited by Pas98 (2020-05-18 09:09:02)

admin

Administrator

Registered: 2017-04-21

Posts: 2,055

Re: CLVMKFS1 error: Failed to clone disk: File too large (1769481)(SOLVED)

That explains it all.
Please post your jobs and relevant data: .vmx file, file listings, otherwise we are just guessing.