2GB Split Problem - vdiskmanager do not obey

hi @ll,

we have a strange effect with an vmware virtual disk file in one of our vmwares.

but first the needed basic infos of the host and guest system:

host system:

vmware guest system:

windows 2008 server r2 enterprise 64bit
the vmware box was created and installed on the same host system
at the installation the vmware virtual disk was set to a size of 1tb as not preallocated hard disk stored in multiple files
this disk properties are also shown under the vmware hardware settings after installation

noticed problem

the guest system is up and running and full operational
we store about 150 gb on the guest system before we noticed at a box backup that we got only one big vmdk file
we tried to solve the problem with vmware-vdiskmanager -r sourceDisk.vmdk -t 1 targetDisk.vmdk but ended with the same result on the new targetdisk
we also noticed at that time that we needed 500gb more space at all so we expand the drive with
vmware-vdiskmanager -x 500GB sourceDisk.vmdk
at that moment the next strange thing happen because this time the vdiskmanager tool created new container 320kb files with the endings sourceDisk-s001.vmdk til sourceDisk-s252.vmdk
to solve this problem at all we tried it once again with the vdiskmanager. because we expect some false infos in the vmdk header we thought to solve it perhaps in two steps. first convert it back to an single growable file and than back to a not preallocated with multiple files, so we used
vmware-vdiskmanager -r sourceDisk.vmdk -t 0 dummyDisk.vmdk
vmware-vdiskmanager -r dummyDisk.vmdk -t 1 newSourceDisk.vmdk
but in the end the newSourceDisk.vmdk were once again one big single files but the vmware hardware setting for the hardware still speaks another language (not preallocated hard disk stored in multiple files)
perhaps someone have any clue how to fix this because its not funny at all to copy one big file over the network

thanks for any hints ... and a merry chrismas to all

greets

swavmware