Before you can back up data and log entries to a data carrier, you have to define a backup template. In the properties of the backup template you specify the backup type and the type of data carrier that is to be used.
To speed up backups, you can carry them out to several data carriers in parallel. If choose to do so, you need to define a backup template for parallel backups.
You are logged on to the database as the database system administrator or as a DBM operator with server authorization for performing backups.
More information: Glossary, Server Permission
In the context menu of the database, choose Administration.
Open the Backup tab page.
Expand Templates.
Choose New.... .
Note
To create a backup template for parallel backups, choose
. You then proceed as with normal backup templates, except that you define several devices instead of one. For backups of the TAPE type, you can use up to 32 tape devices in parallel.Enter the following data:
Property |
Description |
---|---|
Name |
The name of the backup template has no influence on the name of the backup created later using this backup template. |
Backup Type |
|
Device Type |
Data carrier type
|
Backup Tool |
If you are using a backup tool from a third-party provider, specify the abbreviation for your backup tool:
More information: Database Administration, Using Backup Tools from Other Providers |
Device/File |
Depending on the backup type enter the required information:
We recommend that you do not use the same data carrier for several databases. For log backups to files, the system adds a sequence number to the name of each new backup file. It assigns the numbers sequentially as long as the history of the log backups is not interrupted. If the log backup history is interrupted (for example after the database was initialized), the system begins numbering at 001 again. It also uses sequential numbers if you carry out multiple log backups for one database onto different data carriers, and thus to files with different file names. Example LogUri.001 LogKai.002 LogOleg.003 LogUri.004 LogUri.005 End of the example. If automatic log backup is switched on, the system stores all backup files under the same file name using a sequence number. Example DEMODB_MYLOG.001 DEMODB_MYLOG.002 DEMODB_MYLOG.003 DEMODB_MYLOG.004 DEMODB_MYLOG.005 End of the example. You can also back up to data carriers on remote computers. More information: Database Administration, Backing Up and Restoring Data with Remote Computers |
Size |
There is no size restriction in default mode. The size of log backups to files is calculated as the size of a log segment (general database parameter AutoLogBackupSize) plus the space required by system information. More information: Database Administration, General Database Parameters |
Overwrite |
If you want to back up to a file and use this file more than once, define the backup template so that the data carrier can be overwritten. If you use this type of backup template for backups, the system overwrites old backups with new backups. We recommend that you do not overwrite a backup with the backup that immediately follows it. Always keep an older version of the backup. |
Block Size |
Block size that the system uses to write backups to the data carrier. |
Autoloader |
Select this option if you want to use a tape device with an automatic tape loader. |
OS Command |
Operating system commands for backing up to tape devices. |
Note
For automatic log backup, you cannot use pipes.
To use a third-party backup tool, choose the following settings:
Device Type: Pipe
Backup Tool: Identification code of the backup tool
Device/File: Operating system path of the pipe
Name |
Key |
Description |
More information |
---|---|---|---|
TSM (IBM/Tivoli) |
TSM |
You can connect TSM using the TSM client adint2 or using the Backint for Oracle interface. You can use adint2 for better performance. However, it is not available on all platforms. |
Installation Manual, |
NetWorker (Legato) |
NSR |
You can connect NetWorker using the command line clients SAVE, RECOVER and MMINFO included in the Networker software or using the Backint for Oracle interface. The command line clients deliver better performance. |
See Installation Manual, Connecting to NetWorker |
NetBackup (Veritas) |
BACK |
- |
Installation Manual, Connecting to VERITAS NetBackup |
All backup tools that support Backint for SAP MaxDB |
BACK |
Backint for SAP MaxDB is an interface that is supported by various other providers. |
Installation Manual, Connecting to a Backint for SAP MaxDB Interface For more information about the requirements for the Backint for SAP MaxDB interface, see http://maxdb.sap.com/archive/. For more information about technology partners that support Backint for SAP MaxDB, use the search function at http://www.sap.com/partners/directories. |
All backup tools that support Backint for Oracle |
BACK |
Backint for Oracle is an interface that is supported by various other providers. |
Installation Manual, Connecting to a Backint for Oracle Interface For more information about technology partners that support Backint for Oracle, use the search function at http://www.sap.com/partners/directories. |
Property |
Value |
---|---|
Name of the backup template |
COM |
Backup type |
COMPLETE DATA |
Data carrier type |
FILE |
Data carrier (Device/File) |
DEMODB_COM If you do not enter an absolute path, then the database system uses the run directory of the database. Example: C:\Documents and Settings\All Users\Application Data\sdb\data\wrk\DEMODB\ More information: Run directory |
Size of data carrier |
No restriction (blank or 0) |
Block size |
8 pages |
Overwritable |
Yes |
Property |
Value |
---|---|
Name of the backup template |
MYLOG |
Backup type |
LOG |
Data carrier type |
FILE |
Data carrier (Device/File) |
DEMODB_MYLOG If you do not enter an absolute path, then the database system uses the run directory of the database. Example: C:\Documents and Settings\All Users\Application Data\sdb\data\wrk\DEMODB\ More information: Run directory |
Size of data carrier |
No restriction (blank or 0) |
Block size |
8 pages |
Overwritable |
No |
Database Administration, Backup Templates and Data Carriers