Hi again,
I would do two things first:
1.) enable the termination on the adapter in the adapter-setup.
Sometimes automatic-termination mode does not do the expected.
2.) set the speed for all devices on this scsi-bus to 5MB/s,
and disable the ultra-mode-operation on this scsi-bus.
I remember readi
Someone I work with accidentally amrmtaped the wrong tape (number 10),
but immediately flushed what was in the holding disk to the correct tape
(number 15). Therefore I have the following situation:
* I have all of tape 10's data (but it may or may not have a header)
* I have the curinfo records
Hi,
Got a new problem...
Backing up a FreeBSD 4.0 box, the client does not report any problems
during amcheck, but after the nightly run, the summary reports:
real.cho.c da0s1a lev 0 FAILED [could not connect to
real.cho.cstone.net]
It seems to connect fine during the check process? Here's the
On Tue, 21 Nov 2000, David McCall wrote:
> here's my stats from last night full run:
>
> Total Full Daily
>
> Estimate Time (hrs:min)0:04
> Run Time (hrs:min)14:27
> Dump Time (hrs:min)
here's my stats from last night full run:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min)14:27
Dump Time (hrs:min) 72:11 72:11 0:00
Output Size (meg) 50257
Hi,
Here is my understanding of the compatibility issues.
With the Quantum range of DLT's (2000, 2000XT, 4000, 7000 & 8000) there is
complete read & write backward compatibility.
Any drive will read its native capacity and any lower capacity without
problem.
On write if you are appending to
On 21 Nov 2000, John Goerzen wrote:
> <[EMAIL PROTECTED]> writes:
> > > Probably. That's why there's the holding disk, right? I'm backing up
> > > some machines over VPN Internet connection anyway, so this may
> > > actually speed that up. The local server is an Alpha :-)
> >
> > okay then...
> >Indeed, the mail report suggests that the next dump should go
> onto the first
> >tape. I had assumed that it would suffice to insert the first
> tape and the
> >new dump would simply overwrite the dump from the first cycle. No? ...
>
> That's what should happen.
Thanks for clarifying this. I
On Tue, Nov 21, 2000 at 01:41:05PM -0500, John R. Jackson wrote:
> >-rwsr-x---1 root backup 78558 Nov 3 13:21 killpgrp*
>
> Ummm, your xinetd line says to run things as group "disk", and user
> "backup". That combination does not have access to execute killpgrp.
>
> I assume you
David Wolfskill wrote:
>
> >Date: Mon, 20 Nov 2000 17:52:54 -0500
> >From: Michael Lea <[EMAIL PROTECTED]>
>
> >Sorry if this is covered elsewhere, but I couldn't find anything about it.
> >My understanding of the way that amanda works is that it streams the
> >dump file to the holding disk on t
>No NFS involved. Permissions on killprgrp:
>
>-rwsr-x---1 root backup 78558 Nov 3 13:21 killpgrp*
Ummm, your xinetd line says to run things as group "disk", and user
"backup". That combination does not have access to execute killpgrp.
I assume you said --with-group=backup since i
On Tue, Nov 21, 2000 at 12:59:28PM -0500, John R. Jackson wrote:
> >...
> > user= backup
> > group = disk
> >...
> >The amdump email states:
>
> What does amcheck have to say?
>
amcheck reports no problems.
> >And /tmp/amanda/sendsize.de
>When I'm backing a filesytem that's part of SUN cluster ENV i 'm getting the
>message:
>filessytem offline and it's not getting backed up.
What does amcheck say? And please post all of the output, not a summary.
What's in /tmp/amanda/sendsize*debug and sendbackup*debug on the client?
>Ruksana
>Hows this for funny, the only person in the whole company who can't get his
>workstation to backup is the backup operator! :-)
Don't you just hate that? :-) :-)
>...
> user= backup
> group = disk
>...
>The amdump email states:
What does
> Are you running 24/7? If so, how do you deal with the issue
> of changes in the db during file transfer? ...
Yes, we're running 24/7. And it's my understand the technique the script
we use employs deals with that.
>> The scripts we use are at:
>>
>> ftp://gandalf.cc.purdue.ed
>... It's very much like the tcl script John Jackson wrote ...
Ummm, I didn't write that. A co-worker, Todd Helfter, did (as it says
in the inline comments).
>The script essentially backs up all of the tablespaces, control
>files, and config files to a spare partition set up specifically
>for
Hows this for funny, the only person in the whole company who can't get his
workstation to backup is the backup operator! :-)
Basically I installed Mandrake 7.2 a few weeks back, and got it nicely tweaked,
then went to setup the amanda clinet. We're using 2.4.2. Mandrake 7.2 uses
xinetd. I've co
One other thing to check. Make sure any (e.g. DIP) switches that
control drive options didn't accidentally get flipped or moved to
half-on/half-off. They may have been wrong for a while and just now
took effect because of the reset.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECT
Title: RE: Problem with Amcheck
Strange that a hardware problem would occur only after
rebooting the server (or perhaps coincidence *shrugs*). This was actually a new
tape drive that was sent to us from Exabyte after we shipped back a damaged one
few months back.
Everything seems to look ok
>Looks like a hardware problem. ...
That would be my conclusion as well, or else the kernel confused about
something.
>Is there anything else I can check before
>coming to this conclusion?
The usual suspects and techniques:
* cables seated properly.
* proper termination (not too much, no
unsubscribe [EMAIL PROTECTED]
Veasey Manley
System Administrator
Search123.com
818.597.4799
Hi,
no, that won't be an issu, it is completly normal for linux.
it always reports scsi-Tapes as st[0-x].
how long is the external cable connected?
The cable is only a few feet in length.
Title: RE: Problem with Amcheck
Check to make sure the devices are set up correctly. For example, here's what I get from ls -l /dev/*st0:
crw-rw 2 root disk 9, 128 May 5 1998 nst0
crw-rw 1 root disk 9, 0 May 5 1998 st0
If that looks right, It's time
>I can now rest in peace knowing that my backups will not be destroyed
>by one errant bit :-)
As long as you're using GNU tar, which I realize you are. But just to
make sure everyone else understands, system dump programs may or may
not be so amused with a missing chunk of data. I've seen both
no button luxuries on the ADIC 40/80 unit
just an unload button.
"John R. Jackson" wrote:
> >I seem to remember there being a way to get tapes setup for 20/40 to be
> >written at 35/70, but I can't remember if that was using a specific
> >software package or just using the certain buttons on the
Title: RE: Problem with Amcheck
/dev/st0 is the first SCSI tape. /dev/nst0 is the same device, without the 'feature' of automatic rewind after each close(). AMANDA writes multiple images to one tape, so automatic rewinds would be problematic. Having two logical device names pointing to the sam
I'm putting the finishing touches this week on a perl script
that handles Oracle database hot backups (to keep the database
up and running 24/7). It's very much like the tcl script John
Jackson wrote, but uses the Expect perl module to interact with
the database.
The script essentially backs up
Looks like a hardware problem. Is there anything else I can check before
coming to this conclusion?
[bin@mail sbin]$ mt -f /dev/nst0 rewind
/dev/nst0: Input/output error
-Original Message-
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 21, 2000 1:13 PM
To: Sh
Hi,
no, that won't be an issu, it is completly normal for linux.
it always reports scsi-Tapes as st[0-x].
how long is the external cable connected?
"Shane T. Ferguson" schrieb:
[]
> I also have my symbolic link between /dev/tape and /dev/nst0 -- notice above
> it detects scsi tape st0 (not n
>Indeed, the mail report suggests that the next dump should go onto the first
>tape. I had assumed that it would suffice to insert the first tape and the
>new dump would simply overwrite the dump from the first cycle. No? ...
That's what should happen.
>In fact,
>when I try to do this, my Sun DL
>... notice above
>it detects scsi tape st0 (not nst0) -- would this be an issue?
No.
What happens if you stick an Amanda tape in the drive and do this:
$ mt -f /dev/nst0 rewind
$ dd if=/dev/nst0 bs=32k
You should see the (ASCII) Amanda label.
>Shane
John R. Jackson, Technical Software S
>At least planner, dumper and amcheck must be setuid-root.
Here's the complete list:
-rwsr-x--- 1 root backup244676 Nov 3 14:41 libexec/calcsize
-rwsr-x--- 1 root backup803996 Nov 3 15:17 libexec/dumper
-rwsr-x--- 1 root backup233356 Nov 3 14:41 libexec/kil
>I seem to remember there being a way to get tapes setup for 20/40 to be
>written at 35/70, but I can't remember if that was using a specific
>software package or just using the certain buttons on the drive.
I recently converted a bunch of tapes from DLT4000 (20/40) to DLT7000
(35/50). The steps
I did a full shutdown of the server and the devices as you mentioned --
still having the same problem. However, I do have an Exabyte 8700 tape drive
and this is what is detected:
Nov 21 12:29:02 mail kernel: Vendor: EXABYTE Model: EXB-8505
Rev: 0051
Nov 21 12:29:02 mail kernel: Type: Sequ
On Nov 21, 2000, "Blohm, Matthias (init)" <[EMAIL PROTECTED]> wrote:
> fileserver1 /home lev 0 FAILED [fileserver1: [host
> fileserver1.domain.com: port 2107 not secure]
> Did anybody the reason.
At least planner, dumper and amcheck must be setuid-root.
--
Alexandre Oliva Enjoy Guarana',
Hi,
I have successfully dumped to 5 tapes in 5 days. The cycle is now complete.
Indeed, the mail report suggests that the next dump should go onto the first
tape. I had assumed that it would suffice to insert the first tape and the
new dump would simply overwrite the dump from the first cycle. No
On Tue, 21 Nov 2000, David McCall wrote:
> I've receintly upgraded from the 20/40 to the 40/80.
> backward read compatability is fine, however, you can NOT relabel the
> 80 gig tapes that were previously labeled in 40 gig mode. The tapes need
> to be bulk erased 1st. I tried bulk erasing with t
On Tue, 21 Nov 2000, Blohm, Matthias (init) wrote:
> Thanks for helping,
> but the other Problem I have is that following :
>
> --
> FAILURE AND STRANGE DUMP SUMMARY:
> fileserer1 /usr/local/cvsroot lev 0 FAILED [files
Title: RE: Problem with Amcheck
The part of this that concerns me is the status bits BOT (beginning of tape) and DR_OPEN (door open) being on at the same time. On my 8505, DR_OPEN means that there is no tape in the drive, and if there is no tape, how can it be at the beginning?
I would sugge
Thanks for
helping,
but the other
Problem I have is that following :
--
FAILURE AND STRANGE DUMP SUMMARY:
fileserer1 /usr/local/cvsroot lev 0 FAILED
[fileserver1: [host fileserver1.domain.com: port 2107 not secure]
On Tue, 21 Nov 2000, Shane T. Ferguson wrote:
> [bin@mail sbin]$ ./amcheck seascape
> Amanda Tape Server Host Check
> -
> /var/amanda/spool: 6608043 KB disk space available, that's plenty.
> insert tape into slot 11 and press return
>
> It appears not to detect a tape
Hi,
I have a strange problem with my backup system. Everything worked the other
day - until I rebooted the server. The system consists of Redhat 5.2,
amanda-2.4.1p1, Exabyte 8700.
Here is the output of mt status:
[bin@mail sbin]$ mt status
SCSI 2 tape drive:
File number=0, block number=0, parti
Yes, I Did so !
-Ursprüngliche Nachricht-
Von: Alexandre Oliva [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 21. November 2000 15:42
An: Blohm, Matthias (init)
Cc: '[EMAIL PROTECTED]'
Betreff: Re: dumper: FATAL must be run setuid root to communicate
correctly
On Nov 21, 2000, "Blohm,
On Nov 21, 2000, "Blohm, Matthias (init)" <[EMAIL PROTECTED]> wrote:
> Does anybody know why I got that Problems?
Did you `make install' as root?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS
On Tue, 21 Nov 2000, Blohm, Matthias (init) wrote:
> *** A TAPE ERROR OCCURRED: [cannot overwrite active tape TESTTAPE].
> *** PERFORMED ALL DUMPS TO HOLDING DISK.
That's one thing, you're using a tape already used.
> THESE DUMPS WERE TO DISK. Flush them onto a new tape.
> Tonight's dumps shou
Hello,
Does anybody
know why I got that Problems?
And what I am doing
wrong ?
There are no more
Infos in the amdump file.
--
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [cannot overwrite ac
I've receintly upgraded from the 20/40 to the 40/80.
backward read compatability is fine, however, you can NOT relabel the
80 gig tapes that were previously labeled in 40 gig mode. The tapes need
to be bulk erased 1st. I tried bulk erasing with the most powerful
magnetic field we had in the medi
Hi All,
I have setup amanda to backup some file systems in a Linux network (RH
7.0 and 6.1).
The hardware is from HP, A SureStore 818 autoloader with a DLT 8000
drive.
The network has about 180 GB disk which should be backed up. I wonder if
someone can help me with tuning of such a solution.
Al
On Nov 21, 2000, Edwin Peer <[EMAIL PROTECTED]> wrote:
> Is it possible to have amanda do backups of remote workstations using ssh?
It *might* be possible with the new security API in the CVS tree.
> At the moment I'm toying with doing a VPN over ssh using pppd and running
> the backups over th
Hi Guys,
Is it possible to have amanda do backups of remote workstations using ssh?
At the moment I'm toying with doing a VPN over ssh using pppd and running
the backups over that link - but it's messy.
Cheers,
Edwin
Hi,
I can not figure out reason for error conditions during the backup of 5Gb
partition on Linux RedHat7:
==
FAILURE AND STRANGE DUMP SUMMARY:
despinahda7 lev 0 FAILED [data timeout]
despinahda7 lev 0 FAILED [dump to tape failed]
STATISTICS:
Doh!
Sorry. Just found the problem. Copied the config from the old server which
was using the user 'bin'. There is an option on about line 2 of amanda.conf
which tells the system which user to run the dump as. It was set to 'bin'
not 'amanda'!
Sorry!
Chris Mills
-Original Message-
Fro
I am trying to install amanda on a new server and am trying to have it run
as a user other than bin. I configured amanda --with-user=amanda.
amcheck now works fine, but if I try and run amdump as 'amanda' then it all
goes pear shaped. I get the 'amdump: must be run as user bin' message. If I
chan
53 matches
Mail list logo
