Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

High Availability Configuration

High Availability Configuration

A cluster resource manager (CRM) manages the servers and resources in a server cluster. A service monitoring software detects a node failure and reroutes the workload to another node.
The following diagram shows the configuration of a highly available Data Archive and Data Vault environment:
The server cluster includes the following components:
Cluster resource manager (CRM)
The CRM manages access to the servers and resources in the cluster. It also manages the changeover from one node to another.
Service monitor
The service monitor detects when the primary node is down and triggers the changeover to another node.
Primary server
The primary server is the logical server that performs all archiving processes and requests. It is always in active mode.
The primary server hosts the following Data Archive and Data Vault components:
  • ILM Engine
  • Data Vault Service
  • Data Vault Service plug-in for Data Archive
Failover server
If the primary server fails, the failover server takes over the functions of the primary server and performs all archiving processes and requests. The failover server is in passive mode unless the primary server fails. When it is in passive mode, the failover server can process queries to the Data Vault.
The failover server hosts the following Data Archive and Data Vault components:
  • ILM Engine
  • Data Vault Service
  • Data Vault Service plug-in for Data Archive
  • Data Vault Service agent
The failover server hosts the same components as the primary server. It hosts an additional Data Vault Service agent to process queries.
The failover server must have the same directory structure as the primary server. For example, if the ILM Engine is installed in the
c:/ILM
directory in the primary server, then the ILM Engine must also be installed in the
c:/ILM
directory in the failover server.
Shared storage
The primary and failover servers connect to the same Data Vault directories. If the server cluster includes multiple storage devices, the primary server and the failover server must have access to a shared drive.
Create the following Data Archive and Data Vault directories:
  • Directory for the Data Vault repository. For example:
    <SANRootDirectory>/Meta/
  • Directory for the shared run-time files. For example:
    <SANRootDirectory>/FAS_shared/
  • Directory for staging files. For example:
    <SANRootDirectory>/Staging/
  • Directory for archive data files. For example:
    <SANRootDirectory>/SCT/