Hi,
I'm in a bit of a pickle. I've been migrating my v4 pool to some new
infrastructure for ... a while. It's taking much longer than expected, and now
I have a request to provide some data from the backup pool for a legal case.
While the pool transfer (rsync) was running, I had the backuppc service stopped
and disabled. But, it looks like that also prevents me from talking to BPC
through its binaries. bin/BackupPC_serverMesg fails explicitly ("Can't connect
to server"...) and bin/BackupPC_ls returns empty results.
Is there a correct way to turn the backuppc service on again but *ensure* that
it doesn't make any changes to the pool? I don't want to stop and restart the
rsync because it takes a long time to pick up where it left off (days, at this
point).
I've crawled through the documentation, web, mailing list, etc., but might've
missed something.
Absent a recommended way to do this, I might try:
- Making most of the binaries non-executable;
- Suspending the rsync, `mount -o remount,ro` the pool, and re-foregrounding
the rsync;
- Clearing the wakeup schedule for all hosts and manually disabling
bin/BackupPC_nightly;
- ...??
Thanks,
/R
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
