Re: [BackupPC-users] BlackoutPeriods seemingly ignored

2011-06-02 Thread martin f krafft
also sprach Holger Parplies wb...@parplies.de [2011.06.01.2010 +0200]:
  To get my desired behaviour, I set BlackoutGoodCnt to 0 globally and
  deleted all global BlackoutPeriods.
[…]
 As I understand the concept of blackouts in BackupPC, I think it
 is meant to automagically adapt backup strategy to avoid the
 (global) blackout window (working hours) for all hosts that can
 be backed up outside this window. That would be the global
 blackout case above.
 
 Actually, I would modify your suggestion in that I'd set
 BlackoutGoodCnt to 0 *locally* in the pc config file, together
 with a local BlackoutPeriods setting. In the global config,
 BlackoutGoodCnt should be != 0. That way, you would get expected
 behaviour for both cases.

Yes, I understand the concept too, and it makes sense for an office.
However, I am using BackupPC chiefly to back up globally spread
machines. There are no office hours really. The only office hours
that exist are for the machines behind my DSL link, because I cannot
seem to get bandwidth shaping to work properly. Hence, the backups
should not start during the day but run during the night so that
they do not affect our normal usage.

PS: It's still suboptimal, because now at 23:00 hours, BackupPC
tries to back up all hosts at home, which congests the link
— I think it would be faster and more effective in this case to
back each of them up in series, rather than in parallel.
However, I do not want to set the global limit of concurrent
backups to 1. This is at the heart of the feature suggestion
I made here: http://bugs.debian.org/607761

  It wouldn't hurt if BackupPC had some sort of MaxAgeBeforeIgnoringBlackout
  setting to force-ensure some backups.
 
 If you don't have a backup yet, are you supposed to ignore the blackout window
 or not? You can't really say, respect it for three days, then ignore it if
 there is still no backup, at least not without defining a concept of when a
 host was added to the BackupPC configuration (timestamp of the host.pl file?).
 In any case, you have the email reminders that are supposed to alert you to
 the fact that there is no recent backup (or no backup at all). If such a case
 happens, you will need to consider whether your blackout window needs
 adjustment anyway. Automatically degrading from one backup per IncrPeriod to
 one backup per MaxAgeBefore... doesn't seem like a sufficient resolution.

Sure, you just forgot half a dozen parameters to allow tweaking of
all aspects. ;)

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
good advice is something a man gives
 when he is too old to set a bad example.
  -- la rouchefoucauld
 
spamtraps: madduck.bo...@madduck.net


digital_signature_gpg.asc
Description: Digital signature (see	http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BlackoutPeriods seemingly ignored

2011-06-02 Thread Christian Völker
Hi Martin,

I had a similar issue here with a remote site where I have a couple of
hosts to backup. Only one host at a time should be backuped as otherwise
the slow remote connection will be congested.

What I did was to reduce (or raise?) the ping timeout time. As BackupPC
tries to ping the destination hosts before attempting to back up I know
the ping times to the remote office go up to (let's say) 2,000ms instead
of the default ~100ms.
So BackupPC now pings one remote host, notice a good ping and starts to
backup this guy. Then it attempts to backup a second host on the remote
office, but as the ping time is above 1,500ms this guy is not backed up
and I have only a single host backed up from the remote office.

In parallel it's backing up the local hosts without any issues.

Greetings

Christian




--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BlackoutPeriods seemingly ignored

2011-06-02 Thread Tod Detre
On Thu, Jun 2, 2011 at 4:28 AM, martin f krafft madd...@madduck.net wrote:
 Yes, I understand the concept too, and it makes sense for an office.
 However, I am using BackupPC chiefly to back up globally spread
 machines. There are no office hours really. The only office hours
 that exist are for the machines behind my DSL link, because I cannot
 seem to get bandwidth shaping to work properly. Hence, the backups
 should not start during the day but run during the night so that
 they do not affect our normal usage.

Don't forget about rsync's internal '--bwlimit' option. It works great
to keep a single rsync from flooding a connection. The only problem
I've run into with it is the filelist stage is not limited, but the
transfer is.

-- 
Tod

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BlackoutPeriods seemingly ignored

2011-06-02 Thread John Rouillard
On Thu, Jun 02, 2011 at 10:31:57AM -0400, Tod Detre wrote:
 On Thu, Jun 2, 2011 at 4:28 AM, martin f krafft madd...@madduck.net wrote:
  Yes, I understand the concept too, and it makes sense for an office.
  However, I am using BackupPC chiefly to back up globally spread
  machines. There are no office hours really. The only office hours
  that exist are for the machines behind my DSL link, because I cannot
  seem to get bandwidth shaping to work properly. Hence, the backups
  should not start during the day but run during the night so that
  they do not affect our normal usage.
 
 Don't forget about rsync's internal '--bwlimit' option. It works great
 to keep a single rsync from flooding a connection. The only problem
 I've run into with it is the filelist stage is not limited, but the
 transfer is.

Also you can implement a semaphore/queuing system similar to:

http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg13698.html

So only 1 backup runs at a time for a site.

-- 
-- rouilj

John Rouillard   System Administrator
Renesys Corporation  603-244-9084 (cell)  603-643-9300 x 111

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BlackoutPeriods seemingly ignored

2011-06-01 Thread Holger Parplies
Hi,

martin f krafft wrote on 2011-05-30 14:28:23 +0200 [Re: [BackupPC-users] 
BlackoutPeriods seemingly ignored]:
 also sprach martin f krafft madd...@madduck.net [2011.05.19.0925 +0200]:
  [...]
  It seems almost like BackupPC is just ignoring BlackoutPeriods, [...]
 
 To answer my own question:

sorry that you didn't get a reply.

 It is really such that BlackoutPeriods only work once and as long as
 BlackoutGoodCnt pings succeed in succession.

Correct. (Well, one bad ping won't end it, BlackoutBadPingLimit successive
bad pings will.)

 To get my desired behaviour, I set BlackoutGoodCnt to 0 globally and
 deleted all global BlackoutPeriods.

That's a good thing to keep in mind. Strangely, I can't remember anyone
suggesting that yet, even though it is rather obvious (and documented, as
I see).

Personally, I only back up servers automatically, so I simply set
WakeupSchedule to not interfere with normal operation, much like blackouts
are meant to work (which also turns out to be documented).

 The only disadvantage is that if a host never comes online during
 this period, it won't be backed up, but I can live with that.

With per-host blackouts it seems reasonable to assume that they are meant
as they were specified. For a global blackout it seems reasonable to assume
that it doesn't apply to hosts that are never (or seldom) online outside
the blackout window.

As I understand the concept of blackouts in BackupPC, I think it is meant to
automagically adapt backup strategy to avoid the (global) blackout window
(working hours) for all hosts that can be backed up outside this window.
That would be the global blackout case above.

Actually, I would modify your suggestion in that I'd set BlackoutGoodCnt to 0
*locally* in the pc config file, together with a local BlackoutPeriods
setting. In the global config, BlackoutGoodCnt should be != 0. That way, you
would get expected behaviour for both cases.

 It wouldn't hurt if BackupPC had some sort of MaxAgeBeforeIgnoringBlackout
 setting to force-ensure some backups.

If you don't have a backup yet, are you supposed to ignore the blackout window
or not? You can't really say, respect it for three days, then ignore it if
there is still no backup, at least not without defining a concept of when a
host was added to the BackupPC configuration (timestamp of the host.pl file?).
In any case, you have the email reminders that are supposed to alert you to
the fact that there is no recent backup (or no backup at all). If such a case
happens, you will need to consider whether your blackout window needs
adjustment anyway. Automatically degrading from one backup per IncrPeriod to
one backup per MaxAgeBefore... doesn't seem like a sufficient resolution.

Regards,
Holger

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BlackoutPeriods seemingly ignored

2011-05-30 Thread martin f krafft
also sprach martin f krafft madd...@madduck.net [2011.05.19.0925 +0200]:
 I have a few hosts that should only be backed up between 23:00 and
 7:00, i.e. when the network is not used much. Hence, I set
 BlackoutPeriod
[…]
 However, all the PCs ended up being queued at 09:00 this morning,
 and their last backup was yesterday between 17:00 and 19:00 o'clock.
 It seems almost like BackupPC is just ignoring BlackoutPeriods, but
 I doubt that this is the case.

To answer my own question:

It is really such that BlackoutPeriods only work once and as long as
BlackoutGoodCnt pings succeed in succession. I was under the (false)
impression that this was some sort of internal blackout period, and
BlackoutPeriods would be custom and just work.

To get my desired behaviour, I set BlackoutGoodCnt to 0 globally and
deleted all global BlackoutPeriods.

Now, for each host that I do not want backed up during the day,
I add an appropriate BlackoutPeriod.

The only disadvantage is that if a host never comes online during
this period, it won't be backed up, but I can live with that.

It wouldn't hurt if BackupPC had some sort of
MaxAgeBeforeIgnoringBlackout setting to force-ensure some backups.

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
they that can give up essential liberty
 to obtain a little temporary safety
 deserve neither liberty nor safety.
  -- benjamin franklin
 
spamtraps: madduck.bo...@madduck.net


digital_signature_gpg.asc
Description: Digital signature (see	http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


[BackupPC-users] BlackoutPeriods seemingly ignored

2011-05-19 Thread martin f krafft
Hello,

I have a few hosts that should only be backed up between 23:00 and
7:00, i.e. when the network is not used much. Hence, I set
BlackoutPeriod for them to

  $Conf{BlackoutPeriods} = [
{
  'hourEnd' = '23',
  'weekDays' = [
'1',
'2',
'3',
'4',
'5',
'6',
'7'
  ],
  'hourBegin' = '7'
}
  ];

which I can verify in the web interface (see attached image).

However, all the PCs ended up being queued at 09:00 this morning,
and their last backup was yesterday between 17:00 and 19:00 o'clock.
It seems almost like BackupPC is just ignoring BlackoutPeriods, but
I doubt that this is the case.

Any idea what I might be doing wrong?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
now, bring me that horizon.
   -- captain jack sparrow
 
spamtraps: madduck.bo...@madduck.net
attachment: backuppc.png

digital_signature_gpg.asc
Description: Digital signature (see	http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/