Using versioning to back up multiple versions of a stored object

• US 8,126,854 B1
• Filed: 03/05/2007
• Issued: 02/28/2012
• Est. Priority Date: 03/05/2007
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Sreedharan, Sachhin
• Primary Examiner(s): Fleurantin, Jean B
• Assistant Examiner(s): GIRMA, ANTENEH B
• Application Number:
  US11/714,714
• Time in Patent Office: 1,821 Days
• Field of Search: None
• US Class Current: 707/693
• CPC Class Codes: G06F 11/1402 Saving, restoring, recovering or retrying
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Using a versioning feature of an authoring application to back up multiple versions of a stored object in single, version-enabled instance stored on backup media is disclosed. In some embodiments, an indication is received that a subsequent version data associated with an object an existing instance of which is stored in a backup storage location is to be backed up. A version control mechanism of an authoring application that created or updated the object as stored in a primary storage location is invoked to incorporate the subsequent version data into the existing instance of the object as stored in the backup storage location.

Claims

1. A computer-implemented method for performing a backup of a stored object, comprising:

receiving an indication that a subsequent version data associated with an object stored by an authoring application in a shared primary storage location on a primary storage device is to be backed up to a backup storage location where an existing instance of the object is stored;

copying the subsequent version data to the backup storage location; and

invoking, by a backup application, a version control mechanism of the authoring application that created or updated the object stored in the primary storage location to incorporate the subsequent version data as copied to the backup storage location into the existing instance of the object stored in the backup storage location;

wherein the version control mechanism of the authoring application is invoked by the backup application programmatically via an API or other interface of the authoring application; and

wherein the authoring application is configured to export subsequent version data by storing subsequent version data in the shared primary storage location when a new version of a stored object is saved.

2. A method as recited in claim 1, wherein the authoring application incorporates the subsequent version data into the existing instance of the object as stored in the backup storage location by importing the subsequent version data from the second shared storage location to the backup storage location.

3. A method as recited in claim 1, wherein determining that the existing instance is stored in the backup storage location comprises determining an object identifier associated with an object with which the subsequent version data is associated and determining that the existing instance stored in the backup storage location is associated with the object identifier.

4. A method as recited in claim 1, wherein the backup storage location comprises a storage location on a secondary disk.

5. A method as recited in claim 1, wherein the backup storage location comprises a storage location on a backup server.

6. A method as recited in claim 1, wherein the backup application or another process invokes the authoring application.

7. A method as recited in claim 1, wherein the subsequent version data comprises a version number.

8. A method as recited in claim 7, wherein the subsequent version data comprises an object the name or other identifier of which includes a version number.

9. A method as recited in claim 1, wherein the backup application or another process is configured to maintain in an index an indication that the object has been backed up but not version information for the object.

10. A method as recited in claim 1, wherein version information for the object is included in the existing instance of the object.

11. A method as recited in claim 1, further comprising storing the existing instance a first time the corresponding object is backed up.

12. A method as recited in claim 1, wherein the authoring application is configured to determine that a retention period has expired with respect to an expired version included in the existing instance.

13. A method as recited in claim 12, wherein the authoring application is further configured to delete the expired version from the existing instance.

14. A method as recited in claim 1, further comprising receiving a request that a recovery operation be performed with respect to the object.

15. A method as recited in claim 14, further comprising retrieving the existing instance from the backup storage location.

16. A method as recited in claim 15, further comprising determining from the existing instance one or more versions available to be recovered.

17. A method as recited in claim 16, further comprising displaying to a user a displayed data indicating said one or more versions available to be recovered.

18. A method as recited in claim 17, further comprising receiving a selection of a selected version to be recovered.

19. A method as recited in claim 14, wherein the authoring application is configured to use the existing instance to perform one or more of the following:

identify one or more versions available to be recovered;

display to a user a displayed data indicating said one or more versions available to be recovered;

receive a selection of a desired version to be recovered; and

recover the desired version.

20. A computer program product for performing a backup of a stored object, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for:

receiving an indication that a subsequent version data associated with an object stored by an authoring application in a shared primary storage location on a primary storage device is to be backed up to a backup storage location where an existing instance of the object is stored;

copying the subsequent version data to the backup storage location; and

invoking, by a backup application, a version control mechanism of the authoring application that created or updated the object stored in the primary storage location to incorporate the subsequent version data as copied to the backup storage location into the existing instance of the object stored in the backup storage location;

wherein the version control mechanism of the authoring application is invoked by the backup application programmatically via an API or other interface of the authoring application; and

wherein the authoring application is configured to export subsequent version data by storing subsequent version data in the shared primary storage location when a new version of a stored object is saved.

21. A system for backing up data, comprising:

a storage device comprising a backup storage location; and

a processor coupled to the storage device and configured to;

receive an indication that a subsequent version data associated with an object stored by an authoring application in a shared primary storage location on a primary storage device is to be backed up to a backup storage location where an existing instance of the object is stored;

copy the subsequent version data to the backup storage location; and

invoke, by a backup application, a version control mechanism of an authoring application that created or updated the object stored in the primary storage location to incorporate the subsequent version data as copied to the backup storage location into the existing instance of the object stored in the backup storage location;

wherein the version control mechanism of the authoring application is invoked by the backup application programmatically via an API or other interface of the authoring application; and

wherein the authoring application is configured to export subsequent version data by storing subsequent version data in the shared primary storage location when a new version of a stored object is saved.

22. A system as recited in claim 21, wherein the subsequent version data comprises a version number.

23. A system as recited in claim 22, wherein the subsequent version data comprises an object the name or other identifier of which includes a version number.

24. A system as recited in claim 21, wherein the backup application or another process is configured to maintain in an index an indication that the object has been backed up but not version information for the object.

25. A system as recited in claim 21, wherein version information for the object is included in the existing instance of the object.

26. A system as recited in claim 21, wherein the authoring application is configured to determine that a retention period has expired with respect to an expired version included in the existing instance.