Abstract: A SAN management application stores a password file in a secure repository inside a database to which the stored passwords provide access. A separate database account (i.e. login) is created to afford access to the password repository. The password repository, typically a database table or file, is stored in a secure area accessible only by the specialized password account. A separate password, or access token, is employed for access to the password repository account. Executable entities, such as processes of the management application, are encoded with the password, or access token, to the password repository account. From the password account, the password repository provides availability to the stored passwords for specific privileged access by designated processes. In this manner, a dual level authorization is provided to privileged database operations, and corresponding logic embedded in particular processes authorized to traverse both levels.

Abstract: In a storage area network (SAN), a SAN management application provides a security audit log of security sensitive user actions performed across the storage area network. In a SAN, multiple services operate to perform requested user actions. Configurations herein substantially overcome the shortcomings of conventional SAN security event logging by providing a comprehensive security audit mechanism operable to identify and record user actions. An event normalizer disposed in each of the services identifies requested user actions, creates a uniform user action object, and sends the user action object to a coalescer operable to receive user action objects from the plurality of services in the SAN. The user action object provides a generic template responsive to each of the event normalizers in the services. The event normalizers normalize event properties and attributes concerning a user action into the generic user action object, and employs preexisting conduits for gathering and recording events.

Abstract: A system receives notification from an agent of that agent's availability for data collection from resources within a network. The system identifies, from the notification, a version value associated with the agent. The system determines, from the version value, a set of operations to be assigned to the agent that will be compatible with that agent, and assigns a subset of the set of operations to the agent to enable that agent to collect data from resources in the network.

Abstract: Upgrading an original repository of data is disclosed. A repository is defined by a set of schema structures and data contained therein. A copy of the original repository is exported. The set of schema structures of the original repository is modified to create a set of schema structures of the upgraded repository. Schema structures that are not present after the upgrade are deleted after data migration is completed. Data is migrated to the set of schema structures of the upgraded repository. Data includes existing data from the original repository and seed data for the upgraded repository. Existing data is copied into the appropriate schema structures of the upgraded repository. Seed data is inserted into new schema structures of the upgraded repository. The set of schema structures of the upgraded repository are validated against a standard set of schema structures corresponding to a properly upgraded standard repository to detect any errors.

Abstract: Generating a repository template of a repository of data for a storage area network (SAN) management tool is disclosed. The repository will hold data describing SAN elements and configurations, and will be stored on a host. A configuration file is updated to include current configuration data for the repository, and includes specifications for a set of new schemas that define structures within the repository. A set of new schemas is created from those specifications. Seed data that defines initial information for the repository is copied to the host. New schemas are initialized with the seed data. A repository template is generated from the created set of new schemas and the seed data, from which one or more repositories may be created to hold SAN data.

Abstract: A system receives a dataset for storing in a staging database. The dataset contains network management data collected from a managed resource. The system stores the dataset in the staging database, and maintains a changeset identifying changes made to the staging database during the step of storing the dataset. The system synchronizes the staging database and the production database with each other using the changeset.

Abstract: A system detects an event suggesting a data discrepancy between a staging database and a production database that maintain network management data within a network management system. The staging database is logically separate from the production database. The system prevents modification to the production database, and replaces data in the staging database with data from the production database. The system then allows modification to the production database.

Abstract: A system receives a dataset for storing in a staging database. The dataset contains network management data collected from a managed resource. The system disengages a connection between the staging database and a production database, and stores the dataset in the staging database. The system then re-engages the connection between the staging database and the production database.

Abstract: A system allows software not equipped to work with remote location alert reporting software to obtaining alert data indicating an alert associated with a first managed resource in a storage area network. The system identifies a top-level resource in the storage area network to which the first managed resource indicated by the alert data is related and performs remote alert notification analysis to determine if the top-level resource is a managed resource in the storage area network for which remote location alert reporting software is not operational. If the top-level resource is a managed resource for which remote location alert reporting software is not operational, the system proxy engages operation of remote location alert reporting software on behalf of the top-level resource to report the alert data via the communications interface to the remote location.