The Makers of FDR®

  • FDRPASVM...Non-Disruptive
  • Migration of z/VM and
  • Linux on z Systems Volumes

FDRDRP Introduction

Enhanced z/OS Disaster Recovery for ABR (FDRINC) DASD Volume Restores

FDRDRP reduces the overall disaster recovery time for your z/OS system by enhancing the ABR (FDRINC) full-volume reconstruct process.

FDRDRP co-ordinates multiple FDRINC volume restore tasks in order to minimize tape contention and reduce delays caused by excessive (and unnecessary) tape rewinds and dismounts.

With FDRDRP you can recover your z/OS system in a much shorter space of time, using your existing FDRINC backups, and without having to change your backup procedures or JCL.

Why do I Need FDRDRP?
If you’re creating full and incremental backups with FDRINC, the likelihood is that you are creating lots of individual backup files each day.

To achieve optimum usage of each backup tape, you’re probably using “tape stacking” to put those individual FDRINC backups onto one (or maybe just a handful) of high capacity tapes.

In the simplified example below, the FULL backups of disks PROD01, PROD02 and PROD03 have all been written onto one tape (volser 111111), and all of the Monday incrementals for the same disks have been written onto another tape (volser 222222).

Weekend FULL Backups Monday INCREMENTAL Backups


Unfortunately, when running multiple concurrent disk restores during a Disaster Recovery (test or real), FDRINC would experience heavy tape contention, as multiple volume recovery tasks for volumes PROD01, PROD02 and PROD03 all fight to gain concurrent access to the same physical tape(s).
  • By automatically co-ordinating multiple concurrent FDRINC volume recoveries, FDRDRP reduces this tape contention, allowing the recovery to be done is a much shorter window.

  • FDRDRP achieves this by passing tapes between multiple FDRINC restore tasks, and by ensuring that the input tapes are mounted a minimum number of times – often only once.

  • By reducing the unnecessary tape delays (caused by rewinds, dismounts and re-mounts) savings of up to 80% have been achieved when compared to a standard FDRINC recovery.

See the TECH page for a more detailed description on how FDRDRP addresses the problem.

No Need To Change Your Backup Procedures
The key benefit of FDRDRP is that it does not require you to make any changes to your existing FDRINC backup procedures. This means you can:
  • Continue to enjoy the benefits of a reduced backup window and minimized application downtime achieved when taking full and incremental backups with FDRINC.

  • Continue getting optimum benefit from your high-capacity tapes by “stacking” your FDRINC backups onto fewer tapes.
And, when you do a Disaster Recovery (test or real):
  • You can reduce by up to 80% the amount of time it takes to complete the recovery.

Other Disaster Recovery Tools
In addition to FDRDRP described above, the FDR Storage Management System also includes a range of other tools that can help you prepare for and implement your Disaster Recovery strategy.

  FDRINC – Volume Incremental Backup
FDRINC can reduce your daily backup times by backing up only the data sets that have changed since the last backup. The powerful volume reconstruct process can restore entire DASD volumes from your incremental backups.

For more information, see the FDRINC section.

  FDRAPPL – High-Speed Application Backup
FDRAPPL can backup all the data sets from a single application, even when they are spread across many disk volumes. You can then restore either the whole application, or individual data sets, either to their original locations or to new disks.

For more information, see the FDRAPPL section.

  FDRERASE – Secure Data Erasure
FDRERASE can quickly and easily erase the data you’ve restored during your Disaster Recovery test (or real disaster recovery), ensuring that no residual data is left behind for other people to access.

For more information, see the FDRERASE section.

For more introductory information on FDRDRP, see the Product Portfolio Sheet

For more technical detail on FDRDRP, see the Tech Detail section.

return to top