Friday, June 6, 2014

Resizing Partition with Bad Sectors in GParted

Recently I tried to expand a Windows 2003 system drive on a VM using GParted but was not able to as it kept complaining about bad sectors. The recommended fix was to run chkdsk /f /r on Windows and then reboot it twice. After applying the recommended fix and rebooting back into Gparted, the error remains and I was unable to proceed with expanding the drive. Luckily, we are able to override the bad-sectors error and proceed with the drive expansion.


Solution:

  1. While booted into the GParted X environment, open the terminal window.
  2. Navigate to /sbin: cd /sbin 
  3. Rename ntfsresize: sudo mv ntfsresize ntfsresize.orig
  4. Create new ntfsresize: sudo touch ntfsresize
  5. Edit ntfsresize with vi: sudo vi ntfsresize
  6. Add the following lines into ntfsresize and save the file:
    1. #!/bin/bash
    2. exec ntfsresize.orig --bad-sectors “$@”   (Note the double "-" before bad-sectors)
  7. Add permissions to run the resize: sudo chmod 777 ntfsresize
  8. Go back into the GParted wizard and expand the disk as you normally would

Thursday, May 1, 2014

Backing up VMs with vRDM using Veeam over FC Network

With the release of vSphere 5.5, the size limitation for a virtual RDM has been increased substantially to a limit of 62TB. In my opinion, this makes the use of physical RDMs redundant unless they are needed for some type of Microsoft Clustering or bus sharing. One of the advantages of vRDM is that it can be snapshotted which translates to being able to be backed up via Veeam.

In order to backup a vRDM over the fiber channel network (SAN Mode) with Veeam, the following is required:
  1. Zone and present the vRDM LUN to both the ESXi cluster and the Veeam Backup Proxy 
  2. Zone and present the VMFS LUN where the VM's VMDK and vRDM pointer files are stored to both the ESXi cluster and the Veeam Backup Proxy

Thursday, April 17, 2014

Upgrading vCenter from 5.1 to 5.5 with Multisite SSO and Linked Mode

A month ago, I upgraded our vSphere environment was from 5.1 to 5.5. This post documents the steps required to upgrade a linked mode vCenter environment with multisite SSO from 5.1 to 5.5.

Here's a summary of the environment I was working with (original configuration blog is found here):
  • 2 vCenter Servers in 2 different geographical locations
  • each vCenter Server has it's own instance of SSO in a multisite configuration
  • all the components of vCenter Server are installed on one server 
  • linked mode is configured

As with any upgrade process, take backups before you start. In this case here, it is important to snapshot/backup both vCenter servers as they have dependencies with each other.

While there are probably many different ways to upgrade the vSphere environment, this method was what worked for me. The overall steps can be summarized as:

  1. Break vCenter Linked Mode
  2. Clean up Application Users registered with SSO
  3. Upgrade SSO
  4. Upgrade Web Client
  5. Upgrade Inventory Services
  6. Upgrade vCenter Server
  7. Upgrade Update Manager
  8. Upgrade Second vCenter Server
  9. Rejoin vCenter Linked Mode

1. Break vCenter Linked Mode

Log in to one of the vCenters and open up the Linked Mode configuration installer.


Proceed through the installer and isolate the vCenter Server from the linked mode group (essentially destroying the linked mode group if you only have 2 vCenter Servers).








If you have more than 2 vCenters, I assume you will have to repeat this for all the vCenter Servers.


2. Clean up Application Group users in SSO

Connect to the web client and login using any account that has access to make SSO configuration changes. I used the default admin@system-domain account which was created in the default 5.1 installer.


Once logged in, navigate to the SSO Users and Groups > Application Users section.

 
Remove any Application Users entries that are not associated with this vCenter. If you are unsure which ones belong to this vCenter, you can always make a clone of the vCenter and uninstall components to see which ones get removed.



3. Upgrade SSO

At this point, you'll want to stop all the VMware related services. One additional task that you may want to do is to change the autogrowth options for the vCenter log database as explained here.




Once that is done, launch the vSphere 5.5 Installer and select Custom Install > vCenter Single Sign On to upgrade SSO.


Proceed through the setup, selecting the defaults. You may get a warning regarding not being able to contact the SSO services in order to confirm the certificates. Accept the default to continue past that.





Select first existing "vCenter Single-Sign On server".


Set the default administrator@vsphere.local password. Make sure to note this down for future references.







4. Upgrade Web Client

Launch the custom install for the Web Client and proceed through the set up. Everything should be default and self explanatory.




 



5. Upgrade Inventory Services

Similar to the upgrade procedure for the web client, launch the custom installer for Inventory Services and proceed with the installation selecting all the defaults.












6. Upgrade vCenter Server

Next, upgrade vCenter Server. Run the custom installer and proceed with the installation.




Upgrade the existing vCenter Server database.


Upgrade all the hosts automatically.


I chose to use the Windows Local System account, you may want to put in your service account credentials. Proceed with the remainder of the setup choosing the defaults.









7. Upgrade Update Manager

Launch the installer for the update manager and proceed with the installation selecting all the defaults.





Enter the credentials for your VUM database.






Restart the vCenter Server and then proceed to the next step of upgrading the second (or more) vCenter Servers.


8. Upgrade second vCenter Server

Once the first vCenter Server has been restarted, repeat steps 2-7 for the secondary vCenter Server. During the installation of SSO, select "An additional existing vCenter Single-Sign On Server in a new site". Enter the required information, pointing it to the first vCenter.


9. Rejoin vCenter Linked Mode

Once the second vCenter Server has been upgraded and restarted, run the Linked Mode Configuration installer and join the vCenters together.


This concludes the vCenter Server 5.1 to 5.5 upgrade.