Database Mirroring (DB2) on remote site » History » Version 5
chin-yeh, 03/21/2012 05:58 PM
1 | 1 | chin-yeh | {{toc}} |
---|---|---|---|
2 | |||
3 | 2 | chin-yeh | h1. Database Mirroring on remote site |
4 | |||
5 | h2. Introduction |
||
6 | |||
7 | 3 | chin-yeh | To mirror production database(s) to remote site, there are a number of approaches: |
8 | # Use <code>(full)</code> database backup |
||
9 | # Use <code>(full + incremental)</code> database backup |
||
10 | # Use <code>(full + delta)</code> database backup |
||
11 | # Use <code>(full + incremental + delta)</code> database backup - _not recommended because it is too complex_ |
||
12 | # Use <code>(full database backup + transaction logs)</code> |
||
13 | |||
14 | > the approach 1-4 are described in "Using DB2 incremental backup":http://www.ibm.com/developerworks/data/library/techarticle/dm-0910db2incrementalbackup/ |
||
15 | |||
16 | The following sections will describe how the last approach actually works. Before that, let's do a compare: |
||
17 | 4 | chin-yeh | |
18 | 3 | chin-yeh | !database_mirroring_approach.png! |
19 | 4 | chin-yeh | |
20 | h2. Full Database Backup + Transaction Logs |
||
21 | 5 | chin-yeh | |
22 | Below diagram describes how this approach works: |
||
23 | |||
24 | !full_transaction_logs_approach.png! |