Hi,
We have an issue with our Exchange server.
The D drive resides on a Datastore with a 2MB block size.
Last week the D drive of the Exchange server was extended from 400GB to a maximum size of 512GB. Disk part used to then extedn the volume in Windows.
Veeam backups are failing as the snapshot can not be created on the 2MB block size Datastore.
I have found this: and it seems the overhead was over looked?
http://www.veeam.com/kb_articles.html/KB1091/Backup_Replication:1/file%20is%20larger
Two options i can see are:
1: You may want to move the machine to storage with a bigger block size.
2: You may want to edit the VMX file, so that snapshots will be created on a different datastore that has a bigger block size. Refer to the knowledge base link below for further details:
Any recommended way for me to move forward on this..?
I was thinking option 1, however un sure if i will be able to move the VMDK as snapshot files already exisit on the datastore..
Thanks in advance.
I would commit the snapshots and move the VMDK to a larger datastore.
Hi,
thanks, was not sure if i can commit the snapshots..? is this 100% safe todo with the curent disk layout (512GB on 2MB Block Size)
also we not had a backup of this server for near 4 days, and am little worrres about some thign failing during the migration process?
I would check with VMware Support but I am pretty sure you should be able to commit the snapshots as your VMDK will not be going over 512GB. That is if I am understanding your issue.
what is the largest vmdk file size for datastore with a block size of 2MB?
Is it 512GB - 512 Bytes?
Thanks
Check out this KB Article: http://kb.vmware.com/kb/1003565
That article lists all of the maximums for VMFS.
... however un sure if i will be able to move the VMDK as snapshot files already exisit on the datastore
I'm a little bit confused. How could there be snapshots for this virtual disk!? Can you please explain this and/or post a screen shot of the datastore browser window showing the vmdk files and their sizes, time stamps, ...
André
what is the largest vmdk file size for datastore with a block size of 2MB?
Is it 512GB - 512 Bytes?
Depends on the ESXi version. For 4.0 it's 512GB-512B, for 4.1 it's 512GB. However if you need to be able to take snapshots, the table at the bottom of http://kb.vmware.com/kb/1012384 (Calculating the overhead required by snapshot files) is what is important.
André
Action Plan:
Any thoughts?
Hi Screen shot attached
Does not sound bad. Maybe some thoughts.
André
Hi,
I have checked the disks from the properties of the VM - and the disk names are corect:
Snapshot Manager does not have any snap shots listed under it.
The VMX and VMSD Files are attached - can you please let me know asap as i am due to carry out this work in a few hours. (6) (thanks for the help)
Also noted to move the entire VM rather then just the 512GB VMDK File.
If the files are orphansed, can i leave them and just migrate?
As far as I can see, everything is ok with the two files and the .vmsn files are most likely orphaned. Anyway, since you are going to migrate the VM to the other datastore, any unneeded files usually remain in the old datastore and can be deleted once the VM is up and running from the 4MB datastore.
If you are unsure, post a list of the remaining files once the VM has been moved and/or rename the VM's folder on the "old" datastore prior to deleting the files. This way you would be able to restore them if needed (what I don't expect).
André
so no need to create a snapshot and commit? or shall i do this anyway?
It does not hurt to if you do this. However, since there are no snapshots on the VM it does not make much sense in my opinion.
André