EXTENSIBLE APPLICATION BACKUP SYSTEM AND METHOD

• US 20090276591A1
• Filed: 04/30/2008
• Published: 11/05/2009
• Est. Priority Date: 04/30/2008
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Mu, Yuedong Paul, Aravindan, Sajeev
• Granted Patent: US 7,934,066 B2
• Time in Patent Office: Days
• US Class Current: 711/162
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

An archive method and system receives a backup request for a target dataset used by an application on a primary storage system to be backed up on a secondary storage system. Different applications may each have a corresponding proprietary application format for storing their datasets. An application translator module is loaded into an extensible backup manager that converts between a proprietary application format associated with the target dataset and a predetermined storage format used by the extensible backup manager. The application translator module converts from the proprietary application format into the predetermined storage format when the baseline backup of the target dataset has not yet been performed. An incremental backup uses the application translator module to convert from the proprietary application format associated with the application into the predetermined storage format of the extensible backup manager. Once completed, a data mover component causes the incremental backup and the baseline backup of the entire target dataset, if scheduled, to be moved from the primary storage to the secondary storage and stored in the predetermined storage format rather than the proprietary application format associated with the application.

Claims

1. An archive method using a primary storage and a secondary storage comprising:

receiving a backup request for a target dataset used by an application on a primary storage system to be backed up on a secondary storage system, wherein the primary storage system may have one or more different applications and each application having a corresponding one or more different proprietary application formats for storing their datasets;

identifying an application translator module component to be loaded into an extensible backup manager that converts between a proprietary application format associated with the target dataset and a predetermined storage format used by the extensible backup manager;

scheduling a baseline backup of entire target dataset from the primary storage to the secondary storage using the application translator module to convert from the proprietary application format into the predetermined storage format when the baseline backup of the target dataset has not yet been performed;

performing an incremental backup of the target dataset in addition to the baseline backup of the entire target dataset, if the incremental backup is scheduled, wherein the incremental backup uses the application translator module to convert from the proprietary application format associated with the application into the predetermined storage format of the extensible backup manager; and

invoking a data mover component from the extensible backup manager when the application translator module has completed converting from the proprietary application format into the predetermined storage format wherein the data mover component causes the incremental backup and the baseline backup of the entire target dataset, if scheduled, to be moved from the primary storage to the secondary storage as requested and stored in the predetermined storage format rather than the proprietary application format associated with the application.

2. The method of claim 1 wherein the application is selected from a set of applications including an application server delivering application data to a thin client, a web application server delivering web application data to a web application thin client, an on-demand application server delivering on-demand application data to a on-demand application thin client.

3. The method of claim 1 wherein the application may be a filesystem and the target dataset includes data associated with the filesystem.

4. The method of claim 2 wherein the thin client is remotely located from the extensible backup manager over a network.

5. The method of claim 1 further comprising:

generating an additional application translator module for each backup request that operates to separately convert between a proprietary application format and a predetermined storage format; and

a single extensible backup manager that identifies each additional application translator module in accordance with the target dataset and application and ensures each application translator module completes conversion of the target dataset from the proprietary application format into the predetermined storage format.

6. The method of claim 1 wherein performing the incremental backup and the baseline backup further comprises;

interfacing the application translator module with each application to obtain the target dataset; and

providing backup location information associated with the resulting target dataset to the extensible backup manager once the backup request has been fulfilled.

7. The method of claim 1 further comprising:

performing post-processing verification on the target dataset once the backup request has been fulfilled using the extensible backup manager; and

storing backup location information using the extensible backup manager wherein the backup location information of the resulting target dataset on the primary storage is stored on a destination organizational structure on the secondary storage.

8. The method of claim 1 wherein the incremental backup includes all files modified since the most recent baseline backup of the entire target dataset.

9. The method of claim 1 wherein the incremental backup includes all blocks of data modified since the most recent baseline backup of the entire target dataset.

10. The method of claim 1 wherein the application translator module further performs a snapshot backup for the dataset at a particular time to provide an application consistent view of the dataset as preparation for subsequent backup events.

15. The method of claim 1 further comprising:

generating an additional application translator module for each restore request that operates to separately convert between a predetermined storage format and a proprietary application format; and

a single extensible backup manager that identifies each additional application translator module in accordance with the target dataset and application and ensures each application translator module completes conversion of the target dataset from the predetermined storage format into the proprietary application format.

16. The method of claim 1 further comprising:

performing post-processing verification on the target dataset once the restore request has been fulfilled using the extensible backup manager; and

storing restore location information using the extensible backup manager wherein the restore location information of the resulting target dataset on the primary storage may be stored on a destination organizational structure on the secondary storage.

11. An archive method using a primary storage and a secondary storage comprising:

receiving a restore request for a target dataset archived on a secondary storage system and associated with an application on a primary storage system, wherein the primary storage system may have one or more different applications and each application having a corresponding one or more different proprietary application formats for storing their datasets;

identifying an application translator module to be loaded into an extensible backup manager that converts between a predetermined storage format used by the extensible backup manager and a proprietary application format associated with the target dataset;

converting the target dataset archived in a predetermined storage format back into the proprietary application storage format associated with the application using the application translator module; and

invoking a data mover component from the extensible backup manager when the application translator module has completed converting from the predetermined storage format into the proprietary application format wherein the data mover component causes the incremental backup and the baseline backup of the entire target dataset, if the baseline backup is requested, to be moved from the secondary storage to the primary storage as requested in the restore request and to be stored on the primary storage in the proprietary application format associated with the application instead of the predetermined storage format associated with the extensible backup manager.

12. The method of claim 11 wherein the application is selected from a set of applications including an application server delivering application data to a thin client, a web application server delivering web application data to a web application thin client, an on-demand application server delivering on-demand application data to a on-demand application thin client.

13. The method of claim 11 wherein the application may be a filesystem and the target dataset includes data associated with the filesystem.

14. The method of claim 12 wherein the thin client is remotely located from the extensible backup manager over a network.

17. A computer program product, tangibly stored on a computer-readable medium, for archiving using a primary storage and a secondary storage comprising instructions operable to cause a programmable processor to:

receive a backup request for a target dataset used by an application on a primary storage system to be backed up on a secondary storage system, wherein the primary storage system may have one or more different applications and each application having a corresponding one or more different proprietary application formats for storing their datasets;

identify an application translator module component to be loaded into an extensible backup manager that converts between a proprietary application format associated with the target dataset and a predetermined storage format used by the extensible backup manager;

schedule a baseline backup of entire target dataset from the primary storage to the secondary storage using the application translator module to convert from the proprietary application format into the predetermined storage format when the baseline backup of the target dataset has not yet been performed;

perform an incremental backup of the target dataset in addition to the baseline backup of the entire target dataset, if the incremental backup is scheduled, wherein the incremental backup uses the application translator module to convert from the proprietary application format associated with the application into the predetermined storage format of the extensible backup manager; and

invoke a data mover component from the extensible backup manager when the application translator module has completed converting from the proprietary application format into the predetermined storage format wherein the data mover component causes the incremental backup and the baseline backup of the entire target dataset, if scheduled, to be moved from the primary storage to the secondary storage as requested and stored in the predetermined storage format rather than the proprietary application format associated with the application.

18. A computer program product, tangibly stored on a computer-readable medium, for archiving using a primary storage and a secondary storage comprising instructions operable to cause a programmable processor to:

receive a restore request for a target dataset archived on a secondary storage system and associated with an application on a primary storage system, wherein the primary storage system may have one or more different applications and each application having a corresponding one or more different proprietary application formats for storing their datasets;

identify an application translator module to be loaded into an extensible backup manager that converts between a predetermined storage format used by the extensible backup manager and a proprietary application format associated with the target dataset;

convert the target dataset archived in a predetermined storage format back into the proprietary application storage format associated with the application using the application translator module; and

invoke a data mover component from the extensible backup manager when the application translator module has completed converting from the predetermined storage format into the proprietary application format wherein the data mover component causes the incremental backup and the baseline backup of the entire target dataset, if the baseline backup is requested, to be moved from the secondary storage to the primary storage as requested in the restore request and to be stored on the primary storage in the proprietary application format associated with the application instead of the predetermined storage format associated with the extensible backup manager