This section describes how you set up a standby database.
Use the Database Manager to carry out the following steps:
...
1. Create the standby instance by making a copy of your original instance. Proceed as described in Creating a Homogeneous System Copy (points 1-5). However, do not start the copy in the operational state ONLINE. Keep the copy in the operational state ADMIN instead.
You must set up the original instance and the standby instance on different computers.
2. In the standby instance, create a backup medium for importing log backups.
3. Make log backups in your active original instance at regular intervals.
4. At regular intervals, import these log backups into your standby instance with the time delay of your choice.
In the Database Manager GUI, import the backups as described under Restoring Without a Backup History.
In the Database Manager CLI, use the restore commands recover_start and recover_replace.
Keep the following points in mind:
· The data volumes and log volumes of the standby instance must be configured with enough space to be able to import the log backups of the original instance.
· The two instances cannot access the same files. This means that their run directories must be physically separate.
· You can use pipes to transport the data backup. You can transport log backups by ftp or use an exported file system (such as NFS or a shared file system) to copy them.