Remote standalone secondary servers

These topics provide an overview of setting up and configuring remote standalone (RS) secondary servers in a high availability environment.

Comparison of RS secondary servers and HDR secondary servers
Index page logging
Starting an RS secondary server for the first time
After you complete the hardware configuration of the RS secondary server, you are ready to start the RS secondary server and connect it to the primary server.
Converting an offline primary server to an RS secondary server
After a planned or unplanned failover of the primary server to an RS secondary server, you can convert the old primary server to an RS secondary server.
Delayed application of log records
To aid in disaster recovery scenarios, you can configure RS secondary servers to wait for a specified period of time before applying logs received from the primary server.
Flow control for remote standalone secondary servers
Flow control provides a way to limit log activity on the primary server so that remote standalone (RS) secondary servers in the cluster do not fall too far behind on processing transactions. Enabling flow control ensures that logs on RS secondary servers remain current if the servers are on a busy or intermittent network.

Parent topic: High-availability cluster configuration