SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Removing a machine from the list of failures requiring atten
Author Message
Post Removing a machine from the list of failures requiring atten 
I have a machine that is very irregularly available on the network, but
that I want backups of.

Last time it got taken offline before the backup run finished. I now
have it listed as a failure that needs attention...

Is there any other way than a successful backup for me to tell BackupPC
that I have given this attention and that it is really OK to stop
telling me about it now?

Daniel

--
It is well to remember that the entire universe, with one trifling exception,
is composed of others.
-- John Andrew Holmes


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post Removing a machine from the list of failures requiring atten 
Daniel,

You can add the following to the machines per-pc config.pl file and it
will no longer try to back this machine up. Manual backups will work
fine. I use this for offsite reps that are in once to twice a year.
You'll still need to get a successful backup of the machine to clear the
error, but it will no longer try to back the system up on a daily schedule.

$Conf{FullPeriod} = -1;

The FullPeriod is surrounded by a curly bracket, not an open parenthesis.

Doug



Daniel Pittman wrote:

I have a machine that is very irregularly available on the network, but
that I want backups of.

Last time it got taken offline before the backup run finished. I now
have it listed as a failure that needs attention...

Is there any other way than a successful backup for me to tell BackupPC
that I have given this attention and that it is really OK to stop
telling me about it now?

Daniel







-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post Removing a machine from the list of failures requiring atten 
But what about the cases where the machine no longer exists? I put this
entry as well as limit the notification period on these old systems,
but they are still reported on the status web page, which I would like
to clear up. I keep these retired systems in BackupPC for 3-4 months so
that the user is able to recover any files that somehow didn't get
copied to their new system.

Steve

On Mar 6, 2004, at 9:28 AM, Doug Lytle wrote:
Daniel,

You can add the following to the machines per-pc config.pl file and it
will no longer try to back this machine up. Manual backups will work
fine. I use this for offsite reps that are in once to twice a year.
You'll still need to get a successful backup of the machine to clear
the error, but it will no longer try to back the system up on a daily
schedule.

$Conf{FullPeriod} = -1;

The FullPeriod is surrounded by a curly bracket, not an open
parenthesis.

Doug



Daniel Pittman wrote:

I have a machine that is very irregularly available on the network,
but
that I want backups of.

Last time it got taken offline before the backup run finished. I now
have it listed as a failure that needs attention...

Is there any other way than a successful backup for me to tell
BackupPC
that I have given this attention and that it is really OK to stop
telling me about it now?

Daniel






-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post Removing a machine from the list of failures requiring atten 
Steve Waltner writes:

But what about the cases where the machine no longer exists? I put this
entry as well as limit the notification period on these old systems,
but they are still reported on the status web page, which I would like
to clear up. I keep these retired systems in BackupPC for 3-4 months so
that the user is able to recover any files that somehow didn't get
copied to their new system.

I have not tested this, but how about this:

- put $Conf{FullPeriod} = -1; (or -2) in the respective hosts config.pl,

- remove the host(s) from the conf/hosts file,

- tell BackupPC to reload (kill -HUP pid or /etc/init.d/backuppc reload),

- add the host(s) back to the conf/hosts file,

- tell BackupPC to reload (kill -HUP pid or /etc/init.d/backuppc reload).

In any case, this will be fixed in 2.1.x. After 2 days, any machine
with disabled backups (ie: $Conf{FullPeriod} < 0) that has an error
on the last backup will have the error cleared and the status will
be set back to idle. That way you have time to see errors on manual
backups, but they will eventually go away.

Craig


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post Removing a machine from the list of failures requiring atten 
On Mar 16, 2004, at 2:08 AM, Craig Barratt wrote:
Steve Waltner writes:

But what about the cases where the machine no longer exists? I put
this
entry as well as limit the notification period on these old systems,
but they are still reported on the status web page, which I would like
to clear up. I keep these retired systems in BackupPC for 3-4 months
so
that the user is able to recover any files that somehow didn't get
copied to their new system.

I have not tested this, but how about this:

- put $Conf{FullPeriod} = -1; (or -2) in the respective hosts
config.pl,

- remove the host(s) from the conf/hosts file,

- tell BackupPC to reload (kill -HUP pid or /etc/init.d/backuppc
reload),

- add the host(s) back to the conf/hosts file,

- tell BackupPC to reload (kill -HUP pid or /etc/init.d/backuppc
reload).

In any case, this will be fixed in 2.1.x. After 2 days, any machine
with disabled backups (ie: $Conf{FullPeriod} < 0) that has an error
on the last backup will have the error cleared and the status will
be set back to idle. That way you have time to see errors on manual
backups, but they will eventually go away.

Craig

Thanks for the suggestion Craig. Doing this temporary host removal
cleared the error message on the Server Status web page. The exact
config file that I use on these disabled hosts is:

$Conf{FullPeriod} = -1;
$Conf{EMailNotifyMinDays} = 365;

This keeps the system from attempting to backup the system (and
generating new errors on the web page) as well as not sending the user
warning messages about their old computer not getting backed up.

The new feature in 2.1 sounds great. I'll make the assumption that the
2 day window is configurable in config.pl since I would probably want
to set that to something like 7-14 days.

Thanks again for your effort on BackupPC. I have had this implemented
for a while and within the last month have saved the bacon for 3 users
who had laptop drives die. Having automated backups run on these
systems whenever they happen to be connected to the network has been
very nice. I recently needed to upgrade my pool from 150 GB to 500 GB
and keep getting more users connected to the system.

Steve



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post Removing a machine from the list of failures requiring atten 
Steve Waltner writes:

Thanks for the suggestion Craig. Doing this temporary host removal
cleared the error message on the Server Status web page. The exact
config file that I use on these disabled hosts is:

$Conf{FullPeriod} = -1;
$Conf{EMailNotifyMinDays} = 365;

This keeps the system from attempting to backup the system (and
generating new errors on the web page) as well as not sending the user
warning messages about their old computer not getting backed up.

Ah, yes. Perhaps emails should be disabled on any host with
$Conf{FullPeriod} < 0?

The new feature in 2.1 sounds great. I'll make the assumption that the
2 day window is configurable in config.pl since I would probably want
to set that to something like 7-14 days.

It's not configurable, but I can add a config setting for it.
I was hoping to avoid more gratuitous config variables. The
name would be perverse, maybe $Conf{DisabledHostErrorTimeout}?

Thanks again for your effort on BackupPC. I have had this implemented
for a while and within the last month have saved the bacon for 3 users
who had laptop drives die. Having automated backups run on these
systems whenever they happen to be connected to the network has been
very nice. I recently needed to upgrade my pool from 150 GB to 500 GB
and keep getting more users connected to the system.

Thanks for the feedback!

Craig


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB