Bucket Snapshot Metafile for Instant Object Version Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional object storage products do not provide native support for bucket-level snapshots, placing the burden of backup and data recovery on client applications, and existing snapshot restoration methods are not instantaneous and fail to recover deleted object versions.
Innovation Solution
A storage system creates bucket-level snapshots by adding a snapshot entry with an identifier and time indicator to a metafile, protecting object versions at a specific point in time, and performs background restoration to make the process instantaneous and recover deleted versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional object storage products are used without native bucket-level snapshot support, then device complexity is reduced, but data protection capability and ease of operation deteriorate as clients must manually traverse all objects to perform backup and recovery
Solution Approach 1:
The patent segments the bucket into versioned objects with time indicators, allowing snapshots to capture state at specific points in time. Each object version is independently tracked with its creation time, enabling selective protection and restoration without requiring manual traversal of all objects.
Solution Approach 2:
The system performs preliminary action by automatically creating snapshots at specified time points before deletions or modifications occur. The snapshot metafile is updated in advance to record the state of all objects at a given time, so that when restoration is needed, the data is already prepared and can be restored instantly without manual intervention.
2Productivity
If client applications manually traverse all objects to perform backup and recovery, then device complexity is reduced, but productivity and loss of time increase due to manual operations required
Solution Approach 1:
The storage system performs self-service by automatically managing snapshots without client intervention. When a snapshot is created, the system automatically records all object versions and their time indicators in the snapshot metafile. During restoration, the system automatically identifies and restores the appropriate versions based on the snapshot time, eliminating the need for clients to manually traverse and select objects.
Solution Approach 2:
The system uses feedback from time indicators associated with each object version to automatically determine which versions should be restored. The snapshot metafile provides feedback about the state of the bucket at a given time, enabling the system to automatically identify matching object versions and perform restoration without manual guidance from the client.
3Reliability
If existing snapshot restoration methods are used, then device complexity is reduced, but reliability deteriorates as restoration is not instantaneous and deleted object versions cannot be recovered
Solution Approach 1:
The system performs preliminary action by continuously maintaining the snapshot metafile with time indicators for all object versions. When restoration is needed, the data is already prepared and indexed, allowing instantaneous restoration without the time-consuming process of manually traversing and reconstructing the bucket state from scratch.
Solution Approach 2:
The patent uses copying by creating a snapshot metafile that copies the state information of all objects at a given time. This metafile serves as a reference copy that can be quickly accessed during restoration, eliminating the need to re-traverse and re-construct the entire bucket state, thereby achieving instantaneous restoration.
4Reliability
If bucket-level snapshots are implemented with automatic protection, then data protection capability is improved, but device complexity increases due to snapshot metafile management and version tracking
Solution Approach 1:
The system achieves universality by using a single snapshot metafile structure that serves multiple functions: recording snapshot creation times, tracking object version states, enabling instantaneous restoration, and providing automatic protection. This unified approach consolidates what would otherwise require multiple separate mechanisms into one efficient system.
Solution Approach 2:
The patent applies parameter changes by using time indicators as the key parameter for tracking and protecting object versions. By changing the focus from manual object traversal to time-based parameter comparison, the system achieves automatic protection with minimal complexity. The snapshot metafile stores and compares time parameters to automatically determine which versions need protection and restoration.
Data Source
AI summary
Systems and methods for creation of bucket-level snapshots and snapshot ownership determination are provided. In one example, a storage system maintains a bucket containing multiple objects each having one or more object versions. A snapshot of the bucket may be efficiently created to protect object versions in the bucket at a specific point in time by simply adding an entry, containing information regarding a snapshot identifier (ID) and a snapshot creation time indicator, to a snapshot metafile. Object-modifying operations may be hooked to internally modify them while making it appear to the client the operation has been successfully completed. For example, before deletion of a particular object, an “Is-Object-Protected” check may be performed based on time indicators of the one or more object versions and respective snapshot creation time indicators. When the particular object is protected, it may be subsequently hidden from the client but maintained as an internal version.