unsubscribe thomas.baer@brodos.de
unsubscribe [EMAIL PROTECTED]
Re: tapetype entries
I have been using this drive with Linux dump and restore for over a year
now and have not had any problem. I have done many restores...
Since I am planning to use DUMP with amanda, I cannot see how this would
be any different.
I will look in the archives just in case though...
Anybody else had any problem with this drive?
Thanks,
Dick
P.S. If it was a firmware bug, maybe it was fixed by 2.39?
> Hi,
>
> you wrote on Freitag, 18. Januar 2002 on amanda users list:
>
> > [...]
> > define tapetype adr50 {
> > comment "OnStream Model: ADR50 Rev: 2.39"
> > length 21077 mbytes
> > filemark 29 kbytes
> > speed 547 kps
> > }
>
> Have you ever tried to actually *restore* data from this drive? My
> experience which is based on many contributions from other users is
> that this drive has a firmware bug which prevents it from working with
> amanda at all. Search the list archives for more.
>
> Regards,
> Moritz
>
Re: amrestore->newbie question
Is there a way to tell amrestore to restore the files from tape to a directory different than the original source? (just to make comparisons? of the file and to make sure that the file was correctly copied from the tape). Once again thanks for your help. > > > > > On Monday 04 February 2002 12:25, Alvaro Rosales R. wrote: > > Hi fellows, finnally I've got amanda running I have made some > > tests and I could see that amanda is what I was looking for, Now I > > want to make amanda use a tape per day but I want it to make full > > backups of my data each day I run it , How can I do this ?? > > > > Thanks in advance fo ryour answers > > in your amanda.conf file use these settings > > dumpcycle 0 > runspercycle 1 > tapecycle X (where X is the number of tape you have) > > Alvaro A. Rosales Rojas. a.k.a. RAZA Proud user of Pegasus Mail Soporte Tecnico de Sistemas Procacao S.A 3368113 ext 260 "You'll never know how far you can go until you break the chains that tie your soul "
Re: amrestore->newbie question
On Tue, 5 Feb 2002 at 8:07am, Alvaro Rosales R. wrote
> Is there a way to tell amrestore to restore the files from tape to a
> directory different than the original source? (just to make comparisons?
> of the file and to make sure that the file was correctly copied from the
> tape). Once again thanks for your help.
>
amrestore does not extract individual files from the tape -- it pulls off
the entire {dump|tar} image and puts that on disk as one file.
If you mean amrecover, then it will simply put files into whatever
directory in which you start it.
So, in short, yes.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: amrestore->newbie question
Hi Alvaro! On 5 Feb 02 at 8:07 you wrote: > Is there a way to tell amrestore to restore the files from tape to a > directory different than the original source? By default, amrestore restores the files with full path into the directory you start it up from. So, if you have backed up a file /home/alvaro/myfile (assuming /home is separate partition), you will restore the file to /home/alvaro/home/alvaro/myfile if you start amrestore in /home/alvaro directory. If you want to restore over the original file you start amrestore in /home. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * One can never know for sure what a deserted area looks like.
Re: Kernel 2.4.17 crashing
> Well, it's generally a really bad idea to run a kernel that hasn't been > all that thoroughly beaten on by the masses. What's a worse idea is > running a "bleeding-edge" kernel on the machine that does your backups! > I would never even consider doing backups on a machine with anything but > a stock release + vendor recommended updates! > > I would *very* strongly suggest you revert to the 7.1 or 7.2 kernel as > shipped by Red Hat (or superceded by Red Hat recommended updates, of > course). Well, it seems like there's overwhelming support for not running 2.4.18. Very well then. I had originally upgraded because I've been having problems with nfsd causing kernel panics occasionally. The new kernel stopped doing that, but then st would seemingly crash the kernel. Perhaps I'll try one of the kernels in between. Thanks for the input! -Chris
Cron and Amdump
For some strange reason, cron has stopped running Amdump for me at night. I do see that cron is trying to run amdump at night. cron.log: Feb 5 00:45:00 itchy CROND[6620]: (amanda) CMD (/usr/sbin/amdump BIG1) Here is Amanda's crontab: 0 16 * * 1-5/usr/sbin/amcheck -m BIG1 45 0 * * 2-6/usr/sbin/amdump BIG1 There is nothing in /tmp/amanda, as if amdump never runs. If I manually run amdump: su amanda -c "/usr/sbin/amdump BIG1" It works. I get logs in /tmp/amanda, and a report emailed to me. I changed group permissions for Amanda about a week ago. I noticed that I still had Amanda in the group "operator" from a previous install from a redhat rpm. Now, amanda is part of group "disk" (6). Amanda is set up like the following: amanda:x:33:6:Amanda user:/var/lib/amanda:/bin/bash Any thoughts? -- Cheers, Karl Bellve, Ph.D. ICQ # 13956200 Biomedical Imaging Group TLCA# 7938 University of Massachusetts Email: [EMAIL PROTECTED] Phone: (508) 856-6514 Fax: (508) 856-1840 PGP Public key: finger [EMAIL PROTECTED]
Problems with changer device
Hi, once again I've built a new kernel from source, 2.4.8-26mdk, with built in scsi and sg support including the option for scanning all luns. Now during but the changer is detected, as you guessed, at sg1: [-] SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 5 for device 00:10.0 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.1 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs Vendor: HPModel: C1557ARev: U812 Type: Sequential-Access ANSI SCSI revision: 02 (scsi0:A:5): 10.000MB/s transfers (10.000MHz, offset 32) Vendor: HPModel: C1557ARev: U812 Type: Medium Changer ANSI SCSI revision: 02 Vendor: IBM Model: DDYS-T09170N Rev: S96H Type: Direct-Access ANSI SCSI revision: 03 (scsi0:A:6): 40.000MB/s transfers (20.000MHz, offset 63, 16bit) scsi0:0:6:0: Tagged Queuing enabled. Depth 253 st: Version 20010812, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16 Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0 Attached scsi disk sda at scsi0, channel 0, id 6, lun 0 SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB) /dev/scsi/host0/bus0/target6/lun0: p1 p2 Attached scsi generic sg1 at scsi0, channel 0, id 5, lun 1, type 8 [-] I've changed chg-scsi.conf to [---] number_configs 1 eject 1 # Tapedrives need an eject command sleep 90 # Seconds to wait until the tape gets ready cleanmax100 # How many times could a cleaning tape get used changerdev /dev/sg1 # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/nst0 # the device that is used for the tapedrive 0 scsitapedev /dev/sg1 startuse1 # The slots associated with the drive 0 enduse 5 # cleancart 6 # the slot where the cleaningcartridge for drive 0 is located statfile/usr/local/etc/amanda/caup/tape0-slot # The file where the actual slot is stored cleanfile /usr/local/etc/amanda/caup/tape0-clean # The file where the cleanings are recorded usagecount /usr/local/etc/amanda/caup/totaltime tapestatus /usr/local/etc/amanda/caup/tapestatus [---] But i should have some bad configuration somewhere because when i run amcheck i get Amanda Tape Server Host Check - amcheck-server: slot 1: date Xlabel Tape-2 (first labelstr match) NOTE: skipping tape-writable test Tape Tape-2 label ok NOTE: info dir /usr/adm/amanda/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/adm/amanda/index: does not exist Server check took 26.628 seconds Amanda don't goes thru all the tapes, it just loaded tape from storage element 3 (and not slot 1 as mencioned). During amcheck i get an error at the lcd display in front of the tape drive stating: SCSI error: Check interface. I'm completly lost! Help? My debug files are bellow. TIA. Regards, Manuel Monteiro DEGUB FILES: [START amcheck.20020205151758.debug] amcheck: debug 1 pid 2189 ruid 1 euid 0 start time Tue Feb 5 15:17:58 2002 amcheck-clients: dgram_bind: socket bound to 0.0.0.0.565 changer: got exit: 0 str: 1 5 1 0 changer: got exit: 0 str: 1 /dev/nst0 amcheck: pid 2189 finish time Tue Feb 5 15:18:28 2002 [END amcheck.20020205151758.debug] [START chg-scsi.20020205151758.debug] chg-scsi: debug 1 pid 2192 ruid 1 euid 1 start time Tue Feb 5 15:17:58 2002 chg-scsi: $Id: chg-scsi.c,v 1.37 2002/01/08 01:32:38 martinea Exp $ ARG [0] : /usr/local/libexec/chg-scsi ARG [1] : -info Number of configurations: 1 Tapes need eject: Yes Inv. auto update: No barcode reader : No Tapes need sleep: 90 seconds Cleancycles : 100 Changerdevice : /dev/sg1 Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 1 Endslot : 5 Cleanslot : 6 Devicename: /dev/nst0 changerident : none SCSITapedev : /dev/sg1 tapeident : none statfile : /usr/local/etc/amanda/caup/tapestatus Slotfile : /usr/local/etc/amanda/caup/tape0-slot Cleanfile : /usr/local/etc/amanda/caup/tape0-clean Usagecount: /usr/local/etc/amanda/caup/totaltime DecodeModeSense : Disconnect/Reconnect Pag e Buffer Full Ratio 14 Buffer Empty Ratio0 Bus Inactivity Limit 0 Disconnect Time Limit 5120 Connect Time Limit0 Maximum Burst Size0 DTDC 0 DecodeModeSense : Element Address Assignment Page Medium Transport Element Address 0 Number of Medium Transport Elements 0 First Storage Element Address 2 Number of Storage Elements 6 First Import/Export Element Address 0 Numbe
Re: Cron and Amdump
Are you sure that the cron daemon is still running? ps aux | grep crond We have a box that the http daemon occasionally fills up memory, and the vm system seems to dump crond before anything else. On Tuesday 05 February 2002 07:38, Karl Bellve wrote: > For some strange reason, cron has stopped running Amdump for me at > night. I do see that cron is trying to run amdump at night. > > cron.log: > Feb 5 00:45:00 itchy CROND[6620]: (amanda) CMD (/usr/sbin/amdump BIG1) > > > Here is Amanda's crontab: > 0 16 * * 1-5/usr/sbin/amcheck -m BIG1 > 45 0 * * 2-6/usr/sbin/amdump BIG1 > > > There is nothing in /tmp/amanda, as if amdump never runs. > > If I manually run amdump: > su amanda -c "/usr/sbin/amdump BIG1" > > It works. I get logs in /tmp/amanda, and a report emailed to me. > > I changed group permissions for Amanda about a week ago. I noticed that > I still had Amanda in the group "operator" from a previous install from > a redhat rpm. Now, amanda is part of group "disk" (6). > > Amanda is set up like the following: > amanda:x:33:6:Amanda user:/var/lib/amanda:/bin/bash > > > > Any thoughts? -- Rick Morris Network Manager WeDoHosting.com 101-4226 Commerce Circle Victoria BC V8Z 6N6 ph: +1 250 479 1595 fax: +1 250 479 1517 [EMAIL PROTECTED] http://www.wedohosting.com
RE: Cron and Amdump
What does it say it /etc/group? Is amanda listed in the users for disk there? Did you reconfig amanda with-group=disk after you made this change? -Original Message- From: Karl Bellve [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 9:38 AM To: Amanda Subject: Cron and Amdump For some strange reason, cron has stopped running Amdump for me at night. I do see that cron is trying to run amdump at night. cron.log: Feb 5 00:45:00 itchy CROND[6620]: (amanda) CMD (/usr/sbin/amdump BIG1) Here is Amanda's crontab: 0 16 * * 1-5/usr/sbin/amcheck -m BIG1 45 0 * * 2-6/usr/sbin/amdump BIG1 There is nothing in /tmp/amanda, as if amdump never runs. If I manually run amdump: su amanda -c "/usr/sbin/amdump BIG1" It works. I get logs in /tmp/amanda, and a report emailed to me. I changed group permissions for Amanda about a week ago. I noticed that I still had Amanda in the group "operator" from a previous install from a redhat rpm. Now, amanda is part of group "disk" (6). Amanda is set up like the following: amanda:x:33:6:Amanda user:/var/lib/amanda:/bin/bash Any thoughts? -- Cheers, Karl Bellve, Ph.D. ICQ # 13956200 Biomedical Imaging Group TLCA# 7938 University of Massachusetts Email: [EMAIL PROTECTED] Phone: (508) 856-6514 Fax: (508) 856-1840 PGP Public key: finger [EMAIL PROTECTED]
Re: Cron and Amdump
Rebecca Pakish wrote: > > What does it say it /etc/group? Is amanda listed in the users for disk > there? Did you reconfig amanda with-group=disk after you made this change? > Amanda is part of group disk. disk:x:6:root,amanda I didn't compile Amanda, but used the RPMS. Redhat changed the user that Amanda was run under with the last RPM upgrade from operator to amanda. I didn't pay attention to see if they also changed the group that Amanda belonged to. So, last week, I noticed that I still had the following in /etc/group disk:x:6:root,operator But, I can't see why this would have broke cron running amdump. Remember, I can still run amdump as user amanda without problems. -- Cheers, Karl Bellve, Ph.D. ICQ # 13956200 Biomedical Imaging Group TLCA# 7938 University of Massachusetts Email: [EMAIL PROTECTED] Phone: (508) 856-6514 Fax: (508) 856-1840 PGP Public key: finger [EMAIL PROTECTED]
Re: Cron and Amdump
Rick Morris wrote: > > Are you sure that the cron daemon is still running? > ps aux | grep crond > > We have a box that the http daemon occasionally fills up memory, and the vm > system seems to dump crond before anything else. > Yes... root 1105 0.0 0.1 3696 128 ?SJan29 0:00 crond It also logs the attempt to run /usr/sbin/amdump in cron.log: Feb 5 00:45:00 itchy CROND[6620]: (amanda) CMD (/usr/sbin/amdump BIG1) -- Cheers, Karl Bellve, Ph.D. ICQ # 13956200 Biomedical Imaging Group TLCA# 7938 University of Massachusetts Email: [EMAIL PROTECTED] Phone: (508) 856-6514 Fax: (508) 856-1840 PGP Public key: finger [EMAIL PROTECTED]
amdump question
Hi, I use BSDI 4.2. AMANDA is already here. I have created the user amanda, have added it to group operator. amanda.conf has copied in /etc/amanda. Then: dmps:/etc/amanda | 25 >amdump amanda.conf amdump: could not find directory /etc/amanda/amanda.conf dmps:/etc/amanda | 26 > Would you be so kind to promt me how to compel amdump work? Thank you in advance, Mary
Re: Problems with changer device
I've done all of your suggestions. Thanks for spending some of your time to help me! > >Amanda don't goes thru all the tapes, it just loaded tape from > > storage element 3 (and not slot 1 as mencioned). > >During amcheck i get an error at the lcd display in front of the > > tape drive stating: SCSI error: Check interface. > > Are both the drive and the scsi card set to match regarding the > parity setings? > Sorry but i don't understand you, what do you mean by parity settings? I've got and adaptec 29160 scsi card (SCSI ID-7) and attached to it an internal SCSI HDD (ID-6) and the external autoloader (ID-5) as you can see in my log. > > Make the above changes I noted, and try a "amtape /config/ reset" > which should load the first tape and record it to the system, and > then do an "amtape /config/ show", which should scan all tapes in > the drive except the cleaning tape presumably in slot 6. > -- The output from amtape /config/ reset is # su bin -c 'amtape caup reset' changer: got exit: 2 str: Can't read STE status amtape: could not reset changer: read STE status could not reset changer: read STE status amtape: pid 2375 finish time Tue Feb 5 16:21:34 2002 TIA. Regards, Manuel
Re: amdump question
On Tue, 5 Feb 2002 at 7:36pm, Mary N Koroleva wrote > I use BSDI 4.2. AMANDA is already here. As an aside, pre-compiled amanda is generally bad. You learn a lot going through the building and installation process. > I have created the user amanda, have added it to group operator. > amanda.conf has copied in /etc/amanda. Then: > > dmps:/etc/amanda | 25 >amdump amanda.conf > amdump: could not find directory /etc/amanda/amanda.conf > dmps:/etc/amanda | 26 > > > Would you be so kind to promt me how to compel amdump work? The amdump man page tells you the proper syntax. You're telling amanda that the configuration name is amanda.conf, and it's looking for an amanda.conf file in the configuration directory. The best ways to get started with amanda are (somewhat in this order): 1) The chapter on amanda at www.backupcentral.com 2) docs/INSTALL in the amanda source distribution 3) FAQ-O-Matic available via www.amanda.org 4) The man pages 5) This list -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: 2.4.2p2 on Irix 6.5.x, user=amanda, group=sys
I had to revert my configuration, I wasn't getting anywhere and I wasn't getting the nightly backups done. I did a make clean, re-ran configure with user root and group sys and rebuild the programs. I reinstalled on the amanda-server/nfs-server and updated /etc/inetd.conf on server and clients to use user root rather than amanda. --- or should I have left it as root all along... Anyway, that server and clients are cleanly passing amcheck tests again. However the amanda-server/nfs-client is now showing these errors [laksha] /usr/local/sbin 42> /usr/local/sbin/amcheck laksha Amanda Tape Server Host Check - ERROR: running as user "root" instead of "amanda" WARNING: holding disk /amanda/work: only 87589220 KB free (9216 KB requested) ERROR: /dev/dlt: not an amanda tape (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /amanda/laksha/curinfo: does not exist NOTE: it will be created on the next run Server check took 26.853 seconds Amanda Backup Client Hosts Check ERROR: running as user "root" instead of "amanda" Client check: 2 hosts checked in 0.279 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) Why is it expecting to run as user "amanda" rather than root ? I did modify /etc/inetd.conf to use root and did HUP the daemon. This is making no sense to me... does it make any to any of you ? thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: 2.4.2p2 on Irix 6.5.x, user=amanda, group=sys
I couldn't figure out where amanda was getting the information as to who it should be run by... I found it finally. /usr/local/etc/amanda/laksha/amanda.conf dumpuser "amanda" I wonder if this wasn't all that was wrong (in reverse) on the Bali server that specified "root" in the config file. If amanda runs tonight I'm going to leave well enough alone for a couple of weeks and work on some other projects. Want to thank you for your help, the amanda community is very strong and always willing to share their expertise. > I had to revert my configuration, I wasn't getting anywhere > and I wasn't getting the nightly backups done. > > I did a make clean, re-ran configure with user root and group sys > and rebuild the programs. > > I reinstalled on the amanda-server/nfs-server and updated > /etc/inetd.conf on server and clients to use user root rather > than amanda. > > --- or should I have left it as root all along... > > Anyway, that server and clients are cleanly passing amcheck > tests again. > > However the amanda-server/nfs-client is now showing these errors > > [laksha] /usr/local/sbin 42> /usr/local/sbin/amcheck laksha > Amanda Tape Server Host Check > - > ERROR: running as user "root" instead of "amanda" > WARNING: holding disk /amanda/work: only 87589220 KB free (9216 KB requested) > ERROR: /dev/dlt: not an amanda tape >(expecting a new tape) > NOTE: skipping tape-writable test > NOTE: info dir /amanda/laksha/curinfo: does not exist > NOTE: it will be created on the next run > Server check took 26.853 seconds > > Amanda Backup Client Hosts Check > > ERROR: running as user "root" instead of "amanda" > Client check: 2 hosts checked in 0.279 seconds, 0 problems found > > (brought to you by Amanda 2.4.2p2) > > Why is it expecting to run as user "amanda" rather than root ? > I did modify /etc/inetd.conf to use root and did HUP the daemon. > > This is making no sense to me... does it make any to any of you ? > > thanks, > > Brian > > --- >Brian R Cuttler [EMAIL PROTECTED] >Computer Systems Support(v) 518 486-1697 >Wadsworth Center(f) 518 473-6384 >NYS Department of HealthHelp Desk 518 473-0773 >
mailing of logreport
hi I'm not running a MTA on the server I'm doing my backups... so I don't receive any reports by mail of my backupsessions... I'm guessing amanda just dumps its logs to localhost:25 to the predefined user in amanda.conf... any way I can make it connect to my mailserver and have it send me the mail through that host? thank you regards Tom -- Tom Van de Wiele System Administrator Eduline Colonel Bourgstraat 105a 1140 Brussel http://www.eduline.be
Re: specifying gnutar, trouble with OSF1 file system
What dumptype specs are you using for your disklists?
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index yes
record yes
exclude list ".amanda_excludes"
strategy nofull
priority low
maxdumps 3
}
The line
program "GNUTAR"
is what points the dumper at gtar
On Mon, Feb 04, 2002 at 07:24:12PM -0800, John Koenig wrote:
> A lot of my issues with the client and dump were resolved by using
> the "advfs.diff" patch located here:
>
>
> Question: Have all these patches been rolled into post-2.4.2p2 builds?
>
> "All the sudden" amanda and vdump and everything is just working like
> a charm on OSF1 (Tru64) v5.1
>
> Though, I am still interested in forcing the use of tar (gnutar 1.13).
>
> Currently, I have this in my configuration however it is calling vdump:
>
> --with-gnutar=/usr/local/gnu/bin/tar
>
> This is after the advfs.diff patch was applied.
>
> Question: How do I force the dump program to use gnutar?
>
> Oh... and the no-record option does perform the backup however with
> this dumptype specified the "backup command" (e.g. dump, vdump, etc)
> will not update its state file (e.g. /etc/dumpdates)
>
>
>
> >Using AMANDA version 2.4.2p2 on OSF/Tru64 v5.1
> >
> >On the client side, amanda is sending an inappropriate parameter to
> >the /sbin/dump
> >
> >
> >=
> >sendsize: running "/sbin/dump 0Esf 1048576 - /net/home1"
> >running /usr/local/amanda-2.4.2p2/libexec/killpgrp
> >dump:
> >dump: Cannot open file-system file home1_dmn#home1_fs
> >dump: Bad file system specification or bad file system. The raw device
> >must
> >dump: be entered when the file system's pathname has not been entered in
> >the
> >dump: fstab file. A bad file system is reported when the the magic number
> >dump: is not found in the super block.
> >=
> >
> >
> >I think i should be using gnutar... As this would likely work-around
> >this issue...
> >
> >At configure time, I have specified:
> >
> > --with-gnutar=/usr/local/gnu/bin/tar
> >
> >Only problem, I have not figured out how to force "the use" of
> >gnutar instead of the distribution's dump program. The client in
> >this case is still calling dump? And, btw, would this be the same
> >way I get amanda to use the "vdump" program? vdump was found at
> >compile-time.
> >
> >Though, when I get the configuration to work, will I again encounter
> >amanda passing a bogus string which is likely obtained from the
> >/etc/fstab file? I am specifying a file system location in the
> >disklist:
> >
> > host /path-to/home1 no-record
> >
> >
> >###
> >
> >I believe it is OK to use no-record for testing right?
> >I read about this somewhere... I think...
> >
> >Would it be weird to run the no-record config and see a
> >file system get dumped to the holding disk and then written to tape?
> >On another client -- which is working somewhat -- I saw this behavior...
> >What does no-record mean exactly?
> >
> >
> >
> >thanks!!
>
--
-ashley
One of these days I'm going to completely organize my life.
Problems using "tapetype HARD-DISK"
Hi I have some minor problem with amanda-2.4.3b1. I use the tapetype HARD-DISK to make backup directly to disk. The diskarea I'm using is mounted from another server. I set up the system almost a month ago, and everything worked fine. Then I rebooted the system, and missed to remount the diskarea used for backup, and ofcourse the backup failed. I then remounted the disk, and the backup started to work. My problem is that everyday I rececive from amcheck the message included below, even thou the disk is mounted. Amdump on the other hand has no problem performing the backup. Another strange thing is that I only receive the error message the first time I run amcheck every day. Does anyone have a clue waths wrong. Best regards Anders Rosendal Bostream - Amanda Tape Server Host Check - Holding disk /var/space: 9026668 KB disk space available, that's plenty amcheck-server: slot 5: chg-multi: slot is empty amcheck-server: slot 6: chg-multi: slot is empty amcheck-server: slot 7: chg-multi: slot is empty amcheck-server: slot 8: date 20020130 label BostreamSet108 (active tape) amcheck-server: slot 1: date 20020131 label BostreamSet101 (active tape) amcheck-server: slot 2: date 20020201 label BostreamSet102 (active tape) amcheck-server: slot 3: date 20020202 label BostreamSet103 (active tape) amcheck-server: slot 4: date 20020203 label BostreamSet104 (active tape) ERROR: label BostreamSet106 or new tape not found in rack (expecting tape BostreamSet106 or a new tape) NOTE: skipping tape-writable test Server check took 0.937 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.459 seconds, 0 problems found (brought to you by Amanda 2.4.3b1) -- This EMail Was brought to you by WebMAIL A Netwin Web Based EMail Client http://netwinsite.com/webmail/
Skipping a tape
Is there any way to skip a tape? My server has crashed while doing a partition for 2 nights running, and tonight's backup is supposed to overwrite my last level 0 of this partition. Regards, --Ruth Anne
Re: mailing of logreport
Yes, use ssmtp, a send-only replacement for sendmail. P. On 02/05/02, [EMAIL PROTECTED] wrote: > >hi > >I'm not running a MTA on the server I'm doing my backups... so >I don't receive any reports by mail of my backupsessions... I'm >guessing amanda just dumps its logs to localhost:25 to the predefined >user in amanda.conf... > >any way I can make it connect to my mailserver and have it send me the >mail through that host? > >thank you > >regards > >Tom > -- > Tom Van de Wiele > System Administrator > > Eduline > Colonel Bourgstraat 105a > 1140 Brussel > [1]http://www.eduline.be > > References > >1. http://www.eduline.be/ -- Philip J. Hollenback [EMAIL PROTECTED] http://www.hollenback.net
RE: Skipping a tape
You have a few choices: 1. Add a new tape to the rotation. It will be used before any other. 2. You can prevent a tape from being used for backups with a command like this: amanda@tape$ amadmin YourConfig no-reuse YourGoodTape (See `man amadmin` for more info.) 3. Anything else I might have forgotten. (Like AMANDA remembering that that's the last level 0 and declining to overwrite the tape.) You should probably also be concerned about those crashes, but that's a separate topic. Good Luck. Paul > -Original Message- > From: Ruth Anne [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 05, 2002 2:23 PM > To: [EMAIL PROTECTED] > Subject: Skipping a tape > > > Is there any way to skip a tape? My server has crashed while doing a > partition for 2 nights running, and tonight's backup is supposed to > overwrite my last level 0 of this partition. > > Regards, > --Ruth Anne >
Incrementals with tar
This is probably a super dumb question but ... I have just noticed ( never really looked very hard before ), that amanda doesn't seem to be doing incrementals with tar. A Level 0 and the subsequent Level 1 dumps are the same size ( give or take a few bytes ). How does one make tar do incrementals when used with amanda. There are /etc/amandates files that are owned by amanda but they never appear to be written to. I am using the comp-root-tar and comp-user-tar dumptypes. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Glen and Rosanne Eustace, GodZone Internet Services, a division of AGRE Enterprises Ltd., P.O. Box 8020, Palmerston North, New Zealand 5301 Ph/Fax: +64 6 357 8168, Mob: +64 21 424 015
Re: mailing of logreport
On Tue, Feb 05, 2002 at 07:43:19PM +0100, [EMAIL PROTECTED] wrote: > hi > > I'm not running a MTA on the server I'm doing my backups... so I don't > receive any reports by mail of my backupsessions... I'm guessing amanda > just dumps its logs to localhost:25 to the predefined user in > amanda.conf... > > any way I can make it connect to my mailserver and have it send me the > mail through that host? > Amanda checks for mailx when configure is run. You can write a small script as mailx substitute, depending on your network configuration. Easiest way would be calling mailx over ssh. IIRC there is also a Perl Module which speaks SMTP. Ciao Dietmar -- Alles Gute / best wishes Dietmar GoldbeckE-Mail: [EMAIL PROTECTED] Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.
Re: Compression on Exb 8500
Glen Eustace wrote:
>
> On Tue, 05 Feb 2002 18:35, you wrote:
> > Try: "man stinit" and after you've created the proper device nodes
> > (search the archive for an earlier post of mine), add "post-install st
> > /sbin/stinit" to /etc/conf.modules. You already have the proper density
> > codes, so it shouldn't take more than a few minutes to get it all set
> > up.
>
> Thanks for the info, I read your previous letter and am still a bit confussed.
>
> I only want the single mode on the drive, so didn't put a mode line in the
> stinit.def file, stinit complains it is missing.
>
> If I add a mode1, then it complains there is not device /dev/nst1, which is
> true it is /dev/nst0.
>
> It doesn't like mode0, and clues ?
Hmmm, if I said mode0-3, my bad. Must be mode1-4, but you don't need
all of them. You do, however, want to be certain to identify the drive
to stinit, using the "manufacturer=" and "model=" (which you get from
the kernel boot messages in /var/log/messages). For instance, the
customized part of my stinit.def file for my AIT-1 drive:
manufacturer=SEAGATE model="AIT" {
can-bsr can-partitions scsi2logical auto-lock
mode1 blocksize=0 density=0x30 compression=0# native, no compression
mode2 blocksize=0 density=0x30 compression=1# native, w/ compression
}
(note that you have your own density codes, and probably should not use
"compression=" for the Exabyte drives). Also, after editing
/etc/stinit.def, do "rmmod st", then "modprobe st". Oh, yeah, the
device files:
$ ls -l /dev | grep ' 9, ' | grep st0
crw-rw-rw- 1 root disk 9, 128 May 5 1998 nst0
crw-rw-rw- 1 root root 9, 160 Dec 11 1999 nst0c
crw-rw-rw- 1 root disk 9, 0 May 5 1998 st0
crw-rw-rw- 1 root root 9, 32 Dec 11 1999 st0c
stinit is smart enough to find them, no matter what you've called them,
but you must have both a rewind and non-rewind device for each mode you
specify. If, in fact, you have more than 1 tape drive, and the drive
you're messing with is actually st1, increment all the device minor
numbers by 1 (1, 33, 129, 161).
Let me know if any of that helps
(Copied back to the list, as the problem continues to crop up for
folks.)
Marty
--
Marty Shannon, RHCE, Independent Computing Consultant
mailto:[EMAIL PROTECTED]
RE: Skipping a tape
On Tue, 5 Feb 2002, Bort, Paul wrote: > You have a few choices: > > 1. Add a new tape to the rotation. It will be used before any other. > > 2. You can prevent a tape from being used for backups with a command like > this: > > amanda@tape$ amadmin YourConfig no-reuse YourGoodTape OK, But won't this remove any logs, indexes, etc? I don't really want to remove this tape for good, just for right now. As for the crashes, yeah, we're working on it. Coming in before the sun comes up to reboot servers is not my idea of fun. --Ruth Anne
Re: Incrementals with tar
On Wed, Feb 06, 2002 at 09:48:00AM +1300, Glen Eustace wrote: > This is probably a super dumb question but ... > > I have just noticed ( never really looked very hard before ), that amanda > doesn't seem to be doing incrementals with tar. A Level 0 and the subsequent > Level 1 dumps are the same size ( give or take a few bytes ). How does one > make tar do incrementals when used with amanda. > > There are /etc/amandates files that are owned by amanda but they never appear > to be written to. I am using the comp-root-tar and comp-user-tar dumptypes. > -- Actually incrementals are working fine for me. GNUtar records inode numbers in a listed incremental file. Could you please run tar --version and check if you have a runtar debug file (usually under /tmp/amanda) What OS and filesystem are you using? IIRC GNUtar checks inode numbers and this fails for some filesystems without UNIX inodes (e.g. mounting Novell drives, or NTFS filesystems under Linux). The other possible reason is running GNUtar with --atime-preserve. You can configure Amanda to use --atime-preserve, but this is only useful if you can live with large incrementals. Ciao Dietmar -- Alles Gute / best wishes Dietmar GoldbeckE-Mail: [EMAIL PROTECTED] Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.
Re: Incrementals with tar
On Wed, 06 Feb 2002 10:11, Dietmar Goldbeck wrote: > tar --version 1.13.17 > and check if you have a runtar debug file (usually under /tmp/amanda) gtar: version 2.4.2p2 running: /bin/gtar: gtar --create --file - --directory / --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/agree-10__1.new --sparse --ignore-failed-read --totals . > What OS and filesystem are you using? RH6.2 on SPARC RH7.1 on i386 RH7.2 on i386 -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Glen and Rosanne Eustace, GodZone Internet Services, a division of AGRE Enterprises Ltd., P.O. Box 8020, Palmerston North, New Zealand 5301 Ph/Fax: +64 6 357 8168, Mob: +64 21 424 015
first amrecover attempt problems
Well, I have 5 systems set up to backup to the backup server
(datadev). I have run a successful (I think) amdump. amverify seems to
think all is well with this tape. However, I haven't figured out how to
actually recover anything yet. My amrecover attempt is shown below. I
did some searching in the faq-o-matic and saw some references to looking
at the /tmp/amanda/amidxtaped debug file, which is not getting created
(part of my problem, I would guess).
-
{datadev:root}# amrecover -C Daily
AMRECOVER Version 2.4.2p2. Contacting server on datadev ...
amrecover: Unexpected server end of file
-
amverify:
Tapes: DailySet101
No errors found!
amverify Daily
Tue Feb 5 15:52:58 EST 2002
Using device /dev/rmt/0bn
Volume DailySet101, Date 20020205
Checked datadev._export_home.20020205.0
Skipped prodmedia._home.20020205.0 (** Cannot do /bin/gtar dumps)
Checked lincvs._var.20020205.0
Skipped prodmedia._media.20020205.0 (** Cannot do /bin/gtar dumps)
Checked prodhtml._export_home.20020205.0
Checked mail._home.20020205.0
Checked lincvs._home.20020205.0
End-of-Tape detected.
--
The only files showing up in /tmp/amanda are amandad and amrecover debug
files.
{datadev:root}# cat amandad.20020205164043.debug
amandad: debug 1 pid 4072 ruid 104 euid 104 start time Tue Feb 5
16:40:43 2002
amandad: version 2.4.2p2
amandad: build: VERSION="Amanda-2.4.2p2"
amandad:BUILT_DATE="Wed Jan 30 14:27:48 EST 2002"
amandad:BUILT_MACH="SunOS datadev 5.8 Generic_108528-03 sun4u
sparc SUNW,Ultra-250"
amandad:CC="gcc"
amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man"
amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad:CONFIG_DIR="/usr/local/etc/amanda"
DEV_PREFIX="/dev/dsk/"
amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump"
amandad:RESTORE="/usr/sbin/ufsrestore"
GNUTAR="/usr/local/bin/tar"
amandad:COMPRESS_PATH="/usr/bin/gzip"
amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/ucb/Mail"
amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
amandad: defs: DEFAULT_SERVER="datadev" DEFAULT_CONFIG="DailySet1"
amandad:DEFAULT_TAPE_SERVER="datadev"
amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/0bn" HAVE_MMAP
HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
amandad: dgram_recv: timeout after 30 seconds
amandad: error receiving message: timeout
error receiving message: timeout
amandad: pid 4072 finish time Tue Feb 5 16:41:13 2002
{datadev:root}# cat amrecover.20020205164043.debug
amrecover: debug 1 pid 4071 ruid 0 euid 0 start time Tue Feb 5 16:40:43
2002
amrecover: stream_client: connected to 63.168.35.62.10082
amrecover: stream_client: our side is 0.0.0.0.834
Can anyone point me in the right direction?
Thanks,
Gene
--
Gene Matthews
Matthews Midrange Consulting, Inc.
(678) 923-8327
(877) 882-6291 (toll free)
http://mmc-inc.com
RE: Skipping a tape
The only thing that no-reuse changes is tapelist. No logs or indexes are deleted, and you can still restore from the tape. It just won't be written to. NB: I don't remember if this causes AMANDA to prompt for a new tape if taking the tape out of rotation takes you below tapecycle. > -Original Message- > From: Ruth Anne [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 05, 2002 4:28 PM > To: [EMAIL PROTECTED] > Subject: RE: Skipping a tape > > > On Tue, 5 Feb 2002, Bort, Paul wrote: > > > You have a few choices: > > > > 1. Add a new tape to the rotation. It will be used before any other. > > > > 2. You can prevent a tape from being used for backups with > a command like > > this: > > > > amanda@tape$ amadmin YourConfig no-reuse YourGoodTape > > OK, But won't this remove any logs, indexes, etc? I don't really want > to remove this tape for good, just for right now. > > As for the crashes, yeah, we're working on it. Coming in before the > sun comes up to reboot servers is not my idea of fun. > > --Ruth Anne > >
RE: Skipping a tape
On Tue, 5 Feb 2002, Bort, Paul wrote: > The only thing that no-reuse changes is tapelist. No logs or indexes are > deleted, and you can still restore from the tape. It just won't be written > to. My most humble apologies. Yes, no-reuse will do what I want. > NB: I don't remember if this causes AMANDA to prompt for a new tape if > taking the tape out of rotation takes you below tapecycle. I guess I will find out. Thanks to all, --Ruth Anne
DLT2700xt Changer conf
I'm new to amanda and dont see anything specific to this drive/changer. I do see some generic DLT configurations for DLT drives, and see something that should work. However, I have no clue how to get this working with the 7 tape changer unit. Any help and any of the "glue scripts" that people are using would be appreciated. Any and all info appreciated, TIA. -- John Gonzalez, Tularosa Communications | (505) 439-0200 work JG6416, ASN 11711, [EMAIL PROTECTED] | (505) 443-1228 fax http://www.tularosa.net
Re: Problems with changer device
On Tuesday 05 February 2002 11:44 am, Manuel Monteiro wrote: >I've done all of your suggestions. Thanks for spending some of your > time to help me! > >> >Amanda don't goes thru all the tapes, it just loaded tape from >> > storage element 3 (and not slot 1 as mencioned). >> >During amcheck i get an error at the lcd display in front of the >> > tape drive stating: SCSI error: Check interface. >> >> Are both the drive and the scsi card set to match regarding the >> parity setings? > >Sorry but i don't understand you, what do you mean by parity settings? I'd assume there is a dip switch setting on the drive that controls whether or not the scsi interface data bus uses a parity bit to detect errors that would otherwise be missed, so using the parity bit is highly recomended. Set the drives switches or jumpers to turn it on, then reboot the computer and when it says to hit ctrl+a to see the cards bios settings, do so and verify that the card is also set to use the parity bit AT THAT DEVICE ADDRESS. >I've got and adaptec 29160 scsi card (SCSI ID-7) and attached to it an >internal SCSI HDD (ID-6) and the external autoloader (ID-5) as you can > see in my log. Humm, you might want to set the tape down to ID=4 in case the robot needs 5, some use the next address above the drive to access the robot. >> Make the above changes I noted, and try a "amtape /config/ reset" >> which should load the first tape and record it to the system, and >> then do an "amtape /config/ show", which should scan all tapes in >> the drive except the cleaning tape presumably in slot 6. >> -- > >The output from amtape /config/ reset is ># su bin -c 'amtape caup reset' >changer: got exit: 2 str: Can't read STE status >amtape: could not reset changer: read STE status >could not reset changer: read STE status >amtape: pid 2375 finish time Tue Feb 5 16:21:34 2002 Mmm, whats the permissions and owner:group of /dev/nst0? Somethings fubar. Can you do a "mt -f /dev/nst0 status" and such as user amanda? If you can't, then those perms need adjusting. Cheers, Gene
2 questions::multiple simultaneous instances && DIR vs. FS
hello all, I know these questions have been asked before, but I can't seem to be able to dig them up in my archives. First: I have Amanda v2.4.2p2 on Linux RHv6.2 w/two 8 Tape DLT autoloaders installed on two seperate SCSI Buses/Adapters Q1: Is it possible to run two simultaneous instances of Amanda (amdump) at one time? I have two tape devices each running a different configuration. I'd like to run them both starting at midnight every night. Each one writes to a different tape device and uses a different holding disk. I remember someone posting once that they got a message like: "amdump is already running" Q2: Where can I read up on some info on backing up Directories vs. Filesystems? I remember reading that I have to use GNU-Tar to do this (no problem), however, I'd like to read up on a thread or web document if anyone knows where i can get details on this, please let me know. Thanks in advance everyone. Keep on Amanda'ing. Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799 <[EMAIL PROTECTED]>
Re: Holding disk
Thank you for the pointers...
> >I'm having the same problem here, also running Amanda 2.4.2p2.
>
> Actually, you're having a different problem. But be that as it may ...
>
> >ERROR: /export/dumps/amanda: rewinding tape: Inappropriate ioctl for
device
> > (expecting a new tape)
> >...
> >I had set tapedev "/export/dumps/amanda" in amanda.conf with the
(obviously
> >mistaken) understanding that Amanda would just dump to that dir. ...
>
> The 2.4.2p2 version of Amanda only writes to tapes. If you want to store
> your images in a disk area, you need what's called the "tapeio" feature.
> You can get that either via the amanda-242-tapeio CVS branch (see the
> FAQ for details on how to check out and build from CVS), or it's also
> part of 2.4.3, which is now in beta.
>
> Are you planning on leaving the images in that disk area, i.e. treating it
> like a pseudo tape, or are you planning on flushing them to tape later on?
I plan to buy a tape setup, but the kind I want wont be available in Japan
until March, so I am trying to test the system by dumping to hard disk for
the time being. It will also make the boss feel better to be able to see
backed up data physically on another machine. :-)
> If you plan to eventually flush them, then you want to do things
> differently (and 2.4.2p2 support this). Just set "reserve" to zero in
> the holding disk declaration so Amanda will go ahead and do full dumps,
> then set tapedev to something like "/no/such/device". The tape writing
> portion of Amanda will fail, but the dumping to the holding disk part
> will work. Then change tapedev and run amflush as needed (and set
> tapedev back after the amflush).
>
> In fact, the above might do what you want even without the flushing.
> It depends on what the goal is.
I set tapedev to literally "/no/such/device" :-)
and set reserve to 0.
I then ran:
# su amanda -c "amcleanup daily"
# su amanda -c "amcheck daily"
# su amanda -c "amdump daily"
I then checked the dump directory to see what happened:
# ls -l /export/dumps/amanda/
total 1
drwx-- 2 amanda backup 512 Feb 5 11:21 20020205/
and saw that a new directory with today's date has been created.
I then looked in that directory for backed up data, but:
# ls -al /export/dumps/amanda/20020205/
total 2
drwx-- 2 amanda backup 512 Feb 5 11:21 ./
drwxrwxr-x 3 1 backup 512 Feb 5 11:21 ../
hmm... nothing...
Any idea what I'm missing?
The error mail I get from Amanda follows.
Thanks,
Shawn
*** A TAPE ERROR OCCURRED: [no tape online].
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.
FAILURE AND STRANGE DUMP SUMMARY:
mydom.co. /usr lev 0 FAILED [disk /usr offline on mydom.co.jp?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk mydom.co.jp:/usr.
driver: WARNING: got empty schedule from planner
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
mydom.co /usr0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
