Legato Storage Manager Administrator's Guide Release 8.0.4 A58373-01 |
Library | Product | Contents | Index

# 4
Backup and Restore Operations

This chapter presents information about using LSM for Oracle backup and restore operations after you have configured the requisite LSM resources in the LSM Server. It provides general information on how to run Oracle backups and restores as well as details on LSM Server bootstrap backups. The methods for monitoring Oracle backups and restores by means of the LSM Administrator GUI and specific log files are also outlined.

##### Major Topics:

- Running Oracle Backups and Restores
- LSM Server Bootstrap Backups
- Monitoring Oracle Backups and Restores

## Running Oracle Backups and Restores

The preceding chapters of this guide outline the procedures for configuring LSM for Oracle backup and restore operations. After applying the information in those chapters, you should have all the required client, server, device, and volume pool resources configured in the LSM Server. Also, you should have a labeled volume mounted in each configured backup device-or, if auto media management is enabled for a tape device, a tape loaded in the tape device for LSM to use automatically.

As explained in "Overview of LSM Features" in Chapter 1, you can start an Oracle backup or restore by running one of the two following programs:

- Command-line interface of the Oracle backup/restore utility on the Oracle Server
- OEM Backup Manager on a Windows NT or Windows 95 system

For information about using the command-line interface, see "Using the Oracle Backup/Restore Utility" as follows. For more information on using the GUI, see "Using the Oracle Enterprise Manager Backup Manager".

### Using the Oracle Backup/Restore Utility

The Oracle backup/restore utility is one of the following programs:

- Enterprise Backup Utility (EBU) in Oracle7
- Recovery Manager (RMAN) in Oracle8

You can use the command-line interface to issue the appropriate EBU or RMAN command to start a specific type of backup, restore, or recovery on your Oracle7 Server or Oracle8 Server. The backup/restore utility interacts with LSM in performing the backup or restore operation, as explained in "Overview of Oracle Backup and Recovery System" in Chapter 1.

For information on using EBU in Oracle7, refer to the Oracle7 Enterprise Backup Utility Administrator's Guide. It outlines the EBU commands that you can use to start different types of Oracle7 backup and restore operations. It also describes the important procedures that you must perform prior to using EBU with LSM. The following tasks are among those outlined in the Oracle7 guide:

- How to create an EBU Catalog
- How to register an Oracle database in the EBU Catalog
- How to properly set up the required EBU_HOME environment variable

For details about using RMAN in Oracle8, refer to the Oracle8 Server Backup and Recovery Guide. This guide outlines the RMAN commands to use for starting different types of Oracle8 backup and restore operations. It also explains the prerequisite tasks to perform prior to using RMAN with LSM. The following tasks are among those outlined in the Oracle8 guide:

- How to create a Recovery Catalog
- How to register an Oracle database in the Catalog
- How to resynchronize the Recovery Catalog
- How to allocate a channel connection to the target database
- How to generate unique output file names for backups

  Note: For RMAN backups using LSM, each backup piece (or LSM "save set") must have a unique generated name. As mentioned in the section "Generating Unique File Names" in the Oracle8 Server Backup and Recovery Guide, you must generate a unique name for each backup piece by means of the substitution variables (%d, %t, %s, %p, and %u) provided by Recovery Manager. The format string specified in the "backup" command or "allocate channel" command determines the name of the backup piece. If an RMAN backup using LSM generates a name that already exists in the LSM index database, the original backup save set with that name is deleted. For example, if you back up two databases to one LSM server, and you use the format string %s%p in the backup command for both databases, the same piece names will be generated for both databases. In this case the database backup which started first will be deleted when the backup of the second database begins, as %s%p is not unique across databases. Alternatively; if you use the format string ORA_%d_%u where %d is the database name and %u is a generated number, then each save set backed up with a unique name can be restored later without difficulty.

### Using the Oracle Enterprise Manager Backup Manager

You can use the Oracle Enterprise Manager instead of the Oracle utility command-line interface to start an Oracle backup or recovery. The OEM Backup Manager is the graphical user interface to the Oracle backup/restore utility that enables you to perform backup and restore operations through a point-and-click method.

The Oracle Enterprise Manager provides a much simpler interface for running Oracle backups and restores; it generates the required commands for the appropriate Oracle utility. In Oracle7, the OEM Backup Manager generates commands for EBU, while in Oracle8, it generates RMAN commands.

For complete information on using the Oracle Enterprise Manager, refer to the Oracle Enterprise Manager Administrator's Guide and the other Oracle Enterprise Manager documentation included with your product kit.

You must install the Oracle Enterprise Manager on a Windows NT or Windows 95 system, which can be either the Oracle Server machine or a separate machine on the network.

It is possible to install and run the LSM Administrator GUI on the same Windows NT or Windows 95 machine as the Oracle Enterprise Manager. (The LSM installation process automatically installs the LSM Administrator GUI on the Oracle Server.) You can use the LSM Administrator GUI to connect to the LSM Server and monitor the status of Oracle backup and restore operations.

## LSM Server Bootstrap Backups

As mentioned in "Overview of LSM Operations" in Chapter 2, the LSM Server is preconfigured to perform a special automatic backup-the LSM Server bootstrap backup-every day at 3:33 a.m. The bootstrap consists of the following three files from the LSM Server:

- Client index
- Media index
- Resource database

The bootstrap is a special backup set essential for disaster recovery procedures of the LSM Server. LSM writes the bootstrap file to the backup media and generates a report about the success of the bootstrap backup. LSM sends an automatic notification to the administrator about the bootstrap backup and displays the same information in the LSM Administrator GUI. Also, bootstrap information is sent to a printer on the LSM Server.

Note: Note that if the LSM system is down at the time that the automatic bootstrap backup is scheduled to run, the backup will run when the system comes back up.

You can also run the bootstrap backup manually. For example, after finishing the last of many Oracle backups performed during a day, it would be advisable to manually run a bootstrap backup, to ensure that you have an up-to-date bootstrap. An up-to-date bootstrap is essential for a complete disaster recovery on the Oracle Server.

The next section, "Automatic Bootstrap Backup", contains instructions about how to verify that the LSM Server is properly configured for the automatic bootstrap backup. For information about how to run the bootstrap backup manually, see "Manual Bootstrap Backup". "Maintaining Bootstrap Information" has details about the critical bootstrap information you need to keep for future disaster recovery procedures.

Chapter 5, "Disaster Recovery" contains complete details about how to use the LSM Server bootstrap during a disaster recovery on the Oracle Server.

### Automatic Bootstrap Backup

To verify that the LSM Server configuration is properly set up for the automatic bootstrap backup, you need to run the LSM Administrator GUI. See "Using the LSM Administrator GUI" in Chapter 2 for details about running the GUI on either a UNIX or Windows system.

Then, you need to verify that the client resource and Default group resource are both configured correctly. For information about accessing the client resource, see "Client Resource" in Chapter 2. In the client resource, be sure that the Group attribute is set to Default.

Finally, check the Default group resource configuration. Open the Groups window by one of the following methods, depending on the type of system running the GUI:

- On a UNIX system, select Groups from the Customize pull-down menu in the main LSM Administrator window.
- On a Windows system, click the Configure tab in the Server window (of the main Administrator window) to make the Configure window active, and then click Manage Groups to open the Groups window.

The Groups window lists the single group resource, with the name Default. On a UNIX system, the Groups window also shows all the attribute settings of the group resource.

On a UNIX system, the Groups window is displayed as shown in Figure 4-1.

#### Figure 4-1 Groups Window on UNIX

On a Windows system, the Groups window does not automatically show the attribute settings of the group resource, so you must perform the following additional steps to see the group's attributes:

1. In the Groups window, right-click the icon of the Default group and select Edit from the pop-up menu to open the Edit Group dialog box.
2. In the Edit Group dialog box, the General (default) tab shows the attributes of the Default group resource. Click Field Help to learn more about each attribute shown.

The Edit Group dialog box on a Windows system, listing all the attributes of the group resource, is displayed as shown in Figure 4-2.

#### Figure 4-2 Edit Group Dialog Box on Windows

The Start time attribute specifies when the bootstrap backup is configured to begin-3:33 a.m. by default. To have the bootstrap information sent to a specific printer, set the Printer attribute to the name of that printer.

Note: Be sure that the Autostart attribute is set to Enabled to enable the automatic bootstrap backup. If Autostart is set to Disabled, the bootstrap backup does not run.

Note that information confirming the completion of the automatic bootstrap backup is displayed in the LSM Administrator GUI. It's in the Messages section of the main LSM Administrator window on a UNIX system or in the Messages section of the Monitor window on a Windows system.

### Manual Bootstrap Backup

If you want to manually run the bootstrap backup, you must be root on the LSM Server on a UNIX system or Administrator on a Windows NT system. Then, to run the manual backup, enter this `savegrp` command at the system prompt:

    savegrp -O -l full -P printer_name -c server_name

Here, printer_name is the name of the printer where the bootstrap information is printed at the end of the bootstrap backup. Also, server_name is the hostname of the LSM Server.

On UNIX, refer to the `savegrp` manual page for information about the `savegrp` command and its options. On Windows NT, refer to `savegrp` in the Command-Line Utilities Help provided with LSM on Windows NT. See "Windows Command-Line Utilities Help" in Chapter 1 for details about using the Command-Line Utilities Help.

Note that information confirming the completion of the manual bootstrap backup is displayed in the LSM Administrator GUI. It's in the Messages section of the main LSM Administrator window on a UNIX system or in the Messages section of the Monitor window on a Windows system.

### Maintaining Bootstrap Information

At the end of the automatic daily bootstrap backup, LSM prints the bootstrap information to the printer specified in the Printer attribute of the Default group resource; or, if that Printer attribute is blank, to the default printer.

At the end of a manual bootstrap backup run with the `savegrp` command, as described in "Manual Bootstrap Backup", the bootstrap information is sent to the printer specified in that `savegrp` command.

Be sure to store the bootstrap printout in a safe place. The printed bootstrap information includes dates, locations, and save set ID numbers for the bootstrap save sets backed up during the past month. With this information, you can determine which volumes are needed to recover the LSM Server indexes and resource database files during a disaster recovery.

An example of a bootstrap printout is as follows:

    August 20 03:30 1997 LSM bootstrap information Page 1
    date     time     level  ssid        file  record  volume
    8/19/97  2:29:08  9      1148868949  56    0       jupiter.005
    8/20/97  2:52:25  9      1148868985  77    0       jupiter.001

## Monitoring Oracle Backups and Restores

You can use the LSM Administrator GUI to monitor the status of Oracle backup and restore operations. In the GUI on UNIX, the messages are displayed in the Sessions and Messages sections of the main LSM Administrator window. In the GUI on Windows NT, the messages appear in the Monitor window.

You can view progress messages that appear during the backup and completion messages that advise when the backup is complete. You can also view the messages in specific online system files.

- For progress messages, watch the Sessions display in the LSM Administrator GUI. The Sessions display information is also written to a daemon.log file in the /nsr/logs directory on UNIX or in \win32app\nsr\logs on Windows NT.
- For completion messages, watch the Messages display in the LSM Administrator GUI. The Messages display information is also written to a messages file in the /nsr/logs directory on UNIX or in \win32app\nsr\logs on Windows NT.
- For information about why a backup cannot progress, view the messages in the Pending display. The Pending display shows requests to mount tapes and other conditions that require operator intervention. See "Volume Operations" in Chapter 3 for examples of the messages that LSM displays when requesting a volume for Oracle backup or restore.
- LSM also writes error messages to a specific system file. On UNIX, the file is /nsr/applogs/dmo.messages. On Windows NT running Oracle7 or Oracle8, LSM error messages are written to \win32app\nsr\logs\dmo.messages and \win32app\nsr\logs\orasbt.messages. In some circumstances, these messages files can be created in your TEMP directory. On Windows NT running Oracle8, the error messages can also be found in $ORACLE_HOME\RDBMS80\TRACE\sbtio.log. For more information on a particular error condition, refer to the appropriate error file for your system.

  Note: Ensure that Oracle has write permissions on the dmo.messages and orasbt.messages files mentioned above.

The following example shows the types of messages displayed in the Sessions and Messages sections of the main LSM Administrator window on UNIX during Oracle backups.

#### Figure 4-3 Oracle Backup Messages on UNIX

Prev | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index