Backup Catalog Recovery via Metadata Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current backup solutions, such as NetBackup, face inefficiencies in disaster recovery due to slow metadata replication and unnecessary metadata replication when rebuilding catalogs at disaster recovery sites, especially when managing data from multiple primary sites.
Innovation Solution
A method where a subset of catalog metadata is stored as a separate 'sidecar' file and replicated alongside the archived data, allowing for efficient import and reconstruction of the catalog by reading the metadata from the sidecar file, rather than the entire archive.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If the entire catalog is replicated from the primary site along with the archived data, then the catalog recovery process is simplified, but unnecessary amounts of metadata are replicated and the recovery process becomes inefficient
Solution Approach 1:
The patent segments the catalog into two distinct parts: archived data and associated metadata. By separating these components and replicating only the metadata (not the entire catalog), the system eliminates unnecessary data replication while simplifying the recovery process at the disaster recovery site.
Solution Approach 2:
The patent extracts only the essential metadata from the complete catalog and replicates this extracted subset to the disaster recovery site. This extraction approach avoids replicating unnecessary catalog elements while maintaining the ability to efficiently recover and manage archived data.
2Reliability
If the entire catalog is replicated from the primary site, then catalog metadata is available at the disaster recovery site, but the replication bandwidth and storage requirements increase significantly
Solution Approach 1:
The patent extracts only the metadata portion from the complete catalog, replicating only this essential subset to the disaster recovery site. This extraction eliminates the need to replicate the entire catalog, significantly reducing replication data volume while ensuring catalog metadata availability for disaster recovery operations.
3Adaptability or versatility
If the disaster recovery site maintains archived data from multiple primary sites, then disaster recovery coverage is improved, but managing multiple sets of archived data with a single backup solution becomes complex
Solution Approach 1:
The patent segments the catalog management function by separating archived data from its associated metadata. Each disaster recovery site receives only the metadata needed for its specific archived data, enabling simplified management of multiple primary sites without requiring complex coordination between sites.
Solution Approach 2:
The patent applies local quality by providing each disaster recovery site with only the specific metadata relevant to its archived data, rather than a universal complete catalog. This localized approach simplifies management complexity while maintaining adaptability across multiple sites.
Data Source
AI summary
A method, system, and computer-readable storage medium are disclosed for recovering a backup catalog from replicated data. A set of catalog metadata may be stored in a metadata object on a first storage device. The set of catalog metadata may describe a plurality of files stored in an archive. The metadata object and the archive may be copied to a second storage device, thereby generating a replicated metadata object and a replicated archive on the second storage device. The set of catalog metadata may be imported from the replicated metadata object into a destination backup catalog. The destination backup catalog describes the plurality of files stored in the replicated archive.