Manage the OpenEdge Database

Roll-forward recovery with fewer than 100 rekey operations

Save PDF

Save PDF

Follow the steps in this example when fewer than 100 DB policy rekey operations are involved in the roll-forward process:

Back up the source database sourceDB using PROBKUP, for example:
```
probkup sourceDB sourceDB.bck
```
Note that PROBKUP does not back up the keystore, users need to copy and save it. If there are over 100 TDE DB Policy rekey operations after this point, the latest version of keystore on the source database no longer keeps the DMK needed by the target database. You can use this copy to open the target database and perform AI roll-forward.
Start after-imaging on the source database:
```
rfutil sourceDB -C aimage begin
```
After some database activities on the source database that fill some AI extents including TDE DB Policy Rekey options up to 100 times, users decide to roll forward after-imaging on the hot standby database. To roll forward:
1. Restore the hot standby database from the backup of the source database:
```
prorest targetDB sourceDB.bck
```
2. Copy the latest keystore from the source database:
```
cp sourceDB.ks targetDB.ks
```
3. Perform roll-forward recovery on the hot standby database with one of two parameters – -a or -ailist.. For example, for -a:
```
rfutil targetDB -C roll forward -a sourceDB.a1
```
```
rfutil targetDB -C roll forward -a sourceDB.a2
```
```
...
```
```
rfutil targetDB -C roll forward -a sourceDB.aN
```
  Alternatively, use -ailist, as follows:
```
rfutil targetDB -C roll forward -ailist listFile
```