From 74b90ce63385d6f3aa0623c7ea8717f69837e64f Mon Sep 17 00:00:00 2001 From: Dmitry Yemanov Date: Sat, 11 Nov 2023 13:47:58 +0300 Subject: [PATCH] Better description of the replica creation --- doc/README.replication.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/README.replication.md b/doc/README.replication.md index f0f13ec389..549fa01a6a 100644 --- a/doc/README.replication.md +++ b/doc/README.replication.md @@ -108,13 +108,17 @@ To apply the changed replica-side settings, Firebird server must be restarted. ## Creating the replica database -In the Beta 1 release, any physical copying method can be used: +Any physical copying method can be used on the primary host: * File-level copy when Firebird server is shutdown * ALTER DATABASE BEGIN BACKUP + file-level copy + ALTER DATABASE END BACKUP * nbackup -l + file-level copy + nbackup -n * nbackup -b 0 +If _nbackup_ was used, restore or fixup operation should be performed to complete the replica creation. Note that if you're recreating a priorly working replica, then `-seq[uence]` option of _nbackup_ must be used to preserve the replication sequence counter inside the database, so that replication could continue from the moment when the primary database was copied: + +* nbackup -f <databasw> -seq + Then the replica mode must be activated for the database copy. Two options are possible: * gfix -replica read\_only <database> -- set up database as read-only replica