After vMotioning VM's back and forth from westwood to northvale to make sure the configuration is bullet proof, I moved my vCenter Server VM over from westwood to cresskill (utility host) and put vCenter's files in the shared storage on NFS via the utility VM (lets call this VM Uber, the Ubuntu build).
In my testing haste, I did shutdown Uber while vCenter had its files on shared storage! After realizing this, I powered Uber back up. While vCenter's Win2k3 event logs showed the missing disk, the server came back alive.
I am now thinking it is better to use the local cresskill host datastore such that I can shut down Uber while I am still logged into vCenter. I just activated Storage vMotion to move vCenter's files. The down side is of course single point of failure (will resolve this next week).
I am getting yellow and red warnings on Uber about high CPU and memory usage. This is partially being caused by the migration vCenter's files to local storage on cresskill. Also, various Cluster VM's continue to read & write to Uber's shared storage.
Uber currently has 1.5 GB of virtual memory. I will push it to 2.5 GB shortly. This Ubuntu VM will be a memory and network workhorse going forward since I plan to put the files from most VM's on it.
I brought up my legacy XP utility machine to do some data backups onto its 1 TB Raid 1 array. Tomorrow, DRS testing and building a few more VM's, including x64 builds. Next week, make vCenter Server Fault Tolerant. Once done, consider making Uber FT.
No comments:
Post a Comment