Storing application data as an enhanced copy

Description

BACKGROUND

Computer data is vital to today's organizations and a significant part of protection against disasters is focused on data protection. As solid-state memory has advanced to the point where cost of memory has become a relatively insignificant factor, organizations can afford to operate with systems that store and process terabytes of data.

Conventional data protection systems include backup, for storing organizational production site data on a periodic basis. Another conventional data protection system uses data replication, by generating a copy of production site data of an organization on a secondary site, and updating this copy with changes. The backup storage system may be situated in the same physical location as the production storage system, or in a physically remote location. Data replication systems generally operate either at the application level, at the file system level, or at the data block level.

SUMMARY

In one example, a method includes generating an enhanced copy, which includes application data generated from using an application, the application, a configuration of the application and runtime settings to run the application. The method also includes restoring at least one of the application, the configuration of the application and the runtime settings using the enhanced copy.

In another aspect, an apparatus includes electronic hardware circuitry configured to generate an enhanced copy that includes application data generated from executing an application, the application and data that enables the application to operate. The circuitry is also configured to access the application data by restoring from the enhanced copy the application and the data that enables the application to operate.

In a further aspect, an article includes a non-transitory computer-readable medium that stores computer-executable instructions. The instructions cause a machine to generate an enhanced copy that includes application data generated from executing an application, the application and data that enables the application to operate. The instructions also cause the machine to access the application data by restoring from the enhanced copy the application and the data that enables the application to operate.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example of a system to generate and manage an enhanced copy, according to one embodiment of the disclosure.

FIG. 2 is a flowchart of an example of a process to generate and manage the enhanced copy, according to one embodiment of the disclosure.

FIG. 3 is a block diagram of an example of a computer on which any portion of the process of FIG. 2 may be implemented, according to one embodiment of the disclosure.

DETAILED DESCRIPTION

Data generated by using an application (application data) is often saved and replicated. However, what is not saved also is the application itself and the runtime environment. For example, a user may have an old copy of the application data but not a means to access and use the data because, for example, the application is gone or has a different version, the components required to run the application no longer exist and so forth. Thus, merely saving just the application data does not ensure being able to access the application data in the future. With some government regulators requiring storing copies up to seven years, for example, and with technologies changing at a much faster cycle, just saving application data is becoming a major problem. Described herein are techniques to save application data as an enhanced copy, which includes at least the application data, the application and runtime environment needed to access and use the application data. Thus, a full working application is restored—not just the data. This has significant advantages in testing, developing and relocating data to new cloud networks.

Referring to FIG. 1, a data protection system 100 is an example of a system to store an enhanced copy. The system 100 includes a host 102, a storage array 104, a cloud storage 106, data protection components 108, a layer 112 and other data sources 150 (e.g., object stores, databases, volumes and so forth). In one example, the storage array 104 is the source location with data that is replicated to the cloud storage 106, which is the target location.

The system 100 also includes an enhanced copy module 120 used to generate an enhanced copy 116. While the enhanced copy module 120 is shown as a separate block in FIG. 1, in other examples, the enhanced module 120 may be located anywhere in system 100 including being in the layer 112.

The host 102 includes an application 110.

In one example, the layer 112 includes at least one of a block storage API (application programming interface), an object storage API, a key/value API, a file system API, a database API and a messaging API.

The cloud storage 106 includes the enhanced copy 116. An enhanced copy 106 includes application data and other data to be able to regenerate data. For example, other data may include the application and the whole operating environment which may include run time environment, run time parameters, data, data copies and any other data needed for the application 110 to operate.

In one particular example, an enhanced copy includes application data, the application, application configuration and runtime settings. In some examples, application data is a consolidation copy of data sources of the application. These data copies may be generated using existing backup/replication technologies or any other method and are in some examples a set of different copies of different sources. Currently the latter is typically the only information stored by backup applications.

In some examples, the application itself is stored to be able to restore/access the data with the correct application version, which in some examples includes the application itself and the applications that generated the data copies. In some examples, the application configuration enables the application to be run from the enhanced copy. In some examples, runtime settings enable the environment to be mimicked.

An enhanced copy ensures that even if the enhanced copy is dormant for seven years, for example, the data can still be accessed. The restore operations may use some or all of the above information in an enhanced copy to re-create copies for different purposes. For example, the data and runtime may be used from an enhanced copy but the restore uses a new version of the application.

In some examples, applications with multiple data sources (e.g., object stores, databases, volumes and so forth) can then be backed up and restored correctly as parts of the data of the application are stored together. Referring to FIG. 2, a process 200 is an example of process to generate and manage an enhanced copy. In one example, the process 200 is executed by the enhanced copy module 120.

Process 200 generate enhanced copy metadata (202). The enhanced copy module 120 adds additional parameters to the enhanced copy than previously used in the art. For example, an enhanced copy will include metadata on application operation parameters which describe how to run the application, number of instances, scale out parameters and availability information. In addition, the application metadata may include metadata on how to connect to additional resources: databases, object stores, data volumes, file systems and so forth. Additional application metadata added may further include metadata that provides information about the resources that the application uses including one or more of IDs, names and types.

Process 200 defines the application policy (206). For example, the enhanced application module 120 defines what service to provide (backup, replication, HA (high-availability) storage, multiple copies, multiple point-in-time copies and so forth) and the location where the resulting enhanced copy will be (or should be) located.

Process 200 intercepts data resources (210) and transfers the data to appropriate location (216). For example, the layer 112 uses the enhanced copy metadata to intercept data resources used by the application (e.g., other sources 150) and transfers the data to the appropriate location.

The process 200 ensures having the elements that constitute an enhanced copy, for example, the application data, the actual application, the application configuration and the runtime environment information. Interception of data sources is a method to retrieve copies of application data. This can be a splitter in case of replication, an array snapshot mechanism, a backup agent and so forth.

Process 200 generates an enhanced copy (222). For example, the enhanced copy is generated using at least the enhanced copy metadata generated in processing block 202, the application policy defined in processing block 206 and the information intercepted from the data resources in processing block 210.

In one example, the enhanced copy module 120 orchestrates generation of enhanced copies of the application data (e.g., BITC application data), possibly in multiple locations and attaches to the application data, the application (e.g., BITC application) modules and runtime environment parameters. Attaching to the application data, the application modules and runtime environment parameters means that every enhanced copy has the ability to be reconstructed back to a full running application with all the related data. That is, this generates copies of the full application and not just the application data.

In one example, the enhanced copy may be generated at the source location (e.g., production site) and transferred to the target location (e.g., replication site). In another example, the enhanced copy may be generated at the target location.

Process 200 manages the enhanced copy (228). For example, the enhanced copy module 120 perform one or more of the following management functions: tracks the location, retention and integrity of the enhanced copies; performs recovery operations on the enhanced copies; performs maintenance operations on the enhanced copies; and manages the cost of storage of the application copies across multiple locations/clouds.

Tracking the location, retention and integrity of the enhanced copies ensures that enhanced copies can be utilized when needed and that restored data is correct. Performing recovery operations on the enhanced copies includes restoring an application from an enhanced copy (to existing or new instance); failing over the application to an enhanced copy and exposing an enhanced copy as a snapshot for business continuity purposes. Performing maintenance operations on enhanced copies includes deleting enhanced copies once retention time has passed; transferring enhanced copies to new locations and generating copies of enhanced copies if there is a need to provide additional redundancy. Managing the cost of storage allows for cost optimization using copy location, retention and availability.

Referring to FIG. 3, in one example, an enhanced copy module 120 is an enhanced copy module 120′. The compression module 120′ includes a processor 302, a volatile memory 304, a non-volatile memory 306 (e.g., hard disk) and the user interface (UI) 308 (e.g., a graphical user interface, a mouse, a keyboard, a display, touch screen and so forth). The non-volatile memory 306 stores computer instructions 312, an operating system 316 and data 318. In one example, the computer instructions 312 are executed by the processor 302 out of volatile memory 304 to perform all or part of the processes described herein (e.g., process 200).

The processes described herein (e.g., process 200) are not limited to use with the hardware and software of FIG. 3; they may find applicability in any computing or processing environment and with any type of machine or set of machines that is capable of running a computer program. The processes described herein may be implemented in hardware, software, or a combination of the two. The processes described herein may be implemented in computer programs executed on programmable computers/machines that each includes a processor, a non-transitory machine-readable medium or other article of manufacture that is readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices. Program code may be applied to data entered using an input device to perform any of the processes described herein and to generate output information.

The system may be implemented, at least in part, via a computer program product, (e.g., in a non-transitory machine-readable storage medium such as, for example, a non-transitory computer-readable medium), for execution by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers)). Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the programs may be implemented in assembly or machine language. The language may be a compiled or an interpreted language and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network. A computer program may be stored on a non-transitory machine-readable medium that is readable by a general or special purpose programmable computer for configuring and operating the computer when the non-transitory machine-readable medium is read by the computer to perform the processes described herein. For example, the processes described herein may also be implemented as a non-transitory machine-readable storage medium, configured with a computer program, where upon execution, instructions in the computer program cause the computer to operate in accordance with the processes. A non-transitory machine-readable medium may include but is not limited to a hard drive, compact disc, flash memory, non-volatile memory, volatile memory, magnetic diskette and so forth but does not include a transitory signal per se.

The processes described herein are not limited to the specific examples described. For example, the process 200 is not limited to the specific processing order of FIG. 2. Rather, any of the processing blocks of FIG. 2 may be re-ordered, combined or removed, performed in parallel or in serial, as necessary, to achieve the results set forth above.

The processing blocks (for example, in the process 200) associated with implementing the system may be performed by one or more programmable processors executing one or more computer programs to perform the functions of the system. All or part of the system may be implemented as, special purpose logic circuitry (e.g., an FPGA (field-programmable gate array) and/or an ASIC (application-specific integrated circuit)). All or part of the system may be implemented using electronic hardware circuitry that include electronic devices such as, for example, at least one of a processor, a memory, a programmable logic device or a logic gate.

Elements of different embodiments described herein may be combined to form other embodiments not specifically set forth above. Other embodiments not specifically described herein are also within the scope of the following claims.