HP A.06.11 - Manual (Page 196)

fileA=0;
fileB=1;
fileC=0;fileD=2;}}
When you group files into subsets, consider the following:
• Use only one file from the same hard disk at a time.
• The number of files in a subset must be equal to or smaller than the sum of the
concurrencies of all devices specified for backup.
• If the backup specification contains files that are not allocated to any subset, Data
Protector automatically adds these files to the list of files to be backed up using
the load balancing principle. Before the backup, this list is logged in:
UNIX: ORACLE_HOME/sapbackup/.*.lst
Windows: SAPDATA_HOME\sapbackup\*.lst
Restore
You can restore SAP R/3 objects in any of the following ways:
• Use the Data Protector GUI. See “ Restoring using the Data Protector
GUI ” on page 197.
• Use the Data Protector CLI. See “ Restoring using the Data Protector
CLI ” on page 200.
• Use the SAP restore commands. See “ Restoring using the SAP
commands ” on page 201.
After the restore, you can recover the database to a specific point in time using the
SAP BRTOOLS interface.
Considerations
• Backups created by Oracle RMAN can only be restored using the SAP restore
utilites.
• SAP R/3 tablespaces located on raw partitions cannot be restored using the Data
Protector GUI. Workaround: Use SAP restore commands (for example,
brrestore
).
• If you are restoring a sparse file, you can improve the performance by setting the
sparse option. See “
Sparse files ” on page 203.
• If your Oracle database is localized, you may need to set the appropriate Data
Protector encoding before you start a restore. For details, see “
Localized SAP
R/3 objects ” on page 202.
Integrating SAP R/3 and Data Protector 196