Abstract: Iteratively determining compliance of a backup system with a service level agreement (SLA) of service level policies (SLPs), including receiving an SLP having a data management schedule and indicating a first backup time of a first backup job; determining an SLP schedule type of windowed or continuous based on the SLP, and a first compliance analysis time based on the SLP schedule type and the first backup time; determining a first monitoring event associated with the first compliance analysis time and with a first compliance analysis type; performing a first compliance analysis of the first compliance analysis type to generate a first compliance status of the first monitoring event; and creating a second monitoring event associated with a second analysis time based on the first compliance status, and with a second compliance analysis type, and being based on the first compliance status.

Abstract: Techniques include systems, computerized methods and computer readable media for creating a private network for one or more execution environments inside of an existing network using a data center container, such that the private network can provide one or more services that are independent of identical services of the existing network. A private network is created in an existing network. A data center container provides a service in the private network that is identical to an existing service provided by the existing network. A data center container manager manages execution of one or more execution environments in the data center container using the service in the private network, such that the one or more execution environments can execute in the private network using the service without interfering with the operation of the existing service in the existing network.

Abstract: Computerized systems and methods are provided for integrating copy data tokens with source code repositories. A first command associated with the version control system stores in the memory a copy of source code and a copy of the data token from the remote repository, comprising source data and mount data. A second command associated with the version control system is executed to create a version of the source code stored in the memory. Based on the execution of the second command a working copy of the copy data is created based on the data token for use with the version of the source code, comprising creating a copy of the copy data from the data source based on the source data, and mounting the working copy to the device based on the mount data, thereby automatically managing the copy data for the version control system.

Abstract: Computerized systems and methods are provided for data virtualization using copy data tokens. A data token is stored that defines attributes associated with copy data, including source data, transformation data, and access data for the copy data. The access data is indicative of a set of access settings for the copy data that define how an instance of the copy data is to be created for the user, and a set of access permissions for the copy data that define an access level for the user for the copy data that defines how much of the copy data the user can access. The data token is transmitted to a remote computer storing the copy data based on the source data in the data token. A copy of the copy data that was generated based on the preparation information and the access data is received.

Abstract: Systems and methods of capturing application data locally on a source data management system and performing a high performance, bandwidth optimized replication the data from the source data management system to a remote data management system either (a) in parallel with copying data from an application to the source data management system, or (b) serially by replicating the data to the remote data management system after the data is copied to the source data management system, wherein the determination to operate in parallel or serially is based on at least one of a characteristic of the data and user specified tuning parameters.

Abstract: Systems and methods of enabling a service level agreement to specify interactions between an application and a remotely located object store that manages data as objects. A computing device receives data associated with a request to write application data to an object store according to a schedule, wherein the data is file system data. The computing device creates a snapshot associated with the requested application at a snapshot pool, and transmits instructions to a cloud formatting engine to create a virtual disk at a storage pool associated with an object store. The computing device copies the snapshot from the snapshot pool to the virtual disk, the snapshot comprising file system data and transmits instructions to the cloud formatting engine to convert the data associated with the first snapshot into an object, and move the object from the virtual disk to the object store.

Abstract: Systems and methods of providing search capabilities for data backups by indexing multiple time-based versions of the data backups such that the multiple time-based versions of each of the data backups are factored into a search result. First data associated with a first backup of a data set is received, the first data including a list of changes associated with the data set between a first backup and a second backup. For each of the first backup, second backup and one or more intermediary backups an index representative of difference data is created. Second data associated with a search request is received. A version of the file is retrieved based on the search request, thereby providing search capabilities for data backups by indexing data backups at a plurality of backup times such that multiple versions of each of the data backups are factored into a search result.

Abstract: Techniques disclosed herein provide for global management of a set of data management services being executed by at least one of one or more physical data management appliances and one or more virtual data management appliances. First instructions are transmitted to a first copy data management appliance that cause the first copy data management appliance to send first data associated with protecting a first application entity to the management server. Second instructions are transmitted to a second copy data management appliance that cause the second copy data management appliance to send second data associated with protecting a second application entity to the management server. A plurality of data management policies associated with the first copy data management appliance and the second copy data management appliance are scheduled using a third service level template, which includes a merged set of schedules for the first and second copy data management appliances.

Abstract: Systems and methods are disclosed for managing deduplicated images of data objects that change over time. The method includes: organizing unique content of each data object as a plurality of content segments and storing the content segments in a data store; for each data object, creating an organized arrangement of hash structures, wherein each structure, for a subset of the hash structures, includes a hash signature for a corresponding content segment and is associated with a reference to the corresponding content segment, and for each data object, maintaining an organized arrangement of temporal structures to represent a corresponding data object over time, wherein each structure is associated with a temporal state of the data object, and wherein each temporal state is associated with the hash structures representing the content of the data object during that temporal state.

Abstract: Techniques are disclosed for preventing a user from configuring a service level agreement from creating a data management schedule that creates a set of data backups that exceeds data resource limits available for storing the set of data backups. A first amount of pool resources associated with the backup of each of the at least one application is determined according to a received schedule. A first amount of data volumes associated with the backup of each of the at least one application is determined according to the received schedule. A resource shortage warning is transmitted when the aggregate amount of pool resources exceeds an available amount of pool resources or the aggregate amount of data volume resource exceeds an available amount of data volume resource, thereby preventing a user from configuring a service level agreement that exceeds data resource limits.

Abstract: Systems and methods of utilizing multiple threads to facilitate parallel data copying to reduce an amount of time associated with backing up data. A request to copy application is received that indicates a number of available threads. A first available thread is used to select files from the application for backup. Selecting a file includes adding files to a work queue and creating backup work items associated with the work queue files. The files in the work queue are processed by a multiple threads in parallel such that an amount of time associated with backup up the application is reduced.

Abstract: Systems and methods for backing up clustered databases such that production backups associated with the clustered databases are restorable with near zero downtime. First data indicative of a backup request of a clustered database is transmitted by a first computing device to a second computing device. The first computing device maps the backup staging disks to each of a plurality of nodes. The second computing device adds the mapped staging disks to a backup staging diskgroup on a primary node. The second computing device mounts the backup staging diskgroup to each of the plurality of nodes. The second computing device executes a full backup from at least one of the plurality of nodes to the backup staging diskgroup. The second computing device transmits a catalog of backup information to a database associated with the first computing device. The first computing device creates a snapshot of the first backup staging disk.

Abstract: Systems and methods of backing up data to a replication target such that the data is recoverable from the replication target when a source application and one or more other intermediary replication targets are unavailable. A first deduplicated data object associated with an application is received at a first intermediary copy data management system based on a first schedule. The first deduplicated data object is replicated to generate at least one of a second deduplicated data object at a second copy data management system according to a second schedule.

Abstract: Systems and methods are disclosed for copying a data object to a target storage pool using a hybrid of storage pools, in which at least one of the storage pools of the hybrid is particularly efficient at identifying data that should be used for copying the data object to the target storage pool, and at least one of the storage pools of the hybrid is particularly efficient at retrieving the data that should be sent to the target storage pool. The system comprises a performance storage pool for storing data and having relatively high performance for retrieving stored data; a deduplicating storage pool for storing deduplicated data and storing metadata about data objects in the system and which has relatively high performance for identifying and specifying differences in a data object over time; and a controller for causing the performance storage pool to retrieve differences and provide the data to the target storage pool.

Abstract: Systems and methods of performing backup of databases and associated logs with one schedule such that a backup of both a database and its associated log can be restored or recovered to a desired point in time. A backup request associated with a backup type is received and defined by a service level agreement. The service level agreement includes a combined schedule for backing up both data stored in the database and log data associated with a database.

Abstract: Systems and methods for checking data integrity of a data object copied between storage pools in a storage system by comparing data samples copied from data objects. A series of successive copy operations are scheduled over time for copying a data object from a source data store to a target data store. A first data sample is generated based on a sampling scheme comprising an offset and a period. A second data sample is generated using a similar sampling scheme. The blocks of data in the first data sample and the second data sample are compared to determine if they differ to thereby indicate that the data object at the target store differs from the corresponding data object at the source data store.

Abstract: Systems and methods are disclosed for checking the data integrity of a data object copied between storage pools in a storage system by comparing data fingerprints of data objects, by scheduling a series of successive copy operations over time for copying a data object from a source data store to a target data store; generating a partial fingerprint of the data object at the source data store using a data fingerprinting operation that creates a fingerprint from a subset of data of the data object; sending the partial fingerprint of the data object to the target data store; sending any new data contents for the data object to the target data store; and creating a partial fingerprint of the data object at the target data store and comparing it to the partial fingerprint sent to the target data store to determine if they differ.

Abstract: Systems and methods are disclosed for a system for managing data in accordance with service level agreements (SLAs) that specify schedules on a calendar basis for performing prescribed data management functions and for reducing inter-function redundancy. This system may include a data management engine for performing data management functions, including at least a snapshot function, and at least one back-up function. The data management engine may include a service level policy engine that receives SLAs in electronic form and which controls the scheduling of the data management functions. Each electronic SLA may be associated with a corresponding application and may specify at least one service level policy, each policy specifying a source pool, a destination pool, a copy frequency, a retention period and schedule information. A collection of policies is capable of expressing a non-uniform schedule for when a given function should be performed.

Abstract: Systems and methods for facilitating test failover on a remote virtual machine without creating a full copy of the remote virtual machine. A snapshot is created of a remote virtual machine disk, the remote virtual machine disk protecting a source virtual machine disk. An instant, thin provisioned virtual machine is created from the snapshot, and the instant, thin provisioned virtual machine is powered on based on a received instruction to power on the instant, thin provisioned virtual machine thereby creating a running instance of a virtual machine, thereby facilitating test failover on the remote virtual machine without creating a full copy of the remote virtual machine.

Abstract: Systems and methods of orchestrating recoveries of virtual machines protected by a data management systems from a primary system to a secondary system, such that performing the recoveries depends on relationships between the virtual machines. First data indicative of a recovery plan associated with a failover of at least one group of virtual machines is received. The recovery plan includes an application group with data indicative of a hierarchical relationship between the virtual machines wherein each of the virtual machines is associated with an order based on the second data. A plurality of sequences is created in the application group to designate an order of executing a plurality of recoveries for each of the virtual machines. A first recovery is executed in parallel for each of the virtual machines associated with a first sequence and a subsequent recovery is executed in parallel for each of a subsequent set of sequences.