Siebel Remote and Replication Manager Administration Guide > Administering Siebel Replication Manager > Process of Administering Siebel Replication Manager >

Maintaining Replication Manager

This topic describes some of the management activities not addressed elsewhere in this chapter that you can do periodically to keep your Replication Manager implementation running efficiently.

Backing up and Recovering a Database on the Headquarters Node or Regional Node

This topic describes how to backup and recover a database of the headquarters or regional node.

To back up and recover a database on the headquarters node or regional node

1. Make sure you do regular backups and maintenance tasks on the headquarters database and on the regional databases.

   It is strongly recommended that you regularly do this work.

2. If a failure occurs, then do the following work:
   • If a failure occurs on a regional database, and if you cannot recover it to the exact point of failure, then you must reextract the regional database on the Siebel Server at the parent node.
   • If transactions are lost on the headquarters node, then you must do the following:
     • Reextract all child nodes.
     • Reextract the users who synchronize with the regional server whose regional database failed.

If you can recover the regional node to the exact point of failure, then the S_DOCK_STATUS values of the headquarters and regional nodes are synchronized. Replication Manager synchronizes the following transactions after recovery to the point of failure:

• Transactions that Replication Manager had not synchronized at the time of failure
• Transactions that Replication Manager created on the headquarters node and the regional nodes after the point of failure

Backing Up and Recovering the Siebel Enterprise Server

To back up the entire server database or user schema, you can use an RDBMS tool that a third-party vendor provides. You must take some precautions, such as not backing up the docking folders. For more information, see Technical Note 0026 on My Oracle Support.

Administering Monitoring and Logging

This topic describes how to monitor Siebel Servers and how to manage data that Replication Manager logs in the transaction log table.

Monitoring the Regional Siebel Servers

This topic describes how to monitor the regional Siebel Servers.

To monitor the regional Siebel Servers

• To monitor server components and the movement of data between regional nodes and the parent node, use the following screens in the administrative interface:
  • Administration - Siebel Remote
  • Administration - Server Management

It is also recommended that you monitor disk space availability.

Reducing the Transaction Log Table by Expiring Obsolete Transaction Processors

It is strongly recommended that you periodically expire each obsolete Transaction Processor. A Transaction Processor can become obsolete in the following situations:

• Replication Manager starts a Transaction Processor on the Siebel Server but then does not use it
• Replication Manager starts a Transaction Processor and then you uninstall the Siebel Server
• After an upgrade

For more information, see Troubleshooting a Large Transaction Backlog Problem.

To reduce the transaction log table by expiring obsolete transaction processors

1. Log in to the Siebel Server with administrator privileges.

   For more information, see Logging In to the Siebel Server as an Administrator.

2. Navigate to the Administration - Siebel Remote screen, and then the Processor Status view.
3. In the Transaction Processors list, choose the obsolete Transaction Processor.
4. In the End Date field, enter an end date that has already occurred.