Re: Debian packages for Amanda
On Fri, Sep 08, 2006 at 03:58:11PM -0500, Phil Howard wrote: > On Fri, Sep 08, 2006 at 11:01:10AM +0100, Dave Ewart wrote: > > | On a Debian system, the backup user is a member of the appropriate > | system groups to allow backups to function, i.e. a member of 'disk' > | > | For what it's worth, on a Debian Stable system, I've found that the > | AMANDA packages Just Work very nicely, especially on the clients, since > | there is basically no configuration required. > > Wouldn't I need to at least tell it where the backup server is? > The server initiates the backup session, so the client does not need server knowledge for this. For recovery a default server is compiled in, but that can be overridden with command line arguments. The system I'm typing this on was my backup server, and of course a client of itself. I have now moved the amanda service to a different computer. When I did, I made no changes to the current system. It is just responds as a client when the new server contacts it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: NFS strangeness
On Fri, Sep 08, 2006 at 04:51:08PM -0700, Steffan Vigano wrote:
> Frank-
>
> Thanks so much for your reply... that did the trick! I knew it had to
> be something simple... I'll be adding that to the Amanda Wiki for
> future users.
>
> Thanks again
> -Steffan
>
> Frank Smith wrote:
> >Dump works on devices, not filesystems, so it won't work on an NFS mount.
> >Tar works on filesystems, but Amanda calls it with the option to not
> >cross filesystem boundaries, so a backup of /nfs in your case will
> >just give you the local files in /nfs and not mounts under /nfs.
> > If you are trying to backup /nfs/remotedir, add /nfs/remotedir
> >to your disklist and it will do what you want. I backup our legacy
> >NetApps via an NFS mount this way and it works fine.
> >
If you have several nfs mounts under /nfs and want them all backed
up as a single DLE, you could do a set of "include" directives
in the dumptype.
host /nfs NFSDIRS {
user-tar
include file"./rmtdir1"
include file append "./rmtdir2" "./rmtdir3"
include file append "./rmtdir4"
}
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
got my L9!
Ok I've received the L9 array now (picked up yesterday). It uses diff SCSI and that's no problem since I've got some Sbus diff SCSI cards to go into the Sparc 20 system which I plan to use as the new tape host manager system. Slighty off topic Q - Does diff SCSI require different cables to regular wide SCSI cables or can regular wide SCSI cables be used without a problem? Are there any gotchas when configuring Amanda to use an L9 that I should be aware of? I've got a bundle of new DLT-IV tapes here already. Should a cleaning tape be put in any particular slot of the tape holder or is it an artitrary config setting to specify which slot it's in? Regards, Craig. -- Post by Craig Dewick (tm). Web @ "http://lios.apana.org.au/~cdewick";. Email 2 "[EMAIL PROTECTED]". SunShack @ "http://www.sunshack.org"; Forums @ "http://www.sunshack.org/phpBB2";. Also Galleries, tech archive, etc. Sun Microsystems webring at "http://n.webring.com/hub?ring=sunmicrosystemsu";.
Re: NFS strangeness
Frank- Thanks so much for your reply... that did the trick! I knew it had to be something simple... I'll be adding that to the Amanda Wiki for future users. Thanks again -Steffan Frank Smith wrote: Dump works on devices, not filesystems, so it won't work on an NFS mount. Tar works on filesystems, but Amanda calls it with the option to not cross filesystem boundaries, so a backup of /nfs in your case will just give you the local files in /nfs and not mounts under /nfs. If you are trying to backup /nfs/remotedir, add /nfs/remotedir to your disklist and it will do what you want. I backup our legacy NetApps via an NFS mount this way and it works fine. Frank
NFS strangeness
Hello all, Just wondering if anyone might be able to shed some light on my problem... we recently got a SnapServer on our network and would like to use our existing Amanda install to back it up via NFS but so far have been unsuccessful. - FreeBSD 4.7-RELEASE - Amanda v2.4.4b1 - GNU tar v1.13.25 I have tried mounting the NFS shares onto the main Amanda backup host as well as other servers being backed up via Amanda. I can manually, from the command line, read/write and tar up the attached NFS shares without issue, both as root and user Amanda. Yet when Amanda runs through it's backup process, nothing gets backed up from that share. I've checked the logs, and there are no errors showing. Running an amrecover shows the root directory that the share is mounted on, but there are no files or directories within to recover. I've tried changing the dump type in amanda.conf to both DUMP and GNUTAR for the partition in question. No change. I've also tried an NFS mount from an alternate FreeBSD machine to rule out the SnapServer. Same issue. Here are the runtar and sendsize debug files: runtar: debug 1 pid 49585 ruid 1002 euid 0: start at Fri Sep 8 13:41:26 2006 gtar: version 2.4.4b1 running: /usr/bin/tar: gtar --create --file - --directory /nfs --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/phatb.boothcreek.net_dev_aacd0s2h_1.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendbackup._dev_aacd0s2h.20060908134126.exclude . sendsize: debug 1 pid 50252 ruid 1002 euid 1002: start at Fri Sep 8 13:59:38 2006 sendsize: version 2.4.4b1 sendsize[50252]: time 0.005: waiting for any estimate child sendsize[50257]: time 0.005: calculating for amname '/dev/aacd0s2h', dirname '/nfs', spindle -1 sendsize[50257]: time 0.006: getting size via gnutar for /dev/aacd0s2h level 0 sendsize[50257]: time 0.008: spawning /usr/local/libexec/runtar in pipeline sendsize[50257]: argument list: /usr/bin/tar --create --file /dev/null --directory /nfs --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/phatb.boothcreek.net_dev_aacd0s2h_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._dev_aacd0s2h.20060908135938.exclude . sendsize[50257]: time 0.052: Total bytes written: 102400 (100kB, 3.1MB/s) sendsize[50257]: time 0.053: . sendsize[50257]: estimate time for /dev/aacd0s2h level 0: 0.045 sendsize[50257]: estimate size for /dev/aacd0s2h level 0: 100 KB sendsize[50257]: time 0.053: waiting for /usr/bin/tar "/dev/aacd0s2h" child sendsize[50257]: time 0.053: after /usr/bin/tar "/dev/aacd0s2h" wait sendsize[50257]: time 0.054: done with amname '/dev/aacd0s2h', dirname '/nfs', spindle -1 sendsize[50252]: time 0.054: child 50257 terminated normally sendsize: time 0.054: pid 50252 finish time Fri Sep 8 13:59:38 2006 as you can see... it only sees the 100k of real test files that I have in the /nfs directory, and not the actual mounts that live under /nfs. ??? Am I missing something easy? Anything special I need to add to 'amanda.conf'? or 'disklist'? I do just mount the NFS share to an existing entry in my disklist, right? Rather then adding the NFS mount as a separate entry? I've check all the permissions on the share (no_root_squash, etc)... I'm at a loss. Digging around the net, I've been unable to find any clear docs on what the proper setup might need to look like. Anyone have any more suggestions about next steps? Thanks a bunch, -Steffan
Re: using disk instead of tape
On Fri, Sep 08, 2006 at 02:46:48PM +0200, Geert Uytterhoeven wrote: | On Fri, 8 Sep 2006, Ronan KERYELL wrote: | > Third, what about bad blocks on disk? How to skip them in a raw partition | > if you do not have state-of-the-art disks that do block remapping for you | > in your back-yard (such as SCSI)? Often FS do these tricks for you on | > IDE disks for example. | | These days IDE does that too. | But if there are too many of them, you loose (same for SCSI). A few years ago I was doing a forensics security review for a client that had data that needed to be erased VERY reliably. The determination was that because even IDE disks did remapping internally, it would be possible for previously written data to be inaccessible to a program writing random data over the whole disk several times. The only way to ensure that this confidential data was destroyed was to grind the disk to dust, or at least do so to the platters. But modern IDE disks perhaps are indeed doing this. I haven't had a bad sector on such a disk in years. -- - | Phil Howard KA9WGN | http://linuxhomepage.com/ http://ham.org/ | | (first name) at ipal.net | http://phil.ipal.org/ http://ka9wgn.ham.org/ | -
Re: Debian packages for Amanda
On Fri, Sep 08, 2006 at 11:01:10AM +0100, Dave Ewart wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | On Friday, 08.09.2006 at 01:28 -0500, Phil Howard wrote: | | > These packages configure the user to run Amanda as "backup". But it | > seems the "backup" user also does other things. Does anyone see any | > possible conflict in this? | | I'd say "may be used for other things", rather than "also does other | things", really. | | To be honest, a user called backup makes more sense than a user called | 'amanda' - we used to have a staff member called Amanda who existed | prior to an AMANDA installation and things got ... messy. I can imagine. | On a Debian system, the backup user is a member of the appropriate | system groups to allow backups to function, i.e. a member of 'disk' | | For what it's worth, on a Debian Stable system, I've found that the | AMANDA packages Just Work very nicely, especially on the clients, since | there is basically no configuration required. Wouldn't I need to at least tell it where the backup server is? | Feel free to ask further related questions, because I've been using | AMANDA on Debian systems for many years... I'm also trying to document the steps. This server may not actually be used, but rather, someone with less experience than I (which is not very much with either Amanda or Debian) may be re-installing everything by my instructions. Amanda is very flexible, so I don't know how specific I can be if they change things. -- - | Phil Howard KA9WGN | http://linuxhomepage.com/ http://ham.org/ | | (first name) at ipal.net | http://phil.ipal.org/ http://ka9wgn.ham.org/ | -
Re: NFS strangeness
Steffan Vigano wrote: > Hello all, > > Just wondering if anyone might be able to shed some light on my > problem... we recently got a SnapServer on our network and would like to > use our existing Amanda install to back it up via NFS but so far have > been unsuccessful. > > - FreeBSD 4.7-RELEASE > - Amanda v2.4.4b1 > - GNU tar v1.13.25 > > I have tried mounting the NFS shares onto the main Amanda backup host as > well as other servers being backed up via Amanda. I can manually, from > the command line, read/write and tar up the attached NFS shares without > issue, both as root and user Amanda. Yet when Amanda runs through it's > backup process, nothing gets backed up from that share. I've checked > the logs, and there are no errors showing. Running an amrecover shows > the root directory that the share is mounted on, but there are no files > or directories within to recover. I've tried changing the dump type in > amanda.conf to both DUMP and GNUTAR for the partition in question. No > change. I've also tried an NFS mount from an alternate FreeBSD machine > to rule out the SnapServer. Same issue. > > Here are the runtar and sendsize debug files: > >> runtar: debug 1 pid 49585 ruid 1002 euid 0: start at Fri Sep 8 >> 13:41:26 2006 >> gtar: version 2.4.4b1 >> running: /usr/bin/tar: gtar --create --file - --directory /nfs >> --one-file-system --listed-incremental >> /usr/local/var/amanda/gnutar-lists/phatb.boothcreek.net_dev_aacd0s2h_1.new >> --sparse --ignore-failed-read --totals --exclude-from >> /tmp/amanda/sendbackup._dev_aacd0s2h.20060908134126.exclude . > >> sendsize: debug 1 pid 50252 ruid 1002 euid 1002: start at Fri Sep 8 >> 13:59:38 2006 >> sendsize: version 2.4.4b1 >> sendsize[50252]: time 0.005: waiting for any estimate child >> sendsize[50257]: time 0.005: calculating for amname '/dev/aacd0s2h', >> dirname '/nfs', spindle -1 >> sendsize[50257]: time 0.006: getting size via gnutar for /dev/aacd0s2h >> level 0 >> sendsize[50257]: time 0.008: spawning /usr/local/libexec/runtar in >> pipeline >> sendsize[50257]: argument list: /usr/bin/tar --create --file /dev/null >> --directory /nfs --one-file-system --listed-incremental >> /usr/local/var/amanda/gnutar-lists/phatb.boothcreek.net_dev_aacd0s2h_0.new >> --sparse --ignore-failed-read --totals --exclude-from >> /tmp/amanda/sendsize._dev_aacd0s2h.20060908135938.exclude . >> sendsize[50257]: time 0.052: Total bytes written: 102400 (100kB, 3.1MB/s) >> sendsize[50257]: time 0.053: . >> sendsize[50257]: estimate time for /dev/aacd0s2h level 0: 0.045 >> sendsize[50257]: estimate size for /dev/aacd0s2h level 0: 100 KB >> sendsize[50257]: time 0.053: waiting for /usr/bin/tar "/dev/aacd0s2h" >> child >> sendsize[50257]: time 0.053: after /usr/bin/tar "/dev/aacd0s2h" wait >> sendsize[50257]: time 0.054: done with amname '/dev/aacd0s2h', dirname >> '/nfs', spindle -1 >> sendsize[50252]: time 0.054: child 50257 terminated normally >> sendsize: time 0.054: pid 50252 finish time Fri Sep 8 13:59:38 2006 > > as you can see... it only sees the 100k of real test files that I have > in the /nfs directory, and not the actual mounts that live under /nfs. ??? > > Am I missing something easy? Anything special I need to add to > 'amanda.conf'? or 'disklist'? I do just mount the NFS share to an > existing entry in my disklist, right? Rather then adding the NFS mount > as a separate entry? Dump works on devices, not filesystems, so it won't work on an NFS mount. Tar works on filesystems, but Amanda calls it with the option to not cross filesystem boundaries, so a backup of /nfs in your case will just give you the local files in /nfs and not mounts under /nfs. If you are trying to backup /nfs/remotedir, add /nfs/remotedir to your disklist and it will do what you want. I backup our legacy NetApps via an NFS mount this way and it works fine. Frank > > I've check all the permissions on the share (no_root_squash, etc)... > I'm at a loss. Digging around the net, I've been unable to find any > clear docs on what the proper setup might need to look like. Anyone > have any more suggestions about next steps? > > Thanks a bunch, > -Steffan -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda 2.4, not using work area
Frank, et al, FYI - amanda.conf choked on "reserve" apparently not a legal parameter in v2.4. While upgrading would help there should be a 2.4 solution, eh ? good weekend all. Brian On Fri, Sep 08, 2006 at 03:02:44PM -0400, Brian Cuttler wrote: > > Frank, > > Good suggestion, it might be that something as old as 2.4 reserved > a lot of space. I was over this issue recently with another (more > recent system) and had thought that "reserve" only came into play > in degraded mode - when the tape drive was unavailable. However it > might be that in 2.4 the rules where somewhat different. > > I have set reserve to be 15, will see how amanda progresses in > the next run. > > Will post results either way. > > thank you, > > Brian > > On Fri, Sep 08, 2006 at 01:46:34PM -0500, Frank Smith wrote: > > Brian Cuttler wrote: > > > Hello amanda users, > > > > > > I'm running an old version of amanda 2.4 on a Solaris 9 system > > > with a Solaris 8 client. > > > > > > Its come to my attention that the two larger client partitions > > > are not being moved through the work area but are being written > > > directly to tape. > > > > > > The work area is a 70 Gig partition, the client DLEs are on 35 Gig > > > partitions. I'd expect to use the work area even if they did so > > > sequentially, the partitions however are only about 70% occupied, > > > aprox 24 Gig each, so ideally I'd have liked to have seen some > > > parallelism. > > > > > > From the daily reports I see that the smaller client partitions > > > on both the Solaris 8 and 9 machine (the amanda server does have > > > itself as a client) do utilize the work area. > > > > > > I do not know what is preventing the work area from being used. > > > I would add more work area if I thought it would help, but I don't > > > see anything screaming "work area capacity" issue. > > > > If the direct-to-tape DLEs are level 0s, look at the 'reserve' option. > > It tells amanda what percentage of your holdingdisk to save for use by > > incrementals, so in case of tape problems you can run longer because > > you don't fill it up with fulls. I don't remember what it defaults to > > if not specified, but I think it is most of the space. > > > > > > > > Here is a question, I assume chunksize appeared around the same > > > time (if not actually with) the ability to split a single DLE > > > across multiple work areas. I see it back in the docs into '98 > > > or more but I'm not sure when it first appeared. Is there a list > > > of what version which features where added, other than the changelog > > > installation file ? > > > > Chunksize was a workaround for writing dumps to disk larger than the > > system's max file size (which was 2GB on many machines at the time). > > I think support for multiple holding disks was added later. > > > > Frank > > > > > > > > Anyway it doesn't look like a work area capacity issue. What, other > > > than adding chunksize to my amanda.conf and perhaps adding additional > > > work area can I do to investigate this issue. > > > > > > There does not seem to be any output in the /tmp/amanda/* files > > > showing which DLEs will be work area and which will not, where else > > > can I look for an explaintation/solution to this issue ? > > > > > > thank you, > > > > > > 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 > > > > > > > > > -- > > Frank Smith [EMAIL PROTECTED] > > Sr. Systems Administrator Voice: 512-374-4673 > > Hoover's Online Fax: 512-374-4501 > --- >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 > --- 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: amtapetype problems
On Fri, Sep 08, 2006 at 03:45:57PM -0400, Joshua Baker-LePain enlightened us: > Please keep responses on the list. Also, top posting and not trimming > posts are generally frowned upon. > > >Thanks for pointing that out. > > > >I've had so many problems with this, I just assumed this to be another > >strange error and did not even notice the medium not present > >message duh. > > > >Also, I think load is not the right word to use since mt cannot load a > >tape, it must be done manually or by a robot. > > Precisely. Use 'mtx' to have the robot load the tape. After the tape > drive goes through its (automatic) loading cycle, the tape will be ready > for use. 'mt status' can confirm that. Furthermore, at least with my > Overland robot, 'mtx unload' automatically does a 'mt offline' to eject > the tape. So running 'mt' manually is pretty rare, really. Just for the record, I use mt's load command to pull a tape in that has been previously ejected, but not removed from the drive. After I dump to tape, I eject the tape, but don't physically remove it from the drive. That way if I need to restore a file from last week, it's as easy as mt -f /dev/nst0 load amrecover I eject the tape so that when amdump runs each night, it doesn't read the headers over and over, shortening the life of the tape (since I spool to holding disk all week and flush to tape once a week) and forces me to run another command before I can have a typo erase all of last weeks dumps :-) Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: amtapetype problems
On Fri, 8 Sep 2006 at 2:39pm, Nick Jones wrote Please keep responses on the list. Also, top posting and not trimming your posts are generally frowned upon. Thanks for pointing that out. I've had so many problems with this, I just assumed this to be another strange error and did not even notice the medium not present message duh. Also, I think load is not the right word to use since mt cannot load a tape, it must be done manually or by a robot. Precisely. Use 'mtx' to have the robot load the tape. After the tape drive goes through its (automatic) loading cycle, the tape will be ready for use. 'mt status' can confirm that. Furthermore, at least with my Overland robot, 'mtx unload' automatically does a 'mt offline' to eject the tape. So running 'mt' manually is pretty rare, really. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: 2.5.1 parsing conf problems?
* Gene Heskett <[EMAIL PROTECTED]> [20060908 15:01]:
> On Friday 08 September 2006 09:46, Jean-Francois Malouin wrote:
> >* Ronan KERYELL <[EMAIL PROTECTED]> [20060908 06:41]:
> >> >>>>> On Thu, 7 Sep 2006 16:34:36 -0400, Jean-Francois Malouin
> >> >>>>> <[EMAIL PROTECTED]> said:
> >>
> >> Jean-Francois> Hello, I had my first compilation try at
> >> amanda-2.5.1 Jean-Francois> today on a SGI irix-6.5 and apart from the
> >> fact that I Jean-Francois> had to add '-lgen' to LDFLAGS while
> >> configuring Jean-Francois> everything went smooth. I read the release
> >> notes on the Jean-Francois> wiki on the new auth scheme and updated
> >> inetd.conf and Jean-Francois> the amandahost file and after installing
> >> a new Jean-Francois> amanda.conf and its minions (I plan to use a STK
> >> L180 Jean-Francois> with LTO drives) my first attempt at checking the
> >> Jean-Francois> server and client fails while parsing the conf file:
> >>
> >> Jean-Francois> "...amanda.conf", line 43: configuration keyword
> >> Jean-Francois> expected "...amanda.conf", line 43: end of line is
> >> Jean-Francois> expected
> >>
> >> Jean-Francois> ad nauseam. amanda.conf is 42 lines long...
> >>
> >> Jean-Francois> I compiled using the native sgi C compiler and gcc
> >> Jean-Francois> 3.3.2 with the same results. Any ideas?
> >>
> >> Same here for me.
> >>
> >> I guesse this is because the format of the conf file has changed and is
> >> less permisive about old features. So I needed to update my conf, by
> >> replacing for example "option compress best" by "compress client best"
> >> and so on. And afterwards it was fine.
> >>
> >> But with your file, we could help more...
> >
> >Here it comes with the includes put inline (makes it 185 lines long):
> >
> >org "stk_180-conf10"
> >mailto "amanda"
> >dumpuser "amanda"
> >inparallel 10
> >dumporder "TT"
> >taperalgo largestfit
> >netusage 1000 Mbps
> >dumpcycle 7 days
> >runspercycle 7
> >tapecycle 20 tapes
> >displayunit "m"
> >bumpsize 20 Mb
> >bumpdays 1
> >bumpmult 4
> >etimeout 2880
> >dtimeout 2880
> >ctimeout 60
> >tapebufs 20
> >runtapes 20
> >usetimestamps no
> >tpchanger "chg-zd-mtx"
> >tapedev "/hw/tape/50050763d95d/lun0nrnsv/c2p40"
> >rawtapedev "/dev/null"
> >changerfile "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/stk_180"
> >changerdev "/dev/changer-l180"
> >tapetype "Ultrium-SGT-LTO1"
> >labelstr "^stk_180-conf10-[0-9][0-9]*$"
> >holdingdisk hd1 {
> > comment "main holding disk"
> > directory "/holddisk/conf10/stk_180"
> > use 100 Gb
> > chunksize 0
> >}
> >reserve 100
>
> Humm, I believe the reserve keyword defaults to 100%. I use about 20%.
yes, that's what the doc says...
>
> >autoflush no
> >diskfile "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/disklist"
> >tapelist "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/tapelist"
> >infofile "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/curinfo"
> >logdir "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/log"
> >indexdir "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/index"
> >columnspec
> > "HostName=0:8,Disk=1:8,OrigKB=1:10,OutKB=1:10,DumpRate=1:7,TapeRate=1:7"
> > amrecover_do_fsf yes
> ^ an extra space here & this is about line 43...
nope, I rechecked the amanda.conf I sent as well as the email
and there is no space there... maybe the mailter indentention?
[...%<...]
I've started from scratch and followed the order of keyword
as explained on the wiki and I still get the error:
line XXX: configuration keyword expected
line XXX: end of line is expected
where XXX is the 1 + the number of lines in amanda.conf.
Here is my new amanda.conf and amanda-client.conf that still have
amcheck barfing. I can't see what I'm missing. Or is it an declaration
order issue? That had me bitten a while ago...
amanda.conf:
org "stk_180-conf10"
mailto "amanda"
dumpcycle 7
runspercycle 7
tapecycle 20
usetimestamps no
dumpuser "amanda"
printer "wb219"
tapedev "/hw/tape/50050763d95d/lun0nrnsv/
Re: amtapetype problems
On Friday 08 September 2006 14:31, Nick Jones wrote: >Ok, here is what I have tried finally. Trying to get amtapetype to work. > >[EMAIL PROTECTED] ~]# mt -f /dev/nst0 status >SCSI 2 tape drive: >File number=-1, block number=-1, partition=0. >Tape block size 0 bytes. Density code 0x0 (default). >Soft error count since last status=0 >General status bits on (5): > DR_OPEN IM_REP_EN > >[EMAIL PROTECTED] ~]# mt -f /dev/nst0 offline >/dev/nst0: Input/output error > >[EMAIL PROTECTED] ~]# mt -f /dev/nst0 load >/dev/nst0: Input/output error > >[EMAIL PROTECTED] ~]# mt -f /dev/st0 status >SCSI 2 tape drive: >File number=-1, block number=-1, partition=0. >Tape block size 0 bytes. Density code 0x0 (default). >Soft error count since last status=0 >General status bits on (5): > DR_OPEN IM_REP_EN > >[EMAIL PROTECTED] ~]# mt -f /dev/st0 load >/dev/st0: Input/output error > >Here's what the log says > >Sep 8 13:30:50 localhost kernel: st0: Error with sense data: <6>st0: >Current: sense key: Not Ready >Sep 8 13:30:50 localhost kernel: Additional sense: Medium not > present > >Any ideas? Only one, and its so obvious I hesitate to mention it, but those errors would seem to indicate that there is not a tape in the drive. >Thanks alot > >Nick > >On 8/21/06, Jon LaBadie <[EMAIL PROTECTED]> wrote: >> On Mon, Aug 21, 2006 at 01:58:16PM -0500, Nick Jones wrote: >> > [EMAIL PROTECTED] sbin]#./amtapetype -f /dev/nst0 -e 400g >> > amtapetype: could not open /dev/nst0: Input/output error >> > [EMAIL PROTECTED] sbin]#mtx -f /dev/nst0 inquiry >> > cannot open SCSI device '/dev/nst0' - Input/output error >> > >> > I don't have mt. I figured mtx is a suitable replacement. >> >> You figured wrong. >> >> mtx works on the robotic changer mechanism, >> st0 is a tape drive inside your changer. >> >> mt is for manipulating tape drives. >> >> I have two tape drives, and standalone Ultrium and a DDS 3 changer. >> mtx -f /dev/st does nothing useful on my system. >> Doesn't give an error, just hangs. >> >> > Not sure if it is going to work under Yellow Dog Linux 4.1. Any >> > other ideas? >> >> Does anything do anything with your tapedrive? >> Can you tar to it? tar from it? dd to or from it? cat to or from it? >> >> > Next I will try Backula I think. >> >> bacula may be a fine product. >> But unless you can access your tapedrive with some basic commands >> no backup product is going to do diddly. >> >> -- >> Jon H. LaBadie [EMAIL PROTECTED] >> JG Computing >> 4455 Province Line Road(609) 252-0159 >> Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Amanda 2.4, not using work area
Frank, Good suggestion, it might be that something as old as 2.4 reserved a lot of space. I was over this issue recently with another (more recent system) and had thought that "reserve" only came into play in degraded mode - when the tape drive was unavailable. However it might be that in 2.4 the rules where somewhat different. I have set reserve to be 15, will see how amanda progresses in the next run. Will post results either way. thank you, Brian On Fri, Sep 08, 2006 at 01:46:34PM -0500, Frank Smith wrote: > Brian Cuttler wrote: > > Hello amanda users, > > > > I'm running an old version of amanda 2.4 on a Solaris 9 system > > with a Solaris 8 client. > > > > Its come to my attention that the two larger client partitions > > are not being moved through the work area but are being written > > directly to tape. > > > > The work area is a 70 Gig partition, the client DLEs are on 35 Gig > > partitions. I'd expect to use the work area even if they did so > > sequentially, the partitions however are only about 70% occupied, > > aprox 24 Gig each, so ideally I'd have liked to have seen some > > parallelism. > > > > From the daily reports I see that the smaller client partitions > > on both the Solaris 8 and 9 machine (the amanda server does have > > itself as a client) do utilize the work area. > > > > I do not know what is preventing the work area from being used. > > I would add more work area if I thought it would help, but I don't > > see anything screaming "work area capacity" issue. > > If the direct-to-tape DLEs are level 0s, look at the 'reserve' option. > It tells amanda what percentage of your holdingdisk to save for use by > incrementals, so in case of tape problems you can run longer because > you don't fill it up with fulls. I don't remember what it defaults to > if not specified, but I think it is most of the space. > > > > > Here is a question, I assume chunksize appeared around the same > > time (if not actually with) the ability to split a single DLE > > across multiple work areas. I see it back in the docs into '98 > > or more but I'm not sure when it first appeared. Is there a list > > of what version which features where added, other than the changelog > > installation file ? > > Chunksize was a workaround for writing dumps to disk larger than the > system's max file size (which was 2GB on many machines at the time). > I think support for multiple holding disks was added later. > > Frank > > > > > Anyway it doesn't look like a work area capacity issue. What, other > > than adding chunksize to my amanda.conf and perhaps adding additional > > work area can I do to investigate this issue. > > > > There does not seem to be any output in the /tmp/amanda/* files > > showing which DLEs will be work area and which will not, where else > > can I look for an explaintation/solution to this issue ? > > > > thank you, > > > > 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 > > > > > -- > Frank Smith [EMAIL PROTECTED] > Sr. Systems Administrator Voice: 512-374-4673 > Hoover's Online Fax: 512-374-4501 --- 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.5.1 parsing conf problems?
On Friday 08 September 2006 09:46, Jean-Francois Malouin wrote:
>* Ronan KERYELL <[EMAIL PROTECTED]> [20060908 06:41]:
>> >>>>> On Thu, 7 Sep 2006 16:34:36 -0400, Jean-Francois Malouin
>> >>>>> <[EMAIL PROTECTED]> said:
>>
>> Jean-Francois> Hello, I had my first compilation try at
>> amanda-2.5.1 Jean-Francois> today on a SGI irix-6.5 and apart from the
>> fact that I Jean-Francois> had to add '-lgen' to LDFLAGS while
>> configuring Jean-Francois> everything went smooth. I read the release
>> notes on the Jean-Francois> wiki on the new auth scheme and updated
>> inetd.conf and Jean-Francois> the amandahost file and after installing
>> a new Jean-Francois> amanda.conf and its minions (I plan to use a STK
>> L180 Jean-Francois> with LTO drives) my first attempt at checking the
>> Jean-Francois> server and client fails while parsing the conf file:
>>
>> Jean-Francois> "...amanda.conf", line 43: configuration keyword
>> Jean-Francois> expected "...amanda.conf", line 43: end of line is
>> Jean-Francois> expected
>>
>> Jean-Francois> ad nauseam. amanda.conf is 42 lines long...
>>
>> Jean-Francois> I compiled using the native sgi C compiler and gcc
>> Jean-Francois> 3.3.2 with the same results. Any ideas?
>>
>> Same here for me.
>>
>> I guesse this is because the format of the conf file has changed and is
>> less permisive about old features. So I needed to update my conf, by
>> replacing for example "option compress best" by "compress client best"
>> and so on. And afterwards it was fine.
>>
>> But with your file, we could help more...
>
>Here it comes with the includes put inline (makes it 185 lines long):
>
>org "stk_180-conf10"
>mailto "amanda"
>dumpuser "amanda"
>inparallel 10
>dumporder "TT"
>taperalgo largestfit
>netusage 1000 Mbps
>dumpcycle 7 days
>runspercycle 7
>tapecycle 20 tapes
>displayunit "m"
>bumpsize 20 Mb
>bumpdays 1
>bumpmult 4
>etimeout 2880
>dtimeout 2880
>ctimeout 60
>tapebufs 20
>runtapes 20
>usetimestamps no
>tpchanger "chg-zd-mtx"
>tapedev "/hw/tape/50050763d95d/lun0nrnsv/c2p40"
>rawtapedev "/dev/null"
>changerfile "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/stk_180"
>changerdev "/dev/changer-l180"
>tapetype "Ultrium-SGT-LTO1"
>labelstr "^stk_180-conf10-[0-9][0-9]*$"
>holdingdisk hd1 {
> comment "main holding disk"
> directory "/holddisk/conf10/stk_180"
> use 100 Gb
> chunksize 0
>}
>reserve 100
Humm, I believe the reserve keyword defaults to 100%. I use about 20%.
>autoflush no
>diskfile "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/disklist"
>tapelist "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/tapelist"
>infofile "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/curinfo"
>logdir "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/log"
>indexdir "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/index"
>columnspec
> "HostName=0:8,Disk=1:8,OrigKB=1:10,OutKB=1:10,DumpRate=1:7,TapeRate=1:7"
> amrecover_do_fsf yes
^ an extra space here & this is about line 43...
>amrecover_check_label yes
>amrecover_changer "changer"
>define tapetype Ultrium-SGT-LTO1 {
> comment "just produced by tapetype program"
> length 101376 mbytes
> filemark 0 kbytes
> speed 15084 kps
>}
>define dumptype global {
> comment "Global definitions"
> index yes
> record yes
>}
>define dumptype always-full {
> global
> comment "Full dump of this filesystem always"
> compress none
> priority high
> dumpcycle 0
>}
>define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress none
> priority low
>}
>define dumptype user-tar {
> root-tar
> comment "user partitions dumped with tar"
> priority medium
>}
>define dumptype high-tar {
> root-tar
> comment "partitions dumped with tar"
> priority high
> maxdumps 4
>}
>define dumptype high-tar-test {
> root-tar
> comment "partitions dumped with tar"
> priority high
> record no
> index no
> ignore yes
>}
>define dumptype comp-root-tar {
> root-tar
> comment "Root partitions with compression"
> compress client fast
>}
>define dumpty
Re: amtapetype problems
On Fri, 8 Sep 2006 at 1:31pm, Nick Jones wrote [EMAIL PROTECTED] ~]# mt -f /dev/nst0 status SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (5): DR_OPEN IM_REP_EN [EMAIL PROTECTED] ~]# mt -f /dev/nst0 offline /dev/nst0: Input/output error [EMAIL PROTECTED] ~]# mt -f /dev/nst0 load /dev/nst0: Input/output error [EMAIL PROTECTED] ~]# mt -f /dev/st0 status SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (5): DR_OPEN IM_REP_EN [EMAIL PROTECTED] ~]# mt -f /dev/st0 load /dev/st0: Input/output error Here's what the log says Sep 8 13:30:50 localhost kernel: st0: Error with sense data: <6>st0: Current: sense key: Not Ready Sep 8 13:30:50 localhost kernel: Additional sense: Medium not present Any ideas? Err, there's no tape in the drive? Read through 'man mtx' and 'man mt', and understand them. In brief, you use 'mtx' to manipulate the loaders robotics -- e.g. telling it to move the tape in slot 10 into drive 1. You use 'mt' to talk to the tape drive, e.g. to get the status. 'mtx' talks to the generic SCSI device associated with the loader, while 'mt' talks to the SCSI tape device associated with, well, the tape device. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Amanda 2.4, not using work area
Brian Cuttler wrote: > Hello amanda users, > > I'm running an old version of amanda 2.4 on a Solaris 9 system > with a Solaris 8 client. > > Its come to my attention that the two larger client partitions > are not being moved through the work area but are being written > directly to tape. > > The work area is a 70 Gig partition, the client DLEs are on 35 Gig > partitions. I'd expect to use the work area even if they did so > sequentially, the partitions however are only about 70% occupied, > aprox 24 Gig each, so ideally I'd have liked to have seen some > parallelism. > > From the daily reports I see that the smaller client partitions > on both the Solaris 8 and 9 machine (the amanda server does have > itself as a client) do utilize the work area. > > I do not know what is preventing the work area from being used. > I would add more work area if I thought it would help, but I don't > see anything screaming "work area capacity" issue. If the direct-to-tape DLEs are level 0s, look at the 'reserve' option. It tells amanda what percentage of your holdingdisk to save for use by incrementals, so in case of tape problems you can run longer because you don't fill it up with fulls. I don't remember what it defaults to if not specified, but I think it is most of the space. > > Here is a question, I assume chunksize appeared around the same > time (if not actually with) the ability to split a single DLE > across multiple work areas. I see it back in the docs into '98 > or more but I'm not sure when it first appeared. Is there a list > of what version which features where added, other than the changelog > installation file ? Chunksize was a workaround for writing dumps to disk larger than the system's max file size (which was 2GB on many machines at the time). I think support for multiple holding disks was added later. Frank > > Anyway it doesn't look like a work area capacity issue. What, other > than adding chunksize to my amanda.conf and perhaps adding additional > work area can I do to investigate this issue. > > There does not seem to be any output in the /tmp/amanda/* files > showing which DLEs will be work area and which will not, where else > can I look for an explaintation/solution to this issue ? > > thank you, > > 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 > -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Amanda deadlock ?
Hello Amanda users, I am running amanda VERSION="Amanda-2.4.4p1-20030716" on an SGI/IRIX system v6.5.28 and saw something odd today. The output from amstatus showed that for several partitions the amount of data being dumped far exceeded the estimated size of the data (300% dumped and still going). I do not believe this is an amanda issue but the result of heavy user activity on the partiton (several TAR dumped partitons on a RAID array that exceeds the capacity of the tape drive). It seems that running several of these dumps concurrently exhausted the capaicity of the work area, which again is not an amanda issue, I'm sure if the data size where anywhere near the estimates results we would not have had this happen. However it seems that when we ran out of work area the dumps all deadlocked against one another, all incomplete, none eligable to be written to tape. It was an odd problem, not really an amanda issue but something I thought should be meantioned since it might be desirable to eventually (it not already) providing some form of deadlock monitoring. At least I think this is why amanda wasn't progressing. thank you, 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: amtapetype problems
Ok, here is what I have tried finally. Trying to get amtapetype to work. [EMAIL PROTECTED] ~]# mt -f /dev/nst0 status SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (5): DR_OPEN IM_REP_EN [EMAIL PROTECTED] ~]# mt -f /dev/nst0 offline /dev/nst0: Input/output error [EMAIL PROTECTED] ~]# mt -f /dev/nst0 load /dev/nst0: Input/output error [EMAIL PROTECTED] ~]# mt -f /dev/st0 status SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (5): DR_OPEN IM_REP_EN [EMAIL PROTECTED] ~]# mt -f /dev/st0 load /dev/st0: Input/output error Here's what the log says Sep 8 13:30:50 localhost kernel: st0: Error with sense data: <6>st0: Current: sense key: Not Ready Sep 8 13:30:50 localhost kernel: Additional sense: Medium not present Any ideas? Thanks alot Nick On 8/21/06, Jon LaBadie <[EMAIL PROTECTED]> wrote: On Mon, Aug 21, 2006 at 01:58:16PM -0500, Nick Jones wrote: > [EMAIL PROTECTED] sbin]#./amtapetype -f /dev/nst0 -e 400g > amtapetype: could not open /dev/nst0: Input/output error > [EMAIL PROTECTED] sbin]#mtx -f /dev/nst0 inquiry > cannot open SCSI device '/dev/nst0' - Input/output error > > I don't have mt. I figured mtx is a suitable replacement. You figured wrong. mtx works on the robotic changer mechanism, st0 is a tape drive inside your changer. mt is for manipulating tape drives. I have two tape drives, and standalone Ultrium and a DDS 3 changer. mtx -f /dev/st does nothing useful on my system. Doesn't give an error, just hangs. > Not sure if it is going to work under Yellow Dog Linux 4.1. Any other > ideas? Does anything do anything with your tapedrive? Can you tar to it? tar from it? dd to or from it? cat to or from it? > > Next I will try Backula I think. > bacula may be a fine product. But unless you can access your tapedrive with some basic commands no backup product is going to do diddly. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Nick Jones University of Iowa Dept of Neurology Systems Analyst 319-356-0451
Amanda 2.4, not using work area
Hello amanda users, I'm running an old version of amanda 2.4 on a Solaris 9 system with a Solaris 8 client. Its come to my attention that the two larger client partitions are not being moved through the work area but are being written directly to tape. The work area is a 70 Gig partition, the client DLEs are on 35 Gig partitions. I'd expect to use the work area even if they did so sequentially, the partitions however are only about 70% occupied, aprox 24 Gig each, so ideally I'd have liked to have seen some parallelism. >From the daily reports I see that the smaller client partitions on both the Solaris 8 and 9 machine (the amanda server does have itself as a client) do utilize the work area. I do not know what is preventing the work area from being used. I would add more work area if I thought it would help, but I don't see anything screaming "work area capacity" issue. Here is a question, I assume chunksize appeared around the same time (if not actually with) the ability to split a single DLE across multiple work areas. I see it back in the docs into '98 or more but I'm not sure when it first appeared. Is there a list of what version which features where added, other than the changelog installation file ? Anyway it doesn't look like a work area capacity issue. What, other than adding chunksize to my amanda.conf and perhaps adding additional work area can I do to investigate this issue. There does not seem to be any output in the /tmp/amanda/* files showing which DLEs will be work area and which will not, where else can I look for an explaintation/solution to this issue ? thank you, 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: using disk instead of tape
On Friday 08 September 2006 07:08, Ronan KERYELL wrote: > First I would say it is possible to mkfs the disk before each new usage to > have clean data structures with less overhead (no fragmentation...). Not really necessary; on any modern filesystem (and a few very old ones), emptying the filesystem will clear any fragmentation that might have appeared. > Secondly you could choose a file system optimized for big files and > write-ahead only. It s possible to change the parameters of the FS to push > even more this behaviour (how many cylinders? block size? no logging on > the data, no block reserve for fast allocation...). Well, there's no such thing as write-ahead (the kernel will guess the data you will write? :o) but as for big files, the best thing you can do at the FS layer is to use a large block size and no data journaling. Setting reserved blocks to zero is a good idea, as is using O_DIRECT (as discussed elsewhere). > Third, what about bad blocks on disk? How to skip them in a raw partition > if you do not have state-of-the-art disks that do block remapping for you > in your back-yard (such as SCSI)? Often FS do these tricks for you on > IDE disks for example. Irrelevant. All modern drives (IDE included) since MFM have done automatic internal remapping. > Well, IMHO, I would vote for a FS solution except if I have a real > gain... :-) As would I. -- Forums for Amanda discussion: http://forums.zmanda.com/
Re: amanda configuration file question
Robert, With amanda-2.5.1, you can do 'amadmin config'. It will dump the config. Jean-Louis McGraw, Robert P. wrote: Is there an amanda command that will list the .config parameters that will be used in a particular run. I have two types of runs; archive and daily. I have an includefile for most of my parameters and a .config file for each type run. I would like to run a command that will list the parameters that will be used for a particular run. The will allow me to be sure I have the right parameters for the different run types. Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067
RE: Amanda error "Unexpected field value..."
It seems that tar 1.15.91 does not work with my version of amanda. I have dropped back to an older version of tar until I can upgrade my amanda. Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 > -Original Message- > From: Olivier Nicole [mailto:[EMAIL PROTECTED] > Sent: Friday, September 08, 2006 10:37 AM > To: McGraw, Robert P. > Cc: amanda-users@amanda.org > Subject: Re: Amanda error "Unexpected field value..." > > > > The difference is that the good run was a level 0 and the run with the > error > > was a level 1. > > What is the "Unexpected field value"? > > Well that's the problem with cygwin... We have little reference. > > Apparently running level 0 gtar creates a sort of index file, to use > in level 1 and compare files that have changed. > > And it seems that in between the run 0 and 1 gtar cannot read the file > it created. > > If you look at the sendzie debug you should see a command very close > to this one > > gtar --create --file - --directory /local > --one-file-system --listed-incremental /local/Amanda/amanda-2.4 > .5p1/var/amanda/gnutar-lists/coriolis_local_1.new --sparse > --ignore-failed-read --totals . > > but that will say "gtar --create --file /dev/null ..." > > Did that one completed without error? > > Try to run the long gtar command by hand, with --file - and --file > /dev/null > > Tryto extract the comamnd for level 0 and run it... > > Check your version of gtar. > > Bests, > > Olivier smime.p7s Description: S/MIME cryptographic signature
Re: Amanda error "Unexpected field value..."
> The difference is that the good run was a level 0 and the run with the error > was a level 1. > What is the "Unexpected field value"? Well that's the problem with cygwin... We have little reference. Apparently running level 0 gtar creates a sort of index file, to use in level 1 and compare files that have changed. And it seems that in between the run 0 and 1 gtar cannot read the file it created. If you look at the sendzie debug you should see a command very close to this one gtar --create --file - --directory /local --one-file-system --listed-incremental /local/Amanda/amanda-2.4 .5p1/var/amanda/gnutar-lists/coriolis_local_1.new --sparse --ignore-failed-read --totals . but that will say "gtar --create --file /dev/null ..." Did that one completed without error? Try to run the long gtar command by hand, with --file - and --file /dev/null Tryto extract the comamnd for level 0 and run it... Check your version of gtar. Bests, Olivier
amanda configuration file question
Is there an amanda command that will list the .config parameters that will be used in a particular run. I have two types of runs; archive and daily. I have an includefile for most of my parameters and a .config file for each type run. I would like to run a command that will list the parameters that will be used for a particular run. The will allow me to be sure I have the right parameters for the different run types. Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
Amanda error "Unexpected field value..."
the following are errors in my amanda mail report. Both mailrelay and coriolis are Window machines running cygwin. FAILURE AND STRANGE DUMP SUMMARY: mailrelay /local lev 1 FAILED [no backup size line] mailrelay /cygdrive/c/Alligate/agbackupfiles lev 1 FAILED [no backup size line] coriolis /local lev 1 FAILED [no backup size line] the backup ran find yesterday and then today I get these errors. **Here is the sendbackup...debug file for 20060906 ( the good run) ** ** sendbackup: debug 1 pid 2388 ruid 18 euid 18: start at Wed Sep 6 20:16:04 2006 /local/Amanda/amanda-2.4.5p1/libexec/sendbackup: version 2.4.5p1 parsed request as: program `GNUTAR' disk `/local' device `/local' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.536 sendbackup: time 0.015: stream_server: waiting for connection: 0.0.0.0.537 sendbackup: time 0.015: stream_server: waiting for connection: 0.0.0.0.538 sendbackup: time 0.015: waiting for connect on 536, then 537, then 538 sendbackup: time 0.031: stream_accept: connection from 128.210.3.177.62757 sendbackup: time 0.031: stream_accept: connection from 128.210.3.177.62758 sendbackup: time 0.031: stream_accept: connection from 128.210.3.177.62759 sendbackup: time 0.031: got all connections sendbackup-gnutar: time 0.062: doing level 0 dump as listed-incremental to /local/Amanda/amanda-2.4.5p1/var/amanda/gnutar-lists/corioli s_local_0.new sendbackup-gnutar: time 0.062: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: time 0.093: spawning /local/Amanda/amanda-2.4.5p1/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /local --one-file-system --listed-incremental /local/Amanda/amanda-2.4.5p 1/var/amanda/gnutar-lists/coriolis_local_0.new --sparse --ignore-failed-read --totals . sendbackup-gnutar: time 0.125: /local/Amanda/amanda-2.4.5p1/libexec/runtar: pid 2660 sendbackup: time 0.250: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" sendbackup: time 3.093: 53:size(|): Total bytes written: 3819520 (3.7MiB, 1.4MiB/s) sendbackup: time 3.312: index created successfully sendbackup: time 3.328: pid 2388 finish time Wed Sep 6 20:16:08 2006 sendbackup.20060906201604.debug (END) **Here is the sendbackupdebug for 20060907 (the one with the error) ** ** sendbackup: debug 1 pid 3892 ruid 18 euid 18: start at Thu Sep 7 20:17:07 2006 /local/Amanda/amanda-2.4.5p1/libexec/sendbackup: version 2.4.5p1 parsed request as: program `GNUTAR' disk `/local' device `/local' level 1 since 2006:9:7:0:16:4 options `|;bsd-auth;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.015: stream_server: waiting for connection: 0.0.0.0.951 sendbackup: time 0.015: stream_server: waiting for connection: 0.0.0.0.952 sendbackup: time 0.015: stream_server: waiting for connection: 0.0.0.0.953 sendbackup: time 0.015: waiting for connect on 951, then 952, then 953 sendbackup: time 0.031: stream_accept: connection from 128.210.3.177.44647 sendbackup: time 0.031: stream_accept: connection from 128.210.3.177.44648 sendbackup: time 0.031: stream_accept: connection from 128.210.3.177.44649 sendbackup: time 0.031: got all connections sendbackup-gnutar: time 0.078: doing level 1 dump as listed-incremental from /local/Amanda/amanda-2.4.5p1/var/amanda/gnutar-lists/co riolis_local_0 to /local/Amanda/amanda-2.4.5p1/var/amanda/gnutar-lists/coriolis_local_1.new sendbackup-gnutar: time 0.078: doing level 1 dump from date: 2006-09-07 0:16:04 GMT sendbackup: time 0.109: spawning /local/Amanda/amanda-2.4.5p1/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /local --one-file-system --listed-incremental /local/Amanda/amanda-2.4 .5p1/var/amanda/gnutar-lists/coriolis_local_1.new --sparse --ignore-failed-read --totals . sendbackup-gnutar: time 0.140: /local/Amanda/amanda-2.4.5p1/libexec/runtar: pid 2992 sendbackup: time 0.281: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" sendbackup: time 0.687: 125: strange(?): gtar: Unexpected field value in snapshot file sendbackup: time 0.687: 125: strange(?): gtar: Error is not recoverable: exiting now sendbackup: time 1.124: index created successfully sendbackup: time 1.156: error [no backup size line] sendbackup: time 1.156: pid 3892 finish time Thu Sep 7 20:17:08 2006 ** ** ** The difference is that the good run was a level 0 and the run with the error was a level 1. coriolis->[46] > tar --version tar (GNU tar) 1.15.91 gtar is a link to tar. What is the "Unexpected field value"? Thanks Robert _
Re: 2.5.1 parsing conf problems?
* Ronan KERYELL <[EMAIL PROTECTED]> [20060908 06:41]:
> >>>>> On Thu, 7 Sep 2006 16:34:36 -0400, Jean-Francois Malouin <[EMAIL
> >>>>> PROTECTED]> said:
>
> Jean-Francois> Hello, I had my first compilation try at amanda-2.5.1
> Jean-Francois> today on a SGI irix-6.5 and apart from the fact that I
> Jean-Francois> had to add '-lgen' to LDFLAGS while configuring
> Jean-Francois> everything went smooth. I read the release notes on the
> Jean-Francois> wiki on the new auth scheme and updated inetd.conf and
> Jean-Francois> the amandahost file and after installing a new
> Jean-Francois> amanda.conf and its minions (I plan to use a STK L180
> Jean-Francois> with LTO drives) my first attempt at checking the
> Jean-Francois> server and client fails while parsing the conf file:
>
> Jean-Francois> "...amanda.conf", line 43: configuration keyword
> Jean-Francois> expected "...amanda.conf", line 43: end of line is
> Jean-Francois> expected
>
> Jean-Francois> ad nauseam. amanda.conf is 42 lines long...
>
> Jean-Francois> I compiled using the native sgi C compiler and gcc
> Jean-Francois> 3.3.2 with the same results. Any ideas?
>
> Same here for me.
>
> I guesse this is because the format of the conf file has changed and is less
> permisive about old features. So I needed to update my conf, by replacing
> for example "option compress best" by "compress client best" and so
> on. And afterwards it was fine.
>
> But with your file, we could help more...
Here it comes with the includes put inline (makes it 185 lines long):
org "stk_180-conf10"
mailto "amanda"
dumpuser "amanda"
inparallel 10
dumporder "TT"
taperalgo largestfit
netusage 1000 Mbps
dumpcycle 7 days
runspercycle 7
tapecycle 20 tapes
displayunit "m"
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 2880
dtimeout 2880
ctimeout 60
tapebufs 20
runtapes 20
usetimestamps no
tpchanger "chg-zd-mtx"
tapedev "/hw/tape/50050763d95d/lun0nrnsv/c2p40"
rawtapedev "/dev/null"
changerfile "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/stk_180"
changerdev "/dev/changer-l180"
tapetype "Ultrium-SGT-LTO1"
labelstr "^stk_180-conf10-[0-9][0-9]*$"
holdingdisk hd1 {
comment "main holding disk"
directory "/holddisk/conf10/stk_180"
use 100 Gb
chunksize 0
}
reserve 100
autoflush no
diskfile "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/disklist"
tapelist "/opt/amanda/amanda10/etc/amanda/stk_180-conf10/tapelist"
infofile "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/curinfo"
logdir "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/log"
indexdir "/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/index"
columnspec
"HostName=0:8,Disk=1:8,OrigKB=1:10,OutKB=1:10,DumpRate=1:7,TapeRate=1:7"
amrecover_do_fsf yes
amrecover_check_label yes
amrecover_changer "changer"
define tapetype Ultrium-SGT-LTO1 {
comment "just produced by tapetype program"
length 101376 mbytes
filemark 0 kbytes
speed 15084 kps
}
define dumptype global {
comment "Global definitions"
index yes
record yes
}
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compress none
priority high
dumpcycle 0
}
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
priority low
}
define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
priority medium
}
define dumptype high-tar {
root-tar
comment "partitions dumped with tar"
priority high
maxdumps 4
}
define dumptype high-tar-test {
root-tar
comment "partitions dumped with tar"
priority high
record no
index no
ignore yes
}
define dumptype comp-root-tar {
root-tar
comment "Root partitions with compression"
compress client fast
}
define dumptype comp-user-tar {
user-tar
compress client fast
}
define dumptype holding-disk {
global
comment "The master-host holding disk itself"
holdingdisk no
priority medium
}
define dumptype comp-user {
global
comment "Non-root partitions on reasonably fast machines"
compress client fast
priority medium
}
define dumptype nocomp-user {
comp-user
comment "Non-root partitions on slow machines"
compress none
}
define dumptype comp-root {
global
comment "Root partitions with compression"
compress client fast
priority low
}
define dumptype nocomp-root {
comp-root
comment "Root partitions witho
Re: using disk instead of tape
On Fri, 8 Sep 2006, Ronan KERYELL wrote:
> Third, what about bad blocks on disk? How to skip them in a raw partition
> if you do not have state-of-the-art disks that do block remapping for you
> in your back-yard (such as SCSI)? Often FS do these tricks for you on
> IDE disks for example.
These days IDE does that too.
But if there are too many of them, you loose (same for SCSI).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: using disk instead of tape
> On Tue, 5 Sep 2006 04:09:05 -0500, Phil Howard <[EMAIL PROTECTED]> said: Phil> If tar can read from raw tape, it can read from raw disk. I've Phil> already done that several times for various things. Bare metal Phil> recovery will need at a minimum the tar or dump utility Phil> depending on format used. I've thought about this raw partition stuff and I'm a bit afraid like some others on the list. First I would say it is possible to mkfs the disk before each new usage to have clean data structures with less overhead (no fragmentation...). Secondly you could choose a file system optimized for big files and write-ahead only. It s possible to change the parameters of the FS to push even more this behaviour (how many cylinders? block size? no logging on the data, no block reserve for fast allocation...). Third, what about bad blocks on disk? How to skip them in a raw partition if you do not have state-of-the-art disks that do block remapping for you in your back-yard (such as SCSI)? Often FS do these tricks for you on IDE disks for example. Well, IMHO, I would vote for a FS solution except if I have a real gain... :-) -- Ronan KERYELL |\/ Tel:(+33|0) 2.29.00.14.15 Département Informatique|/) Fax:(+33|0) 2.29.00.12.82 ENST Bretagne, CS 83818 KGSM:(+33|0) 6.13.14.37.66 F-29238 PLOUZANÉ CEDEX |\ E-mail: [EMAIL PROTECTED] FRANCE | \ http://enstb.org/~keryell callto:ils.seconix.com/[EMAIL PROTECTED]
Re: 2.5.1 parsing conf problems?
> On Thu, 7 Sep 2006 16:34:36 -0400, Jean-Francois Malouin <[EMAIL > PROTECTED]> said: Jean-Francois> Hello, I had my first compilation try at amanda-2.5.1 Jean-Francois> today on a SGI irix-6.5 and apart from the fact that I Jean-Francois> had to add '-lgen' to LDFLAGS while configuring Jean-Francois> everything went smooth. I read the release notes on the Jean-Francois> wiki on the new auth scheme and updated inetd.conf and Jean-Francois> the amandahost file and after installing a new Jean-Francois> amanda.conf and its minions (I plan to use a STK L180 Jean-Francois> with LTO drives) my first attempt at checking the Jean-Francois> server and client fails while parsing the conf file: Jean-Francois> "...amanda.conf", line 43: configuration keyword Jean-Francois> expected "...amanda.conf", line 43: end of line is Jean-Francois> expected Jean-Francois> ad nauseam. amanda.conf is 42 lines long... Jean-Francois> I compiled using the native sgi C compiler and gcc Jean-Francois> 3.3.2 with the same results. Any ideas? Same here for me. I guesse this is because the format of the conf file has changed and is less permisive about old features. So I needed to update my conf, by replacing for example "option compress best" by "compress client best" and so on. And afterwards it was fine. But with your file, we could help more... -- Ronan KERYELL |\/ Tel:(+33|0) 2.29.00.14.15 Département Informatique|/) Fax:(+33|0) 2.29.00.12.82 ENST Bretagne, CS 83818 KGSM:(+33|0) 6.13.14.37.66 F-29238 PLOUZANÉ CEDEX |\ E-mail: [EMAIL PROTECTED] FRANCE | \ http://enstb.org/~keryell callto:ils.seconix.com/[EMAIL PROTECTED]
Re: Debian packages for Amanda
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, 08.09.2006 at 01:28 -0500, Phil Howard wrote: > These packages configure the user to run Amanda as "backup". But it > seems the "backup" user also does other things. Does anyone see any > possible conflict in this? I'd say "may be used for other things", rather than "also does other things", really. To be honest, a user called backup makes more sense than a user called 'amanda' - we used to have a staff member called Amanda who existed prior to an AMANDA installation and things got ... messy. On a Debian system, the backup user is a member of the appropriate system groups to allow backups to function, i.e. a member of 'disk' For what it's worth, on a Debian Stable system, I've found that the AMANDA packages Just Work very nicely, especially on the clients, since there is basically no configuration required. Feel free to ask further related questions, because I've been using AMANDA on Debian systems for many years... Dave. - -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Cancer Epidemiology Unit Cancer Research UK / Oxford University PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370 Get key from http://www.ceu.ox.ac.uk/~davee/davee-ceu-ox-ac-uk.asc N 51.7518, W 1.2016 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD4DBQFFAT9mbpQs/WlN43ARAoMaAKCp62nbpm4BtIdkkJcsUY0UeH2+4gCUCs02 FgHS+8Lh8DC9ro/SlIGhYw== =qpWS -END PGP SIGNATURE-
Re: Debian packages for Amanda
On Fri, 8 Sep 2006, Phil Howard wrote:
> Any Debian users/gurus around?
>
> I found that Debian has Amanda broken into 3 packages:
> amanda-common
> amanda-client
> amanda-server
>
> What I expected was I could install amanda-client on client machines and
> amanda-server on a server machine (both on a machine that is the tape
> server _and_ has data to be backed up). I expected amanda-common to be
> needed on either client or server.
Yes.
> However, when installing amanda-common, it also installs amanda-client.
> Anyone know why Debian has things arranged this way?
None of the amanda-common packages (I checked stable, testing, and unstable)
depend on amanda-client.
I had no problem (on Debian testing) removing amanda-client (and keeping
amanda-common), or installing amanda-common only.
But amanda-common does suggest amanda-client | amanda-server. Perhaps you have
some `auto install suggested packages' option enabled?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
