Hello,
we backup several Servers with BackupPC - on every server we got several
Directories - everyone as an own Host ... (dir1, dir2, dir3, ... and mapped
those names to the IP in /etc/hosts)
Is it possible that backuppc allows you to put your hosts into groups (aka
queues) so that you could
On Thu, Aug 28, 2014 at 7:01 AM, Andreas Schnederle-Wagner -
Futureweb.at schnede...@futureweb.at wrote:
Is it possible that backuppc allows you to put your hosts into groups (aka
queues) so that you could limit the number of backup jobs running from any
specific queue/host group?
No you
This is a feature I've wanted as well. I have virtual machines running on
multiple hypervisors, and I'd prefer to only run one backup per hypervisor at a
time. If I could do that, I could get away with backups during the day... but
if I back up the main file server and the groupware server at
Hello,
is it possible to have variable substitution at run-time for RsyncShareName?
Following Scenario:
- Server Directory Structure
o /ctDIR1
o /ctDIR2
o /ctDIR3
o ...
- Within /etc/hosts we have:
o *IP-1* ctdir1
o *IP-1* ctdir2
o
On Thu, Aug 28, 2014 at 8:11 AM, Carl Cravens ccrav...@excelii.com wrote:
This is a feature I've wanted as well. I have virtual machines running on
multiple hypervisors, and I'd prefer to only run one backup per hypervisor at
a time. If I could do that, I could get away with backups during
Andreas Schnederle-Wagner - Futureweb.at wrote at about 14:31:49 + on
Thursday, August 28, 2014:
Hello,
is it possible to have variable substitution at run-time for
“RsyncShareName“?
Following Scenario:
- Server Directory Structure
o
On Thu, Aug 28, 2014 at 9:59 AM, backu...@kosowsky.org wrote:
While it's not clear to me what you are actually trying to do, there
is a *lot* that you can do short of patching the Rsync.pm file.
- You can have separate config files per host
- You can put arbitrary executable Perl code
I can't complete all the backups in a day with a maxbackups of 1. It's
unreasonable to micromanage the blackout periods for 70+ hosts to keep certain
ones from overlapping.
I've coped with the problem, but it's something that an
only-one-host-at-a-time-from-this-group feature would make a lot
The Reason we did this ist o avoid custom Config Files for each Host.
We only need to create the Host with name 'ctDIR8' and everything works like a
charm ... so only thehosts file needs tob e changed when adding/removing
Hosts ...
Andreas Schnederle-Wagner
Futureweb OG
Innsbrucker Str. 4
6380
On Thu, Aug 28, 2014 at 10:36 AM, Carl Cravens ccrav...@excelii.com wrote:
I can't complete all the backups in a day with a maxbackups of 1. It's
unreasonable to micromanage the blackout periods for 70+ hosts to keep
certain ones from overlapping.
I've coped with the problem, but it's
On Thu, Aug 28, 2014 at 10:41 AM, Andreas Schnederle-Wagner -
Futureweb.at schnede...@futureweb.at wrote:
The Reason we did this ist o avoid custom Config Files for each Host.
We only need to create the Host with name 'ctDIR8' and everything works like
a charm ... so only thehosts file needs
Andreas Schnederle-Wagner - Futureweb.at wrote at about 15:41:11 + on
Thursday, August 28, 2014:
The Reason we did this ist o avoid custom Config Files for each Host.
We only need to create the Host with name 'ctDIR8' and everything works like
a charm ... so only thehosts file needs
On Thu, Aug 28, 2014 at 10:36:50AM -0500, Carl Cravens wrote:
I can't complete all the backups in a day with a maxbackups of 1.
It's unreasonable to micromanage the blackout periods for 70+ hosts to
keep certain ones from overlapping.
I've coped with the problem, but it's something that an
Andreas Schnederle-Wagner - Futureweb.at wrote at about 15:41:11 + on
Thursday, August 28, 2014:
The Reason we did this ist o avoid custom Config Files for each Host.
We only need to create the Host with name 'ctDIR8' and everything works
like a charm ... so only thehosts file
On Thu, Aug 28, 2014 at 12:18 PM, Andreas Schnederle-Wagner -
Futureweb.at schnede...@futureweb.at wrote:
Andreas Schnederle-Wagner - Futureweb.at wrote at about 15:41:11 + on
Thursday, August 28, 2014:
The Reason we did this ist o avoid custom Config Files for each Host.
We only
Les Mikesell wrote at about 13:53:04 -0500 on Thursday, August 28, 2014:
On Thu, Aug 28, 2014 at 12:18 PM, Andreas Schnederle-Wagner -
Futureweb.at schnede...@futureweb.at wrote:
Andreas Schnederle-Wagner - Futureweb.at wrote at about 15:41:11 + on
Thursday, August 28, 2014:
On 29/08/14 01:36, Carl Cravens wrote:
I can't complete all the backups in a day with a maxbackups of 1. It's
unreasonable to micromanage the blackout periods for 70+ hosts to keep
certain ones from overlapping.
I've coped with the problem, but it's something that an
On Thu, Aug 28, 2014 at 3:49 PM, backu...@kosowsky.org wrote:
Aren't $client and $host set by the time you need them (as documented
to be used in $Conf(RsyncArgs}, $conf{DumpPreUserCmd}, etc.)?
You are correct that at the time the config file is sourced, the
variable $host (not
18 matches
Mail list logo
