Successful System Recovery using Ignite-UX

Retention
Typically, you should retain recovery archives using similar retention periods as those used for your
application backups. This is because there may be a time delay between finding a problem and
needing to recover a system to a known state.
Retention periods are best explained with the following example.
Example
– Weekly recovery archives may have a retention period of 4 weeks.
– Every 4
th
recovery archive (monthly) may have a retention period of 6 months.
– Every 12
th
(quarterly) recovery archive may have a retention period of one year.
– Every 24
th
(semi-annual) recovery archive may have a retention period of two years.
To clarify this example further,
Table 2 provides a pictorial view of these retention periods.
Table 2
Week # 1 month 6 months 1 year 2 years
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
This example provides for multiple generations of recovery archives. At the end of 24 weeks, you
have recovery archives that are 1-, 2-, 3-, 4-, 8-, 12-, 16-, 20-, and 24-weeks old. Continuing the
retention cycle forward another 24 weeks, you have recovery archives that are 1-, 2-, 3-, 4-, 8-, 12-
, 16-, 20-, 24-, 36- and 48-weeks old (excluding any ad hoc recovery archives). Older
5