C H A P T E R 7

ILOM Back Up and Restore Operations

Topics
Description | Links
--- | ---
Learn about ILOM’s configuration management features | ILOM Configuration Management Tasks Backup and Restore Operations Reset to Defaults Feature

Related Topics
For ILOM | Chapter or Section | Guide
--- | --- | ---
CLI | Backing Up and Restoring ILOM Configuration Updating ILOM Firmware | Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide (820-6412)
Web interface | Backing Up and Restoring ILOM Configuration Updating ILOM Firmware | Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide (820-6411)
The ILOM 3.0 Documentation Collection is available at: `http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic`

##

ILOM Configuration Management Tasks

ILOM’s configuration management tasks enable you to:

- Back up the ILOM configuration to a XML file on a remote system.

- Use the backup file to restore ILOM to the backed up configuration.

- Use the backup file to install the backed up configuration on other ILOM SPs.

- Reset the ILOM configuration to the default settings.

You can use the Backup and Restore and Reset to Defaults features together in the following ways:

- Save the ILOM configuration to a backup XML file, reset the ILOM configuration to the default settings, and use the command-line interface (CLI) or web interface to create a new ILOM configuration.

- Reset the ILOM configuration to the default settings and restore it using a known good ILOM configuration backup file.

- Use the CLI or web interface to create a new ILOM configuration, save the ILOM configuration to a backup XML file, edit the XML file to remove settings that are unique to a particular system, and perform restore operations to load the backup file to other systems.

Given the above capabilities, the following use cases describe how you might typically use these features:

- You changed your ILOM configuration but it no longer works and you want to recover ILOM by restoring it to a known good configuration. To do this, first reset the ILOM configuration to the default settings and then perform a Restore operation using the known good configuration.

- You want to use the Backup and Restore feature to replicate an ILOM configuration onto other systems. To do this, create a standard ILOM configuration, back up the configuration, edit the backed up XML file to remove settings that are unique to a particular system (for example, the IP address), then perform Restore operations to replicate the configuration onto the other systems.

- You created a minimum ILOM configuration but to make it complete you need to configure a number of users (ILOM supports a maximum of 10 active user sessions per service processor). If you have backed up a configuration previously that has the same users, you can edit the XML file so that it only includes the user information and then simply perform a Restore operation to overlay the minimum configuration with the configuration that has the user accounts. Reuse of large network configurations such as Active Directory is another use case for this approach.

You can use either the web interface or the CLI to perform configuration management tasks in ILOM. For more information about these tasks, see:

- Backup and Restore Operations

- Reset to Defaults Feature

### Backup and Restore Operations

ILOM supports two separate operations for backup and restore.

- The Backup operation consists of gathering the current ILOM configuration data into an XML file and transferring that file to a remote system.

- The Restore operation consists of retrieving the XML backup file and using it to restore the ILOM SP to the backed up configuration.

Thus you can use Backup and Restore to save the ILOM configuration to a backup XML file, and later restore the backup file to the same system. Further, if you want to use the backup XML file on other systems, you can edit the XML file to remove or change settings that are unique, such as the IP address. The backup XML file is readable and can be edited manually.

| Caution - If you are going to restore the edited backup XML file to the same system, you should reset the ILOM configuration to the default settings; otherwise, the restored configuration will simply overlay the current configuration. If you are going to restore the edited backup XML file to others systems that already contain an ILOM configuration, you should erase the ILOM configuration unless you want to overlay the current configuration. To erase the current ILOM configuration, you must reset the ILOM configuration to the default settings. For instructions, see “Reset the ILOM Configuration to Defaults” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, or in theOracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide.

All of the information that can be configured on the system can be backed up. The privileges assigned to the user account that is used to execute the Backup operation determine how much of the configuration is included in the backup XML file. For security reasons, if the user account used to execute the Restore operation has fewer privileges than the account used to create the backup file, some of the configuration might not be restored. For each configuration property that is not restored due to lack of privileges, a log entry is created. Therefore, one way to verify that all the configuration properties were restored is to check the event log.

You can also limit the amount of information included in the backup XML file by using user accounts that have limited privileges. For example, an account assigned the Admin (`a`), User Management (`u`), Console (`c`), Reset and Host Control (`r`), and Read Only (`o`) roles would have full privileges and would create the most complete configuration backup file. For this reason, it is recommended that user accounts assigned the `a`,`u`,`c`,`r`,`o` roles be used whenever you perform Backup and Restore operations.

Configuration Backup and Restore operations do not change the power state of the host operating system. However, both operations cause all sessions on the ILOM SP to be momentarily suspended until the Backup or Restore operation completes. A Backup or Restore operation typically lasts two to three minutes, after which all logged in sessions resume normal operation.

For instructions on performing Backup and Restore operations and editing a backup XML file, see “Backing Up and Restoring ILOM Configuration” in the following guides:

- Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide

- Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide

### Reset to Defaults Feature

With the Reset to Defaults feature in ILOM, you can reset the ILOM configuration settings to their default settings. When you use this feature you are given three options:

- All - Select this option if you want to erase the existing ILOM configuration file. When the ILOM SP reboots, the configuration file that was included in the SP firmware is used instead.

- Factory - Select this option if you want to erase the existing configuration file and the internal log files. When the ILOM SP reboots, the configuration file that was included in the SP firmware is used instead and the internal log files are erased.

- None - Select this option if you want to cancel the reset operation you initiated previously. To cancel a previously initiated reset operation you must initiate a reset operation with the None option before the ILOM SP reboots.

Note - When you execute an ILOM configuration reset, the reset configuration does not take effect until the ILOM SP reboots.

For instructions on resetting the ILOM configuration to the default settings, see “Reset the ILOM Configuration to Defaults” in the following guides:

- Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide

- Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide

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