Move the VirtualCenter SQL database or migrate the VirtualCenter SQL database to different server.

VMware released two new handy KB articles about how to move or migrating  the SQL VirtualCenter database to different server.

To move the database

When relocating your SQL database:

  1. To move SQL Server databases to a new location by using Detach and Attach functions in SQL Server, see Microsoft KB article http://support.microsoft.com/kb/224071/en-us
  2. If you are using the Copy Database Wizard in SQL Server 2000 see, Microsoft KB article http://support.microsoft.com/kb/274463
  3. Update the Datasource (DSN) in the OBDC Administrator to reflect any changes made.
  4. If either the database login or password changed during the relocation, VirtualCenter must be updated to with the new credentials. For more information, see the Modifying the username and password VirtualCenter uses to connect to the database server section of Troubleshooting the database data source used by VirtualCenter Server (1003928).

Read the KB article here.

Migrate the database to a new server:

 
  1. Shutdown the VirtualCenter Server service. For more information, see Stopping, starting, or restarting the VirtualCenter Server service (1003895).
  2. Take a backup of the SQL database.
  3. If the SQL database is also being moved, create a second instance of your database and use the vendor’s tools to migrate the data.Note: For SQL Server, use Microsoft’s Copy Database Wizard. For more information, see http://support.microsoft.com/?kbid=274463

    .

     

     

     

  4. Create the appropriate System DSN connections on the new VirtualCenter Server host.
  5. Begin the installation of the VirtualCenter software on the new server. If you are installing VirtualCenter in a virtual machine, guidelines for deploying VirtualCenter in a virtual machine, including sizing, installation, functionality, and configuration of VMware HA can be found at http://www.vmware.com/vmtn/resources/798.
  6. When prompted, select Use existing database, and provide the correct credentials to that database.
  7. When prompted, select to not re-initialize the data, as this erases all your inventory data.
  8. Reboot the virtual machine when the installation is finished.
  9. When you first start the VirtualCenter Client, it may ask for licenses. Configure the licenses as you had previously in your environment. For more information about licensing for ESX Server 3 hosts, see the Installation Guide. For more information about licensing for ESX Server 3i hosts, see the Setup Guide. You are now able to see the same settings and configuration details.Note: If the IP address of the new VirtualCenter Server has changed your ESX Servers must be made aware of that change, otherwise the ESX Servers continue to send their heartbeats to the original IP address of VirtualCenter and appear as Not Responding.To correct this situation:

     

     

    1. Log in as root with an SSH client to each ESX host.
    2. Use a text editor to change the IP address inside the <serverIp>xxx.xxx.xxx.xxx</serverIp> tags the following file:/etc/opt/vmware/vpxa/vpxa.cfg (VirtualCenter 2.5.x)
      /etc/vmware/vpxa.cfg (VirtualCenter 2.0.x). 

       

    3. Save your changes and exit.
    4. Restart the management agents. For more information, see Restarting the Management agents on an ESX Server (1003490).
    5. Repeat for all ESX hosts connected to the VirtualCenter Server.

 

Read the KB article here.

[ad#verticaal]

Offline Virtual Machine Servicing tool 2.0 released

The Offline Virtual Machine Servicing Tool 2.0 helps organizations maintain virtual machines that are stored offline in a Microsoft® System Center Virtual Machine Manager library. While stored, virtual machines do not receive operating system updates. The tool provides a way to keep offline virtual machines up-to-date so that bringing a virtual machine online does not introduce vulnerabilities into the organization’s IT infrastructure.

The Offline Virtual Machine Servicing Tool combines the Windows Workflow programming model with the Windows PowerShell™ interface to bring groups of virtual machines online just long enough for them to receive updates from either System Center Configuration Manager 2007 or Windows Server Update Services. As soon as the virtual machines are up-to-date, the tool returns them to the offline state in the Virtual Machine Manager library.

This Solution Accelerator includes the following components:

  • Brief Overview. Available online only on Microsoft TechNet. Summary for business and technical managers that briefly explains how this Solution Accelerator can fit into an organization’s IT infrastructure management strategy.
  • OfflineVMServicing_x64 and OfflineVMServicing_x86. Setup files for the tool, for 64 bit and 32 bit versions on Microsoft® System Center Virtual Machine Manager (VMM) 2007 or 2008.
  • Offline Virtual Machine Servicing Tool Getting Started Guide. Provides information about how the tool works, explains prerequisites for the tool, and describes how to install and configure the tool.
  • Offline_VM_Servicing_Tool_2.0_Release_Notes.rtf. Notes provide information about this release, describe known issues in the tool, and include feedback instructions.
  • Offline_Virtual_Machine_Servicing_Tool_Help. Help file for the tool. Provides instructions for using the tool.

Download the tool @

http://www.microsoft.com/downloads/details.aspx?FamilyId=8408ECF5-7AFE-47EC-A697-EB433027DF73&displaylang=en

VMware ESX 3.5 Update 3 VM’s spontaneously reboot.

A week ago i upgraded a customers environment to VMware ESX 3.5 Update 3 and VC 2.5 Update 3. After the upgrade some Virtual Machines (VM) spontaneously rebooted. After investing the problem we saw that after a VMotion action the spontaneously reboot occurred.

We disabled in HA the option “Virtual Machine Monitoring” and set DRS to manual.  The problem with Virtual Machine monitoring is:

The Virtual Machine heartbeats are being dropped which is triggered by Vmotion and the VM gets reset by the HA feature as it thinks it has gone offline. Since the feature is now off it should be safe to turn on DRS again.

 

There are more people who have this problem, read the following post on the VMware forum, 3.5U3 – any guinea pigs yet?.

I made a support request @ VMware. The told me today that 20 November patch 10 for VMware 3.5 Update 3 will be released. Patch 10 fixes SOME random reboot problems in Update 3. I hope it resolves this nasty issue.