PRESERVING THE INTEGRITY OF A SNAPSHOT ON A STORAGE DEVICE VIA EPHEMERAL WRITE OPERATIONS IN AN INFORMATION MANAGEMENT SYSTEM

• US 20160042090A1
• Filed: 08/06/2014
• Published: 02/11/2016
• Est. Priority Date: 08/06/2014
• Status: Abandoned Application

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: MITKAR, Amit, KUMARASAMY, Paramasivam
• Application Number:
  US14/453,507
• Publication Number:
  US 20160042090A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

A pseudo-storage-device driver is employed to configure pseudo-volumes that correspond to respective snapshots in a storage array. Each pseudo-volume is mounted as a recovery point instead of the corresponding snapshot. Instead of writing changes to the snapshots, the changes—typically modifications to metadata associated with the snapshot—are managed via the pseudo-volume. Metadata changes that arise in the context of mapping, mounting, and/or using a snapshot are written to the pseudo-volume, in a data structure referred to as a “private store.” Information management operations that need metadata associated with the snapshot are directed to the private store for the latest updates to the metadata. After the information management operation ends, the pseudo-volumes are unmounted and the updates in the private store are discarded. Because no changes were made to the snapshot, no changes need to be reversed. Accordingly, the illustrative system preserves the integrity of the snapshots through any number of information management operations that may generate metadata changes. Moreover, because the illustrative system is agnostic as to whether a given storage device is persistent-type or not, there is less burden on administration and also less risk of error.

Claims

1. A method for preserving the integrity of a snapshot in a storage array, the method comprising:

generating, by a storage array, a snapshot of a volume on the storage array, wherein the snapshot is stored on the storage array, and wherein the snapshot comprises one or more first blocks comprising original metadata;

mapping the snapshot as a logical unit number to a client computing device that is in communication with the storage array;

configuring a pseudo-volume to correspond to the mapped snapshot, wherein the pseudo-volume is presented by a pseudo-storage-device driver that executes on the client computing device;

mounting, by a media agent that executes on the client computing device, the pseudo-volume to a mount point on the client computing device,

wherein the mounting results in at least one second block comprising metadata that is different from the one or more first blocks of original metadata in the snapshot, and

further wherein the mounting comprises writing the at least one second block of different metadata to a first data structure configured in the pseudo-volume;

executing an information management operation that uses the snapshot, based on at least some of the different metadata read from the first data structure configured in the pseudo-volume; and

wherein the writing of the at least one second block of different metadata to the first data structure configured in the pseudo-volume prevents the original metadata in the snapshot from changing, thereby preserving the integrity of the snapshot through the course of the mounting operation.

2. The method of claim 1 further comprising:

unmounting, by the media agent, the pseudo-volume from the mount point on the client computing device; and

unmapping the logical unit number from the client computing device; and

wherein, following the unmounting and the unmapping, the original metadata in the snapshot remains unchanged.

3. The method of claim 1 further comprising:

unmounting, by the media agent, the pseudo-volume from the mount point on the client computing device, wherein the unmount comprises discarding the different metadata in the first data structure; and

unmapping the logical unit number from the client computing device; and

wherein, following the unmounting and the unmapping, the original metadata in the snapshot remains unchanged.

4. The method of claim 1 further comprising:

unmounting, by the media agent, the pseudo-volume from the mount point on the client computing device, wherein the unmount comprises discarding the different metadata in the first data structure; and

unmapping the logical unit number from the client computing device; and

wherein, following the unmounting and the unmapping, the snapshot remains unchanged relative to the volume upon which the snapshot is based.

5. The method of claim 1 wherein the mounting further comprises:

instructing a logical volume management component that executes on the client computing device to write the different metadata resulting from the mounting operation to the first data structure on the pseudo-volume instead of changing the original metadata in the snapshot on the storage array.

6. The method of claim 1 wherein the executing of the information management operation that uses the snapshot, based on at least some of the different metadata in the first data structure, comprises reading the different metadata from the first data structure in the pseudo-volume instead of reading the original metadata from the snapshot on the storage array.

7. The method of claim 1 wherein the executing of the information management operation that uses the snapshot, based on at least some of the different metadata in the first data structure, comprises instructing a logical volume management component that executes on the client computing device to read the different metadata from the first data structure in the pseudo-volume instead of reading the original metadata from the snapshot on the storage array.

8. The method of claim 1 wherein the storage array is a persistent-type of storage array.

9. The method of claim 1 wherein the storage array is a non-persistent-type of storage array.

10. A system for preserving the integrity of a snapshot on a storage array, the system comprising:

a client computing device, comprising a data agent, a media agent, and a pseudo-storage-device driver, wherein the client computing device is configured with a mount point for mounting a pseudo-volume based on the pseudo-storage-device driver;

a storage array in communication with the client computing device, wherein the storage array comprises a snapshot of a volume on the storage array, and wherein the snapshot comprises one or more first blocks comprising original metadata; and

wherein the media agent is configured to;

map the snapshot as a logical unit number to the client computing device,

configure the pseudo-volume to correspond to the snapshot,

configure a first data structure in the pseudo-volume,

mount the pseudo-volume to the mount point of the client computing device, wherein at least one second block comprising metadata that is different from the original metadata is written to the first data structure in the pseudo-volume, and

cause at least some of the different metadata in the first data structure of the pseudo-volume to be used, instead of the original metadata in the snapshot, by an information management operation that uses the snapshot.

11. The system of claim 10 wherein the original metadata in the snapshot remains unchanged through the course of at least one of (i) the mount, and (ii) the information management operation.

12. The system of claim 10 wherein by causing the different metadata to be written to the first data structure on the pseudo-volume instead of changing the original metadata in the snapshot, the media agent is configured to preserve the integrity of the snapshot stored on the storage array through the course of at least one of (i) the mount, and (ii) the information management operation.

13. The system of claim 10 wherein the media agent is further configured to:

unmount the pseudo-volume from the mount point,

discard the contents of the first data structure in the pseudo-volume, and

unmap the logical unit number from the client computing device; and

wherein the original metadata in the snapshot remains unchanged through the course of at least one of (i) the mount, (ii) the information management operation, (iii) the unmount, and (iv) the unmap.

14. The system of claim 10 wherein the media agent is further configured to:

unmount the pseudo-volume from the mount point;

discard the contents of the first data structure in the pseudo-volume;

unmap the logical unit number from the client computing device; and

preserve the integrity of the snapshot stored on the storage array.

15. A method comprising:

preserving the integrity of a snapshot on a storage array, wherein the snapshot comprises one or more first blocks of original metadata, the preserving based on;

mapping the snapshot as a logical unit number to a client computing device, wherein the snapshot is generated by the storage array, and further wherein the snapshot is a block-level image of a volume on the storage array;

configuring, based on a pseudo-storage-device driver that executes on the client computing device, a pseudo-volume to correspond to the mapped snapshot;

mounting the pseudo-volume to a mount point on the client computing device,

wherein the mounting results in at least one second block comprising metadata that is different from the one or more first blocks of original metadata in the snapshot, and

further wherein the mounting comprises writing the at least one second block of different metadata to a first data structure configured in the pseudo-volume;

during the execution of an information management operation that uses the snapshot, reading at least some of the different metadata from the first data structure configured in the pseudo-volume instead of reading the original metadata from the snapshot on the storage array; and

wherein, after the execution of the information management operation that uses the snapshot has completed, the integrity of the snapshot on the storage array is preserved.

16. The method of claim 15, wherein the preserving is further based on:

unmounting the pseudo-volume from the mount point after the execution of the information management operation that uses the snapshot has completed; and

wherein, after the unmounting, the integrity of the snapshot on the storage array is preserved.

17. The method of claim 15, wherein the preserving is further based on:

unmounting the pseudo-volume from the mount point after the execution of the information management operation that uses the snapshot has completed, and

unmapping the logical unit number from the client computing device; and

wherein, after at least one of the unmounting and the unmapping, the integrity of the snapshot on the storage array is preserved.