Re: Amanda, FreeBSD, HP SureStore DAT 40 config file?
At 08:41 1/13/2002, Gene Heskett, wrote: Amanda, left to its own devices, does its own scheduleing as it attempts to make the most efficient useage of the available tape. You can force a full if you'd like, and that could be put into the crontab for automatic also. Hi Gene, Thanks for your answer! How would I do this? Do you have samples for: 1. Config files, 2. Crontab entry 3. Tape Type entry On Sunday 13 January 2002 01:16 am, W. D. wrote: Hi Folks, Does anyone have this configuration? If so, can you give me some simple and straightforward instructions on how to get this working? One scenario: Backup of ALL files ON DEMAND. Second Scenario: Backup of ALL files Sunday night, Incremental other 6 nights What would the config file look like? Any other gotchas? Thanks for any light you can shed! -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.3+% setiathome rank, not too shabby for a hillbilly Start Here to Find It Fast!© - http://www.US-Webmasters.com/start.htm
Re: backup Mac files on Windoze
Brian we do this without any problems. BUT the servers in Question are Unix (running netatalk or Pacers now defunct appletalk stuff) or running off a SNAP server which we use smblient to backup. What happens if you try and open the file with w2k - do you still get the error? -- Martin Brian Whitehead wrote: I ran a backup of a Win2K Server using Amanda with smbclient tonight. It worked perfectly with the exception of Macintosh created files. Is there any special configuration that can be done to make it handle these files. It gives an error NT_STATUS_FILE_NOT_FOUND, or something similar. The files do exist and can be seen just fine, but they have special characters in the name that MacOS creates. If anyone has worked around this type of problem let me know. I did copy these files across using the mget command in a smbclient session without a problem. Brian W.
Port not secure, problem
Hi everyone I hope that you can help me. Well, when i execute the command #su amanda -c /software/amanda/sbin/amcheck -c amanda The output is Amanda Backup Client Hosts Check ERROR: wendy: [host sc01us0105: port 10087 not secure] ERROR: frostis: [host sc01us0105.cf.jcyl.es: port 10087 not secure] Client check: 2 hosts checked in 0.068 seconds, 2 problems found (brought to you by Amanda 2.4.2p2) does anybody tell me why? --- Javier Fernández Pérez Servicio de Informática Corporativa D.G. de Telecomunicaciones y Transportes Consejería de Fomento - Junta de Castilla y León Rigoberto Cortejoso, 14. 47014 Valladolid (Spain) e-mail: [EMAIL PROTECTED] ---
Re: Amanda, FreeBSD, HP SureStore DAT 40 config file?
On Monday 14 January 2002 03:14 am, W. D. wrote: At 08:41 1/13/2002, Gene Heskett, wrote: Amanda, left to its own devices, does its own scheduleing as it attempts to make the most efficient useage of the available tape. You can force a full if you'd like, and that could be put into the crontab for automatic also. Hi Gene, Thanks for your answer! How would I do this? Do you have samples for: 1. Config files, 2. Crontab entry 3. Tape Type entry I'll try and answer this tonight. This morning, when I looked, amdump didn't run to completion here. Sometime in the night, my samba link to another machine did something, locking up an 'ls' of the supposedly mounted directory so tight it couldn't be killed! The only link left was the shell I had ssh'd to it, running ksetispy in the background so I could watch both machines. amcheck eventually timed out too, and at 20:31 last night, all was well. I wound up rebooting both machines. amcheck now runs normally, but it appears something is foobared for sure. On Sunday 13 January 2002 01:16 am, W. D. wrote: Hi Folks, Does anyone have this configuration? If so, can you give me some simple and straightforward instructions on how to get this working? One scenario: Backup of ALL files ON DEMAND. Second Scenario: Backup of ALL files Sunday night, Incremental other 6 nights What would the config file look like? Any other gotchas? Thanks for any light you can shed! -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.3+% setiathome rank, not too shabby for a hillbilly Start Here to Find It Fast!© - http://www.US-Webmasters.com/start.htm -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.3+% setiathome rank, not too shabby for a hillbilly
lev 1 ERROR [not in disklist]
hello, I have an AIX v4.2.1 box running Amanda v2.4.2p2 I set it up to backup the directory where we dump our database exports to, however, i get this error after amdump runs: FAILURE AND STRANGE DUMP SUMMARY: ibmbld1.us /dbexports lev 1 ERROR [not in disklist] This is the entry in my disklist file: aix421.us.lhsgroup.com /dbexports always-full can anyone suggest what the problem might be? i did add this entry a few days after i set up amanda on that box and i ran several backups of other local filesystems, however, that shouldn't be a problem, right? Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799[EMAIL PROTECTED]
[data write: File too large]
hello again, my aix 4.2.1 box running Amanda v2.4.2p2 is not backing up one of my filesystems at level 0 anymore, it did it only once (the first amdump run). here is the error: aix421.us.lhsgroup.com /home4/bscs_fam lev 0 FAILED [data write: File too large] here is the entry in my amanda.conf file chunksize 1536 mbytes can you suggest anything? thanks in advance. Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799[EMAIL PROTECTED]
Re: [data write: File too large]
On Mon, Jan 14, 2002 at 10:03:57AM -0500, Rivera, Edwin wrote: my aix 4.2.1 box running Amanda v2.4.2p2 is not backing up one of my filesystems at level 0 anymore, it did it only once (the first amdump run). here is the error: aix421.us.lhsgroup.com /home4/bscs_fam lev 0 FAILED [data write: File too large] here is the entry in my amanda.conf file chunksize 1536 mbytes can you suggest anything? thanks in advance. 2GB limit on files perhaps? Not sure about AIX 4.2.1-support for files bigger 2GB, quit AIX with version 3.2.5. Might be the holding-disk-file. Regards, Adrian Reyer -- Adrian Reyer Fon: +49 (7 11) 2 85 19 05 LiHAS - Servicebuero SuttgartFax: +49 (7 11) 5 78 06 92 Adrian Reyer Joerg Henner GbR Mail: [EMAIL PROTECTED] Linux, Netzwerke, Consulting Support http://lihas.de/
RE: lev 1 ERROR [not in disklist]
sorry, it's not aix421 as listed below, the machine names do match in the disklist and report files.. it should be: FAILURE AND STRANGE DUMP SUMMARY: ibmbld1.us /dbexports lev 1 ERROR [not in disklist] This is the entry in my disklist file: ibmbld1.us.lhsgroup.com /dbexports always-full ..monday morning.. -Original Message- From: Rivera, Edwin [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: lev 1 ERROR [not in disklist] hello, I have an AIX v4.2.1 box running Amanda v2.4.2p2 I set it up to backup the directory where we dump our database exports to, however, i get this error after amdump runs: FAILURE AND STRANGE DUMP SUMMARY: ibmbld1.us /dbexports lev 1 ERROR [not in disklist] This is the entry in my disklist file: aix421.us.lhsgroup.com /dbexports always-full can anyone suggest what the problem might be? i did add this entry a few days after i set up amanda on that box and i ran several backups of other local filesystems, however, that shouldn't be a problem, right? Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799[EMAIL PROTECTED]
RE: [data write: File too large]
Could be that your holding disk space is to small, or you trying to backup a file that is larger than 2 gigs? Thats all I can come up with. Pedro -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rivera, Edwin Sent: Monday, January 14, 2002 10:04 AM To: [EMAIL PROTECTED] Subject: [data write: File too large] hello again, my aix 4.2.1 box running Amanda v2.4.2p2 is not backing up one of my filesystems at level 0 anymore, it did it only once (the first amdump run). here is the error: aix421.us.lhsgroup.com /home4/bscs_fam lev 0 FAILED [data write: File too large] here is the entry in my amanda.conf file chunksize 1536 mbytes can you suggest anything? thanks in advance. Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799[EMAIL PROTECTED]
RE: [data write: File too large]
You sure you don't have a huge file in that filesystem? Pedro -Original Message- From: Rivera, Edwin [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 10:55 AM To: Pedro Aguayo; Rivera, Edwin; [EMAIL PROTECTED] Subject: RE: [data write: File too large] my holding disk is 4GB and i have it set to use -100Mbytes i'm confused on this one.. -Original Message- From: Pedro Aguayo [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 10:53 AM To: Rivera, Edwin; [EMAIL PROTECTED] Subject: RE: [data write: File too large] Could be that your holding disk space is to small, or you trying to backup a file that is larger than 2 gigs? Thats all I can come up with. Pedro -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rivera, Edwin Sent: Monday, January 14, 2002 10:04 AM To: [EMAIL PROTECTED] Subject: [data write: File too large] hello again, my aix 4.2.1 box running Amanda v2.4.2p2 is not backing up one of my filesystems at level 0 anymore, it did it only once (the first amdump run). here is the error: aix421.us.lhsgroup.com /home4/bscs_fam lev 0 FAILED [data write: File too large] here is the entry in my amanda.conf file chunksize 1536 mbytes can you suggest anything? thanks in advance. Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799[EMAIL PROTECTED]
RE: [data write: File too large]
yeah, it's a CVMC filesystem with a ton of small flat files, no large individual files.. only .c and .h files and things like that. -Original Message- From: Pedro Aguayo [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 11:00 AM To: Rivera, Edwin; [EMAIL PROTECTED] Subject: RE: [data write: File too large] You sure you don't have a huge file in that filesystem? Pedro -Original Message- From: Rivera, Edwin [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 10:55 AM To: Pedro Aguayo; Rivera, Edwin; [EMAIL PROTECTED] Subject: RE: [data write: File too large] my holding disk is 4GB and i have it set to use -100Mbytes i'm confused on this one.. -Original Message- From: Pedro Aguayo [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 10:53 AM To: Rivera, Edwin; [EMAIL PROTECTED] Subject: RE: [data write: File too large] Could be that your holding disk space is to small, or you trying to backup a file that is larger than 2 gigs? Thats all I can come up with. Pedro -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rivera, Edwin Sent: Monday, January 14, 2002 10:04 AM To: [EMAIL PROTECTED] Subject: [data write: File too large] hello again, my aix 4.2.1 box running Amanda v2.4.2p2 is not backing up one of my filesystems at level 0 anymore, it did it only once (the first amdump run). here is the error: aix421.us.lhsgroup.com /home4/bscs_fam lev 0 FAILED [data write: File too large] here is the entry in my amanda.conf file chunksize 1536 mbytes can you suggest anything? thanks in advance. Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799[EMAIL PROTECTED]
Re: S.O.S.
I use for test tapes of 2 GBytes. Is not Amanda multi-volume? Em Sex 11 Jan 2002 19:03, Joshua Baker-LePain escreveu: On Fri, 11 Jan 2002 at 6:31pm, Túlio Machado de Faria wrote I am using: tpchanger chg-multi for automatically dumb of unit. You cannot have a single filesystem (disklist entry) that is bigger than your tapes -- amanda doesn't span. How big are your tapes?
Re: S.O.S.
On Mon, 14 Jan 2002 at 3:05pm, Túlio Machado de Faria wrote I use for test tapes of 2 GBytes. Is not Amanda multi-volume? Amanda can use multiple tapes in one run (see 'runtapes'), but cannot span a single disklist entry across multiple tapes. In other words, each filesystem must be smaller than your tapes. Note that you can backup subdirectories of partitions with tar, in order to achieve this. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
smbclient question
I have about 60 MS clients, and currently, they are all mounted by smbclient through the AMANDA backup server. I have a few other Linux machines that are backed up too, and I was wondering if it would be better to spread these SAMBA mounts out across 2 or 3 other Linux machines. So, instead of mounting 60 MS clients on the Amanda server, spread the 60 out across 3 Linux machines. Or does it matter? Any advice is appreciated. -- Brad
Re: S.O.S.
using parametro: program GNUTAR in amanda.conf it does not function? Em Seg 14 Jan 2002 15:08, Joshua Baker-LePain escreveu: On Mon, 14 Jan 2002 at 3:05pm, Túlio Machado de Faria wrote I use for test tapes of 2 GBytes. Is not Amanda multi-volume? Amanda can use multiple tapes in one run (see 'runtapes'), but cannot span a single disklist entry across multiple tapes. In other words, each filesystem must be smaller than your tapes. Note that you can backup subdirectories of partitions with tar, in order to achieve this.
Re: S.O.S.
On Mon, 14 Jan 2002 at 5:49pm, Túlio Machado de Faria wrote using parametro: program GNUTAR in amanda.conf it does not function? What does not function? AMANDA will not split a single disklist entry across multiple tapes. I don't know that I can make it any clearer. If you have a filesystem/disklist entry that is bigger than your tapes, you need to use program GNUTAR and split the filesystem in multiple disklist entries. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: S.O.S.
span a single disklist entry across multiple tapes Em Seg 14 Jan 2002 17:58, Joshua Baker-LePain escreveu: On Mon, 14 Jan 2002 at 5:49pm, Túlio Machado de Faria wrote using parametro: program GNUTAR in amanda.conf it does not function? What does not function? AMANDA will not split a single disklist entry across multiple tapes. I don't know that I can make it any clearer. If you have a filesystem/disklist entry that is bigger than your tapes, you need to use program GNUTAR and split the filesystem in multiple disklist entries.
Re: smbclient question
On Mon, 14 Jan 2002, R. Bradley Tilley wrote: I have about 60 MS clients, and currently, they are all mounted by smbclient through the AMANDA backup server. I have a few other Linux machines that are backed up too, and I was wondering if it would be better to spread these SAMBA mounts out across 2 or 3 other Linux machines. So, instead of mounting 60 MS clients on the Amanda server, spread the 60 out across 3 Linux machines. Or does it matter? Any advice is appreciated. Seems rather Rube Goldberg to me. Why add an extra level of complexity for yourself when trying to debug problems? Brandon D. Valentine -- Iam mens praetrepidans avet vagari. - G. Valerius Catullus, Carmina, XLVI
XFS, Linux, and Amanda
I am going slowly nuts (ok, so I'm already there :) trying to get Amanda to backup my XFS partitions. I've rebuilt from source (CVS), configured it with XFS, and even used strings on the executables to prove that the xfsdump command is making it in there. However, I still get the following in my nightly backups: FAILURE AND STRANGE DUMP SUMMARY: morpheus hde11 lev 0 FAILED [disk hde11 offline on morpheus?] morpheus hde10 lev 0 FAILED [disk hde10 offline on morpheus?] and so on Any ideas of what I can look for? I can't find anything in the list archives or the Yahoo Amanada group that seems to help. Thanks! -- Dan Rich [EMAIL PROTECTED] | http://www.employees.org/~drich/ | Step up to red alert! Are you sure, sir? | It means changing the bulb in the sign... | - Red Dwarf (BBC)
Re: XFS, Linux, and Amanda
On Mon, 14 Jan 2002 at 1:17pm, Dan Rich wrote FAILURE AND STRANGE DUMP SUMMARY: morpheus hde11 lev 0 FAILED [disk hde11 offline on morpheus?] morpheus hde10 lev 0 FAILED [disk hde10 offline on morpheus?] and so on Any ideas of what I can look for? I can't find anything in the list archives or the Yahoo Amanada group that seems to help. What is in /tmp/amanda/sendbackup*debug and /tmp/amanda/amandad*debug on morpheus at the time(s) of the attempted dump(s)? What distribution? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: S.O.S.
At 06:42 PM 1/14/2002 -0200, you wrote: span a single disklist entry across multiple tapes If you are saying this is what does not function, no it doesn't. It isn't supposed to. So it is not a question of not functioning but of not designed to do this. If you want the backup of one filesystem to go to more than one tape, you have to change your dumptype. In the sampleamanda.config file, there are dumptypes labelled -tar. In your disks configuration file, make sure you use a dumptype of -tar for this disk.That way, it should use tar to do the backup, and not dump. Also, you would specify a sub-directory on the filesystem, not the top of the disk-tree.Pick a sub-directory which will fit onto one tape. Make anotherxxx-tar entry for the next sub-directory.And so on. Clearer? Deb Baddorf P.S. theoretical knowledge only; still looking for time to setup my first amanda system Em Seg 14 Jan 2002 17:58, Joshua Baker-LePain escreveu: On Mon, 14 Jan 2002 at 5:49pm, Túlio Machado de Faria wrote using parametro: program GNUTAR in amanda.conf it does not function? What does not function? AMANDA will not split a single disklist entry across multiple tapes. I don't know that I can make it any clearer. If you have a filesystem/disklist entry that is bigger than your tapes, you need to use program GNUTAR and split the filesystem in multiple disklist entries. --- Deb Baddorf [EMAIL PROTECTED] 840-2289 You can't help getting older, but you don't have to get old. - George Burns IXOYE
Re: smbclient question
On Monday 14 January 2002 04:13 pm, you wrote: On Mon, 14 Jan 2002, R. Bradley Tilley wrote: I have about 60 MS clients, and currently, they are all mounted by smbclient through the AMANDA backup server. I have a few other Linux machines that are backed up too, and I was wondering if it would be better to spread these SAMBA mounts out across 2 or 3 other Linux machines. So, instead of mounting 60 MS clients on the Amanda server, spread the 60 out across 3 Linux machines. Or does it matter? Any advice is appreciated. What I've seen is the change in the response time. But if your response time is good enough, leave it alone. F.ex. if you ran some big db which hauled all the data back and forth on all pc's you'd end up with heave network load. On the other hand if load is light you would not see any difference. Also, I would build a bigger server before I spread it over several machines. Use minimum 100MB network with switches rather than hubs. I have fourty machines running a stupid DOS db app. It has 115 files open per user! (I'm having it redone) We have no problem with access. My smaller server is a dual 700MHz PIII Coppermine with a mere 256MB RAM. It's feeding this old DOS db for all just fine. (It used to be fed OK by a single 600MHz with 256MB running NT.) Besides, how would you solve three servers feeding the same data? Clusters would probably be the only practical way to go. Steve -- Steve Szmidt V.P. Information Video Group Distributors, Inc.
Re: XFS, Linux, and Amanda
On Mon, 14 Jan 2002, Joshua Baker-LePain wrote: On Mon, 14 Jan 2002 at 1:17pm, Dan Rich wrote FAILURE AND STRANGE DUMP SUMMARY: morpheus hde11 lev 0 FAILED [disk hde11 offline on morpheus?] morpheus hde10 lev 0 FAILED [disk hde10 offline on morpheus?] and so on Any ideas of what I can look for? I can't find anything in the list archives or the Yahoo Amanada group that seems to help. What is in /tmp/amanda/sendbackup*debug and /tmp/amanda/amandad*debug on morpheus at the time(s) of the attempted dump(s)? A *whole* lot of data. :) The sendbackup log only shows my one ext2 partition. The amandad log looks good for all the partitions. The debug log that worries me is the sendsize log: calculating for amname 'hde11', dirname '/misc/mp3' sendsize: getting size via dump for hde11 level 0 sendsize: running /sbin/dump 0Ssf 1048576 - /dev/hde11 running /usr/lib/amanda/killpgrp /dev/hde11: Bad magic number in super-block while opening filesystem . (no size line match in above dump output) . asking killpgrp to terminate Shouldn't it be using xfsdump instead of dump to determine the size? Oh, I should have mentioned, it's working fine for my non-XFS partitions. What distribution? Redhat 7.0 with lots of packages replaced (mostly upgrades). The system is running a 2.4.9 kernel. -- Dan Rich [EMAIL PROTECTED] | http://www.employees.org/~drich/ | Step up to red alert! Are you sure, sir? | It means changing the bulb in the sign... | - Red Dwarf (BBC)
Re: XFS, Linux, and Amanda
On Mon, 14 Jan 2002 at 2:08pm, Dan Rich wrote On Mon, 14 Jan 2002, Joshua Baker-LePain wrote: What is in /tmp/amanda/sendbackup*debug and /tmp/amanda/amandad*debug on morpheus at the time(s) of the attempted dump(s)? A *whole* lot of data. :) The sendbackup log only shows my one ext2 There would be a senbackup log for every partition backed up, but... partition. The amandad log looks good for all the partitions. The debug log that worries me is the sendsize log: calculating for amname 'hde11', dirname '/misc/mp3' sendsize: getting size via dump for hde11 level 0 sendsize: running /sbin/dump 0Ssf 1048576 - /dev/hde11 running /usr/lib/amanda/killpgrp /dev/hde11: Bad magic number in super-block while opening filesystem . (no size line match in above dump output) . asking killpgrp to terminate Shouldn't it be using xfsdump instead of dump to determine the size? Indeed it should, and that's your problem -- amanda isn't getting estimates for your XFS partitions. I assume that xfsdump was present when you ./configured amanda, right? What does your fstab look like? Can you try again with either 2.4.2p2 (plus the advfs patch) or 2.4.3b2? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: XFS, Linux, and Amanda
On Mon, 14 Jan 2002 at 2:57pm, Dan Rich wrote I found part of the problem, it appears that the original RPM I installed installs things in a very different location from make install. Amdump was running the wrong copy of sendsize. Now that that is fixed, I can start figuring out the next error :) Hmmm, you did 'rpm -e' the RPM version, right? Pre-build amanda=bad. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: XFS, Linux, and Amanda
* Joshua Baker-LePain ([EMAIL PROTECTED]) [020114 15:37]: On Mon, 14 Jan 2002 at 2:57pm, Dan Rich wrote I found part of the problem, it appears that the original RPM I installed installs things in a very different location from make install. Amdump was running the wrong copy of sendsize. Now that that is fixed, I can start figuring out the next error :) Hmmm, you did 'rpm -e' the RPM version, right? Pre-build amanda=bad. Although that has been my general experience as well, the RedHat 7.1/7.2 RPMs work well enough in my setup, which is fairly complex. Earlier ones barfed all over the place. Best, -- Patrick Michael Kane [EMAIL PROTECTED]
Re: XFS, Linux, and Amanda
On Mon, 14 Jan 2002, Joshua Baker-LePain wrote: Hmmm, you did 'rpm -e' the RPM version, right? Pre-build amanda=bad. Word. Especially the moronic way in which RedHat has decided to build it. Brandon D. Valentine -- Iam mens praetrepidans avet vagari. - G. Valerius Catullus, Carmina, XLVI
