Writable snapshots for boot consolidation
First Claim
1. A system for boot consolidation comprising:
- a storage subsystem;
a physical storage device associated with the storage subsystem;
a plurality of volume snapshots stored on the physical storage device, each one of the plurality of volume snapshots associated with a respective one of a plurality of initiators;
one or more modules operable to cause the storage subsystem to provide each one of the plurality of initiators access to the respective associated one of the plurality of volume snapshots for booting from;
one or more modules operable to cause the storage subsystem to create a read-only snapshot from one of the plurality of volume snapshots, wherein each one of the plurality of volume snapshots is a writable snapshot, andone or more modules operable to cause the storage subsystem to provide a data structure for maintaining volume snapshot dependencies, the data structure providing for arbitrary dependencies between the read-only snapshot and the one of the plurality of volume snapshots.
3 Assignments
0 Petitions
Accused Products
Abstract
Boot consolidation based on writeable volume snapshots can leverage flexible mappings of snapshot dependencies. Such flexible mappings can be established by relating sequence numbers associated with various volume snapshots and can provide for an arbitrarily complex mapping to support a potentially unlimited number of writable snapshots in potentially any dependency configuration. Additionally, the pinning of volumes can provide support for chains of snapshots to depend from snapshots within other chains of snapshots. Merge agents can operate with writable snapshots and boot consolidation to provide system-wide updates where security patches, upgrades, and application software may be applied to a group of servers or a group of users in an efficient fashion.
78 Citations
17 Claims
-
1. A system for boot consolidation comprising:
-
a storage subsystem; a physical storage device associated with the storage subsystem; a plurality of volume snapshots stored on the physical storage device, each one of the plurality of volume snapshots associated with a respective one of a plurality of initiators; one or more modules operable to cause the storage subsystem to provide each one of the plurality of initiators access to the respective associated one of the plurality of volume snapshots for booting from; one or more modules operable to cause the storage subsystem to create a read-only snapshot from one of the plurality of volume snapshots, wherein each one of the plurality of volume snapshots is a writable snapshot, and one or more modules operable to cause the storage subsystem to provide a data structure for maintaining volume snapshot dependencies, the data structure providing for arbitrary dependencies between the read-only snapshot and the one of the plurality of volume snapshots. - View Dependent Claims (2, 3, 4)
-
-
5. A method for managing volume snapshots using dependency mapping, the method comprising:
-
providing a data structure for maintaining volume snapshot dependencies, the data structure providing for arbitrary dependencies between read-only and writeable snapshots; adding a dependency to the data structure in response to a snapshot being created; determining a chain of snapshot dependency from the data structure; and traversing the chain of snapshot dependency to determine physical locations for data storage operations. - View Dependent Claims (6, 7, 8, 9, 10, 11, 12)
-
-
13. A method for system-wide updates, the method comprising:
-
providing a writable snapshot system; generate a writable snapshot; applying an update to the writable snapshot; creating delta information associated with the update; and propagating the update to a plurality of snapshots to be updated, the propagating comprising; determining if the update can be applied automatically; automatically applying the update in response to determining that the update can be applied automatically; and generating a notification requesting manual intervention in response to determining that the update cannot be applied automatically. - View Dependent Claims (14, 15, 16, 17)
-
Specification