Emc Corporation

Patrick M Simonich

Upanshu Singhal

Matthew Dickey Buchman

Janet Lynn Schneider

Eric Alfred Herrmann

Scott Forrest Bingham

Dianne C Thompson

Carolina P Uhlmann

Nathan Kryger

George Shioyama

Mu Chai

Aditya Kapoor

Peter Armorer

Michael Jones

Troy Thompson

Tom Frencel

Rock Brown

Jeff Beeghly

A method for restoring associated with a collaborative software application is disclosed. A virtual file system exposing backup data of a collaborative software application stored in a backup data storage is created. A selection of a portion of the backup data to be restored to the collaborative software application is received via an interface associated with the virtual file system. The selected portion of the backup data is caused to be granularly restored to the collaborative management system without restoring one or more unselected portions of the backup data. A write capability of the virtual file system is used to modify a portion of the restored data in response to a write operation by the collaborative software application.

Write capable exchange granular level recoveries

An application framework is disclosed for handling predefined events for various application modules executing as threads. Events are received and associated with a thread and an event handling function. Event handling functions are classified as mutually exclusive and non-mutually exclusive. Mutually exclusive functions are blocked while another mutually exclusive function is executing. Event handling functions are processed by setting a corresponding thread to execute the function and placing the thread in a 'non-wait' state. Threads in the 'non-wait' state are then executed concurrently under the control of a system thread manger and are returned to a &#x2018;wait&#x2019; state when the handling function ends. Each such thread maintains the session state throughout use of the application.

User interface for event-driven state thread architecture

Systems and methods for backing up and/or restoring data. When a backup operation is initiated, systems and methods are provided for creating a single snapshot of the backup items, including backup groupings. The single snapshot is used by a backup/recovery application to perform a save process on each backup grouping. By using the same snapshot, the backup is performed based on the same point in time so that the backed up data across the client system is consistent and synchronized. When a recovery operation is initiated, recovery items (e.g., backup groupings, writers and writer components) are selected from backup grouping of the client.

Creation of a single snapshot using a server job request

Systems and methods for performing scheduled backups and recovery of data generated by one or more production applications operating on a MAGIC platform located on two or more host computers in a coherency group. The data for a coherency group is stored in a primary storage in the form of one or more production volumes and ISB protocol is used to create one or more clone volumes. Exemplary methods for backing up one or more clone volumes for a coherency group to a backup storage include copying the one or more clone volumes to a backup storage or creating a snapshot of the one or more clone volumes. The ISB functions of splitting and/or reconnecting the one or more production volumes and one or more clone volumes occur at substantially the same time for all the two or more host computers in the coherency group.

Backup and restore operations using coherency groups for ISB protocol systems

Systems and methods for backing up and/or restoring data. When a backup operation is initiated, systems and methods are provided for creating a single snapshot of the backup items, including backup groupings. The single snapshot is used by a backup/recovery application to perform a save process on each backup grouping. By using the same snapshot, the backup is performed based on the same point in time so that the backed up data across the client system is consistent and synchronized. When a recovery operation is initiated, recovery items (e.g., backup groupings, writers and writer components) are selected from backup groupings of the client.

Creation of a single client snapshot using a client utility

Methods and systems for backing up data of a client connected to a server. The methods and systems include operating a graphical user interface for displaying to a user information about the data of a client. At an administrator module and client module, initiating one or more wizard program modules including dynamic link libraries configured to carry a user through the steps to complete a backup function, each wizard program module having one or more application programming interfaces which allow the wizard program modules to communicate with the operating system on which the administrator module or client module is operating. A common presentation layer can also be included to provide one or more common user interface screens which are insertable into each wizard program module.

Software configuration methods and common presentation layer

A method and system for performing multiple concurrent recovery operations using a single instance of a user interface. One exemplary method includes initiating a first recovery operation via a single user interface. The first recovery operation includes copying a first data object from a first backup storage location to a first recovery storage location. The exemplary method further includes initiating a second recovery operation via the single user interface without requiring a user to open a separate instance of the user interface. Similarly, the second recovery operation includes copying a second data object from a second backup storage location to a second recovery storage location. At least a portion of the second recovery operation occurs concurrently with at least a portion of the first recovery operation.

Multiple concurrent restore using same user interface

A method and system for restoring data on a production server by recovering individual data objects from a recovery storage group to a database residing on the production server. In one example method, a recovery interface accesses a recovery storage group containing a recovered database. The recovered database has been recovered from a backup storage location and contains a copy of a database residing on the production server. The method then identifies each data object residing in the recovery storage group and displays each of the data objects on a graphical user interface configured to allow a user to select and individual data objects for recovery from the recovered database. The selected data objects are restored to the appropriate location on the production server.

Browsing and selecting items in recovery storage groups to perform recovery onto production server

Systems and methods for performing scheduled backups and recovery of data generated by a production application operating on a MAGIC platform located on a host computer. The data is stored in a primary storage in the form of a production volume and ISB protocol is used to create a clone volume. Exemplary methods for backing up a clone volume to a backup storage include receiving a backup command from a backup server, sending a split command to a host computer to initiate splitting of a production volume and a clone volume using ISB protocol, initiating creation of a snapshot from the clone volume, and initiating storing of the snapshot in the primary storage.

Generating automated and scheduled SAN copy sessions for ISB protocol systems

Systems and methods for performing scheduled backups and recovery of data generated by a production application operating on a MAGIC platform located on a host computer. The data is stored in a primary storage in the form of a production volume and ISB protocol is used to create a clone volume. Exemplary methods for backing up a clone volume to a backup storage include receiving a backup command from a backup server, sending a split command to a host computer to initiate splitting of a production volume and a clone volume using ISB protocol, receiving an identification of the clone volume, initiating the clone volume for surfacing and mounting, and initiating a backup of the surfaced and mounted clone volume to a backup storage.

Remote backup and restore operations for ISB protocol systems

Backup and restore operations using a single snapshot driven by a server job request

Backup and restore operations using a single snapshot

Systems and methods for performing scheduled backups and recovery of data generated by a production application operating on a MAGIC platform located on a host computer. The data is stored in a primary storage in the form of a production volume and ISB protocol is used to create a clone volume. Exemplary methods for creating and storing a snapshot from a clone volume include receiving a backup command from a backup server, sending a split command to a host computer to initiate splitting of a production volume and a clone volume using ISB protocol, receiving an identification of the clone volume, initiating creation of a snapshot from the clone volume, and directing saving of the created snapshot in one of two or more snapshot storage spaces such that priority for saving the created snapshot is based on at least one of identifying an empty snapshot storage space that does not currently have a snapshot stored therein or identifying a used snapshot storage space having a snapshot saved at an oldest point in time.

Rotation policy for SAN copy sessions of ISB protocol systems

Systems and methods for backing up or restoring interdependent applications. During a backup or recovery process, the writers and writer components included in the backup groupings of a client are displayed. Some of the writers and writer components can be individually selected for backup or recovery. Some of the writer components may have a dependency on a writer component in another writer. The dependency is automatically selected, although a user can disable the automatic selection of the dependency or deselect the dependency. The dependency is then backed up or recovered along with the selected writers and selected writer components.

Backup and restore operations of interdependent system components

Systems and methods for recovering data from a backup copy and for backing up data. When a recovery operation is initiated, recovery items are selected from backup groupings of the client. The recovery items can include backup groupings, writers, and writer components. After the recovery items are selected, backed up metadata for each selected writer is retrieved from the backed up data. The backed up metadata is then queried to identify the restore method of the writer. The data of the client is then recovered by implementing the restore method included in the backed up metadata of the writer. During a backup operation, some of the backup groupings, as well as the content of the backup groupings, can be individually selected for backup. In both backup and recovery, a visual indication may be provided to identify individual selectability.

Growing community of inventors

Kent, WA, United States of America

Patrick M Simonich