Best practice in using removable disk cartridges (RDX) as a storage device with Veritas System Recovery

Article: 100005976
Last Published: 2018-04-09
Ratings: 0 0
Product(s): System Recovery

Problem

Best practice in using removable disk cartridges (RDX) as a storage device with Veritas System Recovery (VSR).  These drives are also known as RDX 1000 and RD1000.

Cause

VSR atempts to automatically remove older recovery point images to stay within the retention limit specified within the backup job setting:  "Limit the number of recovery point sets saved for this backup."  A recovery point set consists of a Base (aka Full) backup (.v2i file extension) plus all Incrementals (.iv2i file extension) occurring after it until the next Base backup runs.

1.  Depending upon the type of backup job being used, VSR, by design, needs to have enough room on the RDX cartridge to create one additional base or Independant backup beyond the value of the retention period. Once this threshold has been met, VSR will delete the oldest recovery point set.  VSR determines the earlist recovery point image based upon information stored in the backup history files (i.e. *.PQH files).

Example: If the default value of three is kept for the backup job setting, "Limit the number of recovery point sets saved for this backup," then there needs to be enough space on the RDX cartridge for a fourth set. If the history file becomes corrupt or has been cleared/deleted before reaching this fourth set, the recovery points stored on the RDX cartridge(s), created prior to the current history file was made will become 'Orphaned' and will need to be manually removed from the cartridge(s).

2. VSR, by design, executes the command to remove older recovery point sets shortly after the successful creation of this, 'one additional,' base image.  If the earliest recovery point set (i.e The oldest baseline and its incremental updates) scheduled to be removed is not on the RDX cartridge currently inserted, VSR will delete that recvoery point set after the RDX cartridge containing them is reinserted and a new base backup is completed on the cartridge.

NOTE: This applies to System Recovery 2013 R2 and newer.  With System Recovery 2013 and earlier, if the cartridge containing the oldest recovery point set is not currently available when the recovery point set limit is exceeded, the old recovery point set will be orphaned on the cartridge and will not be deleted at a later time when that cartridge is reinserted into the RDX drive. Manual intervention is required by the user to delete the oprhaned recovery point sets.

3.  A new base backup is always created the first time a backup runs after a different RDX cartridge is inserted, even if an incremental backup was originally scheduled.

Solution

There are two possible approaches to using RDX cartridges with VSR:

  • Single job approach
  • Multiple job approach

Single job approach

1.   The number of recovery sets to retain should be a multiple of the number of cartridges used in rotation
eg. If available cartridges = 2, the number of recovery point sets to retain could be 2, 4, 6 etc, depending upon how many recovery point sets can be accommodated on a single cartridge.  Keep in mind there needs to be room for the number of recovery point sets specified plus one additional base backup since VSR does not delete the oldest backup once the recovery point set limit is reached until a new base backup is created. 

2.   Create only one backup job (with recovery point set) that will take only incremental backups. Base backups will be taken as soon as the cartridge is rotated.  Backup job schedule should be configured to create base backups as infrequently as possible (i.e. Yearly). 

3.   The path specified for the backup destination should exist on each RDX cartridge

 

Usage scenarios:

Scenario 1:
One backup per day, 1 cartridge for Monday through Thursday and another one for Friday through Sunday.  
Limit the number of recovery point sets saved for this backup = 2 
Number of cartridges = 2
Each cartridge needs room for 2 base backups plus all incrementals associated with oldest base backup.

 Day

Cartridge 1 

 Cartridge 2

 Remarks

 Mon

 1.v2i

 -

Base backup 

 Tue

 1_001.iv2i

 -

 Incremental backup

 Wed

 1_002.iv2i

 -

 Incremental backup

 Thu

 1_003.iv2i

 -

 Incremental backup

 Fri

-

 2.v2i

Cartridge rotated prior to scheduled backup start time.
Base backup created due to new cartridge being inserted.

 Sat

-

2_001.iv2i

Incremental backup

 Sun

-

2_002.iv2i

Incremental backup 

 Mon

3.v2i 

-

Cartridge rotated prior to scheduled backup start time.  
Base backup created due to new cartridge being inserted.  
Recovery point set limit of 2 is exceeded.
Recovery point set 1 gets deleted after base backup 3.v2i is created 

 Tue

3_001.iv2i

-

Incremental backup 

 Wed

3_002.iv2i

-

Incremental backup 

 Thu

3_003.iv2i

-

Incremental backup 

Fri 

-

4.v2i

Cartridge rotated prior to scheduled backup start time.
  Base backup created due to new cartridge being inserted.
Recovery point set limit of 2 is exceeded.
  Recovery point set 2 gets deleted after base backup 4.v2i is created

 Sat

-

4_001.iv2i

Incremental backup

 Sun

-

4_002.iv2i

Incremental backup

 

Scenario 2:
One base and one incremental per day, rotate cartridge every weekday. 
No backups Saturday or Sunday
Limit the number of recovery point sets saved for this backup = 4
Number of cartridges = 2
Each cartridge needs room for 3 base backups plus all incrementals associated with oldest 2 base backups.

 Day

Cartridge 1

 Cartridge 2

 Remarks

 Mon

1.v2i
1_001.iv2i

Base and Incremental recovery point set 1 run to cartridge

 Tue

 -

2.v2i
2_001.iv2i 

Cartridge 2 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 2 run to cartridge

 Wed

 3.v2i
3_001.iv2i

Cartridge 1 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 3 run to cartridge
Recovery point set 1 remains on cartridge as set limit of 4 has not been exceeded.
Cartridge contains sets 1 and 3 after backups for day are completed.

 Thu

 -

4.v2i
4_001.iv2i 

Cartridge 2 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 4 run to cartridge
Recovery point set 2 remains on cartridge as set limit of 4 has not been exceeded.
Cartridge contains sets 2 and 4 after backups for day are completed.

 Fri

 5.v2i
5_001.iv2i

Cartridge 1 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 5 run to cartridge
After 5.v2i is created, set limit of 4 has been exceeded.
Recovery point set 1 is deleted from cartridge.
Cartridge contains sets 3 and 5 after backups for day are completed.

 Sat

 -

-

No backups

 Sun

 -

No backups

 Mon

 -

6.v2i
6_001.iv2i 

Cartridge 2 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 6 run to cartridge
After 6.v2i is created, set limit of 4 has been exceeded.
Recovery point set 2 is deleted from cartridge.
Cartridge contains sets 4 and 6 after backups for day are completed.

 Tue

 7.v2i
7_001.iv2i

Cartridge 1 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 7 run to cartridge
After 7.v2i is created, set limit of 4 has been exceeded.
Recovery point set 3 is deleted from cartridge.
Cartridge contains sets 5 and 7 after backups for day are completed.

 Wed

 -

8.v2i
8_001.iv2i  

Cartridge 2 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 8 run to cartridge
After 8.v2i is created, set limit of 4 has been exceeded.
Recovery point set 4 is deleted from cartridge
Cartridge contains sets 6 and 8 after backups for day are completed.

 Thu

 9.v2i
9_001.iv2i

Cartridge 1 rotated into drive prior to first scheduled backup of the day
Base and Incremental for recovery point set 9 run to cartridge
After 9.v2i is created, set limit of 4 has been exceeded.
Recovery point set 5 is deleted from cartridge.
Cartridge contains sets 7 and 9 after backups for day are completed.

 Fri

 -

10.v2i
10_001.iv2i  

Cartridge 2 rotated into drive prior to first scheduled backup of the day
Base and Incremental recovery point set 10 run to cartridge
After 10.v2i is created, set limit of 4 has been exceeded.
Recovery point set 6 is deleted from cartridge.
Cartridge contains sets 8 and 10 after backups for day are completed.

 Sat

 -

No backups

 Sun

 -

No backups

 

Multiple job approach:

  • Can be used if only base (Full) backups are desired.  Recovery point set jobs cannot be created in this manner as each source drive can only have one recovery point set job defined for it.
  • Use the RDX drive as a primary removable / swappable storage device if the capacity of all cartridges involved in the rotation cycle can contain two or more full backups.
  • Do not reuse RDX cartridge(s) for a new client's cartridge rotation cycle until all the cartridge(s) has been reformatted.
  • Create a seperate independant backup job (not a recovery point set) per each RDX cartridge to be used in the client's rotation cycle. By doing this, each backup job will have its own history file per drive selected to maintain retention.

Example: If a VSR client has three RDX cartridges in its rotation cycle, with each cartridge having the capacity that can contain three full backup images, the retention period would then be set to two on each job providing a one week of recovery window as shown below: 

 Cartridge #  Day's of the Week this cartridge will be used Generic job name
 1  Monday & Wednesday  MW_Independent_full
 2  Tuesday & Thursday  TuTh_Independent_full
 3  Friday  Fri_Independent_full

 Expected image and retention site schedule:

Sunday Monday Tuesday Wednesday Thursday Friday Saturday
 

Cartridge#1

Creates:

-- *_drive001.v2i

Cartridge#2

Creates:

---- *_drive002.v2i

Cartridge#1

Creates:

-- -- *_drive003.v2i

Cartridge#2

Creates:

--  *_drive004.v2i

Cartridge#3

Creates:

-- *_drive005.v2i

 
 

Cartridge#1

Creates:

-- *_drive006.v2i

Remove

-- *_drive001.v2i

Cartridge#2

Creates:

-- *_drive007.v2i

Remove

-- *_drive002.v2i

Cartridge#1

Creates:

-- *_drive008.v2i

Remove

-- *_drive003.v2i

Cartridge#2

Creates:

-- *_drive009.v2i

Remove

-- *_drive004.v2i

Cartridge#3

Creates:

-- *_drive010.v2i

 
   

Cartridge#1

Creates:

-- *_drive011.v2i

Remove

-- *_drive006.v2i

 

Cartridge#2

Creates:

-- *_drive012.v2i

Remove

-- *_drive007.v2i

 

Cartridge#1

Creates:

-- *_drive013.v2i

Remove

-- *_drive008.v2i

 

Cartridge#2

Creates:

-- *_drive014.v2i

Remove

-- *_drive009.v2i

 

Cartridge#3

Creates:

-- *_drive015.v2i

Remove

-- *_drive005.v2i

 

 

 

Applies To

Windows based client systems.

Was this content helpful?