Emc Corporation

Emc IP Holding Company LLC

Evgeny Roytman

Anoop George Ninan

Michael G Hegerich

Boris Farizon

Michael J Virgil

Thomas L Watson

William J Elliott, Iv

Andrew S Becher

Ameer Jabbar

Gregory MacKinnon

John P Sheehy, Jr

Samuil Shmuylovich

Vitaly Rozenman

Benjamin Bushoy

Benjamin Thrift

Valery Altman

Matthew L Troutman

Terrence Lewis

Thomas Demay

Stephen Walsh

Eyal Kedem

Shreesha PaiManoor

Boris Zeldin

Steven M Stramaglia

Yogesh Athawale

A method is used in providing remote replication management. A storage management system detects a storage driver for a storage array, where the storage driver enables managing remote replication for the storage array. The storage management system manages remote replication of storage objects for the storage array by using the storage driver, where the storage driver includes interfaces for managing remote replication.

Storage drivers for remote replication management

A computer program product, system, and computer-executable method for managing meta volumes in a data storage system, the computer program product, system, and computer-executable method comprising receiving one or more data storage characteristics, analyzing the one or more data storage characteristics, based on the analyzing, creating a policy responsive to the data storage characteristics, and allocating a meta volume based on the policy.

Policy-driven volume expansion

A system, method, and computer program product for storage provisioning in a data storage environment comprising protecting, through an orchestration API, a source volume at a source site by setting the source volume to be replicated to a target volume at a target site through the use of a replication appliance; wherein the API is enabled to create network zones between the source site and the target site for replication from the source site to the target site and wherein the network zone is configured to include the replication appliance; wherein the API is enabled to mask storage devices used to store data on the source volume and the target volume.

Storage provisioning in a data storage environment

In one aspect, a method includes receiving, at a computer, a request for a resource over an interface from a client, returning the resource from the computer to the client, receiving, at the computer, an action from the client based on the resource returned, returning a unique task instance that includes information about the action, enabling the client to poll the resource periodically and enabling the client to access affected resources. The affected resources include resources affected by the action.

Task-based approach to execution, monitoring and execution control of actions

In one aspect, a method includes receiving a request to provision a resource in a data storage system, determining whether any one of a set of quotas will be exceeded if the resource is provisioned, denying the request to provision the resource if any one of a set of quotas is exceeded and enabling the resource to be provisioned if none of the set of quotas is exceeded.

Provisioning resource using quota

In a storage area network, a task manager identifies a set of preconditions for execution of storage management tasks. The set of preconditions establish dependencies between tasks in the storage area network. Execution of the tasks is contingent upon satisfaction of the set of preconditions. In addition, the task manager generates a scheduling data structure based on the set of preconditions in order to schedule execution of the tasks. As a result, the task manager can utilize the scheduling data structure to optimize task execution in the storage area network (e.g., by applying a task optimization algorithm). Such optimization minimizes resource consumption (e.g., thread allocation, processor time commitment, etc.) in the storage area network during execution of the tasks.

Dependency-based task management using set of preconditions to generate scheduling data structure in storage area network

A task analyzer analyzes received tasks to identify and classify corresponding sub-tasks. For example, for each given received task, the task analyzer analyzes a given task to identify a first type of sub-tasks (e.g., sub-tasks that can be executed in any order). The task analyzer also analyzes the given task to identify a second type of sub-tasks (e.g., sub-tasks that are to be executed in parallel) associated with the given task. A task execution manager submits the first type of sub-tasks for execution by a first pool of processing threads, which is dedicated for executing the first type of sub-tasks. The task execution manager submits the second type of sub-tasks for execution by the second pool of processing threads. The second pool of processing threads is dedicated to execute the second type of sub-tasks.

Task execution using multiple pools of processing threads, each pool dedicated to execute different types of sub-tasks

A task manager (or related operation) keeps track of free processing threads amongst multiple processing threads. The task manager receives a request to execute a task. Prior to execution, the task manager processes the task to identify portions of the task that must be executed in parallel. In response to detecting that there is a first processing thread in the pool free to execute a main portion of the task as well as sufficient free additional processing threads in the pool to execute each of the identified sub-tasks in parallel, the task manager submits the task for execution by the pool of multiple processing threads. For accounting purposes, the task manager modifies tracking information to indicate that the first processing thread and additional processing threads are now unavailable for use for execution of other tasks.

Task management using multiple processing threads

Methods and systems for separating presentation and business models for common management platform tasks in a storage area network (SAN) are disclosed. A graphical user interface (GUI) object may be mapped to a task object, which include action(s) performed on a SAN. A selection of task objects from a collection of task objects is received, which are needed to implement the underlying functionality of a GUI object. The collection of task objects is part of a task framework. An arrangement of the task objects according to a hierarchy of the framework is received. The hierarchy includes simple task objects, corresponding to actions performed on a SAN, and composite task objects, corresponding to at least two simple task objects and may include other composite task objects. The arranged task objects are mapped to the GUI object by extending a presentation object to encapsulate the GUI object and the arranged task objects.

Separation of presentation and business models for common management platform tasks in a storage area network

The present disclosure is directed to a system, method, apparatus, encoded computer readable media, etc., for maintaining data. A processor function maintains a map that keeps track of which data information stored in a first repository have corresponding record information stored in a second repository. The map can be used to facilitate synchronization of the first repository and the second repository. For example, the processor function can receive a command to delete a particular managed object from the first repository. In response to receiving the command, the processor function utilizes the map to identify whether the particular managed object to be deleted from the first repository has any corresponding related records stored in the second repository. If so, the processor function provides a notification (to an information management application associated with the second repository) indicating that the corresponding related record stored in the second repository can be deleted.

Methods and apparatus for synchronizing information

A custom host naming mechanism that allows a user to define a custom host name as a virtual name for the hosts in the managed information environment, such as the storage area network, overcomes the shortcomings of the use of a network assigned machine name during a failover operation. The custom host naming mechanism allows the operator to define a mnemonic virtual name for each host in the managed information environment, thereby facilitating failover switching. Further, such secondary hosts may undertake offline, lower priority executing tasks while not in failover mode, and rapidly reconfigure as the failover secondary host should the need arise. Therefore, secondary hosts at a hot site deploy with a mnemonically descriptive name indicative of their status as a secondary host for a corresponding primary host, and further, need not remain idle pending a disaster recovery scenario, but rather are employable for offloading of other, lower priority tasks pending failover response.

System and methods for host naming in a managed information environment

Mechanisms and techniques for processing information in a network management application, such as a storage area network management application, include an agent and store process. The agent collects a current management data set from managed entity(s) in a network and compares the current management data set to a former management data set previously collected from the managed entity to identify differences in the current management data set as compared to the former management data set. The agent transmits the current management data set to a store process. The store process receives the current management data set and uses verification values and change indicators contained therein to identifying current portions of management data in the current management data that reflect a change. For any changed data portions, the store process modifies or updates managed object data in the management database.

Method and apparatus for identifying and processing changes to management information

In a managed information network, unavailable agents have a detrimental effect on user access to manageable entities. Intelligent, optimal assignment of manageable entities to available agents becomes a formidable task, particularly in a large storage area network. The task becomes especially complex when there are deployed agents of different types capable to manage a different scope of functionality of managed elements of the same type. A failover processor provides reliable, rule based methods for initial assignment of manageable entities (elements) to best available management agents, and a reliable, dynamic, rule based mechanism to reallocate manageable entities to a best management agent in case when current agent, responsible for element management, become unavailable or new best agent for element management starts up. A prioritized list of failover rules specifies metrics for determining alternate agents for manageable entities in the event agents become unavailable. A failover chain, or list of agent types, identifies preferential agent types to which the reassigned manageable entities correspond. Successive prioritization rules apply in the event that multiple candidate agents of the failover chain selection are available.

Growing community of inventors

Sharon, MA, United States of America

Evgeny Roytman