Part 2 of 5 · 1 min read
A standby system
A separate, running copy of the database, continuously kept up to date, ready to take over without a lengthy restore.
Think of an understudy actor who has learned every line of a play. Already dressed and waiting backstage, the understudy can step onto the stage immediately, rather than needing to be called in and prepared from scratch if the lead actor cannot go on.
In plain words: a standby system is a separate, running copy of the database, kept continuously up to date with the primary system, ready to take over serving requests if the primary fails. Unlike the backup covered on the previous page, which must be actively restored, taking real time to complete, a standby is already running and already nearly caught up, meaning taking over can happen far faster than a full backup restore would allow. A standby is typically kept on physically separate infrastructure, satisfying the same storage-separation reasoning covered on the previous page.
A worked example. A primary database serving live traffic has a standby copy running on a separate server, continuously receiving updates, ready to begin serving requests directly if the primary server fails.
The key lines. No new SQL; setting up and maintaining a standby is an operational configuration, not something expressed in ordinary transaction statements.
Standby system
A standby system is a separate, running copy of the database, continuously kept up to date with the primary, ready to take over serving requests far faster than a full backup restore would allow.
Example: an understudy actor already dressed and waiting backstage, ready to step on immediately, mirrors a standby system's readiness compared to a backup that must be restored from scratch.