Before you can back up data and log entries to a data carrier, you must define backup templates. In the properties of a backup template you specify, among other things, the backup type and the type of data carrier that is to be used. You can use the same backup template more than once.
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. |
The following table shows the different types of data carriers you can use for data and log backups.
Type |
Suitable for the Following Backup Types |
Comments |
---|---|---|
FILE |
|
Do not create backups on data carriers of the FILE type that are located on the same hard disk as the volumes of the database. Always back up to a separate hard disk. If your data carriers are located on the same computer as the database, regularly copy the backups to other computers or data carriers using operating system commands. |
TAPE |
|
You can use autoloaders. Do not use tapes more often than is recommended by the manufacturer. Unix:
|
PIPE |
|
On Microsoft Windows, the pipes are created by the database kernel. On Unix, the pipes are not created by the database kernel:
Before you carry out a log backup to a pipe without a third-party backup tool or with a third-party backup tool not directly supported by SAP MaxDB, first set the value of the special database parameter EnableLogBackupToPipe to YES. This ensures that the system can overwrite the log entries in the log area that have already been written to the pipe. Note that the system does not check whether the log backup to the pipe was successful. More information: Database Administration, Special Database Parameters |
To create backup templates, use Database Studio, Database Manager CLI or CCMS (in SAP systems only). More information:
Database Studio,
Database Manager CLI Tutorial, Defining Backup Templates
Database Administration in CCMS, Backup Templates
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 |