Backing up DB2 resources

Before you back up DB2 resources, review the following:

Note:

You cannot back up databases to devices that are attached to a computer on which the Remote Media Agent for Linux Servers is installed.

To back up DB2 resources

  1. On the navigation bar, click the arrow next to Backup.

  2. Click New Backup Job.

  3. In the backup selection list, under the Favorite Resources node, expand the Windows Systems node.

  4. Expand the DB2 server that you want to back up.

    If the DB2 server is not listed under Favorite Resources, then you can add it.

    See About the Favorite Resources node in the backup selections list.

  5. Select the following objects as appropriate:

    Instance

    Select an instance to back up all of the DB2 databases that it contains.

    Database

    Select a database to back up all of the partitions that it contains.

    During a file system backup, online DB2 database files that are included in the selecton list are not automatically excluded. You must manually exclude the datafiles of an online DB2 database from the selection list.

    Partition

    Select a partition to back up all of the tablespaces and log folders that it contains.

    Tablespace

    Select all tablespaces or individual tablespaces to back up.

  6. On the Properties pane, under Settings, click DB2.

  7. Complete the appropriate options as follows:

    Backup method

    Select one of the following backup methods:

    • Full - Back up selections. Select this method to perform a full backup of DB2 selections.

    • Differential - Back up changes since last full. Select this method to back up all database changes since the last full backup.

    • Incremental - Back up changes since last full or incremental. Select this method to back up all database changes since the last full or incremental backup.

    Perform the backup offline

    Check Perform the backup offline to have Backup Exec take the database offline before you start the backup job. Backup Exec brings the database online after the backup job is complete.

    If circular logging is enabled for the database, then you must select this option; otherwise the backup job fails.

    Quiesce the database before offline backup

    Check Quiesce the database before offline backup to have Backup Exec force users off the database before it brings the database offline for the backup job. Users who are not actively running databases tasks are forced off the database. Users who are running database tasks can complete their current task before being forced off.

  8. To configure multiple data streams for backup, under Destination, click Device and Media.

  9. Complete the appropriate options as follows:

    Maximum number of devices to use for resources that support multiple data streams

    Enter the maximum number of devices that the backup job can use.

    When you run a DB2 database backup job, Symantec recommends that the number of backup devices that are available for the job is at least equal to the number of streams. If archive logging is enabled for the database, an additional backup device must be available.

    If you specify more than one device, you must choose one of the following items as a destination device for the backup job:

    • A device pool.

    • A backup-to-disk folder that has at least two concurrent operations enabled.

    See Creating a backup-to-disk folder.

    This feature is not available for DBA-initiated jobs.

    Minimum number of devices, terminate job if fewer devices are available

    Enter the minimum number of devices that the job can use.

    If the job cannot acquire the minimum number of devices, the job fails.

    This feature is not available for DBA-initiated jobs.

  10. Complete the remaining backup job properties as necessary.

More Information

Creating a backup job by setting job properties

Configuring DBA-initiated job settings for DB2

Setting application defaults for DB2