[email protected] wrote at about 09:52:03 -0400 on Friday, October 28, 2022:
> Rob Sheldon wrote at about 21:05:06 -0700 on Thursday, October 27, 2022:
> > I considered that, but it's unclear whether BackupPC_nightly or
> _updateRefCount might still run.
>
> If there have been no changes to the backups since the last full run
> of BackupPC_nightly, then there should be no additional changes to the
> pool or ref counts as obviously nothing has changed.
>
> Alternatively, you could set
> $Conf{BackupsDisable} = 1;
> for all of your hosts.
>
> Better yet, setting:
> $Conf{WakeupSchedule} = [];
> *should* prevent waking up for both backups and BackupPC_nightly --
> and would thus in one line do everything you want.
>
Also, if you are worried about BackupPC_nightly inadvertently running,
I would suggest renaming the executable temporarily so it can be found/run.
> Alternatively, use backuppcfs which creates an easily browsable fuse
> filesystem for all of your backups -- it works even when backuppc is
> *not* running.
>
> Personally, in most cases, I find backuppcfs much easier to use to
> access backups than using either the web gui or tar/rsync restores.
>
> >
> > On Thu, Oct 27, 2022, at 8:19 PM, Jon Daley via BackupPC-users wrote:
> > > Can you simply edit the config BlackoutPeriods value to block out all
> of
> > > the time?
> > >
> > > On Thu, 27 Oct 2022, Rob Sheldon wrote:
> > >
> > > > 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
> > [email protected]
> > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> > Wiki: https://github.com/backuppc/backuppc/wiki
> > Project: https://backuppc.github.io/backuppc/
>
>
> _______________________________________________
> BackupPC-users mailing list
> [email protected]
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: https://github.com/backuppc/backuppc/wiki
> Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
