Virtual Volume Access for Remote Snapshot Transparency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data storage systems face challenges in managing remote snapshots efficiently, limiting host access to both local and remote file system objects and hindering transparent access to destination storage objects from a source.
Innovation Solution
The technique involves specifying policies for snapshots on a destination data storage system, enabling remote access and associating them with a SCSI target, creating a virtual volume at the source configured as a SCSI initiator, and exposing it to the host, allowing transparent access to both local and remote snapshots.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of stationary object
If remote snapshots are stored on a destination data storage system, then snapshot retention and history are improved, but host access to remote snapshots is limited and operation complexity increases
Solution Approach 1:
The source data storage system acts as an intermediary between the host and destination snapshots. The source creates a virtual volume that is exposed to the host, which then accesses destination snapshots through the source rather than directly. This intermediary approach allows hosts to access remote snapshots as if they were local, resolving the access limitation while maintaining long-term retention at the destination.
2Ease of operation
If hosts directly access destination storage objects, then access transparency is improved, but resource usage on the source and system complexity increase
Solution Approach 1:
The source data storage system creates a virtual volume that copies the interface and access methods of local volumes. This virtual volume is exposed to the host using the same file mechanisms as local snapshots, providing access transparency without requiring direct host access to destination storage objects. The copying approach maintains simplicity at the host level while managing complexity at the source level.
3Quantity of substance
If more snapshot history is maintained, then data recovery options are improved, but resource usage on the source storage system increases
Solution Approach 1:
The snapshot storage is segmented between source and destination systems. The source maintains a virtual volume that provides access to snapshots, while the actual snapshot data is stored at the destination. This segmentation allows extensive snapshot history to be maintained without proportionally increasing resource usage at the source, as the bulk storage burden is transferred to the destination system.
Data Source
AI summary
A technique for managing snaps of data objects is disclosed. Managing snaps of a data object hosted by a source data storage system (source) involve specifying, by the source, a set of policies for snaps of the data object stored on a destination data storage system (destination). The set of policies include a remote access policy information to designate a destination snaps as remote access enabled. The policy information is transferred to the destination enabling policy implementation on destination snaps. Destination snaps designated as remote access enabled are associated with a SCSI target at the destination. A virtual volume having virtual snaps associated with corresponding remote access enabled destination snaps is created at the source. The virtual volume is configured as a SCSI initiator, and exposed to a host providing access of destination snaps at the source; the source and destination are file systems implementing checkpoint functionality.