Controlling incremental backups using opaque object attributes

• US 7,660,836 B2
• Filed: 03/09/2006
• Issued: 02/09/2010
• Est. Priority Date: 03/09/2006
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bolik, Christian, Kojenov, Alexei, Smith, James Patrick, Young, Jason Christopher, Naineni, Malahal R., Palsule, Ninad S., Jujjuri, Venkateswararao, Seeger, James John
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): BURKE, JEFF A
• Application Number:
  US11/372,816
• Publication Number:
  US 20070214197A1
• Time in Patent Office: 1,433 Days
• Field of Search: 707/204
• US Class Current: 707/640
• CPC Class Codes: G06F 11/1451 by selection of backup contents

Abstract

Provided are techniques for determining whether content of an object has changed. Under control of a backup system, opaque object attributes and a data identifier are received, wherein the data identifier is generated based on one or more relevant object attributes of the opaque object attributes that indicate whether at least one of the content of the object and one or more of the relevant object attributes has changed. The received data identifier is compared with a previously stored data identifier. In response to determining that the received data identifier and the previously stored data identifier do not match, it is determined that the content of the object has changed.

Claims

1. A method for determining whether content of an object has changed, comprising:

under control of a backup system executing at a client computer having a processor, requesting opaque object attributes and a data identifier by issuing a command to an object system module executing at the client computer, wherein the backup system is not able to interpret the opaque object attributes to identify opaque object attributes that are relevant to determining whether to perform incremental backup, and wherein the object system module is able to interpret the opaque object attributes to identify object attributes that are relevant to determining whether to perform the incremental backup;

under control of the object system module, generating the data identifier by;

selecting a set of relevant opaque object attributes from a set of object attributes for the object, wherein the selected set of relevant opaque object attributes indicate at least one of the content of the object or a relevant opaque object attribute has changed, wherein at least one object attribute is not relevant to determining whether to perform the incremental backup and is not in the set of relevant opaque object attributes; and

generating the data identifier by generating a checksum on the selected set of relevant opaque object attributes; and

under control of the backup system;

receiving the opaque object attributes and the data identifier from the object system module;

comparing the received data identifier with a previously stored data identifier that was previously generated by the object system module;

in response to determining that the received data identifier and the previously stored data identifier do not match,

determining that the content of the object has changed; and

performing an incremental backup of the object and a backup of the opaque object attributes; and

in response to determining that the received data identifier and the previously stored data identifier do match, determining that the content of the object has not changed and that incremental backup of the content of the object does not need to be performed.

2. The method of claim 1, further comprising:

storing the received data identifier.

3. The method of claim 1, further comprising:

in response to determining that this is a first time that the object is being backed up,

storing the data identifier in a first data store; and

backing up the object and the opaque object attributes to a second data store.

4. The method of claim 1, further comprising:

in response to determining that the received data identifier and the previously stored data identifier do match,

generating a first checksum of the received opaque object attributes;

retrieving a second checksum of previously stored opaque object attributes; and

in response to determining that the first checksum and the second checksum do not match, backing up the opaque object attributes separate from the object.

5. A computer program product for determining whether content of an object has changed comprising a computer readable storage medium including a computer readable program, wherein the computer readable program when executed by a processor on a client computer causes the computer to:

under control of a backup system executing at the client computer, request opaque object attributes and a data identifier by issuing a command to an object system module executing at the client computer, wherein the backup system is not able to interpret the opaque object attributes to identify opaque object attributes that are relevant to determining whether to perform incremental backup, and wherein the object system module is able to interpret the opaque object attributes to identify object attributes that are relevant to determining whether to perform the incremental backup;

under control of the object system module, generate the data identifier by;

selecting a set of relevant opaque object attributes from a set of object attributes for the object, wherein the selected set of relevant opaque object attributes indicate at least one of the content of the object or a relevant opaque object attribute has changed, wherein at least one object attribute is not relevant to determining whether to perform the incremental backup and is not in the set of relevant opaque object attributes; and

generating the data identifier by generating a checksum on the selected set of relevant opaque object attributes; and

under control of the backup system;

receive the opaque object attributes and the data identifier from the object system module;

compare the received data identifier with a previously stored data identifier that was previously generated by the object system module;

in response to determining that the received data identifier and the previously stored data identifier do not match,

determine that the content of the object has changed; and

performing an incremental backup of the object and a backup of the opaque object attributes; and

in response to determining that the received data identifier and the previously stored data identifier do match, determining that the content of the object has not changed and that incremental backup of the content of the object does not need to be performed.

6. The computer program product of claim 5, wherein the computer readable program when executed on a computer causes the computer to:

store the received data identifier.

7. The computer program product of claim 5, wherein the computer readable program when executed on a computer causes the computer to:

in response to determining that this is a first time that the object is being backed up,

store the data identifier in a first data store; and

back up the object and the opaque object attributes to a second data store.

8. The computer program product of claim 5, further comprising:

in response to determining that the received data identifier and the previously stored data identifier do match,

generate a first checksum of the received opaque object attributes;

retrieve a second checksum of previously stored opaque object attributes; and

in response to determining that the first checksum and the second checksum do not match, back up the opaque object attributes separate from the object.

9. A system for determining whether content of an object has changed, comprising:

hardware logic at a client computer implementing operations to;

under control of a backup system at the client computer, request opaque object attributes and a data identifier by issuing a command to an object system module at the client computer, wherein the backup system is not able to interpret the opaque object attributes to identify opaque object attributes that are relevant to determining whether to perform incremental backup, and wherein the object system module is able to interpret the opaque object attributes to identify object attributes that are relevant to determining whether to perform the incremental backup;

under control of the object system module, generate the data identifier by;

selecting a set of relevant opaque object attributes from a set of object attributes for the object, wherein the selected set of relevant opaque object attributes indicate at least one of the content of the object or a relevant opaque object attribute has changed, wherein at least one object attribute is not relevant to determining whether to perform the incremental backup and is not in the set of relevant opaque object attributes; and

generating the data identifier by generating a checksum on the selected set of relevant opaque object attributes; and

under control of the backup system;

receive the opaque object attributes and the data identifier from the object system module;

compare the received data identifier with a previously stored data identifier that was previously generated by the object system module;

in response to determining that the received data identifier and the previously stored data identifier do not match,

determine that the content of the object has changed; and

performing an incremental backup of the object and a backup of the opaque object attributes; and

in response to determining that the received data identifier and the previously stored data identifier do match, determining that the content of the object has not changed and that incremental backup of the content of the object does not need to be performed.

10. The system of claim 9, wherein the backup system is adaptable to store the received data identifier.

11. The system of claim 9, wherein the backup system is adaptable to, in response to determining that this is a first time that the object is being backed up, store the data identifier in a first data store and back up the object and the opaque object attributes to a second data store.

12. The system of claim 9, wherein the backup system is adaptable to,

response to determining that the received data identifier and the previously stored data identifier do match, generate a first checksum of the received opaque object attributes,

retrieve a second checksum of previously stored opaque object attributes, and

in response to determining that the first checksum and the second checksum do not match, back up the opaque object attributes separate from the object.