RE: [/sbin/dump returned 3]
well updating to static rpm didn't work. I am not sure it's the problem of dump -- other partitions dump ok on the same system. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Joi Ellis Sent: Thursday, December 21, 2000 5:30 PM To: Shane T. Ferguson Cc: Bernhard R. Erdmann; Amanda-Users Subject: RE: [/sbin/dump returned 3] On Thu, 21 Dec 2000, Shane T. Ferguson wrote: >Date: Thu, 21 Dec 2000 17:05:34 -0400 >From: Shane T. Ferguson <[EMAIL PROTECTED]> >To: Bernhard R. Erdmann <[EMAIL PROTECTED]> >Cc: Amanda-Users <[EMAIL PROTECTED]> >Subject: RE: [/sbin/dump returned 3] > >I got the latest dump from sourceforge about 2 weeks ago. Did you get the static rpm, or the dynamic one? RH5.2 was a libc5 platform, but the current rpms assume you're using glibc. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
help
unsubscribe
RE: [/sbin/dump returned 3]
I will try the static rpm update first and run that before giving gnutar a try. -Original Message- From: Joi Ellis [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 5:30 PM To: Shane T. Ferguson Cc: Bernhard R. Erdmann; Amanda-Users Subject: RE: [/sbin/dump returned 3] On Thu, 21 Dec 2000, Shane T. Ferguson wrote: >Date: Thu, 21 Dec 2000 17:05:34 -0400 >From: Shane T. Ferguson <[EMAIL PROTECTED]> >To: Bernhard R. Erdmann <[EMAIL PROTECTED]> >Cc: Amanda-Users <[EMAIL PROTECTED]> >Subject: RE: [/sbin/dump returned 3] > >I got the latest dump from sourceforge about 2 weeks ago. Did you get the static rpm, or the dynamic one? RH5.2 was a libc5 platform, but the current rpms assume you're using glibc. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
RE: [/sbin/dump returned 3]
oops, my mistake -- forgot to specify 'program gnutar' in my dumptype definition. I will try that to see if it will work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Shane T. Ferguson Sent: Thursday, December 21, 2000 10:12 PM To: Dan Wilder; Amanda-Users Subject: RE: [/sbin/dump returned 3] I even tried it using gnu-tar .. same results -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Wilder Sent: Thursday, December 21, 2000 5:21 PM To: Amanda-Users Subject: Re: [/sbin/dump returned 3] On Thu, Dec 21, 2000 at 05:05:34PM -0400, Shane T. Ferguson wrote: > I got the latest dump from sourceforge about 2 weeks ago. Dump has been problematic, off and on, for years and years. With each new release comes a new wave of users who proclaim, "dump works well for me, now". Then comes the trickle for whom it continues to fail. The story repeats itself, on and on. Consider using tar. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Bernhard R. Erdmann > Sent: Thursday, December 21, 2000 4:41 PM > To: Shane T. Ferguson > Cc: Amanda-Users > Subject: Re: [/sbin/dump returned 3] > > > "Shane T. Ferguson" wrote: > > > > Whenever I do my backups, everything dumps fine except for 1 specific > > partition (the / (root) partition on a remote machine). I always get the > > following error: > [...] > > | DUMP: master/slave protocol botched. > > | DUMP: The ENTIRE dump is aborted. > > sendbackup: error [/sbin/dump returned 3] > > \ > > > > I am using Amanda 2.4.2. The host machine is RH6.1 and the above client is > > RH5.2. Also, other partitions on the above client dump fine. Any > suggestions > > as to what I did wrong? Thanks. > > What version of dump are you using? RedHat has an update to dump 0.4b19 > for RHL 5.2 available. > > -- - Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Correspondent SSC, Inc. P.O. Box 55549 Phone: 206-782-7733 x123 Seattle, WA 98155-0549 URLhttp://www.linuxjournal.com/ -
Re: typetape
On Dec 21, 2000, Monserrat Seisdedos Nuñez <[EMAIL PROTECTED]> wrote:
>> > Yes the system is hang.
This is not something a user process should be able to do, ever. If
the system hangs, you've got a problem with the kernel of the OS, more
likely in the SCSI tape driver. You'll have to reset the machine and
start over, and hope for the best. But if the system hangs while
writing garbage to the tape to test its length, there's no reason to
have much hope that it won't hang while writing your backups too.
>> > Any way, what is exactly the meaning of much quicker??, 1
>> or 2 days??
A few hours.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
RE: [/sbin/dump returned 3]
I even tried it using gnu-tar .. same results -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Wilder Sent: Thursday, December 21, 2000 5:21 PM To: Amanda-Users Subject: Re: [/sbin/dump returned 3] On Thu, Dec 21, 2000 at 05:05:34PM -0400, Shane T. Ferguson wrote: > I got the latest dump from sourceforge about 2 weeks ago. Dump has been problematic, off and on, for years and years. With each new release comes a new wave of users who proclaim, "dump works well for me, now". Then comes the trickle for whom it continues to fail. The story repeats itself, on and on. Consider using tar. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Bernhard R. Erdmann > Sent: Thursday, December 21, 2000 4:41 PM > To: Shane T. Ferguson > Cc: Amanda-Users > Subject: Re: [/sbin/dump returned 3] > > > "Shane T. Ferguson" wrote: > > > > Whenever I do my backups, everything dumps fine except for 1 specific > > partition (the / (root) partition on a remote machine). I always get the > > following error: > [...] > > | DUMP: master/slave protocol botched. > > | DUMP: The ENTIRE dump is aborted. > > sendbackup: error [/sbin/dump returned 3] > > \ > > > > I am using Amanda 2.4.2. The host machine is RH6.1 and the above client is > > RH5.2. Also, other partitions on the above client dump fine. Any > suggestions > > as to what I did wrong? Thanks. > > What version of dump are you using? RedHat has an update to dump 0.4b19 > for RHL 5.2 available. > > -- - Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Correspondent SSC, Inc. P.O. Box 55549 Phone: 206-782-7733 x123 Seattle, WA 98155-0549 URLhttp://www.linuxjournal.com/ -
Re: invalid mid from server
On Dec 20, 2000, Thom Sulanke <[EMAIL PROTECTED]> wrote:
> ? code 0 opening remote file \talks\cern092600.ppt (\talks\)
> ? invalid mid from server!
> sendbackup: error [/usr/bin/smbclient returned 1]
> Does anyone know the source or remedy for this "invalid mid from
> server" error?
The source is certainly smbclient. Which means the second question is
more likely to be answered in a mailing list devoted to Samba :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Firewall
Wang, Depending on what firewall software you are using, you should be able to do port forwarding, i.e. when a request hits the firewall coming from the amanda server on port 1008x udp or tcp you would need to setup rules to forward these packets to the port lower than 1024 on the external interfaces. If your firewall is using linux w/ kernel 2.2.x, look at ipchains and ipfwadm, or if its kernel 2.4.xpre then look to iptables (Netfilter) rules. read the manpages, othewise if its another firewall package, there should be a means to forward packets to another machine and/or port for a service traversing the firewall. I hope that was what you meant. Thanks Phil On Thu 21 Dec 2000 at 14:36:25 -0800, you wrote: > > Hi folks, > > I've built the Amanda-2.4.2 backup inside firewall. > Server and client machines are using the ports as: > amanda 10080/udp > amandaidx 10082/tcp > amidxtape 10083/tcp . > > We'are going to backup servers outside firewall, the > build require with option --with-portrange=x and > --with-udpportreage=xx. My question is : do we > have to re-config our servers inside firewall to > change > to those ports because the ports outside firewall are > required set to the ports lower then 1024. Thank you > in advance. > > Wang > > > __ > Do You Yahoo!? > Yahoo! Shopping - Thousands of Stores. Millions of Products. > http://shopping.yahoo.com/ > -- Phillip Davis, MIS Department 415.354.4238 tel or x4238 @ 415.354.4878 [EMAIL PROTECTED], http://www.linuxcare.com/ Linuxcare. Support for the Revolution.
Firewall
Hi folks, I've built the Amanda-2.4.2 backup inside firewall. Server and client machines are using the ports as: amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp . We'are going to backup servers outside firewall, the build require with option --with-portrange=x and --with-udpportreage=xx. My question is : do we have to re-config our servers inside firewall to change to those ports because the ports outside firewall are required set to the ports lower then 1024. Thank you in advance. Wang __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
RE: [/sbin/dump returned 3]
On Thu, 21 Dec 2000, Shane T. Ferguson wrote: >Date: Thu, 21 Dec 2000 17:05:34 -0400 >From: Shane T. Ferguson <[EMAIL PROTECTED]> >To: Bernhard R. Erdmann <[EMAIL PROTECTED]> >Cc: Amanda-Users <[EMAIL PROTECTED]> >Subject: RE: [/sbin/dump returned 3] > >I got the latest dump from sourceforge about 2 weeks ago. Did you get the static rpm, or the dynamic one? RH5.2 was a libc5 platform, but the current rpms assume you're using glibc. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: [/sbin/dump returned 3]
On Thu, Dec 21, 2000 at 05:05:34PM -0400, Shane T. Ferguson wrote: > I got the latest dump from sourceforge about 2 weeks ago. Dump has been problematic, off and on, for years and years. With each new release comes a new wave of users who proclaim, "dump works well for me, now". Then comes the trickle for whom it continues to fail. The story repeats itself, on and on. Consider using tar. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Bernhard R. Erdmann > Sent: Thursday, December 21, 2000 4:41 PM > To: Shane T. Ferguson > Cc: Amanda-Users > Subject: Re: [/sbin/dump returned 3] > > > "Shane T. Ferguson" wrote: > > > > Whenever I do my backups, everything dumps fine except for 1 specific > > partition (the / (root) partition on a remote machine). I always get the > > following error: > [...] > > | DUMP: master/slave protocol botched. > > | DUMP: The ENTIRE dump is aborted. > > sendbackup: error [/sbin/dump returned 3] > > \ > > > > I am using Amanda 2.4.2. The host machine is RH6.1 and the above client is > > RH5.2. Also, other partitions on the above client dump fine. Any > suggestions > > as to what I did wrong? Thanks. > > What version of dump are you using? RedHat has an update to dump 0.4b19 > for RHL 5.2 available. > > -- - Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Correspondent SSC, Inc. P.O. Box 55549 Phone: 206-782-7733 x123 Seattle, WA 98155-0549 URLhttp://www.linuxjournal.com/ -
RE: [/sbin/dump returned 3]
I got the latest dump from sourceforge about 2 weeks ago. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bernhard R. Erdmann Sent: Thursday, December 21, 2000 4:41 PM To: Shane T. Ferguson Cc: Amanda-Users Subject: Re: [/sbin/dump returned 3] "Shane T. Ferguson" wrote: > > Whenever I do my backups, everything dumps fine except for 1 specific > partition (the / (root) partition on a remote machine). I always get the > following error: [...] > | DUMP: master/slave protocol botched. > | DUMP: The ENTIRE dump is aborted. > sendbackup: error [/sbin/dump returned 3] > \ > > I am using Amanda 2.4.2. The host machine is RH6.1 and the above client is > RH5.2. Also, other partitions on the above client dump fine. Any suggestions > as to what I did wrong? Thanks. What version of dump are you using? RedHat has an update to dump 0.4b19 for RHL 5.2 available.
Re: [/sbin/dump returned 3]
"Shane T. Ferguson" wrote: > > Whenever I do my backups, everything dumps fine except for 1 specific > partition (the / (root) partition on a remote machine). I always get the > following error: [...] > | DUMP: master/slave protocol botched. > | DUMP: The ENTIRE dump is aborted. > sendbackup: error [/sbin/dump returned 3] > \ > > I am using Amanda 2.4.2. The host machine is RH6.1 and the above client is > RH5.2. Also, other partitions on the above client dump fine. Any suggestions > as to what I did wrong? Thanks. What version of dump are you using? RedHat has an update to dump 0.4b19 for RHL 5.2 available.
RE: [/sbin/dump returned 3]
I updated the dump program on all machines. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 4:41 PM To: Shane T. Ferguson Cc: Amanda-Users Subject: Re: [/sbin/dump returned 3] "Shane T. Ferguson" wrote: > > Whenever I do my backups, everything dumps fine except for 1 specific > partition (the / (root) partition on a remote machine). I always get the > following error: [...] > | DUMP: master/slave protocol botched. > | DUMP: The ENTIRE dump is aborted. > sendbackup: error [/sbin/dump returned 3] > \ > > I am using Amanda 2.4.2. The host machine is RH6.1 and the above client is > RH5.2. Also, other partitions on the above client dump fine. Any suggestions > as to what I did wrong? Thanks. What version of dump are you using? RedHat has an update to dump 0.4b19 for RHL 5.2 available.
[/sbin/dump returned 3]
Whenever I do my backups, everything dumps fine except for 1 specific partition (the / (root) partition on a remote machine). I always get the following error: FAILURE AND STRANGE DUMP SUMMARY: mail hda2 lev 0 FAILED [/sbin/dump returned 3] taper: FATAL shmctl: Invalid argument FAILED AND STRANGE DUMP DETAILS: /-- mail hda2 lev 0 FAILED [/sbin/dump returned 3] sendbackup: start [mail:hda2 level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end | DUMP: Date of this level 0 dump: Thu Dec 21 09:21:05 2000 | DUMP: Date of last level 0 dump: the epoch | DUMP: Dumping /dev/hda2 (/) to standard output | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 36913 tape blocks. | DUMP: dumping (Pass III) [directories] | DUMP: master/slave protocol botched. | DUMP: The ENTIRE dump is aborted. sendbackup: error [/sbin/dump returned 3] \ I am using Amanda 2.4.2. The host machine is RH6.1 and the above client is RH5.2. Also, other partitions on the above client dump fine. Any suggestions as to what I did wrong? Thanks. Shane T. Ferguson
No Subject
In a message dated: Thu, 21 Dec 2000 14:34:19 +0800
"Mark Berger" said:
>What I cannot seem to figure out is supposing I have 8 machines ( 1 main
>server & 7 others) & want to do a full backup of the main server every night
>& a full backup of one other machine per day either in rotation or ad-hoc
>how can I persuade amanda to allow me to label / rotate tapes manually &
>always do a full backup of the specified machine?
Well, you can tell amanda what type of backup to perform in the disklist
for that particular host:
hostA / comp-root-always-full
says to backup the root partition on hostA and use the "comp-root-always-full"
dumptype from the amanda.conf file. This dumptype (for me anyway) is defined
in amanda.conf as:
define dumptype comp-root-always-full {
comp-always-full
comment "Root partitions with compression"
compress client fast
priority high
holdingdisk yes
maxdumps 5
}
which in turn inherits from the "comp-always-full" dumptype defined thusly:
define dumptype comp-always-full {
global
comment "Full dump of this filesystem always"
compress server fast
priority high
dumpcycle 0
}
So, hostA always gets a full dump performed when ever amdump is run on this
particular configuration.
>It appears to me that much effort has gone into the scheduling etc but I am
>completely unclear as to how I might just say "backup machine 10.0.78.56 (
>or whatever ) in full to whatever tape happens to be in the drive - no
>arguments - no wrong tape etc just do it!" . - Or for that matter restore a
>file / group of files from tape in drive to machine
>xx.xx.xx.xx:/directory/subdirectory
Well, using whatever tape is in the drive may be a little trickier, since
amanda was intentionally designed to never overwrite an existing tape.
However, with a little ingenuity, all things are possible :)
You could write a script that did something like the following. (beware,
completely untested :)
#!/usr/bin/perl
$config="DailySet1"
$current=`amtape DailySet1 current`;
($junk,$slot,$junk,$date,$junk,$label) = split (/\s/,$current);
$slot =~ s/://g;
if ( $current =~ /label DailySet/) {
$label = s/.*label (\w+\d+)/\1/;
system ("amrmtape -q $config $label);
system (amtape $config $label);
}
system ("amdump $config");
The only problem with the above command is this line:
$current=`amtape DailySet1 current`;
The problem is that amtape seems to send all it's output to STDERR instead of
STDOUT. You may be able to get creative with shell re-direction.
>Surely there must be a way to use the program on a more simple basis as
>above
Sure, you need a little creativity :)
>Perhaps sonmeone would be good enough to shed some light on this mystery
>please??
Make sure you read through all the man pages and understand all the various
amanda "am" commands. Those combined with some shell scripting can result in
some truly and amazingly customizable configurations :)
--
Seeya,
Paul
I'm in shape, my shape just happens to be pear!
If you're not having fun, you're not doing it right!
Re: amanda
Jan Van den Abeele wrote:
>
> For obvious reasons (inetd is no more ... xinetd.conf) this doesn't work
> for Redhat 7.0...
Check the list archives using "xinetd" as keyword. This has been handled
already some times in the past. I found the following posting (but there
might be more out there):
snip-
1) the rpm files don't create a file amandad in /etc/xinetd.d, so you
have to create one :
#xinetd.d file = amandad#
# default: off
#
# description: Part of the Amanda server package
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= operator
group = disk
server = /usr/lib/amanda/amandad
disable = no
}
after this you have to create an entry in hosts.allows as well ... I
added the following line on the server PC:
ALL: localhost 127.0.0.1 128.197.61.90
...
4) I used the following amandaidx amidxtape files :
#xinetd.d file = amandaidx#
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
socket_type = stream
protocol= tcp
wait= yes
user= operator
group = disk
server = /usr/lib/amanda/amindexd
disable = no
}
#xinetd.d file = amidxtape#
# default: off
#
# description: Part of the amanda server package
#
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= operator
group = disk
server = /usr/lib/amanda/amidxtaped
disable = no
}
snip-
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: your mail
On Thu, 21 Dec 2000, Mark Berger wrote: > Hi, > > > I was inspired to mess with the Amanda program for the nth time recently. > > It seem to have the feature that I want - & some that I do not want as > well! > > What I cannot seem to figure out is supposing I have 8 machines ( 1 main > server & 7 others) & want to do a full backup of the main server every night > & a full backup of one other machine per day either in rotation or ad-hoc > how can I persuade amanda to allow me to label / rotate tapes manually & > always do a full backup of the specified machine? Look into amadmin force. You could script this so that full dumps are scheduled for when you want. However, I recommend against this. Amanda's scheduler does an excellent job of deciding when to do a full dump of each file system in the interest of keeping the time for the amdump run roughly the same. Forcing full dumps will just screw up the schedule and Amanda will do a better job than what you are planning. $.02 > > It appears to me that much effort has gone into the scheduling etc but I am > completely unclear as to how I might just say "backup machine 10.0.78.56 ( > or whatever ) in full to whatever tape happens to be in the drive - no > arguments - no wrong tape etc just do it!" . - Or for that matter restore a > file / group of files from tape in drive to machine > xx.xx.xx.xx:/directory/subdirectory You seek amrecover, some time spent with the documentation would be well spent. Bill Carlson -- Systems Programmer[EMAIL PROTECTED]| Opinions are mine, Virtual Hospital http://www.vh.org/| not my employer's. University of Iowa Hospitals and Clinics|
Help to solve a dump problem
Hi: I'm having a problem with 3 filesystem to get them dumped. Everything was running smoothly until about 30 days ago. In the search of a solution I've already upgraded to Amanda2.4.2 but no lucky. Persusing the logfiles I've noticed that Amanda is trying to dump those 3 filesystems directly to tape. One piece of a amdump log file is here: driver: dumping sv:da0s1f directly to tape driver: send-cmd time 3469.442 to taper: PORT-WRITE 00-00035 sv da0s1f 0 2000121 9 driver: result time 3469.442 from taper: PORT 1596 driver: send-cmd time 3469.443 to dumper0: PORT-DUMP 01-00036 1596 sv da0s1f 0 1 970:1:1:0:0:0 DUMP |;bsd-auth;compress-best;index; driver: state time 3469.443 free kps: 1885 space: 819200 taper: writing idle-dum pers: 3 qlen tapeq: 0 runq: 1 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 3469.443 if : free 485 if LE0: free 400 if LOCAL: f ree 1000 driver: hdisk-state time 3469.443 hdisk 0: free 819200 dumpers 0 driver: result time 3469.444 from dumper0: FAILED 01-00036 [taper port open: Con nection refused] driver: result time 3589.442 from taper: TAPE-ERROR 00-00035 [port connect timeo ut] In the report I got (obviously): sv da0s1f lev 0 FAILED [dump to tape failed] sv da0s1g lev 0 FAILED [dump to tape failed] My holding disk has only 800mbytes (the above compressed filesystem has about 2.5mbytes) - I've set CHUNKSIZE to less than 800mbytes. I I don't know what causes the TAPE ERROR (maybe speed ? Bandwidth ?). I've defined bandwidth to 600Kbps and I'm using a HP Surestore Dat 24 (that allows, if I'm not mistaken, 1mbit/s). I've searched the mailling list, read the faq, the docs and do not find a clue to help me out. Anyone has a tip or direction ? Thanks a lot, Helio. -- CompuLand ISP Admin GnuPG Public Key: http://www.compuland.com.br/helio/gpgpublic.txt -- In our era, the road to holiness necessarily passes through the world of action. -Dag Hammarskjold
Re:typetape
> > > > > Yes the system is hang. I can't do anything nor even move the mouse. > > Any way, what is exactly the meaning of much quicker??, 1 > or 2 days?? > > Thanks for your help > > mo > > > -Mensaje original- > > > De: Jens Krause [mailto:[EMAIL PROTECTED]] > > > Enviado el: jueves 21 de diciembre de 2000 13:43 > > > Para: [EMAIL PROTECTED] > > > CC: '[EMAIL PROTECTED]' > > > Asunto: Re: tapetype > > >=20 > > >=20 > > >=20 > > >=20 > > > Monserrat Seisdedos Nu=F1ez wrote: > > >=20 > > > > Hello every body: > > > > i have run tapetype in a PV-100T-DDS4, in a Power Edge > > 2450. It is=20 > > > running > > > > since yesterday at 2 PM, almost 24 hours, the system is=20 > > > completely halt,=20 > > > it > > > > is normal or should i stop the process??? > > > > thanks > > >=20 > > > What do you mean with "the system is completely halt"? > > > Does your system hang? > > >=20 > > > Tapetype from Amanda versions up to 2.4.1 will run a very > very long > > > time (several days is normal, afaik). > > > The Tapetype from Amanda 2.4.2 will be much quicker. > > >=20 > > >=20 > > > Jens > > >=20 > > >
Re: your mail
On Thu, 21 Dec 2000 at 2:34pm, Mark Berger wrote > Hi, Hi. These types of questions really belong only on amanda-users. So that's where I've responded, and set follow-ups. > I was inspired to mess with the Amanda program for the nth time recently. If you devote just a little more time to your "messing with", I bet you'll be very pleased. > What I cannot seem to figure out is supposing I have 8 machines ( 1 main > server & 7 others) & want to do a full backup of the main server every night > & a full backup of one other machine per day either in rotation or ad-hoc > how can I persuade amanda to allow me to label / rotate tapes manually & > always do a full backup of the specified machine? This is easy. In your amanda.conf, you specify a dumpcycle of 7 days, and runspercycle of 7 (assuming you're going to run amanda every day). Your tapecycle should be at least 8, but make it as long as you need a history for. Where you handle the "full of this machine every day, full of these others once a week" is in the disklist. For the machine you want a full backup of everyday, you use, e.g., a dumptype like "always-full" which, in its definition, includes "dumpcycle 0". For the others, you use a different dumptype, e.g., comp-user, with no dumpcycle definition. This is exactly what I do. I do full backups of all my machines' /var and / partitions every night, and rotate full backups of everybody's /home drives. > It appears to me that much effort has gone into the scheduling etc but I am > completely unclear as to how I might just say "backup machine 10.0.78.56 ( > or whatever ) in full to whatever tape happens to be in the drive - no > arguments - no wrong tape etc just do it!" . - Or for that matter restore a > file / group of files from tape in drive to machine > xx.xx.xx.xx:/directory/subdirectory Restoring is handled by amrecover (for picking and choosing) and amrestore (for getting an entire dump image), which both have very informative man pages... Hope this helps. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: tapetype
Monserrat Seisdedos Nuñez wrote: > Hello every body: > i have run tapetype in a PV-100T-DDS4, in a Power Edge 2450. It is running > since yesterday at 2 PM, almost 24 hours, the system is completely halt, it > is normal or should i stop the process??? > thanks What do you mean with "the system is completely halt"? Does your system hang? Tapetype from Amanda versions up to 2.4.1 will run a very very long time (several days is normal, afaik). The Tapetype from Amanda 2.4.2 will be much quicker. Jens
amanda
Hi I want to setup a client on Redhat Linux 7.0. The Amanda server (2.4.1) is installed on another linux machines (redhat 6.1). I used to setup a client by adding to the inetd.conf amanda dgram udp wait root /sysman/amanda-2.4.1p1/pineau/libexec/amandad amandad For obvious reasons (inetd is no more ... xinetd.conf) this doesn't work for Redhat 7.0... Can anybody help me? Jan
tapetype
Hello every body: i have run tapetype in a PV-100T-DDS4, in a Power Edge 2450. It is running since yesterday at 2 PM, almost 24 hours, the system is completely halt, it is normal or should i stop the process??? thanks
Re: newby
Monserrat Seisdedos Nuñez wrote: > > Hello : > > i'm a newby users of amanda. > > I'm testing the amanda utility and i just want to backup the > > /home fs in > > /home/amanda which is the holding disk but not dumping it to > > the tape, (i > > haven't got any yet),so i typed /dev/null in the configure file field > > tapedev > > > > i want to obtain in the holding disk an image of what i would > > had in the > > tape if i would had one. > > it is possible?? Yes; i assume you are using Amanda 2.4.1 or 2.4.2? In these versions /dev/null is for testing purposes only. Use a device that does'nt really exist and configure your dumptype to use a holdingdisk. Then all dumps will go to the holdingdisk and nothing will be written to a non existing device. Jens
Re: amrecover problem
Hi Mirko and list, > We set up a new amanda-2.4.2 backup-server, and right now I'm > involved in testing > the backup and recover with the server. > While testing amrecover, some strange behaviour showed up: > I'm unable to see all backed up files while browsing trough the > directorys > via amrecover, but viewing the index-files manualy showed that the > files are > included in the backup... Whats the problem with this ? > > We use amanda on Solaris, but with gnu-tar... I ran across the same problem yesterday when trying to restore a directory which had been deleted by accident. I should have seen more than 15 directories with "ls" in amrecover, but all I got was 3 entries. I tried the "setdate" command, but that did not help. In the index-files all the directory entries where present, and I was able to restore the directory "by hand". This happens in my case with amanda 2.4.1p1 on Solaris 2.6 system. Has anybody an idea what is happening here? Urte
Re: hostnames do not match
Bernhard! > And verify DNS reverse lookup Off the top of my head that gives a different error... :-) -- GOD SAVE AMERICA! - because President Bush, the Second Will Not!
Re: hostnames do not match
David Lloyd wrote: > > Roshan! > > > ERROR: stat: [hostnames do not match: amanda1 amanda1.popken.de] > > Client check: 1 host checked in 0.264 seconds, 1 problem found > > amanda1 is not the same as amanda1.popken.de. They don't match... > > specify: > > amanda1.popken.de in the disk list file followed by the other normal > stuff... And verify DNS reverse lookup
Re: [ BUG? ] Running out of disk space...
Jean-Louis Martineau wrote: > On Tue, Dec 19, 2000 at 10:00:23AM +0100, David Klasinc wrote: > > Banzai! > > > > I upgraded to 2.4.2 and I noticed that if dump won't fit on one disk that > > amdump will go into endless loop trying to do a backup. > > Could you try this patch? > > Jean-Louis > -- > Jean-Louis Martineau email: [EMAIL PROTECTED] > Departement IRO, Universite de Montreal > C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 > Montreal, Canada, H3C 3J7Fax: (514) 343-5834 > > > >driver.c.est_size.diffName: driver.c.est_size.diff > Type: Plain Text (text/plain) Tryed the patch ;) amanda still loops infinitely ... following is a part of my amdump file got result for host localhost disk /artis/sources: 0 -> 2813650K, -1 -> -1K, -1 -> -1K ... ... pondering localhost:/artis/sources... next_level0 -11312 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 1406825 total size 1410460 total_lev0 1409900 balanced-lev0size 281980 ... ... INITIAL SCHEDULE (size 3156618): localhost /artis/sources pri 11313 lev 0 size 1406825 ... ... GENERATING SCHEDULE: localhost /artis/sources 11313 0 1970:1:1:0:0:0 1406825 46894 ... ... driver: send-cmd time 6386.362 to dumper0: FILE-DUMP 00-9 /opt/dumps/amanda/20001220/localhost._artis_sources.0 localhost /artis/sources 0 1970:1:1:0:0:0 1048576 GNUTAR 1406944 |;bsd-auth;compress-fast;index; driver: state time 6386.362 free kps: 1970 space: 283715 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 6386.362 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time 6386.362 hdisk 0: free 283715 dumpers 1 driver: result time 7440.619 from dumper0: RQ-MORE-DISK 00-9 driver: send-cmd time 7440.631 to dumper0: CONTINUE /opt/dumps/amanda/20001220/localhost._artis_sources.0 1048576 70400 driver: state time 7440.631 free kps: 1970 space: 213315 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 7440.631 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time 7440.631 hdisk 0: free 213315 dumpers 1 driver: result time 7490.946 from dumper0: RQ-MORE-DISK 00-9 driver: send-cmd time 7491.022 to dumper0: CONTINUE /opt/dumps/amanda/20001220/localhost._artis_sources.0 1048576 73920 driver: state time 7491.022 free kps: 1970 space: 139395 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 7491.022 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time 7491.022 hdisk 0: free 139395 dumpers 1 driver: result time 7540.364 from dumper0: RQ-MORE-DISK 00-9 driver: send-cmd time 7540.379 to dumper0: CONTINUE /opt/dumps/amanda/20001220/localhost._artis_sources.0 1048576 77600 driver: state time 7540.379 free kps: 1970 space: 61795 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 7540.379 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time 7540.379 hdisk 0: free 61795 dumpers 1 driver: result time 7608.579 from dumper0: RQ-MORE-DISK 00-9 driver: send-cmd time 7608.596 to dumper0: ABORT driver: state time 7608.596 free kps: 1970 space: 61795 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 7608.596 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time 7608.596 hdisk 0: free 61795 dumpers 0 dumper: kill index command driver: result time 7608.615 from dumper0: ABORT-FINISHED 00-9 driver: send-cmd time 7680.923 to dumper0: FILE-DUMP 00-00010 /opt/dumps/amanda/20001220/localhost._artis_sources.0 localhost /artis/sources 0 1970:1:1:0:0:0 1048576 GNUTAR 1629568 |;bsd-auth;compress-fast;index; driver: state time 7680.923 free kps: 1970 space: 61091 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 7680.923 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time 7680.923 hdisk 0: free 61091 dumpers 1 driver: result time 8171.638 from dumper3: driver: state time 8171.787 free kps: 1970 space: 61091 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 8171.787 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time 8171.787 hdisk 0: free 61091 dumpers 1 driver: result time 8186.346 from dumper2: driver: state time 8186.346 free kps: 1970 space: 61091 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 8186.346 if : free 600 if LE0: free 400 if LOCAL: free 970 driver: hdisk-state time
