Integrating SAP DB/MaxDB and Data Protector

Restoring an SAP DB/MaxDB Database

NOTE

During the restore or migration, the archive logs on the SAP DB/MaxDB

 

Server are never deleted.

 

 

SAP DB/MaxDB Migration Prerequisites

The integration supports SAP DB/MaxDB migration, meaning that an SAP DB/MaxDB instance can be restored to some other SAP DB/MaxDB Server or instance than the original.

If the SAP DB/MaxDB Server has not yet been configured for the Data Protector SAP DB/MaxDB integration, it must be configured before the restore is started. If the instance does not exist, it must be configured before the restore is started. During the migration, the existing data is overwritten and the existing redo logs are deleted.

Perform the following list of tasks before starting an SAP DB/MaxDB migration:

•Install the Data Protector SAP DB/MaxDB integration on the

SAP DB/MaxDB Server to which you want to migrate the backed up SAP DB/MaxDB instance. When this is done, add the

SAP DB/MaxDB Server in the Data Protector cell.

•Identify or create an OS user under whose account the

SAP DB/MaxDB is running and add it to the Data Protector admin group. For information on how to do this, see “Configuring Users” on page 263.

•When performing an SAP DB/MaxDB migration, first configure the instance to which you want to perform the restore. For information on how to configure an instance, see “Modifying the Configuration of an SAP DB/MaxDB Instance in Data Protector” on page 272.

When performing an SAP DB/MaxDB migration using the Data Protector GUI, the instance does not need to be configured beforehand, it can be configured during the restore process.

294

Chapter 3