Here's our issue. We have two servers.
Server A (Named CLOUD1)
ESXi 5.5 U2 (HP Build)
P400 Array Controller, 256MB BBWC
We have Array controller caching set to 25% / 75% ratio, we also have disk caching enabled.
8 SATA III disks in a RAID1+0 array.
Each VM on this server runs in it's own store which is made up of 1 pair of disk (as per RAID arrangement above).
All was well with this server until we lost a disk in one of the pairs (STORE1) (since replaced disk and synced in the RAID). We moved the VM to another store (STORE2 \ another pair), we had an additional crash the following evening (ESX froze) so decided as this is a production VM best to move it to our secondary ESX server. We are concerned about moving the VM back to SERVER A until we know it is stable.
What we did:
Shut the VM down, copied the files to the backup VM server (which is the spec below). Powered on the VM but it is running extremely slow, the VM is Windows SBS 2011 and it took over an hour to boot to the Windows login, interactive with the VM from there on in is still very very slow. We have the client's OWA access to this box up but again access to that is very slow. We've granted the VM 8GB of RAM and 1*4 vCPU.
Backup VM Server Hardware:
Server B (COLOMG01)
ESXi 5.5 (not Update 2 as per Server A).
RAID5 (yes I know we should really not have R5, it's on the list of tasks to do)
Any other VM's on this box run fine.
Now for the big question:
On the backup VM server this VM is now running we have in vSphere a message stating "virtual machine disk consolidation is needed".
As this is an Exchange (well SBS 2011) box I'm concerned if I do the "consolidation" option under Snap Shot Manager that it will revert back to some old version of the VM or version of the virtual hard disk which wont contain their current Exchange database and respective email data. I'll attach a screenshot of the vhd's we can see for this VM once I can get onto the box (should be in the next hour). My other concern is with the speed that it's currently running at I dont want to kick off the consolidation and it take the machine offline (due to high disk activity) for days as it's barely accessible now through OWA with a lot of lag and time outs.
One thing that concerns me is that the VM has moved from a new version of ESX. Do we need to do "upgrade virtual hardware"? I've had bad experiences of VM's not booting after doing that. We're currently installing VMWare Tools onto the VM to see if that helps with the operating speed but my understanding is that is more for graphical interfacing with the VM, no?
Really stuck here and I'm due to travel tomorrow so I'm hoping some of you ESX \ VMWare guru's can get us out of this mess.