Thursday, March 8, 2012

snapvault

Struggled with snapvault this week. First, we were missing some datastores in one of the snapvault jobs, then the snapvault copies on another datastore disappeared.

When snapvault works, it is great. But when it does not, it is a pain. If a datastore should be getting snapvaulted, but is not, the only way to know this is to be aware which datastores are suppossed to get snapvaulted and verify the snapshots on either the promary or secondary. It is very easy to create a new datastore, and then forget to add it to the snapvault job.

I have a script that checks for snapshots, but I need to remember to add new datastores to the script. Time to review my scripts!

Passed!


Passed the VCP5 exam on 2/28/12... This was relatively easy compared to the VCAP, which I am scheduled to re-take in a couple weeks.


4.1 Upgrade postmoderm

Upgraded our vDS switches to 4.1 and enabled Network I/O.  Thi was very easy to do and had no surprises. The only thing left to do is to finish upgrading vmware tools, and  one cluster still needs to be upgraded. Two clusters have older servers and will not get upgraded to 4.1.

Once again, after switching the vCenter Server database to SQL, everything went very smooth. There were just a couple gotchas along the way. One was with 4.1U1, we were unable to edit the settings in a template without removing it from inventory first. Upgrading vCenter Server to 4.1 U2 foxed this. The other issue was the historical perfromance data quit working a couple times. We fixed that by re-creating the view tables in the database.

I almost do not want to upgrade to vSphere 5, now that 4.1 is working so well. But we will probably do that prior to migrating our ERP physical servers to Vms which should happen in the fall.