Procedure documentationDefining Backup Templates Locate this document in the navigation structure

 

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 can use third-party backup tools to back up and restore data and log entries

Prerequisites

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

Procedure

  1. Select the database in the explorer tree.

  2. In the context menu of the database, choose Administration.

  3. Open the Backup tab page.

  4. Expand Templates.

  5. Choose New.... .

    To create a backup template for parallel backups, choose   New   New Parallel Backup Template  . 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.

  6. Enter the following data:

    Backup Template Properties

    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

    • Complete data backup

    • Incremental data backup

    • Log backup

    Device Type

    Data carrier type

    • File

    • Tape

    • Pipe

      Note Note

      For automatic log backups, you cannot use pipes.

      End of the note.

    Backup Tool

    Only if you are using a third-party backup tool

    Specify the backup tool:

    • BACK: Backint for Oracle or Backint for MaxDB

    • NSR: Networker

    • TSM: TSM

    More information: Database Administration, Using Third-Party Backup Tools

    Device/File

    Depending on the backup type enter the required information:

    • Name of the tape device in the operating system

    • Path and file name of the file in the file system

      Caution Caution

      If you do not enter a full path here, the system stores your backup in the run directory of the database.

      More information: Glossary, Run Directory

      End of the caution.

    • Path and name of the pipe

    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 starts 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 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 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

    Compressed

    For backup templates of the FILE and PIPE types only

    Specifies whether the backup is compressed

    Overwrite

    For backup templates of the FILE type only

    Specifies whether the backup file can be overwritten

    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

    For backup templates fo the TAPE type only

    Operating system command for backing up to tape devices

    Encryption

    Prerequisites: license for SAP Cryptolib (only available in SAP systems), private-public key pair has been created using sapgenpse

    • Algorithm

      Available encryption algorythms: DES, AES

    • Owner

      Private key owner (see X.509 certificate)

    For more information, see Encryption.

    To use a third-party backup tool, choose the following settings:

    • Device Type: Pipe

    • Backup Tool: Name of the backup tool

    • Device/File: Operating system path of the pipe

    Supported Third-Party Backup Tools

    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.

    With adint2, you achieve better performance. However, this program is not available on all platforms.

    Installation Manual,

    NetWorker (Legato)

    NSR

    You can connect NetWorker using the command line clients SAVE, RECOVER and MMINFO that are 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 third-party vendors.

    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/

    All backup tools that support Backint for Oracle

    BACK

    Backint for Oracle is an interface that is supported by various third-party vendors.

    Installation Manual, Connecting to a Backint for Oracle Interface

Example

Example of a Backup Template for a Complete Data Backup

Property

Value

Name of the backup template

COM

Backup type

COMPLETE DATA

Data carrier type

FILE

Data carrier (Device/File)

DEMODB_COM

Note that if you do not enter an absolute path, then the database system uses the run directory of the database, see Run directory.

Example: C:\ProgramData\sdb\globaldata\wrk\DEMODB\DEMODB_COM

Size of data carrier

No restriction (blank or 0)

Block size

8 pages

Overwritable

Yes
Example of a Backup Template for a Log Backup

Property

Value

Name of the backup template

DEMODB_LOG

Backup type

LOG

Data carrier type

FILE

Data carrier (Device/File)

DEMODB_MYLOG

Note that i you do not enter an absolute path, then the database system uses the run directory of the database, see Run directory.

Example: C:\ProgramData\sdb\globaldata\wrk\DEMODB\DEMODB_LOG

Size of data carrier

No restriction (blank or 0)

Block size

8 pages

Overwritable

No

More Information

Database Administration, Backup Templates and Data Carriers