Re: Amrecover - Amandaidx Looping?
Bernhard,
Thanks for the information. You are absolutely correct. Changing the 'wait =
yes' to 'wait = no' fixed the problem. Thanks so much for your help.
Jeff
"Bernhard R. Erdmann" wrote:
> > [root@garfield amanda]# cat amrecover.20011010121258.debug
> > amrecover: debug 1 pid 2022 ruid 0 euid 0 start time Wed Oct 10
> > 12:12:58 2001
> > amrecover: stream_client: connect(10082) failed: Connection
> > refused
> > cannot connect to garfield: Connection refused
> > amrecover: pid 2022 finish time Wed Oct 10 12:12:58 2001
> >
> > And this is what I see in "/var/log/messages":
> > Oct 10 12:01:20 garfield xinetd[1927]: warning: can't get client
> > address: Transport endpoint is not connected
> [...]
> > Oct 10 12:01:21 garfield xinetd[1936]: warning: can't get client
> > address: Transport endpoint is not connected
> > Oct 10 12:01:21 garfield xinetd[1923]: amandaidx service was
> > deactivated because of looping
> [...]
> > [root@garfield amanda]# cat /etc/xinetd.d/amandaidx
> > # default: off
> > #
> > # description: Part of the Amanda server package
> > service amandaidx
> > {
> >socket_type = stream
> >protocol= tcp
> >wait= yes
> >user= amanda
> >group = disk
> >server = /usr/lib/amanda/amindexd
> > }
> [...]
>
> Please check again with "wait = no" (don't forget to SIGUSR1 xinetd or
> to restart it - SIGHUP won't help).
>
> $ grep ^am /etc/inetd.conf
> amanda dgram udp waitamanda /usr/libexec/amanda/amandad
> amandad
> amandaidx stream tcp nowait amanda
> /usr/libexec/amanda/amindexd amindexd
> amidxtape stream tcp nowait amanda
> /usr/libexec/amanda/amidxtaped amidxtaped
sendsize.*.debug reports negative value
Dear Amanda-Users, I have been scouring the list archives and google for an answer to this problem, but can't seem to figure it out. I have a few clients that are having a problem in the nightly backup. Last week I started fresh and installed the client from sources, brand new, on to a workstation named 'barry'. This workstation is a Sun Sparc 5 running Solaris 2.5.1 (old, I know). The client was configured using the following command: ./configure --with-user=root --with-group=bin --without-server This ran with no problem, as did the 'make' and 'make install'. I believe the entry in the /etc/inetd.conf' file is correct: amanda dgram udp wait root /usr/local/libexec/amandad amandad Everything is reportedly looking good when I run amcheck. I tried to run a non-indexed test backup with only barry in the disklist, but it failed. Here's what the report said: FAILURE AND STRANGE DUMP SUMMARY: barry /export/home lev 0 FAILED [disk /export/home offline on barry?] The *.debug files in /tmp/amanda seem fine, except for sendsize*.debug. It has a negative number for the "Total bytes written" and then says there was no size line. In case one were to wonder, the version of barry's /usr/local/bin/gnutar is: tar (GNU tar) 1.13.19 This seems like it is a fairly simple problem, but I can't seem to find the answer. I've attached the *.debug logs below. All help is greatly appreciated! Jeff Smith [EMAIL PROTECTED] sendsize*.debug sendsize: debug 1 pid 1267 ruid 0 euid 0 start time Thu Feb 21 12:20:10 2002 /usr/local/libexec/sendsize: version 2.4.2p2 calculating for amname '/export/home', dirname '/export/home' sendsize: getting size via gnutar for /export/home level 0 sendsize: missing exclude list file "/export/home/.amanda.excludes" discarded sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /usr/local/bin/gnutar --create --file /dev/null --directory /export/home --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/barry_export_home_0.new --sparse --ignore-failed-read --totals . Total bytes written: -2079072256 . (no size line match in above gnutar output) . sendsize: pid 1267 finish time Thu Feb 21 12:37:42 2002 amandad*.debug amandad: debug 1 pid 1266 ruid 0 euid 0 start time Thu Feb 21 12:20:10 2002 amandad: version 2.4.2p2 amandad: build: VERSION="Amanda-2.4.2p2" amandad:BUILT_DATE="Thu Feb 21 10:16:05 PST 2002" amandad:BUILT_MACH="SunOS barry 5.5.1 Generic sun4m sparc SUNW,SPARCstation-5" 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" amandad:GNUTAR="/usr/local/bin/gnutar" COMPRESS_PATH="/bin/gzip" amandad:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/ucb/Mail" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="barry" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="barry" 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="root" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" got packet: Amanda 2.4 REQ HANDLE 000-80B00708 SEQ 1014322585 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=barry; GNUTAR /export/home 0 1970:1:1:0:0:0 -1 exclude-list=.amanda.excludes sending ack: Amanda 2.4 ACK HANDLE 000-80B00708 SEQ 1014322585 bsd security: remote host garfield user amanda local user root amandahosts security check passed amandad: running service "/usr/local/libexec/sendsize" amandad: got packet: Amanda 2.4 REQ HANDLE 000-80B00708 SEQ 1014322585 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=barry; GNUTAR /export/home 0 1970:1:1:0:0:0 -1 exclude-list=.amanda.excludes amandad: received dup P_REQ packet, ACKing it sending ack: Amanda 2.4 ACK HANDLE 000-80B00708 SEQ 1014322585 amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-80B00708 SEQ 1014322585 OPTIONS maxdumps=1; /export/home 0 SIZE -1 amandad: got packet: Amanda 2.4 ACK HANDLE 000-80B00708 SEQ 1014322585 amandad: pid 1266 finish time Thu Feb 21 12:37:43 2002 runtar*.debug runtar: debug 1 pid 1268 ruid 0 euid 0 start time Thu Feb 21 12:20:10 2002 /usr/local
Backup stop time?
Dear Amanda-Users, Can any one tell me if there is a way to set a stop time for backups? I am not thrilled about this idea, but some of my backups do run a bit long and I am getting complaints some mornings when there are many level 0 dumps. Thanks in advance! Jeff
Re: Backup stop time?
Thanks to Brian and Chris for your answers on this topic. As I found out, there is no mechanism to make Amanda stop at a particular time. That's ok, though. I wasn't too thrilled about the idea of stopping my backup. It's likely that the day I do something like that, I need that backup. :-) I am going to experiment with upping my settings to 8 dumpers and see if that helps. I will probably move my backup start time a few hours earlier, too. Jeff On Fri, 2002-03-01 at 01:45, Chris Marble wrote: > Jeffery Smith wrote: > > > > Can any one tell me if there is a way to set a stop time for backups? I > > am not thrilled about this idea, but some of my backups do run a bit > > long and I am getting complaints some mornings when there are many level > > 0 dumps. > > No way that I can think of. You could start backups earlier. You > could increase maxdumps. You could lengthen your dumpcycle so Amanda won't > have to fit as many level 0s on a tape. > Would you really want unfinished backups to abort? You could do that > with some kill commands in cron. > -- > [EMAIL PROTECTED] - HMC UNIX Systems Manager > My opinions are my own and probably don't represent anything anyway.
Re: sendsize.*.debug reports negative value
Hi Chris, Thanks for your reply. I think you've actually hit the problem on the head. Yesterday I started updating the tar program on my clients and backups started happening. The negative number disappeared. Apparently the older tar would not go high enough. Thanks for your reply! Jeff On Fri, 2002-03-01 at 01:17, Chris Marble wrote: > Jeffery Smith wrote: > > > > Last week I started fresh and installed the client from sources, brand new, > > on to a workstation named 'barry'. This workstation is a Sun Sparc 5 > > running Solaris 2.5.1 (old, I know). The client was configured using > > the following command: > > > > ./configure --with-user=root --with-group=bin --without-server > > I've run Amanda on 2.5, 2.5.1, 2.6, 7 and 8 boxes. Never bothered with > the "without-server" option though. > > > This ran with no problem, as did the 'make' and 'make install'. I > > believe the entry in the /etc/inetd.conf' file is correct: > > > > amanda dgram udp wait root /usr/local/libexec/amandad amandad > > Looks right to me too. amcheck should report any terrible problem. > > > Everything is reportedly looking good when I run amcheck. I tried to > > run a non-indexed test backup with only barry in the disklist, but it > > failed. Here's what the report said: > > > > FAILURE AND STRANGE DUMP SUMMARY: > > barry /export/home lev 0 FAILED [disk /export/home offline on barry?] > > Is this an automounted volume? Could it be unmounted when you do the > backups in the wee hours? > > > In case one were to wonder, the version of barry's /usr/local/bin/gnutar is: > > tar (GNU tar) 1.13.19 > > That's a good version. And the files below show that's the path it's using. > > > > > sendsize*.debug > > > > sendsize: debug 1 pid 1267 ruid 0 euid 0 start time Thu Feb 21 12:20:10 > > 2002 > > /usr/local/libexec/sendsize: version 2.4.2p2 > > calculating for amname '/export/home', dirname '/export/home' > > sendsize: getting size via gnutar for /export/home level 0 > > sendsize: missing exclude list file "/export/home/.amanda.excludes" > > discarded > > sendsize: spawning /usr/local/libexec/runtar in pipeline > > sendsize: argument list: /usr/local/bin/gnutar --create --file /dev/null > > --directory /export/home --one-file-system --listed-incremental > > /usr/local/var/amanda/gnutar-lists/barry_export_home_0.new --sparse > > --ignore-failed-read --totals . > > Total bytes written: -2079072256 > > . > > (no size line match in above gnutar output) > > . > > sendsize: pid 1267 finish time Thu Feb 21 12:37:42 2002 > > Does 2.5 support files larger than 2Gb? I have a feeling support for that > wasn't introduced until 2.5.1 or so. > -- > [EMAIL PROTECTED] - HMC UNIX Systems Manager > My opinions are my own and probably don't represent anything anyway.
Re: Requested to client timed out?
Roger, I am relatively new to Amanda, but I think I might be able to point you in the right direction. If you look in /tmp/amanda on lexus you should find a series of ".debug" files. You will know them when you see them. These are log files that the client keeps and are really handy when something like this pops up. When I am having trouble, I generally move (do not delete) any existing *.debug files to a temporary directory and then run an 'amcheck '. This will generate new *.debug files to read and check for problems. If there are no clues there, then I would look at the older logs. It sounds to me, just based on the report you attached that the client on lexus is just misconfigured. In order for anyone from the list to effectively help you, we will need some additional information. The following questions are a start: Did you install the client software from a pre-compiled 'packaged' file or did you compile from sources? What is the OS of the client (and server, presumably)? What sort of dumps are you running (tar, dump, etc)? Please remember to attach a representative sample of the /tmp/amanda/*.debug logs as well. Best of luck! Jeff On Tue, 2002-03-05 at 02:19, Roger wrote: > Hi I am having problems with my amanda server to back up some of it's own > directories. lexus is my amanda server and also a client. I have not > problems with other clients except lexus itself. > Below is the log that is emailed to me. Anyone encounter such problem and > have a solution for it? > > > These dumps were to tape Daily-06. > The next tape Amanda expects to use is: Daily-07. > > FAILURE AND STRANGE DUMP SUMMARY: > lexus /data lev 0 FAILED [Request to lexus timed out.] > lexus /home/mysql lev 0 FAILED [Request to lexus timed out.] > lexus /home/bugs lev 0 FAILED [Request to lexus timed out.] > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)1:10 > Run Time (hrs:min) 1:16 > Dump Time (hrs:min)0:04 0:03 0:00 > Output Size (meg) 108.1 107.01.1 > Original Size (meg) 146.2 136.59.7 > Avg Compressed Size (%)73.9 78.4 11.6 (level:#disks ...) > Filesystems Dumped4 2 2 (1:1 2:1) > Avg Dump Rate (k/s) 501.0 573.5 38.5 > > Tape Time (hrs:min)0:03 0:03 0:00 > Tape Size (meg) 108.2 107.01.2 > Tape Used (%) 0.90.90.0 (level:#disks ...) > Filesystems Taped 4 2 2 (1:1 2:1) > Avg Tp Write Rate (k/s) 680.9 686.3 401.3 > > > NOTES: > planner: Last full dump of lexus:/home/bugs on tape overwritten in 1 run. > planner: Last full dump of lexus:/home/mysql on tape overwritten in 1 > run. > planner: Last full dump of lexus:/data on tape overwritten in 1 run. > planner: Incremental of astinus:/home/cvs bumped to level 2. > planner: Full dump of astinus:/home/intranet/backup promoted from 11 days > ahead. > planner: Full dump of astinus:/home/szcvs/data promoted from 11 days > ahead. > taper: tape Daily-06 kb 110816 fm 4 [OK] > > > DUMP SUMMARY: > DUMPER STATSTAPER STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > astinus /home/cvs 26760896 13.3 0:17 53.8 0:02 561.9 > astinus -net/backup 0 139730 109504 78.4 3:11 574.0 2:19 787.3 > astinus -me/project 13200256 8.0 0:13 19.2 0:01 208.7 > astinus -szcvs/data 0 10 32 320.0 0:00 136.7 0:21 3.1 > lexus/data 0 FAILED --- > lexus/home/bugs 0 FAILED --- > lexus/home/mysql 0 FAILED --- > > (brought to you by Amanda version 2.4.2p2) > > > Roger > > > >
Re: outgrown my one tape drive (DDS-4) solution; anyrecommendations?
Hi, I am using a Cybernetics CY-8960 stand alone tape drive. It uses 8mm Mammoth-2 cartridges which hold 60GB native / 150GB compressed. Nightly I backup 55 clients and it has performed reasonably well for me. The tapes are pretty expensive, but I think they are cheaper than DLT. Jeff On Wed, 2002-03-06 at 10:39, Johannes Niess wrote: > Gene Matthews <[EMAIL PROTECTED]> writes: > > > Hi all, > > > > I hope this isn't considered off topic. I have been running amanda now > > for a month or so and all is going well (thanks to alot of help from > > this list!). > > > > My tape server is a Sun E250 (Solaris 8) with a single DDS-4 tape > > drive. I'm backing up approximately 15 clients (mostly solaris 8 /linux > > - RH7.2) with three windows boxes. The last windows box I added is > > taking me over the limit. It has 4 large partitions, the largest of > > which can't ever seem to fit on the tape with everything else when it > > does a level 0 dump. > > > > I don't really want to go the manual changer route since the backups are > > cron'd and nobody is around in the middle of the night to change tapes. > > > > I'm starting to look at another tape drive solution and leaning towards > > DLT. I've seen references to AIT-2/AIT-3 also; I'm not sure what that > > is. I'm not up on my tape technology I guess. > > > > I'm thinking of a DLT stacker or maybe a low end DLT tape library. Does > > anyone have any recommendations that they know works well with Amanda? > > There seems to be plenty of h/w to choose from based upon my web > > searches and looking at vendor sites, but I don't want to purchase > > something that isn't going to work with Amanda. > > > > I couldn't find any info like this in the FAQ and my search of the > > archives didn't turn up anything either. > > > > All input very much appreciated! > > > > Thanks, > > > > Gene > > Gene, > > Don't spend money too fast. > > So you're saying that the compressed size of your biggest disklist > entry is over 20 GB on a level 0? > > In this case you could make different disklist entries for all sub > directories, creating new, (hidden $) shares (just for backup). This > works best if the subdir's are somehow constant and no new sibblings > are created. E. g. if you did backup \\nt\c$ , you could backup > \\nt\c$\winnt , \\nt\c$\programms, etc. > > > Or are you just getting "out of tape" errors? > > Amanda will balance the backup levels for you over time. So after a > few cycles the tape with a level 0 of \\nt (current configuration) > will have (high numbered) incrementals of all other partitions. You > could increase "dumpcycle". > > HTH, > > Johannes Nieß
Solution: errors during make
Greetings all, I was having difficulting getting the Amanda client compiled on a Solaris 6 workstation and subsequently found the solution on Google. Here's what I was getting when trying to run make: --- Snip: begin error --- ar cru .libs/libamanda.a alloc.o amflock.o debug.o dgram.o error.o file.o fileheader.o match.o protocol.o regcomp.o regerror.o regexec.o regfree.o security.o statfs.o stream.o token.o util.o version.o versuff.o pipespawn.o ../libtool: ar: not found make[1]: *** [libamanda.la] Error 1 --- Snip: end error --- The solution turned out to be simple. I had to modify my path statement to include "/usr/ccs/bin" and then it compiled fine. I thought I would post this to the list for in order that others may find it when searching. Jeff
Re: amanda and dump->gnuitar
Hi Robert, I by no means an Amanda expert, however I am pretty sure you can mix dump and gnutar in your backups. I think it is simply a matter of adjusting the entries in your disklist. I have been able to use both dump and gnutar without problems. You may need to make sure that your clients have access to the desired program (ie. install gnutar if you don't have it on the client). Jeff On Thu, 2002-03-14 at 02:03, Robert Kearey wrote: > I'm sure this is an obvious FAQ, but anyway ... > > The time has come when I need greater granularity for our backups, so I > want to switch from dump to gnutar. I gather this isn't a simple > proccess - is there a Canonical Way of doing so? > > Mixing dump and gnutar backups in the same tape cycle sounds scary :) > > -- > Rob KeareyWebsite: http://apac.redhat.com > Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer > +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Re: Backups take to long
lding disk
> ##
>
> holdingdisk hd1 {
> comment "main holding disk"
> directory "/export/dumps/amanda" # where the holding disk is
> use -500 Mb # Use all except ~8 GB (leave some for other
>stuff)
> chunksize 8 Gb# size of chunk if you want big dump to be
> # dumped on multiple files on holding disks
> # N Kb/Mb/Gb split disks in chunks of size
> N
> # 0 split disks in INT_MAX/1024 Kb
> chunks
> # -1 same as -INT_MAX/1024 (see
> below)
> # -N Kb/Mb/Gb dont split, dump larger
> # filesystems directly to tape
> # (example: -2 Gb)
> }
>
> ##
> ## Location of log files
> ##
> infofile "/var/adm/amanda/scms/curinfo" # database DIRECTORY
> logdir "/var/adm/amanda/scms" # log directory
> indexdir "/var/adm/amanda/scms/index" # index directory
> tapelist "/var/adm/amanda/scms/tapelist" # list of used tapes
>
> includefile "/opt/amanda/etc/amanda/scms/amanda.conf.tape"
> includefile "/opt/amanda/etc/amanda/scms/amanda.conf.dumptypes"
> includefile "/opt/amanda/etc/amanda/scms/amanda.conf.net"
>
>
> amanda.conf.tape:
>
> ##
> ## Amanda tape config
> ##
> define tapetype DLT {
> comment "DLT tape drives"
> length 2 mbytes # 20 Gig tapes
> filemark 2000 kbytes# I don't know what this means
> speed 1536 kbytes # 1.5 Mb/s
> }
>
> define tapetype DAT {
> comment "DAT tape drives"
> length 1000 mbytes # these numbers are not accurate
> filemark 100 kbytes # but you get the idea
> speed 100 kbytes
> }
>
> # Definition added by jr
> define tapetype DLT7000 {
> comment "DLT-7000 on E450"
> length 35000 mbytes
> filemark 8 kbytes
> speed 10 mbytes
> }
>
>
> amanda.conf.dumptypes:
>
> # SCMS dump types:
> define dumptype winnt {
> global
> comment "Backup of Windows NT clients using Samba"
> compress server fast
> program "GNUTAR"
> }
> define dumptype scms-static {
> global
> comment "Static filesystems with little change"
> compress client fast
> dumpcycle 10
> priority low
> }
>
> define dumptype scms-static-local {
> global
> comment "Static filesystems with little change on local machine"
> compress client fast
> dumpcycle 10
> priority low
> #holdingdisk no
> }
>
> define dumptype scms-homes {
> global
> comment "Home areas on machines"
> compress client fast
> dumpcycle 5
> priority high
> }
>
> define dumptype scms-homes-local {
> global
> comment "Home areas on local server"
> compress client fast
> priority high
> dumpcycle 5
> #holdingdisk no
> }
>
> define dumptype scms-root {
> global
> comment "Root filesystems"
> compress client fast
> priority medium
> dumpcycle 10
> }
>
> define dumptype scms-root-local {
> global
> comment "Root filesystem on local machine"
> compress client fast
> priority medium
> dumpcycle 10
> #holdingdisk no
> }
>
> define dumptype scms-var {
> global
> comment "var filesystems"
> compress client fast
> priority medium
> exclude "/tmp"
> dumpcycle 10
> }
>
> define dumptype scms-var-local {
> global
> comment "var filesystem on local machine"
> compress client fast
> priority medium
> exclude "/tmp"
> dumpcycle 10
> #holdingdisk no
> }
>
> define dumptype scms-comp {
> global
> comment "Disks to be compressed"
> compress client fast
> }
>
> define dumptype scms-comp-local {
> global
> comment "local disks to be highly compressed"
> compress client fast
> #holdingdisk no
> }
>
> define dumptype scms-nocomp {
> global
> comment "Disks which aren't compressed"
> compress none
> }
>
> define dumptype scms-gnutar {
> global
> program "GNUTAR"
> comment "Disks using GNU tar"
> compress server fast
> }
>
>
> amanda.conf.net:
>
> ##
> ## amanda.conf.net
> ## Network interface definitions
> ##
>
> define interface local {
> comment "a local disk"
> use 1 kbps
> }
>
> #define interface le0 {
> #comment "10 Mbps ethernet"
> #use 400 kbps
> #}
>
> #define interface hme0 {
> #comment "100 Mbps ethernet"
> #use 4000 kbps
> #}
>
> define interface qfe0 {
> comment "Quad fast ethernet 0"
> use 6000 kbps
> }
>
> define interface qfe1 {
> comment "Quad fast ethernet 1"
> use 6000 kbps
> }
>
> define interface qfe2 {
> comment "Quad fast ethernet 2"
> use 6000 kbps
> }
>
> define interface qfe3 {
> comment "Quad fast ethernet 3"
> use 6000 kbps
> }
>
>
>
--
++
| Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] |
| Sky Computers, Inc. (www.skycomputers.com) |
++
Re: Other problems...
Hi Richard, Hang in there! I think I can offer a little help. Rather than going to the trouble of compiling gcc, which can be a bit intimidating, perhaps you may like to download a PKG. If you go to http://www.sunfreeware.com you can browse to the pages for both Solaris versions you have and download the appropriate gcc. Once you have them downloaded, 'gunzip' them and run a 'pkgadd' to install. I have found that works well for me. You need to make sure you have enough space in your "/usr/local/" partition because that is where these packages like to install themselves. Additionally, you may need to get new versions of: Tar, GZip, Flex, and Make. I found that after updating these programs it was much easier to compile Amanda. I hope this helps! Jeff -- +--------+ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Problems with very large dumps
Hi Trevor, You may want to check your chunksize. I have mine set to 1GB so large backups are split into 1GB files. Additionally you may need, even on Solaris 8, to update tar & gzip such that they will be able to handle the larger files. You could also effect this in your disklist. Rather than having an entry such as: systemname /export/homecomp-root-tar You could have more than one entry, breaking down the directories into individual dumps: systemname /export/home/dir1 comp-root-tar systemname /export/home/dir2 comp-root-tar systemname /export/home/dir3 comp-root-tar I am not certain these are the best solutions, but I am pretty sure they will work. Best of luck! Jeff -- ++ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: question to the audience.....
Hi Dan, I can't speak for everyone, but I think we'd all agree that more is better. I, for one, would be very interested. Jeff On Tue, 2002-03-26 at 08:18, Don Potter wrote: > I'm sure we all have a selection of scripts that we use to make our > backup lives that much easier. Would there be any objections posting > any scripts that we find to be prudent to this mailer. Majority of mine > are quick and nasty bourne scripts which can be pasted in, but they > could prove to be useful out there. > > Just inquiring to see if there is a interest. > Don -- +--------+ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Error in Debian
Hi Pablo, I believe the source of the error you mention is from the client. You may need to check the ".amandahosts" file on the client for the user under which the client runs. In other words, if in your INETD (or XINETD) the amanda client runs as "backup", the ".amandahosts" in backup's home directory probably needs to be adjusted. I hope this helps you! Jeff On Wed, 2002-03-27 at 12:06, Pablo Miscevich wrote: > I´am running amanda 2.4.2p2 in debian linux (installing from apt-get > ) > My error is : > ERRROR: backup: [access as backup not allowed from backup@backup] > amandahostsauth failed > > Who is my problem? > > Who is the diference in Debian and other linux distributions? -- +--------+ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Amanda Tapedrives
Hi Jose, I have a Cybernetics CY-8960 tape drive. It uses Mammoth-2 8mm cartridges (225m) which store 60GB native & 150GB compressed. I have been backing up 60+ partitions per night with little trouble. Jeff On Wed, 2002-04-17 at 13:58, Jose Pereira Van-Dunem wrote: > > Hello Everybody, > > I intend to install Amanda on a RedHat Linux 7.1 box. > I am afraid of buying a tapedrive that do NOT work nice with Amanda. > So, I would like to have your help on what tapedrive (make and models) do you >recommend me to buy ! > Your suggestion will be well appreciated ! > Thanks in advance. > > > Jose Pereira Van-Dunem > > EBONet / PAcomm Systems > > -- +--------+ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Guidelines/suggestions for backing up a large RAID array?
Hi David, I am no expert on this, however I think you may run into problems with that approach. Amanda expects consistency with the disk list and if you changed it each night, I think you'd have trouble with restores and Amanda would have trouble keeping track of the level of backup needed. I think a more workable approach would be to determine or identify directories that contain less than 50GB of data and make entries in your disk list accordingly. In fact, you could have several entries in your disklist for that partition, on a subdirectory by subdirectory basis... I hope this helps. Jeff On Tue, 2002-04-23 at 14:20, David Trusty wrote: > Hi, > > I am working with a very large RAID array which needs backing-up. > > The array has 3 partitions, each containing approximately > 150GB of files. > > I have a tape changer with 20 tapes, each holding 50GB of data. > > Since amanda currently will not back up a disk larger than a > tape, I believe I need to specify smaller peices of the partitions > in my disklist. What I am thinking about doing is writing a script > which scans the partitions down to a certain depth and generates > a disklist of peieces small enough to backup onto a single tape, > using the GNUTAR method. > > Has anyone had a similar problem, and had any other solutions? > > Also, what is the effect on amanda of changing the disklist > (perhaps every night)? The changes (when they occur) will all > be different subpaths of the same partitions. Will this get > amanda confused, or make it back up a lot of extra files, or > is the gtar indexing able to handle this situation? > > Thanks in advance!! > > David > > > > > _ > MSN Photos is the easiest way to share and print your photos: > http://photos.msn.com/support/worldwide.aspx -- ++ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Problems with NT clients
Hi Jesús, I don't know if I can answer your questions but I do see some things that may help you out. > i've mounted the exported directories of the NT client in my tape server > using smbmount: > > smbmount //JOSAN/nem /mnt/josanNem -U Administrador > > Then i add the proper line to the disklist file: > > mordor.nuevomundo.es /mnt/josanNem high-tar2 > --snip-- > But when i make the backups, the mail that amanda sent to me says this: > > FAILURE AND STRANGE DUMP SUMMARY: mordor.nue /mnt/josanNem lev 0 FAILED > [disk /mnt/josanNem offline on mordor.nuevomundo.es?] > Ok, well I can't really offer any advice on that part. I think you'd have to check the logs in /tmp/amanda on mordor.neuvomundo.es for more clues. I understand with the above approach you are mounting the drive and then including it in your backup just like any other *nix disk. > I've tried another form: > > i've utilized the amandapass file: > > amandapass file > //josan/nem pijos > It's not clear to me if "pijos" is the username or the password, but I am guessing that is the password. With that assumption in mind, I believe you need to include the username in your amandapass file. (ie. //josan/nemusername%pijos) > The disklist line: > > mordor.nuevomundo.es //josan/nem/ high-tar2 > > The error: > > FAILURE AND STRANGE DUMP SUMMARY: > mordor.nue //josan/nem/ lev 0 FAILED [missing result for //josan/nem/ > in mordor.nuevomundo.es response] > > the amcheck output: > > Amanda Backup Client Hosts Check > > ERROR: mordor.nuevomundo.es: [cannot find password for //josan/nem/] > Client check: 4 hosts checked in 0.388 seconds, 1 problem found --snip-- > what is happening? I have been struggling with the smbclient setup today and just happened to see this. I hope it helps you! -- ++ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Trouble getting SAMBA to work with AMANDA
CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" amandad:GNUTAR="/bin/gtar" COMPRESS_PATH="/bin/gzip" amandad:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="zeus" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="zeus" DEFAULT_TAPE_DEVICE="/dev/null" amandad:HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID amandad:DEBUG_CODE 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: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-A0AA0808 SEQ 1039115909 SECURITY USER amanda SERVICE noop OPTIONS features=feff9f00; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 000-A0AA0808 SEQ 1039115909 amandad: time 0.001: bsd security: remote host garfield user amanda local user amanda amandad: time 0.001: amandahosts security check passed amandad: time 0.001: running service "noop" amandad: time 0.002: sending REP packet: Amanda 2.4 REP HANDLE 000-A0AA0808 SEQ 1039115909 OPTIONS features=feff9f00; amandad: time 0.008: got packet: Amanda 2.4 ACK HANDLE 000-A0AA0808 SEQ 1039115909 amandad: time 0.008: pid 25909 finish time Thu Dec 5 14:18:29 2002 -- -> amandad.*.debug (2 of 2 generated) from /tmp/amanda on zeus -- amandad: debug 1 pid 25910 ruid 33 euid 33: start at Thu Dec 5 14:18:29 2002 amandad: version 2.4.3 amandad: build: VERSION="Amanda-2.4.3" amandad:BUILT_DATE="Thu Dec 5 11:17:51 EST 2002" amandad:BUILT_MACH="Linux zeus 2.4.18-18.7.x #1 Wed Nov 13 20:29:30 EST 2002 i686 unknown" amandad:CC="gcc" amandad:CONFIGURE_COMMAND="'./configure' '--with-user=amanda' '--with-group=disk'" 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/" amandad:RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" amandad:GNUTAR="/bin/gtar" COMPRESS_PATH="/bin/gzip" amandad:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="zeus" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="zeus" DEFAULT_TAPE_DEVICE="/dev/null" amandad:HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID amandad:DEBUG_CODE 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: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-68AF0808 SEQ 1039115910 SECURITY USER amanda SERVICE selfcheck OPTIONS features=feff9f00;maxdumps=1;hostname=zeus; GNUTAR //meggie/c$ 0 OPTIONS |;auth=bsd; GNUTAR //frenchfry/barcode 0 OPTIONS |;auth=bsd; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 000-68AF0808 SEQ 1039115910 amandad: time 0.001: bsd security: remote host garfield user amanda local user amanda amandad: time 0.001: amandahosts security check passed amandad: time 0.001: running service "/usr/local/libexec/selfcheck" amandad: time 0.651: sending REP packet: Amanda 2.4 REP HANDLE 000-68AF0808 SEQ 1039115910 OPTIONS features=feff9f00; OK //meggie/c$ OK //meggie/c$ OK \\meggie\c$ OK //frenchfry/barcode OK //frenchfry/barcode OK \\frenchfry\barcode OK /bin/gtar executable OK /etc/amandates read/writable OK /usr/local/var/amanda/gnutar-lists/. read/writable OK /usr/bin/smbclient executable OK [/etc/amandapass is readable, but not by all] OK /bin/gzip executable OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: time 0.653: got packet: Amanda 2.4 ACK HANDLE 000-68AF0808 SEQ 1039115910 amandad: time 0.653: pid 25910 finish time Thu Dec 5 14:18:30 2002 -- -- ++ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Trouble getting SAMBA to work with AMANDA
Richard, Thanks for your reply. I checked and found that the Win98 client's share was set to read only and the "backup" account on the Win2k client was in the "backup operators" group. I changed the Win98 share to full access and changed the Win2k "backup" account to the "administrators" group. Unfortunately there was no change in the results. I still have the same logs and report. :( Any other ideas? :) Jeff -- +--------+ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Trouble getting SAMBA to work with AMANDA
I will give that a try tomorrow (the ntbackup approach). Sounds like a great idea. I double checked the "backup" account on the Win2k box. It is in the administrators group, so I am fairly certain is has full control. I failed to mention in my last reply that the drive on this one is NTFS, not FAT. Your ntbackup approach sounds perfect as I believe that would preserve all the permissions. I am not sure how the smbclient approach handles permissions, etc. I will try the backup again tomorrow with a subdirectory instead of the entire disk. If I can get that to work, I will use your ntbackup idea. I also checked the Win95 box again and I have the share set to full-control. I'm not sure what is going on there. Of course this drive is FAT32. I am completely baffled. If I mount the shares on zeus, I have no problems. I can move around and copy files and everything seems fine. I didn't think of checking the samba lists...I will take a peek over there tomorrow, too...it's been a long day. Thanks again for your help! Jeff On Thu, 2002-12-05 at 16:25, Richard B. Tilley (Brad) wrote: > On the 2000 box, be certain that the user that smbclient uses to access > the share has full-control over the files within that share. In order to > avoid this problem, I us ntbackup to create an archive of all the files > that I want backed-up and then only allow access to the user that > amanda/smbclient uses to get to that file. And, I give that user > full-control. If possible, it's best to create a separate partition > formated NTFS so you can control access. > > I do this on 75 2000 boxes without problems. I have an old 95 box that > used to display the same error that you listed, but when I set its share > to full-control, the error stopped and amanda worked just fine. I read > someplace once (a long time ago) that the user that smbclient uses to > access the shares has to have write/change ability in order to do > incrementals. > > Maybe someone else (more familiar with this) can go into this more. Try > the samba list too. > -- ++ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Trouble getting SAMBA to work with AMANDA
Sorry I forgot to mention this in my previous reply. I did mention it in my last reply, but I think it was still in transit. The Win2K box is NTFS. The Win98 is FAT32. I checked the permissions and on the Win98 box it is now set to full-control. I checked on the Win2k box and changed the "backup" account from backup operators group to administrators. Unfortunately, no change in the backup results. The report & logs look just the same... I will try a subdirectory (rather than the entire C: drive) on the Win2k box tomorrow and will make the it owned with full access for the "backup" account. If that works, I should be able to use your ntbackup approach. :) Jeff On Thu, 2002-12-05 at 15:37, Richard B. Tilley (Brad) wrote: > On the Windows shares, I'm assuming that they are both fat partitions. > You must allow full-control of the share, not just read (or whatever MS > calls it). > > -- +--------+ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
Re: Trouble getting SAMBA to work with AMANDA
Hi Tom, Thanks for that command. I tried it out and don't see any problems right off. Here are the results: -- [amanda@zeus /]# smbclient '\\frenchfry\barcode' amanda -d 3 -U backup -c 'recurse;dir' added interface ip=10.0.0.65 bcast=10.0.0.255 nmask=255.255.255.0 Client started (version 2.2.1a). resolve_lmhosts: Attempting lmhosts lookup for name frenchfry<0x20> resolve_hosts: Attempting host lookup for name frenchfry<0x20> Connecting to 10.0.0.3 at port 139 directory recursion is now on received 3 entries (eos=1) .D0 Tue Feb 26 15:08:46 2002 .. D0 Tue Feb 26 15:08:46 2002 filecopy D0 Fri Apr 5 09:38:28 2002 \filecopy received 9 entries (eos=1) .D0 Fri Apr 5 09:38:28 2002 .. D0 Fri Apr 5 09:38:28 2002 cmdlist.txt A 747 Wed Aug 11 15:34:14 1999 AUTOLOG.TXT A 233 Tue Feb 26 15:30:24 2002 EXE2ABS.EXE A17793 Thu Apr 29 11:21:30 1999 t24fcopy.exe A 604160 Tue Jan 16 15:16:14 2001 itcfc.dllA81920 Thu May 20 11:56:12 1999 FileCopy4.3.exe A 531607 Tue Feb 26 15:09:48 2002 IMFILECP.INI A 529 Mon Aug 19 09:56:22 2002 38919 blocks of size 524288. 34291 blocks available Total bytes listed: 1236989 -- It looks to me like SAMBA is working properly. I can mount the share and the smbclient command works fine for reporting the size. I was also seeing the size reported correctly in the Amanda logs. Jeff On Thu, 2002-12-05 at 17:35, Tom Schutter wrote: > I pulled this comment from my disklist file: > # PCs via Samba > # If you edit this section, you must also edit ./amandapass > # To test a new entry, use the commands: > # smbclient '\\HOST\backup' PASSWORD -d 3 -U USER -c 'recurse;dir' > # amcheck -c daily > > The smbclient command is what the estimation phase sends to the PC. > By running it from a command prompt, you usually can find the problem. > Don't forget to replace HOST, PASSWORD, and USER when running the > command. > -- ++ | Jeffery Smith - Systems Administrator - [EMAIL PROTECTED] | | Sky Computers, Inc. (www.skycomputers.com) | ++
