REPLICATING LOCAL FILE SYSTEMS AS RESPECTIVE LUNS IN A STORAGE ARRAY, USING BLOCK-LEVEL DATA TRANSFERS AND ENHANCED STORAGE MANAGERS, DATA AGENTS, AND MEDIA AGENTS IN AN INFORMATION MANAGEMENT SYSTEM

• US 20160004721A1
• Filed: 07/01/2014
• Published: 01/07/2016
• Est. Priority Date: 07/01/2014
• Status: Abandoned Application

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: IYER, Sudha Krishnan, LITTLEFIELD, Duncan Alden, KUMAR, Kuldeep
• Application Number:
  US14/321,705
• Publication Number:
  US 20160004721A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/184 implemented as replicated file system

Abstract

Systems and methods are disclosed for block-level incremental replication of a local file system in a source volume/partition to a storage array—replicated to a single logical disk designated by a logical unit number (LUN) with a single volume/partition corresponding to the source. From the perspective of the storage array, non-native data (e.g., data in a local file system residing in locally-attached storage) may be backed up to a LUN that is native to the storage array and thus available for any number of subsequent LUN-based operations. Enhanced data agents, media agents, and storage manager(s), including replication storage policies, operate in concert with the storage array to execute successive file-system-to-LUN block-level replication jobs to protect the data in the local file system.

Claims

1. A system for block-level replication of data stored in a file system to a logical disk identified by a logical unit number, the system comprising:

a client computer in communication with a first locally-attached storage device, the client computer comprising an application, a data agent, and a media agent,

wherein the first storage device comprises a first set of data generated by the application, and

wherein the first set of data is organized as a first file system;

a storage manager in communication with the client computer;

a second storage device in communication with the client computer and with the storage manager,

wherein the second storage device is a storage array comprising a first logical disk identified by a first logical unit number;

wherein the storage manager is configured to manage a replication job of the first file system, based on one or more incremental block-level transfers, to the first logical unit number on the second storage device;

wherein to manage the replication job of the first file system, the storage manager is configured to;

instruct the data agent to generate a software snapshot of the first set of data in the first file system, and to track any changed blocks in the software snapshot as compared to a preceding software snapshot of the first set of data,

instruct the media agent to transfer the changed blocks of the software snapshot from the first storage device to the first logical disk identified by the logical unit number,

instruct the storage array (i) to generate a hardware snapshot of the first logical disk identified by the logical unit number and (ii) to store the hardware snapshot on the storage array, wherein the hardware snapshot represents a copy of the first file system at the time that the software snapshot was taken, and

designate the hardware snapshot as a primary copy of the first file system; and

wherein the storage manager is further configured to manage a restoration job of the primary copy of the first file system to be accessible to the application.

2. The system of claim 1 wherein the first logical unit number is configured, based on instructions from the storage manager, to comprise a storage volume that is configured to store a second file system of the same type as the first file system.

3. The system of claim 1 wherein the first logical unit number is configured, based on instructions from the storage manager, based on one or more characteristics of the first file system.

4. The system of claim 1 wherein the storage manager is further configured to manage a secondary copy operation based on the primary copy of the first file system, wherein at least one of the following results from the secondary copy operation:

(i) an auxiliary copy of the first file system, and

(ii) an archive copy of the first file system.

5. A method for block-level replication of data stored in a file system to a logical disk identified by a logical unit number, the method comprising:

replicating a file system, based on block-level transfers, from a first locally-attached storage device to a logical disk on a storage array, wherein the logical disk is identified by a logical unit number,

wherein the data in the file system is generated by an application that executes on a client computing device,

wherein the replicating is managed by a storage manager, and wherein the replicating comprises;

generating, by the client computing device, a software snapshot of the data in the first file system, including tracking any changed blocks in the software snapshot as compared to a preceding software snapshot, wherein the software snapshot is generated based on one or more instructions received from an application-specific data agent that executes on the client computing device,

transferring, by a media agent that executes on the client computing device, the changed blocks of the software snapshot of the first file system from the first locally-attached storage device to the logical disk identified by the logical unit number,

instructing the storage array, by the storage manager, to (i) generate a hardware snapshot of the logical disk identified by the logical unit number, which comprises the transferred changed blocks, and (ii) store the hardware snapshot on the storage array, wherein the hardware snapshot represents a copy of the file system at the time that the software snapshot was taken, and

designating, by the storage manager, the hardware snapshot as a primary copy of the file system; and

restoring the data in the file system to be accessible to the application, based on restoring, as managed by the storage manager, the primary copy of the first file system from the hardware snapshot.

6. The method of claim 5, wherein, if the data in the file system was not previously backed up by the storage manager before transferring the changed blocks, transferring, by the media agent all the blocks of the software snapshot of the file system from the first locally-attached storage device to the logical disk identified by the logical unit number.

7. The method of claim 5 wherein the logical unit number is configured, based on instructions from the storage manager, to comprise a storage volume for a second file system of the same type as the file system in the locally-attached storage device.

8. The method of claim 5 wherein the logical disk identified by the first logical unit number is configured, based on instructions from the storage manager, based on one or more characteristics of the file system.

9. The method of claim 5 further comprising:

generating an auxiliary copy, as managed by the storage manager, based on the primary copy, wherein the auxiliary copy represents a copy of the data in the file system at the time of the software snapshot; and

storing the auxiliary copy to another storage device that is distinct from the first locally-attached storage device and from the storage array.

10. The method of claim 5 further comprising:

generating an archive copy, as managed by the storage manager, based on the primary copy, wherein the archive copy represents a copy of the data in the file system at the time of the software snapshot; and

storing the archive copy to another storage device that is distinct from the first locally-attached storage device and from the storage array, wherein the file system is no longer on the locally-attached storage device.

11. A method for managing block-level replication of data stored in a file system to a logical disk identified by a logical unit number, the method comprising:

managing a replication job, by a storage manager in an information management system that comprises a data agent and a media agent executing on a client computing device,

wherein the replication job is based on block-level transfers of a file system, from a first locally-attached storage device to a logical disk on a storage array, wherein the logical disk is identified by a logical unit number,

wherein data in the file system is generated by an application that executes on the client computing device,

wherein the managing of the replication job comprises;

instructing the data agent to trigger a software snapshot of the file system and to track any changed blocks in the software snapshot as compared to a preceding software snapshot,

instructing the media agent to transfer one or more blocks of the software snapshot of the file system from the first locally-attached storage device to the logical disk identified by the logical unit number,

instructing the storage array to (i) generate a hardware snapshot of the logical disk identified by the logical unit number, which comprises the transferred one or more blocks, and (ii) store the hardware snapshot on the storage array, wherein the hardware snapshot represents a copy of the file system at the time that the software snapshot was taken, and

designating, by the storage manager, the hardware snapshot as a primary copy of the file system,

instructing the storage array to configure a second logical disk identified by a second logical unit number, the second logical disk comprising the hardware snapshot; and

managing a restoration job by the storage manager, based on mounting the second logical disk to a mount path accessible to the application, resulting in the primary copy of the file system becoming accessible to the application.

12. The method of claim 11 further comprising:

triggering, by the data agent executing on the client computing device, based on the instructing by the storage manager, a software snapshot of the file system; and

tracking, by the data agent, which blocks in the software snapshot are changed as compared to an earlier software snapshot of the file system.

13. The method of claim 11 further comprising:

triggering, by the data agent executing on the client computing device, based on the instructing by the storage manager, a software snapshot of the file system;

tracking, by the data agent, which blocks in the software snapshot are changed as compared to an earlier software snapshot of the file system;

transferring, by the data agent, the changed blocks to the media agent.

14. The method of claim 11 further comprising:

triggering, by the data agent executing on the client computing device, based on the instructing by the storage manager, a software snapshot of the file system;

tracking, by the data agent, which blocks in the software snapshot are changed as compared to an earlier software snapshot of the file system; and

transferring, by the media agent, the one or more blocks of the software snapshot of the file system as instructed by the storage manager, wherein the transferring is based on the tracking of changed blocks by the data agent, and wherein only the changed blocks, as tracked by the data agent, are transferred from the first locally-attached storage device to the logical disk identified by the logical unit number.