From 1334fcfad674551cbd7e8144a1c56829fa41459d Mon Sep 17 00:00:00 2001 From: Dmitry Yemanov Date: Sat, 11 Nov 2023 20:34:24 +0300 Subject: [PATCH] Fixed typo --- doc/README.replication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/README.replication.md b/doc/README.replication.md index 549fa01a6a..ecc8c2527e 100644 --- a/doc/README.replication.md +++ b/doc/README.replication.md @@ -117,7 +117,7 @@ Any physical copying method can be used on the primary host: 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 +* nbackup -f <database> -seq Then the replica mode must be activated for the database copy. Two options are possible: