Solved -- samba backups "offline"
About 2 weeks ago I asked the following: > I'm backing up a single W2K machine to my tape server. > There are 4 partitions on the windows box. Some nights > al 4 partitions are processed normally. Most nights > 1 or more of the partitions fail with the query > "host offline?" which obviously it is not as the other > partitions are backing up. I got a reply from Chris Marble that helped: > I'd try cranking down maxdumps for just that host. See if that helps. Rather than change the maxdumps parameter (which probably would have solved the problem) I chose to use the "spindle" feature and indicate each of the 4 partitions are on the "same spindle". Amanda limits the number of dumps on each spindle to 1 at a time. Since the change 10 days ago, not a single "offline" partition. Thanks Chris! -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amrecover - dealing with whitespace in names
I'm backing up one W2K box and need to recover some files. amrecover doesn't seem to have a way to deal with whitespace in directory/file names. I've tried wildcards (*, ., ?), quoting (single and double) and ignoring the spaces actually there. Have I missed something? Suggestions? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
ok to insert correct tapes during amdump run?
What would happen IF ... Situation: I do 6 dumps a week, changing a 6 tape cartridge each weekend. When I forget to change it, I change the cartridge on Monday and amflush so everything is ok. Weeks and tapes are in sync. Last night I realized I had forgotten to change cartridges when the dump was about 1/2 way through. Some disklist entries done, others in progress, others not started. What would happen IF I put in the correct cartridge at that time? - would any dumps go to tape as they finished? - would the already finished dumps be automatically flushed? - ? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: selfcheck request timed out. Host down?
On Wed, Jan 30, 2002 at 07:05:19AM +1100, Tim Tuck wrote: > Hi Don, > > I've been following this discussion and you might have what my Solaris boxs did > firts time I ran Amanda ; your /tmp is not writable by the user Amanda is > running as. > > Amanda needs to build an amanda dir inside /tmp - check the perms you might find > that /tmp has limited access. Or that the subdirectory, /tmp/amanda, has inappropriate ownership/permissions. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
samba backup - sometimes yes, sometimes no
I'm doing 4 W2K partitions (single client) to a Solaris host using Samba shares. Generally all 4 work fine, but too frequently the largest partition, "C", fails with "smbclient received signal 13". A broken pipe, remote end terminated early I guess. This happens on both full and incremental. My configuration only allows one dump from this client at a time. Amanda 2.4.2. Any common, fixable :) reasons for such failures? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Solved -- samba backups "offline"
About 2 weeks ago I asked the following: > I'm backing up a single W2K machine to my tape server. > There are 4 partitions on the windows box. Some nights > al 4 partitions are processed normally. Most nights > 1 or more of the partitions fail with the query > "host offline?" which obviously it is not as the other > partitions are backing up. I got a reply from Chris Marble that helped: > I'd try cranking down maxdumps for just that host. See if that helps. Rather than change the maxdumps parameter (which probably would have solved the problem) I chose to use the "spindle" feature and indicate each of the 4 partitions are on the "same spindle". Amanda limits the number of dumps on each spindle to 1 at a time. Since the change 10 days ago, not a single "offline" partition. Thanks Chris! -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover doesn't mount tape
On Wed, Feb 27, 2002 at 08:27:14AM -0500, John Dalbec wrote: > > > "Bernhard R. Erdmann" wrote: > > > > > solution to this? I sure hope 'amrecover' doesn't require me to load the > > > tape manually. > > > > It does. You have to insert the tape as directed. > > I can see why amrecover does this when no changer is defined. But why can't it >issue 'amtape ... slot ##' commands when there is a changer? To find which tape > is in which slot all it needs to do is 'amtape ... show'. > If the desired tape is not there it can fall back to the current behavior. Personally I would dislike this behavior. Often when I am recovering a few files it is for an immediate need. I may have people breathing down my neck. Literally standing behind me :) I don't know about your changer, but to have the changer step through all the tapes takes several minutes. I "know" what tapes are there and can get the right one in position very quickly. Those wasted minutes would just raise the tension level. Also, I've had at least on case where amrecover had to be done on a non- changer device when it had been made on a changer device. amrecover did not bat an eye. jon -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: 2.4.3b2 fail on "/bin/tar returned 2"
On Wed, Feb 27, 2002 at 12:51:33PM -0500, Chris Dahn wrote:
> On Monday 25 February 2002 11:29 am, Carl Wilhelm Soderstrom wrote:
> > due to permission problems, we've had repeated cases of tar returning error
> > message '2', even tho amanda uses the --ignore-failed-read option (tar
> > 1.3.25). as I understand it, amanda should still accept the backup data
> > that tar got, but it doesn't. it simply ignores the backup.
> >
> > is there an option I need to turn on at compile time, or is there something
> > I can set somewhere? my searches turned up a mail-list message (which I
> > can't seem to find again), which said 'update to tar 1.3.19 or amanda
> > 2.4.2p2'; but after surpassing both of those things (currently amanda
> > 2.4.3b2 and tar 1.3.25), it's still no luck. :(
> >
> > Carl Soderstrom.
>
> Yes, I just started having the same problem due to a filesystem
> inconsistency. Tar gets lots and lots of data, then returns '2', so all of it
> is lost. I'm running redhat 2.4.16, tar 1.13.19.
>
>>> End of included message <<<
I don't know the real fix, but what I see is this:
--ignore-failed-read is a gnutar option that allows it to continue on
file read errors, just skipping the file on which it encounters the error
and setting a flag.
At termination, gnutar checks the flag and if set, exits with status 2
indicating some read errors. But otherwise the tarchive is ok.
If the next component merely checks exit status non-zero, it thinks there was
a failed tar and doesn't use the tarchive.
One crude way to fix it is mess with the last few lines of tar.c,
i.e. the end of main. The original is:
if (exit_status == TAREXIT_FAILURE)
error (0, 0, _("Error exit delayed from previous errors"));
exit (exit_status);
}
TAREXIT_FAILURE is defined as to 2, and exit_status is our flag of read error.
In the if statement, force exit_status to zero. An error message will still
be printed, but it will look to the next component like everything was ok.
Crude, but if you are using a special copy of gnutar for amanda only, maybe ok.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
only dir names in index
I'm trying something out and wonder if anyone has seen this problem before. Before I investigate too much more :) Just added a gnutar client (first one) and the index's for that client contain only directory names. None of the files names. Based on the size of the image dumped to tape it does contain the files. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amanda article in SysAdmin magazine
New SysAdmin issue has an article titled "Configuring Amanda" by David T. Smith. Article is online at: http://www.samag.com/documents/s=7033/sam0204a/sam0204a.htm -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: admanda problem
On Tue, Mar 19, 2002 at 11:56:55PM -0800, Nageshwar Rao Shetty Vutukuri wrote: > hello all, > > where can i find samba user's group. > could u please write me the exact path of that site. Did you consider a 5 second search on google? The first entry returned is: SAMBA Web Pages ... Please refer to these mirroring instructions for information on mirroring the Samba web pages. Non-English. ... Other sites in samba.org. ... Description: The official SAMBA site. Provides links to mirrors. Category: Computers > Internet > Protocols > CIFS www.samba.org/ - 8k - Cached - Similar pages ^ -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Make gives error on HP....????
On Wed, Mar 20, 2002 at 11:29:18AM -0500, Kaan Saldiraner wrote: > Hello Everbody, > > I have a HP-UX 10.20. > The configure works fine but when i do the "make" I get the errors > below... Whats going on? > > Thanks > > > cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -Ae -c alloc.c > (Bundled) cc: warning 480: The -A option is available only with the C/ANSI C pro >compiler > (Bundled) cc: "amanda.h", line 359: error 1705: Function prototypes are an ANSI HP was slow to adopt the ansi standard for the C language. I mean it is only 14 years old (about 6 when 10.20 came out). Anyway, amanda is written to ansi c standards. Your compiler is not. For some HP compilers an option can be given to make them recognize ansi conventions. I suspect that is what the "-Ae" option above is "trying" to do. Check your documentation for the C compiler to see if it has an ansi option. I recall it as "-aA". In that case, find where -Ae is being defined (probably CFLAGS in some Makefile, and redefine it as "-whatever". You may also have an "acc" program on your system. This is the "pro" compiler to which they refer. If you have that, redefine CC to be acc rather than cc. Best to do this during the configure run (ex. CC=/acc ./configure ". Before rerunning configure, remember to do a "make distclean". HTH -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover pb
On Thu, Mar 21, 2002 at 02:42:54PM +0800, Robert SHEN wrote: > I got the following error when I tried to test the amrecover command > > After executed amrecover, it showed > Can't determine disk and mount point fr om $CWD > Normal, CWD = current working dir CWD is not one of the dirs in your disk list. So amrecover could not determine, from CWD, what disk list entry you want to work on. You will have to "set disk" interactively. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Make problem on Solaris 2.8
On Wed, Mar 20, 2002 at 04:56:00PM -0800, Anthony A. D. Talltree wrote: > >Thank you all for the advice, I got through make successfully after setting > >LD_LIBRARY_PATH. > > >However, after I've installed Amanda, there's a new problem. When I try > >to run any amanda executables, I get the following error: > > >$ amlabel DailySet1 DailySet1-001 > >ld.so.1: amlabel: fatal: libreadline.so.4: open failed: No such file or > >directory The environment for LD_LIBRARY_PATH was set during the build, but is not retained by the executables. It has to be reset in the runtime environment. If set in the .profile of the this would allow amlabel to succeed from the command line. However, amcheck/amdump run from a crontab entry does not process the .profile. They don't use readline so this specific library may not cause a problem. > This is why linking with -R is the better answer. The executables then > know where to find the dynamic libs without LD_LIBRARY_PATH or > LD_RUN_PATH. Absolutely! > One way to do this might be > > unsetenv LD_LIBRARY_PATH > setenv LD_FLAGS "-R /usr/local/lib" Assuming "MT" is using c-shell :) > > before running configure, presuming that readline is in /usr/local/lib. > Use ldd on completed binaries to ensure that they can find the libs. An alternative for Solaris users (eg "MT") is the ld.config file. This is created and maintained by the crle command. It specifies what directories the dynamic linker searches for its libraries, i.e., the default LD_LIBRARY_PATH. If the contents of /usr/local/lib are trusted, this directory could be added to the default dirs in ld.config. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush and irc?
On Thu, Mar 21, 2002 at 05:45:58PM +0100, Juanjo wrote: > Hello, > > Two things; > > On one hand, I have been thinking about running amanda once a week for > totals directly to tape, and the rest of weekdays without tapes so > incrementals are sent to holding disk, and then before next total on > friday with tapes, I do amflush... > > Would that work nicely? I ask cause seems that amanda balances the backup > on her own, but I cannot spend expensive DLT40/80 tapes with 2 gigs of > incrementals only. You won't. After running a while amanda will spread the level 0's over all the dump days. So if your once a week tape "now" gets 40GB and your daily "incrementals" now get 2, each will average about 8 GB daily. Some might suggest that if you can't justify the expense of tapes then the value/cost of losing the data must be low. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush and irc?
On Thu, Mar 21, 2002 at 12:16:10PM -0600, Brandon D. Valentine wrote: > On Thu, 21 Mar 2002, Jon LaBadie wrote: > > >You won't. After running a while amanda will spread the level 0's over > >all the dump days. So if your once a week tape "now" gets 40GB and your > >daily "incrementals" now get 2, each will average about 8 GB daily. > > Actually it's even better than that. Each tape should average a full > 40GB. Amanda will do its best to fill each and every tape to capacity, > promoting as many full dumps per run as possible. If you have 40GB of > data and a 40GB tape drive, you should get a full set of level 0s on > every run. YMMV, but that has not been my experience. My tapes are 12GB (dds3) and although I have about 50GB (data precompression, not disk) to back up, my nightly tape usage is about 7GB. I thought the planner attempted to get a consistant nightly backup, not a filled-tape backup. Our differing observations may be the result of different amanda.conf settings. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: newbie questions
On Sat, Mar 23, 2002 at 06:57:38PM -0300, Fernan Aguero wrote: > +[ John R. Jackson ([EMAIL PROTECTED]) dijo sobre "Re: newbie questions": > | > | One possibility (although I know zip about FreeBSD) might be to set the > | shell to /bin/false and add /bin/false to /etc/shells (or whatever file > | they use to define what is valid). > | > +] > > Tried it with no sucess. Set /bin/false and added it to /etc/shells. > The problem is that since /bin/false doesn't exist, a command like: > su amanda -c "amcheck normal" > fails. > >>> End of included message <<< /bin/false is simply an exit . Create an executable somewhere, /bin/false, or /usr/local/bin/false with the lines: #!/usr/bin/sh exit 255 and try that in /etc/passwd and /etc/shells. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Interesting gtar observation, [ was: restore/tar problem ]
On Fri, Mar 29, 2002 at 08:54:11AM -0500, Joshua Baker-LePain wrote: > On Thu, 28 Mar 2002 at 7:20pm, Andy Zhang wrote > > > So, basically, a file looked like '74550524305 7550414032 /./scripts/driver' > > Each file has this preceeding directory. It's hard, if not impossible to > > access these directories to retrieve the files that I > > wanted. I tried not to '| tar xvf -', instead '> tarfile', and it still > > showed the same results by viewing the tarfile through 'tar -tvf'. > *snip* > > > - both are using Gnu-tar, downloaded the source, and compiled on the > > server/client. > > Sounds like a bad version of tar -- 1.13. You need to get at least > 1.13.19 or 1.13.25 from alpha.gnu.org and use one of those. On my Solaris tape host I have tar (from sun), gtar (1.13.whoknows that I have to leave alone), and "amgtar" (my installed version of 1.13.25, just for amanda). I was recovering a file from a remote client on the tape host, manually, not using amrecover. I blindly stuck gtar, the bad version, in the pipeline. When it gave results like Andy Zhang got "745505..." I thought 'SH**' the client still has a bad tar. But the client was using 1.13.25. Then I remembered my good, "amgtar" and the recovery went fine. Points to be made: a bad gtar can't even read good tapes. Maybe even bad gtar's write good tapes, but can't read them. Don't chuck your "bad tapes" until you try to read with a good gtar. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: small holdingdisk, large FS
On Tue, Apr 16, 2002 at 10:24:17PM -0500, Dan Debertin wrote: > One of my client hosts has a drive that is larger than my holding disk > -- drive is 18G, holdingdisk is only 4G. No, I can't swap them, and > no, I'd rather not buy a bigger disk right now. > > I would have thought that Amanda would dump the client to the > holdingdisk in 1G chunks (isn't that what the "chunksize" directive is > for?), as it does the other clients, and then gradually flush those to > tape, in order to keep the drive streaming. But it's not; it uses the > holdingdisk for the other clients, and dumps straight to tape with the > large one. > > Is there any way around this behavior? I don't believe so. I think the entire fs is dumped to the holding disk before anything gets sent to tape. If the holding disk is not large enough to hold the fs, it must go directly to tape. The chunksize parameter is generally used to work around the single file size limit that some os's have. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: PLZ HELP!! need to restore urgently
On Thu, Apr 18, 2002 at 12:01:25PM +0200, José wrote:
> Hi,
{snip}
>
> amrecover -C uis -s backserver -t backserver -d /dev/nst0
>
{snip}
>
> Extracting files using tape drive /dev/nst0 on host backserver
> The following tapes are needed: mytape01
> mytape02
> Restoring files into directory /restore
> Continue? [Y/n]: Y
> Load tape mytape01 now
> Continue? [Y/n]: Y
This message could really use some revision to be clearer.
Something like "Please manually load and rewind tape <...> now"
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problem excluding with GNUtar
On Thu, Apr 18, 2002 at 04:59:15PM +0100, Spicer, Kevin wrote: > Thanks, (and to everyone else who replied) > > If I'm reading this right... > I want to back up each partition seperately so to backup my root / partition > I should put /var in an exclude list and then backup var excluding > ./log/messages... > yes? > Sorry if that seems like a stupid question but I'd like to be sure. No, here is some clarification (hopefully) "partitions", "file systems", "directories", each a term with multiple uses. To avoid confusion, you back up "disk list entries" (DLE's :), ie things you put in your disklist file. These DLE's can be any of the above, but using tar there should be at least one DLE for each file system (partition?) you want to backup. A DLE of "/" does not back up the entire system unless you have only one file system. I installed my laptop Solaris is like this, but no other system. Often the DLEs are the full path to the mount point of a file system. Thus, supposing you have 3 file systems, the root (/), /var, and /opt, you should have a minimum of 3 DLEs. hostname/ dumptype hostname/vardumptype hostname/optdumptype To exclude a single file like /var/log/messages, you could put a line in the dumptype 'exclude "./log/messages". Note that the path should NOT include the part of the path to the start of the DLE. (for more detail, see the excellent article on exclude by A.Hall in your "docs" directory) But note that this will also exclude /opt/log/messages and /log/messages if all three DLEs use the same dumptype entry. For finer control you will have to create separate, nearly identical dumptypes. (not hard as one dumptype can incorporate a common type). This exclude mechanism will only allow the exclusion of a single file. For multiple file exclusions you have to use an 'exclude list filename' directive and specify a file containing the exclusions. Again see A.Hall's article. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Estimates - 7 hour 50mins
On Tue, Apr 23, 2002 at 09:29:57AM -0400, Uncle George wrote: > I presume u are using tar?! > From My experience, 17gigs of a (few) large files does not take a long > time. > On the other hand, backing up a large amount of files in a (single) > directory takes a long time. The orig tar that came with this (linux) > sys readily reached 80% cpu usage. The later tar fixed that, so now it > still takes a long time ( but mainly it just waits for all the > disk/directory activity ?! ) > > So whats the culprit? Since there are 2 phases ( size estimate, and then > data transfer ) i suspect that each part takes about 4 hours.To find > out, you can do a "time tar cf - .. " just like what the sendsize > program would do on your system. just to See how long that takes. > > Then how fast is your tape drive? a 5.0mb/sec tape drive would take 56 > min just to back up 17gig. This presumes that the tape is screaming ( i > ment streaming ) . > > a "df -i" might help in determing how many files might be out on the > system. > > David Flood wrote: > > > > We kick off our backup at 10pm at the moment we are only > > backing up 4 seperate directorys i.e. 4 seperate disklist entries. > > These are estimated by amanda to be 17.4GB. The estimates are > > taking just short of 8 hours to complete which is unacceptable. > > This is after making every dump a full dump in an attempt to cut > > down time with doing estimates for level 1 & 2. To force it to do full > > dumps I have did the following in amanda.conf: Another datapoint, also Solaris, but Solaris is not the culprit :) If I understand the scheme, the planner can't finalize its actual dumps until all estimates are in. Thus when the dumping begins is dependent on the speed of the slowest system's estimates. In my case, the Solaris estimates (5 drives, about 90G capacity) takes about 30 minutes. But I also have a W2000 system and the estimates for its 1 drive (4 partititions) of 30G takes 3+ hours. When I added the M$ system I had to move the dumps from 3AM to 2AM to prevent them from still running when I awoke. To David, see if one (or more) systems are causing the total system to be slow to completion. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: what's this??
On Tue, Apr 23, 2002 at 08:49:44AM -0400, Axel Haenssen wrote: > Hi Guys, > can someone tell me what this (except from my daily report) means? > > NOTES: > planner: Full dump of node8:/scratch promoted from 10 days ahead. > planner: Full dump of node6:/scratch promoted from 10 days ahead. > planner: Full dump of node14:/scratch promoted from 10 days ahead. > planner: Full dump of node15:/scratch promoted from 10 days ahead. > planner: Full dump of node9:/scratch promoted from 10 days ahead. > planner: Full dump of node11:/scratch promoted from 10 days ahead. > planner: Full dump of node7:/scratch promoted from 10 days ahead. > planner: Full dump of node10:/scratch promoted from 10 days ahead. > planner: Full dump of node12:/scratch promoted from 10 days ahead. > planner: Full dump of node17:/scratch promoted from 10 days ahead. > planner: Full dump of node13:/scratch promoted from 10 days ahead. > planner: Full dump of node5:/scratch promoted from 10 days ahead. > taper: tape DMP007 kb 144672 fm 16 [OK] Amanda trys to balance the amount of data dumped nightly. To do this she sometimes will do some level 0 (Full) dumps earlier than absolutely necessary. It is normal. I suspect you have a new amanda installation and did many first dumps all on the same day. Now amanda is in the process of moving them around to balance the size of the dumps. This will go on for several dump cycles then be pretty consistant. Besides, "extra" level 0's don't hurt, do they? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amcheck output
On Tue, Apr 23, 2002 at 09:43:13PM -0600, Trevor Morrison wrote: > HI, > > I am running amcheck on my backup called Daily and I am getting the > following output: > > Amanda Tape Server Host Check > - > ERROR: tapelist dir /usr/local/share/amanda/Daily: not writable > Holding disk /amanda: 404144 KB disk space available, that's plenty >(expecting a new tape) > NOTE: skipping tape-writable test > NOTE: info dir /usr/local/share/amanda/Daily/curinfo: does not exist > NOTE: it will be created on the next run > NOTE: index dir /usr/local/share/amanda/Daily/index: does not exist > Server check took 9.687 seconds > > Amanda Backup Client Hosts Check > > ERROR: stud.hailix.com: [can not read/write > /usr/local/var/amanda/gnutar-lists/.: No such file or directory] > Client check: 1 host checked in 0.028 seconds, 1 problem found > > I am using the root-tar dump type. I just installed the gnu tar and > reconfigured amanda. I put no where in the amanda.conf file any such > directory /usr/local/var/amanda/gnutar-lists. Amanda and associated > progarms are ing /usr/local/etc/amanda. Any thoughts? TIA Amanda uses that directory for gnutar during the planning/estimate phase. It will be created. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amdump problem
On Thu, Apr 25, 2002 at 09:35:18PM +1000, [EMAIL PROTECTED] wrote: > I have just setup amanda on a test installation for a sparc 5. > > It has mounted partitions as follows: > Filesystemkbytesused avail capacity Mounted on > /dev/dsk/c1t3d0s01778230 694298 103058641%/ > /dev/dsk/c1t5d0s02007070 265390 168146814%/home > /dev/dsk/c1t2d0s02007070 119950 1826908 7%/opt > /dev/dsk/c1t1d0s02007070 1230887 71597164%/opt/local > > All of which adds up to around 2.2 Gb. I have specified the tape compression > device, but to use software compression for c1t1d0s0 otherwise amanda won't > touch it. Don't get what you mean "specified the tape compression device" unless you are saying something like /dev/rmt/0cn. If that is the case, figure out why amanda "won't touch" /opt/local. You should never mix hardware and software compression. Amanda doesn't do the backups, so she really never touches them. > My test level 0 dump produced this, which is baffling: > > These dumps were to tapes godzilla1, godzilla2. > The next 2 tapes Amanda expects to used are: a new tape, a new tape. > > FAILURE AND STRANGE DUMP SUMMARY: > godzilla c1t1d0s0 lev 0 FAILED ["data write: Broken pipe"] > godzilla c1t1d0s0 lev 0 FAILED [dump to tape failed] > > [lots of ufsdump output deleted] > > and then this: > > DUMP SUMMARY: > DUMPER STATSTAPER STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > godzilla c1t1d0s00 1242399 704928 56.7 185:46 63.2 185:47 63.2 > godzilla c1t2d0s00 121088 121088 --4:29 450.2 4:30 448.6 > godzilla c1t3d0s00 720032 720032 -- 23:19 514.8 23:20 514.5 > godzilla c1t5d0s00 267392 267392 -- 10:15 434.5 10:17 433.8 > > (brought to you by Amanda version 2.4.2p2) > > So it looks like it succeeded, but amanda wasted a couple of hours getting > halfway through a ufsdump which was always going to fail, then getting it > right with the second tape. Is there a reason you are not using a holding disk? Is your tape capacity below 2 GB? Only 1.8 GB total was written? Why do you say it "was always going to fail"? Is it something that amanda should have predicted? Why did it fail? Amanda is just reporting what the backup programs reported to her. There may be more detail available in some log files. Amanda generally puts its debug logs in /tmp/amanda. Solaris is likely to have recorded something about the ufsdump error in /var/adm/messages. > Is there a way to force the first three partitions onto one tape, and the > fourth onto the second? Don't recall one, why would you want to? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: gnu tar option --ignore-failed-read?
On Fri, Apr 26, 2002 at 03:49:42PM +, David Trusty wrote: > Hi, > > In looking at the debug logs, I see that the gnu tar option of > "--ignore-failed-read" is set. > > Is this a problem? Would there ever be a time when tar had a > problem reading a file, and I would not get notified in a report? Without this option tar would abort its run if a file read failed. For example, the file was removed, changed during backup, or ?? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: crontab entries, Amanda and interdependencies
On Mon, Apr 29, 2002 at 01:16:46PM +0200, Arvid Grøtting wrote:
>
> ... . Also, I *think* I've found
> a way to work around this while keeping amverify in my crontab:
>
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.31807 installed on Sat Apr 27 13:21:02 2002)
> # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> 3 23 * * 1-5 /usr/local/sbin/amdump nf-amanda
> 13 16 * * 1-5 /usr/local/sbin/amcheck -m nf-amanda
> 01 17 * * 1-5 /bin/mt -f /dev/nst1 retension
> 01 08 * * 2-6 /usr/local/sbin/amstatus nf-amanda || /usr/local/sbin/amverify
>nf-amanda 2> /dev/null > /dev/null
>
> This hasn't been tested yet, but the idea is that amstatus should
> return 0 ("true" to the shell) if the backups are still running, thus
> preventing the execution of the amverify.
An alternative:
prepare a shell script wrapper containing 2 (or more) lines like:
/usr/local/sbin/amdump nf-amanda
/usr/local/sbin/amverify nf-amanda 2> /dev/null > /dev/null
And change your crontab first line to:
3 23 * * 1-5 /usr/local/sbin/amdumpwrapper
That way, amverify will run when amdump happens to finish, be it
in 2 hrs or 20 hrs.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda increment level?
On Tue, Apr 30, 2002 at 06:13:21AM +0300, Alexander Belik wrote: > > :) Will Amanda ask me for a new type when new dumpcycle begin? > Or I must do it manualy? > >>> End of included message <<< Alexander, Amanda uses a different model/concept than you are trying to fit on her. First, amanda expects each run of amdump will be on its own set of tapes. This means several tapes are in a rotation known as a tape cycle. My tape cycle is 18 tapes. Amanda will NOT add one dump to the end of a tape containing a previous dump. It will either refuse to use the tape (if your config says it is not time to reuse the tape) or it will overwrite the old data with a new amdump. Having a tapecycle of 1 means the next dump always destroys the ONLY dump you currently have. A definite NO-NO :) Second, amanda does not synchronize the levels of dump of each file system with each other one. Instead, each file system is scheduled independently with an aim of keeping the total size of each amdump run consistant. So you should excpect to see a mixture of levels in each amdump run. Third, to answer your specific question, no it will not ask. That sounds like you expect an interactive session. Amanda is designed to be run automatically on a scheduled basis (like my 2 AM nightly backup). And I'm not "always" here at 2 AM :) Instead, each amdump run generates a report, generally emailed to the admin, saying what tape it used and what tape it expects to have available the next amdump run. If that tape is not available for the next run, amanda complains (in the email report) and tries to do what she can. A common outcome is that the new amdump get written to a disk area known as the "holding disk" and can later be "amflush'ed" to the proper tape. HTH -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: "infofile" and multiple configs...
On Thu, May 02, 2002 at 09:54:15AM -0400, Chris Noon wrote: > I was reading through my amanda.conf and I saw this line: > > > #You need a separate infofile and > # logdir for each configuration, so create subdirectories for each conf > and > # put the files there. Specify the locations below. > > Well, I don't have separate infofiles and logdirs for each config, and > never have... Everything seems to be working fine, as I've done many > restores from each config. So could someone shed some light on the > above statement Thanks in advance. My daily backup is its own config. However, for several of my archive configs I do something similar. They share a common "logdir" which includes curinfo, index, tapelist, and changer files. Each config then has its own directory including only amanda.conf and disklist. In fact, the amanda.conf files are so similar they could be merged and simply be links to a single conf. I too have encounted no problems, but would be interested in a definitive answer to what potential problems exist. My guess, and it is strictly a guess, is that the problems are minimal or non-existent if there are no duplicate disklist entries among the configs. In my case, I'm archiving the tapes, setting them aside for "permanent" keeping. They even have the same tape label pattern. I could see a problem if I were reusing the tapes in a limited tapecycle. A more definitive rather than emperical answer will be appreciated. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Tape rotation problem?
On Thu, May 02, 2002 at 09:41:03AM -0500, Michael Davis wrote: > however, what I am trying to achieve is a 1 week cycle where there is a full > backup on Sundays and incremental throughout the week. Amanda's standard way of operating is to spread the full backups of all your disklist entries throughout the dumpcycle. It does not schedule "full backups" for Sunday ... After you have run amanda for a while, each run of amdump will contain a mixture of levels. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Using Multiple Tape Sizes
On Thu, May 02, 2002 at 12:36:12PM -0400, Brook Hurd wrote: > We currently use 20 8 gig tapes for our backup in > amanda. We have obtained some 20 gig tapes and we > would like to add these to the backup schedule. Do we > need to replace the 8 gig tapes with the 20's or can > we intermix them? > I think there is only one place to specify a tape size. What size would you specify? Maybe if you specify the 20GB size, and runtapes > 1, failed writes would go to the next, hopefully larger, tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Expanding tapecycle
On Thu, May 02, 2002 at 04:08:26PM -0700, Brandon Moro wrote: > Hello again all, > > Now that I have amanda running in a somewhat reliable manner, its time to > make her a part of the disaster revovery plan. I run about 8 tapes a week > and this config: > > dumpcycle 1 week > runspercycle 5 days > tapecycle 10 tapes > > So, I need to get my tapes offsite for 6 weeks at a time. This seems simple > enough to do by increasing the number of tapes in my tapecycle and > amlabeling some new tapes. > > Here's where the problem is (unless you see one above that I have > overlooked). I send the tapes from the last week of every month offsite for > 1 year. Can I arrange the tapecycle in such a way that I can get amanda to > recognize a tape as being eligible to overwrite even though it is not in > chronological order (that is, tape 8 may still be offsite for a year, but > tape 24 has come back from a 6 week offsite cycle and I want to use it > again)? What should I expect to happen when I try this method? Will I have > to set up a second config (ex: DailySet2) and run this second config with > its own set of tapes and run it during the last week of every month? Related questions for those in the know. - What happens if I keep introducing "new" tapes beyond the quantity specified by tapecycle? I would expect amanda will happily use the additional tapes. - Once I have lots of tapes beyond tapecycle, will amanda then accept any "out of order" tape as long as it is has not been used in tapecycle number of tapes? I'm hoping yes. Or must they continue to be used in the same order they were initially used? If the answers are those I "expect and hope", then you might try a scheme like this. Assuming 8 tapes per dumpcycle. 13 sets in yearly storage (13 x 4 wks = 52 wks, not 12 months), 1 set in use, 1 most recent held locally, and 6 sets in 8 wk storage (I up'ed it to account for yearly storage). That is 21 total sets of tapes, or 168. But only 8 sets are really cycling. So set the tapecycle to 64. (maybe lower) For three out of every 4 weeks, take one set to and retreive one set from 8 week storage. The retreived tapes will fall naturally within the 64 tape tapecycle. One of every 4 weeks, take one set to and retreive one set from yearly storage. They will certainly be beyond the most recent 64 and will "I hope" be accepted. Now, what happens to the index during all this I haven't a clue. Do people do all these weird things with commercial backup software? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: True Tape Overflow
On Fri, May 03, 2002 at 02:10:53PM -0500, Jim Summers wrote: > Hello All, > > I am preparing to re-configure my amanda system. I noticed while > reading the man pages that the version (2.4.2p2) of amanda I am using > will not do true tape overflow. > > I have an old DDS3 tape changer I am going to use (I have a stockpile of > DDS3) with a 12/24G capacity per tape. > > One of my file systems is slightly over the 24G limit and has not been > able to be backed up on my current config of one tape. I was hoping > that when I went to the changer and have 2 tapes per run set that it > would continue on to the next tape. Now I am not sure. > > Will the newest version do overflow? As is said many times here, each disklist entry must fit on a single tape. > Any ideas on how to handle this? use tar and split the single disklist entry into multiple entries instead of /fs backup /fs/a and /fs/b separately. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Getting old mails ?
On Tue, May 14, 2002 at 09:22:24AM +0100, Niall O Broin wrote: > Is it just me, or have other people on the list been getting old mails again > - I just got one from Michael Richard about problems with firewalls. I was > sure I'd read it before and sure enough - date in header was May 5. > Looking at the headers the problem (with this one anyway) appears to be on > the server hongkong.com. There have been a bunch of them. I've already informed [EMAIL PROTECTED] They tell me the problem is addressed (by refusing hongkong.com posts). -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: mtx
On Wed, May 15, 2002 at 02:02:03PM -0400, fil krohnengold wrote: > > Next question - folks using chg-mtx with it? I'm sure some 1 or 4 of the 8 who said yes to the first query are. Myself, I use both the freeware version and HP's version of mtx. I got both of them working with chg-mtx, did not try the "zd" version. I settled on the freeware version just to match future amanda releases. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Tape and dump cycles
On Thu, May 16, 2002 at 05:45:27AM -0700, adi adi wrote: > ... I have > no choice but to stick with the labelling, will there > be much of a problem if i'd use the "friday1 > saturday1"... kinda labelling? Guarantee: they will not stay matched with the day of the dump. If you gotta label that way so be it. Inquiring minds ask why? Nitpicking perhaps, but earlier you said: >> The tapes are >> labelled for week 1 as monday1, tuesday2, wednesday3 >> and for the second week would be monday2, tuesday2 and >> so on. You definitely can not have multiple tapes with the same label. You show two "tuesday2"s and so on. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: more level 0 dumps?
On Thu, May 16, 2002 at 10:22:31AM -0700, Soo Hom wrote: > Hello, > > I want more level 0 dumps in the tapecycle. Currently we get about 2 > level 0's every six weeks. > > > dumpcycle 6 weeks > tapecycle 30 tapes > > tapedev "/dev/nrst0" > tapetype SDT1 > > infofile "/var/amanda/eceadm/curinfo" > indexdir "/var/amanda/eceadm/index" > logdir "/var/amanda/eceadm" > > labelstr "VOL[1-6][1-5]*$" > > If I change the number of tapes from 30 to 40 and the dumpcycle to 4 weeks > will this result in more than 2 level 0's per tapecycle? > > > dumpcycle 4 weeks > tapecycle 40 tapes Question 1. What is the LONGEST interval between level 0's you want? Right now you are saying 6 weeks. Getting more than 1 every 6 weeks is not certain. Only that you will get at least 1. Setting dumpcycle to 4 weeks only makes certain you get at least 1 every 4 weeks. Set it to 1 week and you will get at least 1 every week. Question 2. How frequently do you run amdump? It appears to be 5 times a week. You should set runspercycle to the number of amdump runs per dump cycle. If you set dumpcycle to 2 weeks and do 5 dumps per week, runspercycle should be 10. The number of tapes does not affect the other parameters. But it should be greater than runspercycle. Usually by a factor of 2 or 3 or 4 or... depending on how many cycles you wish to keep in case of problems. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: 24 gig Tape Settings
On Fri, May 17, 2002 at 10:28:06PM +0100, Niall O Broin wrote: > > You must bear in mind that a DDS-3 tape holds 12GB and NOT 24 GB of data, > despite what the marketing scum might like you to think. They "assume" a > compression ratio of 2:1 which I've never heard of ANYONE achieving (apart > from tape drive manufacturers in their contrived tests). I don't know, varies greatly with the data. Here are the results of the last full dumps of my disklist entries: butch /w/jg1 0.20 butch /opt 0.35 butch /w/tape8 0.35 winnie / 0.37 butch / 0.40 butch /usr 0.41 butch /w/dutch 0.45 butch /w 0.53 butch /win/c 0.55 butch /export0.62 butch /u 0.69 butch /var 0.70 winnie /cygdrive/c0.72 butch /images0.73 butch /u20.79 winnie /cygdrive/e0.91 winnie /cygdrive/d0.93 winnie /cygdrive/f0.96 butch /w/InstPkg 0.97 butch /w/Packages0.97 butch /d23.20 butch /d43.20 Anything under 0.5 is a 2:1 compression ration. One gave nearly 5:1. And of course several file systems were virtually uncompressible. It demonstrates the difficulty of guessing the hardware compressed capacity of a tape. BTW the last two entries are anomalies of totally empty file systems. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: 24 gig Tape Settings
On Sat, May 18, 2002 at 08:34:41AM +0300, Alexander Belik wrote:
> On 17 May 2002, Jason L Tibbitts III wrote:
>
> > > "BH" == Brook Hurd <[EMAIL PROTECTED]> writes:
> > BH> I am about to use the following tape type: HP C5708A DDS-3 Data
> > BH> Cartridge, 24GB
> > I've used:
> > define tapetype DDS-3 {
> > comment "DDS-3 DAT drive"
> > length 12288 mbytes # 12 GB
> >>> filemark 0 kbytes
> > speed 850 kbytes
> > }
>
> "filemark 0 kbytes" What is this?
You didn't like the explanation I sent to you?
> Tapetype measures the native capacity and will probably tell you something
> like 11.6 GB with a filemark of 0, maybe 16KB. You ask later what the
> latter is, it is wasted space (wasted to us) between files on the tape.
> Each disklist entry is put on tape as one file. Some tape drives have
> large filemarks. So a lot of disklist entries can eat lots of tape.
> Not so with most modern drives.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Setting compression on Sony AIT2 drive from host?
On Fri, May 24, 2002 at 11:52:06AM -0400, David Chin wrote: > > In message <008d01c202b0$6149c780$062b96d5@PETE>, "Peter Normann" writes: > > Have you tried (using GNU mt): > > > > mt -f /dev/st0 datcompression 0 # turns compression off > > mt -f /dev/st0 datcompression 2 # turns compression on > > mt -f /dev/st0 datcompression 1 # Shows you whether it is on or off > > I just RTFM, and it said: > > mt -f /dev/st0 datcompression -- queries status > mt -f /dev/st0 datcompression (0|off) -- toggles OFF > mt -f /dev/st0 datcompression (.*)-- toggles ON My mt has no "compression" commands. Just shows to go you two things :) 1. It is seldom appropriate to state absolutes where unix is concerned. 2. Read The Fine Manual (actually should be Read YOUR Fine Manual). -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Any automagic exclusion of filesystems?
On Mon, May 27, 2002 at 03:05:12PM +0200, Jens Rohde wrote: > Hi > > I'm changing the dump-method on some of my filesystems from ufsdump to > gtar (so I can restore these filesystems on non-Sun hardware/OS). > > I used to backup via the mount-point, and that worked ok, but will I get > double amount of data now? > > Hmm... how the do I explain this... :) > amanda backups with tar does not branch to other file systems through the mount points. each fs must be backed up individually with tar you can specify multiple starting points within a single file system. this would be done with multiple disklist entries. in this case, duplication of data in the backup is possible as is omission of a complete fs backup. depends on your choice of starting points -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Getting My Data Back Off The Tape
On Tue, May 28, 2002 at 10:46:01PM -0400, Mitch Collinsworth wrote: > > On Wed, 29 May 2002, GIC MLs wrote: > > > # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf usr.dump > > > > ... but I get: > > > > /usr/local/bin/gtar: usr.dump: Cannot open: (null) > > /usr/local/bin/gtar: Error is not recoverable: exiting now > > > > What am I doing wrong here? Am I using the gtar command incorrectly? > > I read through the tar manpage trying to find my mistake, but can't seem to > > see what I'm doing wrong. > > Yeah, it's right here in the SYNOPSIS section of the man page: > > Ok, see it now? (Neither do I :-) But you need a - after the -xf, Yeah, it is :)) > SYNOPSIS >tar [ - ] A --catenate --concatenate | c --create | d >--diff --compare | r --append | t --list | u --update | x >-extract --get [ --atime-preserve ] [ -b, --block-size N ] >[ -B, --read-full-blocks ] [ -C, --directory DIR ] [ >--checkpoint ] [ -f, --file [HOSTNAME:]F ] [ --force- ^^^ The gtar options being used are -x and -f (-xf). The -f option, aka --file, takes a required argument "F" (required is noted by the absence of [...] with an optional ([...] present) prefix of "HOSTNAME:". I'm sure the required argument "F" is explained later as the name of the tarball file. There is no tarball file, the data is coming from standard input (the pipe). But the argument F is still required. It is a common unix convention to use "-" as a file name placeholder meaning "standard input". For example: "ls | cat foo - bar" puts the ls output between the contents of the files foo and bar. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: retain dump files on holding disk
On Tue, May 28, 2002 at 11:11:11PM -0700, Don Wolski wrote: > At 11:58 AM 5/28/02 -0500, Nick Russo wrote: > >I'd like to keep all the dump images on disk even after they > >get written to tape. My reasoning is that a large percentage > >of the restore requests I get from my users could be satisfied > >by files from the last day or two. > > Another reason for retaining dump images would be to make a second backup > tape in case writing one of the tapes is to be it's last use before errors > occur, and so that one copy could be kept off-site (in case the disaster > that destroys your disks also destroys your tape copies kept on-site). Skyblue thinking. Wouldn't this be just the level 0's you'd want retained? At least that is my antiquated impression of off-site archiving. > So I would add to Nick's question, can the retained dump images be taped a > second time, hopefully in a way that allows amanda to record the fact that > the images exists on two different tapes. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: make problem - HP-UX 11i, amanda 2.4.2p2
On Thu, May 30, 2002 at 10:47:44AM -0500, Gary Hines wrote: > Hi All, > I'm having trouble with running make with Amanda. The configure appears > to run fine, then when I run make I get the following errors: > [ lots of errors I think amhpfixdevs is supposed to fix deleted ] > > As a side note: I received the following warning during configure. Is this > something that I need to be worried about? > configure: warning: *** Run amhpfixdevs on HP-UX systems using /dev/vg??. Did you? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Not enough space on tape
On Fri, May 31, 2002 at 11:59:25AM +0100, Niall O Broin wrote: > On a couple of occasions recently, when I added a new machine into the > rotation, some incrementals didn't get done because I didn't have enough > tape space. However, amanda doesn't even do these dumps and leave them in > the holding disk. Is there any way of forcing that behaviour i.e. for some Really? That doesn't seem the way amanda handles things. There is a reserve parameter that specifies how much of the holding disk to reserve for incrementals. The default is 100%. That would force it to skip full dumps, defering to incrementals. So I would have expected full dumps to not be done. > reason some night there isn't quite enough tape, do the backups anyway to > the holding disk. I can then flush those if I so desire but probably I'd > just leave them there as insurance against a failure of the disk concerned > before the next tape backup (yes, I know I've a problem there in the event > of a simultaneous failure of one of the not taped disks and the holding disk) > > One way that springs to mind is to lie about the tape capacity but it occurs > to me that then amanda will feel free to use that much each night if it > needs to. I'd rather that it knew of the capacity of my tape, but backed up > as much as was necessary, leaving the surplus on the holding disk. > > I've a horrible suspicion that I'm asking for a glass of dry sweet wine here > but perhaps someone can make sense of my requirements / desires. :-) I'm guessing you do not have an automatic tape changer. In that case you could still set runtapes to 2 (rather than default 1). The chg-manual type of changer can be specified. This setting will cause amanda to think it can use a second tape if necessary. But it will not be able to dump to it because a manual change is needed. The untaped data will be left on the holding disk. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: level 1 differential backup config
On Fri, May 31, 2002 at 02:25:03PM -0400, David Chin wrote: > > However, I seem to be having trouble with this. I've been running with a 7 > tape tapecycle, and a dumpcycle of 5 days, and runspercycle of 5days. I > recently changed it to (9 tapes, 7 days, 7 days). After modifying the > config on Sunday (before the level 0 was to be made), I forced level 0 > backups. Unfortunately, the force didn't work. (No, not in the Star Wars > sense, either.) > > My less-frequently-changing filesystems get dumped at level 1, but > /home keeps getting dumped at level 2; the last level 1 was on Sat May 25. Once the level goes to a higher number I believe it will not go back to a lower level until the next level 0. > > Ach. I guess I have a general question: What's the right procedure to > switch backup configs in the way that I describe above, i.e. changing the > cycle periods. I don't see what problems you expect. Nor do I see anything else to do except make the config change and introduce the new tapes. BTW runspercycle is unitless, not 7days, just 7. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Dump Program Not available
On Sat, Jun 01, 2002 at 06:09:07PM -0500, Frank Smith wrote: > Amanda uses the full path to all the backup/restore programs that it was > configured with (and are fixed at compile time). So if Amanda was built > with your dump program as /usr/sbin/dump. but now it is /sbin/dump or > /usr/local/bin/dump, then you will get the 'program not available' error > even though 'dump' is somewhere in the Amanda user's path. (Disclaimer: > I'm a 'tar' user, and am assuming Amanda deals with ufsdump, vxdump, and > other variants of dump in a similar way to the way it finds GNU tar.) >Somewhere near the beginning of /tmp/amanda/amandad.*.debug you can > find the full command path that Amanda is trying to run. You can then > either make a link from there to the real program, or (probably better > for the long term) rebuild Amanda with the correct path. > > Good luck, > Frank > > --On Saturday, June 01, 2002 14:08:30 -0400 Kaan Saldiraner <[EMAIL PROTECTED]> >wrote: > > > Hello, > > > > Thanks for the responce .. I ran this command while su - to amanda > > > > export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin > > > > Now amanda user can infact run the dump and restore without doing /sbin/dump > > ..etc. > > Look in your config header file, /config/config.h, for the path compiled in for the "#define's" of DUMP and GNUTAR. These absolute paths are what amcheck and friends are using. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Dump Program Not available
On Sat, Jun 01, 2002 at 02:08:30PM -0400, Kaan Saldiraner wrote: > Hello, > > Thanks for the responce .. I ran this command while su - to amanda > > export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin > > Now amanda user can infact run the dump and restore without doing /sbin/dump > ..etc. > > But when i do amcheck on my server It is still giving me the same error. > > DUMP Porgram not available > RESTORE program not available > >>> End of included message <<< Amcheck and friends do not use the PATH variable for find "dump" or "tar". They are hardcoded as absolute paths at compile time. To see what has been compiled in, look at the file /config/config.h There will be two line #define DUMP and #define GNUTAR. These defines are where amcheck is failing to find the programs. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Tape Labelling
On Mon, Jun 03, 2002 at 08:14:10AM +0700, Brad Waugh wrote:
> Have trouble with trying to label tapes. The drive on ide0. Have tried
> /dev/ht0 & /dev/nht0. Both give;
>
> $ /usr/sbin/amlabel iogta Tape1
> rewinding, reading label, not an amanda tape
> rewinding, writing label Tape1, checking label
> amlabel: no label found, are you sure /dev/nht0 is non-rewinding?
>
> I have a Seagate STT2A (using Travan 20GB tapes).
>
> Have set my tapetpye in /etc/amanda/iogta/amanda.conf to;
>
> runtapes 1
> tapedev "/dev/nht0"
> tapetype STT2A
> labelstr "^Tape[0-9][0-9]*$"
>
> define tapetype STT2A {
> comment "just produced by tapetype program"
> length 9500 mbytes
> filemark 103 kbytes
> speed 914 kbytes
> }
Basic questions,
Can you write to and read from your tapedrive? (tar, dd, ... )
Does mt status give you reasonable results?
Is nht0 a no rewinding device? If you tar to the device,
do you have to do an mt rewind to read the tarball back?
It is not a familiar device name to me,
but then I have no idea what os you are using.
Is your tape write protected?
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Tape Labelling
On Mon, Jun 03, 2002 at 12:43:17PM +0700, Brad Waugh wrote: > > On Mon, Jun 03, 2002 at 08:14:10AM +0700, Brad Waugh wrote: > > > Have trouble with trying to label tapes. The drive on ide0. Have tried > [ lots of data snipped ] > >>> End of included message <<< With Linux, I'm out of my realm. Quite different administration than systems I use. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amrecover connection refused - again!
On Mon, Jun 03, 2002 at 10:15:34AM -0500, Rebecca Pakish wrote: > >Can you telnet to each of thes ports? > > >$ telent amandaix (use 'quit' to exit) > > [root@slaw etc]# telnet slaw.unterlaw.com amandaidx > Trying 10.1.7.23... > telnet: connect to address 10.1.7.23: Connection refused > Not stating the obvious I hope, but this should not be: jon: telnet localhost amandaidx Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 butch AMANDA index server (2.4.2) ready. This is the starting dialog I get. At least you can now focus on amandaidx. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amrecover connection refused - again!
On Mon, Jun 03, 2002 at 04:16:11PM -0500, Rebecca Pakish wrote: > You're right, that worked. > > Joshua, I should have tried that sooner when you suggested it. But I'm > racking my notes trying to remember why I changed that to yes in the first > place. I know I just used this configuration to recover a file a couple of > months ago and the wait=yes was in place then!! Lee Fellows earlier wrote: > I know of no server using tcp that the superserver waits upon for > connection completion. I'm going to tuck this one away in some hidden recess of my brain. Hopefully recoverable :) Does anyone know of any exceptions? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amdump and config questions
On Tue, Jun 04, 2002 at 10:26:50AM -0400, GOODWYN,RON (HP-USA,ex1) wrote: > Greetings, > > I'm pretty new to AMANDA. I have a few questions that will be helpful to me > as I explore more AMANDA documentation. > > 1. Can the tape server be a system other then the AMANDA server or a system > acting as both the client and the server. So in other words, lets say you > have systems A, B, and C. System A is the client. System B, is the AMANDA > server and system C is the tape server. Does the AMANDA architecture allow > for this? > Joshua has already answered the other questions quite well. Only one possibility I can think of here, but I've never seen it implemented. Solaris, bsd, maybe linux/gnu, and Joerg Schilling, have a program "rmt" for Remote Magnetic Tape. I don't know any details about its usage though. I've only used it with programs already setup for the purpose. Eg. solaris' dump can specify the tape device as "host:device" and it will automagicaly use rmt. If you explore using rmt for the setup you propose and are succesful, be sure to report back to the list. One problem I forsee is double network traffic. First in going to the amanda controlling host, then via rmt to the tapehost. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist issue?
On Wed, Jun 05, 2002 at 12:35:31AM +0200, Ulrik Sandberg wrote:
> On Tue, 4 Jun 2002 [EMAIL PROTECTED] wrote:
>
> > > Have you recently edited the tapelist file or changed the number of
> > > tapes in use? Rotated a tape into or out of circulation?
> >
> > Yes. I have been replacing my AIT-1 tapes with AIT-2. I have been
> > relabling them with the same label as the one I am removing. I did not
> > see how this could have caused an error.
>
> I will here give a somewhat verbose explanation about fixing up tapelist.
> Perhaps it will shed some light on your problem.
>
...
> How do you fix this up? Simple. Reorder and set time stamp. First,
> reorder:
>
> 20020602 DailySet1-003 reuse
> 20020601 DailySet1-002 reuse
> 20020531 DailySet1-001 reuse
> 0 DailySet1-006 reuse <-- new tape now in correct position
> 20020530 DailySet1-005 reuse
> 20020529 DailySet1-004 reuse <-- this tape is due
>
> Then, fix time stamp so that the new tape has the same time stamp as the
> previous entry ('previous' meaning 'below'):
>
> 20020602 DailySet1-003 reuse
> 20020601 DailySet1-002 reuse
> 20020531 DailySet1-001 reuse
> 20020530 DailySet1-006 reuse <-- time stamp now same as for 005
> 20020530 DailySet1-005 reuse
> 20020529 DailySet1-004 reuse <-- this tape is due
What is the purpose of "dating" the tape.
I presume 0 indicates not yet used.
Doesn't amanda accept a "new" tape at anytime?
jon
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapecyle question
On Wed, Jun 05, 2002 at 02:23:56AM +0200, Marcus Schopen wrote: > Hi, > > I'd like to run a daily backup with a dumpcycle of three weeks. Amanda is started >from Monday to Saturday (6 days a week). What tapecycle value do I have to use: > > dumpcycle3 weeks > runtapes 1 > runspercycle 18 > tapecycle24 tapes ??? > > A second weekly backup should run every Sunday with a dumcycle of 2 month. Would >this be the correct configuration: > > dumpcycle2 month > runtapes 1 > runspercycle 8 > tapecycle12 tapes dumpcycle: maximum number of days or weeks between full, aka level 0, backups. You really want 3 weeks between full backups? runspercycle: number of amdump runs in one dumpcycle You seem to have this conceptually correct tapecycle: number of tapes you want to cycle. Make it larger than one dumpcycle. maybe even 2x, 3x, or 4x. >From your "weekly backup" I suspect like so many before, you are trying to fit amanda's nice round model into the square old-style scheme; full backups one specific day a week, incrementals every other day. If I'm correct and you choose to continue with your geometric squeeze, I think you want a dumpcycle of 1 week and runspercycle of 1 for your second configuration. jon -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: gnu tar
On Tue, Jun 04, 2002 at 10:11:10PM -0500, Matthew Boeckman wrote: > Is it possible to have tar called with -h (follow symlinks) from within > amanda? I haven't found a blurb in amanda.conf like TAR_OPTIONS. It will be fun if there happens to be a symlink loop. Many amanda users, myself included, compile amanda with GNUTAR set to a placeholder program. I use .../libexec/amgnutar to keep it with many other amanda programs. Then amgnutar can be a copy of, a link to, or a shell script calling the real gnutar. If it is the latter, it is called a "wrapper" and you can add any options you like. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tar or dump
On Wed, Jun 05, 2002 at 10:37:09AM +0200, BRINER Cedric wrote: > hi, > > I have 2 questions: > 1) what are you using as system to back up : "tar | dump" > -tar :advantage: The tar is independent of the FileSystem and it could > work also on an active partition > -dump: I can't see any advantage? > > 2)I'm using amanda with "dump" for 8 months and now every run we are > almost fulling a tape. > -I change the disklist by replacing the nocomp-user with user-tar > -I thought that in this way the transition will be smooth. > > But I get this message from amanda > > > > obsul35/export/diskA1 lev 1 FAILED [dumps way too big, must skip incremental >dumps] > > obsul39/export/diskA1 lev 1 FAILED [dumps way too big, must skip incremental >dumps] I'm always wary of making wholesale changes like this. I prefer to bring in one or two disklist entries at a time. Well actually 1 or 2 from a couple of hosts. Then 1 or 2 more from all hosts. But then I very seldom have to make recoveries (lucky me) and I'm not too concerned about the promptness of the transition nor having an absolute changeover date. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist issue?
On Wed, Jun 05, 2002 at 11:01:43AM -0500, Dave Sherohman wrote: > On Tue, Jun 04, 2002 at 11:45:22PM -0400, Jon LaBadie wrote: > > What is the purpose of "dating" the tape. > > To prevent it from being immediately requested. > > > I presume 0 indicates not yet used. > > Doesn't amanda accept a "new" tape at anytime? > > Yes. However, in the example presented, the new tape was #6 and we > wanted to use #4 next. Since amanda doesn't like reusing old tapes when > new tapes are available, #6 needs to be dated manually so that #4 and > #5 will be used first. I'm on really shakey ground here, meaning I've never tested it, but I don't think amanda goes looking for new tapes anywhere in the list. I think it looks at the tape available in the drive, then checks whether it is a valid tape to use. Then the date comes into play. That is "date" or "new" comes into play. If I'm correct, then the new tapes position in the list won't matter as long as amanda sees the tapes in the correct order in the drive itself. Again, if I'm correct (and I'm not certain), the advantage of dating the new tapes is to prevent accidentally using them out of order. But as long as you present #4 and #5 to amanda first, it won't reject them and go looking for that #6 just because it is new. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Can AMANDA only backup < 24GB partitions???
On Wed, Jun 05, 2002 at 05:42:35PM +0100, Kenny MacPherson wrote: > Can AMANDA on the whole only backup < 24GB partitions or is this a tape > limitation in this case? > > I have a /home5 partition on a DELL 4400 running RH7.2 and it's failing > daily! Other partitions do backup okay. The only issue is that I have a > Mammoth-2/EZ17 and even when I snip my disklist down to this directory > alone, it fails to complete a backup. > > It's 55GB and AFAICT the M2 should eat that kind of space up no problem. > It's set for nocomp-high as Exabyte tell me the EZ17 always has hardware > compression on! > I'm not following your numbers, mentioning 24 and 55GB. But, no amanda has no built in limits. Remember amanda just kicks off other programs to do the backups. So the question should be does your dump program or gnutar have limits. Gnutar itself does not to my knowledge. Don't know what your dump program (dump varys with the system) limits are if any. However, are you going to a holding disk? Is the unreserved portion of the holding disk sufficiently large? Are you writing to the holding disk with no "chunk" size and encountering single file size limits? You have not said what the failure messages are? That might give a clue. What does your tapetype say is the tape capacity? Is amanda refusing to even try, or is it running out of some resource like holding disk or tape capacity or ... Is your data compressible. You say HW compression is on so "the M2 should eat ..." But random data, semi random data, compressed data, ... all may undergo expansion when subjected to HW compression. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist issue?
On Wed, Jun 05, 2002 at 12:53:00PM -0500, Dave Sherohman wrote: > On Wed, Jun 05, 2002 at 01:42:23PM -0400, Jon LaBadie wrote: > > I'm on really shakey ground here, meaning I've never tested it, but I > > don't think amanda goes looking for new tapes anywhere in the list. > > I'm on slightly less shaky ground, as I increased my tapecycle a couple > months ago, but my recollection is that amanda refused to overwrite used > tapes until all new tapes had been used. I know that it requested a > new tape each time until all new tapes had been used. > > Working around this to get my tapes back into the right order is how I > became familiar with tapelist... Agreed if you are increasing the tapecycle. Amanda refuses to use any old tapes until at least tapecycle number of tapes are in use. But ahall, the OP, was changing tape types, ait-1 to ait-2 if I recall. Thus the new tapes were not for an increased tapecycle. They were simply unused and labeled with the same label as the previous tapes. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover missing files
On Fri, Jun 07, 2002 at 01:52:39PM -0500, Ben Kochie wrote: > I am using indexing, and gnutar to backup all of my filesystems, I keep > the indexes in /etc/amanda/backupset/index/ according to my amanda.conf > file. > > backups are working properly, no errors reported. I can run amrestore on > a tape and see all of the files that are supposed to be backed up.. I can > also gunzip the files in the index, and see them listed.. > > but when I run amrecover, set the host/disk, and do an ls, i only see a > few of the directories/files that are supposed to be backed up. it seems > like something in amindexd is not working properly, and I have no idea > what. > > has any other amanda users run into this problem? One of my systems has similar problems. But because this system is a Windows 2000 system and I'm backing it up from an amanda client under Cygwin, I thought it might have been the unusual setup I'm using. However I'm coming to believe others are having similar problems so that it may not be my unique setup. A sample of my results. When I look at the D: partition, there are > 2100 directories and files there. When I look at the amanda tape of a level 0 of that partition, it seems all the files are there. And the size of the dump is reasonable. But the index is certainly not. The index has 220 entries, 190 of them directories. Very few, if any, of those are more than 3 levels down. The 30 or so files are all in the top 2 directories. I originally did the cygwin client using gnutar 1.13.19. Now I'm using 1.13.25 and seeing the same results. Suggestions? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrestore program
On Sat, Jun 08, 2002 at 05:46:57PM -0600, Trevor Morrison wrote: > > Hi, > > When I do my backups I use the GNU tar for my root-tar dumptype. While > I was trying to restore a file tonight I would get the following error: > > tar: ./trevor/trevor: Cannot open: Not a directory > tar: Error exit delayed form previous errors > extract_list - child returned non-zero status: 2 > > trevor is just regular file in my /home/trevor directory. I first > changed into that directory before starting amrecover. What am I doing > wrong? TIA. It seem no one replied to you the first time your submitted this last week. I read it the first time and had nothing to say. Probably other frequent contributors were in the same boat. It wasn't that we did not read it. When you resubmit a query, I'd suggest changing things, adding new info. Might stimulate some ideas that the original message did not. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: ./var/adm not being excluded
On Wed, Jun 12, 2002 at 11:32:47AM -0400, Martinez, Michael - CSREES/ISTM wrote: > I had posted this msg before, but I had given the wrong info. > > I'm backing up / on one of my clients. I would like to exclude > /var/adm/syslog from the backup. > > On my server:amanda.conf, I have defined a disklist entry with "exclude > "./var/adm/syslog"" and I'm using this in my disklist file. > > But it's not working. tar continues to give me an error (actually a failure) > about "/var/adm/syslog: changes as we read it." > > Now, I know this isn't much of a problem. But since my Amanda report gets > mailed out every day to the IT director and the project manager, I'd like to > NUKE this FAILURE message, cuz they think the backup is failing. > Do you need to backup anything under /var/adm? Maybe exclude the entire directory. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: "incremental bumped to level x" incremental? I want full!
On Wed, Jun 12, 2002 at 04:42:30PM +0200, Tom Van de Wiele wrote:
> Hello list!
>
> My objective: to make a FULL backup on tape every weekday. If there is
> data on the tape, I want it removed and/or overwritten by new data...
> First of all, I'm using version 2.4.2p2 on a Linux server (Dell
> PowerEdge) with kernel 2.4.16
>
> my 'disklist' file contains:
>
> delta.eduline.be hda1 always-full
> delta.eduline.be hda4 always-full
> delta.eduline.be hda3 always-full
>
>
> in my amanda.conf I have:
>
> define dumptype always-full {
> global
> comment "Full dump of this filesystem always"
> program "GNUTAR"
> compress none
> index yes
> priority high
> dumpcycle 0
> }
>
dumpcycle and its kin, runspercycle, tapecycle, ...
are not properties of a particular dumptype, but
of the configuration. define them outside your
dumptype definition.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: To use software compression or not ?
On Sat, Jun 15, 2002 at 12:01:26PM +0100, Niall O Broin wrote: > > At the moment this is not an issue because the most data ever gets taped in > one run is ~10GB but as I'm adding clients and disks this will increase and > I'm concerned about maximising my use of the limited capacity of the DDS-3 > drive. Obviously using software compression helps with this because Amanda > knows exactly how big each compressed dump is and I can also tell her the > truth about the tape capacity. Don't tell it the capacity is 24GB :), More like 11.8 (post compression). > However my big concern is restoring. I know that even with current > processors gzipping several GB of data takes some time and the same applies > in reverse - or does it ? Does it take significantly longer to extract one > file from a gzipped tar file on a DDS-3 than it does to extract one file > from an uncompressed tar file or can a reasonable CPU gunzip in a pipe as > fast as the DDS-3 can deliver data ? > > And then of course there's the fact that I won't be restoring very often > anyway, so the extra backup capacity obtained may be worth the price of > slower restores. Why should they be slower? Ungzipping is much faster than gzipping. I ran a small test, a 200MB cdrom image. gzipping, 99 real seconds, 53 cpu seconds (~2MB/sec) unzipping, 23 real seconds 9 cpu seconds (~8MB/sec) I'm also using dds-3. My tapetype definition shows a transfer speed of 1MB/sec. Looks like gunzipping should be able to keep up with the tape drive. > > A second question that arises is the issue of existing tapes. I've read that > once a DDS-3 tape has been written in hardware compressed mode, the tape is > marked accordingly and will ever after be written with compression, no > matter what the drive is told to do. I've also read that this mark can only > be removed by using a magnetic tape eraser. Is this correct ? I don't think it is a dds-3 issue. More like a specific format and/or hardware vendor and/or model issue. I may be wrong, (please correct me if so), but I don't recall any instances of this problem with dds-3. I have an HP 6 6 tape changer. I know when running the tapetype program early on I used the same tapes with HW and no compression. My results were clear that my drive did not exhibit this problem (i.e. capacity with HW compression was less that without irrespective of previous use of the tape). jon -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: getting further
On Tue, Jun 18, 2002 at 09:57:24AM -0700, Mike Heller wrote: > I am getting further with Amanda. I ran a backup last night but had a > problem: > > error [/bin/tar returned 2] My reading of the gtar code shows 2 is the return code when it has been run with the "ignore failed reads" option and did in fact ignore at least one failed read. > > This problem has come up in the past (searched the group) but there > seems to be no specific reason for this. I'm using tar version: > > tar (GNU tar) 1.13.11 Not a recommended tarsion. (that was supposed to be "version", but "tarsion" seems so right :). -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Auto-flush during amdump?
As others have pointed out, it is a new, existing feature. One thing though. you will probably want to make sure there is a sufficient tape capacity, possilby allowing multiple tapes, for both flush and normal dump. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: 2.4.3 Tapeless file-driver pure-disk backups
On Fri, Jun 21, 2002 at 10:00:58AM -0700, Steve Follmer wrote: > > I for one am glad that amanda has grown beyond its unix/tape roots to > support samba/windows and to support file: disk backups. This does not > have to be sacrificed, in adding even more robust support for file: and > also, some SWAT like GUI. And this would make amanda more useful for > more people, if the amanda community wants to go in that direction. > > Though there will be conflicts; appending is bad on tape, good on disk. > Explicitly specifying incremental backups is bad for large networks, but > I would desire it for my small network. That said, certainly there are > windows and mac clients in the large commercial/university installations > that characterize the bulk of amanda users. > > I admit that the majority of existing amanda users use tape, but its a > biased legacy sample. But let us not ignore the possible users > represented by the exponential growth in home networks, linux, and cheap > disks; a growing audience of users like myself, for whom disk backup is > better than none, who don't have the money to sink into a tape system, > and who don't see enough upside (what are the odds that 2 drives in > different machines will die on the same day) on changing and labeling > tapes and shipping them off to the abandoned limestone mine. Amanda was originally written by, and is currently maintained by, a surprisingly small total number of talented people. Their objective, as I understand it, is to provide quality backup services for their own use, not for ours. For the most part they do administer large sites that use tape. Wide-spread, increasing adoption of amanda on small systems is not a requirement of that objective. We small users are benefitors of their efforts. Changes we see as highly desireable, or immensely practical in our environments may be of little value in the environment of the amanda developers. As they are not developing a commercial product, increased "sales" is not an incentive. In fact, increased usage actually causes them to devote more of their freely given time to supporting the new users. This does not imply new features and niceties for small users do not make it into amanda. But the 'primary' use of amanda at large sites, as you indicate, can not be sacrificed. File: disk backups are one example, but be aware that it is a pretty recent addition to amanda and is probably undergoing teething pains. (I have not used it, so I say that from ignorance) You indicate two desireable features, GUI and appending. In general, GUI's are wonderful things for end-users/desktop environments. They hold fewer benefits for large installations. So any impetus and development effort on a GUI is unlikely to come from the traditional amanda developers. That does not mean you, or someone else with a similar desire, can't contribute their time freely and develop such an interface and contribute it to the project. Many would love to see that. Appending is a topic that comes up often (weekly? daily? :). As you seem to accept appending is bad for tape, it might only be used for disk file-based backups. I'm not at all sure why you feel appending is good for disks. Even if it is a good thing for file-based backups, you have to consider the effort of revising not just the backup software, but also the recovery and all the administrative software to handle this special case. The alternative, which has been adopted, is to make the disk "look like a tape". Thus no appending to disk file backups either. > I appreciate your advice about the autochanger and will explore that. It will probably meet your needs, just in a different way than you think is "right". jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
only dir names in index
I'm trying something out and wonder if anyone has seen this problem before. Before I investigate too much more :) Just added a gnutar client (first one) and the index's for that client contain only directory names. None of the files names. Based on the size of the image dumped to tape it does contain the files. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: crontab entries, Amanda and interdependencies
On Mon, Apr 29, 2002 at 01:16:46PM +0200, Arvid Grøtting wrote:
>
> ... . Also, I *think* I've found
> a way to work around this while keeping amverify in my crontab:
>
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.31807 installed on Sat Apr 27 13:21:02 2002)
> # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> 3 23 * * 1-5 /usr/local/sbin/amdump nf-amanda
> 13 16 * * 1-5 /usr/local/sbin/amcheck -m nf-amanda
> 01 17 * * 1-5 /bin/mt -f /dev/nst1 retension
> 01 08 * * 2-6 /usr/local/sbin/amstatus nf-amanda || /usr/local/sbin/amverify
>nf-amanda 2> /dev/null > /dev/null
>
> This hasn't been tested yet, but the idea is that amstatus should
> return 0 ("true" to the shell) if the backups are still running, thus
> preventing the execution of the amverify.
An alternative:
prepare a shell script wrapper containing 2 (or more) lines like:
/usr/local/sbin/amdump nf-amanda
/usr/local/sbin/amverify nf-amanda 2> /dev/null > /dev/null
And change your crontab first line to:
3 23 * * 1-5 /usr/local/sbin/amdumpwrapper
That way, amverify will run when amdump happens to finish, be it
in 2 hrs or 20 hrs.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: 2.4.3b2 fail on "/bin/tar returned 2"
On Wed, Feb 27, 2002 at 12:51:33PM -0500, Chris Dahn wrote:
> On Monday 25 February 2002 11:29 am, Carl Wilhelm Soderstrom wrote:
> > due to permission problems, we've had repeated cases of tar returning error
> > message '2', even tho amanda uses the --ignore-failed-read option (tar
> > 1.3.25). as I understand it, amanda should still accept the backup data
> > that tar got, but it doesn't. it simply ignores the backup.
> >
> > is there an option I need to turn on at compile time, or is there something
> > I can set somewhere? my searches turned up a mail-list message (which I
> > can't seem to find again), which said 'update to tar 1.3.19 or amanda
> > 2.4.2p2'; but after surpassing both of those things (currently amanda
> > 2.4.3b2 and tar 1.3.25), it's still no luck. :(
> >
> > Carl Soderstrom.
>
> Yes, I just started having the same problem due to a filesystem
> inconsistency. Tar gets lots and lots of data, then returns '2', so all of it
> is lost. I'm running redhat 2.4.16, tar 1.13.19.
>
>>> End of included message <<<
I don't know the real fix, but what I see is this:
--ignore-failed-read is a gnutar option that allows it to continue on
file read errors, just skipping the file on which it encounters the error
and setting a flag.
At termination, gnutar checks the flag and if set, exits with status 2
indicating some read errors. But otherwise the tarchive is ok.
If the next component merely checks exit status non-zero, it thinks there was
a failed tar and doesn't use the tarchive.
One crude way to fix it is mess with the last few lines of tar.c,
i.e. the end of main. The original is:
if (exit_status == TAREXIT_FAILURE)
error (0, 0, _("Error exit delayed from previous errors"));
exit (exit_status);
}
TAREXIT_FAILURE is defined as to 2, and exit_status is our flag of read error.
In the if statement, force exit_status to zero. An error message will still
be printed, but it will look to the next component like everything was ok.
Crude, but if you are using a special copy of gnutar for amanda only, maybe ok.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Compile error, resolution, confusion
On Mon, Jun 24, 2002 at 01:10:24PM -0700, Jason Brooks wrote: > Hello, > > I have been reading through the archives and found a bit of information > that helped me. > > for amanda 2.4.3b3, I received errors while compiling on a solaris8 (bybee) > machine. I applied a change I found in reference to this error, and the > compiler error went away. the wierd part: this error didn't happen on > different machines running solaris8(bramble), 7, 251, redhat 6.2-7.2, or > freebsd3.4. > > the change was to line 244 of client-src/sendbackup-dump.c: > I changed "no_record" to "options->no_record". I'm only looking at the 2.4.3.b"2" code, but I doubt it makes a difference. Certainly your change is not the proper correction. The "options" identifier I see is a character pointer, not a structure pointer. Also, the no_record parameter should be in scope as an external integer. It is a flag as to whether the no record option is set in the configuration. Check sendbackup.c. In my code, line 55 has the declaration. Check sendbackup.h. In my code, line 65 has the definition. Check sendbackup-dump.c and confirm sendbackup.h is being included. If your correction is valid, there are lots of places around line 244 that should be similarly corrected. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Suggestions please - amanda can't backup remote client.
On Tue, Jun 25, 2002 at 09:47:55AM +0200, klavs klavsen wrote: > > and then I grabbed this from the amdump file which looks weird to me > too.. Haven't used file-based backups, nor with linux, but these caught my eye. Maybe Joshua or someone else can give give better analysis. > driver: result time 797.683 from taper: TAPER-OK > driver: dumping compaq.vsen.dk:/ directly to tape > driver: send-cmd time 797.684 to taper: PORT-WRITE 00-1 > compaq.vsen.dk / 0 20020617 > taper: try_socksize: receive buffer size is 65536 > taper: bind_portrange: port 577: Permission denied ^^^ Sounds like an xinetd/firewall/NAT/ipchains problem > taper: stream_server: waiting for connection: 0.0.0.0.34583 ^^^ Is this a reasonable value? > taper: reader-side: got label DiskBackup11 filenum 1 ^^ > driver: result time 988.044 from taper: TAPE-ERROR 00-1 [input: > can't open: 674S^F: No such file or directory] Do disk "tapes" have to exist before use? Do they have to be amlabelled? Have they been? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: end-of-tape error
On Wed, Jun 26, 2002 at 10:13:32AM -0400, Jesse Griffis wrote: > Hello, > > Briefly, I have an Exabyte EZ-17 with a Mammoth-2 drive inside. I'm running it on a >dual-CPU RedHat 7.2 server with plenty of RAM and a holding disk around 25 GB (I can >certainly provide more detail when / if needed). > > I've been able to figure out 99% of the Amanda process (some trial and error, lots >of research on this list, among other good web sites out there), but I'm stuck now, >and the boss is about to make me go spend a thousand bucks on Veritas' or someone >else's... > > I am getting an odd end-of-tape error on every tape, every time I try to write a >very large file. Below is the Amanda report for the last attempt I tried. I'm >chopping out some of the extraneous detail (the STRANGE results on some of the drives >is from NT machines, files with odd characters, thanks to Word). Can someone explain >why 7.7% used tape would give me an out-of-tape error? On the holding disk, the >/home partition is about 4.6 GB and there is much space remaining (10 GB right now, >even though there are numerous holdings stuck there for the moment...) > breaking up long lines with would be appreciated by some of us. > Any help at all would be greatly appreciated! 7.7% is probably a calculated value based on your tapetype setting. You don't show that. What do you claim is the capacity of your tape? Are you be claiming 60GB? That is 4.59GB / 0.077. Is that valid for your drive and tape combination? Are you using (perhaps unknowingly) hardware compression? That should never be used in combination with the software compression you are using. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: end-of-tape error
On Wed, Jun 26, 2002 at 12:14:12PM -0400, Jesse Griffis wrote: > taper: tape DailySet1-17 kb 5373824 fm 4 writing file: Input/output error > > Does this mean that it only managed to write 5 MB before the I/O error? No, I think that is in KB, so 5.37 GB was written at the time of the error. I think the difference in that number and the earlier part of the report, 4.59 GB is that the smaller number is "successfully written", i.e. complete dumps while the larger is total written including the incomplete dump in progress at the time of the error. > > I don't see anything in /var/log/messages around the time of this backup, so > I suppose > I'll have to run another with the express purpose of hunting for fresh log > results... :) I think that is the proper approach. You seem to have most other bases covered. Sounds like some form of hardware situation (head cleaning, cableing, terminator, ...) Look for scsi messages too. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: MacOSX and gnutat problem
On Wed, Jun 26, 2002 at 03:47:41PM +0100, Martin Hepworth wrote: > Hi all > > well I've been fiddle with my new shiney iMac G4 trying to get amanda to > back the thing up. Currently I'm getting this from the backup report.. > > FAILURE AND STRANGE DUMP SUMMARY: > stuartdmg4 / lev 0 FAILED [/usr/bin/gnutar returned 2] > [ snipped part and rearranged next line ] > > sendbackup: argument list: gtar --create --file - --directory / --one-file-system > --listed-incremental /var/amanda/gnutar-lists/stuartdmg4__0.new --sparse > --ignore-failed-read --totals . [ snipped part ] > sendbackup: index created successfully > error [/usr/bin/gnutar returned 2] > sendbackup: pid 588 finish time Wed Jun 26 01:11:36 2002 Note: amanda uses the "--ignore-failed-read" option to tar. To not use this would cause tar to abort if it ever failed to read a file successfully. Even something as benign as file removed before tar got to it. But generally permissions problems. When using this flag, and encountering one or more failed reads, tar exits with a status of 2 rather than 0. This is what amanda is telling you. The interpretation is that tar had to skip one or more files. I don't know of any way to determine which files. The rest of the dump should be fine. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: 2 problems with Amanda
On Wed, Jun 26, 2002 at 09:49:23AM -0500, Robert Renzetti wrote: > The Unix admin quit a few weeks ago and I have been trying to > pickup the pieces, with little Unix experience. So, if possible, could > someone please help me out here with Amanda? I have tried to > figure it out on my own to no avail, and the literature hasn't helped > me much, since I am such a novice. > > -(FIRST PROBLEM) > > When the admin left, she said she "suspended" amanda. By > "suspended" it appears that she meant she commented out > amanda's crontab. So, the first thing I did was to remove the #'s and > see if it would run properly. It didn't; the crontab didn't run at all. > Another admin that I know, but who isn't familiar with Amanda, tried > to help me through setting up the crontab. I did the following: > > 1) As root, "crontab -e amanda". I created the crontab all over again, > which looks like the following (2 lines): > > 0 16 * * 1-5 /opt/bin/amcheck -m geo > 45 0 * * 2-6 /opt/bin/amdump geo;mt -f /dev/rmt/0 off > > 2) "crontab amanda" > 3) "chown amanda amanda" > 4) "chmod 600 amanda" > > This time the crontab ran, but something didn't work right. I got an > email from Amanda saying the following: > > "Amanda Tape Server Host Check > - > /dump: 5549882 KB disk space available, that's plenty. > ERROR: /dev/rmt/0hn: no tape online. > (expecting tape geo_vol51 or a new tape) > NOTE: skipping tape-writeable test. > Server check took 0.030 seconds. > > Amanda Backup Client Hosts Check > > Client check: 5 hosts checked in 0.140 seconds, 0 problems found. > > (brought to you by Amanda 2.3.0.4)" > > The tape was in the drive and when I manually entered > "/opt/bin/amcheck -m geo", it found the tape fine (as "su amanda"). > > After a few days screwing around with this, I still have not gotten it to > work properly from cron (still cannot find the tape). But I can > manually do it from the command line. Since I was getting worried > that the backups weren't getting done, I decided to manually run > "amdump" from the command line (as "su amanda"). So I entered > "/opt/bin/amdump geo;mt -f /dev/rmt/0 off" and the backup ran. > > -(SECOND PROBLEM) > > However, even though the backup ran, I got a warning: > > "driver: WARNING: /dump: 512 KB requested, but only > 3549720 KB available. > planner: Incremental of nutmeg:/pc bumped to level 2." > > There were many more "planner" entries. (This text was snipped > from the report of the amdump that Amanda emailed me). > > You will notice in the "amcheck" that I quoted at the top that > "amcheck" reported "/dump: 5549882 KB disk space available, > that's plenty." This was the first day that I tried getting Amanda to > work. There were about 4-5 days between then and when I > manually ran Amanda from the command line. So, not only do I > have a problem with the crontab, it also appears that I now have a > problem with the dump being too big for the tape. > > -(QUESTIONS) > > 1) Can anyone, please, help me with *exactly*, *literally* what I need > to do to get the crontab setup properly? Apparantly I did something > wrong. No, no one can do that. We can give some guidance. First your crontab is probably ok at this point, though how you got to it is FTB (For The Birds). Step 1 was sufficient. Cron keeps its own copies of the "active" crontabs. Anything in your directory is superfluous. "crontab -e" edits it directly and leaves nothing behind. > 2) Is there anyway to rebuild the dump directory so that I don't get > the not enough space on the tape error? I think I might have > messed something up there and either duplicated data or doubled > up the dump such that the dump dir has the data for two tapes > stored for backup. I know for a fact that there *should* be enough > space on the tapes because I have read the logs for previous > backups performed under the previous admin. Somewhere on your system are amanda's configuration files. In my case it is /usr/local/etc/amanda. Yours are in ??? How can I tell you where your administrator decided to put them. Lets call that path XX/amanda. Amanda can work with multiple configurations, but there will be at least one. From what you show it appears you have a configuration called "geo". That would also be the name of a subdirectory under XX/amanda. Go to XX/amanda/geo. In there you will find a file called "disklist". It specifies what is to be backed up, one line per file system (or directory tree). To get restarted I suggest your comment out all entries in the disklist file, i.e. put a # at the start of each line. For manual testing of amdump or amcheck, uncomment one or two lines. To bring the system working again from cron, don't uncomment all the lines at once, but uncomment maybe 20 or 25% of them. The next day uncomment another 20 or 25%. This will spread out the initial full dumps over sev
Re: MacOSX and gnutat problem
On Thu, Jun 27, 2002 at 09:30:17AM +0100, Martin Hepworth wrote:
> Jon
>
> Well it's not happy - amanda is constantly trying to do a level 0. So
> it's seeing this as a fail.
>
I find it is generally easier to follow a thread
if new comments are added at the bottom.
> --
> Martin
>
> Jon LaBadie wrote:
> >On Wed, Jun 26, 2002 at 03:47:41PM +0100, Martin Hepworth wrote:
> >
> >>Hi all
> >>
> >>well I've been fiddle with my new shiney iMac G4 trying to get amanda to
> >>back the thing up. Currently I'm getting this from the backup report..
> >>
> >>FAILURE AND STRANGE DUMP SUMMARY:
> >> stuartdmg4 / lev 0 FAILED [/usr/bin/gnutar returned 2]
> >>
> >
> > [ snipped part and rearranged next line ]
> >
> >>sendbackup: argument list: gtar --create --file - --directory /
> >>--one-file-system
> >> --listed-incremental /var/amanda/gnutar-lists/stuartdmg4__0.new
> >> --sparse
> >> --ignore-failed-read --totals .
> >
> >
> > [ snipped part ]
> >
> >
> >>sendbackup: index created successfully
> >>error [/usr/bin/gnutar returned 2]
> >>sendbackup: pid 588 finish time Wed Jun 26 01:11:36 2002
> >
> >
> >Note: amanda uses the "--ignore-failed-read" option to tar. To not use
> >this
> >would cause tar to abort if it ever failed to read a file successfully.
> >Even something as benign as file removed before tar got to it. But
> >generally permissions problems.
> >
> >When using this flag, and encountering one or more failed reads,
> >tar exits with a status of 2 rather than 0. This is what amanda is
> >telling you. The interpretation is that tar had to skip one or more
> >files. I don't know of any way to determine which files. The rest
> >of the dump should be fine.
> >
>
>
>
>
>>> End of included message <<<
Well, I hate to suggest this, but ...
On my unix system I use gnutar 1.13.25.
I use the same gnutar version on an amanda client I run on a Win2K box under CYGWIN.
The unix amanda is version 2.4.2, on the w2k box it is 2.4.3b2.
The unix box never exhibits the problem you are seeing, the w2k box always "did".
I don't know if my unix box, version 2.4.2, never sees any failed reads, or whether
there is code in amanda 2.4.2 that accepts the exit status of 2 without considering
it a failure. But the 2.4.3b2 under w2k/cygwin is sensitive to an exit status of 2.
So I had to remove the sensitivity or change gnutar so it did not exit 2.
I chose to modify gnutar. I always have amanda use its own copy of tar
so if I want to customize it, or shell wrapper it, I can without affecting
the system version of tar.
If you are compiling or can compile your own gnutar, it is a simple change.
At the end of main(), at the very end of the file tar.c is an if statement.
Nominally it says "if the exit status is 2 (aka TAREXIT_FAILURE) print an
error message". I simply added an exit(0) in the if statement. Actually,
the curley braces, a comment, and the exit(0);.
Here is the resulting code with the changes (at the end of tar.c).
if (exit_status == TAREXIT_FAILURE)
{
error (0, 0, _("Error exit delayed from previous errors"));
/* added for amanda */
exit(0);
}
exit (exit_status);
}
I scanned the gnutar code and as far as I could see, the only place the
"exit_status" variable is set to TAREXIT_FAILURE (defined as 2) is when a
failed read occured and was ignored. So I don't think any other failure mode
would be affected. But I've been wrong before :(
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: help with amdump
On Thu, Jun 27, 2002 at 09:11:34AM -0300, Eduardo Ceva wrote: > Hi this is the first time I use Amanda. I read every documentation, and I installed >AMANDA as documentation says. > > I created a label on a tape and after that I runed amdump. I noted that I am having >a problem of authentication. Can anyone help me? > In my log I have what follow > > START planner date 20020627 > INFO planner Adding new disk piaui:/etc. > INFO planner Adding new disk piaui:/usr/local/etc/amanda. > START driver date 20020627 > FAIL planner piaui /usr/local/etc/amanda 0 [piaui: [access as operador not allowed >from operador@piaui] amandahostsauth failed > ] > FAIL planner piaui /etc 0 [piaui: [access as operador not allowed from >operador@piaui] amandahostsauth failed > ] > FINISH planner date 20020627 > WARNING driver WARNING: got empty schedule from planner > STATS driver startup time 0.092 > START taper datestamp 20020627 label backup00 tape 0 > INFO taper tape backup00 kb 0 fm 0 [OK] > FINISH driver date 20020627 time 16.340 > > On piaui, does your amanda user have a properly configured and permissioned file called .amandahosts in their home directory? I would also suggest that you not try amdump until you can get clean runs from amcheck. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: MacOSX and gnutat problem
On Thu, Jun 27, 2002 at 06:02:55PM +0100, Martin Hepworth wrote: > > The client/server are both using amanda 2.4.2.p2 > > Maybe I;m being totally stupid but I couldn't find anything above 1.13 > (ie I couldn't find the beta's anywhere, just mentions of it.). I'll > have another dig tomorrow (knocking off time now). However if you have a > URL to hand :-) Don't think the 1.13.X are considered "beta", but ... IIRC the plain vanilla 1.13 is generally incompatible with amanda. The 1.13.19 and .25 versions generally work. Maybe anything between 19&25. > > I'll have another dig tomorrow. Try ftp://alpha.gnu.org/pub/gnu/tar/ -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: help with amdump
On Thu, Jun 27, 2002 at 04:18:49PM -0300, Eduardo Ceva wrote: > Hi Joshua, > becouse it become to hard do find out the problems with my amanda I did what follow > > I reinstall all my OS, I am running Mandrake Linux 8.2 > > after, I logged as root and install Amanda as documentation says Whoops, you installed amanda, not compiled and installed from source. Is this a package that came with the Linux distribution? Are you following Mandrake's instructions/documentation or those that come with amanda source? Very important, if installing a precompiled version, does that version expect a user named "operador" to be the amanda user? The user name gets hard coded into the amanda programs and with a precompiled version you don't get to choose. > after, I configure my amanda.conf and disklist > > after I give permitions to the user operador to give full access to local filesystem >/etc and to my filesystem /usr/local/etc/amanda I don't think that suggestion was ever made, and it should not be done. > after I create my .amandahosts What is in it? Where did you put it? What are ownership/permissions? > then I run amcheck and I get this: > > Amanda Tape Server Host Check > - > Holding disk /mnt/dumps: 8349040 KB disk space available, that's plenty > NOTE: skipping tape-writable test > Tape backup00 label ok > NOTE: info dir /usr/local/etc/amanda/database/curinfo: does not exist > NOTE: it will be created on the next run Do not be concerned about "NOTE's" at this point. > Server check took 17.421 seconds > Amanda Backup Client Hosts Check > > ERROR: piaui: [access as operador not allowed from operador@piaui] amandahostsauth >failed > Client check: 1 host checked in 0.017 seconds, 1 problem found > (brought to you by Amanda 2.4.2p2) > > > It looks like I have a problem of authentication, can someone help me? > > It´s a good idea recompile .configure witth the options --without-bsd-security and >--without-amandahosts ? If you did compile yourself, what were your configure options? Assuming you ran configure more than one time (for any reason), did you run "make distclean" before the last configure and compile? Configure sometimes caches things that need to be cleared. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Tape Drives, why?
On Sat, Jun 29, 2002 at 09:07:53PM -0700, robinsom wrote: > Michael C. Robinson > > 100 gigabyte hard disk is less than $200 while the last check on high capacity tape >drives turned up prices exceeding 4 times that for maybe a quarter the capacity >because advertised tape capacity is compressed capacity. Worse, tapes don't last, > they have a three year shelf life if they are stored properly and the tape doesn't >physically break when it winds around the spools... HD don't last forever either :< I've had a good number go bad. > Is it possible to configure Amanda to backup to a harddisk or Raid volume instead of >a tape? What about CD-R, it's the cheapest media and it has a thirty year shelf life >where the only downsides are the capacity, the risk of disks getting scratched, > the fact that they are made using mercury, and the risk of them getting exposed to >UV light. Thats a lot of CD's to get 100 GB. > I'm asking about the issue because the recommended book to read on Amanda suggests >that Amanda > doesn't offer an alternative to tape backup. My last search on tape drives >suggested that a high capacity unit that can handle 40 gigs per tape is between $800 >and $1000. I could buy a lot of ATA hard drives for that kinda cash. Well, you're talking initial cost. I got a 6x24GB tape changer for $1100. The tapes are $10 each, so my 144GB is only $60 for the media. And I can extend those $60 increments as much as I want. A damaged tape can be replaced for $10. I can take copies off site. I can be reasonably confident that my backups can be read on any system with the same format tape drive. If I am keeping multiple days (3 wks worth in my case) on my media, a damaged tape causes the loss of one days backup. If they were all on the same disk I'd lose everything. Pros and cons abound. Use what suits you. Yes, current amanda versions do support backup to disk. They are considered "beta" version, but like most amanda beta's, they are quite solid. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: permission problem
On Mon, Jul 01, 2002 at 03:31:29PM -0700, Soo Hom wrote: > Hello, > > I am getting this error on a new client I added: > Amanda Backup Client Hosts Check > > ERROR: song3: [can not access /dev/rdsk/c0t0d0s7 (c0t0d0s7): Permission > denied] > ERROR: song3: [can not access /dev/rdsk/c0t0d0s4 (c0t0d0s4): Permission > denied] > ERROR: song3: [can not access /dev/rdsk/c0t0d0s3 (c0t0d0s3): Permission > denied] > ERROR: song3: [can not access /dev/rdsk/c0t0d0s0 (c0t0d0s0): Permission > denied] > ERROR: song3: [can not read/write /etc/dumpdates: Permission denied] > > I setup the .amandahosts file with: > servername.ucsd.edu root > >2 -rw-r--r-- 1 amanda sys 21 Jun 21 14:21 .amandahosts Think that should be -rw--- When you did "make install" of amanda, were you doing it as user amanda or as user root? Should have been root. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Long numbers running together in amanda output
On Tue, Jul 02, 2002 at 10:23:46AM -0700, Doug Silver wrote: > Joshua - > > Is this for a particular rev of Amanda, i.e. will this work in 2.4.2p2? > > Thanks! > > > > > Look for columnspec in amanda.conf. Here's one I use that stays under 80 > > columns (it's 79, I think): > > Should be pretty easy to look, as suggested, and see if it is in there; possibly commented out. Hint, its in there. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: How to restore unknown tapes
On Tue, Jul 02, 2002 at 08:37:05PM +0200, Harald Schmalzbauer wrote: > Hello all, > > I have a complete amanda generated backup consisting of eight daily1-8 > tapes (SLR100). > Now I need to look into these tapes. How do I do that? > Alternatively I could also restore the complete set, I have enough > space. > I have no idea how to use amanda, all quick attempts ended up in missing > log files. > I only have the tapes, nothing else. > > Any help appreciated (I won't dive deep into amanda, I just want to > restore the data) Amanda doesn't have to be present to use the tapes. Each dump (generally a file system) is saved on the tape as a separate file. There is also an administrative file placed at the start of the tape. At the start of each dump file on the tape there is also a 32KB header that says what was dumped and how to recover it. Basically it follows the scheme 1. move the tape to the beginning of the dump file mt rewind mt fsf 2. use dd to extract the 32KB header dd if= of= bs=32k count=1 reading the header will tell you what file system is in the dump file and what commands can be used to extract it. Repeat step 1 and modify step 2 according to the header Besure you use a "no rewinding" device in your mt and dd commands. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problems with amanda
On Wed, Jul 03, 2002 at 09:43:08AM +1000, Robert Kearey wrote: > Gene Heskett wrote: > > >The majority opinion of those on this list is that any rpm's for > >amanda probably should be subjected to an intentional rm -f, they > ... > Incorrect. Where did you get that idea? > ... > > A little research does wonders, you'll find. > > >Generally speaking, making an rpm installation work is going to be > >10x more difficult than making a home built install work. There > > I'd dispute that most strongly. It's all there in the spec file, if > you'd care to look. ... Sounds like you took it personally. Gene was commenting from a point having viewed many bad packages. Perhaps yours is wonderous. That has not been the general experience of long time contributers to this list. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Archival tape backup configuration help
On Mon, Jul 08, 2002 at 04:57:07PM -0400, Cory Visi wrote:
> Ok, I have my daily tape backup set configured and working perfectly. Now I
> want to setup an archival (available for offsite storage) backup strategy.
> Here is how I want it to work:
>
> Week 1: Full backup to tapes 1 and 2
> Week 3: Take tapes 1 and 2 offsite
> Week 5: Full backup to tapes 3 and 4
> Week 7: Replace tapes 1 and 2, take tapes 3 and 4 offsite
> Week 9: Full backup to tapes 1 and 2
> etc...
>
> There will be 4 tapes total, 2 tapes per backup. amdump will be run
> every 4 weeks.
> The difficulty is that a full backup of our disks do not fit on one
> tape. We can easily fit the excess in the holding space though.
The limitation is not the size of the total backup.
The limitation is the size of the largest disklist entry. No SINGLE entry
in the disklist can span a tape. If you are using the same list (even if
in a different file and config) you already know each individual disklist
entry will fit onto a tape.
> Aside from the weird crontab line, how would I configure Amanda to handle
> this strategy? This is what I have right now (I know it's wrong because
> it's not working at all):
>
> dumpcycle 8 weeks
4 weeks
> runspercycle 2
1
> tapecycle 4 tapes
>
> define dumptype comp-user-full {
> comment "Non-root partitions on reasonably fast machines (full only)"
> record yes
Probably no so your dailies don't think a full was done and will
still do their own at the appropriate times.
> index yes
> skip-incr yes
Some suggest a dumpcycle of 0 to always force full.
> compress client fast
> priority medium
> }
>
> amdump email returns the following message:
> driver: WARNING: got empty schedule from planner
> and all the disks get "SKIPPED."
>
> I have a feeling "skip-incr" is not the right setting to use.
> Anyone have any ideas?
>
> Thank you for your help,
> Cory Visi
>
>
>>> End of included message <<<
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: gaphical frontend (GUI) for amanda?
On Tue, Jul 09, 2002 at 10:54:14PM +0200, Lorenzo Canovi wrote: > > Hi there. > > Anyone is working on this topic? > > I know that we are all "command-line" oriented, here :-) but when I try to > propose amanda to my customers this is the main question (not "reiable?" or > "scalable?" ... strange people) ... Not that I know of, but I'd be glad to have you contribute one. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Device Compatibility
On Wed, Jul 10, 2002 at 01:05:22PM +0930, Adam Smith wrote: > > I've been looking around at tape drives and backup software, and I had > Amanda recommended to me. Upon looking at amanda.org, I didn't see any > kind of Hardware Compatibility list. Is this more dependant on the > operating system itself? > > Devicewise, I was thinking about perhaps going with the Ultrium standard > because it seemed to be a high capacity standard (200Gb+) that would see > us into the future, but as yet have not decided on the right unit to use > for this purpose. > > Since this backup system will now be implemented from scratch, I was > wondering if I could get some opinions on the following: > > a) Which backup units would people recommend for a detatched device > backing up approximately 200Gb+ > b) Whether or not Amanda would have any difficulty in working with such > a device > c) Whether or not the above (a) and (b) would work correctly under > FreeBSD Amanda does not actually perform the backups. It is a backup "manager". One of her strengths, IMO, is the use of standard unix utilities to perform the backups. Thus, if gnutar and/or your favorite "dump" utility can talk to the tape drive, if mt can rewind and position the tape, if one of the supplied changer scripts can operate the changer (usually they can, particularly if the drive is scsi), then amanda should work fine. So your first assumption was correct, hardware compatibility is mostly a function of the os and its utilities. Others may have direct experience with Ultrium drives, I don't. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumptype and holding directives qestion.
On Wed, Jul 10, 2002 at 01:21:40PM +0100, Mark Cooke wrote:
> I have now configured amanda to work the was it wants, rather than the
> way *I* want (ref: Quick Tape cycle Query),I have now replaced all my
> DDS2 tapes with DDS3 and ammended this section to read for 'DailySet':
>
> dumpcycle 2 weeks
> runspercycle 12
> tapecycle 15 tapes
>
> which AFAIK will run a dumpcycle of 2 weeks, with 2 full backups and
> incrementals 6 days a week, with a tape amount of 15
Not quite.
First major item, you are specifying a full backup once every 2 weeks.
Not twice. Assuming I understand what you want, I think dumpcycle
should be 1 week, and runspercycle should be 6. This will say you
play to run amdump 6 times in a 1 week cycle. During that cycle
everything should get a full backup at least once, incrementals
the other runs. So your 15 tapes will contain a total of 2.5
cycles. Any 6 sequential tapes will contain at least one full
backup of everything.
Second, the full/incremental decision is made during each dump run,
separately for each entry in your disklist. The disklist entries can
be a single file sytem or it can be a directory tree. Assuming your
disklist has a sufficient number of entries, each dump run will be
a mixture of full dumps for some entries, incrementals for others.
Third, the full dump frequency you specify is a "minimum". For any
particular disklist entry, amanda may decided to do its full dump
earlier than necessary. This can happen because amanda is trying
to balance the size of the daily backups or because so much changed
that the difference between a full and an incremental is small,
so why not do a full backup.
>
> But have I got my understanding of the following correct:
>
> 1. holding drives:
> I have specified 2 hdds to use as holding areas in the amanda.conf,
> called 'holding' and 'holding2'
> Am I correct in thinking that if holding gets full, then it will
> continue onto holding2?
That is not my experience, but don't ask me how amanda decides
which holding disk to use. It seems to use all 3 of my holding
areas each run. Perhaps in part it tries to use a different
holding disk than the disk being dumped.
> 2. dumpcycle:
> With the example below:
>
> define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> exclude list "/etc/amanda/DailySet/exclude.files"
> compress server best
> priority high
> index yes
> record yes
> }
>
> define dumptype user-tar {
> root-tar
> comment "user partitions dumped with tar"
> compress server best
> priority low
> index yes
> record yes
> }
>
> If I define user-tar in diskypes, am I correct in thinking that the
> 'root-tar' directive specified within user-tar, means use the settings
> from the dumptype 'root-tar', but override them with the extra settings
> in user-tar?
Yes, the last 4 lines of user-tar could be eliminated as they duplicate
root-tar entries.
BTW I find compress ... "BEST" to suck up lots of cpu for marginal
improvement in compression. YMMV
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumptype and holding directives qestion.
On Wed, Jul 10, 2002 at 08:57:36AM -0600, Scott Sanders wrote: > With respect to the holding drives and which one gets used when, I was > reading through my amanda.conf this morning and stumbled on this comment > > # If more than one holding disk is specified then > # they will all be used round-robin. > > So there ya go. I always say, RTFCF (Read The Fine Conf Files :) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumptype and holding directives qestion.
On Wed, Jul 10, 2002 at 05:16:08PM +0100, Mark Cooke wrote: > Jon LaBadie wrote: > >On Wed, Jul 10, 2002 at 08:57:36AM -0600, Scott Sanders wrote: > > > >>With respect to the holding drives and which one gets used when, I was > >>reading through my amanda.conf this morning and stumbled on this comment > >> > >># If more than one holding disk is specified then > >># they will all be used round-robin. > >> > >>So there ya go. > > > > > >I always say, RTFCF (Read The Fine Conf Files :) > > I did, I just must of missed that bit (as if I never RTFM, then I > wouldn't of known about using more holding areas). > > But thanks for the advise :-) Actually, as I said I did not know, it was self-directed advice. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: "no space on holding disk" == ~80GB?
On Wed, Jul 10, 2002 at 10:23:01AM -0500, Peter Seebach wrote: > So, I'm doing some dumps using a 120GB holding disk, and without a tape, > and *MOST* of them work. Out of ~40 filesystems, the same few fail every > time, without exception... and they're all sort of big. > > So... I have a 120GB disk, with "reserve" set to 0, and "use" set to -1, > and the other hacks suggested from the web site to force Amanda to dump to > the local disk. And a dump of a 40GB filesystem fails with "no more > holding disk space". > > This is amanda 2.4.1p1. If it matters, it's on a system with 32-bit int > and long, and 64-bit long long. > > Am I doing something obviously stupid? Is this a known bug that I somehow > missed in my groveling through Faq-O-Matic? Not chunksize problems is it? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: autochanging tapes after tape is full...
On Thu, Jul 11, 2002 at 10:45:21AM +0200, Patrick Schumacher wrote: > hello list. > after 4 days of work at least i made it und amanda and my tapechanger works. > hmm, the mtx and amtape commands works. so i think everything is ok for the > changer. > so i go on an try to make a back up of one of my servers. i what to back up > round about 50GB from the server. > today i found a mail in my postbox, reporting me this: > > *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]]. > Some dumps may have been left in the holding disk. > Run amflush to flush them to tape. > The next tape Amanda expects to use is: a new tape. > > FAILURE AND STRANGE DUMP SUMMARY: > peppone/mnt/homes lev 0 FAILED [out of tape] > > [snip] > > hmm, i think the tape ist full, so amanda cannot write more data on the > tape. is this right? > and is there a away to auto-change the tape if the first is full? Yes, there is a parameter that tells amanda it may use more than one tape. The parameter is "runtapes #" where # is the "maximum" number of tapes amanda is allowed to use for a single amdump run. Be aware, as others have pointed out, no single entry in your disklist file can be split across two tapes. Thus each entry, not the total list, but each entry, must be smaller than the tape capacity. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel problems
On Thu, Jul 11, 2002 at 02:30:20PM -0600, Trevor Morrison wrote: > > ... . When I run amlabel I > get this output: > > rewinding, reading label, no tape online I would interpret this as saying the system does not believe there is a tape in the drive. Why it is saying that I don't know. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Netapp dumps using Amanda
On Thu, Jul 11, 2002 at 01:56:04PM -0700, Ashwin Kotian wrote: > Hi Paul, > > I think the reason we disabled indexing was because with indexing > enabled, amanda was trying to use the "u" option & try to update the > dumpdates file & was failing therein. Amanda wouldn't even do a dump & > it complained with it a "cannot update dumpdates file" error. Shouldn't that be the "record" parameter, not the index param? You can also compile amanda to use its own "amandates" file instead of the system dumpdates file. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Gnutar not recognized
On Thu, Jul 11, 2002 at 03:41:25PM -0600, Scott Sanders wrote: > Hi all, > > I've got amanda up and running pretty well now with the local dump s/w. > I'd like to have the GNUtar at my disposal as well but even after > installing it and deleting the config.cache files, re-running configure > amcheck still can't find it. will running make clean or make distclean > solve this? make clean is not sufficient. I use make distclean though I thought deleting the *.cache files would work also. Did you use the configure option, --with-gnutar= ? For more on configure options, run configure --help and hold on to your hat. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Archival tape backup configuration help
On Fri, Jul 12, 2002 at 05:28:12PM -0400, Bort, Paul wrote: > amanda@tape$ amadmin MyConfig no-reuse MyOffsiteTapeLabel-1 > > Amanda will keep the record of the backup, but never ask for the tape again. > It is essentially read-only. > > You should add another tape to your rotation (with a new name) to replace > it. > > > -Original Message- > > From: Anthony Valentine [mailto:[EMAIL PROTECTED]] > > Sent: Friday, July 12, 2002 5:08 PM > > To: Jon LaBadie > > Cc: Amanda Users > > Subject: Re: Archival tape backup configuration help > > > > > > If I wanted to do something similar, but I didn't want to reuse the > > tapes at all (I need to store each one for 7 years), how would I set > > Amanda up to do that? > > Paul, If one wanted to store every tape, i.e. never reuse one, is there a difference between setting each to "no-reuse" after it is written or setting tapecycle 99 (some huge number)? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) duplicating list replies in personal email is superfluous
Re: Gnutar not recognized
On Mon, Jul 15, 2002 at 09:33:20AM -0600, Scott Sanders wrote: > > I'm sure it had something to do with a PATH statement somewhere but the fix I > found to work was move the original tar in /usr/bin and /usr/sbin and put > links to the GNUtar in their place. I got this suggestion from the yahoo > group surrounding amanda. Isn't the yahoo group just a reflection of this list? Many UNIX administrators would replacing the OS installed versions of "anything" improper. If there are differences in the vendor's tar and the gnutar you replace it with, it may affect other things of which you are unaware. configure has a specific option to tell it where the "gnutar" you want amanda to use is located. "--with-gnutar=." It doesn't have to be in your PATH at all because it will be hardcoded during compile. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Gnutar not recognized
On Mon, Jul 15, 2002 at 10:09:14AM -0600, Scott Sanders wrote: > not that I don't believe you, but I tried the --with-gnutar option with no luck? > Definitely a valid point though about replace OS version software! > > Jon LaBadie wrote: > > > On Mon, Jul 15, 2002 at 09:33:20AM -0600, Scott Sanders wrote: > > > > > > I'm sure it had something to do with a PATH statement somewhere but the fix I > > > found to work was move the original tar in /usr/bin and /usr/sbin and put > > > links to the GNUtar in their place. I got this suggestion from the yahoo > > > group surrounding amanda. > > > > Isn't the yahoo group just a reflection of this list? > > > > Many UNIX administrators would replacing the OS installed versions > > of "anything" improper. If there are differences in the vendor's tar > > and the gnutar you replace it with, it may affect other things of which > > you are unaware. > > > > configure has a specific option to tell it where the "gnutar" you want > > amanda to use is located. "--with-gnutar=." It doesn't have to > > be in your PATH at all because it will be hardcoded during compile. > > Unlike some other reports, the gnutar I use is not in my PATH at all. And it is uniquely named, amgtar, just to prevent mistaking it for gtar or tar. No way configure would find it without the option. I suggest the possibility that something else was the problem when you tried it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
