On 3/9/2010 10:21 AM, Sylvain Viart - Gmail wrote:
> Hi,
>
>>> My question in fact is about interpreting current config?
>>> Is there tools which displays when a host will be backuped given the
>>> current full configuration?
>>>
>> Not exactly, but if you look at the host summary page you can figure it out. 
>>  A
>> backup happens when the time since the last backup (which is shown) reaches 
>> the
>> time you've set for the backup interval, and it will start at the first 
>> wakeup
>> that is not in a blackout interval.
>>
> hum, not really.
> You're right, but for example backuppc started a backup somewhat during
> my editing of the config files.

The first backup will start immediately when you add a host unless 
something else blocks it, so that's expected.  The blackout interval 
isn't respected until the host has been seen to be available outside of 
it for a configurable number of times.

> And the summary looks like :
>
>> Host backuppc-05 Backup Summary
>>
>> This PC has never been backed up!!
>>
>>      * This PC is used by backuppc.
>>      * Last status is state "idle" (backup canceled by user) as of
>> 2010-03-09 16:51.
>>      * Last error is "fileListReceive failed".
>>      * Pings to backuppc-05 have succeeded 1 consecutive times.
>
> Which seems totally useless.

No, if it is idle and hasn't had a backup it is going to try again at 
the next wakeup - unless that number of pings is enough to make it 
observe the blackout.

> may be a debug mode?

When you cancelled it, you had the opportunity to set a time to wait 
before trying again.

> The problem is that for each host I want to backup, will take 14h hour
> or more for the backup to complete.
> So I have to wait many days to see the result, and if I continue as it,
> will take month to setup the right timing. :-(

Just add the hosts at the time you want each to start. Or go to the 
cancel backup screen and put in a time to wait before starting.

> worse, I probably need to stop the backup on the host, because it's a
> backuppc server.
> hum, another $Conf{BlackoutPeriods} , should probably do the job on the
> remote host here.
>
> Of course the blackout behavior is a good thing for backup purpose.
> I mean, it's better to exclude dir, than to miss a new not included dir,
> form a backup point of view.

More relevant, you want the server to manage concurrency and to use 
whatever time window it can without breaking other things.

> It may ends with crontab scheduling.

Then it is left up to you to handle concurrency - and you probably can't 
do that as well as the server since you don't know when any backup will 
finish.

> I will post back other userfull parameter I found about that.
> Yes, BlackoutPeriod to stop remote host a specific day + a cron on the
> backup server, will be easyier to setup.
> I gonna try that.
>
> Instead of  reversing this behavior in full BlackoutPeriod syntax. :-)
> KISS principle.

Actually, I think scheduling is going to be the least of your problems 
in trying to make one backuppc instance back up others.  I'd expect it 
to take weeks to restore one to a point where it would be usable again. 
  I'd test that before going much farther.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/