• Table of contents
• Database Mirroring on remote site
  • Introduction
  • Full Database Backup + Transaction Logs
  • Test Tools

Database Mirroring on remote site¶

Introduction¶

To mirror production database(s) to remote site, there are a number of approaches:

1. Use (full) database backup
2. Use (full + incremental) database backup
3. Use (full + delta) database backup
4. Use (full + incremental + delta) database backup - not recommended because it is too complex
5. Use (full database backup + transaction logs)

the approach 1-4 are described in Using DB2 incremental backup

The following sections will describe how the last approach actually works. Before that, let's do a compare:

Full Database Backup + Transaction Logs¶

Below diagram describes how this approach works:

Sample steps:

1. Like any other approaches, you must perform a full database backup (either offline or online)
   • e.g.:
     

     $ db2 backup db prod_db online

2. Use the rsync command to do an one way incremental sync from remote (production) site to standby site.
   • e.g.:
     

     $ rsync -var --delete db2inst1@db-prod:/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/ /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR

3. Execute the rollfoward on the standby database: (do not include the complete option)
   • e.g.:
     

     $ db2 rollforward db prod_db to end of logs

4. If want to bring up the standby database, just execute this command (change the database alias):
   

   $ db2 rollforward db prod_db complete

The biggest advantage of this approach is there's little or no need to revise current backup strategies, however, the mirror database cannot be used until the rollforward process is terminated.

Test Tools¶