VOLUME OR VIRTUAL MACHINE LEVEL BACKUP AND GENERATING PLACEHOLDERS FOR VIRTUAL MACHINE FILES

• US 20180075166A1
• Filed: 08/23/2017
• Published: 03/15/2018
• Est. Priority Date: 07/16/2014
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Pawar, Rahul S., DORNEMANN, Henry Wallace, KOTTOMTHARAYIL, Rajiv, RAMASWAMY, Chitra, SANCHETI, Ashwin Gautamchand
• Granted Patent: US 10,650,057 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• 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/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/24564 Applying rules; Deductive queries
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 2201/83 the solution involving signatures
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

According to certain aspects, a method can include creating a backup copy of data associated with a virtual machine (VM) on one or more secondary storage devices, wherein the backup copy includes corresponding secondary copies of a plurality of files associated with the VM; analyzing metadata associated with the secondary copies to determine which of the plurality files are eligible to be removed from the primary storage device; in response determining that one or more files are eligible to be removed from the primary storage device, for respective file of the one or more files: determining whether the respective file has been changed since a first time at which the backup copy of the data associated with the VM was created; in response to determining that the respective file has not changed since the first time, removing the respective file; and adding a file placeholder for the removed file.

Claims

1. A method of removing files associated with a virtual machine (VM), the method comprising:

creating a backup copy of data associated with a VM on one or more secondary storage devices, wherein the data associated with the VM resides on a primary storage device and comprises a plurality of files associated with the VM, and wherein the backup copy comprises corresponding secondary copies of the plurality of files;

generating first metadata associated with the backup copy, wherein the first metadata indicates for each respective file included in the backup copy, when the respective file was last modified or accessed;

identifying, based on the first metadata associated with the backup copy and without accessing the data associated with the VM residing on the primary storage device, a set of candidate files from the plurality of files that are eligible to be removed from the primary storage device; and

for each candidate file in the set of candidate files identified based on the first metadata associated with the backup copy and without accessing the data associated with the VM residing on the primary storage device;

determining, based on second metadata associated with the candidate file stored on the primary storage device, whether the candidate file has changed since a first time at which the backup copy including the candidate file was created;

in response to determining that the candidate file has not changed since the first time at which the backup copy including the candidate file was created, removing the candidate file from the primary storage device; and

adding a file placeholder for the removed candidate file on the primary storage device.

2. The method of claim 1, wherein:

the data associated with the VM is included in a volume that resides at least in part on the primary storage device; and

said creating a backup copy of data associated with the VM comprises creating a backup copy of the volume.

3. The method of claim 2, wherein the backup copy of the volume is a snapshot of the volume.

4. The method of claim 3, wherein the snapshot is a hardware snapshot.

5. The method of claim 1, wherein the first metadata comprises one or more of:

file creation time, file access time, file modification time, file size, file extension, user associated with a file, or application associated with a file.

6. The method of claim 1, further comprising identifying the set of candidate files based on a determination that each candidate file in the set has not been modified or accessed for a threshold amount of time.

7. The method of claim 1, further comprising identifying the set of candidate files based on a determination that each candidate file in the set has been accessed fewer that a threshold number of times.

8. The method of claim 1, further comprising refraining from removing the candidate file in the set based on a determination that the candidate file has changed since the first time at which the backup copy including the candidate file was created.

9. The method of claim 1, wherein said creating a backup copy of data associated with the VM comprises:

identifying changed blocks since a time at which a previous backup copy of the data associated with the VM was created; and

copying only the changed blocks to the one or more secondary storage devices.

10. The method of claim 9, wherein a hypervisor associated with the VM identifies the changed blocks.

11. The method of claim 9, wherein a driver marks used blocks to identify the changed blocks.

12. The method of claim 9, wherein the changed blocks are identified by signature comparison.

13. The method of claim 1, wherein the file placeholder comprises a unique identifier associated with the secondary copy of the removed candidate file and an offset associated with the secondary copy of the removed candidate file.

14. The method of claim 1, further comprising, in response to an access of the file placeholder for the removed candidate file, restoring the secondary copy of the removed candidate file from the one or more secondary storage devices to the primary storage device.

15. An information management system configured to remove files associated with a virtual machine (VM), the system comprising:

one or more computing devices comprising computer hardware and configured to;

create a backup copy of data associated with a VM on one or more secondary storage devices, wherein the data associated with the VM resides on a primary storage device and comprises a plurality of files associated with the VM, and wherein the backup copy comprises corresponding secondary copies of the plurality of files;

generate first metadata associated with the backup copy, wherein the first metadata indicates, for each respective file included in the backup copy, when the respective file was last modified or accessed;

identify, based on the first metadata associated with the backup copy and without accessing the data associated with the VM residing on the primary storage device, a set of candidate files from the plurality of files that are eligible to be removed from the primary storage device; and

for each candidate file in the set of candidate files identified based on the first metadata associated with the backup copy and without accessing the data associated with the VM residing on the primary storage device;

determine, based on second metadata associated with the candidate file stored on the primary storage device, whether the candidate file has changed since a first time at which the backup copy including the candidate file was created;

in response to determining that the candidate file has not changed since the first time at which the backup copy including the candidate file was created, remove the candidate file from the primary storage device; and

add a file placeholder for the removed candidate file on the primary storage device.

16. The system of claim 15, wherein:

the data associated with the VM is included in a volume that resides at least in part on the primary storage device; and

the one or more computing devices are further configured to, as part of the creation of the backup copy of the data associated with the VM, create a backup copy of the volume.

17. The system of claim 15, wherein the first metadata comprises one or more of:

file creation time, file access time, file modification time, file size, file extension, user associated with a file, or application associated with a file.

18. The system of claim 15 wherein the one or more computing devices are further configured to identify the set of candidate files based on a determination that each candidate file in the set has not been modified or accessed for a threshold amount of time.

19. The system of claim 15, wherein the one or more computing devices are further configured to identify the set of candidate files based on a determination that each candidate file in the set has been accessed fewer that a threshold number of times.

20. The system of claim 15, wherein the one or more computing devices are further configured to refrain from removing the candidate file in the set based on a determination that the candidate file has changed since the first time at which the backup copy including the candidate file was created.