Emc IP Holding Company LLC

Ajith Gopinath

Kishore Krishna Kumar

Sathyamoorthy Viswanathan

Shelesh Chopra

Gururaj Reddy Kulkarni

Chetan Battal

Hareej G Hebbur

Harsh Sharma

Sathayamoorthy Viswanathan

Techniques to back up data associated with a cluster environment are disclosed. In various embodiments, an indication is received to back up data associated with the cluster. A backup configuration data associated with the cluster is used to back up, in a unified backup operation, one or more save sets associated with virtual resources associated with the cluster and one or more saves sets associated with physical nodes associated with the cluster, including by storing each respective save set in a manner that associates the save set with a virtual or physical node comprising the cluster suite.

Unified protection of cluster suite

Techniques to back up a cluster resource are disclosed. In various embodiments, an active cluster node is used to take and store persistently on a cluster shared volume a snapshot of the cluster shared volume. The persistent snapshot is used to back up the cluster shared volume, including by storing checkpoint information indicating as the backup progresses which portions of the snapshot have been backed up. A cluster environment with which the cluster shared volume is associated is monitored to detect any failover or failback affecting the backup.

Data protection using checkpoint restart for cluster shared resources

A rule specifies a data change percent and a backup level to use corresponding to the data change percent. The backup level may be a full backup or a non-full backup. Before backing up a source for an impending backup, a percent of data change of the source from a last backup of the source to the impending backup is calculated. The rule is evaluated against the calculated percent change to select a backup level for the impending backup. Based on the evaluation, the full backup level or non-full backup level is selected and the source is backed up according to the selected backup level.

Intelligent selection of backup levels

Embodiments are directed to a method of regulating client agent backup jobs in a backup server by defining a server parallelism value specifying a maximum number of active backup jobs that can be simultaneously performed by the backup server, maintaining a plurality of queues in memory and including an active queue storing active backup jobs comprising a number of current backup jobs not exceeding the server parallelism value, and one or more overflow queues storing backup jobs exceeding the server parallelism value, receiving backup job requests from a plurality of clients and processing the received backup job requests through the plurality of queues, and transmitting a hold command to the plurality of clients if the plurality of queues are full. The overflow queues may comprise a wait queue and a sleep queue.

Multi-queue based system for throttling backup agent save processes

A method for recovering data from one or more storage systems for a group recovery. In response to receiving a request for the group recovery, the method implemented at a backup server identifies a group recovery resource based on the request, where the group recovery resource includes one or more recovery item lists. The backup server traverses the one or more recovery item lists of the group recovery resource to determine a source recovery storage system, target recovery storage systems, and one or more data items to be recovered to each of the target recovery storage systems. The backup server then initiates one or more recovery sessions to recover the one or more data items from the source recovery storage systems to the recovery target storage systems substantially concurrently.

Method and system for performing group recovery from a recovery source to multiple recovery targets

Techniques to back up a cluster shared volume (CSV) are disclosed. In various embodiments, a snapshot of the cluster shared volume is stored persistently on the cluster shared volume itself. A task to back up a corresponding assigned portion of the snapshot is assigned to each of one or more cluster servers available to participate in backing up the cluster shared volume. The cluster servers have shared access to the snapshot as stored on the cluster shared volume, and each is configured to perform the task assigned to it in parallel with any other cluster servers assigned to back up other portions of the same cluster shared volume snapshot. The respective assigned tasks are monitored to completion.

Growing community of inventors

Bengaluru, India

Ajith Gopinath