This command places a special lock on the replica. Between this point and the completion of step 6, the syncreplica –import command adjusts the lock temporarily to permit application of the update, and then restores the full lock. During this time, you can only modify the replica by using the syncreplica –import command.
You can send the packets using your standard synchronization method. To recover the replica more quickly, create the packets with syncreplica –export –fship.
Because your replica is in the special restoration state, each outgoing update packet includes a special request for a return acknowledgment. It also includes your replica’s old epoch numbers, which are now its current epoch numbers, by virtue of the restoration in step 1. Each destination replica uses these numbers to roll back its row for your replica.
Collectively, these update packets include all the operations that occurred between the time of the backup and the last update that your replica sent before its storage was lost, including operations that originated at your replica. (The packets also include more recent operations that originated at other replicas.) Each incoming packet also includes the requested return acknowledgment from the sending host.
Database <name> is unlocked after restoration.
Development work in the replica can now resume.