Browse Prior Art Database

Layered Data Recovery

IP.com Disclosure Number: IPCOM000225382D
Publication Date: 2013-Feb-12
Document File: 2 page(s) / 21K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method applied to fast replication techniques that enables increased backup speed and efficiency. The core novelty of this invention is the method for managing and layering the various “daughter” backups on top of a base mother backup, allowing the user to recover any entire backup of volA to a specific version of without having to dump the entire contents of volA during each of those timeframes.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Layered Data Recovery

With current fast replication techniques, users can only use incremental backup to back up an entire volume or specific data sets that have changed since the last incremental copy was performed. This is useful, but can still lead to elongated backups and inefficient use of tape drives because, even though only the changed tracks or data sets are copied to the target volume of the fast replication incremental step, a backup utility still dumps the entire volume or data set(s) during the backup operation. Also during restore processing, the entire volume or an individual data set can be restored, but current methods are lacking a way to incrementally restore a portion of a data set.

The disclosed invention is a method to enable increased backup speed and efficiency. The system only dumps the changed tracks that are identified during each fast replication technique incremental step, essentially performing a true incremental backup from the fast replication process to DUMP. Then, at RESTORE time, the invention allows a space management utility to layer the incremental backups together to form the complete volume or data set for the requested recovery. In addition, the invention allows the user to select versions up to a certain date, in the event that a less recent version the data needed (e.g., in cases of application-caused data corruption, where the most current backup version might have corrupted data).

Example Embodiment: A full volume dump conditioned fast replication technique incremental copy from volA to volB

1. The initial fast replication incremental copy and dump/backup works as it does in existing systems; however, this backup version is marked as the "mother" backup and given a unique data source name (DSN), which is identified in the catalog as an incremental mother backup of volB, my.dump.VOLBM.date

2. A small number of tracks on volA changes, and the system performs a fast replication technique incremental copy; it only copies these changed tra...