Hallo all
I have a problem with a host here.I ghet the following when running amcheck
from the tapehost
WARNING: backu.client.net: selfcheck request timed out. Host down?
Now I did the following
netstat -a | grep -i amanda
the output is below
udp0 0 *:amanda
Mozzi wrote:
Hallo all
I have a problem with a host here.I ghet the following when running amcheck
from the tapehost
WARNING: backu.client.net: selfcheck request timed out. Host down?
Now I did the following
netstat -a | grep -i amanda
the output is below
udp0 0 *:amanda
Hi,
I'm in the process of checking out amanda, and I've run into a slight
difficulty: the disk I was using as a holding disk has bad blocks and
amflush cannot flush out the dumps. What should I do? Can I make
amanda forget about the disk it failed to flush out so that it will get
rescheduled?
On Fri, 3 Jan 2003, Henning P. Schmiedehausen wrote:
Examples from the dump report:
newww.gta. / lev 0 FAILED [Request to newww.gta.com timed out.]
bento.gta. / lev 0 FAILED [Request to bento.gta.com timed out.]
Do you have a firewall between you and the servers? Maybe a SonicWall?
I
Hi gurus,
What could be the reason that some boxes get backed up with level 0
every day (although the dumpcycle set up for 7 days). Does it mean that
some index (or whatever it is) files got corrupted so Amanda does not
track the backups properly ?
What so I do to fix the problem in this
On Fri, 3 Jan 2003 at 11:10am, Yura Pismerov wrote
What could be the reason that some boxes get backed up with level 0
every day (although the dumpcycle set up for 7 days). Does it mean that
some index (or whatever it is) files got corrupted so Amanda does not
track the backups properly ?
On Friday 03 January 2003 11:10, Yura Pismerov wrote:
Hi gurus,
What could be the reason that some boxes get backed up with level
0 every day (although the dumpcycle set up for 7 days). Does it
mean that some index (or whatever it is) files got corrupted so
Amanda does not track the backups
Yura Pismerov wrote:
Hi gurus,
What could be the reason that some boxes get backed up with level 0
every day (although the dumpcycle set up for 7 days). Does it mean that
some index (or whatever it is) files got corrupted so Amanda does not
track the backups properly ?
What so I
At 03:53 PM 1/3/2003 +0100, Alexander JOLK wrote:
... holding disk has bad blocks and
amflush cannot flush out the dumps. What should I do? Can I make
amanda forget about the disk it failed to flush out so that it will get
rescheduled? Or forget about the whole amdump run?
amadmin
At 03:53 PM 1/3/2003 +0100, Alexander JOLK wrote:
... holding disk has bad blocks and
amflush cannot flush out the dumps. What should I do? Can I make
amanda forget about the disk it failed to flush out so that it will get
rescheduled? Or forget about the whole amdump run?
amadmin
[root@backup root]# su amanda -c amcheck DailySet1
bash: /root/.bashrc: Permission denied
Amanda Tape Server Host Check
-
Holding disk /var/tmp: 2330384 KB disk space available, that's plenty
NOTE: skipping tape-writable test
Tape Indyme001 label ok
Server check took
At 2003-01-02T15:26:06Z, Joshua Baker-LePain [EMAIL PROTECTED] writes:
Amanda uses a suid wrapper to run tar as root when making backups.
I guess my question was triggered by error messages like:
root@kanga:~# su operator -c amcheck -c Daily
Amanda Backup Client Hosts Check
Hey folks.
I've successfully done this on 4 OSX machines now, all v10.1+. I figure
this'll help out those who need it. (there sure wasn't much information
available when I started!)
First, you'll need at least one OSX machine with the developers kit
installed, since you need to compile
On Fri, Jan 03, 2003 at 11:12:18AM -0800, John Oliver wrote:
[root@backup root]# su amanda -c amcheck DailySet1
bash: /root/.bashrc: Permission denied
Amanda Tape Server Host Check
-
Holding disk /var/tmp: 2330384 KB disk space available, that's plenty
NOTE:
On Fri, Jan 03, 2003 at 02:27:30PM -0600, Deb Baddorf wrote:
Up until now, amanda has used /var/lib/amanda So I created
/usr/local/lib/amanda/ and chowned it to amanda, but I still get the
same message.
On the client, right?
In this case, sure... I did this locally.
And did you put
Not sure this is really Amanda related, but I'm sure someone here ran into the
same problem.
I'm trying to back up 2 linux servers and one windows 2000 server with amanda.
There are a few Macs on the network, storing files in those servers.
Machintosh will let users save files with about any
On Friday 03 January 2003 14:12, John Oliver wrote:
[root@backup root]# su amanda -c amcheck DailySet1
bash: /root/.bashrc: Permission denied
Amanda Tape Server Host Check
-
Holding disk /var/tmp: 2330384 KB disk space available, that's
plenty NOTE: skipping
amrestore: could not stat /dev/rmt0.1
That message comes from a pretty simple stat() system call on the tape
device. Was the drive ready when you did this? I assume /dev/rmt0.1
was the right device name?
In any case, could you apply the following patch and report what the
error code is (it
If I use 2.4.3 I have to specify the blocksize to get tapetype to work
(20). If I just it run I get short write errors and also problems about
multiple block write errors in /var/log/messages. Same for trying to
label a tape.
Sounds like the drive is set to use a fixed hardware block size. If
And did you put a file exclude.gtar in there?
Yes, I did, and that got rid of the message. But if amanda needs this
file, why doesn't it just create it?
Amanda doesn't need it --- but you told her to look for it.
It's a file that YOU fill in, to say what to exclude from
the gnutar
can somebody enlighten me a little about the ./tapetype command?
What determines the blocksize and what's meant by estsize??
The blocksize is the size of each tape block you are going to tell
Amanda to use. Prior to 2.4.3 that was fixed at 32 KBytes. At 2.4.3 you
can specify it in the tapetype
On Fri, Jan 03, 2003 at 05:03:21PM -0500, Jon LaBadie wrote:
On Fri, Jan 03, 2003 at 01:15:35PM -0800, John Oliver wrote:
On Fri, Jan 03, 2003 at 02:27:30PM -0600, Deb Baddorf wrote:
And did you put a file exclude.gtar in there?
Yes, I did, and that got rid of the message. But
Even though amanda does not run as root, the tar command which archives
everything does run as root. (I believe this is true because I have
individual files which have 700 permissions which do get archived.)
That's correct.
However, when the amcheck command is run, it is not running as root,
I'm in the process of checking out amanda, and I've run into a slight
difficulty: the disk I was using as a holding disk has bad blocks and
amflush cannot flush out the dumps. What should I do? Can I make
amanda forget about the disk it failed to flush out so that it will get
rescheduled? Or
WARNING: backu.client.net: selfcheck request timed out. Host down?
Now I did the following
netstat -a | grep -i amanda
the output is below
udp0 0 *:amanda*:*
I assume you checked this on the client (backu), not the server (the
machine you ran amcheck on),
So, what now? It *still* doesn't see the disk in the local machine.
Some messages in this thread are missing, so I'm not sure what else went
on here.
I assume you've run amcheck? And it doesn't have anything interesting
to say about /dev/hda1?
The next place to look would be the
I received these messages at the end of a backup:
driver: dumper3 exited with signal 11
Oops. :-)
I am running version 2.4.3.
What OS?
I believe most files were written to tape, but these messages look unusual.
I did not find core files, but they may be somewhere I haven't yet
discovered.
taper: tape DailySet101 kb 1408 fm 1 writing filemark: I/O error
...
Now, I know that there is enough room on the tape for what I am backing up.
(40G tape, /home on the cvs server = 188M, /home on the cclcsup server = 3.1G)
Amanda is just telling you what the OS told it -- there was an I/O
OK, here are the diagnostics:
amcheck -c Daily
Amanda Backup Client Hosts Check
ERROR: localhost: [could not access /mnt/sglab/monica/DPO
(/mnt/sglab/monica/DPO): Permission denied]
ERROR: localhost: [could not access /mnt/sglab/monica/BACKUPS
Amflush has stopped working recently. ...
Not sure if you saw it, but a patch was posted recently for this.
Look for amflush hangs in the archive.
Bill Hults
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Can't answer most of your questions (no experience using RAIT), but ...
... Do all of the tools work with it
(amverify, amrecover, amcheck, amadmin )? ...
The RAIT (and file and normal tape and null) support is at a pretty
low level in Amanda, so all the tools should work the same, assuming
On Fri, Jan 03, 2003 at 02:34:32PM -0800, John Oliver wrote:
On Fri, Jan 03, 2003 at 05:03:21PM -0500, Jon LaBadie wrote:
On Fri, Jan 03, 2003 at 01:15:35PM -0800, John Oliver wrote:
On Fri, Jan 03, 2003 at 02:27:30PM -0600, Deb Baddorf wrote:
And did you put a file exclude.gtar
On Fri, Jan 03, 2003 at 11:37:18PM +, David Trusty wrote:
OK, here are the diagnostics:
amcheck -c Daily
Amanda Backup Client Hosts Check
ERROR: localhost: [could not access /mnt/sglab/monica/DPO
(/mnt/sglab/monica/DPO): Permission denied]
ERROR:
ERROR: localhost: [could not access /mnt/sglab/monica/DPO
(/mnt/sglab/monica/DPO): Permission denied]
...
Looks like nsf mounts. ...
What does the National Science Foundation have to do with this??? :-)
Sorry, couldn't resist. I've flipped those characters many times myself.
In addition
Is there a reason indexing isn't on by default? They don't really take up
that much space ...
I beg to differ:
$ du -sk /var/amanda/index/champion
4641743 /var/amanda/index/champion
Yup. Four and a half *GBytes*.
Now, granted, this is on a very large Amanda configuration. But it's
not
amrecover will in my setup make a completely wrong guess about what disk
to consider at startup in most cases. The example output included below
should illustrate the problem; /usr/freeware/apache is not on the /u
filesystem, and it has a separate disklist entry. Any ideas what is going
on?
* amrecover does not rewind the tape for you. I'm sure that there
is a good reason for this, but I don't know what it is. You have
to rewind the tape first, then run the command.
The normal mode for amrecover (actually, amrestore, which it calls)
is to do a linear scan of the tape searching
Hello all. I'm attempting to restore a couple of files using amrecover, but I
am confused as to what the proper behavior of amrecover should be. I
successfully get the files that I've added to the extraction list. But, when
it finishes untarring the last file, it just sits there forever.
On Fri, Jan 03, 2003 at 10:44:50PM -0500, John R. Jackson wrote:
* amrecover does not rewind the tape for you. I'm sure that there
is a good reason for this, but I don't know what it is. You have
to rewind the tape first, then run the command.
The normal mode for amrecover (actually,
39 matches
Mail list logo
