Dave Sherohman wrote at about 14:03:05 +0100 on Thursday, March 11, 2021:
> If I were to set $Conf{MaxBackups} = 1 for one specific host, how would
> that be handled? Would it prevent that specific host from running
> backups unless there are no other backups in progress? Would it prevent
> any other backups from being started before that host finished? Would
> it do both? Or is that an inherently-global setting that has no effect
> if set for a single host?
I don't see how this would make sense at a per-host level. And any
behavior to have it differ by host is undocumented and not necessarily
predictable.
It would seem though to do the opposite of what you want in that one
hung rsync backup would prevent any other hosts from starting.
>
> My use-case here is that I've got a lot of linux hosts and a handful of
> windows machines. The linux hosts work great with standard ssh/rsync
> configuration, no problems there.
>
> The windows machines, on the other hand, are using a windows backuppc
> client that our windows admin found on sourceforge and it's having...
> problems... with handling shadow volumes. As in it appears to be
> failing to create them, which causes backup runs to take many hours as
> it waits for "device or resource busy" files to time out. Which ties up
> available slots in the MaxBackups limit and prevents the linux machines
> from being scheduled.
Look at the code that I recently submitted to the group to streamline
creation/deletion of shadow backups.
If the long wait is in the pre dump command, then there is not much
you can do other than to make sure that pre-dump command times out
faster. If the long wait is in a hung rsync, then you can change
$Conf{ClientTimeout} to a smaller number.
> So I'm thinking that it might work to temporarily set the windows hosts
> to MaxBackups = 1, if that would prevent multiple windows hosts from
> running at the same time and free up slots for the linux hosts to run.
> If it would also prevent linux hosts from running when a windows host is
> in progress, though, then that would just make things worse.
To me this sounds backasswords.
Why not just INCREAE MaxBackups to allow for a few hung Windows
machines. It's not like they are consuming any server bandwidth or cpu.
Alternatively, I might divide the blackout periods into one period for Linux
and one for Windows machines. That way Linux machines don't compete
with Windows machines for slots. You can then write a script to kill
any hanging Windows backups that bleed into your Linux slot.
But the only real solution is to figure out why and where the Windows
backups are hanging...
>
> Or is there some other way I could specify "run four backups at once,
> BUT only one of these six can run at a time (alongside three others
> which aren't in that group)"?
> ****
>
> _______________________________________________
> 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/
_______________________________________________
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/
