![]() I also get the same behavior on my other 2003 Server VM. ![]() Is not exported NFS and has no thin backups on it, and is not compressed. ![]() This behavior is consistent for the system drive as well, which However, if I repeat the process, I will get the same errors on the same files no matter how many times I do it. If I run chkdsk /f, and reboot, it finds and fixes errors. If I run chkdsk, no switches, from within Windows (read only), it shows no errors.Ĥ. In vmkfstools is that there is not enough disk space, even when there is almost a terabyte free.ģ. When I run into the problem, no matter how many backups I erase, and no matter how much free space the NFS volumes shows I have, I can no longer backup the VMs. ![]() It will get to 90%+ complete before it fails.Ģ. (80 declared, 55 GB thin) I have other declared at 80 also, but they are much smaller from a thin standpoint. This VM is because it's larger than the rest all put together. I'm assuming the reason the problem is with The error from vmkfstools is that it is out of disk space, even though it shows it has almost a terabyte of free space. After so many cycles, the same, and largest VM, will not backup anymore. Oldest backups, so there is no reason for the volume to run out of space, and indeed both Windows and ESXi agree on the amount of free space, and that there are many times what is required for the backup even if the backups were not thin. ![]() Seems like I must be missing something in the SCP command.I use GhettoVCB latest to do thin clone backups to a Windows 2003 Server compressed volume, projecting the volume as an NFS share. I tried scp /vmfs/volumes/datastore/VMNAME/VMNAME.vmdk it copes something, but it's a tiny destination file, not the actual 128GB VHD. REALLY wishing I had copied the successful command to a reference document last week. I THOUGHT this was the proper command, after CD to the source folder vmkfstools -i /vmfs/volumes/datastore/VMNAME/VMNAME.vmdk also tried it with a single forward slash after the IP, which I have also seen when searching, so vmkfstools -i /vmfs/volumes/datastore/VMNAME/VMNAME.vmdk both cases I get Failed to clone disk: The destination file system does not support large files (12) which my searching suggests is a bit of a misnomer, actually indicating I am getting my arguments wrong. I have to use IP address for the destination as for some reason DNS isn't getting the HostName of these hosts, even though they are using DHCP to get an IP address and all the Windows clients do the same and manage to update DNS. I am trying to clone a VHD between hosts, and somehow I can't recreate something I did last week. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |