ISB Protocol SAN Copy Sessions for Scheduled Backup
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.
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 recovery functions using the ISB protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If basic backup operations are performed using ISB protocol, then data backup capability is provided, but scheduled backups and point-in-time recovery capabilities are lacking
Solution Approach 1:
The system segments backup operations into distinct types (scheduled backups, point-in-time recovery, replication operations) that can be independently configured and executed. This allows the system to provide basic backup operations while also enabling advanced recovery capabilities through separate, specialized processes.
Solution Approach 2:
The system implements dynamic backup scheduling that allows administrators to configure and modify backup operations at different points in time. Scheduled backups can be set to execute automatically at specified intervals, and point-in-time recovery allows restoration to specific historical moments, making the backup system adaptable to varying operational requirements.
2Reliability
If production volume continuously records changes and mirrors to clone volume, then data availability is maintained, but connection management complexity increases
Solution Approach 1:
The system introduces a proxy host as an intermediary between the production volume and clone volume. This proxy host manages the connections and coordinate the mirroring operations, temporarily severing connections when backup operations need to be performed. The intermediary simplifies connection management by centralizing control logic in one component rather than requiring complex coordination between multiple components.
3Reliability
If clone volume is used for mirroring, then data redundancy is achieved, but backup operation flexibility is limited
Solution Approach 1:
The clone volume is designed to serve multiple functions: it acts as a real-time mirror for data redundancy, a backup destination for scheduled backups, and a source for point-in-time recovery operations. This multi-functional design allows the system to achieve data redundancy while simultaneously providing flexible backup and recovery operations without requiring separate dedicated volumes for each function.
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, initiating creation of a snapshot from the clone volume, and initiating storing of the snapshot in the primary storage.