DB2 UDB integration
Data Protector
integrates with IBM DB2 Universal Database Server (DB2 Server) to back up DB2
database objects online and offline.
Available Backup Types: Full, Incremental, Delta
The basic backup unit
is a table space. Only table spaces or databases (DB2 objects) can be selected
for backup.
Prerequisites:
- For
rollforward recovery, and setting the logarchmeth1 to either User Exit or
Vendor, first back up the database offline.
- db2arch: Program that
backs up and restores DB2 log files when DB2 log archive method (logarchmeth1) is set to user exit
- libob2db2: Data
transferring (database backup and restore, log archive/retrieval when logarchmeth1 is set to vendor) module called by DB2
Server.
- Ensure
the DB2 user has appropriate authorities to perform DB2 backups and
restores (either SYSADM, SYSCTRL, or SYSMAINT).
- Required
components to configure backup:
- Instance
Name
- OS
User Name and Group/Domain
- DB2
User and Password
- DB2
instance home directory (only in a partitioned environment)
- Add
user root (UNIX only) and the DB2 user to both the Data Protector and DB2 admin user groups.
- Provide
this user in configuration and restore procedures. This user is needed by
Data Protector to start the Data Protector Inet service (Windows) or
process (UNIX).
Considerations:
- HPE
recommends that you set the log archive method (logarchmeth1) to Vendor,
because IBM DB2 has deprecated the UserExit option from the DB2 version
9.5.
- If
your existing database has the log archive method set
to UserExit and you want to change it to Vendor, then the database
recovery for the log that is backed up using the User Exit option can be
done using the below steps:
o
Restore
the database (without enabling the Roll forward recovery in the Data Protector
GUI).
o
Restore
the logs that were backed up using the User Exit program in the active log
directory.
- Set
the environment variables in the omnirc file before restoring to a DB2
database using the automatic Roll forward:
On
the DB2 client, set the following environment variables in the omnirc file:
o
OB2APPNAME=
“source_Instance_name”
o
OB2BARHOSTNAME=”Source_client_name”
o
OB2APPDATABASE=
“source_database_name”
Note: This is valid for
all DB2 log backups using the Vendor library and not required for the User-Exit
mode.
In
the omnirc file, delete the above mentioned three variables after the Roll
forward of the DB2 database.
CLI: Commandline Help
- Run
the command
util_db2 –CONFIG
DB2_instance username password [DB2 _instance_home]
The message “*RETVAL* 0” indicates successful configuration
- Run
the command to Check the configuration status after creating backup
util_db2.exe –CHKCONF
DB2_instance
Restore:
1. Data Protector
currently does not support restore of DB2 objects using DB2 CLI. You must only
use Data Protector GUI or CLI to complete these steps.
2. Databases are
restored offline.
3. Table spaces are
restored online. Only table spaces that are not being restored are available
for use.
4. A dropped table space
can only be restored from a full database backup.
5. For rollforward
recovery, the latest backup version of log files is used. To perform a
rollforward recovery using an older version of log files, first restore the
desired log files and then restore the databases/tablespaces with the
Rollforward option cleared. In a partitioned environment, connect to the
catalog node. Finally, perform a rollforward recovery using DB2 tools.
Restore Types:
When restoring a
database or table space, you can specify restore options to perform:
- Rollforward
recovery
- Version
recovery
- Restore
to a new database (database only)
- Restore
to another instance (database only)
- Restore
to another system (database only)
- Automatic
restore from incremental or delta backups
Databases are
restored offline, table spaces online
0 Comment to "Prerequisites and Must know Configure or integrate Online Database backup with IBM DB2 Universal Database Server (DB2 Server)"
Post a Comment