Hello,
I'm using amanda and all is OK.
But, now I want to implement level null dumps to be made say every first monday
of the month (piece of cake in crontab).
From the Status Update for July 2007 I learned to simply say
amanda config force
to get a level null dump for all hosts and
Hi,
Gerrit A. Smit -TI- schrieb:
I would like a way to tell amrecover that
those tapes are off site without too much fiddling around with setdate.
After your amdump you still can run amstatus. There you see the tapes amanda
used. This you can use for and automatic setting to no-reuse.
Gerrit A. Smit wrote:
I would like a way to tell amrecover that
those tapes are off site without too much fiddling around with setdate.
This question remains unsolved, I think.
By telling Amanda not to re-use a tape, she will refrain from using that tape
for dumping, but IMHO this doen't
Gerrit A. Smit -TI- schrieb:
By telling Amanda not to re-use a tape, she will refrain from using that tape
for dumping, but IMHO this doen't change anything for other operations.
amrecover will still use the tape for reading when needed according to the set
time, and I want to be able to prevent
On Mon, Aug 06, 2007 at 10:09:48AM -0500, Dustin J. Mitchell wrote:
The July Monthly Status Update is available on the wiki at
http://wiki.zmanda.com/index.php/Monthly_Status_Updates/July_2007
As always, feedback and comments are welcome and encouraged.
Thank you. This is very useful.
--
Marc Muehlfeld wrote:
Gerrit A. Smit wrote:
By telling Amanda not to re-use a tape, she will refrain from using that
tape for dumping, but IMHO this doesn't change anything for other
operations. amrecover will still use the tape for reading when needed
according to the set time, and I
On Tue, Aug 07, 2007 at 12:47:27PM +0200, Gerrit A. Smit -TI- wrote:
Gerrit A. Smit wrote:
I would like a way to tell amrecover that
those tapes are off site without too much fiddling around with setdate.
This question remains unsolved, I think.
By telling Amanda not to re-use a
Gerrit A. Smit -TI- schrieb:
If you don't want to have the full dumps seen by amrecovery why don't you
create a separate set for it?
Having a separate set means having a separate configuration, right?
Not a full separate configuration. In ~/KDD/amanda.conf (KDD is one of my two
sets) I
Marc Muehlfeld wrote:
Gerrit A. Smit -TI- schrieb:
If you don't want to have the full dumps seen by amrecovery why
don't you create a separate set for it?
Having a separate set means having a separate configuration, right?
Not a full separate configuration. In ~/KDD/amanda.conf (KDD is
On Mon, Aug 06, 2007 at 11:29:40PM -0400, Steve Newcomb wrote:
Any clues to offer?
I've never tried this, but I think you should take a look at the SSH
documentation for port forwarding. Run on the client,
ssh -l 10080:server:port server 'sleep 7000'
means that connections to port port on
On Tue, 7 Aug 2007, Dustin J. Mitchell wrote:
All in all, it sounds like a lot of work, unless this is a months-long
conference :)
Which is why it would be really nice to have a different triggering method
for performing backups on roaming laptops. Something that begins with the
laptop
Hello all,
I have a problem when trying to compile amanda 2.5.2p1 on an SCO
Openserver 5.0.7. I have made it through about 25 years with only
having to compile from a tarball a hand full of times, so I am not very
knowledgeble in this area.
Questions:
1. Is SCO Openserver 5.0.7 a supported OS?
On Tue, Aug 07, 2007 at 02:23:01PM -0500, Kenneth Berry wrote:
1. Is SCO Openserver 5.0.7 a supported OS? I can find very little
discussion on the Internet.
If you didn't get a warning beginning with
*
This machine, target type , is not known
to be fully supported by this
I have not heard from anyone with SCO experience yet.
I have not had time to search for the warning message yet. I will
report my findings later.
Kenneth
On Tue, 2007-08-07 at 15:04 -0500, Dustin J. Mitchell wrote:
On Tue, Aug 07, 2007 at 02:23:01PM -0500, Kenneth Berry wrote:
1. Is SCO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debian etch, VERSION=Amanda-2.5.1p1
One of the two clients on the DMZ has stopped responding to the server
on the LAN -- both amcheck and amdump.
diff says .amandahosts is identical on the 2 DMZ machines, and stat
shows amcheck causing the file's
On Tue, Aug 07, 2007 at 04:39:24PM -0600, Glenn English wrote:
One of the two clients on the DMZ has stopped responding to the server
on the LAN -- both amcheck and amdump.
A few things to check:
- forward or reverse DNS doesn't work for the server or the client.
- firewall on the client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dustin J. Mitchell wrote:
A few things to check:
- forward or reverse DNS doesn't work for the server or the client.
Hadn't thought of that. But unfortunately, it works perfectly.
- firewall on the client changed
It did change, but it's the
Glenn English wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dustin J. Mitchell wrote:
A few things to check:
- forward or reverse DNS doesn't work for the server or the client.
Hadn't thought of that. But unfortunately, it works perfectly.
- firewall on the client changed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Smith wrote:
If it works on the command line, try restarting inetd, and also
check the system logs to see if inetd has trouble starting it.
Bingo! Looks like maybe we had a little update.
ps aux | grep inetd said inetd wasn't running. In
Mitch Collinsworth [EMAIL PROTECTED] writes:
On Tue, 7 Aug 2007, Dustin J. Mitchell wrote:
All in all, it sounds like a lot of work, unless this is a months-long
conference :)
I agree. Changing a working backup configuration in order to handle a
temporarily out-of-town condition is just
On 6 Aug 2007, Steve Newcomb wrote:
Greetings from the Extreme Markup Languages Conference in Montreal.
(Which is a great conference but it's not what this note is about.)
Here I am at the Europa hotel with pretty good internet service.
Unfortunately, as in most such away-from-home
21 matches
Mail list logo
