Emc Corporation

Dell Products Inc.

Emc IP Holding Company LLC

Ken Owens

Shelesh Chopra

Yasemin Ugur Ozekinci

Amarendra Behera

Jayashree Radha

Yasemin Ugur-Ozekinci

Anand Nadathur

Roger W Kilday

Navneet Upadhyay

Amith Ramachandran

Jayashree B Radha

Peter Armorer

Pawan Singh

Suavek Zajac

Brian Gardner

Anselmo J Barrero

Sunil Kumar Yadav

Krishnendu Bagchi

Asif Khan

Adrian Dobrean

Rejith Mohan M

Matt Buchman

Abhinash Kumar

Mahesh Biradar

System selects application hosts which meet update requirements, then downloads update for instances of application agent corresponding to selected application hosts. System puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. System creates backup copy of state of instances of application agent. System generates installation instructions that, when executed by update sessions to install update, enable roll back from updated instances of application agent to state of instances of application agent recorded in backup copy. System initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions failed to install update in any instances of application agent in cluster of application hosts, system rolls back update for updated instances of application agents in cluster to previous conditions and configurations of instances of application agents.

Generating installation software that rolls back agent updates when cluster updates fail

System enables selection of application hosts which meet update requirements, then downloads update for instances of application agent corresponding to selected application hosts. System puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. System creates copy of instructions, which when executed, installs update in instance of application agent in one of application hosts, and reports on update process to server which communicates with application hosts. System launches worker process from copy of instructions. System initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions failed to install update in any of instances of application agent in cluster of application hosts, system rolls back update for updated instances of application agents in cluster of application hosts to previous conditions of instances of application agents.

Launching copies of installation software that rolls back agent updates when cluster updates fail

Agent lifecycle management for backup and restore applications is described. A system enables selection of application hosts, each of which meets installation requirements for installing instances of application agents from a backup and restore application, then downloads, in parallel, the instances of the application agent to the corresponding selected application hosts. The system installs, in parallel, the instances of the application agent in the corresponding selected application hosts, then registers, in parallel, the instances of the application agent with the backup and restore application. The system subsequently initiates sessions which download and install, in parallel, an update in instances of the application agent in in corresponding application hosts. The system unregisters at least one of the instances of the application agent, in at least one application host, from the backup and restore application. The system decommissions the at least one application host from protection by the backup and restore application.

Agent lifecycle management for backup and restore applications

Automatically updating agents from backup and restore applications is described. A system enables selection of application hosts which meet update requirements, then downloads an update for instances of an application agent corresponding to selected application hosts. The system puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. The system initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions did not fail to install update in any of instances of application agent in cluster of application hosts, then the system stores the updated instances of the application agents in a non-volatile storage.

Automatically updating agents from backup and restore applications

Creating vendor-neutral data protection operations for vendors' application resources is described. Capabilities specified for data protection operations by a vendor of an application are input from a host of the application. Any capabilities specified for the data protection operations are used to create a vendor-neutral version of a data protection operation for a resource of the application. The vendor-neutral version of the data protection operation for the application resource is output to the host. A result of performing the vendor-neutral version of the data protection operation on the application resource is input from the host.

Creating vendor-neutral data protection operations for vendors' application resources

Vendor-neutral models of vendors' application resources are described. A host outputs capabilities of data protection operations which are specified by a vendor of an application that is installed on the host. The host inputs a vendor-neutral version of a data protection operation, based on any of the capabilities, for a resource of the application. The host uses a vendor-neutral model of the resource of the application to perform the vendor-neutral version of the data protection operation on the application resource.

Vendor-neutral models of vendors' application resources

System extracts metadata of system committed change numbers, system change numbers for backup copies. System generates start system change numbers as minimums of committed change numbers, end system change numbers as maximums of change numbers, and identifiers for archive log backup copies. System identifies dependent system change numbers from start number to end number for backup copy. System identifies backed-up system change numbers, from start numbers to end numbers for log backup copies, which are in dependent numbers. If backed-up numbers don't include all dependent numbers, system outputs missing system change numbers. System generates start numbers, end numbers, and identifiers for new archive log backup copies, identifies new backed-up system change numbers, from start numbers to end numbers for new log backup copies, which are in missing numbers. If new backed-up numbers include all missing numbers, system stores backup copy with each log backup copy corresponding to any backed-up numbers.

Dynamically updating database archive log dependency and backup copy recoverability

Backing up data blocks is disclosed, including: receiving an indication that a first backed up data block is to be processed; determining that the first backed up data block and a second backed up data block are related at an application level and are to remain stored together; and processing together the first and second backed up data blocks based at least in part on the determination that the first and second backed up data blocks are related at an application level and are to remain stored together.

Save set bundling for staging

Backing up data blocks is disclosed. An indication that a first set of one or more backed up data blocks are related at an application level to one or more other sets of one or more backed up data blocks is received. An associating data that associates the first set of backed up data blocks with the one or more other sets of backed up data blocks is stored. The associating data is used to ensure that the first set and the one or more other sets remain stored together.

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.

Automated backup and recovery for content repository

Performing a backup is disclosed. One or more directories at a lowest level in a file directory associated with a storage is identified. The identified lowest level directories are divided into one or more directory groups. The backup of the directory groups is performed using parallel threads until all directory groups have been backed up.

Growing community of inventors

Burlington, Canada

Ken Owens