Backup, Restore, and Replication for Disaster Recovery — FoundationDB 7.1 mentions:
When DR is operating normally, the secondary database will lag behind the primary database by as little as a few seconds worth of database commits
It does not seem like fdbdr has a continuous mode, is it expected that we use our own scheduler to run this, or is that just missing in documentation?
Also, it seems that backup expiry is not automatic (e.g. expiring backups more than 30 days old), would it be expected to run this on an interval as well?
