Emc Corporation

Emc IP Holding Company LLC

Everbridge, Inc.

Christopher Chaulk

Serge Marokhovsky

Robert Anthony Lincourt, Jr

Alexander Dubrovsky

Mark Adam Arakelian

Afzal Rahman Jan

Paul Timmins

Anuradha Shivnath

Udi Bar-On

Xiaohua Cheng

Yongmei Xu

Yang Liu

Samuil Shmuylovich

Rajesh Nandyalam

Venkatesh Sudarsanam Madhipatla

Eshwari Prasad Komarla

Prabhakaran Rathinagiri

Conor Fox

Eric Golin

Stalinsaravanakumar Thangapalam

Jia Xi

Nimai Sood

Yuanjin Xu

Viren Pherwani

Yuan Cheng

Sarah Yongmei Xu

Sameer S Chauhan

Konstantin Zilberberg

Syamala Pullakhandam

Junichi Eto

Mallari Mohanrao Kulkarni

Sathianantha Thilagar Thomas

David K Spencer

Anthony Patterson

Umamaheshwar Hegde

Mark Clement

Systems, methods, and computer-readable storage media providing highly scalable and fault tolerant notification systems are disclosed. Disclosed notification systems may be configured to: receive a plurality of notification requests including message content and recipient information, which may be allocated to at least one notification engine for processing. A notification engine may be configured to: generate a plurality of attempts corresponding to notification requests allocated for processing by the first notification engine and assign each generated attempt to a particular attempt queue. A plurality of connectors may be configured to: select a set of attempts for transmission from the plurality of attempt queues, transmit the set of attempts via at least one communication network. One or more databases may be provided to store status information associated with processing of notification requests by the first notification engine.

Systems and methods for providing a notification system architecture

A system provides of data islands of a federated environment storing scalable data used to efficiently search for data and/or other objects across the federated environment and access details of any objects while minimizing the data replicated across all of the data islands. The scalable data may be replicated across all of the data islands and allow a local search for any object across the federated environment. The scalable data may be a subset of data and/or configured meta data that stores a limited subset of data that enables the local search, at each data island, for objects stored in the federated environment.

Replication-based federation of scalable data across multiple sites

Example embodiments of the present invention provide a method, an apparatus, and a computer program product for tagging storage resource management objects in a storage resource management application. The method includes receiving an identification of a storage resource management object in the storage resource management application and associating a tag with the identified storage resource management object. The storage resource management application then may perform an operation on the storage resource management object according to the tag.

Method and apparatus for enabling customized control to applications and users using smart tags

Example embodiments of the present invention provide a method, an apparatus, and a computer program product for message based security audit logging. The method includes receiving an event notification related to an event in a storage resource management service, processing the event notification according to a messaging fabric and an ontology model, and, according to the processed event notification, persisting an audit log entry corresponding to the event.

Method and apparatus for message based security audit logging

A native data collection component may be implemented as a tool, appliance, application and/or utility, and including physical and/or logical implementations thereof. The native data collection component may be responsible for data orchestration, data collection, and aggregation and distribution of collected data from among multiple sources. Accordingly, the native data collection component may be independent of a particular data source and act as an independent performance characteristic collection mechanism. In an embodiment, the native data collection component may include three devices/sub-components: a data orchestration device, a data collection interface and a data aggregation and distribution device. Each sub-component may be service based and communication with each service may be done using state-less protocols. The data collection interface enables a software structure that includes data collection plug-ins that are independent of data sources and are not deployed into the SAN as agents of any of the data sources.

Native storage data collection using plug-ins that are independent from data sources

A system for controlled-tuning path performance data collection is provided according to group membership controlled using a tool or application. In an embodiment, criteria may be established for groups that are populated by member objects that satisfy the criteria, and performance data collection is performed for such criteria groups may be turned on or off from an interface of the tool. The tool may automatically update group membership and performance data collection characteristics according to user controlled settings but without requiring further user intervention during the updating. The described system may thereby be advantageously used in connection with management of performance data collection based on a defined groups framework in which selected groups are created, based on specified criteria, that contain objects (e.g., hosts, arrays, switches etc.) for which performance data should be collected.

Groups based performance data collection

Methods and apparatus for providing a storage resource management application having a protocol independent model for event-based discovery. In response to an event, discovery is performed using a protocol independent ontology model.

Methods and apparatus for protocol independent model to provide event-based discovery

A native data collection component may be implemented as a tool, appliance, application and/or utility, and including physical and/or logical implementations thereof. The native data collection component may be responsible for data orchestration, data collection, and aggregation and distribution of collected data from among multiple sources of a storage area network (SAN). The native data collection component is not required to be installed as an agent on any data source of the SAN, and the native data collection component may be independent of a particular data source and act as an independent performance characteristic collection mechanism. In an embodiment, the native data collection component may include three devices/sub-components: a data orchestration device, a data collection interface and a data aggregation and distribution device. Each sub-component may be service based and communication with each service may be done using state-less protocols.

Native storage data collection using multiple data collection plug-ins installed in a component separate from data sources of one or more storage area networks

A system is provided for managing data sets in a cloud processing and/or federated environment. In an embodiment, the system described herein may be used in connection with cloud processing of big data sets. The term 'big data,' as used herein, may be generally defined to describe data sets so large and complex that they become difficult to work with using on-hand database management tools. The system described herein enables the persistent storage of semantic technology statements for big data sets for processing in a cloud processing and/or federated environment.

Storage resource management information modeling in a cloud processing environment

A report generator of a storage area network management application includes a data validation mechanism that validates data related to managed resources operating in a storage area network. The data validation mechanism obtains first and second data sets concerning first and second characteristics of a resource operating in the storage area network and applies at least one data validation test using data sets to detect inconsistencies in data in the first and second data sets associated with the resource operating in the storage area network. Values can be compared in different columns of the same or different reports to detect report integrity errors or data mining errors. The report generator provides a storage area network management report based on data of the first data set and the second data set that accounts for inconsistencies in data associated with the resource as detected by the at least one data validation test.

Methods and apparatus for performing data validation in a network management application

A system produces a storage area network resource management report view by obtaining at least one report definition containing report parameters that specify a report layout for presentation of data in the graphical user interface. The system receives a report request to view data in a report view and obtains a data set corresponding to the report request. The data set includes data values to be presented as the data in the graphical user interface. The system applies the data values in the data set to the corresponding report parameters in the at least one report definition to populate the report layout specified by the at least one report definition to dynamically generate at least one report view. The system provides the at least one report view for rendering in the graphical user interface. The system also provides the ability to create custom report views without requiring programming language skills.

Method and apparatus for generating report views

A decision support system including a query generation tool provides a Graphical User Interface (GUI) for generating a query of a Storage Area Network (SAN) database using interactive screen displays identifying manageable entities in the SAN and queryable statistics thereof. Configurations herein provide a query mechanism, or interface, that generates an executable query via a GUI having intuitive mnemonic labels corresponding to the real-world (i.e. SAN manageable entities) represented in the query database, rather than the technical database table and attribute names which tend to be more cryptic, particularly to an uninitiated query operator. The GUI presents a sequence of screens for selecting SAN manageable entities, report fields, selection criteria, and output format. The query logic computes SQL syntax for identifying corresponding database tables and attributes, performing the required joins between the tables, and selecting the report set of records for output in the resulting SQL query.

System and methods for querying a report database

A Decision Support System (DSS) coalescer offloads and transforms data from an online statistical gathering database to a report query database adapted for report generation. The coalescer generates and populates a query database structured for query data retrieval, in contrast to realtime access transaction storage as in the online database. Configurations transform the online database into a star join schema (table structure) that centralizes database 'facts' in a central table and forms associations to database 'dimensions' upon which a query is likely to be based. The facts refer to items which tend to change regularly over time, such as sales volumes and unit shipped. Conversely, the dimensions include more static values such as time (e.g. days, weeks, and quarters) and geographic regions, such as states and countries. The resulting query model (schema) includes relatively small dimensions tables associated with (i.e. having a schema association to) a relatively larger fact table.

System and methods for modeling a report query database

A storage area network (SAN) management application generates device allocation reports displaying foundation variables, device specific parameters, and computed, derived fields for different types of storage arrays, without burdening the allocation report with extraneous parameters through the use of a layout indicative of the information included on the report, providing a streamlined and seamless allocation report. The SAN management application defines a layout indicative of the foundation variables, device attributes, and derived fields requested in an allocation report. The user selected layout indicates the requested allocation parameters for a report, indicative of the foundation variable, device attributes, and derived fields, and also indicates the device usage metrics for computing the derived fields from the foundation variables and device attributes. In this manner, a SAN operator requests an allocation report indicative of only the information sought, and need not correlate multiple reports or manually synthesize report output for determining derived fields.

System and methods for reporting device allocation

In a storage area network (SAN) management application, large data sets tend to produce unwieldy results upon display attempts. A mechanism for gathering and organizing a large data set into an ordered set of output display entries which does not require main memory storage for the entire large data set, generates a displayable portion without excessive memory consumption. Configurations employ a multiple pass gathering and organization operation. An output criteria specifies a key field and identifies a range of entries by specifying a particular screen for display from among the full range of screens. A parser retrieves and identifies the entries, during a first pass, using only the key field and an index for each of the entries in the large data set, to avoid loading all fields of each entry in entirety. A second pass fetches entries only for the identified entries corresponding to the output criteria.

Growing community of inventors

Franklin, MA, United States of America

Christopher Chaulk