On Monday 03 February 2003 01:02, Du-Wayne Rood wrote:
>Hi
>
>is there anyway to run a quick erase, or should I just lable the
> tape with a new lable, the reason I'm asking is because a normal
> erase takes forever
The labeling operation will effectively erase the tape since it will
write a new
Ok, I've subscribed to the list and have started wading through the info
and archives. Seems I never quite find the info most applicable to what
I seek. I've been using afio but people have recommended to try amanda,
so I'm looking at it.
I've got two cobalt raqs that use a form of Redhat 6.2 a
On Mon, 3 Feb 2003 at 4:48pm, [EMAIL PROTECTED] wrote
> The amanda on our system use 'gnutar' utility.
> The 'amdump' works. But, it doesn't save the absolute path.
> For example, when I ran 'amrestore -p /dev/nst0 cat02 | tar tvf -', I saw
> the following:
> -rw-rw-r-- root/bin 2368 1
The amanda on our system use 'gnutar' utility.
The 'amdump' works. But, it doesn't save the absolute path.
For example, when I ran 'amrestore -p /dev/nst0 cat02 | tar tvf -', I saw
the following:
-rw-rw-r-- root/bin 2368 1998-08-13 11:50:32 ./f52_tub.im8
-rw-rw-r-- root/bin 129
unsubscribe [EMAIL PROTECTED]
Cassie Stevens
Configuration Management
NLX Dyess AFB
(915) 695-0308
email: [EMAIL PROTECTED]
I've just started backing up my 3+TB of RAID space to an Overland Library
Pro system with 1 AIT3 drive using amanda 2.4.3. I initially set runtapes
to 3, but have since cranked that back to 2. I immediately noticed that
amanda wasn't too smart when it came to putting stuff on tape. (Given how
Hello,
I am going to guess on this one. My first thought is that there is now
a gap in your tapelist. amanda wanted tape number 4. there is nothing
there now, which might be why amanda sez "a new tape" in your messages.
I believe the order of your tapelist dictates to amanda what the next
t
> I still get the same message.
>
> I note that tapelist still shows tape Daily04 as 'reuse', even though I
> amrmtape 'd it.
Provided you changed your amanda.conf so that it is now expecting 7 tapes,
you could edit the tapelist file and remove the bad tape from it.
--On Monday, February 03, 2003 13:07:51 -0500 Joshua Baker-LePain <[EMAIL PROTECTED]> wrote:
On Mon, 3 Feb 2003 at 12:26pm, John wrote
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape Daily01].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The nex
On Mon, Feb 03, 2003 at 01:07:51PM -0500, Joshua Baker-LePain wrote:
> On Mon, 3 Feb 2003 at 12:26pm, John wrote
>
> > *** A TAPE ERROR OCCURRED: [cannot overwrite active tape Daily01].
> > Some dumps may have been left in the holding disk.
> > Run amflush to flush them to tape.
> > The next tape
On Mon, 3 Feb 2003 at 12:26pm, John wrote
> *** A TAPE ERROR OCCURRED: [cannot overwrite active tape Daily01].
> Some dumps may have been left in the holding disk.
> Run amflush to flush them to tape.
> The next tape Amanda expects to use is: a new tape.
>
> Is there a way to make it use the exis
Long story short.
Ran tapetype on a 230m tape. Then got a box of 170m tapes without
noticing.
Tape 4, a 170M tape was snapped at it's end.
I amrmtape tape4, and now amanda insists it needs a new tape to flush
the stored backups to.
I'm now gettings:
*** A TAPE ERROR OCCURRED: [cannot overwri
Angie,
The last item on each line of the disklist specifies the dump type to
use for the filesystem. These dump types are defined in amanda.conf.
Have a look at the comments in amanda.conf to see all the options. The
format for the disklist is:
So, to backup the /home/users filesystem
From my understanding, you should be able to do something like the
following:
fs3 /vol0 always-full
fs3 /vol1 always-full
The dump type 'always-full' is defined in your amanda.conf already:
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compre
On 3 Feb 2003 at 7:47am, Jeff Borders wrote
> # description: Part of the Amanda server package
> service amandaidx
^
> amandaidxd: 192.168.2.3
^
> xinetd: libwrap refused connection to amandaidx from 192.168.2.3
^
Se
Angie,
Can you post your disklist on the list? Which of the dumptypes are you
using? Depending on the dumptype, you may not have amanda to do a full
backup of each filesystem every night. If a file has not changed, it
*may* not be backed up (depends on the dumptype set in the disklist) as
a
Angie
normally amanda will balance the backups so that it will only do full
backup every now and again with incrementals in between.
How are you attempting to restore the file? If you use use amrestore
from the client in question it will tell you which tape it needs for a
specific tape.
--
M
Hello,
amcheck reads ok. I've got the standard xinetd.d setup that I've read
in the docs:
# default: off
#
# description: Part of the Amanda server package
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
Dear Sir/Madam,
I have a problem with the amanda backup.
All the files are not seems fully backup to the backup tape every time.
For example, file A and file B are stored in the same folder C. However,
there was only file A has been found in backup tape which under folder C. I
have no idea why
19 matches
Mail list logo
