Data Recovery and High Availability

High availability disaster recovery overview

When performing the START HADR, STOP HADR, or TAKEOVER HADR commands, the 8 corresponding error codes might be generated: SQL01767N, SQL01769N, 8or SQL01770N with a reason code of 98. The reason code indicates that there 8is no installed license for HADR on the server where the command was run. 8To correct the problem, install a valid HADR license using db2licm or install a version of the server that contains a valid HADR 8license as part of its distribution.

Cross-platform backup and restore support

DB2 Universal Database (UDB) supports cross-platform backup 7and restore operations. You can restore databases created on a DB2 UDB Version 78 32-bit Windows platform to a DB2 UDB Version 8 64-bit Windows platform, 7or the reverse. You can restore databases created on a DB2 UDB Version 78 32-bit Linux x86 platform to a DB2 UDB Version 8 64-bit Linux x86-64 or 7IA64 platform, or the reverse. You can restore databases created on DB2 UDB Version 78 AIX, HP-UX, Linux PPC, Linux zSeries, or the Solaris Operating Environment 7platforms, in 32-bit or 64-bit, to DB2 UDB Version 8 AIX, HP-UX, Linux PPC, Linux zSeries, or Solaris Operating Environment 7platforms (32-bit or 64-bit).

Backing up to tape (Linux)

The maximum block size limit for 3480 and 3490 tape devices on Linux is 61 440 7bytes

Tivoli Storage Manager

When calling the BACKUP DATABASE or RESTORE DATABASE commands, you can 7specify that you want to use the Tivoli Storage Manager (TSM) product to manage 7database or table space backup or restore operation. The minimum required 7level of TSM client API is Version 4.2.0, except on the following:

7
• 64-bit Solaris systems which require TSM client API Version 4.2.1.
7
• 64-bit Windows NT operating systems which require TSM client 7API Version 5.1.
7
• 732-bit Linux for iSeries and pSeries^(R) which requires at minimum TSM client 7API Version 5.1.57
7
• 764-bit Linux for iSeries and pSeries which requires at minimum TSM client 7API Version 5.2.27
7
• 64-bit Linux on AMD Opteron systems which require a minimum TSM client API Version 75.2.0.
7
• Linux for zSeries 64-bit which requires a minimum TSM client API 7Version 5.2.2.

Value restrictions for the HADR local host and local service parameters

When specifying values for the high availability disaster recovery (HADR) 7local host and local service parameters (HADR_LOCAL_SVC and HADR_REMOTE_SVC) 7while preparing an update database configuration command 7, the values must be ports that are not in use for any other service. If the 7parameters are being configured using the Linux or UNIX command line, the values should be also 7set in the /etc/services file.

Additional system requirements for high availability disaster recovery

If you create a table space on the primary database and log replay fails 7on the standby database because the containers are not available, the primary 7database does not receive an error message stating that the log replay failed.

To check for log replay errors, you must monitor the db2diag.log and the 7administration log on the standby database when you are creating new table 7spaces.

If a takeover operation occurs, the new table space that you created is 7not available on the new primary database. To recover from this situation, 7restore the table space on the new primary database from a backup image.

In the following example, table space MY_TABLESPACE is restored on database 7MY_DATABASE before it is used as the new primary database:

7
1. db2 connect to my_database
7
2. db2 list tablespaces show detail 7 7
   Note:
   7
   Run the db2 list tablespaces show detail command to show the 7status of all table spaces and to obtain the table space ID number required 7for Step 5.
7
3. db2 stop hadr on database my_database
7
4. db2 "restore database my_database tablespace (my_tablespace) online 7redirect"
7
5. db2 "set tablespace containers for my_tablespace_ID_# ignore rollforward 7container operations using (path '/my_new_container_path/')"
7
6. db2 "restore database my_database continue"
7
7. db2 rollforward database my_database to end of logs and stop tablespace 7"(my_tablespace)"
7
8. db2 start hadr on database my_database as primary

Non-replicated operations for high availability disaster recovery

Version 8.2 documentation states:

BLOBs and CLOBs are not replicated; however, the space for them will be 7allocated on the standby database.

The statement should read as follows:

Non-logged BLOBs and CLOBs are not replicated; however, the space for them 7will be allocated on the standby database.

HADR does not support raw logs

High availability disaster recovery (HADR) does not support the use of 7raw I/O (direct disk access) for database log files. If HADR is started with 7the START HADR command, or if the database is restarted with HADR configured, 7and raw logs are detected, the associated command will fail with SQL1768N 7reason code "9".