Browse Prior Art Database

A system and method managing metadata for Dynamic Infrastructure and Disaster Recovery in virtualized environments

IP.com Disclosure Number: IPCOM000199999D
Publication Date: 2010-Sep-23
Document File: 4 page(s) / 140K

Publishing Venue

The IP.com Prior Art Database

Abstract

Today's dynamic IT intrastructures are based on virtualization and cloud computing. The loose couling between applications, databases, hardware and storage offers a great flexibility of the IT landscape. In case of a failure of one of the system's components however, the advantages of this loose coupling turn into severe drawbacks: - There is no metadata available which describes which databases and which applications are affected by a disaster or storage hardware failure. It is not obvious which backups need to be restored to recover the databases and applications appropriately. - Not being able to link applications, databases and their storage systems with metadata also means it is impossible to optimize costs for hosting these services with fulfilling the Service Level Agreements (SLAs) with the least expensive layout regarding storage. This document describes a system that consistently collects metadata for all components of an application stack.

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

Page 01 of 4

A system and method managing metadata for Dynamic Infrastructure and Disaster Recovery in virtualized environments

System overview:

Description of the system components:

• IO Metadata Services and Catalog component: This component stores and manages metadata linking applications, databases, logical file systems and physical locations of data in an end-to-end fashion. This data has to be on a different storage then any other storage used by database and application systems - otherwise access to the metadata is not available in a disaster or major hardware failure case because it would be lost as well. Provides a service interfaces to

o Create these metadata entries
o Update these metadata entries
o Delete these metadata entries
o Enable search on the persisted metadata

1

(This page contains 00 pictures or other non-text object)

Page 02 of 4

• The use of a LDAP component linking login user IDs of applications (or application IDs) to technical user IDs. The reason for this is that the ESB might map application IDs or login user IDs to technical IDs before invoking information services of the database system. Thus, the database system might never know the real applications/application user IDs. Therefore, in the disaster recovery case to identify all affected applications, a reverse lookup is needed to be able to resolve the technical user IDs back to the application IDs or login user IDs.

• Dynamic Infrastructure UI: This UI is used to interact with the IO Metadata Services and Catalog component from a System Administrator role perspective.

• Enhancement of the database interfaces and enhancement of the database catalog function. Whenever the database changes the assignment of logical file systems to tablespaces containing data tables, this change is reflected in the IO Metadata Services and Catalog component as well as the usual update of tables in the database catalog by calling the relevant services of that component through the ESB.

• Enhancement of the IO Layer of the Operating System
• Enhancement of Logical Volume Controller: This enhancement is responsible to ensure whenever a new logical file system is created or changed the linkage of the logical file system to one or multiple physical disks and locations on these disks
(

partitions) is also persisted in the IO Metadata Services

                                 & Catalog component by calling the relevant services of that component through the ESB.

Benefits of this solutions:

● Quick disaster recovery is possible by querying the IO Metadata Services & Catalog

component to find out which databases and applications are affected by the disaster.

● The same applies if large scale hardware failure in the storage layer occurs.
● The IO Metadata Services & Catalog enables a dynamic infrastructure or a cloud

computing environment to provision storage more effectively because at any point in time

provisioning components can find and move data from one storage type to the best fit

storage type for cost re...