Extending VMWARE VMFS datastore

We have a VMWARE ESX Server 3.5 up and running.
Because of budget restrictions we only have local SAS harddisks.
The SAS harddisks are configured  as one RAID5 array.
We now extended the RAID5 array by adding two more physical disks.

Now we also would like to extend the VMFS datastore.
When I choose "Add/Extend" I get the following warning:
"The current disk layout will be destroyed. All file systems and data will be lost permanently." (see screenshot attached)

Before I proceed I would like to answer the following question:
- Will all our VMDK virtual machine images be destroyed?
- Isn't it possible to just extend the datastore without loosing all data?
- What is the fastest way to backup all our VMDKs? (if required)
- Any other thougts an this issue?

One more annotation: The ESX server itself is installed on another RAID1 volume.
This means, that the RAID5 voulme is "only" used for VMDKs.

Thanks for your advise!
Volker :-)

Who is Participating?
larstrConnect With a Mentor Commented:
I'm sorry, but you can't extend a VMFS datastore just like that. You can add several extents to a datastore, but it's not really something I would recommend.

The best solution would be to build a new datastore of the required size and move your VMs over there. For a standalone server with local storage setup that might mean that you must backup your VMs and restore them again.

Note also that RAID 1 or RAID 1+0 is normally better for hosting VMs than RAID5 since it will give you much better performance for a mixed workload.

The easiest way to backup/restore your VMs is probably to use esxpress or similar.

kurthvAuthor Commented:
This would mean, if I click on "Next", then all data would be destroyed, right?
> This would mean, if I click on "Next", then all data would be destroyed, right?

That's correct.
kurthvAuthor Commented:
Hi Lars,

I did backup all the VMDKs (using esXpress).
Then I performed the "Add/Extend" operation.
I was expecting to loose all my VMDKs, but they are still there.
See the attached screenshot...

So the warning message was wrong!

Best regards,
Volker :-)

Are you adding an extent now? If you do that, beware of the limitations. Also see: http://www.vmware.com/pdf/vmfs-best-practices-wp.pdf
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.