If the RASD becomes corrupt (for example, because of a device failure), you can restore the database from the most recent backup files.
The Mirror Replication Agent retrieves the RASD backup files from the directory identified by the rasd_backup_dir configuration parameter. See the Mirror Replication Agent Reference Manual for more information about the rasd_backup_dir parameter.
To restore the RASD, the Mirror Replication Agent instance
must be in Admin state.
Log in to the Mirror Replication Agent instance with the administrator login.
Use the following command to determine the state of the Mirror Replication Agent instance:
ra_status
If the Mirror Replication Agent is in Admin state, skip this step and go to step 4.
If the Mirror Replication Agent is in Replicating state:
Use the following command to suspend replication by the Mirror Replication Agent instance:
suspend
Use the following command to verify that the Mirror Replication Agent is in Admin state:
ra_status
After you verify that the Mirror Replication Agent is in Admin state, restore the RASD:
rasd_restore backup_directory
Here, backup_directory contains the backup you want to restore (for example, 2009-07-04_14.21.34). If you issue rasd_restore without any parameters, only the most recent backup is restored.
After the restore operation completes successfully, the Mirror Replication Agent shuts down automatically.
If the Mirror Replication Agent cannot find the directory identified in the rasd_backup_dir parameter, or if it cannot read the RASD backup files in that directory (for example, because of a permission problem), it returns an error. You must correct the cause of the error to restore the RASD.
After the RASD is successfully restored from the most recent backup, use the following command to resume replication in the Mirror Replication Agent instance:
resume
If the Mirror Replication Agent does not return to Replicating state, see Chapter 4, “Troubleshooting Mirror Replication Agent,” for more information.