Replicating client node data after a database restore

When you restore the Tivoli® Storage Manager database on a source replication server, replication is automatically disabled. Before re-enabling replication, you can take steps to preserve the client node data that is on the target replication server.

About this task

Disabling replication prevents the Tivoli Storage Manager server from deleting copies of data on the target replication server that are not referenced by the restored database. Before re-enabling replication, determine whether copies of data that are on the target replication server are needed. If they are, complete the steps that are described in the following example. In the example, the name of the source replication server is PRODSRV. DRSRV is the name of the target replication server. NODE1 is a client node with replicated data on PRODSRV and DRSRV.

Restriction: You cannot use Secure Sockets Layer (SSL) for database restore operations.

Procedure

Remove NODE1 from replication on PRODSRV and DRSRV by issuing the REMOVE REPLNODE command:
```
remove replnode node1
```
Update NODE1 definitions PRODSRV and DRSRV. When replication occurs, DRSRV sends the data to PRODSRV that was lost because of the database restore.
1. On DRSRV, issue the UPDATE NODE command and specify the replication mode SYNCSEND:
```
update node node1 replstate=enabled replmode=syncsend
```
2. On PRODSRV, issue the UPDATE NODE command and specify the replication mode SYNCRECEIVE:
```
update node node1 replstate=enabled replmode=syncreceive
```
On DRSRV, set the replication rules to match the rules on PRODSRV. For example, if only archive data was being replicated from PRODSRV to DRSRV, set the rules on DRSRV to replicate only archive data from DRSRV to PRODSRV. Backup and space-managed data are not replicated to PRODSRV.
To set rules, you can issue the following commands:
- UPDATE FILESPACE
- UPDATE NODE
- SET ARREPLRULEDEFAULT
- SET BKREPLRULEDEFAULT
- SET SPREPLRULE
On DRSRV, issue the SET REPLSERVER command to set PRODSRV as the target replication server:
```
set replserver prodsrv
```
On DRSRV, issue the REPLICATE NODE command to replicate data that is stored on NODE1:
```
replicate node node1
```
Replication processing changes the replication state of NODE1 to SEND on DRSRV and to RECEIVE on PRODSRV.
Remove NODE1 from replication on PRODSRV and DRSRV by issuing the REMOVE REPLNODE command:
```
remove replnode node1
```
Update NODE1 definitions:
1. On DRSRV, issue the UPDATE NODE command and specify the replication mode SYNCRECEIVE:
```
update node node1 replstate=enabled replmode=syncreceive
```
2. On PRODSRV, issue the UPDATE NODE command and specify the replication mode SYNCSEND:
```
update node node1 replstate=enabled replmode=syncsend
```
On PRODSRV, enable replication by issuing the ENABLE REPLICATION command:
```
enable replication
```
On PRODSRV, issue the REPLICATE NODE command to replicate data that is stored on NODE1:
```
replicate node node1
```
Replication processing changes the replication state of NODE1 to SEND on PRODSRV and to RECEIVE on DRSRV.

Results

The original replication configuration is restored. PRODSRV has all the data that was lost because of the database restore.

What to do next

Remember: In step 4, you set the PRODSRV as the target replication server for DRSRV. If in your original configuration you were replicating data from DRSRV to another server, you must reset the target replication server on DRSRV. For example, if you were replicating data from DRSRV to BKUPDRSRV, issue the following command on DRSRV:

set replserver bkupdrsrv