Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. Cluster Merge Rules
  13. Forced Link and Unlink
  14. System Backup and Restore
  15. Batch Utilities

Overview

Overview

Use the operating system and database backup tools to back up the
MDM Registry Edition
systems, and the tools can vary from system to system.
The first step is to ensure that the
MDM Registry Edition
databases and Rulebase are in a stable state. The best way to do that is to shut down the
MDM Registry Edition
Rulebase and connection/search servers. Use the
MDM Registry Edition
Console or run the
idsdown
script to shut down the
MDM Registry Edition
Rulebase and connection/search servers. On UNIX, use the
$SSABIN/idsdown
command.
After you shut down the
MDM Registry Edition
servers, use the database vendor tools to back up all the
MDM Registry Edition
tables and databases. For example, with IBM DB2 UDB, you can use the
BACKUP DATABASE
command. Oracle has multiple ways to back up databases. For example, the Oracle Recovery Manager. Save the user information. IBM DB2 UDB uses system user IDs. A complete system backup is the best way to ensure that all the information is backed up. If a complete backup is not feasible, document all the scripts and procedures that you used to set up the
MDM Registry Edition
system so that a complete restore is possible.

0 COMMENTS

We’d like to hear from you!