VMware Cloud Community
tlyczko
Enthusiast
Enthusiast
Jump to solution

add storage to ESX 3.0.2 server before install ESX 3.5??

I have an HP DL380 server to which I want to add two more drives: 1 for more storage, 1 for a hot spare to its RAID 5 local storage.

This will fill up all the drives and bring the RAID 5 array from 4 drives to 6 drives.

It runs ESX 3.0.2 on its two RAID 1 local drives and stores the VMs on its RAID 5 local drives.

It is just one host-licensed ESX server.

I've learned that I need to boot the DL380 with an HP SmartStart CD, I have a 7.70 version that I used last year to initially set up the server's ACU.

So far what I've learned is that I have to reboot the ESX server with the SmartStart CD and run the ACU to add the storage, then reboot again, then go to my VI Client and re-scan the disks.

I don't want to install agents and stuff because sometime after the storage is added I'm doing a new clean install of ESX 3.5.

HP tells me that adding the storage etc. will be non-destructive, I'll back up anyway.

I'm asking for clarification that:

1) I have the proper procedure for adding the drives to the RAID 5 array

2) How do I rescan the new disks in the COS through the VI Client?? -- where in the VIC is this?? I know all the VMs have to be shut down.

3) Or am I better off recreating the VMFS completely through a clean ESX install?? The current VMs are all ESX 3.0.2 version, would they all carry over??

Thank you, Tom

0 Kudos
1 Solution

Accepted Solutions
Texiwill
Leadership
Leadership
Jump to solution

Hello,

HP tells me that adding the storage etc. will be non-destructive, I'll back up anyway.

This is correct, but you will not be able to access that space within the existing VMFS.

I'm asking for clarification that:

1) I have the proper procedure for adding the drives to the RAID 5 array

Yes.

2) How do I rescan the new disks in the COS through the VI Client?? -- where in the VIC is this?? I know all the VMs have to be shut down.

No need to do so.

3) Or am I better off recreating the VMFS completely through a clean ESX install?? The current VMs are all ESX 3.0.2 version, would they all carry over??

If you want to extend the VMFS, then yes you should recreate the VMFS as there is no way to do this. And VMs would not carry over if you recreated.

If you want another VMFS, this is possible by just adding a new VMFS which will use the remaining space. Most likely you have to create a new partition on the LUN to use this space. TO do this, you need to be comfortable with fdisk and adding a new partition using up the remaining space.

If you want to extend using 'Extents' do the same as the above but Add an extent and not a VMFS. But first you need to add a new partition using fdisk from the command line.

Either way I would back up all your VMs.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354, As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill

View solution in original post

0 Kudos
3 Replies
Texiwill
Leadership
Leadership
Jump to solution

Hello,

HP tells me that adding the storage etc. will be non-destructive, I'll back up anyway.

This is correct, but you will not be able to access that space within the existing VMFS.

I'm asking for clarification that:

1) I have the proper procedure for adding the drives to the RAID 5 array

Yes.

2) How do I rescan the new disks in the COS through the VI Client?? -- where in the VIC is this?? I know all the VMs have to be shut down.

No need to do so.

3) Or am I better off recreating the VMFS completely through a clean ESX install?? The current VMs are all ESX 3.0.2 version, would they all carry over??

If you want to extend the VMFS, then yes you should recreate the VMFS as there is no way to do this. And VMs would not carry over if you recreated.

If you want another VMFS, this is possible by just adding a new VMFS which will use the remaining space. Most likely you have to create a new partition on the LUN to use this space. TO do this, you need to be comfortable with fdisk and adding a new partition using up the remaining space.

If you want to extend using 'Extents' do the same as the above but Add an extent and not a VMFS. But first you need to add a new partition using fdisk from the command line.

Either way I would back up all your VMs.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354, As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
tlyczko
Enthusiast
Enthusiast
Jump to solution

Hi again,

I'm adding this information to this thread, which references your suggestion about using Converter as a QED way to backup and restore the VMs after recreating the array and a new VMFS.

http://communities.vmware.com/message/948325 and http://communities.vmware.com/message/904960

Just for clarification:

1. I don't have to re-install ESX to create the new VMFS??

2, It doesn't make any difference where Converter stores the files so long as they are never opened by Workstation??

I don't have enough local storage for all of them so I was thinking of using NAS storage.

Thank you, Tom

0 Kudos
Texiwill
Leadership
Leadership
Jump to solution

Hello,

1. I don't have to re-install ESX to create the new VMFS??

No.

2, It doesn't make any difference where Converter stores the files so long as they are never opened by Workstation??

I don't have enough local storage for all of them so I was thinking of using NAS storage.

The only place to avoid is the ESX server you are updating. Other than you are correct just somewhere else your machine running VMware COnverter can see.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354, As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos