Decoupling Backup Indexing from Snapshot Windows
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy indexing processes for snapshots are slow and occur during backup windows, leading to failed service level agreements and a lower customer experience due to increased backup times.
Innovation Solution
Implementing save set indexing outside of backup windows by creating snapshots without indexing during the backup window, and indexing later using advanced methods, allowing the process to take advantage of intelligent indexing options and technological advancements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If indexing is performed during backup windows using legacy processes, then the backup operation can identify and catalog save set contents, but the backup time is significantly increased leading to failed service level agreements
Solution Approach 1:
The patent applies preliminary action by creating snapshots before the backup window begins, so that the save set state is captured in advance. This allows the backup operation to work with pre-captured snapshots rather than performing both snapshot creation and indexing during the backup window, thereby reducing backup time while still achieving complete save set identification.
Solution Approach 2:
The patent segments the backup process into distinct phases: snapshot creation occurs outside the backup window, while indexing and cataloging occur during the backup window using the pre-created snapshots. This segmentation allows these operations to be performed in parallel rather than sequentially during the backup window, significantly reducing overall backup time.
2Reliability
If legacy indexing processes are used during backup windows, then save sets can be cataloged for restoration, but service level agreements are failed due to excessive backup duration
Solution Approach 1:
Snapshots are created in advance before the backup window, ensuring that the save set state is captured and preserved. This preliminary action guarantees restoration capability is maintained while allowing the backup operation to proceed more efficiently by working with pre-captured data rather than performing snapshot creation during the backup window.
Solution Approach 2:
The patent enables continuous backup operations by creating snapshots outside the backup window and then performing indexing during the backup window. This continuous approach ensures that backup operations can be performed frequently and reliably without being bottlenecked by the time-consuming legacy indexing process, thereby improving both reliability and productivity.
3Ease of operation
If snapshots are created with immediate indexing, then save sets are fully cataloged for restoration, but backup time increases reducing customer satisfaction
Solution Approach 1:
Snapshots are created in advance before the backup window begins, ensuring that save sets are captured and ready for restoration. This preliminary snapshot creation maintains restoration readiness while decoupling it from the time-consuming indexing operation, allowing indexing to occur during the backup window without extending the overall backup time.
Solution Approach 2:
The patent segments snapshot creation and indexing into separate operations performed at different times. Snapshots are created outside the backup window for immediate restoration readiness, while indexing is performed during the backup window using the pre-created snapshots. This segmentation eliminates the sequential dependency that previously extended backup time, improving customer satisfaction while maintaining ease of operation.
Data Source
AI summary
Save set indexing outside of backup windows is described. A system creates a snapshot of a save set without creating an index of the save set. The system creates the index of the save set in response to creating the snapshot of the save set.