Settings › Configure the Copy Recovery Point Settings › Copy Recovery Points - Example Scenarios

Copy Recovery Points - Example Scenarios

The following example scenarios are provided to give you a better understanding of how the various options can affect your scheduled copying of recovery points.

For this example, assume that you configured your Arcserve UDP Agent (Windows) backup schedule as follows:

• Full Backup - Every 7 days
• Incremental Backup - Every 1 hour
• Verify Backup - Every 3 days

and assume:

• First backup is on Day #1 at 5:00PM (by default, the first backup is always a Full Backup)
• First Incremental Backup will be on Day #1 at 6:00PM (and every hour after)
• Recovery Points retention count is set to 31 (default number)
• Location "D" is configured as the copy destination

Scenario #1

For this scenario, the Copy Recovery Point settings are as follows:

• Copy after 4 backups
• Retain 1 recovery point

  Result:

  • At 8:00PM (after the 4th backup), the scheduled copy job will run and consolidate all 4 recovery points into a single recovery point and store it at destination D.
  • At 12:00 midnight (after the 8th backup), the next scheduled copy job will run and consolidate all 8 recovery points into a single recovery point and store it at destination D.

    The previous recovery point is removed from destination D because the setting is to retain only 1 recovery point at the destination.

Scenario #2

For this scenario, the Copy Recovery Point settings are as follows:

• Copy after 4 backups
• Retain 4 recovery points

  Result:

  • At 8:00PM (after the 4th backup), the scheduled copy job will run and consolidate all 4 recovery points into a single recovery point (Recovery Point #1) and store it at destination D.
  • At 12:00 midnight (after the 8th backup), the next scheduled copy job will run to create Recovery Point #2 and store it at destination D.
  • At 4:00AM on Day #2 (after the 12th backup), the next scheduled copy job will run to create Recovery Point #3 and store it at destination D.
  • At 8:00AM on Day #2 (after the 16th backup), the next scheduled copy job will run to create Recovery Point #4 and store it at destination D.
  • At 12:00 noon on Day #2 (after the 20th backup), the next scheduled copy job will run. A new recovery point will be created and the first recovery point (created after the 8:00PM backup on previous day) is removed from destination D, because the setting is to retain only 4 recovery points at the destination.

Scenario #3

For this scenario, the Copy Recovery Point settings are as follows:

• Copy after 1 backup
• Retain 4 recovery points

  Result:

  • At 5:00PM (after the 1st backup), the scheduled copy job will run to create a single recovery point (Recovery Point #1) and store it at destination D.
  • At 6:00PM (after the 2nd backup), the next scheduled copy job will run to create Recovery Point #2 and store it at destination D.
  • At 7:00PM (after the 3rd backup), the next scheduled copy job will run to create Recovery Point #3 and store it at destination D.
  • At 8:00PM (after the 4th backup), the next scheduled copy job will run to create Recovery Point #4 and store it at destination D.
  • At 9:00PM (after the 5th backup), the next scheduled copy job will run. A new recovery point will be created and the first recovery point (created after the 5:00PM backup) is removed from destination D, because the setting is to retain only 4 recovery points at the destination.