Oracle® Enterprise Manager Ops Center

Restore an Enterprise Controller and Embedded Database on a New System

12c Release 3 (12.3.1.0.0)

E60373-02

December, 2015

You can restore an Enterprise Controller with an embedded database on a new system.

This guide provides an end-to-end example for how to use Oracle Enterprise Manager Ops Center.

This document includes the following sections:

Introduction to Recovery

You can restore an Enterprise Controller with an embedded database on a new system using a backup file.

The ecadm backup and ecadm restore commands enable you to create a backup file that stores the current state of the Enterprise Controller and restore the Enterprise Controller from that backup file. If the original Enterprise Controller system has failed, you can restore on a new system.

As part of restoring an Enterprise Controller, you will complete the following tasks:

  • Backing Up the Enterprise Controller: You must regularly back up the Enterprise Controller to create a backup file to use in restoration.

  • About Preparing a New System: Verify that the new system is supported and install Ops Center.

  • Restoring the Enterprise Controller: Use the backup file to restore the Enterprise Controller's configuration.

What You Will Need

You will need the following:

  • A configured Enterprise Controller with an embedded database

  • Access to the Enterprise Controller system

  • A user with the Ops Center Admin role

Backing Up the Enterprise Controller

You can create a backup for the Enterprise Controller using the ecadm command with the backup subcommand.

The backup file includes the product schema from the embedded database. This database schema includes all logical structures and data related to Oracle Enterprise Manager Ops Center.

  1. From the command line, log in to the Enterprise Controller system.
  2. Use the ecadm command with the backup subcommand to back up the Enterprise Controller. This command is in the /opt/SUNWxvmoc/bin/ on Oracle Solaris systems and in the /opt/sun/xvmoc/bin/ directory on Linux systems.

    For example:

    # ./ecadm backup
    ecadm: using logFile = /var/opt/sun/xvm/logs/sat-backup-2014-12-15-10:43:03.log
    ecadm: *** PreBackup Phase
    ecadm: *** Backup Phase
    ecadm: *** PostBackup Phase
    ecadm: *** Backup complete
    ecadm: *** Output in /var/tmp/sat-backup-2014-12-15-10:43:03.tar
    ecadm: *** Log in /var/opt/sun/xvm/logs/sat-backup-2014-12-15-10:43:03.log
    
  3. Copy the backup file to a separate system.

About Preparing a New System

Before restoring the Enterprise Controller on a new system, you must verify that the new system is compatible.

To check if the new system is compatible:

  • The new system must have the same architecture and operating system as the old system. It is recommended that the operating system versions be identical, including updates and SRUs.

  • The host name of the new system should be the same as the old system. You can change the host name of the new system, provided the old host name is added as an alias host name in the new system.

  • The IP address of the new system can be different. If the new system has a different IP address, the restore process includes a step to configure any remote Proxy Controllers to use the new Enterprise Controller IP address. The MAC address of the new system can be different.

  • The new system's Enterprise Controller software version must also match that of the backed up system.

For a regular backup and restore procedure, the IP address and the host name of the new system should match that of the old system. For a disaster recovery procedure, the IP address and the host name of the new system can be different than that of the old system.

Use the following procedure to ensure that the correct version of Oracle Enterprise Manager Ops Center is installed on the new system.

Preparing a New System

You can restore the Enterprise Controller on a new system.

To prepare a new system for back up, install the Enterprise Controller to the same version that was running when the backup was made, but do not configure the Enterprise Controller, as the ecadm restore command restores your configuration settings.

Restoring the Enterprise Controller

You can use a backup file to restore the state of the Enterprise Controller to the state it had at the time of the backup.

This procedure describes the steps for disaster recovery. It also defines the procedure to change the host name and the IP address of an Enterprise Controller. This procedure restores the data from the backup file, which is the archive created by the ecadm backup operation. The restore process restores the product schema from the embedded database.

  1. Copy the backup file to the new system.

  2. Check if the new host name of the system matches the old host name. If the host name does not match, add the old host name as an alias to /etc/hosts.

  3. Run the ecadm command with the restore subcommand and the -i <backup directory location and file name> option.

    For example:

    ecadm restore -i /var/backup/EC-17December.tar
    ecadm: using logFile = /var/opt/sun/xvm/logs/sat-restore-2014-12-17-21:37:22.log
    ecadm: *** PreRestore Phase
    ecadm: *** Restore Phase
    ecadm: *** PostRestore Phase
    ecadm: *** Log in /var/opt/sun/xvm/logs/sat-restore-2014-12-17-21:37:22.log
    
  4. For an Enterprise Controller with an enabled co-located Proxy Controller, the restore should restore and start the co-located Proxy Controller. The co-located Proxy Controller starts only if the Proxy Controller was enabled during the backup procedure. Check the co-located Proxy Controller's status using the proxyadm command with the status subcommand. If the Proxy Controller is stopped, restart it using the proxyadm command with the start subcommand and the -w option. This command is in the /opt/SUNWxvmoc/bin/ on Oracle Solaris systems and in the /opt/sun/xvmoc/bin/ directory on Linux systems.

    For example:

    # proxyadm status
    offline
    # proxyadm start -w
    proxyadm: Starting Proxy Controller with SMF...
    proxyadm: Proxy Controller services have started
    #
    
  5. Restart each remote Proxy Controller to use the new Enterprise Controller.

    1. Stop the Proxy Controller using the proxyadm command with the stop subcommand and the -w option. For example:

      # proxyadm stop -w
      
    2. On the remote Proxy Controller, update the /var/opt/sun/xvm/persistence/scn-proxy/connection.properties URL property to point to the IP address of the new Enterprise Controller. Update this URL property through the command line interface using the proxyadm command with the update subcommand and the -s option:

      proxyadm update -s|--satellite-ip <ip>
      
    3. Restart the Proxy Controller using the proxyadm command with the start subcommand and the -w option. For example:

      # proxyadm start -w
      

Note:

After restoring the Enterprise Controller, the asset details might take several minutes to display completely in the user interface.

Related Articles and Resources

For more information, see these Oracle resources:


Oracle® Enterprise Manager Ops Center Restore an Enterprise Controller and Embedded Database on a New System, 12c Release 3 (12.3.1.0.0)

E60373-02

Copyright © 2007, 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.