Gary Algier <[EMAIL PROTECTED]> writes:
> Multiple tape drives:
> Our old library had only one drive installed. I could have added
> a second one, but I could not see how amanda would use it to advantage.
> Can amanda use a second (or third...) drive?
> Is there any benefit?
> usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
> me,usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
> me,usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
> me,usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
> me,usubscri
usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
me,usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
me,usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
me,usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe
me,usubscribe me,usubs
On Tuesday 22 October 2002 18:04, Chad Morland wrote:
>I am trying to backup a 100G file onto tape. I am wondering if I
> can use amanda for this. Will it span the archive across more
> than one tape? I am using a DLT 7000 drive. If not, what are you
> recommendations?
Yikes! For that, you will h
Hello,
I have been using amanda
on this system for about 2 months and all has been working graet until today. I
ran these commanda today and this was the result.
1)
bash-2.05a$ /usr/sbin/amtape DailySet1
resetamtape: could not reset changer:
could not read result from "/usr/l
i am using amanda-2.4.3b4 , I have recompiled with options
--with-portrange=850,860 --with-udpportrange=850,860
it passes amcheck but when I run amdump I get the following error in
the amdump.log
dumper: stream_client: connect to 209.123.168.230.49833 failed:
Connection timed out
it appears to
Chris Marble wrote:
>
> Jean-Louis Martineau wrote:
> >
> > Amanda-2.4.3b4 on client is broken and will not talk correctly with
> > older server, upgrade your client to 2.4.3
>
> Okay, upgrade done. I'll find out tonight.
Dumps appear to have gone sucessfully. If only I'd asked before spendin
Jerry,
Same problem. I've tried omitting it AND setting it to other
values, and none of it helps.
Thanks,
Max
* Jerry <[EMAIL PROTECTED]> [10/22/02 11:14] wrote:
> Are you sure you have the right blocking factor?
> Try omitting the -b and see if it works.
>
> Jerry
>
> --- Max Kam
I am trying to backup a 100G file onto tape. I am wondering if I can use
amanda for this. Will it span the archive across more than one tape? I
am using a DLT 7000 drive. If not, what are you recommendations?
-CM
Maybe if I can help by formulating a question.
(I am not addressing your other concerns)
Multiple tape drives:
Our old library had only one drive installed. I could have added
a second one, but I could not see how amanda would use it to advantage.
Can amanda use a second (or third.
Greetings, quick easy question: My amanda machine was down for 2 consecutive
backup days. What can I expect when I bring it back online? Will Amanda
automatically compensate? or do I need to manually do the last 2 tapes?
~wab~
Are you sure you have the right blocking factor?
Try omitting the -b and see if it works.
Jerry
--- Max Kamenetsky <[EMAIL PROTECTED]> wrote:
> Hi!
>I'm looking for some help on my restore problem.
> Everytime I
> attempt to restore, I get an error that says "tape
> is not a dump
> tape".
Keep in mind, the reason tapes are still a good way to
back things up:
1) Large capacity. You can get tapes with 150GB per
tape compressed for example. This is handy.
2) Removeable. You can store a few offsite... or if
the backup server goes belly up due to a hardware
failure, you can move the tap
It is time to get a new tape library. We are outgrowing our old one.
(30 DLT IV tapes, 1 drive, 29 hosts & 521Gbytes to be backed up).
I now wonder what features I should look for.
Perhaps someone can comment?
Multiple tape drives:
Our old library had only one drive installed. I could have
On Tuesday 22 October 2002 11:49, Thom Paine wrote:
>I have a plain jane RedHat 7.3 server with amanda running.
>
>For some reason amanda is not sending out the mail report from
> amcheck -m DailySet1. I get the report after the backup has run.
>
>Anyone know where I should start to look at trouble
--On Tuesday, October 22, 2002 12:20:15 -0400 Thom Paine <[EMAIL PROTECTED]> wrote:
On Tue, 2002-10-22 at 12:03, Martin Schwarz wrote:
IMO you are experiencing perfectly normal behaviour:
- amcheck -m doesn't find any errors, thus is keeping quiet. You will
only get mail from amcheck -m if i
On Tue, 2002-10-22 at 12:09, Martin A. Brooks wrote:
> At 11:49 22/10/2002 -0400, Thom Paine wrote:
> >I have a plain jane RedHat 7.3 server with amanda running.
> >
> >For some reason amanda is not sending out the mail report from amcheck
> >-m DailySet1. I get the report after the backup has run.
On Tue, Oct 22, 2002 at 12:20:15PM -0400, Thom Paine wrote:
> On Tue, 2002-10-22 at 12:03, Martin Schwarz wrote:
> > "Nothing is printed, but mail is sent if any errors are detected."
> > (amcheck manpage)
>
> Oh, well then. I thought it would email with an okay similar to the
> amcheck DailyS
On Tue, 2002-10-22 at 12:03, Martin Schwarz wrote:
> IMO you are experiencing perfectly normal behaviour:
>
> - amcheck -m doesn't find any errors, thus is keeping quiet. You will
> only get mail from amcheck -m if it has encountered some errors:
>
> "Nothing is printed, but mail is sent if
At 11:49 22/10/2002 -0400, Thom Paine wrote:
I have a plain jane RedHat 7.3 server with amanda running.
For some reason amanda is not sending out the mail report from amcheck
-m DailySet1. I get the report after the backup has run.
You'll only get a mail if there's a problem detected during amc
On Tue, Oct 22, 2002 at 11:49:31AM -0400, Thom Paine wrote:
> For some reason amanda is not sending out the mail report from amcheck
> -m DailySet1. I get the report after the backup has run.
IMO you are experiencing perfectly normal behaviour:
- amcheck -m doesn't find any errors, thus is keepi
I have a plain jane RedHat 7.3 server with amanda running.
For some reason amanda is not sending out the mail report from amcheck
-m DailySet1. I get the report after the backup has run.
Anyone know where I should start to look at trouble shoot this?
Thanks,
--
-=/>Thom
Red Hat Linux release 8
ok sorry, I found the example in example/disklist
it work fine :)
howener, I have noticed that server AND client machine must be in 2.4.3
version.
Brunet Eric wrote:
are you sure of this functionnality, because I tested the 2.4.3 with
multiple same disklist entry, like this:
80.65.xxx.yyy /hom
Thanks, I figured as much.
Would be nice to see amanda have a "pre" and "post"
script in the amanda.conf... but a wrapper should
work.
Jerry
--- jordivi <[EMAIL PROTECTED]> wrote:
> Hi
>
> You can write a wrapper, I'm doing so with smbclient
> but should work for
> gtar or dump. I use it to di
Hi list,
my problem is solved for now. It's been more related to automount issues.
I'm doing the mount of the [0-2] dirs via submount now.
Thanks anyways
Michael Mayer
--
Fatal Error: Found [MS-Windows] System -> R
--On Tuesday, October 22, 2002 15:37:54 +0200 Mozzi <[EMAIL PROTECTED]> wrote:
When I run amcheck I get the following:
Amanda Backup Client Hosts Check
ERROR: earth.mydomain.net: [Can't open exclude file '/usr/local/lib/amanda/exclude.gtar': No such file or direc
On Tue, Oct 22, 2002 at 10:04:41AM -0300, Doug Meredith wrote:
> I have seen this a couple of times now. In the notes section of the report,
> planner claims "Incremental of filet:/platoon/v1.1 bumped to level 2.".
> According to the dump summary, a level 0 was done for this directory. The
> stat
When I run amcheck I get the following:
Amanda Backup Client Hosts Check
ERROR: earth.mydomain.net: [Can't open exclude file
'/usr/local/lib/amanda/exclude.gtar': No such file or directory]
ERROR: earth.mydomain.net: [Can't open exclude file
'/usr/local/lib/amand
I have seen this a couple of times now. In the notes section of the report,
planner claims "Incremental of filet:/platoon/v1.1 bumped to level 2.".
According to the dump summary, a level 0 was done for this directory. The
statistics section shows two level 0 and six level 1 dumps. Has anyone see
Hi,
Moment, i think i don't understand your problem, so lets clarify a bit:
you have installed amanda-client on all the hosts in question.
so why do you want to automount the directory's via nfs?
i guess they are local filesystems to the clients, aren't they?
you should install amanda on the nfs s
are you sure of this functionnality, because I tested the 2.4.3 with
multiple same disklist entry, like this:
80.65.xxx.yyy /home/test comp-user-tar-incr-adherent_a
80.65.xxx.yyy /home/test comp-user-tar-incr-adherent_b
(only excluding rule change in these 2 dumptypes)
but I
Hi,
amanda is installed on each client. My problem is how to mount them via
automounter in /home/$host including the subdirs [0-2] which are diferent
filesystems.
Michale
--
Fatal Error: Found [MS-Windows] System -> Repartit
Hi,
Why do you want to nfs-mount these dirs to the amanda server?
It is much better to install the amanda-client part on all these machines
and tell amanda to get the backups direct from these hosts.
This way you can let them do compression localy, saving time, bandwith and
cpu-power on your amanda
Hi
You can write a wrapper, I'm doing so with smbclient but should work for
gtar or dump. I use it to display a Windows popup saying the user to
close applications for a while, sleep 20 seconds, back it up, and a second
popup notifying we are finished. Per machine.
My /usr/bin/smbclient look some
Hello
i get always this error during backup.
FAILURE AND STRANGE DUMP SUMMARY:
db2/izo0/mysql lev 1 FAILED [dumps way too big, must skip
incremental dumps]
fs1 /izo0/home/taoweb lev 1 FAILED [dumps way too big, must skip
incremental dumps]
fs1 /izo0/home/mup lev 1 FAILED [d
35 matches
Mail list logo
