Merge pull request #142 from HarperDB/plexus_start_time

add replication docs for startTime and copyTablesToCatchUp

Author: kriszyp

docs/deployments/configuration.md

@@ -206,15 +206,21 @@ replication:
 
 `routes` - _Type_: array;
 
-An array of routes to connect to other nodes. Each element in the array can be either a string or an object with `hostname` and `port` properties.
+An array of routes to connect to other nodes. Each element in the array can be either a string or an object with `hostname`, `port` and optionally `startTime` properties.
+
+`startTime` - _Type_: string; ISO formatted UTC date string. 
+
+Replication will attempt to catch up on all remote data upon setup. To start replication from a specific date, set this property.
 
 ```yaml
 replication:
+  copyTablesToCatchUp: true
   hostname: server-one
   routes:
     - wss://server-two:9925 # URL based route
     - hostname: server-three # define a hostname and port
       port: 9930
+      startTime: 2024-02-06T15:30:00Z
 ```
 
 `port` - _Type_: integer; _Default_: 9925 (the operations API port `operationsApi.port`)
@@ -229,6 +235,10 @@ The port to use for secure replication connections.
 
 When true, HarperDB will verify certificates against the Node.js bundled CA store. The bundled CA store is a snapshot of the Mozilla CA store that is fixed at release time.
 
+`copyTablesToCatchUp` - _Type_: boolean; _Default_: true
+
+Replication will first attempt to catch up using the audit log. If unsuccessful, it will perform a full table copy. When set to `false`, replication will only use the audit log.
+
 ***
 
 ### `clustering` using NATS