mirror of
https://github.com/FirebirdSQL/firebird.git
synced 2025-01-22 18:43:02 +01:00
Better description of the replica creation
This commit is contained in:
parent
f60493c43b
commit
74b90ce633
@ -108,13 +108,17 @@ To apply the changed replica-side settings, Firebird server must be restarted.
|
|||||||
|
|
||||||
## Creating the replica database
|
## 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
|
* File-level copy when Firebird server is shutdown
|
||||||
* ALTER DATABASE BEGIN BACKUP + file-level copy + ALTER DATABASE END BACKUP
|
* ALTER DATABASE BEGIN BACKUP + file-level copy + ALTER DATABASE END BACKUP
|
||||||
* nbackup -l + file-level copy + nbackup -n
|
* nbackup -l + file-level copy + nbackup -n
|
||||||
* nbackup -b 0
|
* 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:
|
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
|
* gfix -replica read\_only <database> -- set up database as read-only replica
|
||||||
|
Loading…
Reference in New Issue
Block a user