3345 Apr 3 10:45 /usr/local/sbin/amcheck
>>
>> and let us know how it goes.
>
>I've completely rebuilt and reinstalled. Because we also had trouble
> with that data link, I nuked the slots and link as well, and re-ran
> mkvtapes as amanda, only to see
>
>mode of
so had trouble with
that data link, I nuked the slots and link as well, and re-ran mkvtapes as
amanda, only to see
mode of `/Backup/amandatapes/Dailys/slot1' changed to 0750 (rwxr-x---)
./mkvtapes: line 24: amlabel: command not found
etc.
So, two possibilities. Am I running this from the wrong
02:04:13PM -0400, James Jacocks wrote:
We are currently experiencing the below issue using
amlabel. I have tried with and without a tape loaded, with and
without a slot specified etc.. All chg-zd-mtx "tests" described in
the script notes have been confirmed to work..
Indeed, amtape produces the same response. Does this help us to
determine the cause?
Thanks!
On Aug 23, 2005, at 6:49 PM, Jon LaBadie wrote:
On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote:
We are currently experiencing the below issue using
amlabel. I have tried
On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote:
> We are currently experiencing the below issue using
> amlabel. I have tried with and without a tape loaded, with and
> without a slot specified etc.. All chg-zd-mtx "tests" described in
> the
We are currently experiencing the below issue using
amlabel. I have tried with and without a tape loaded, with and
without a slot specified etc.. All chg-zd-mtx "tests" described in
the script notes have been confirmed to work..
amlabel: could not load slot &qu
Thanks Jon. It was device permission. /dev/nst0 was set read only for
group disk.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie
Sent: Tuesday, July 26, 2005 11:32 AM
To: amanda-users@amanda.org
Subject: Re: amlabel: tape is write
On Tue, Jul 26, 2005 at 11:00:48AM -0400, Lei Zhong wrote:
> Hi all,
>
>
>
> When I tried to label a tape using amlabel, I got an error "amlabel:
> tape is write protected". Does anybody know how to fix it? Right now,
> I am running mt -f /dev/nst0 erase. It&
Hi all,
When I tried to label a tape using amlabel, I got an error “amlabel:
tape is write protected”. Does anybody know how to fix it? Right now, I
am running mt –f /dev/nst0 erase. It’s taking forever. Is there
any fast way to commission a tape? Thank you, Lei
Hi again due to the nature of this new sever I have locked everything
down to just a few services and I have disables xinetd .
myserver:/local/sw/amanda/DailySet1 # su amanda -c
"/local/sw/amanda/bckup/sbin/amlabel DailySet1 DailySet101"
rewinding, reading label, not an amanda tape
Hi again
Paul Bijnens I noticed that myself I am going run a make clean and
re-install again .
Cheers
Chuck
On Mon, 2005-04-18 at 16:41 +0200, Paul Bijnens wrote:
> Chuck Amadi wrote:
> > Hi cheers for your reply.
> >
> > I honestly set this up as ./configure as amanada make as amanda and ma
Chuck Amadi wrote:
Hi cheers for your reply.
I honestly set this up as ./configure as amanada make as amanda and make
install as Root.
I have kept to the install and I have read the doc's.
OK, I believe you, but when everyone else in the world
does a "make install", then the amcheck binary ends
up
Chuck Amadi wrote:
I have nuked the default binary (rpm within SuSE Yast2 and installaed
and run source configuration amanda 2.4.4.
...
-rwxr-x--- 1 amanda disk 86322 Apr 18 14:25 amcheck
The above line indicate you did not install correctly.
You should "make install" as root.
And generally, you
/amanda # su amanda -c
"/local/sw/amanda/bckup/sbin/amlabel DailySet1 DailySet101"
rewinding
amlabel: tape_rewind: tape open: /dev/nst0: Permission denied
I have a DDS-4 tape which I am trying to label.
myserver:/local/sw/amanda/bckup/sbin # ls -al
total 677
drwxr-xr-x 2 amanda disk616
ÐÐÑÐÑÐ ÐÐÑ wrote:
amlabel: label svn16 doesn't match labelstr "^svn[1-25][1-25]*$"
in amanda.conf labelstr has a following appearance:
labelstr "^svn[1-25][1-25]*$"
Learn something more about regular expressions again.
Between square brackets is a set of characters, an
I again have a silly question:) At attempt to set a label to tapes, amlabel
gives out a following mistake:
amlabel: label svn16 doesn't match labelstr "^svn[1-25][1-25]*$"
amlabel: label svn17 doesn't match labelstr "^svn[1-25][1-25]*$"
amlabel: label svn18 doesn&
On Tue, Apr 12, 2005 at 01:19:52PM +1000, Jesus Salvo Jr. wrote:
> On Tuesday 12 April 2005 13:07, Jesus Salvo Jr. wrote:
> > I think I know what the problem maybe, though I do not know the solution:
> >
> > The test that I did with chg-zd-mtx works only if I run it in
> > the /usr/local/etc/amanda
On Tuesday 12 April 2005 13:07, Jesus Salvo Jr. wrote:
> I think I know what the problem maybe, though I do not know the solution:
>
> The test that I did with chg-zd-mtx works only if I run it in
> the /usr/local/etc/amanda/Daily directory.
>
> If I do it anywhere else, I get the exact same error
On Tuesday 12 April 2005 12:01, Jesus Salvo Jr. wrote:
> bash-2.05$ amtape Daily reset
> amtape: could not reset changer: changerfile must be specified in
> amanda.conf
>
> The debug output in /tmp/amanda says:
>
> bash-2.05$ cat amtape.20050412112910.debug
> amtape: debug 1 pid 1077 ruid 60008 eu
On Tuesday 12 April 2005 12:01, Jesus Salvo Jr. wrote:
> In fact, the chg-zd-mtx script will not work if the changerfile entry in
> amanda.conf is not valid / incorrect. In chg-zd-mtx script:
>
> changerfile=`amgetconf$SUF changerfile 2>/dev/null | grep -v BUGGY`
> if [ -z "$changerfile" ]; then
>
On Tuesday 12 April 2005 00:29, Steve Yun wrote:
> Did you read the comments in 'chg-zd-mtx'?
>
> Make sure you can successfully complete the basic test procedures written
> in 'chg-zd-mtx'
>
As stated in an earlier post ... yes ... except for amtape, which was
complaining of the same problem.
I knew I should have posted more information ... anyway ...
On Monday 11 April 2005 23:57, Jon LaBadie wrote:
>
> You indicate that chg-zd-mtx is "working". Just to be certain:
>
> Have you exercised the changer script by invoking it directly with all
> the possible commands including "current" (
.org
Subject: Newbie: amlabel: could not load slot "current": changerfile
must be specified in amanda.conf
Hi,
I have a StorEdge L7 on an E220R running Solaris9.
I have configured Solaris9 with sgen and mtx and chg-zd-mtx
mtx is working
chg-zd-mtx is also working
The relevant entries in aman
petype DLT8000
>
> The conf file for chg-zd-mtx is:
> /usr/local/etc/amanda/Daily/chg-zd-mtx.conf
>
> Note that the changerfile entry in amanda.conf does not have the ".conf"
> suffix, as per the document in the chg-zd-mtx script ... and it is the only
in amanda.conf does not have the ".conf"
suffix, as per the document in the chg-zd-mtx script ... and it is the only
way to get chg-zd-mtx working.
However, when I do amlabel, I get:
$ amlabel Daily Daily001
amlabel: could not load slot "current": changerfile must be specified in
amanda.conf
Regards,
John
On Monday 21 February 2005 10:01, Paul Bijnens wrote:
>Gene Heskett wrote:
>> Silly Q? Could this be the reason I've blamed amanda for not
>> being able to rewind the tape in a Seagate 4586N changer? And
>> while amanda couldn't rewind it, mt could?
>
>I don't think so. The file contains paramet
Gene Heskett wrote:
Silly Q? Could this be the reason I've blamed amanda for not being
able to rewind the tape in a Seagate 4586N changer? And while amanda
couldn't rewind it, mt could?
I don't think so. The file contains parameters to set blocksize
and hw-compression if different modes. But
Jon LaBadie wrote:
On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote:
Late reply, as this mail (and some other apparently) got stuck
in the mailserver...
And check the file st.init, where the letters get their meaning.
Paul, I'm unfamiliar with the file st.init.
Nor do I find one on my s
On Sunday 20 February 2005 19:07, Spicer, Kevin (MBLEA it) wrote:
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett
>
>>Paul: That file (st.init/st.conf) doesn't exist on a redhat
>> flavored linux install. Nor on a debian sarge based install of
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett
>Paul: That file (st.init/st.conf) doesn't exist on a redhat flavored
>linux install. Nor on a debian sarge based install of BDI-4.08, I
>just checked that one too
If my Tao box is anything to
On Tuesday 08 February 2005 11:24, Jon LaBadie wrote:
>On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote:
>> Jon LaBadie wrote:
>> >With the ultrium it is less important about considering HW or SW
>> >compression. But be aware that on Solaris whether HW compression
>> >is turned on or n
On Tue, Feb 08, 2005 at 05:53:43PM +0100, Paul Bijnens wrote:
> Jon LaBadie wrote:
>
> >On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote:
> >
> >>All that said, when using an LTO drive, you may have hardware
> >>compression enabled anyway, because the hw compr algorithm in those
> >>d
Jon LaBadie wrote:
On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote:
All that said, when using an LTO drive, you may have hardware
compression enabled anyway, because the hw compr algorithm in those
drives does not expand uncompressable data.
Maybe the amtapetype message should be rev
On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote:
>
> All that said, when using an LTO drive, you may have hardware
> compression enabled anyway, because the hw compr algorithm in those
> drives does not expand uncompressable data.
Maybe the amtapetype message should be revised to so
On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote:
> Jon LaBadie wrote:
> >
> >With the ultrium it is less important about considering HW or SW
> >compression. But be aware that on Solaris whether HW compression
> >is turned on or not is determined by the device you choose. You
> >will
On Tue, Feb 08, 2005 at 09:47:17AM -0500, Gil Naveh wrote:
> The issue I had was that the first time I run amtapetype the result was a
> little off.
I would not consider them different at all.
capacity, differed by 0.31 percent
filemark, differed by 3.41 percent (and only 0.00045%
Gil Naveh wrote:
The issue I had was that the first time I run amtapetype the result was a
little off.
Which was painful because it takes a few hours to run it.
yet, it might not be a bug - the reason I put it in the subject was that
people would notice it.
No, it's not a bug. That's real life wit
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 08, 2005 9:27 AM
To: Gil Naveh
Cc: amanda-users@amanda.org
Subject: Re: AMLABEL - might be a bug in amtapetype
Gil Naveh wrote:
> Hello and thanks,
>
> So it turn out that my suspicious were correct.
Which suspicions?
> Aft
Hello and thanks,
So it turn out that my suspicious were correct.
After rerunning amtapetype twice on our Solaris 9 server I got the
configuration for Ultrium2-LTO slightly different and with the new results
amlabel worked fine :)
In the first run I got the following result:
define
And assuming that "c" does enable compression on your solaris
system the difference (at least on my drives) between "h" and "u"
is also the HW compression, though both are highest density
(on devices where its offered).
On Mon, Feb 07, 2005 at 10:48:27PM -0500, Jon LaBadie wrote:
> On Mon, Feb 0
Jon LaBadie wrote:
With the ultrium it is less important about considering HW or SW
compression. But be aware that on Solaris whether HW compression
is turned on or not is determined by the device you choose. You
will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines
the properties of t
On Mon, Feb 07, 2005 at 10:06:09PM -0500, Gene Heskett wrote:
> On Monday 07 February 2005 18:31, Paul Bijnens wrote:
> >Gil Naveh wrote:
> >> Gene - thanks for trying to help,
> >>
> >> Currently the only reason that I can think of is that Amanda has
> >> not read correctly our tape drive so I am
On Monday 07 February 2005 18:31, Paul Bijnens wrote:
>Gil Naveh wrote:
>> Gene - thanks for trying to help,
>>
>> Currently the only reason that I can think of is that Amanda has
>> not read correctly our tape drive so I am re-running
>> #amtapetype -f /dev/rmt/0n
>
>Add an estimate value! And it
Gil Naveh wrote:
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has not read
correctly our tape drive so I am re-running
#amtapetype -f /dev/rmt/0n
Add an estimate value! And it takes about 5 hours only. Without
an estimate it takes a week or so. L
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has not read
correctly our tape drive so I am re-running
#amtapetype -f /dev/rmt/0n
By tomorrow I'll see what the results are and hopefully it should work...
Any thoughts why amlabel is not workin
Naveh
Subject: Re: AMLABEL
On Monday 07 February 2005 10:56, Gil Naveh wrote:
>Hello,
>
>We have a new tape drive but I am unsuccessfully running amlabel.
>Some background:
>I was successfully running amlabel on HARD-DISK.
>I modified amanda.conf file to accommodate the new tape dri
On Monday 07 February 2005 10:56, Gil Naveh wrote:
>Hello,
>
>We have a new tape drive but I am unsuccessfully running amlabel.
>Some background:
>I was successfully running amlabel on HARD-DISK.
>I modified amanda.conf file to accommodate the new tape drive
>specification
Hello,
We have a new tape drive but I am unsuccessfully running amlabel.
Some background:
I was successfully running amlabel on HARD-DISK.
I modified amanda.conf file to accommodate the new tape drive
specifications:
I added the new tape drive spec - which I got through running amtapetype
On Sun, 2005-01-23 at 11:11 +0100, Paul Bijnens wrote:
> Erik P. Olsen wrote:
> >>>On Sat, Jan 22, 2005 at 09:58:42PM +0100, Erik P. Olsen wrote:
> >>>>[EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
> >>>>rewinding, rea
Erik P. Olsen wrote:
On Sat, Jan 22, 2005 at 09:58:42PM +0100, Erik P. Olsen wrote:
[EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
rewinding, reading label full01
rewinding, writing label full01, checking labelamlabel: couldn't
write tapelist: Permission denied
>
On Sunday 23 January 2005 01:06, Erik P. Olsen wrote:
I put this back on the list.
>On Sat, 2005-01-22 at 23:20 -0500, Gene Heskett wrote:
>> This is a permissions problem I believe, possibly brought on by a
>> miss-build of amanda. The tapelist does NOT need any extended
>> permissions to work,
ing amanda for production I relabeled the tapes
> >> (after having duly removed them from the repository by amrmtape)
> >> and changed the directory into which the tapelist would go. Then
> >> amanda wouldn't label the tapes. The command used was:
> >>
On Sun, 2005-01-23 at 00:20 +0100, Erik P. Olsen wrote:
> On Sat, 2005-01-22 at 22:31 +0100, Paul Bijnens wrote:
> > Erik P. Olsen wrote:
> >
> > > [EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
> > > rewinding, reading label full01
>
removed them from the repository by amrmtape)
>> and changed the directory into which the tapelist would go. Then
>> amanda wouldn't label the tapes. The command used was:
>>
>> [EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
>> rewinding,
ing amanda for production I relabeled
>> > the tapes (after having duly removed them from the repository by
>> > amrmtape) and changed the directory into which the tapelist
>> > would go. Then amanda wouldn't label the tapes. The command used
>> > was:
>
On Sat, 2005-01-22 at 22:31 +0100, Paul Bijnens wrote:
> Erik P. Olsen wrote:
>
> > [EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
> > rewinding, reading label full01
> > rewinding, writing label full01, checking labelamlabel: couldn'
eful if
> > > someone would explain to me what the heck it is and how I can satisfy
> > > amlabel?
> > >
> >
> > Here is what I wrote to the list in Oct about
> > someone who seemed to have a similar problem:
> >
> > == I forget the details now, a
uly removed them from the repository by amrmtape) and changed the
> > directory into which the tapelist would go. Then amanda wouldn't label
> > the tapes. The command used was:
> >
> > [EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
> > r
rectory into which the tapelist would go. Then amanda wouldn't label
> the tapes. The command used was:
>
> [EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
> rewinding, reading label full01
> rewinding, writing label full01, checking labelamlabel: co
Erik P. Olsen wrote:
[EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
rewinding, reading label full01
rewinding, writing label full01, checking labelamlabel: couldn't write
tapelist: Permission denied
Well, I thought it was permissions for the file tapelist and chang
to which the tapelist would go. Then
> amanda wouldn't label the tapes. The command used was:
>
>[EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
>rewinding, reading label full01
>rewinding, writing label full01, checking labelamlabel: couldn't
> w
. The command used was:
[EMAIL PROTECTED] full]# su amanda -c "amlabel -f full full01"
rewinding, reading label full01
rewinding, writing label full01, checking labelamlabel: couldn't write
tapelist: Permission denied
Well, I thought it was permissions for the file tapelist and
mt -f /dev/nst0 status also gives me
Input/output error. If I then unload the tape using mtx -f /dev/sg5
unload, I can reload the tape using mtx -f /dev/sg5 load 1 and mt -f
/dev/nst0 status works fine. I attempt to run amlabel again, and the
whole thing starts over again.
-bash-2.05b$ /usr/amanda/
nload the tape using mtx -f /dev/sg5
unload, I can reload the tape using mtx -f /dev/sg5 load 1 and mt -f
/dev/nst0 status works fine. I attempt to run amlabel again, and the
whole thing starts over again.
-bash-2.05b$ /usr/amanda/sbin/amlabel sunday amanda001 slot 1
labeling tape in slot 1 (/dev/
d mt -f
/dev/nst0 status works fine. I attempt to run amlabel again, and the
whole thing starts over again.
-bash-2.05b$ /usr/amanda/sbin/amlabel sunday amanda001 slot 1
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label, reading label: Input/output error
rewinding, writing label amanda00
works fine. I attempt to run amlabel again, and the
whole thing starts over again.
-bash-2.05b$ /usr/amanda/sbin/amlabel sunday amanda001 slot 1
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label, reading label: Input/output error
rewinding, writing label amanda001
amlabel: writing
On Tuesday 11 May 2004 08:20, Matthias Andree wrote:
>Gene Heskett <[EMAIL PROTECTED]> writes:
>> The 2.6.5 etc kernels also have some configuration switches you
>> can build in for the OnStream stuff, I noticed them in passing
>> just a few days ago. This might, in the long run make your life a
>
Gene Heskett <[EMAIL PROTECTED]> writes:
> The 2.6.5 etc kernels also have some configuration switches you can
> build in for the OnStream stuff, I noticed them in passing just a few
> days ago. This might, in the long run make your life a lot more
> enjoyable if you are comfortable building y
On Sunday 09 May 2004 08:01, Matthias Andree wrote:
>Laurent <[EMAIL PROTECTED]> writes:
>> This a MDK 9.2 now (with 2.4 kernel), but i expected to end up
>> with the latest 10.0 with 2.6 kernel.
>> But i think i'll stay with 2.4 if the latest is tricky.
>
>2.6 isn't tricky but has rearranged conf
Laurent <[EMAIL PROTECTED]> writes:
> This a MDK 9.2 now (with 2.4 kernel), but i expected to end up with the
> latest 10.0 with 2.6 kernel.
> But i think i'll stay with 2.4 if the latest is tricky.
2.6 isn't tricky but has rearranged configuration and gives more
explicit hints that some of the
What os etc?
Onstream is notorious for oddball API's, and the later linux 2.6.x
kernels now have a whole menu page in the kernel configuration for
adding in OnStream work arounds.
This a MDK 9.2 now (with 2.4 kernel), but i expected to end up with the
latest 10.0 with 2.6 kernel.
But i think
re you sure /dev/st0 is
> non-rewinding ?" when amlabel it.
>
>What is badly configured ?
>
>I have an Onstream ADR50 tape reader on a Mandrake 9.2 (MDK amanda
> rpm).
What os etc?
Onstream is notorious for oddball API's, and the later linux 2.6.x
kernels now have a w
device.
Frank
> and commented out tpchanger, changerdev, etc.
>
> But i still have "no label found, are you sure /dev/st0 is non-rewinding ?" when
> amlabel it.
>
> What is badly configured ?
>
> I have an Onstream ADR50 tape reader
On Wed, 05 May 2004 17:43:53 +0200
Laurent <[EMAIL PROTECTED]> wrote:
Hello,
> I have a problem with configuring a single tape unit.
>
> As i saw in the FAQ, i put in amanda.conf :
> runtapes 1
> tapedev /dev/st0
> and commented out tpchanger, changerdev, etc.
>
> But i still have "no label fou
On Wed, 5 May 2004 at 5:43pm, Laurent wrote
> As i saw in the FAQ, i put in amanda.conf :
> runtapes 1
> tapedev /dev/st0
> and commented out tpchanger, changerdev, etc.
>
> But i still have "no label found, are you sure /dev/st0 is non-rewinding
> ?" when
I have a problem with configuring a single tape unit.
As i saw in the FAQ, i put in amanda.conf :
runtapes 1
tapedev /dev/st0
and commented out tpchanger, changerdev, etc.
But i still have "no label found, are you sure /dev/st0 is non-rewinding
?" when amlabel it.
What is badly conf
I created a tapelist file under DailySet1 called "tapelist".
When I used amlabel to label the tapes, it created another file called
tapelist.amlabel.
Why is that?
Michael
Pablo Quinta Vidal wrote:
I get this messages when I execute amlabel Diaria Diaria slot 1
YPBINDPROC_DOMAIN: Domain not bound
YPBINDPROC_DOMAIN: Domain not bound
amlabel: label Diaria doesn´t match labelstr "^DailySet1[0-9][0-9]*$"
What must I do??
Give a string that does mat
--On Wednesday, March 10, 2004 17:11:42 +0100 Pablo Quintía Vidal <[EMAIL PROTECTED]>
wrote:
> I get this messages when I execute amlabel Diaria Diaria slot 1
>
> YPBINDPROC_DOMAIN: Domain not bound
>
> YPBINDPROC_DOMAIN: Domain not bound
This mean your NIS is not
Pablo,
Not sure about the NIS errors, but the amlabel issue it that the label
you are instructing to be placed on the tape does not match the string
specified in the amanda.conf labelstr variable.
Run amlabel with a string that matches the labelstr variable or change
the labelstr var in your
I get this messages when I execute amlabel Diaria Diaria slot 1
YPBINDPROC_DOMAIN: Domain not bound
YPBINDPROC_DOMAIN: Domain not bound
amlabel: label Diaria doesn´t match labelstr "^DailySet1[0-9][0-9]*$"
What must I do??
Thanks
Antivirus
Filtros antispam 6
I get this messages when I execute amlabel Diaria Diaria slot 1
YPBINDPROC_DOMAIN: Domain not bound
YPBINDPROC_DOMAIN: Domain not bound
amlabel: label Diaria doesn´t match labelstr "^DailySet1[0-9][0-9]*$"
What must I d
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17
Feb 2004 14:29:51 +0100
> Don't fear the steps you have to take.
> I assume you try to install and setup the most recent AMANDA-release
> 2.4.4p2. This should take most of the standard-issues off your
> shoulders.
>
>
Hi, Erik,
on Dienstag, 17. Februar 2004 at 14:19 you wrote to amanda-users:
EPO> I realize I have a lot to learn. I am new to Linux and before I can move my
EPO> production to Linux I need a reliable backup system.
Very reasonable ;)
EPO> I am all for standards, so I'll see to that my system co
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17
Feb 2004 14:05:11 +0100
> Hi, Erik,
>
> on Dienstag, 17. Februar 2004 at 12:06 you wrote to amanda-users:
>
> >> Do you really want to keep your config-files in /etc/amanda?
> >> The default points to /usr/local/etc/
Hi, Erik,
on Dienstag, 17. Februar 2004 at 12:06 you wrote to amanda-users:
>> Do you really want to keep your config-files in /etc/amanda?
>> The default points to /usr/local/etc/amanda, for example.
>>
EPO> Anything wrong in that? That's where the sample config is located. Of course I
EPO> can
ing tapes for
> EPO> it. I get the error message:
>
> EPO> amlabel: could not load tapelist "/etc/amanda/normal/tapelist"
>
[snip]
> EPO> modified by the user/administrator. The command I issue from the amanda user is:
>
> EPO> amlabel /usr/sbin/amlabel n
ing tapes for
> EPO> it. I get the error message:
>
> EPO> amlabel: could not load tapelist "/etc/amanda/normal/tapelist"
>
> Do you really want to keep your config-files in /etc/amanda?
> The default points to /usr/local/etc/amanda, for example.
>
Anything wr
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17
Feb 2004 11:55:19 +0100
> Hi, Erik,
>
> on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users:
>
> EPO> The command I issue from the amanda user is:
>
> EPO>
Hi, Erik,
on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users:
EPO> The command I issue from the amanda user is:
EPO> amlabel /usr/sbin/amlabel normal normal00
EPO> and it doesn't help to use the force flag. What am I doing wrong?
Oops, I shot too fast.
The syntax
Hi, Erik,
on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users:
EPO> I am installing amanda for the first time and have problems labeling tapes for
EPO> it. I get the error message:
EPO> amlabel: could not load tapelist "/etc/amanda/normal/tapelist"
Do you reall
I am installing amanda for the first time and have problems labeling tapes for
it. I get the error message:
amlabel: could not load tapelist "/etc/amanda/normal/tapelist"
This seems strange since it is the first tape I try to label and therefore
there is no tapelist file and there sho
On Tue, Nov 18, 2003 at 09:46:55PM +1100, Charlie Allom wrote:
> I found this :(
>
> http://amanda.sourceforge.net/fom-serve/cache/273.html
>
> I suppose I can amlabel each tape before I dump to it.
In fact it is required.
--
Jon H. LaBadie [EMAIL PROTECTED
I found this :(
http://amanda.sourceforge.net/fom-serve/cache/273.html
I suppose I can amlabel each tape before I dump to it.
C.
--
[EMAIL PROTECTED] - Melbourne, Australia
http://rubberduck.com/~yeled/
PGP: 0x14AA7941 || finger [EMAIL PROTECTED]
pgp0.pgp
Description: PGP
Hi,
I was wondering if I can operate without Amanda on-tape labels at all.
ie. Can I just use the VolumeTag= entries from my changer?
chg-zd-mtx (looking at the script) seems to want to match them up - so
I'm just asking for confirmation I guess.
adm1:/etc/amanda/daily# su backup -c /usr/sbin/am
Jeremy Aldrich wrote:
Hello,
I am running Red Hat 7.3 w/amanda 2.4.2p2-7 and I am trying to write to
a hard-drive
> [ ... ]
Here is my problem...I keep getting this error when running amlabel:
amlabel: could not load slot "1": file:/home/backup/t1: not a device file
You
c/amanda/test/changer-status
> firstslot 1
> lastslot 3
> slot 1 file:/home/backup/t1
> slot 2 file:/home/backup/t2
> slot 3 file:/home/backup/t3
>
> I then put the amanda user and disk group priveleges on the amanda directories as
> well as the backup directories and hav
ser and disk group priveleges on the
amanda directories as well as the backup directories and have them all
set with 766 permissions.
Here is my problem.......I keep getting this error when running
amlabel:
amlabel: could not load slot "1": file:/home/backup/t1: not a device
On Tue, Sep 30, 2003 at 09:26:35AM +0200, Mats Blomstrand wrote:
> (Thanks Jon LaBadie and Paul Bijnens for your useful suggestion on my last
> question)
>
> When i run amlabel it quits with an seg-fault. Like this:
>
> -bash-2.05b$ amlabel normal normal01 slot 1
>
(Thanks Jon LaBadie and Paul Bijnens for your useful suggestion on my last
question)
When i run amlabel it quits with an seg-fault. Like this:
-bash-2.05b$ amlabel normal normal01 slot 1
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label normal01
101 - 200 of 371 matches
Mail list logo
