Completing HA Failover

Searching Sun xVM Ops Center 2.1

home Home
Sun xVM Information Exchange
Read Me First
Contact the Wiki Administrators


What's Going On

Get Going

Keep Going

Reference Material

Printable Quick Start Guides

Printable Versions

Previous Releases

Index


back"alt="back High Availability Support


Completing HA Failover

After the storage asset that holds the /var/opt/sun/xvm directory structure has been transferred to the secondary Enterprise Controller, you must run the harestore program, reboot the secondary Enterprise Controller, and start Sun xVM Ops Center services.

After you complete the HA failover procedure, the secondary Enterprise Controller is listed in the Gear panel as controller_0, where controller is the host name of the primary Enterprise Controller.

Caution – The following example procedures are based on the example Solaris OS-based storage solution that is described in Configuring Storage for High Availability. You must determine what specific procedures to use, depending on the storage solution that you have implemented.

To Run the harestore Program

Run the harestore program to restore Sun xVM Ops Center configuration from the primary Enterprise Controller onto the secondary Enterprise Controller.
The harestore program is located in the /opt/sun/xvm/bin/ directory. For example:

# /opt/sun/xvm/bin/harestore
./osp/clientPkgs/Sun_Microsystems,_Inc.-allstart-3.3-1/base-mgmt-allstart-1.0-15.noarch.rpm:  No mapping for uid 63333
Restore complete.  You need to reboot now.
# 

To Reboot the Secondary Enterprise Controller and Start Services

After you run the harestore program, you must reboot the secondary Enterprise Controller and start Sun xVM Ops Center services on that system.

  1. Reboot the operating system on the secondary Enterprise Controller.
    For example, on Solaris systems, you can use the init 6 command to reboot the system:
    # init 6
    
  2. Use the satadm command to start Sun xVM Ops Center Enterprise Controller services.
    • Solaris OS: Use the /opt/SUNWxvmoc/bin/satadm command.
    • RHEL OS: Use the /opt/sun/xvmoc/bin/satadm command.
      For example:
      # /opt/SUNWxvmoc/bin/satadm start -w
      satadm: Starting satellite with SMF...
      satadm: Satellite services have started
      #
      
  3. If the configuration from the primary Enterprise Controler included an enabled co-located Proxy Controller, use the proxyadm command to start Sun xVM Ops Center Proxy Controller services.
    • Solaris OS: Use the /opt/SUNWxvmoc/bin/proxyadm command.
    • RHEL OS: Use the /opt/sun/xvmoc/bin/proxyadm command.
      For example:
      # /opt/SUNWxvmoc/bin/proxyadm start -w
      proxyadm: Starting proxy with SMF...
      proxyadm: Proxy services have started
      #
      

Where to Go From Here
Return to High Availability Support or to Installation to choose another subject.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact