Clone file backup and restore

Patent metadata

Field	Value
Publication number	US-10055299-B2
Application number	US-201514859673-A
Country	US
Kind code	B2
Filing date	Sep 21, 2015
Priority date	Mar 30, 2015
Publication date	Aug 21, 2018
Grant date	Aug 21, 2018

Abstract

In an approach to backup and restore one or more clone file trees, one or more processors generate a clone management table. One or more processors record a clone management information in the clone management table about each clone file. To backup a clone file, one or more processors update the clone management information, and store one or more data blocks that are in the clone file trees. To restore a clone file, one or more processors analyze a clone management information and restore one or more data blocks in the clone file. To restore a clone file parent, one or more processors analyze a clone management information and restore one or more data blocks in the clone file parent. To restore a clone file tree, one or more processors analyze a clone management information and restore one or more data blocks in the clone file tree.

First claim

What is claimed is:

1. A method for maintaining data integrity in a computer data storage system by backing up and restoring one or more clone file trees in the computer data storage system, the method comprising:
generating, by one or more processors, a clone management table that includes at least one clone file parent and at least one clone file child;
recording, by the one or more processors, in the clone management table, a clone management information about each clone file in one or more clone file trees in a file system of a computing device, wherein (i) the clone file tree includes metadata specifying a sequence of files with parent-child relationships in which a given clone file child is generated from a given clone file parent that immediately preceded the given clone file child in the sequence (ii) the given clone file parent is modified to be a read-only file when the given clone child file is created and (iii) the given clone file child is a read and write file;
responsive to receiving a backup request, updating, by the one or more processors, the clone management information, and storing one or more data blocks that are in the one or more clone file trees;
responsive to receiving a request to restore a clone file, analyzing, by the one or more processors, the clone management information about the clone file, and restoring one or more data blocks in the clone file to the file system;
responsive to receiving a request to restore a clone the parent, analyzing, by the one or more processors, the clone management information about the clone file parent, and restoring one or more data blocks in the clone file parent to the file system, wherein a given clone parent file contains all data blocks that were originally in a file when a clone of the given clone parent file was created;
responsive to receiving a request to restore a clone file tree, (i) analyzing, by the one or more processors, the clone management information about the clone file tree, and (ii) restoring, by the one or more processors, one or more data blocks in the clone file tree to the file system of the computing device; and
responsive to receiving a request to check a validity of the clone management table, analyzing, by the one or more processors, the clone management information in the clone management table for coherence, and generating a list of an invalid information that is in the clone management table, wherein the updating of the clone management information in the clone management table enables the backup and the restoration of at least a part of the clone file tree precludes one or more data redundancies and restores the clone file tree to a form that the clone file tree had when the clone file tree was backed up.

2. The method of claim 1 , wherein a clone management information on a clone file is comprised of a file information on the clone file, a location of one or more data blocks that have been written to in the clone file, and a last backup time of the clone file.

3. The method of claim 2 , wherein the file information is comprised of an identifier of the clone file, a size of the clone file, an inode number of the clone file, an inode metadata of the clone file, an inode number of a parent of the clone file, a depth level of the clone file in a clone file tree, a child count of the clone file, and a valid indicator for the clone management information.

4. The method of claim 1 , wherein a backup and restore server backs up clone files from the file system and restores clone files to the file system.

5. The method of claim 4 , wherein the clone management table is located in the backup and restore server.

6. The method of claim 5 , wherein the backup and restore server and the clone management table are distributed across a plurality of computers in the file system.

7. The method of claim 1 , further comprising:
responsive to receiving a file expiration request, updating, by the one or more processors, the clone management information, and deleting one or more data blocks from the one or more clone file trees.

Assignees

• IBM

Inventors

• Bender Stefan
• Haustein Nils
• Mueller-Wicke Dominic
• Sawdon Wayne A
• Smith James P

Classifications

• G06F11/00

  Error detection; Error correction; Monitoring (error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00) · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

• G06F11/1451 Primary

  by selection of backup contents · CPC title

• G06F11/1435

  using file system or storage system metadata · CPC title

• G06F11/1448 Primary

  Management of the data involved in backup or backup restore · CPC title