My team is running a foundationdb cluster, version 5.1.7. There was a DR continuous backup kicked off awhile ago, and it appears to have been aborted without using the
--cleanup flag. The destination cluster no longer exists, and I don’t have the address for it. Now we have the
\xff\x02/blog/ prefix filling up with backup logs that are not being consumed. We need to clear them out and stop them from accumulating, since they are causing our cluster to grow much faster than we scaled it for.
Is there a way to determine what the destination cluster is? I’ve looked under
\xff\x02/backupstatus/dr_backup/json but don’t know how or if I can figure out the destination from the value there.
How can I abort the DR backup? My understanding is that the
fdbdr command only works when there’s a
dr_agent running. When I try to run them without passing in a valid, running destination cluster, the fdbdr commands hang. When I tried recreating the destination cluster with a fresh, empty database, the fdbdr commands returned but gave me an error
ERROR: A DR was not running on tag `default' Fatal Error: Backup unneeded request
Our Plan B is to dump all the data from our cluster into a file, destroy and recreate the database, and load the data back in. But I’m wondering if there’s a better, supported way to clean up the
Anticipating the obvious question – we plan to upgrade to version 6, but we’d like to get a handle on our data bloat problem first.