• Active Support: DS-Client supports backup / restore of DB2 server.

• Passive Support: Backup / restore tests have not been performed on these platforms, but there should not be any technical limitations.

• No Vendor Support: DB2 client used by DS-Client to backup / restore DB2 server is not supported by vendor.

• The DB Administrator / Backup Operator must catalog the remote node and database name before creating a new backup set. You cannot browse the database(s) for names, therefore you must have the exact name. Restores must also catalog the remote node and database name prior to running the (restore) process.

• The credentials used for backup / restore of the DB2 database must have the SYSADM, SYSCTRL, or SYSMAINT authority.

• The account used to connect to the DB2 Client Instance must exist on the DS-Client computer. This is the user specified in the “Ask for database credentials” of the DB2 backup set (Backup Set Properties > Connection Options).

• DS-Client should be running on Red Hat ES/AS Linux 5/6, or SUSE Linux Enterprise 11.

• DB2 Client should be installed on the machine running the DS-Client. This DB2 Client must be the same version as the DB2 Servers being backed up.

• Specify the DB2 Client library directory on DS-Client. This is done in the DS-Client Configuration screen’s Advanced Tab (see “Configuring the advanced settings”):

• DB2 Server should be a certified product.

• You must ensure that the TCP/IP Service name is properly represented in the DB2 instance configuration file; otherwise, you may encounter errors when creating a DB2 database backup set.

• The DB2 database must not be in use when you perform an off-line backup. Otherwise an error will be reported.

• When you create a DB2 backup set, in the Select the source for this backup set screen, specify the DB2 server hostname or type its IP address in the Path field. This must be the same as the one used in the catalog command.

• Linux DS-Client should have read and write privileges to access the transaction log directory on the DB2 database computer (for example ~db2inst1/db2inst1/NODE0000/SQL00005/SQLOGDIR/).

• Online backups are available only for databases configured with either logretain or userexit enabled on DB2 v9.7.

• Online backups are available only for databases configured with the "logarchmeth1" value set either logretain or userexit on DB2 v10.1.

• The backup set must specify that the backup is online or off-line, as determined by the DB2 database configuration settings. (DO NOT CHANGE THIS PROPERTY. If you change this DB2 configuration, make a new backup set with the new option setting.)

• It is recommended not to change the online option setting for a demand backup. If it is changed, you must make a record of the change and the date (manually on paper or other format), so that the information is available if a restore is performed.

• The DB2 database must not be in use when you perform the restore. This requirement applies to all DB2 backup sets (whether configured for online or off-line backup).

• The DB2 database must be configured for online or off-line restore. This setting must match the Backup Set Properties > Options setting that was used for the backup.

• The user ID of the calling application or process is used for client-side authorization. More details are available at the following links: