8 Backup and Recovery

Introduction to Backup and Recovery

Oracle Enterprise Manager Ops Center has several tools that can be used for disaster recovery. These tools let you preserve Oracle Enterprise Manager Ops Center data and functionality if the Enterprise Controller or Proxy Controller systems fail.

The ecadm backup and ecadm restore commands back up and restore the Enterprise Controller, but they do not back up or restore the colocated Proxy Controller. The backup command backs up product data and saves the data in a tar file. You can specify the name and location of the backup file and the log file.

The ecadm backup command creates a backup file that contains all of the Oracle Enterprise Manager Ops Center information stored by the Enterprise Controller, including asset data, administration data, job history, and the database password. Software and storage library contents are not backed up by the ecadm backup command.

If the Enterprise Controller system fails, you can use the ecadm restore command and the backup file to restore the Enterprise Controller to its previous state. The new Enterprise Controller system must have Oracle Enterprise Manager Ops Center installed but not configured. The ecadm restore command accepts the name of the backup file as input, and restores the Enterprise Controller to the state it had at the time of the backup.

Some of the procedures described in this section use the ecadm and proxyadm commands. See the Oracle Enterprise Manager Ops Center Feature Reference Guide for more information about this command.

• On Oracle Solaris systems, this command is in the /opt/SUNWxvmoc/bin/ directory.

• On Linux systems, this command is in the /opt/sun/xvmoc/bin/ directory.

Backing Up an Enterprise Controller

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

To Back Up an Enterprise Controller

By default, the server data is saved in a backup file in the /var/tmp directory with a file name that includes a date and time stamp. You can define the file name and location during the backup, as shown in the example below.

If you are using an embedded database, the backup file will include the product schema from the embedded database. If you are using a customer-managed database, you can back up the database schema using the --remotedb option, or you can use the existing backup and recover processes implemented by your database administrator.

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.

   The following options may be used with the ecadm command:

   • -o|--output <backup file> – Specify the file in which the backup archive will be generated. Do not specify a path inside the /opt/*xvm* directories. The default output file is /var/tmp/sat-backup-<date>-<time>.tar.

   • -c|--configdir <dir> – Specify an alternate backup configuration directory.

   • -l|--logfile <logfile> – Save output from command in <logfile>. Log files are stored in the /var/opt/sun/xvm/logs/ directory.

   • -d|--description <description string> – Embed the <description string> as the description of the backup archive.

   • -r|--remotedb – If the Enterprise Controller uses a customer-managed database, export the database schema to a file on the database server. This does not perform a full database backup, which should be performed separately by the database administrator.

   • -t|--tag <tag> – Embed <tag> as a single-word tag in the backup archive

   • -T|--tempdir <dir> – Specify the temporary staging directory location.

   • -v|--verbose – Increase verbosity level (may be repeated)

   For example:

   ecadm backup -o /var/tmp/backup-file-name.tar
   

3. Save the contents of the most recent upgrade installation directory. This directory is a child of the /var/opt/sun/xvm/update-saved-state/ directory, and is named according to the version number.

4. Copy the backup file to a separate system.

Restoring an 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.

To Restore an Enterprise Controller

This procedure restores the data from the backup file, which is the archive created by the ecadm backup operation.

If you are using an embedded database, the restore process will restore the product schema from the embedded database. If you are using a customer-managed database, you can use the --remotedb optionto restore the product schema on the customer-managed database, or leave this option off to make no changes to the database.

1. Prepare the Enterprise Controller system.

   • If you are restoring the backup on a new system, then the IP address, host name, and Enterprise Controller software version of the restored system must match those of the backed up system.

   • If you are restoring the backup on the same system, but the software has become corrupt or an upgrade failed, uninstall the Enterprise Controller software.

     Run the install script with the -e and -k options. The -e option uninstalls the Enterprise Controller and co-located Proxy Controller, and the -k option preserves the Oracle Configuration Manager software. For example:

     # cd /var/tmp/OC/xvmoc_full_bundle
     # install -e -k
     

   • If you are restoring the backup on the same system, and the software is functioning normally, unconfigure the Enterprise Controller.

2. Install the Enterprise Controller if it has not been installed, but do not configure the Enterprise Controller.

   1. Oracle Solaris OS: See the Oracle Enterprise Manager Ops Center Installation Guide for Oracle Solaris Operating System.

   2. Linux OS: See the Oracle Enterprise Manager Ops Center Installation Guide for Linux Operating Systems.

      The restore command will restore your configuration settings.

3. Upgrade the Enterprise Controller to the same version that was running when the backup was made, if it is not already running that version. Perform this upgrade from the command line.

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

   The following options may be used with the ecadm command:

   • -i|--input <backup file> – (Required) Specify the location of the backup file.

   • -c|--configdir <dir> – Specify an alternate restore configuration directory.

   • -l|--logfile <logfile> – Save output from command in <logfile>. Log files are stored in the /var/opt/sun/xvm/logs/ directory.

   • -r|--remotedb – If the Enterprise Controller uses a customer-managed database, this command restores the product schema on that database.

   • -T|--tempdir <dir> – Specify the temporary staging directory location.

   • -v|--verbose – Increase verbosity level (may be repeated)

   For example:

   ecadm restore -i backup-directory-location/file-name
   

5. For an Enterprise Controller with a co-located Proxy Controller, restart the co-located Proxy Controller using the proxyadm command. The proxyadm command is in the same directory as the ecadm command.

   proxyadm start -w
   

6. For an Enterprise Controller with a co-located Proxy Controller, use the Add Assets method to rediscover the system after running the ecadm restore command. See the Oracle Enterprise Manager Ops Center Feature Reference Guide for more information about the Add Assets procedure. You do not need to re-register the assets.

   Note:

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

Example – Restoring an Enterprise Controller With an Embedded Database

In this example, the restore command includes options to set the restore in verbose mode (-v), and to create a restore log (-l) for debugging purposes. The input (-i) option specifies the backup file location.

# /opt/SUNWxvmoc/bin/ecadm restore -v -i /var/tmp/OC/server1/backup-May28-2012.tar -l logfile-restore-May28-2012.log

Example – Restoring an Enterprise Controller With a Customer-Managed Database

In this example, the restore command includes the (-r) option to restore the database schema on a customer-managed database. The input (-i) option specifies the backup file location.

# /opt/SUNWxvmoc/bin/ecadm restore -i /var/tmp/OC/server1/backup-May28-2012.tar -r

Example – Restoring an Enterprise Controller With a Customer-Managed Database Without Restoring the Database Schema

In this example, the restore command includes options to set the restore in verbose mode (-v), and to create a restore log (-l) for debugging purposes. The input (-i) option specifies the backup file location. The (-r) option is not included.

# /opt/SUNWxvmoc/bin/ecadm restore -v -i /var/tmp/OC/server1/backup-May28-2012.tar -l logfile-restore-May28-2012.log