Showing posts with label Restoring SAP System. Show all posts
Showing posts with label Restoring SAP System. Show all posts

recov_type for restore

This parameter specifies the type of database recovery using BRRECOVER.

Syntax: recov_type = complete|dbpit|tspit|reset|restore|apply|disaster

Default: complete

Possible values:

· complete: complete database recovery

· dbpit: database point-in-time (PIT) recovery

· tspit: tablespace point-in-time (PIT) recovery

· reset: whole database reset

· restore: restore of individual backup files

· apply: restore and application of archivelog (that is, offline redo log) files

· disaster: disaster recovery

This parameter corresponds to BRRECOVER –t|-type.

End of Content Area

Restore and Recovery with BR*Tools

Use

You can restore and recover your Oracle database with BR*Tools.


This section discusses how to perform restore and recovery.

For more information on the approach to restore and recovery, see Restore and Recovery.

Integration

· BRTOOLS calls the SAP tool BRRECOVER. You can also perform restore and recovery with SQLPLUS, but only if you are an expert.

· Make sure that you have set the necessary parameters for BRRECOVER in the Initialization Profile init.sap.

· You have to have SYSDBA privilege to let BRRECOVER connect to the database. This means that you have to log on as ora (UNIX) or adm (Windows).

· The recovery is normally attended, that is, you have to enter parameters as the recovery runs, when prompted by BRRECOVER.

Features

You can perform the following restore and recovery functions with BR*Tools:

· Complete database recovery

· Database point-in-time (PIT) recovery

· Tablespace point-in-time (PIT) recovery

· Whole database reset

· Restore of individual backup files

· Restore and application of archivelog (that is, offline redo log) files

· Disaster recovery

Activities

...

1. You call the restore and recovery function in BRTOOLS and check the displayed parameters, changing them as required.

The default parameter values, which are set in the initialization profile init.sap, are as follows:

¡ Recovery type is complete database recovery.

¡ Serial recovery for applying offline redo logs, using the Oracle default settings

¡ Interval of 30 days for the displayed backups to be restored. This me ans that only backups from the last 30 days can be selected by default.

¡ Scrolling of 20 lines for the list menus, only relevant for character-mode menus


BRTOOLS only lets you change certain parameters for the backup. If you have to make other changes, you must change the init.sap profile manually and then restart BRTOOLS.

2. If required, you change the default values for the restore and recovery parameters in the initialization profile init.sap and restart BRTOOLS.

3. If required, you choose Restore and recovery ® Reset program status to set the defaults used to the values in the initialization profile init.sap. For certain input values, there is no corresponding parameter in the initialization profile, in which case the default value from the BRTOOLS program is used.

4. You start the restore or recovery.

BRRECOVER takes you through the recovery step by step, displaying sub-menus as required.

5. You check the results in the BRRECOVER logs.

End of Content Area

Procedure documentationBacking Up and Restoring Your SAP System on Windows

This procedure describes how to back up and restore a SAP system on Windows Server 2003 or Windows Server 2008.

On Windows, a lot of information created during the SAP system installation and operation is stored in databases like the Windows system registry, the user registry, or the Active Directory, when installing in a Windows domain.

Therefore, we recommend that you always back up and restore the complete computer, including the operating system to avoid data or system inconsistency. In addition, the overhead of a full backup of the computer (backup of operating system disk, non-operating system disks, database data files) compared to a database online backup is negligible. During backup, the SAP system can be online.

To be able to backup and restore your SAP system properly in case of emergency, we strongly recommend that you test the backup and restore procedure on a regular basis, to avoid system downtime and data loss.

Prerequisites

You are logged on as user adm.

Procedure

Backing Up your SAP system
Windows Server 2003
  1. Back up the operating system disk.

  2. Back up the directory structures on non-operating system disks (excluding database data files)

  3. Back up the database data files.


The backup software delivered on Windows Server 2003 is designed to back up and restore a operating system to a disk that is directly connected to the computer. It has no or very limited functions and features to restore data from a disk located in a network. Therefore, customers often use third-party backup tools with more sophisticated features, such as the restore function from network locations or the snapshot backup function. These third-party backup tools often also reduce backup time and the use of system resources.

The Microsoft tool available for creating a backup on Windows Server 2003 is called NTBackup. With NTBackup you can create a backup archive of a selectable amount of objects located on one or more disks. The backup saveset can either be written to a SCSI-attached tape drive or to files on disks, which can also be located on a remote computer.

To run NTBackup, choose  Start  Programs  Accessories  System Tools  Backup  .

You can also run NTBackup in a command prompt:

- ntbackup.exe

For more information about NTBackup, see the F1 help or the Windows Help and Support documentation, which you can find in the Windows Start menu.

The procedure for backing up and restoring a Windows operating system disk is called Automated System Recovery (ASR). For the backup part, it uses a Wizard in NTBackup to create a saveset for restoring the operating system disk. The functionality of the restore part of ASR when it accesses network-based saveset locations is very limited. Therefore, we recommend that you also save the saveset to a local disk.

For more information about ASR, see the Windows Help and Support documentation, which you can find in the Windows Start menu. Search for automated system recovery.

After you have created the backup of the operating system disk, you have to create additional backup sets for the non-operating system disks attached to the system. You use NTBackup to create these backup savesets, which then might be located on a remote disk.

Finally you have to back up the database data files.


Windows Server 2008
  1. Back up the operating system disk.

  2. Back up non-operating system disks (excluding disks that contain database data files only).

  3. Back up the database data files.

In Windows Server 2008, NTBackup was replaced with Windows Server Backup (WSB). You have to activate this feature before you can use it. With WSB you can no longer back up single files or directories, but only complete disk volumes. There is an NTBackup version available, which is running on Windows Server 2008, and which you can download from the Microsoft web page. This version, however, only allows you to restore files that were backed up on Windows Server 2003. You cannot use this version to create backup savesets.

After you have activated the WSB feature, you can invoke it with  Start  Administrative Tools  Windows Server Backup

For more information about the Windows Server 2008 backup and recovery procedures, see the F1 help or the Help and Support documentation, which you find in the Windows Start menu under  Start  Help and Support / Server Fundamentals / Backup and Recovery  .

Restoring Your SAP system

Since the SAP system is very complex, we strongly recommend that you restore complete system backups only.

Restoring partial backups might lead to configuration inconsistencies and is only possible on the computer where the backup was created, and which has the same (unique) Computer Security Identifier (SID), which is generated during the installation of the Windows operating system.

Restoring the directory structure \usr\sap including the database data files on another computer leads to a complete loss of the system- and computer-specific environment on the target computer. You cannot start the system or the database on this computer for the following reasons:

  • Configuration information is also stored in the Windows system registry and this cannot be restored on a different computer.

  • Security settings on Directory and Files use unique SIDs, which cannot be translated on a different computer.

If, for any reason, you must restore a backup on a different computer, you have to perform a homogeneous system copy with the backup/restore procedure. For more information, see the System Copy Guide for your SAP product.

Windows Server 2003
  1. Restore the operating system disk with Automated System Recovery (ASR).

  2. Boot Windows Server 2003 from the installation DVD and press the F2 key.

    For more information, see the Windows ASR documentation.

  3. Restore non-operating system disks with NTBackup.

    For more information, see the F1 help in NTBackup.

  4. Restore the database.


Windows Server 2008
  1. Restore the operating system disk.

    For more information, see the Windows Help and Support documentation, which you can find in the Windows Start menu under  Start  Help and Support / Server Fundamentals / Backup and Recovery / Windows Recovery Environment Overview  .

  2. If not already done in the previous step, restore the non-operating system disks with WSB.

  3. Restore the database.