Abstract: Tracking files which have been processed by a backup/restore operation. A request to perform a backup/restore operation for files on a target computer may be received at the target computer. The request may be received from a server computer. Information regarding which files on the target computer have been processed by the backup/restore operation may be maintained by the target computer. The information may be configured to be used for restart of the backup/restore operation at a requested file. Maintaining the information may include storing file identifiers into a data structure on the target computer corresponding to files that have processed by the backup/restore operation.

Abstract: A technique for restoring file systems by applying full and incremental backups together while streaming them from multiple devices provides a faster system restore from a full backup where incremental backups must also be applied. A first storage device streams the full backup while at least one second storage device streams at least one incremental backup. As files are detected in the incremental backup, they are written instead of the corresponding file in the full backup. Incremental backups can be pre-merged to reduce their number to one less than a number of storage devices available to stream the backups, so that the full backup can be streamed along with the pre-merged incremental backup(s) to restore the file system.

Abstract: A system and method for restoring a web site previously defined with user customizations by an intranet portal application. A backup agent receives a restore request for a backed up web site. Restored data is used by the intranet portal application in order to rebuild the web site according to a predetermined template. Use of the template results in a rebuilt database which does not match the database originally backed up. For one or more identifiers being added, one or more new globally unique identifiers (GUIDs) are generated by the application to replace the identifiers. The backup agent queries the application to receive new GUIDs for a selected level of the hierarchy of the web site. The backup agent updates a mapping of IDs with the new GUIDs. The backup agent uses the mapping to identify differences between the rebuilt database and the database represented by the backup copy of the database.

Abstract: Techniques for transferring objects between database systems. A transfer is controlled by a master table in the RDBMS that is performing the transfer operation. The master table specifies the kind of transfer operation to be performed, a set of objects to be transferred, operations to be performed on the objects as they are being transferred, and filters for selecting a subset of the objects. During execution of the transfer, the transfer mechanism maintains and updates state in the master table and thereby makes it possible for the entity that is doing the transfer to determine the current status of the transfer and to restart the transfer after it has been stopped. The entity that is performing the transfer may also detach from the transfer without stopping the transfer and later again attach to the transfer.

Abstract: A technique for restoring file systems by applying full and incremental backups together while streaming them from multiple devices provides a faster system restore from a full backup where incremental backups must also be applied. A first storage device streams the full backup while at least one second storage device streams at least one incremental backup. As files are detected in the incremental backup, they are written instead of the corresponding file in the full backup. Incremental backups can be pre-merged to reduce their number to one less than a number of storage devices available to stream the backups, so that the full backup can be streamed along with the pre-merged incremental backup(s) to restore the file system.

Abstract: Query processing statistics are logged in a multi-database system containing a plurality of system databases. A plurality of query log entries generated using information regarding the execution of a plurality of queries are temporarily stored in a database query log (DBQL). The information is received from a plurality of system databases. Each query log entry is generated using information regarding execution of one query by the plurality of system databases. Each query log entry includes a field identifying a system database that was the source of the information in that entry. An express request is created upon occurrence of a triggering event. The express request contains a subset of the query log entries temporarily stored in the DBQL cache. The created express request is transmitted to a plurality of system databases and the contents of the transmitted express request are stored in each of plurality of system databases to which it was transmitted.

Abstract: A cluster manager is configured to manage a plurality of copies of a mid-tier database as a mid-tier database cluster. The cluster manager may concurrently manage a backend database system. The cluster manager is configured to monitor for and react to failures of mid-tier database nodes. The cluster manager may react to a mid-tier database failure by, for example, assigning a new active node, creating a new standby node, creating new copies of the mid-tier databases, implementing new replication or backup schemes, reassigning the node's virtual address to another node, or relocating applications that were directly linked to the mid-tier database to another host. Each node or an associated agent may configure the cluster manager to behave in this fashion during initialization, based on common cluster configuration information. Each copy of the mid-tier database may be, for example, a memory resident database. Thus, a node must reload the entire database into memory to recover a copy of the database.

Abstract: Systems and methods for performing hierarchical storage operations on electronic data in a computer network are provided. In one embodiment, the present invention may store electronic data from a network device to a network attached storage (NAS) device pursuant to certain storage criteria. The data stored on the NAS may be migrated to a secondary storage and a stub file having a pointer pointing to the secondary storage may be put at the location the data was previously stored on the NAS. The stub file may redirect the network device to the secondary storage if a read request for the data is received from the network device.

Abstract: Data is processed by receiving a list of one or more file system elements in a level of a file system or a portion thereof. The list is sorted based at least in part on whether a file system element is a file or a directory. A sorted list is obtained. The file system elements in the level are backed up according to the order of the sorted list.

Abstract: This disclosure describes systems and methods for programmatically determining whether to perform full or partial backups. In some implementations, functionality is provided for intelligently escalating to a full backup based on one or more user-supplied escalation parameters. The escalation parameters can include a threshold of data change between backup files, which if exceeded, can result in escalation to a full backup. The escalation parameters can also include time parameters, computing resource consumption parameters, and other features that can govern full backup escalation. Additional features of the systems and methods described herein can include automatic adjustment of escalation parameters, multi-leveled backup set validation, and intelligent backup file cleanup.

Abstract: A method and apparatus for deduplication of files of a storage system is described. During a gathering phase, a file may be simultaneously processed by two or more threads to produce and store content identifiers for data blocks of the file. Each file may be sub-divided into multiple file sub-portions, each file sub-portion comprising a predetermined number of data blocks. A thread may be assigned to each sub-portion of a file for processing the data blocks. The currently assigned sub-portion for each thread may be recorded and used upon a system crash to restart each scanner thread at the currently assigned sub-portion to minimize the data blocks that are re-processed. The size of a file sub-portion may be predetermined based on the organization of inode data structures representing the files (e.g., based on the maximum number of pointers that an indirect block in the inode data structure may contain).

Abstract: System and method for reducing costs of moving data between two or more of multi-tiered storage devices. Specifically, the system operates by moving only high tier portion of data and merely remapping the low tier data to migration target device, which eliminates a large amount of data movement (low tier) while maintaining the SLA of high tier data. Specifically, when a command to migrate a thin provisioned volume is received from a source primary storage device to another target primary storage device, the system doesn't copy all of the tier1 and tier2 chunk data that the source thin provisioned volume holds, but copies only tier1 chunk data to the target storage device. The copy operation is performed after the storage system prepared the target thin provisioned volume on the target side. After that, tier2 chunks are remapped from the primary storage device to another target primary storage device without copying.

Abstract: A system and method for server recovery and migration is presented. The method comprises backing up data and device drivers on a server to a central location, logging-in to the central location, obtaining the backed up data and device drivers from the central location, copying the obtained data to a computer medium and booting the server using the computer medium. In one aspect, the method can further comprise determining whether recovery is needed and performing logging-in, obtaining, copying, and booting when the recovery is needed. In one aspect, the method can further comprise determining whether the server has new device drivers and backing up the device drivers when the server has new device drivers. In one aspect, the backing up is performed periodically. In one aspect, the computer medium is a CD. In one aspect, the obtained backed up data is an ISO file.

Abstract: A file recording device includes a control unit (101) that controls a batch copy process which copies collectively a plurality of files stored in a first recording medium (300) from the first recording medium (300) to a second recording medium (106). When a batch copy process is completed, the control unit (101) records copy date and time identification information for identifying copy completion date and time to the first recording medium. The control unit (101) performs the control so as to compare the batch copy completion date and time indicated by the copy date and time identification information with recording date and time information on files stored in the first recording medium, to identify a file recorded in the first recording medium (300) later than the date and time on which the batch copy is performed, and then to copy the identified file to the second recording medium (106).

Abstract: A disk drive is disclosed comprising a disk, and a head actuated over the disk. Control circuitry within the disk drive is operable to write a plurality of code segments to a primary area of the disk, and write the code segments to a backup area of the disk. The control circuitry reads the code segments from the primary area of the disk and executes the code segments read from the primary area of the disk. After reading the code segments from the primary area of the disk and executing the code segments, the control circuitry verifies recoverability of the code segments from the backup area of the disk, and when the verification fails, copies the code segments from the primary area of the disk to the backup area of the disk.

Abstract: A server apparatus performs data I/O processing on a P-VOL in response to a request from a client apparatus and includes a file system which receives data write and read requests in units of files from the client apparatus. The server apparatus stores, into a D-VOL, differential data generated by updating the P-VOL, and manages a snapshot management table wherein a block address of the D-VOL storing the acquired differential data is registered. When a remaining capacity of a storage area of the D-VOL becomes equal to or less than a predetermined threshold value, the server apparatus enables a block of the D-VOL which had stored therein the differential data on a certain predetermined file, to be used as a storage area for newly acquired differential data.

Abstract: A server auditing process that stores only a single up-to-date data record along with the differences relative to previous changes in the record that allow the user to move “backward in time” to recreate previous values. The auditing feature introduces a baseline database table and a difference database table for each existing database table. The baseline table stores the most recent auditing data and the differences table complements the baseline table by storing pairs in the form of attribute name and previous value. By applying difference rows to baseline data, the user is able to recreate the data as it existed at any given timestamp and at a minimal storage cost. The architecture minimizes the impact of auditing on system performance by employing an asynchronous priority queue so that task processing is deferred until the system has adequate resources and other work is not affected.

Abstract: A medical image filing system comprises a primary storage device and a secondary storage device. In addition, the medical image filing system comprising: an image secondary storage condition setting unit for presetting a secondary storage condition to secondarily store a medical image data to the secondary storage device; an image secondary storage determining unit for determining whether or not the medical image data recorded to the primary storage device satisfies the secondary storage condition set by the image secondary storage condition setting unit; and an image recording unit for recording the medical image data of the secondary storage object to the secondary storage device. Therefore, only medical image data of the secondary storage object is stored in the secondary storage device.

Abstract: Method and system for incremental backup of data containers with fixed length records is provided. Initially, a backup application copies all stored data containers to create an initial backup container. A data structure corresponding to the first backup operation is also created. The data structure maintains unique file identifiers for each data container and information regarding when a record was added. The data structure is created and maintained by an application that also creates, updates, and modifies the fixed length records. The application updates the base data structure when records are added to a data container, after the initial backup. For a next backup operation, the initial data structure is compared to an updated data structure that is current at the next backup time. The comparison identifies the new records that were added (or updated) since the initial backup operation. The backup application then incrementally copies the new records.

Abstract: Systems and methods for managing electronic data are disclosed. Various data management operations can be performed based on a metabase formed from metadata. Such metadata can be identified from an index of data interactions generated by a journaling module, and obtained from their associated data objects stored in one or more storage devices. In various embodiments, such processing of the index and storing of the metadata can facilitate, for example, enhanced data management operations, enhanced data identification operations, enhanced storage operations, data classification for organizing and storing the metadata, cataloging of metadata for the stored metadata, and/or user interfaces for managing data. In various embodiments, the metabase can be configured in different ways. For example, the metabase can be stored separately from the data objects so as to allow obtaining of information about the data objects without accessing the data objects or a data structure used by a file system.

Abstract: Data uploaded from a mobile unit to a remote site can be buffered at an intermediate wireless base station, allowing an initial wireless link to be rapidly terminated and freed for other uses. In one implementation, a method includes forming a wireless link between a device and a first wireless receiver site, receiving a portion of a data set from the device, relinquishing the wireless link, and then transmitting the portion of the data set from the first wireless receiver site to a service provider. In another implementation, a method includes receiving, via an intermediate wireless base station, a backup request and a portion of data to be backed up from a device. The portion of the data to be backed up is received after a wireless link between the device and the wireless base station has been terminated.

Abstract: A method and apparatus for managing locks in a database system is provided. A master node grants a lock on a first resource and a group of resources that includes the first resource to a first requester node. The requester node receives a mapping corresponding to the group of resources that may indicate that a lock already exists for a second resource in the group. If the requester node desires a lock on a resource located in the group, the requester node grants itself the lock without notifying the master node. A second requester node requests a lock for a particular resource in the group of resources. The first requester node grants the lock on the particular resource and updates the mapping to indicate that a different node holds a lock for the particular resource.

Abstract: A method and system for obtaining past information in a generic manner. For a certain time point, obtaining a copy of the process object, including its structure and data from recorded changes. When setting up the process object, an action rule is associated with the process object to automate that any change in the data content and/or structure is recorded with an associated time of the change. In response to a request for past information, steps are taken to acquire past data, acquire past change data, and create a temporary object to simulate the object that would have existed at the specific time requested.

Abstract: Provided is a method, system and program for backing up the contents of a source storage device as an object in a data storage subsystem wherein the object contains image data representing the contents of the source storage device, and restoring the contents of the source storage device from the object to a file such as a flat file. The contents of the file may be copied to a target storage device to restore the contents of the source storage device from the file to the target storage device which may be the source storage device or another target storage device.

Abstract: A system and method for archiving a user's media collection are provided. In general, a central archiving system stores high-quality versions of a number of known media files and a number of known encoding algorithms. First, each media file in the user's media collection and an encoding algorithm used to encode each media file are classified as either known or unknown to the archiving server. For each known media file encoded with a known encoding algorithm, the archive includes information identifying the media file, information identifying the encoding algorithm for the media file, and optionally the one or more quality parameters such as bit rate, sampling frequency, and the like for the media file. For each unknown media file and/or media file encoded with an unknown CODEC or encoding algorithm, the archive includes the media file, which is uploaded and stored at the archiving system.

Abstract: A method and system for generating and restoring a backup image are disclosed. A server receives a request, which includes a backup path, to generate a backup image. The server generates a backup image offset map that indicates a relative location where a file is stored in the backup image before file data has been written to the backup image. The server stores the backup image offset map in a portion of the backup image on a storage device. The backup image offset map comprises an array having a number of elements equal to a number of inodes on a file system that hosts a backup path, an element of the array representing an inode on the file system, and indicates the relative location where a file that is associated with a number of the inode is stored in the backup image.

Abstract: Computer file storage, backup, restore and retrieval is disclosed. A method includes providing a restore file interface allowing a user to restore a plurality of files based on a plurality of filter options, the files stored on multiple local and/or remote storage devices, computing devices, servers, and clouds. A filter option selection is received from the user, and filter details may also be received from the user. An available file list may be prepared based on the filter option selection and, if received, the filter details. A user selection from the available file list may be received. The user selected files are retrieved from one or more appropriate storage devices, computing devices, servers, and clouds. The method may be performed by software executing on a computing device.

Abstract: Provided are a method, system, and article of manufacture for backing-up and restoring files including files referenced with multiple file names. Files to backup are determined. A determination is made from the files to backup files referenced with multiple names. An entry is created for each file to backup in a backup directory indicating file attributes and each name used to reference the file. The determined files and the backup directory are backed-up.

Abstract: A mechanism is provided for archiving and restoring transaction files of a database system without requiring the copying of the transaction files. A server system executes a host application that implements the database system comprising a set of database files and a set of transaction files that contains updates to the set of database files, the files being stored in a storage system. A backup engine interacts with the host application to archive a transaction file having an original filename in an original directory by creating a corresponding archive filename to the transaction file in an archive directory. The archive transaction files may be used later to perform a copy-less restore process of the database system that does not require copying of any transaction files. The copy-less restore process restores any altered original filenames by replacing, in the original directory, an altered original filename with its corresponding archive filename.

Abstract: Provided is a computer system which is capable of backup operation with a minimum count of volumes in a remote copy environment when a disaster or the like causes a storage system to stop working normally. The computer system has a host computer, a first storage system, a second storage system, and a management computer. The first storage system contains a data volume which stores data requested by an application to be written. The second storage system contains a mirrored volume to which data stored in the data volume is copied. The computer system is characterized by being configured to receive an input of a policy about backup processing executed in backup volumes and set a configuration of the first storage system and a configuration of the second storage system under the received policy.

Abstract: Provided is a database schema migration difference detecting technique for detecting differences of a customized database schema before and after database migration by using XML technology, including: extracting a first database schema from a fresh database of a release and saving the first database schema in a first XML file; extracting a customized database schema from a customized database of the release and saving the customized database schema in a second XML file; comparing the first and second XML files, filtering the identical content in the first and second XML files and saving differences in a delta XML file; and comparing the delta XML file with a new database to detect a state of the customized database schema after migration. The detecting state indicates whether there is any loss or change in the customized database schema after migration, as well as, conflicts with the database schema in a database of a new release.

Abstract: A system for onsite backup of internet-based data is provided. The system includes a central computer, a client computer, a communications link between the central computer and the Internet, and a communications link between the client computer and the Internet. The system also includes at least one database containing a plurality of data records accessible by the central computer, each data record containing a client identification number. Software executing on the central computer receives a data backup request, and software executing on the central computer transmits the data backup to the client computer.

Abstract: A method, article of manufacture, and apparatus for tracking a plurality of objects being stored are disclosed. In an embodiment, this comprises computing the hash value of the name of each object being stored, concatenating the hashed values into a hint, and storing the hint in an index. The size of the hash values is determined by dividing the number of objects into the space available for storing the concatenation, and the range of the hash values may be determined by choosing a prime number smaller than the number that can be represented by the space available for storing the concatenation. Either the hint or the longest pathname containing the objects can be stored, and this may be selected based on the application.

Abstract: A method of automatically classifying clients into different backup policy groups according to pre-selected criteria, such as type of client, whether the client is a server, a desktop or a mobile computer, the department or business unit, or even the user. The method uses information obtained from the client itself to classify the client. This information includes the kind of processor platform and operating system in the client, the type and version of software being run, and whether the client has a battery, indicating that it is a mobile computer. Other information that can be used to classify the client for backup may be obtained from information that identifies the user, the department to which the client is assigned, and the location in which it is used. The process enables a mobile client traveling to another site of an enterprise to connect to a local LAN of the enterprise and be authenticated for backup, and to be automatically assigned an appropriate backup classification.

Abstract: Techniques for performing window-by-window remastering are described, in which the mechanism used by nodes to determine the resource-to-window mapping is separated from the mechanism used by the nodes to access resource information. For example, all nodes of a multiple-node system may use the same hash function to determine which resources are involved in a remastering window. However, the resource indexes employed by the nodes to access resource information need not use that same hash function. For example, in nodes where the resource indexes are hash indexes, different nodes may use different hash functions. Further, some or all of the nodes may use mechanisms other than hash indexes to access the resource information.

Abstract: A system for onsite backup of internet-based data is provided. The system includes a central computer, a client computer, a communications link between the central computer and the Internet, and a communications link between the client computer and the Internet. The system also includes at least one database containing a plurality of data records accessible by the central computer, each data record containing a client identification number. Software executing on the central computer receives a data backup request, and software executing on the central computer transmits the data backup to the client computer.

Abstract: A rollback support method for transactions a node among nodes in a distributed system, including modifying a disposable cache copy of data as part of transaction, propagating a version state and/or a data state of the modified cache to any of the nodes, verifying non-violation of a transaction semantic and/or a replication policy relating to the transaction, committing the transaction to any nodes if successful, revising a version state of other reliable replicas and disposable cache copies in the system based on the version state of the modified disposable cache copy, the disposable cache copies being members of a membership-based view, and updating a data state of other reliable replicas in the system based on the data state of the modified copy, and aborting the transaction if it fails, including restoring the disposable cache copy based on any reliable replicas and/or disposable cache copies in the system.

Abstract: A method for performing backup operations while avoiding data loss due to backup failure. A backup agent software receives a database server backup request and decomposes the backup request into a plurality of smaller backup requests. The plurality of smaller backup requests are then performed on the database to backup the specified database components to an archive. The backup agent software monitors success (or failure) of each of the plurality of backup requests and generates backup scripts for those backup requests that failed. These backup scripts may be subsequently executed to “re-run” the failed backups. The backup agent software is a modular program separate from the client application and the database server software.

Abstract: A system may present a document including a form. Forms content may be received into the form. The received forms content may be periodically and automatically saved to reduce the likelihood that received forms content is lost prior to form submission.

Abstract: In accordance with one embodiment of the present invention, a method for efficiently inventorying a plurality of items of media contained in a library is provided. The method includes reading a barcode located on an item of media that contains contents and determining whether the barcode is known. Optionally, the method may also determine if the know item of media was previously offline. If it is determined that the barcode is known, the media is identified as known. However, if it is determined that the barcode is not known, a detailed inventory of the contents of the item of media is performed. In one embodiment, if it is determined that the barcode is not known, a user is notified that a new item of media has been identified.

Abstract: Space on disk, designated for storage of recovery files is automatically managed so as to not exceed a predetermined limit. Specifically, after creation of information to be stored in a new recovery file, an automatic check is made to see if creation of the new recovery file will cause the space to exceed the limit. If so, at least one recovery file currently in the space is deleted. The new recovery file is automatically created, when the space occupied by existing recovery files becomes sufficiently small to accommodate the new file without exceeding the limit. The recovery file(s) deleted to make room for the new recovery file may be automatically identified in accordance with a user-specified policy. Such a policy may be used to automatically identify a subset of recovery files available for deletion, well ahead of time, i.e. prior to a need for deletion arises.

Abstract: A computer investigation system and method that conducts electronic discovery of desired files across a live network in a forensically sound manner. The investigation entails an examining machine electronically identifying, collecting, and preserving evidence from target machines that is responsive to a set of investigation criteria. The set of investigation criteria is associated with an investigation subject that is identified by a global unique identifier (GUID). As the investigation subject is applied to the various files, the responsive files are stamped with the GUID and preserved in a container file referred to as a logical evidence file (LEF). The GUID allows the results of an investigation to be easily and reliably traced to the particular investigation subject that was applied.

Abstract: Surgical sponges and other articles are provided with machine-readable information which provides a serial number or other unique identification of the sponge. In addition, the machine-readable information will provide the type of article and/or a characteristic visual motif associated with the article. That way, by scanning in the machine-readable information from the sponges or other articles prior to a procedure, the computer or other digital processor can determine which articles may be missing after the procedure and alert the surgical team as to the type and/or characteristic visual motif of the missing article.

Abstract: A source code control architecture. A client user checks out a copy of a source code file to the client using a file checkout process. A client cache maintains a pristine copy of the file, and a client activity list maintains a list of commands executed during the offline mode to effect modifications to the copy. The client cache contains a pristine copy of all source code files that are modified or deleted in a local client workspace. The cache is maintained whether the user is online or offline. When the user is offline, the cache is utilized to facilitate many of the activities that historically would require server connectivity. The command activity list allows a developer to continue changing the source code while offline by automatically recording the executed commands. The offline commands are reconciled to the server, and used to update the server file(s) when the client returns online.

Abstract: A system and method for archiving a user's media collection are provided. In general, a central archiving system stores high-quality versions of a number of known media files and a number of known encoding algorithms. First, each media file in the user's media collection and an encoding algorithm used to encode each media file are classified as either known or unknown to the archiving server. For each known media file encoded with a known encoding algorithm, the archive includes information identifying the media file, information identifying the encoding algorithm for the media file, and optionally the one or more quality parameters such as bit rate, sampling frequency, and the like for the media file. For each unknown media file and/or media file encoded with an unknown CODEC or encoding algorithm, the archive includes the media file, which is uploaded and stored at the archiving system.

Abstract: A network based system for archiving digital assets based on keywords associated with the digital assets is provided. In general, digital assets residing at a client node are each tagged with one or more keywords. One or more of the keywords are then identified as archiving keywords, thereby creating a list of archiving keywords. The list of archiving keywords is provided from the client node to a central node. The central node then provides a request to the client node for the digital assets tagged with the keywords in the list of archiving keywords. In response, the client node uploads the digital assets tagged with the keywords in the list of archiving keywords to the central node.

Abstract: A serverless backup system for backing up information on a network including one or more servers, includes a backup storage system for backing up information and a storage system for storing information to be backed up and restored, wherein information being backed up is transferred directly from the storage system to the backup storage system without going through a server and information being restored is transferred directly from the backup storage system to the storage system without going through the server.

Abstract: A method and apparatus for creating backup files by creating an overhead segment for each file that is to be backed up and creating a data segment containing the data that is to be backed up for each file. After creating overhead segment and the data segment, the overhead segment is placed into an overhead stream and the data segment is stored in a memory. The overhead segment is also positioned in the overhead stream with a pointer that identifies the location of the data within the memory. As such, the backup file comprises a data segment and an overhead stream.

Abstract: A method and system are disclosed for transparent backup to a hierarchical storage system. A data management application requests a backup operation, communicating the request using the Network Data Management Protocol with a tape server and a data server. The tape server generates a unique identifier for the data set. In addition, the tape server transfers the data set from the data server to the hierarchical storage system and sends the identifier to the data management application in response to the request. The identifier identifies the data set within the hierarchical storage system. In a certain embodiment, the tape server stores and manages the data set in locations transparent to the data management application. The tape server and data management application may be logically distinct. The data management application may access the data set through the tape server using the identifier.

Abstract: Performing a backup is disclosed. A first set of data associated with a second set of data is backed up. The first set of data is made available for use before backing up the second set of data. The second set of data is backed up within a prescribed interval after completing the backup of the first set of data. One of the first set of data and the second set data comprises metadata associated with the other of the first set of data and the second set of data and the other comprises one or more items of managed content.