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. Seamless Access Setup for Oracle R12 in Data Archive
  21. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  22. Using Multiple Engines in an ILM Environment
  23. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  24. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Overview

Overview

Effective in Data Archive version 6.2, the File Archive Service was renamed to Data Vault. This article uses the new terminology.
You can design the Data Archive system configuration to minimize service interruption and ensure continuous availability of the Data Vault. When you configure high availability, the archive processes can continue to run despite temporary network, hardware, or service failures.
One approach to high availability for Data Archive is to set up a failover server for the ILM Engine and the Data Vault Service. Set up a server cluster with at least two nodes, a primary server and a failover server. The primary server runs in active mode and the failover server runs in passive mode. If the primary server fails, the failover server takes over the archive and query processes.
The primary server, in active mode, processes all archive and query requests for the Data Vault. The failover server, in passive mode, does not process archive requests. However, to improve efficiency, you can install a Data Vault Service agent on the failover server so that it can also process queries sent to the Data Vault.
The primary and failover servers must have identical directory structures to make the switch from one server to another seamless. The primary and failover servers archive data to a network storage that must be accessible to both servers.
Install the Data Archive and Data Vault components on the primary and failover servers. After installation, configure the primary and failover servers to connect to the same directories for the Data Vault repository and the run-time files. Update the configuration files to use the same directories.

0 COMMENTS

We’d like to hear from you!