During backups, the data/log entries are saved onto a data carrier, such as a tape or a file in the file system.
Before you can back up data and log entries onto a data carrier, you have to define a backup template. In the properties of the backup template you specify, among others, the backup type and the type of data carrier that is to be used. The Database Manager stores the backup templates in the file dbm.mmm (see Configuration Files). You can use the same backup template more than once.
● Name
You can use any name for the backup template. The name of the backup template has no influence on the names of the backups created with this backup template.
● Backup type (full or incremental data backup, log backup, automatic log backup)
● Data carrier type
Type |
Usable for Backup Types |
Remarks |
File (FILE) |
● Data backup ● Log backup ● Automatic log backup |
|
Tape (TAPE) |
● Data backup |
You can use an autoloader. |
Pipe (PIPE) |
● Data backup ● Log backup |
Automatic log backups to pipes are not possible. |
Note the further recommendations and restrictions; see Information on Different Types of Data Carriers.
● Data carrier (Device/File)
Enter the name of the tape device in the operating system, or the path and file name of the file in the file system, or the path and name of the pipe.
The system adds a sequence number to the name of each new backup file for log backups to files. The system 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 if the database instance is initialized), the system begins numbering at 001 again.
The system also uses sequential numbers if you carry out multiple log backups for one database instance onto different data carriers, and thereby to files with different file names.
LogUri.001
LogKai.002
LogOleg.003
LogUri.004
LogUri.005
If automatic log backup is switched on, the system stores all backup files under the same file name and adds the sequential number.
autoLog.001
autoLog.002
autoLog.003
autoLog.004
autoLog.005
● Size of data carrier
You can select the size of the data carrier for data backups. There is no size restriction in default mode
The size of log backups in files is the size of a log segment (general database parameter LOG_SEGMENT_SIZE) plus the space required by system information.
● Overwritable
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.
● Block size
You can define the block size that the system uses to write backups onto the data carrier.
Example: Backup Template
Property |
Value |
Name of the backup template |
My data backup of DEMODB |
Backup type |
Complete data backup (DATA) |
Data carrier type |
File (FILE) |
Data carrier (Device/File) |
backup 2005\data\complDataJan |
Size of data carrier |
No restriction (empty) |
Block size |
6 pages |
Overwritable |
No |
You use the Database Manager or the CCMS (in SAP systems).
● Database Manager GUI, Backup Template for a Single Data Carrier, Backup Template for a Group of Parallel Data Carriers
Database Manager CLI, medium_put
Database Administration Tutorial, Defining Backup Templates
Database Administration in CCMS: MaxDB, Backup Templates
Database Administration in CCMS: SAP liveCache Technology, Backup Templates
You can also define backup templates for parallel backups.
Database Manager GUI, Managing the Backup Templates
Database Manager CLI, Backing Up and Restoring Database Instances
Database Administration in CCMS: MaxDB, Backup Templates
Database Administration in CCMS: SAP liveCache Technology, Backup Templates
Regularly check whether your backups are intact. See
Database Manager GUI, Checking Backups
Database Manager CLI, recover_check
See also:
Using Backup Tools from Other Providers
Database Administration Tutorial, Defining Backup Templates