Hi William,
sorry to come back on this but there is definitely something going wrong.
Every weekly the script gives a different output for one of my VM's (sol10).
There are the 2 vmdk's: sol10.vmdk and sol10_1.vmdk.
One week it takes hours to back-up sol10.vmdk and 0 minutes to backup sol10_1.vmdk
Another week it takes 0 minutes to back-up sol10.vmdk and hours to backup sol10_1.vmdk
Yet another week it takes hours to back-up sol10.vmdk and hours to backup sol10_1.vmdk. This I would consider normal.
This week it took 0 minutes to back-up sol10.vmdk and and 0 minutes to backup sol10_1.vmdk
In all cases there is no error indication in the log/
Taking a closer look at this weeks situaton, when I look at the datastore of the sol10 machine, the backup datastore and the filesystem inside the VM:
1) the datastore browser indicates:
[datastore3] sol10
- sol10.vmdk: Virtual Disk 268.435.500
- sol10_1.vmdk:Virtual Disk 268.435.500
2) the backup goes to a datastore mounted via NFS but in dicates a much smaller size:
[VM-Backups] VMWARE_BACKUPS/sol10/sol10-2013-02-22--1
- sol10.vmdk: Virtual Disk 80.512,00 KB
- sol10_1.vmdk:Virtual Disk 2.816,00 KB
3) Doing inside the VM a df -kh, I get a view on the acual sizes and usage:
/dev/dsk/c1t0d0s7 191G 152G 38G 81% /export/home
/dev/dsk/c1t1d0s2 246G 47G 197G 20% /mnt/data1
So in any case the fileystem uses 152 G and the second uses 47 G, but the backup shows only 80 G and 2,3 G respectively.
I have another VM with 2 filesystems and observe similar strange behaviour.
The backups for VM's with 1 filesystem seem to be OK.
What could be the problem?
Greetings,
Johnny