>Hi! This is probably a really easily answered question, but I'm not having
>any luck finding it (probably going blind)...
The answer is easy, you're just not going to like it :-).
>I've got the 2.4.4b1 client set up on a cygwin machine. The backup is going
>well, but in order to create a DLE,
>It didn't ask for change tape, but no progress.
>...
>In addition, I got the similar problem yesterday:
>I ran 'amdump'. The system asked for change tape after while.
>I inserted a tape and pressed return, but the process was hung.
>There was no tape device activity.
>I had to interrupted the proc
>I just added to exclude list for that entry several sub directories and
>now it looks like:
>
>/home/max> cat .amanda.excludes
>/home/max/o/mprj/PDF
>/home/max/o/mprj/NMT
>...
You might want to get a copy of Amanda 2.4.3 and read docs/EXCLUDE
(which you can do without installing anything). Excl
>>>we wrote our own request() function.
>>
>>
>> And what's in your version of the function? My guess is it is not
>> waiting long enough for the tape to go ready.
>>
>> What's in /tmp/amanda/changer.debug?
>AFAIK, if I'm invoking amcheck, then this programm starts the
>changer-script and wait
>amcheck-server: could not get changer info: badly formed result from
>changer: "/usr/lib/amanda/chg-zd-mtx: line 151: [: : integer expression
>expected"
You neglected to mention what version of Amanda you're using, but this
was a known problem with chg-zd-mtx a while back. I don't think it was
e
I have two amanda configurations for two different tape changers and
when I run amtape or amlabel on one them the labels are not read from
the tapes, but seemingly taken from memory somewhere.
The changer this isn't working is an HP SureStore 24x6 that used to work
fine until I had to re-do the con
I ran 'amdump' to backup multiple hosts.
The process was hung.
It didn't ask for change tape, but no progress.
Running 'amstatus' always show the following.
...
dumping : 10k 9903410k ( 0.00%) ( 0.00%)
dumped : 23 11569550k 11569424k (100.00%) ( 53.88%)
wait for
On Tuesday 11 February 2003 15:38, John Cunningham wrote:
[...]
>I'm guessing that I'm looking at recompiling the
>kernal - I was really trying to avoid that...
Why? Once one has a valid config, its relatively painless with the
right script. I'll email you mine John.
>How can I tell for sure
John,
I have been away for ~week, and I am just getting back to this problem.
Thanks for the response, however, this is exactly what I have seen already.
I need some more details on the procedure/process.
Here are some details on what I have done, and the behaviour that
On Tue, 2003-02-11 at 14:41, Pete Poggione wrote:
> I get an error trying to access /dev/sg2 as the Amanda user so I had to
> set /sbin/mtx to run as suid root. That seemed to take care of that
> issue (if anyone has a better idea let me know)
Pete,
This is not wise-- with suid root, any non-privi
--- Joshua Baker-LePain <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Feb 2003 at 12:36pm, John Cunningham
> wrote
>
> > --- Joshua Baker-LePain <[EMAIL PROTECTED]> wrote:
>
> > > Do you know exactly how this changer is set up?
> > > Does the changer have a
> > > separate SCSI ID from the tape drive
Thanks - I've recompiled before, but this is a
production machine with 131 days uptime (it's almost a
pride thing to not reboot) - I will plan on doing this
tonight (really, really late).
-John
--- Joshua Baker-LePain <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Feb 2003 at 12:38pm, John Cunningham
>
On Tue, 11 Feb 2003 at 12:38pm, John Cunningham wrote
> I'm guessing that I'm looking at recompiling the
> kernal - I was really trying to avoid that...
>
> How can I tell for sure?
If your changer is on the same ID, different LUN from your tape drive,
then you'll need to recompile the kernel.
On Tue, 11 Feb 2003 at 12:36pm, John Cunningham wrote
> --- Joshua Baker-LePain <[EMAIL PROTECTED]> wrote:
> > Do you know exactly how this changer is set up?
> > Does the changer have a
> > separate SCSI ID from the tape drive, or is it on a
> > different LUN? Are
> > you having any terminat
On Tuesday 11 February 2003 13:48, John Cunningham wrote:
>I know it's been a while and I bet you weren't
>expecting to hear back from me yet. Unfortunately I
> had to put my time elsewhere - but I've been keeping
> up with the group and suggestions to my problem.
>
>From what I can tell of my /va
--- Joshua Baker-LePain <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Feb 2003 at 10:48am, John Cunningham
> wrote
>
> > >From what I can tell of my /var/log/dmesg file my
>
> > autoloader is on /dev/st0 - which is odd because
> mtx
> > doesn't seem to agree.
>
> mtx needs to talk to an sg device,
Sorry about the double message - sent prematurely
before...
--- Joshua Baker-LePain <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Feb 2003 at 10:48am, John Cunningham
> wrote
>
> > >From what I can tell of my /var/log/dmesg file my
>
> > autoloader is on /dev/st0 - which is odd because
> mtx
> > doe
Jeff Borders <[EMAIL PROTECTED]> wrote:
JB> Most commercial backup softwares have an optional exchange module and
JB> open files module that does this. I was wondering if anyone had worked
JB> through this with amanda. I don't see anything on google or the FAQ
JB> about this.
MS Exchange is rath
If this problem is addressed somewhere else in the mail list archives I
apologize in advance. I have not been able to find anything that helps
me solve this problem after 3 days of searching and fiddling...
THE HISTORY:
I have had Amanda configured and running on this server with a single
interna
On Tue, 11 Feb 2003 at 10:48am, John Cunningham wrote
> >From what I can tell of my /var/log/dmesg file my
> autoloader is on /dev/st0 - which is odd because mtx
> doesn't seem to agree.
mtx needs to talk to an sg device, not an st device.
> when I do the same with sg0: (mtx -f /dev/sg0 inqu
I know it's been a while and I bet you weren't
expecting to hear back from me yet. Unfortunately I
had to put my time elsewhere - but I've been keeping
up with the group and suggestions to my problem.
>From what I can tell of my /var/log/dmesg file my
autoloader is on /dev/st0 - which is odd
Hello,
I use amanda Amanda-2.4.2 on RH 6.2
Works fine a year.
Now I have one home directory about 48Gb (/home/max) and I have to split
it to separate entries in disklist file. My idea was very simple.
I just added to exclude list for that entry several sub directories and
now it looks like:
/ho
On Tue, Feb 11, 2003 at 05:31:04PM +0100, Toralf Lund wrote:
> I'm getting error message
>
> No index records for disk for specified date
>
> when trying to recover a certain DLE using amrecover (version 2.4.3.) The
> full output from the session + some of the debug messages are included
> be
I'm getting error message
No index records for disk for specified date
when trying to recover a certain DLE using amrecover (version 2.4.3.) The
full output from the session + some of the debug messages are included
below. The index looks good to me; I have
# ls -lR /dumps/amanda/ks/index/m
Brad,
Stupid problems I've run into.
Assuming you have both DNS and NIS/NIS+ services enabled.
/etc/nsswitch.conf (Solaris, don't know if redhat had this) wasn't
using "files" just "NIS". Check the equiv in your OS and see, also
make sure that the server information for both services are providi
On Tue, 11 Feb 2003, Joshua Baker-LePain wrote:
> On Mon, 10 Feb 2003 at 5:06pm, justin m. clayton wrote
>
> > I've been receiving this error on some, but not always all, of my hosts
> > during amcheck. What could be causing this issue? Which logs are most
> > likely to be housing the magic info
On 11 Feb 2003 at 8:47am, Brad wrote
> Thanks to all for the help. Still no luck. I'm seeing the below libwrap
> errors in the logs. hosts.allow has entries for 127.0.0.1 and the
> localhost's fqdn, but still no go. Here is my hosts.allow file:
>
> ALL: 127.0.0.1
> ALL: 128.173.141.0/255.255.255.
On Mon, 10 Feb 2003 at 6:56pm, [EMAIL PROTECTED] wrote
> After ran 'amdump' (gnutar is the utility), I saw hosts got different lavel
> of
> backup. I don't know why.
> How to control backup level? ie, all hosts backup level 0.
> The following is the summary of 'amdump':
This is normal. Amanda tr
Yeah, I've restarted it several times. I've reordered the hosts.allow
file too just to see if that would make a difference, but it doesn't.
Thanks for the tip though.
On Tue, 2003-02-11 at 09:41, Joshua Baker-LePain wrote:
> On 11 Feb 2003 at 8:47am, Brad wrote
>
> > Thanks to all for the help. S
On Mon, 10 Feb 2003 at 5:06pm, justin m. clayton wrote
> I've been receiving this error on some, but not always all, of my hosts
> during amcheck. What could be causing this issue? Which logs are most
> likely to be housing the magic info I need to solve this?
If there's already an amandad runnin
On Mon, 10 Feb 2003 at 6:24pm, Mark Stosberg wrote
> At my Amanda installation, we have a server and several clients all
> running 2.4.2p2. I would like to upgrade at least the server to take
> advantage of some of the features in 2.4.3. I have some questions for
> veterans of this upgrade:
>
>
Thanks to all for the help. Still no luck. I'm seeing the below libwrap
errors in the logs. hosts.allow has entries for 127.0.0.1 and the
localhost's fqdn, but still no go. Here is my hosts.allow file:
ALL: 127.0.0.1
ALL: 128.173.141.0/255.255.255.0
ALL: 128.173.203.0/255.255.255.0
ALL: 128.173.20
Thanks to Jon, Gene, Chris, Joshua, Jay and Liam for responding last week. I did
get
the changer set up, turns out I just had to uncomment two lines in sgen.conf and
reboot.
Well it would have been if the changer's default SCSI id was not the same as the
CD
drive in solaris but once I got tha
On Tuesday 11 February 2003 07:53, Rainer Hofmann wrote:
> Is reiserfs the problem? The amanda version installed on the backup server
> is amanda-2.4.1p1-29. On a different machine I'm running ext3 which is
> backed up properly on the same backup server.
What's your backup method - dump or tar ?
Hi,
i guess you are trying to use dump for these filesystems, aren't you?
this will simply not work.
dump is a tool exclusively designed for ext2,
you are very lucky if it works for ext3.
switch over to use tar, and all should be ok.
Christoph
Rainer Hofmann schrieb:
Hi,
I've setup a new workstat
Hi,
First guess: double check your path statements in cron.
If programs/scripts work from commandline but not from cron most times
a needed part of the $PATH env-variable is missing, so a part of your
script/command can't be executed. And this is not necesarryly reported
back to you.
Christoph
Mic
Hi,
I've setup a new workstation to be integrated in daily backup cycles.
amcheck doesn't show any problems. Access is granted. But when it comes to
amdump the following error message turns up in report file:
FAILURE AND STRANGE DUMP SUMMARY:
pc034 /usr lev 0 FAILED [disk /usr offline on p
Hi,
John R. Jackson schrieb:
we wrote our own request() function.
And what's in your version of the function? My guess is it is not
waiting long enough for the tape to go ready.
What's in /tmp/amanda/changer.debug?
AFAIK, if I'm invoking amcheck, then this programm starts the
changer-scrip
38 matches
Mail list logo
