## Setting Up a Standby Instance

### Use

You set up a standby instance for an existing database instance (original instance).

See also:

Standby Database

Database Administration Tutorial, Setting Up and Updating Standby Instances

### Procedure

Use the Database Manager for the following steps:

...

1. Create the standby instance by making a copy of your original instance. Proceed as described in the Database Copy section, but do not start the standby instance in the ONLINE operational state; instead, keep it in the ADMIN operational state. Do not load the system tables yet.

Observe the following points when you create the standby instance:

○ We recommend that you set up the original instance and the standby instance on different computers.

○ The standby instance must use the same version of the database software as the original instance.

○ The database parameters of the target instance were defined with the same values as those of the original instance, but each instance has its own working directory.

2. Define a backup template of backup type log backup for the standby instance. The property Data Carrier (device/file) must refer to the log backup of the original instance to be imported. You use this backup template to update a standby instance at regular intervals by importing log backups from the original instance to the standby instance.

See:

Database Manager GUI, Backup Template for a Single Data Carrier or

Database Manager CLI, medium_put

### Result

The standby instance is in the ADMIN operational state.

You can now repeat the data changes in the original instance in the standby instance at regular intervals and so have a copy of the original instance and your existing data that is slightly delayed in time (see: Updating the Standby Instance ).