Other applications of NetBackup for SQL Server Performing backups and restores in an SAP environment
If the R/3 database disk system is damaged or the transaction log disk system is damaged, follow the instructions in “Restoring the R/3 database after a disk crash” on page 154.
To perform a regular restore of the R/3 database, follow the instructions in “Restoring the database and transaction log backups.”
Including differential backups in a restore operation
If you incorporated differential backups in the backup strategy, the restore process differs depending on the type of backups available.
If differential backups were made after the last full database backup, restore the last database backup followed by the most recent differential backup. Then apply all subsequent transaction logs.
If no differential backups were made since the last full database backup, restore the last full database backup and then apply all subsequent transaction logs.
If several differential backups are available, but the latest one cannot be read.
Restore the most recent full database backup and then you restore the latest readable differential backup. Then apply all subsequently created transaction logs.
Restoring the R/3 database after a disk crash
This section describes how to restore the database when the R/3 database disk system is damaged or the transaction log disk system is damaged. This process is only applicable to a configuration with three disk systems: one system for the R/3 database, one for the R/3 transaction logs and one for all others.
Note: The R3 database must not be in use when performing a restore operation. Make sure that all SAP services are stopped before attempting a restore using NetBackup.
To restoring the R/3 database after a disk crash
Back up the current transaction log.
If the disk system on which the R/3 database resides is damaged, it is vital to immediately backup the currently active transaction log to prevent loss of data. Without a backup of the current log, the database can only be restored to the status at the time of the last transaction log backup. If work has been carried out on the R/3 system since then, this work will be lost.