Backup Central

Hello all...

This might be a silly quetion, however there
are times that some clients are down. My setup
aborts the backups, and then looses the indexes/log files
of pervious backup history.

So two questions, is there an option somewhere in the config to
tell amanda to overlook any clients that are down but still
continue on with the rest of the clients.

Second what would be the easiest way to regenerate the indexes
so I can use amrecover instead of amfetchdump on a per tape basis.


I am running amanda 2.5.2p1-4 on the server and on the clients
with a Debian O.S.
If I need to update everything to 2.6.* that might be posible, but
I had problems with IP6 previously.


Any suggestions would be appreciated, and I can supply my .conf if need
be.

Thanks.....

Tim Johnson wrote:

Hello all...

This might be a silly quetion, however there
are times that some clients are down. My setup
aborts the backups, and then looses the indexes/log files
of pervious backup history.

So two questions, is there an option somewhere in the config to
tell amanda to overlook any clients that are down but still
continue on with the rest of the clients.
That's what amanda should do, there is no way to do differently.
You should explain why your setup aborts the backup, that's what must be
fixed.

Jean-Louis

On Wednesday, March 30, 2011 11:28:05 AM Jean-Louis Martineau did opine:

Tim Johnson wrote:
Hello all...

This might be a silly quetion, however there

are times that some clients are down. My setup
aborts the backups, and then looses the indexes/log files
of pervious backup history.

So two questions, is there an option somewhere in the config to

tell amanda to overlook any clients that are down but still
continue on with the rest of the clients.

That's what amanda should do, there is no way to do differently.
You should explain why your setup aborts the backup, that's what must be
fixed.

Jean-Louis

FWIW Jean-Louis, my setup occasionally misses the 'shop' machine, because
of a power outage that outlasted the UPS its on. That has never caused the
rest of the backup session to abort.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
<http://tinyurl.com/ddg5bz>
<http://www.cantrip.org/gatto.html>
IBM's original motto:
Cogito ergo vendo; vendo ergo sum.

Not sure why it is puking on the event of a
non responsive machine (either not on the network or
estimate time out -- which is set for 8000 sec right now)

I will force a machine down and test again.


Thanks in advance.

On Wed, 30 Mar 2011, Jean-Louis Martineau wrote:

Tim Johnson wrote:

Hello all...

This might be a silly quetion, however there
are times that some clients are down. My setup
aborts the backups, and then looses the indexes/log files
of pervious backup history.

So two questions, is there an option somewhere in the config to
tell amanda to overlook any clients that are down but still
continue on with the rest of the clients.
That's what amanda should do, there is no way to do differently.
You should explain why your setup aborts the backup, that's what must be
fixed.

Jean-Louis

On 3/30/2011 08:30, gene heskett wrote:
On Wednesday, March 30, 2011 11:28:05 AM Jean-Louis Martineau did opine:

Tim Johnson wrote:
Hello all...

This might be a silly quetion, however there

are times that some clients are down. My setup
aborts the backups, and then looses the indexes/log files
of pervious backup history.

So two questions, is there an option somewhere in the config to

tell amanda to overlook any clients that are down but still
continue on with the rest of the clients.
That's what amanda should do, there is no way to do differently.
You should explain why your setup aborts the backup, that's what must be
fixed.

Jean-Louis
FWIW Jean-Louis, my setup occasionally misses the 'shop' machine, because
of a power outage that outlasted the UPS its on. That has never caused the
rest of the backup session to abort.

most systems can be configured to automatically power back on after a
power failure. this one should be no different.

On Wednesday, March 30, 2011 05:33:10 PM Christ Schlacta did opine:

On 3/30/2011 08:30, gene heskett wrote:
On Wednesday, March 30, 2011 11:28:05 AM Jean-Louis Martineau did
opine:
Tim Johnson wrote:
Hello all...

This might be a silly quetion, however there

are times that some clients are down. My setup
aborts the backups, and then looses the indexes/log files
of pervious backup history.

So two questions, is there an option somewhere in the config to

tell amanda to overlook any clients that are down but still
continue on with the rest of the clients.

That's what amanda should do, there is no way to do differently.
You should explain why your setup aborts the backup, that's what must
be fixed.

Jean-Louis

FWIW Jean-Louis, my setup occasionally misses the 'shop' machine,
because of a power outage that outlasted the UPS its on. That has
never caused the rest of the backup session to abort.

most systems can be configured to automatically power back on after a
power failure. this one should be no different.

Yes, but the UPS, if it runs down, shuts down for good and needs a hand re-
start, and about 2 minutes of charging before it will pick up the load. I
don't recall seeing the autostart option in that old Mach Speed's bios
either, but I haven't looked at it since turning off the on-board video
hardware, which is poison to the RTAI equipt kernel required. Its running
a stepper motor driven milling machine with a heartbeat in the 50 kilohertz
area.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
<http://tinyurl.com/ddg5bz>
<http://www.cantrip.org/gatto.html>
If the code and the comments disagree, then both are probably wrong.
-- Norm Schryer