Browse Prior Art Database

Element Catalog (Generalized Central Repository)

IP.com Disclosure Number: IPCOM000109380D
Original Publication Date: 2005-Mar-24
Included in the Prior Art Database: 2005-Mar-24
Document File: 2 page(s) / 22K

Publishing Venue

IBM

Abstract

The basic idea is to have a central repository that has all static information which can be used by any storage application within the storage subsystem. By having this, it will eliminate the dirty reads and overwrites among the storage applications and provide a mediator that determines which application uses the storage. A dirty read is when one transaction reads an uncommitted change made by another transaction.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Element Catalog (Generalized Central Repository)

Disclosed is a system that stores static information of a storage environment that can be used by all applications within that environment. The system, which is called the Element Catalog, is a central repository that has a collection of services and elements. It is where all base information can be obtained for anything that can be managed in a storage environment. An element is any object that can be managed or used by multiple storage applications. Elements are generalized entities of any storage entity such as a volume. Services are storage applications, which operate or manage the elements in any way. The elements within the Element Catalog will only contain static information about a storage entity. For example, an element that represents a volume will only contain information about its size, the id of the storage device it is located on, etc. All specific or dynamic information on any element will be stored or maintained by the service.

Many of today's storage environments are used for more than just storage of information. They are used to detect performance, make backup copies, etc. In other words, applications need to use the elements for many different reasons. The problem is there maybe applications, which can use the element simultaneously with other applications and there are applications, which cannot use the element with other applications. And because of these situations, there exist a need to determine which application uses the element.

Another problem with many of today's central information repositories is that they contain dynamic information, which could change every millisecond or less. This can cause an overflow of transactions to it when updating the information. With these transactions occurring ever so often and many applications querying the repository for information, the applications may not receive the most recent data. And many of the applications need the data to be up to date and consistent.

The Element Catalog will manage the elements. Meaning, it will determine if an element could be used by an application or not. It will allow an application to use the element so it would not cause harm or damage to other applications that are u...