ISB Protocol Clone Volume Backup via Proxy Severing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data backup and recovery systems, particularly in healthcare environments using the Integrated Serverless Backup (ISB) protocol, lack the ability to perform scheduled backups, recover data at specific points in time, and conduct other replication operations efficiently, leading to challenges in maintaining data integrity and availability during system failures or disasters.
Innovation Solution
The system employs a production volume that continuously records changes, mirroring data to a clone volume and creating snapshots at various points in time, allowing for remote backup and recovery, with a proxy host and backup server facilitating replication operations by temporarily severing the connection between production and clone volumes to perform backup and snapshot creation using the ISB protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is continuously mirrored to clone volumes, then data availability is improved, but data integrity control during backup operations deteriorates
Solution Approach 1:
The system performs preliminary actions by temporarily severing the connection between production and clone volumes before backup operations begin. This ensures that no new data changes occur during the backup process, guaranteeing data integrity while maintaining continuous availability through the pre-established clone volume relationship.
Solution Approach 2:
The patent introduces a proxy host as an intermediary component that manages the connection between production and clone volumes. The proxy host controls when connections are severed and reestablished, mediating between the need for continuous data availability and the requirement for data integrity during backup operations.
2Adaptability or versatility
If snapshots are created at various points in time, then recovery flexibility is improved, but system complexity deteriorates
Solution Approach 1:
The system creates simplified copies of volume data at specific points in time through snapshots. Each snapshot is a point-in-time copy that can be independently restored, providing recovery flexibility without requiring complex backup infrastructure. The copying process is automated and managed through the proxy host, reducing operational complexity.
3Reliability
If connection between production and clone volumes is severed for backup, then backup reliability is improved, but operational continuity deteriorates
Solution Approach 1:
The system performs the connection severing as a preliminary action before backup operations begin, ensuring that the disconnection time is minimized and predictable. This allows operational planning around brief, controlled interruptions while maintaining overall operational continuity.
Solution Approach 2:
Backup operations are performed periodically with controlled connection severing, allowing the system to balance backup reliability with operational continuity. The periodic nature of the operations enables planning and minimizes impact on overall system productivity.
Data Source
AI summary
Systems and methods for performing scheduled backups and recovery of data generated by a production application operating on a MAGIC platform located on a host computer. The data is stored in a primary storage in the form of a production volume and ISB protocol is used to create a clone volume. Exemplary methods for backing up a clone volume to a backup storage include receiving a backup command from a backup server, sending a split command to a host computer to initiate splitting of a production volume and a clone volume using ISB protocol, receiving an identification of the clone volume, initiating the clone volume for surfacing and mounting, and initiating a backup of the surfaced and mounted clone volume to a backup storage.