Re: bare metal restore, basically
On Tue, Feb 27, 2007 at 11:43:54PM -0500, Gene Heskett wrote: > Doing almost exactly that with nothing but a cd with dd tar & gzip on it, > was the driving force behind my writing a handfull of scripts > collectively called Genes-Amanda-Helper-0.5. I can throw in some more too-little-too-late advice: I run a nightly crontask to back up both my Amanda configuration and my indices to another machine via rsync. I have done one bare-metal restore this way -- basically, I reinstalled the original OS, installed Amanda on it (I didn't have any trouble with version mismatches -- Amanda's tape format is fairly stable), copied the indexes back, and ran amrecover. It was a bit sketchy to be overwriting all that data on a running system (especially since the restore won't delete files that didn't exist on the backup), but worked out pretty well in the end. I think, in future, that I'd prefer to set up a CD with one of the LiveCD distros that's easily modified, add Amanda to it, and keep that around. Dustin
Re: Amanda on Gentoo Linux?
On Sun, Mar 18, 2007 at 09:41:33PM +0100, Stefan G. Weichinger wrote: > Any amanda-users here who use the gentoo-ebuilds of amanda? > Anyone who runs amanda on Gentoo Linux in productive/professional > environments? > > I would like to hear some feedback on this, thanks (off-list comments > welcome as well, if preferred). I use Gentoo, and am an Amanda developer, although at the moment I'm not using amanda in a "production" environment on Gentoo. I don't know of any issues that would prevent that, though. If you find some issues (e.g., problems with an ebuild), I'll be glad to help. What's up? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: missing function in amanda?
On Sun, Mar 18, 2007 at 08:15:30PM -0400, Gene Heskett wrote: > If we had such a tool, I could run an estimate phase in advance of the > regular run and be in a position to reboot to the older kernel ahead of > time instead of totally screwing with the amanda database. I'm not sure that is the most compelling use-case! ;) That said, it's always useful to be able to decompose operations for debugging purposes. At this point, the system is not factored in such a way as to make that break a clean one. I can think of ways to accomplish something *like* what you're asking, but they're all hacks that would be harder than if [ $(ssh mybox uname -r) == "2.6.foo.bar" ] then echo "Please reboot mybox" | page_gene fi Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda on Gentoo Linux?
On Tue, Mar 20, 2007 at 10:21:07AM -0500, Linda Pahdoco wrote: > The only issue we've hit recently is not being able to get incrementals on > machines with updated tar packages. We get Level 0 every night. We stay > pretty on top of patches from > Gentoo, and we've seen it on multiple systems. We're also seeing it on > Windows 2003 boxes running amanda under Cygwin. I don't think that has > anything to do with the server, only > with the client machine(s). That sounds suspiciously like what Gene is running into: http://marc.info/?l=amanda-users&m=117399694429491&w=2 Pretty much my only substantive gripe with Gentoo is that it encourages its users to "live on the edge", which isn't really appropriate for production systems. I assume you've downgraded your tar packages to keep your backups functional? What version of tar broke for you? What kernel version are you running? I'll make a note to look into this when I can get the relevant equipment lined up. Dustin P.S. Gene -- I haven't been ignoring your messages, but you were using bleeding-edge kernels, and seemed to believe that the kernels, and not tar, were to blame for your lack of incrementals. -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda on Gentoo Linux?
On Tue, Mar 20, 2007 at 11:41:20PM -0400, Gene Heskett wrote: > Humm, may be suspect. I wish gentoo would not change the version numbers > rather willy-nilly so that those of us used to the gnu.org version > numbers applied to the tarballs (this IS the src of tar BTW) among the > various distro's. I've heard maybe 2 other similar queries, naming that > 1.16 puppy. FWIW, Gentoo sticks to the upstream version numbers, only appending -rXXX for local versions. You can see what patches are applied pretty easily from the ebuild. In this case: http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-arch/tar/tar-1.16-r2.ebuild?rev=1.12&view=markup with patches http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-arch/tar/files/tar-1.16-remove-GNUTYPE_NAMES.patch?rev=1.1&view=markup http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-arch/tar/files/tar-1.16-segv.patch?rev=1.1&view=markup both of which are from upstream (sorry for the long URLs) > Once again, I wonder what the real patch level is that gentoo kernel is. > Its an arbitrary name that doesn't appear to follow the kernel.org naming > convention, so who knows how many patches may have been backported to it. That's a much trickier question, but again there's help to be had. See http://dev.gentoo.org/~dsd/genpatches/ for info on the patches applied, although it might be quicker to go to the [EMAIL PROTECTED] mailing list and present the issue there. They will also likely have the resources to help you in your search, or at least discover some extra datapoints for you. I'd help out, but I don't have any boxes on which I can experiment with kernel versions. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: backup when logging on to the network
On Thu, Mar 29, 2007 at 01:21:18PM +0200, Maarten De Quick wrote: > I have been testing with amanda and so far it works good. > We would like to have a configuration that when someone logs on to the > network here, a specified folder gets backupped (users using windows). Has > anyone already tried this and > found a solution. If you mean that the backup is triggered by a logon and runs immediately, you may have some trouble -- amanda is designed to schedule backups itself, and expects to do "runs" at fairly regular intervals (every day, every week, etc.). You may want to write a logon script that will copy (using robocopy, for example, or ntbackup) the specified folder to a "dropbox" for amanda. Then have amanda back up that dropbox, probably in an always-full configuration, and write a script that runs *after* the amanda run to empty that dropbox (assuming that it was successfully backed up). If the folder in question is or includes the user's roaming profile directory, you'll need to use a utility that's capable of copying open files, because NTUSER.DAT will already be loaded into HKCU. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Does amrecover automatically use "unflushed" files on the holding disk ?
On Fri, Mar 30, 2007 at 03:19:35PM -0400, Guy Dallaire wrote: >A quick question. >Suppose you run some level 0 backup (GTAR method) with amanda and leav >the files on the holding disks until there is enough files to fill a >tape and run amflush. Say this takes 5-6 working days. >Now, if, after 3 days, I have to restore something that has been >dumped on the disk on the first day and run "amrecover" on the client >and "setdate -MM-DD (today - 3 days)" >Are the holding disk files "indexed" ? Will amanda use them and not >ask for a tape when comes the time to extract ? Quick answer: yep! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Compression
On Wed, Apr 04, 2007 at 07:36:03PM -0400, Jon LaBadie wrote: > - edit the curinfo files and add a set of fake historical comp-rates If editing makes you nervous you can also use 'amadmin export' / 'amadmin import'. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amrecover using invalid ssh options on Solaris?
On Fri, Apr 06, 2007 at 02:24:44PM -0500, Lee, Raymond wrote:
> Search for PreferredAuthentications in
> {amanda_source}/common-src/ssh-security.c
>
> I don't know C, but maybe you can edit that and recompile? Or maybe the
> authors only intended Amanda to be compatible with OpenSSH.
I think that may have been an unspoken assumption, since so many
platforms run openssh at this point.
That said, we're always willing to patch, so if you find a set of
options that work for your SSH (following Lee's advice, above), please
send them along to [EMAIL PROTECTED] or via a SourceForge patch,
along with information we can use to identify your SSH version.
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: amrecover using invalid ssh options on Solaris?
On Fri, Apr 06, 2007 at 05:29:57PM -0400, Chris Hoogendyk wrote: > Believe it or not, that worked. I spent some time reading the man pages on > both the Solaris and OpenBSD systems to see what that option did and what > would happen without it on > Solaris. With SSH 2 the publickey method is tried first, so that, along with > the Batch option (which was already in the code) worked. I found: > >/* > * Arguments to ssh. This should also be configurable > */ >#define SSH_ARGS"-x", "-o", "BatchMode=yes", "-o", > "PreferredAuthentications=publickey" > > and just removed the last option and did a `make && make install`. > > I actually had to play a little with the restrictions on the authorized_keys > file (I'm not sure yet what the problem was there), but I was able to run > amrecover, do listhosts, > sethost, listdisks, setdisk, and history. I didn't want to actually recover > any files, because it is the end of the day Friday and I didn't want to be > shuffling tapes. So I'll have > to do a more thorough test on Monday. Oops, sorry for the premature reply to the earlier message. Consider the above duly noted. Thanks! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: testing a patched tar question.
On Sat, Apr 07, 2007 at 01:38:12PM -0400, Gene Heskett wrote: > What we are left with, when the linux kernel finally gets this patch for > good (its been reverted for now based on my findings, but its a good > patch, and really needs to be done at some point even if we do have to > play a little 52 pickup by doing an amanda restart from square one, which > will fix it when the patch hits production status) > we will have to treat amanda as if its a restart from square one, slowly > feeding it the big dle's, one per run. > > This is a case of being forewarned might be forearmed. Not much else we > can do at this point. One possibility might be to work with the GNU Tar folks to write a script/app to convert the data stored in the list files. Then the Amanda docs could warn about whatever kernel upgrade will trigger this, instructing users to run this script or app against their /gnutar-lists directories simultaneously with the upgrade. I'm still far from having a setup where I could test this sort of thing, but if their response to the idea is that it'd be too much trouble, I may be able to take a first swing at the script, if you (Gene) are willing to test it out. I'm assuming the list file format is a fairly straightforward packed-record format. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Doing all the work, not writing it to tape
On Sat, Apr 07, 2007 at 12:10:16PM -0600, Chris Cameron wrote:
> app01-/md/dsk/d5 0 184270 00.00:22 2399.7 N/A N/A
>From the look of these, the original (uncompressed) backup is succeeding
(it takes some amount of time, and is pretty big), but the compressed
size is 0. Perhaps something's wrong with your compression
configuration? You could find out more by checking the dumper logs on
the client or server, depending on where the compression is happening,
or by turning off compression altogether for a run, to see if that gets
things working.
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: testing a patched tar question.
On Sun, Apr 08, 2007 at 08:29:53PM -0500, Marc Mengel wrote: > Couldn't someone hack up a utility to do a major number swapout in the > file where tar keeps track of what is in the last incremental/full/etc.? That's what I suggested in http://tech.groups.yahoo.com/group/amanda-users/message/62562 I'm a little busy to work on it at the moment, if you're interested in taking up the task! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: testing a patched tar question.
On Mon, Apr 09, 2007 at 12:05:01PM -0400, Gene Heskett wrote: > Subtract the 00h, and you have the 254 its currently sitting at, > apparently subject to the whims of an individual boot. If I build md as > a module, then md will get 254 and device-mapper (dm_mod) will get 253, > and if I build pktcdvd, the packet writing util for burning cd/dvd's, it > will get one of those numbers, shoving device-mapper down to 252. This > number does not change AFAIK, for any file/directory on that particular > disk. To demo: Is it the case, then, that any block device loaded as a module will get a dynamically generated major device number? Or just devices which don't have a fixed major yet? > Device: fe00h/65024dInode: 11534709Links: 1 > And an inspection of the revelant files says its the decimal version, > present as the first number of every line in the file AFTER line 1. So > this is doable by a bash script I believe. But I'll need a nap and 3 > more cups before I start that project. Could you send me a copy of your incremental file? AFAICT, they're binary files, so I'm not sure how you're speaking of "lines".. If there's private info in there, please use tar to make a new incremental of a non-private directory, rather than munging the file. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Troubleshooting tapeing action?
On Fri, Apr 20, 2007 at 01:12:22PM -0400, Gene Heskett wrote: > In watching the write traffic into /dev/hdd, where my vtapes are located, I'm > seeing, particularly for the larger sized dle's, a write pattern that > resembles a picket fence in the gkrellm display. I have 60 some GB of > holding disk, the reserved is set for about 30%, and the largest dle is less > than the size of a vtape as set in the tapetype. Total data is about 46GB. > > It seems to me that when a dle has been collected into the holding disk, then > a taper should fire up and just dma the data from the holding disk to the > vtape, but I'm seeing writes of less than 10KB, interspersed with 55MB, > reported by the gkrellm utility display. hdparm says the disk is about a > 75MB/Sec disk. Unfortunately, it's not practically possible to "just dma the data".. We looked into a few reasonably portable ways to get the kernel to accelerate disk transfers (O_DIRECT, various madvise flags), and the results were fairly inconclusive. > How best can I troubleshoot this? Well, first, you shouldn't expect to get anywhere near the platter speed of your disk, particularly with ext3 or its brethren. I hear that XFS is capable of higher speeds, but that's unconfirmed and I've never used it. For ext3, somewhere around 40-50MB/s is probably the maximum sustained write-only bandwidth you'll see (based on my experience). You say that both your holding disk and your vtapes are on the same drive. That means that reading from one and writing to the other requires the drive to seek between the relevant files, which is going to be *very* slow. I'm not sure exactly what gkrellm is measuring (individual write() calls or total writes over a certain period?). The two suggestions I have are: - use 'iostat' instead as a rough IO measurement tool - annotate the amanda source to call dbprintf() at the relevant read() and write() calls, along with the sizes requested and actually performed. I think the bottom line is: this might be an interesting exercise, but will probably not lead to any substantial proposed changes in amanda. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Troubleshooting tapeing action?
On Fri, Apr 20, 2007 at 05:13:05PM -0400, Gene Heskett wrote: > And moving the holding disk would only be to another disk on that same cable, > only marginally faster. It would save the seek time, but that's about it. FWIW, that would be a *lot* faster. The major speed problem with disks is seek time, not bus capacity. > That's what I was afraid of. I have the memory buffer set at 90, and since > I've got a gig of ram, would increasing that be of any assistance? OTOH, I > can do that and find the answer fairly quickly. It will use 720 in the next > incarnation. 90 was only a bit over 2 megs, downright puny. That may help. A bigger buffer allows the elevator algorithm more elbow room to schedule things with minimal seeking. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amrecover issue
On Thu, May 03, 2007 at 10:18:34AM -0700, anthonyh wrote: > > Hi Guys,settape x:/backup/amanda/dumps/tape01 > > Thank You for replying this mail. Well actually i'm a bit confused with the > way the amanda recovers the data. > > Is it true that the host in the command "settape > :file:/backup/amanda/dumps/tape01" refers to the amanda tape server? > > Newbie here guys. Yes -- that's correct. If you're on the tape server itself, you should use e.g., localhost:file:/backup/amanda/dumps/tape01 Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Invalid value for ai_flags
On Thu, May 03, 2007 at 06:57:53PM -0700, Richard Stockton wrote: > ERROR: Cannot resolve `localhost': Invalid value for ai_flags > WARNING: bak-05: selfcheck request failed: getaddrinfo(bak-05): Invalid value > for ai_flags > So why is amanda unable to resolve "localhost"? It looks like it's not actually a resolution issue, but a flags issue (a bug). I'll look into it today. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: 2.5.2 compilation failure on irix-6.5.x
This is the same error as in
http://groups.yahoo.com/group/amanda-hackers/message/5401
the same patch is attached here -- could you let us know if it fixes the
compile?
Dustin
On Mon, May 07, 2007 at 12:05:44PM -0400, Jean-Francois Malouin wrote:
> First go at amanda-2.5.2 on a system running irix-6.5.x
> and compile fails with the error:
>
>
> cc-1040 cc: ERROR File = amanda.h, Line = 623
> An identifier is expected.
>
> #define vstrallocf(...)
> debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__)
> ^
>
> cc-1204 cc: WARNING File = amanda.h, Line = 957
> The indicated declaration is not visible outside of the function.
>
> extern int check_security(struct sockaddr_storage *, char *,
> unsigned long, char **);
>^
>
> 1 error detected in the compilation of "alloc.c".
> make[1]: *** [alloc.lo] Error 1
> make[1]: Leaving directory
> `/stuff/amanda-source/amanda-2.5.2/common-src'
> make: *** [all-recursive] Error 1
>
>
> jf
> --
> <
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
diff -u -r --show-c-function --new-file
--exclude-from=/home/martinea/src.orig/amanda.diff
--ignore-matching-lines='$Id:' amanda-2.5.2/common-src/amanda.h
amanda-2.5.2.sockaddr_storage/common-src/amanda.h
--- amanda-2.5.2/common-src/amanda.h2007-04-10 06:56:00.0 -0400
+++ amanda-2.5.2.sockaddr_storage/common-src/amanda.h 2007-05-04
16:40:18.0 -0400
@@ -268,6 +268,9 @@ struct iovec {
#include
#endif
+#define sockaddr_storage sockaddr_in
+#define ss_family sin_family
+
/* Calculate the length of the data in a struct sockaddr_storage.
* THIS IS A HACK.
*
db-based infofiles
In working on cleaning up the amanda codebase, I discovered that at least some of the db-based infofile backends (--with-db=gdbm, ndbm, db, dbm) probably don't work. I talked with Jean-Louis Martineau, and he mentioned that they have been deprecated for a long time in favor of the text database. I'd like to remove this support completely in the next release. So: are you or anyone you know using non-text infofiles? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amanda upgrade questions
On Wed, May 09, 2007 at 09:38:20PM -0400, Guy Dallaire wrote: >2.5 seems pretty scary. I see a lot of problems on the list. Is it >stable, or is it experimental ? 2.5.2 is a stable release. A lot of the recent problems have been small bugs that occurred in configurations not tested during the beta phase. That is to say, the release itself is in no way "experimental", but the testing process could use some work -- that's a discussion I would be happy to have here, but in another thread. As for upgrading -- you're contemplating a rather significant version bump, and I personally hesitate to answer because I'm not very confident that I'll be right[1]. I suspect others may be reticent for similar reasons. I think that things will go smoothly for you in an upgrade, as Amanda development remains fairly conservative in maintaining backward compatiblity. The port-range options still exist and do the same thing. I *think* that the on-disk formats and the on-the-wire network protocols are also compatible; hopefully someone will reply loudly to this email if I'm wrong about that. Probably your best bet is to just try it out in as "safe" a manner as you can muster. Dustin [1] I was absent from the Amanda "scene" from somewhere in 2.4.4 to about 2.5.1, so I'm not familiar with the transition. -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Hardware suggestion
On Thu, May 10, 2007 at 08:59:40AM +0700, Olivier Nicole wrote:
> Could anyone advise on some disk tray solution that is stong and
> reliable and will handle a lot of manipulation. idealy I wouldbe
> looking at one tray bay and 5 or 6 trays for the disks.
I think your best bet may be a set of Firewire enclosures.
If there is hardware out there rugged enough to hot-swap drives in trays
daily (e.g,. with a SCSI or SATA backplane), I expect it will be at a
much higher price-point (both for the hot-swap equipment, and for the
flavor of drives it requires) than equivalent commodity Firewire
hardware.
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: amanda-client version
On Thu, May 10, 2007 at 01:35:46PM -0400, Steven Settlemyre wrote: > How do I find out which version of amanda-client is running on my hosts? I > found the debian ones through the package manager, but wonder if there's a > command-line switch to use? Use amgetconf build.VERSION if the box has 'amgetconf'; otherwise you can look in your sendbackup or sendsize debug logs. -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Ooops
On Thu, May 10, 2007 at 12:17:51PM -0400, Christopher Linn wrote: > i am curious. how many platforms does zmanda have and use for > test builds and amanda testing? OSs and hardware? One of my current projects is to put a more thorough testing process in place -- mostly because it's been *my* patches which have turned out to be non-portable! For the community version, we currently focus our testing on the platforms listed on http://zmanda.com/downloads.html: RHEL 3-5, FC 3-6, OpenSUSE 10, SLES 9-10, and Windows (cygwin). That testing takes place on releases, *not* on the snapshots. The bug which started this thread was in last night's snapshot. For other platforms, we rely on users to test betas, since the Amanda user community has a much wider array of hardware and configurations than we could *ever* hope to test in-house. I have a few nascent ideas of how we could improve this process, but I would prefer to hear others' suggestions and proposals before I bias the conversation with my thoughts. Dustin P.S. As for hardware -- well, virtualization is a wonderful thing ;) -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: first attempt with tape spanning...nogo.
On Thu, May 10, 2007 at 03:00:52PM -0400, Jean-Louis Martineau wrote: > You can't mmap a 10 Gb and alloc a 2GB buffer. > I don't know what are the limit on irix. > Compile in 64 bits mode and/or use lower value for tape_splitsize and > fallback_splitsize I just added a troubleshooting entry on the wiki; Jean-Francois, please feel free to update with your findings. http://wiki.zmanda.com/index.php/Memory_allocation_failed Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amanda-2.5.1p3-20070516 amfetchdump broken
On Thu, May 17, 2007 at 12:27:27PM -0700, Christopher McCrory wrote:
> it looks like amfetchdump is sending misc info to /sbin/restore instead of
> the terminal. ( stdout vs. stderr ?)
Good diagnosis! The source bears out your observation.
Could you try the attached patch, and verify that it solves the problem?
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Index: server-src/find.c
===
--- server-src/find.c (revision 345)
+++ server-src/find.c (working copy)
@@ -106,7 +106,7 @@
logs += search_logfile(&output_find, tp->label, tp->datestamp,
logfile);
}
if(logs == 0 && strcmp(tp->datestamp,"0") != 0)
- printf("Warning: no log files found for tape %s written %s\n",
+ fprintf(stderr, "Warning: no log files found for tape %s written
%s\n",
tp->label, find_nicedate(tp->datestamp));
}
amfree(logfile);
@@ -189,7 +189,7 @@
}
}
if(logs == 0 && strcmp(tp->datestamp,"0") != 0)
- printf("Warning: no log files found for tape %s written %s\n",
+ fprintf(stderr, "Warning: no log files found for tape %s written
%s\n",
tp->label, find_nicedate(tp->datestamp));
}
amfree(logfile);
Re: gtar version
On Fri, May 18, 2007 at 02:32:13PM -0400, Brian Cuttler wrote: > > Sorry, hate to ask this, but one of my DLE's has outgrown the > tape drive and I want to divide it into multiple TAR-DLE entries > but I'm having trouble finding an installable version of gtar > that is a correct version for Amanda and my OS. > > I'm running Solaris 9 and believe that I should use one of > gtar 1.13.19, 1.13.25, 1.15.1 per The 1.15 series is preferred; see http://wiki.zmanda.com/index.php/Installation#Dependencies > Unfortunately the box is being a FW, and the replacement system > with the new (much larger) tape is not online yet. I'm not sure what you mean? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: gtar version
On Fri, May 18, 2007 at 02:52:50PM -0400, Brian Cuttler wrote: > On Fri, May 18, 2007 at 01:47:47PM -0500, [EMAIL PROTECTED] wrote: > > On Fri, May 18, 2007 at 02:32:13PM -0400, Brian Cuttler wrote: > > > > > > Sorry, hate to ask this, but one of my DLE's has outgrown the > > > tape drive and I want to divide it into multiple TAR-DLE entries > > > but I'm having trouble finding an installable version of gtar > > > that is a correct version for Amanda and my OS. > > > > > > I'm running Solaris 9 and believe that I should use one of > > > gtar 1.13.19, 1.13.25, 1.15.1 per > > > > The 1.15 series is preferred; see > > http://wiki.zmanda.com/index.php/Installation#Dependencies > > Newer being better, but is there a binary available that I can > install on my Solaris 9 system, if so, where can I download it from ? Hopefully some of the Solaris folks around here can speak up (Chris? Peter?). AFAIK, sunfreeware.com is the place to go. They only list 1.16 on the front page, but a look at ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/ shows: tar-1.13.19-sol9-sparc-local.gz tar-1.13.94-sol9-sparc-local.gz tar-1.14-sol9-sparc-local.gz tar-1.15.1-sol9-sparc-local.gz tar-1.16-sol9-sparc-local.gz so perhaps one those will do the trick for you? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
amrecover on ubuntu
Im using amrecover on a ubuntu server. amdump and amcheck work great. When I try to run amrecover I get this error. AMRECOVER Version 2.5.1p1. Contacting server on localhost ... [ ][request failed: timeout waiting for ACK]
vtape sizes
Im trying to backup to some virtual tapes. My hard drive is 1.2 tb. The /home directory on the remote host is 4 gigs. I want to run the backup every night and do a full backup on the first night. I want to have a 7 day rotation. When I run the backup I get this error. 65.0.0.0 /home lev 0 FAILED "[dump larger than available tape space, 2088825 KB, but cannot incremental dump new disk]" This is what I have. dumpcycle 7 days runspercycle 7 tapecycle 7 tapes
Incremental Backups
Im trying to setup incremental backups. I would like to perform 1 full backup during a 7 day period and then incremental the following days. Here is my config. dumpcycle 7 days runspercycle 1 tapecycle 15 tapes Here is my disklist amoverview DailySet1 date 07 host disk 07 65.209.1 /etc 11 65.209.1 /home00 65.209.1 /mysql-backups 11 65.209.1 /var/www 11 any help would be great.
amandad stand alone????
Can anyone tell me if it is possible to run amanda in a stand alone config (i.e. not via inetd or brethren)? I am trying to set up amanda on a group of external servers. Because of the limited number of services offered we don't/won't want to run inetd. What we want to do is be able to start and stop amandad only during the backup window. This way we can wrap the amandad startup in a script that only enables the related ipchains rules during the window. If amandad doesn't have a daemon option can anyone provide ideas on what might be options other than inetd/xinted? Thanx (hopefully my objectives make sense) -Dustin
Re: gtar version
On Fri, May 18, 2007 at 03:32:59PM -0400, Brian Cuttler wrote: > Thank you, that is what I needed, I hit the web page and as you said, > found only 1.16, the 1.15.1 should do the trick for sure. > > Apparently the amanda binary I'm using didn't have GNUTAR defined, > I'm trying to put a binary on the amanda user's path so its found > anyway, even without a proper variable definition. > > Linking (# ln -s) GNUTAR to the binary will do the job ? > In what directory should I put the GNUTAR link ? I'm not entirely clear on your situation, but I *think* that you should be able to add a link, named 'gtar' (not GNUTAR), from any directory in $PATH to the GNU tar binary, e.g., # ln -s /usr/bin/gtar /usr/local/bin/tar (assuming that the sunfreeware package installed the binary at /usr/local/bin/tar). Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: gtar version
On Fri, May 18, 2007 at 02:46:21PM -0500, Dustin J. Mitchell wrote: > I'm not entirely clear on your situation, but I *think* that you should > be able to add a link, named 'gtar' (not GNUTAR), from any directory in > $PATH to the GNU tar binary, e.g., > # ln -s /usr/bin/gtar /usr/local/bin/tar > (assuming that the sunfreeware package installed the binary at > /usr/local/bin/tar). Sorry to self-reply. Amanda looks for 'tar', not 'gtar', if it doesn't find GNU tar at configure time. That means that you need to find a way for Amanda to discover GNU tar as 'tar' in its PATH, without interfering with any applications that expect Solaris 'tar' in their PATH. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: planner: estimate of level 1 failed.
On Mon, May 21, 2007 at 01:04:47PM -0300, Bruce S. Skinner wrote: > I'm only getting level 0 dumps for all my disks as estimates for level > 1 are failing. I'm using gnu tar to do the dumps. I've included some > excerpts pertaining to an example disk (/boot) from two days consecutive > amdump log > files. Does anyone have a suggestion why estimates may be failing or > where I should look next? What version of tar are you using? See: http://forums.zmanda.com/archive/index.php/t-299.html Dustin
Re: amverify lockup
On Mon, May 21, 2007 at 12:29:47PM -0600, Glenn English wrote: > I used to do an amverify after every backup, but I started finding my > computer frozen every morning after a backup. I've noticed for some > time, that when I do anything with mt, nothing else can happen on the > computer until it's finished -- no mouse, no menu-bar clock, nothing. > > Is it *conceivable* that interrupts are being disabled, and somebody's > doing polling I/O? I'll grant "conceivable", but not much more. I haven't heard of such a thing. Either way, it's not really a matter for Amanda, but rather for the in-kernel drivers you're using (a userspace app can't disable interrupts like that). That is, if 'mt' is hanging your system, it's probably hung in the kernel, and Amanda's just going to hang out waiting for it. Do your kernel logs reveal anything interesting? Is everything else *really* dead? You mention no mouse, which seems to imply X. X behaves very badly when it's heavily paged, so if 'mt' or some other application is burning through CPU and RAM, you might see the behavior you've described. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: gtar and related issues
On Wed, May 23, 2007 at 09:37:46AM +0200, Stefan G. Weichinger wrote: > General suggestion (maybe I already suggested that sometimes): > > Why not test for the version of tar inside amanda? > > configure could test for it at compile-time, amcheck at check-time. > Grep "tar --version", compare the result with a list of good and bad > tar-releases, WARN if a known problematic version is detected. > > Optionally add a parameter to turn that check off, for people who want > to override that out of specific reasons. > > Wouldn't that be better than relying on (new) users to research that > information, possibly AFTER running into problems? That's a great point! It would also be great to have the relevant versions more prominently displayed in the wiki -- currently the relevant documentation is scattered in a few forum posts and mailing list archives. I'm swamped at the moment, so any help would be appreciated -- anyone want to produce a configure.in patch and/or edit up the wiki? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: changerfile
On Wed, May 23, 2007 at 09:03:37AM -0400, McGraw, Robert P. wrote: > The following is from the chg-lib.sh file. What file is the "changerfile" > that is mentioned below. > > # These are the defaults discovered by configure when Amanda was installed. > # They can be overridden here, or by by 'mt_binary' and 'mtx_binary', > # respectively, in the changerfile (currently only for chg-zd-mtx.sh and > # chg-manual.sh). The changerfile is the file specified in amanda.conf, e.g., changerfile "/etc/amanda/Conf/changerfile" Note the end of that comment, though: only chg-zd-mtx.sh and chg-manual.sh use changerfiles; the other changers were not updated to use a changerfile for this purpose. > I want to set mt_binary and mtx_binary at compile time but I cannot find > where thisis located. If you want to set it at *compile* time, you can use the following in your ./configure: ./configure MT="/path/to/mt" MTX="/path/to/mtx" --with-user= which is a way of overriding the search made in the configure script. If there's somewhere "obvious"[1] that configure should be looking for mt/mtx, and it's not looking there, let me know and I'll add it to the search path. Alternately, if this is the kind of thing a lot of people need to do (speak up!), I can add --with-mt and --with-mtx options. Dustin [1] Meaning something like, "Everyone knows mtx is always in /foo/bar/frob/bin on Mynix 4.3.2!" -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: chunker error
On Wed, May 23, 2007 at 04:55:27PM -0400, McGraw, Robert P. wrote: > I looked in the amanda group searching for "could not bind to any port" but > did not fine any helpful hits. There were a few errors on Solaris builds in the 2.5.2 release. Could you try the latest snapshot from http://www.zmanda.com/community-builds.php And see if that works better? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Fwd: Amanda newbie with permissions error on labeling and connecting to client
On Wed, May 23, 2007 at 03:48:25PM -0700, Nick Peterson wrote: > file://space/vtapes/DailySet1/slots: Permission denied > amcheck-server: slot 19: tape_rdlabel: tape open: What are the permissions on that directory? It should be owned by the amanda user. Post the output of 'ls -alR /space/vtapes/DailySet1/slots' if that doesn't help. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amflush problem with 2.5.2-20070508
On Thu, May 24, 2007 at 09:58:44AM -0400, Jean-Francois Malouin wrote: > My first attempt at flushing the holdding disk > with Amanda-2.5.2-20070508 fails: > > su amanda -c "/opt/amanda/amanda4/sbin/amflush stk_80-conf4"Scanning > /holddisk/conf4/stk_80... > 20070408091512: found Amanda directory. > 20070507221512: found Amanda directory. > 20070509221513: found Amanda directory. > 2007051514: found Amanda directory. > > Multiple Amanda directories, please pick one by letter: > A. 20070408091512 > B. 20070507221512 > C. 20070509221513 > D. 2007051514 > Select directories to flush [A..D]: [ALL] > Could not find any valid dump image, check directory. > > Looking at the content of the holdding disk: Which directory is this? There should be four subdirectories of stk_80, one with each of the timestamps above. > drwx--2 amanda sys 4096 May 24 02:12 ./ > drwxr-xr-x6 amanda sys 90 May 24 09:51 ../ > -rw---1 amanda sys 63488 May 23 09:56 > yorick._data_ado_ado1_slsj_subjects.2 > -rw---1 amanda sys 0 May 23 17:00 > yorick._data_ado_ado1_slsj_transfer.2 > -rw---1 amanda sys 0 May 23 20:07 yorick.ado1.1 > -rw---1 amanda sys2480128 May 23 11:08 yorick.ado1_slsj.1 > -rw---1 amanda sys 0 May 24 01:17 yorick.mril4_2.1 > -rw---1 amanda sys 135168 May 23 09:17 yorick.mril4_3.1 > -rw---1 amanda sys 7268272128 May 23 07:11 yorick.mril4_4.0 Have you recently changed your 'usetimestamps' setting? A mismatch between the timestamp or datestamp in each dumpfile and the timstamp (never a datestamp) that is the name of the directory can cause an error like the one you're seeing. Can you run the following at the bash prompt and send us the result? for i in `find /holddisk/conf4/stk_80 -type f`; do echo $i; head -n1 $i; done Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda - unable to create temporary directory
On Fri, May 25, 2007 at 05:47:33PM -0400, Jon LaBadie wrote: > ISTR, from your original message, that the "Strange" message said > unable to create temporary directory under, /tmp, /var/tmp, and /. > I don't recall it saying anything about /tmp/amanda. I don't > understand why you are fixed on that particular directory. That was confusing me too :) To clarify, ufsdump is prbably trying to create temporary files on its own (who knows why, but lots of programs do it!). Because of some permissions problem, it is unable to create those files. Likely causes: - bad permissions on /tmp, /var/tmp, and / - ufsdump not running as the correct user - selinux or other kernel-based security mechanisms As Jon said, the problem is on the Amanda client, not on the server. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: feature request : infos about holdingdisk-content
Stefan -- The new 'amadmin holding list' command gives that sort of result. If you run, e.g., amadmin DailySet1 holding list -l It will give you a detailed listing; an example from my development box: size (kB) lv dump specification 1720 knuth /tmp/amanda/prefix/etc 20070529 62 1 knuth /tmp/amanda/prefix/etc 20070529 'amadmin holding delete' can then be used to delete files from the holding disk and update indexes appropriately, if you'd like. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: feature request : infos about holdingdisk-content
On Wed, May 30, 2007 at 12:54:51AM +0200, Stefan G. Weichinger wrote:
> Is that documented somewhere?
Only in the manpages at the moment. It's on my wiki todo list.
> When was it added?
2.5.2.
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: Configure error
On Wed, May 30, 2007 at 10:13:47AM -0500, Paul Crittenden wrote: >I am trying to install amanda backup software on my server and I get >the error, " configure: error: *** --with-user=USER is missing", when >I run "./configure". > >Can anyone point out what I need to do? Add "--with-user=USER" to your invocation of ./configure ;) Amanda needs to know the user and group it will run as -- probably ./configure --with-user=amanda --with-group=amanda ... But you should *definitely* look at ./configure --help to see what other options you'll be interested in! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amdump - backup error
On Wed, May 30, 2007 at 11:24:28AM -0500, Jeanna Geier wrote: > sendsize[30823]: time 0.007: running "/usr/sbin/backup 0sf 1048576 - /etc" > sendsize[30823]: time 0.010: running /usr/local/amanda_2.5.2/libexec/killpgrp > sendsize[30818]: time 0.010: waiting for any estimate child: 1 running > sendsize[30823]: time 0.044: backup: Extra argument. Try backup --help for > more info. > > Does anyone know what these messages are caused by and how > to correct them? Or see anything else that is causing my > dump to error out that I'm missing?? It looks like Amanda is calling /usr/sbin/backup incorrectly. I've forgotten what flavor of system you're on, but if you can figure out how 'backup' *should* be called on your system, then we either need to figure out how you can configure Amanda to call it that way, or add a patch to Amanda to detect and correctly handle the differences. Dustin P.S. Thanks for chipping in and answering others' questions while you're asking your own! -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amdump - backup error
On Wed, May 30, 2007 at 12:36:17PM -0500, Jeanna Geier wrote: >Send bug reports to [EMAIL PROTECTED] Interesting -- so this is a part of GNU tar. You would probably be better off simply using GNU tar directly, then. It seems that this particular backup script doesn't support the options Amanda needs (and my GNU tar install doesn't include anything named 'backup'..) Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amdump - backup error
On Wed, May 30, 2007 at 01:19:42PM -0500, Jeanna Geier wrote: > I looked in the amdump script, and I don't see anything in > there that I can/should modify - but it has to be getting > called from somewhere, because when I run 'amdump > DailySet3', it's calling 'backup' from within there > somewhere... See http://wiki.zmanda.com/index.php/Amanda.conf#DUMPTYPE_SECTION You want to use 'program GNUTAR' in your dumptypes. Amanda has detected 'backup' as the local DUMP implementation (other, completely different programs are called 'backup' on other systems) Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: FW: amrecover problem
On Wed, May 30, 2007 at 01:41:17PM -0400, McGraw, Robert P. wrote: > > amrecover> cd jflack > > amrecover: regex "/jflack/$/": unknown regex error > > > > ... and amrecover exits out to the shell. Interesting -- I get the same regex, but my regex library (in libc) doesn't complain about it. I haven't heard of anyone else having this problem, either. Do your local modifications include any sort of funny business with the regex library? Remind me what OS you're running again? I get: amrecover> setdisk /tmp/amanda/prefix/etc 200 Disk set to /tmp/amanda/prefix/etc. amrecover> cd amanda regex: ^amanda$ regex_path: amanda/$ path_on_disk: /amanda/$ path_on_disk_slash: /amanda/$/ /tmp/amanda/prefix/etc/amanda With the following patch applied: Index: recover-src/set_commands.c === --- recover-src/set_commands.c (revision 385) +++ recover-src/set_commands.c (working copy) @@ -324,6 +324,7 @@ amfree(regex); return; } +fprintf(stderr, "regex: %s\n", regex); /* * glob_to_regex() anchors the beginning of the pattern with ^, * but we will be tacking it onto the end of the current directory @@ -336,6 +337,7 @@ regex_path[strlen(regex_path) - 1] = '\0'; strappend(regex_path, "/$"); } +fprintf(stderr, "regex_path: %s\n", regex_path); /* convert path (assumed in cwd) to one on disk */ if (strcmp(disk_path, "/") == 0) @@ -345,6 +347,7 @@ path_on_disk = vstralloc(clean_disk_path, "/", regex_path, NULL); amfree(clean_disk_path); } +fprintf(stderr, "path_on_disk: %s\n", path_on_disk); cd_dir(path_on_disk, uqglob); @@ -404,6 +407,7 @@ DIR_ITEM *ditem; path_on_disk_slash = stralloc2(path_on_disk, "/"); +fprintf(stderr, "path_on_disk_slash: %s\n", path_on_disk_slash); nb_found = 0; -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amdump - backup error
On Wed, May 30, 2007 at 01:47:57PM -0500, Jeanna Geier wrote: > Thanks for all of your replies and help with this! > > I do have SEVERAL "GNUTAR" dumptype parameters > declared...is there an issue with having more than one in > my conf file?? I added the last one in the block per the > WIKI instructions > (http://wiki.zmanda.com/index.php/Test_environment_with_virtual_tapes), > otherwise, the rest were already present in there... Which dumptypes are you using in your disklist? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: autoflush doesn't?
On Thu, May 31, 2007 at 09:25:58AM -0400, Gene Heskett wrote: > It seems we haven't an autoflush function anymore. It did not flush > yesterday > mornings EOT leftovers this morning, so I am doing it by hand. This > shouldn't be required when there is a line: > > autoflush yes > > in my 'Daily' amanda.conf > > This is (brought to you by Amanda version 2.5.2-20070525), on an uptodate FC6 > system running kernel 2.6.22-rc3 on an AMD XP-2800 cpu. Did the 'amflush' work? If not, then what is your "usetimestamps" setting, and what does your holding disk look like? Please send part of an ls -lR /path/to/holding/. Thanks! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: autoflush doesn't?
On Thu, May 31, 2007 at 11:40:00AM -0400, Gene Heskett wrote: > Humm, odd indeed. I did get an email from the amverify phase of flush.sh, > but > the sub-terminal and shell I ran it from are gone! And I did not get an > email from the flush itself, nor did it delete whats in the holding disk. > > [EMAIL PROTECTED] ~]# grep usetimestamps > /usr/local/etc/amanda/Daily/amanda.conf > # the usetimestamps option is enabled, however, Amanda can track as many > usetimestamps yes > > [EMAIL PROTECTED] ~]# ls -lR /dumps > /dumps: > total 4 > drwx-- 2 amanda disk 4096 May 30 01:58 2007053504 > > /dumps/2007053504: > total 6052 > -rw--- 1 amanda disk 43008 May 30 01:58 coyote._bin.1 > -rw--- 1 amanda disk 301829 May 30 01:55 coyote._etc.1 > Scanning /dumps... > 2007053504: found Amanda directory. > Could not find any valid dump image, check directory. Can you send along 'head -n1' of coyote._bin.1? The problem we had with this recently was that the holding-disk scanning code looked for a timestamp in the holding file header, but when usetimestamps=no, the header only contained a datestamp. But that was fixed on 5/15 (r329), and you're not using usetimestamps=no, so I'm somewhat stumped. Please also send the output of 'amadmin Daily holding list -l'. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: autoflush doesn't?
On Thu, May 31, 2007 at 03:26:22PM -0400, Gene Heskett wrote:
> [EMAIL PROTECTED] 2007053504]# head -n1 coyote._bin.1
> AMANDA: FILE 2007053504 coyote /bin lev 1 comp N program /bin/tar
This is as it should be - that holding file contains a full timestamp.
> [EMAIL PROTECTED] 2007053504]# su amanda -c "amadmin Daily holding list
> -l"
> Scanning /dumps...
> 2007053504: found Amanda directory.
> Scanning /dumps/2007053504...
> size (kB) lv dump specification
> 33 1 coyote '/GenesAmandaHelper-0.5' 2007053504
> 42 1 coyote /bin 2007053504
> 2951 coyote /etc 2007053504
> 3151 coyote /opt 2007053504
> 1241 coyote /tmp 2007053504
> 33 1 coyote /usr/X11R6 2007053504
> 72 1 coyote '/usr/dlds-misc' 2007053504
> 42 1 coyote '/usr/dlds-rpms' 2007053504
> 2172 1 coyote /usr/dlds 2007053504
> 42 1 coyote /usr/games 2007053504
> 2151 coyote /usr/include 2007053504
> 52 1 coyote /usr/kerberos 2007053504
> 1123 1 coyote /usr/libexec 2007053504
> 62 1 coyote /usr/man 2007053504
> 62 1 coyote /usr/movies 2007053504
> 1121 coyote /usr/pix 2007053504
> 1185 1 coyote /usr/share 2007053504
>
> Is this helpfull?
Yes, and no -- it showed me that everything was in order, but didn't
really lead me to the problem. Nevertheless, I've found an error that
would cause what you're seeing. Can you apply the attached patch and
see if it helps?
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Index: server-src/holding.c
===
--- server-src/holding.c(revision 385)
+++ server-src/holding.c(working copy)
@@ -194,7 +194,7 @@
if (date_list) {
date_found = 0;
for (dl= date_list->first; dl != NULL; dl = dl->next) {
- if (strcmp(dl->name, workdir->d_name)) {
+ if (strcmp(dl->name, workdir->d_name) == 0) {
date_found = 1;
break;
}
Re: amtapetype - silly thing I tried
On Fri, Jun 01, 2007 at 10:40:38AM -0400, Jon LaBadie wrote:
> On Fri, Jun 01, 2007 at 08:00:21AM -0400, Jean-Louis Martineau wrote:
> > Jon,
> >
> > amtapetype should terminate once it fill the disk.
> >
> > Jean-Louis
>
> I didn't see any smiley there ;) so I'll just note that once
> amtapetype seemed to recognize the file driver I half-expected
> it to also see the EOF like taper does.
If I understand correctly (and just to summarize), Jon, you expected
amtapetype to terminate when the tape was filled to its stated capacity
(stated in the tapetype definition..) the way taper does. Instead,
amtapetype runs until the OS returns ENOSPC ("No space available") and
then terminates, probably with a pretty accurate description of the
amount of space available on the partition.
Sound about right?
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: autoflush doesn't?
On Fri, Jun 01, 2007 at 02:31:27PM -0400, Gene Heskett wrote:
> On Thursday 31 May 2007, Dustin J. Mitchell wrote:
> >if (strcmp(dl->name, workdir->d_name) == 0) {
>
> I note this patch didn't make it into the Amanda 2.5.2-20070531 snapshot.
The general practice has been to post fixes and wait for confirmation
that they corrected the problem before committing them to subversion.
Sorry if that caused some confusion here.
> So I did it before I built it. Install & amcheck was normal.
Great! Let me know how the amflush and/or autoflush go.
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: chg-zd-mtx can't find mtx command.
On Mon, Jun 04, 2007 at 04:35:20PM -0700, Alan Jedlow wrote: > I've installed the RHEL RPMs from www.zamanda.com... currently > trying to figure out why "chg-zd-mtx" thinks mtx doesn't > exist: > > -bash-3.00$ whoami > amandabackup > -bash-3.00$ which mtx > /usr/sbin/mtx > -bash-3.00$ /usr/lib/amanda/chg-zd-mtx -info > mtx command (mtx) doesn't exist > -bash-3.00$ > > Suggestions? Thanks for the report! Ironically, it's just the check that's bogus -- chg-zd-mtx will run just fine in that situation. Try the attached patch, which just removes the checks. The problem is that the RPM was built on a machine without mtx installed, so it recorded the path to mtx as just 'mtx'. Then chg-zd-mtx, assuming it is given a fully qualified path, checks that the file exists. Because 'mtx' is an unqualified filename, the check fails. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/ Index: changer-src/chg-zd-mtx.sh.in === --- changer-src/chg-zd-mtx.sh.in(revision 385) +++ changer-src/chg-zd-mtx.sh.in(working copy) @@ -714,11 +714,6 @@ cleancount=`cat $cleanfile` accesscount=`cat $accessfile` -test -z "$MT" && Exit 2 "" "No mt command defined" -test ! -f "$MT" && Exit 2 "" "mt command ($MT) doesn't exist" -test -z "$MTX" && Exit 2 "" "No mtx command defined" -test ! -f "$MTX" && Exit 2 "" "mtx command ($MTX) doesn't exist" - Dig out of the config file what is needed varlist=
Re: old server 2.4.2p2 fails to backup newer client 2.5.1p1
On Wed, Jun 06, 2007 at 09:26:43AM -0400, Jon LaBadie wrote: > does this mean that the 2.5.1 default authentication is different > than in the 2.4 releases and thus breaks backward compatibility > without some config changes? No worries -- no such change has taken place. See common-src/conffile.c: 1299 conf_init_string(&conf_data[CNF_AUTH], "bsd"); Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda 2.5.1p3 gnutar permissions trouble
On Wed, Jun 06, 2007 at 09:48:51PM -0400, Jordan Desroches wrote: > I'm running into a problem with permissions when backing up a nfs mount. I'm > using gnutar, and while I can backup the entire mount just fine, if I try to > put just a subdirectory of > the mount in the disklist, I get "Permission Denied" errors from amcheck and > amdump. Any ideas as to what I'm doing wrong? The OS is Ubuntu Linux 7.04. > Thanks all! Hmm - at a guess, are you using an automounter? Could you paste the errors themselves, and any relevant debug files? Dustin P.S. Please consult, and feel free to update, the wiki page on the topic: http://wiki.zmanda.com/index.php/How_To:Backup_Partitions_Mounted_via_NFS -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: FAILURE AND STRANGE DUMP SUMMARY
On Fri, Jun 08, 2007 at 01:15:51AM -0700, fedora wrote: > Is there any proper mysql backup that can backup database without stopping > it?? You've already had a number of suggestions, so I'll just add one (and a shameless one, at that): ZRM for MySQL can back up MySQL databases without the need to dump them first or take them offline. See http://mysqlbackup.zmanda.com/ for documentation and downloads. For the other folks who posted scripts (wow! I haven't seen a response like that in a while!), please feel free to add the scripts and descriptions of them to http://wiki.zmanda.com, for those that are not already posted there. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda crashes if /tmp/amanda is full
On Wed, Jun 13, 2007 at 09:56:21AM -0400, Jon LaBadie wrote: > Does amanda use /tmp for anything other than writing the debug files? > > I ask because it seems to me that the backups themselves may be more > important than the debug files it can not write. > > Rather than controlled clean-up and terminate, perhaps a flag in > the debug message writing routines (are they self-contained as a > library function) could be used to stop write attempts and let the > backups proceed without debug files. Lots of things use /tmp, unfortunately including the external applications that Amanda runs. For example, it may not be possible to send mail in that circumstance. That said, the 'debug_printf' function (common-src/debug.c:67) is responsible for debug output. It calls through to fpritnf and vfprintf, but doesn't check the error return from either of those. So when /tmp fills up, Amanda will simply stop writing debug messages as you've described. If someone would like to do some additional investigation and suggest a fix or even submit a patch, that would be great! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: OT: LTO Barcodes
On Fri, Jun 15, 2007 at 02:21:32PM +0200, Harald Schioeberg wrote: > Hi, > > definately off-topic, but i have written a script to generate sheets > with LTO barcode labels. > > Still i think i can share it with the amanda community, and as i don't > know a good place for it, perhaps somebody here on the list will put it > to a place where others can find it :) > > > I hope that i don't violate list policies too badly with a 2k attachment. That's not so off-topic -- we always appreciate contributions. Probably the easiest way to contribute this would be to add it to the wiki at http://wiki.zmanda.com (see "Useful Amanda Tools"), either as a link or as text included in a new article, with any necessary accompanying documentation. Be sure to give yourself credit! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Virtual tape to Real tape cycles
On Fri, Jun 15, 2007 at 02:14:43PM -0400, Jon LaBadie wrote: > On Tue, Jun 12, 2007 at 04:27:32PM -0400, Charlie Reitsma wrote: > > Has there been any work on amanda being aware of backups going to > > virtual tape and then the virtual tape being archived to real tape? > > I'd love to be able to keep as much as possible on virtual tape but at > > some point I need to archive the data to an offsite location. But in > > order to do a restore I would need the index of the virtual tape > > associated with the real tape. Very likely, multiple real tapes would > > be required to hold a single virtual tape so the index might need to > > be rewritten to reflect the media change. I see the move from virtual > > tape to real tape more of a tape duplication - almost as if the > > virtual disk were looked at as the holding disk being flushed to tape. To Charlie's initial question -- this is a *hard* problem, and one for which a complete answer is a long, long way off. However, we are looking in that direction. In fact, the Device API is a step along the way, as it gives us a consistent way to talk about different devices (e.g., vtape and tape) and moving data between them. > Related to potential projects such as Charlie suggests: > > Does an documentation exist that might be called "Amanda Internals"? > Things that describe the backup process, authentication procedures, > network communications and particularly for this project, amanda > data location, layout, and parsing info? > > Obviously several amanda utilities can access these data. For example, > amoverview can lookup the dates and levels for each active DLE backup > and amrecover can determine on which tapes they are located. But > aside from reading the sources for these utilities is the location > and procedure for accessing these data documented somewhere? We created the "Developer Documentation" section on wiki.zmanda.com a few weeks ago. It's far from comprehensive, but it contains links to all of the developer-targetted documentation we could find, which includes descriptions of many of the APIs, authentication methods, and data storage formats. The (small) parts of that section that I wrote myself are based on things I learned while exploring new areas of the codebase. If someone wanted to take on a significant project in Amanda, I think it would make sense to leverage the exploration that would take place to generate some additional developer documentation. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Virtual tape to Real tape cycles
On Fri, Jun 15, 2007 at 04:23:57PM -0400, Charlie Reitsma wrote: > As I read through the man pages I am finding hints that it has been thought > of. In the amdd man page "This may be used for debugging or to convert from > one format to another." > > I began looking at the contents of various directories and files based on > comments found in Gene's Amanda Helper scripts. The index is just a list of > files contained in the images > contained on the the tape. It wouldn't change at all as the images aren't > being modified. I couldn't find anything that maps an image file to a > particular location on a tape. It > appears that the contents of a virtual tape need no further processing before > moving them to a real tape. Copying those images onto a tape and moving the > index, curinfo and > tapelist date to another cycle seems like it might be straightforward. Since > all the image sizes are known in advance they might even be reordered more > optimally to fit on tape. I > didn't like Gene's suggestion that the virtual tape size and the real tape > size should be kept the same. We might even choose to put different file > systems on different tapes as > they may go to different offsite locations for security reasons. > > Restores appear to collect the images associated with a particular file > system and give them back to the appropriate program to extract the file(s) > requested. That process wouldn't > change just because the media changed. > > I'll take a look at the Developer Documentation to continue my exploration. Charlie -- This sounds like a great project, and I'm excited you're working on it. Please feel free to consult amanda-hackers with any further technical questions or musings you might have. The functionality you're thinking about is a form of hierarchical storage management, with data migrating between storage media based on enterprise policies and needs. It's a kind of functionality that would be welcome in Amanda, and that has been in the back of most developers' minds for some time. The new Device API will be an important step in this direction, since (among other benefits) it will allow us to treat all storage media the same way. With a little reworking, taper can then become a generic data migration tool. The major unresolved issues are: - policy (how does Amanda know when to migrate what, and where) - metadata updates (which you mentioned above) Device API: http://wiki.zmanda.com/index.php/Device_API Once the Device API is released, the immediate next step is to treat holding disk as a device. This represents Amanda's existing functionality -- dumping to holding, then spooling to tape -- as a data migration, opening the door to more complex migrations down the road. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Backup all drives on server
On Thu, Jun 21, 2007 at 12:07:58PM +0100, Weber, Philip wrote: >Is it possible to set up some kind of a wildcard disk list entry, so >all filesystems on a client get backed up, without explicitly >specifying them. i.e. equivalent to NetBackup's "ALL_LOCAL_DRIVES" >directive? I don't like the idea of having to run the risk of missing >newly-added filesystems. There's no such option. One possible solution, though, is to automatically generate your disklist based on manipulating the output of 'df' or 'mount' or the like. You could even use such manipulations to *check for* newly-added filesystems, and send an email (rather than adding them directly). Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: debug files for restore
On Thu, Jun 21, 2007 at 03:18:27PM +0530, kamalesh krishna murthy wrote: >Hi all, > >I have taken backup using amanda, after that i have restored the same >but .debug file for restore is not created in /tmp/amanda directory. > >can any one please help me to solve this problem You should see debug files for amrestore on the machine where you ran it -- the client. The server will produce several other debug files as it provides data to the client. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: suggestion for a disk-to-disk backup server
On Tue, Jun 26, 2007 at 09:29:52AM +0200, Paul Bijnens wrote: > I'm not 100% certain, but I believe you may even erase (some of) the > holdingdisk files, without flushing. I think that Amanda will take into > account that the holdingdisk file disappeared, and schedule the same > incremental level again (or a level 0 if due). Because there is no > equivalent to amrmtape for a holdingdisk file, and, there are at least > some things implemented that detect the loss of an holdingdisk file. > Would be nice if someone could confirm this. You're half-right -- Amanda will not try to flush a missing file, but it will not take missing files into account in the planner. Amanda-2.5.2 and later has 'amadmin holding delete' which can delete holding files and adjust the 'curinfo' database accordingly, such that the appropriate level of dump will take place next time. Also, note that 'amdump' takes a [ hostname [ diskname ..] ] argument, if you only want to dump certain DLEs. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Problems after splitting up a DLE
On Thu, Jun 28, 2007 at 10:09:34PM +0300, Toomas Aas wrote: > To remedy this situation, I removed the amanda-client and amanda-server ports > once again, in order to reinstall them with correct gnutar-listdir. And when > removing the port, I > again got the same error message about the same file: > > pkg_delete: '/usr/local/lib/libamandad.a' fails original MD5 checksum - not > deleted. > > Having exactly the same library to go corrupt during two compilations of > Amanda seems too much to be just a coincidence. The box generally seems > healthy, there are no random signal > 11-s or other common indications of faulty hardware. This is really a mystery. That is very strange. libamandad.a is a static library, and as such isn't used by Amanda in any way, since all of the binaries either link against a shared library or already contain the relevant code from libamanda.a. That makes it all the more unlikely that Amanda itself is somehow modifying that library. This is probably something you should take up with the FreeBSD folks. You can feel free to direct them to this list, or me personally, if they have any questions. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Encryption questions
On Tue, Jul 03, 2007 at 09:22:16AM -0400, Mangala Gunadasa wrote: >Greetings, When posting on a new topic, please do not reply to existing posts (referred to a "hijacking a thread"). Please create a new post with a different subject. >We have been using Amanda for 7 years to backup 15 servers(AIX and >SUN). It works perfectly. We asked to do backup encryption of one of >the File Systems. Do we need to install a new package?. We use gpg >encryption for other purpose. Ho to integrate it to Amanda?. >Any help/suggestions will be greatly appreciated. Amanda 2.5.0 supports encryption, potentially using GPG. Please see http://wiki.zmanda.com for information on how to install and configure it. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: suggestion for a disk-to-disk backup server
Folks -- I looked into this '-o' question, and have some answers for you. On Mon, Jul 02, 2007 at 03:44:55PM -0400, Chris Hoogendyk wrote: > Jon LaBadie wrote: > > On Mon, Jul 02, 2007 at 01:48:59PM -0400, Chris Hoogendyk wrote: > >> I checked the documentation & man pages and the documentation of the -o > >> option is pretty sparse. All references say "see the configuration > >> override section in amanda(8)". That section is only a few lines long > >> and makes no reference to the syntax with a comma separating multiple > >> parameter=value pairs. > >> > >> So, possibilities ... > >> > >> 1. The syntax is wrong? And I need to use "amdump daily -o reserve=100 > >> -o tapedev=/dev/rmt/0n"? (In either case, this should be documented, > >> since one would typically want to override more than one parameter if > >> any at all.) The documentation could use some help there, for sure. FWIW, it doesn't seem that comma-separated options are supported, from my look at the source. The basic problem is that, since you're using a changer, tapedev is actually supplied by the *changer*, which looks directly in amanda.conf. There's no provision to hand configuration overrides (-o) to changers. Furthermore, many changers (e.g., chg-multi) supply their own tapedev. The best solution, in this case, is to completely disable the changer, too: amdump -o tapedev=/no/such/dev -o tpchanger= I hope that helps. I'll work on the documentation. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: suggestion for a disk-to-disk backup server
On Thu, Jul 05, 2007 at 10:35:21AM -0400, Chris Hoogendyk wrote: > The one thing that is annoying is that on /var/mail an incremental is > essentially the same as a full. Those mail files (one per account) are > just like a database file -- add or remove one message and you have to > back up the whole file. It would be interesting to write a wrapper to do > incremental mail dumps sort of like the sql database programs that do > incremental dumps. I wonder if there would be any demand for such a > thing. It could get a little messy, and would probably require the > Application API. In our case, we have about 1200 accounts/files. It > would require reading headers and doing proper locking so as not to > collide with the mail programs. Yes, I think there would be demand for that (there are a lot of application-specific things that could use better backups). And yes, it will be a lot easier after the Application API is in place :) > I'm guessing that for those changers where it's all tied up in one scsi > address, and/or where there are multiple drives in a library, it might > be desirable to have changer handle it. Then my case becomes the special > case -- the changer is set up in sgen.conf and has a scsi device > address, and the tape drive is set up in st.conf and is /dev/rmt/1 -- so > the changer does not know how the drive got set up. This special case > might require the changer to look somewhere else, e.g. amanda.conf, to > find out. But, then, couldn't it also tell somehow if there had been an > override? Or does that get too messy? That's basically the answer -- the current changer interface has no provision for passing along overrides, and adding one would potentially break a lot of custom changer scripts. You've hit the nail on the head as to why changers provide devices to Amanda, rather than leaving her to use tapedev. > Ok, maybe we just need to document that when someone overrides tapedev > they should also override tpchanger if they have one. See the attached patch. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/ Index: man/xml-source/amanda.8.xml === --- man/xml-source/amanda.8.xml (revision 423) +++ man/xml-source/amanda.8.xml (working copy) @@ -1221,15 +1221,36 @@ CONFIGURATION OVERRIDE -Most command allow to overwrite any configuration parameter on -the command line with the -o option. --o NAME=value -eg. -o runtapes=2 -eg. -o DUMPTYPE:no-compress:compress="server fast" -eg. -o TAPETYPE:HP-DAT:length=2000m -eg. -o INTERFACE:local:use="2000 kbps" +Most commands allow the override of specific +configuration options on the command line, using the -o option. This option has the form -oname=value. +An optional space is allowed after the -o. +Each configuration option should be specified in a separate +command-line option. +For global options, name is simply the name of the option, e.g., + +amdump -oruntapes=2 + +For options in a named section of the configuration, name has the +form SECTION:section_name:name, where SECTION is one of TAPETYPE, DUMPTYPE, HOLDINGDISK, or INTERFACE, and section_name is the name of the tapetype, dumptype, holdingdisk, or interface. Examples: + +amdump -o TAPETYPE:HP-DAT:length=2000m +amdump -o DUMPTYPE:no-compress:compress="server fast" +amdump -o HOLDINGDISK:hd1:use="-100 mb" +amdump -o INTERFACE:local:use="2000 kbps" + + +Note that configuration overrides are not effective for tape +changers, which supply a tapedev based on their own configuration. In order to +override tapedev, you must also disable any changer: + +amdump -otapedev=/dev/nst1 -otpchanger='' + + + AUTHOR
Status Summary for June 2007
This is the second month in which we've prepared status updates. We'd love your feedback! As always, a fully linked version of this text is available at http://wiki.zmanda.com/index.php/Monthly_Status_Updates/June_2007 June saw the release of Amanda 2.5.2p1 on June 6, a patch release which was thoroughly tested with the help of the Platform Experts and many users from the mailing lists and forums. This patch release has proven quite stable, and development has shifted to feature development for the next release. Wiki Changes * Marc Muehlfeld provided a link to a useful script for performing backups of MySQL databases. * Harald Schioeberg provided Lto-barcode, a perl script to generate barcode labels for LTO Tapes. Chris Hoogendyk suggested barcodewriter, a PostScript-based barcode utility, as a more general solution. * Erik W wrote a detailed How To:Install Amanda Server on AIX. * Harald Schioeberg provided Chg-multiplex, a wrapper to use multiple Amanda configs in a single restore operation. * Paul Bijnens contributed a multitude of minor edits all over the wiki, increasing readability and clarity. * Dustin J. Mitchell refactored Stefan G. Weichinger's file driver into How To:Set Up Virtual Tapes, FAQ:Should I use a holdingdisk when the final destination of the backup is a virtual tape?, How To:Migrate Virtual Tapes to Real Tapes, and How To:Restore from Virtual Tapes. Forums Discussions Many users had questions about configuring Amanda to their needs. Most questions were about communication problems, and were quickly addressed. Among the more unusual questions were the following. * tamiral asked several interesting questions: * How can I verify that AMANDA has successfully backed-up files? -- Shailen Patel suggested using amrecover to test a full restore, which is more thorough than the tape verification performed by amverify. * I'm concerned that because my defined tape size is larger than the amount of diskspace I have... -- Shailen Patel and Dustin J. Mitchell responded that yes, this could cause a problem, and referencing wiki pages describing the optimal configuration. * Basically, I'd rather use 'dd' for those kind of jobs (even unmount the filesystem so it won't change), but I guess I can't with AMANDA. What is the recommended dumptype for this kind of backup...? -- Paddy Sreenivasan suggested a dumptype with always-full, compression off, and encryption off. * George Reeke had a client machine which exceeded Amanda's connect timeout because its hard drives took too long to spin up. Paddy Sreenivasan suggested increasing ctimeout and etimeout. * mickeyn has clients with dynamically-assigned addresses. Marc Muehlfeld suggested using static IP assignments in the DHCP server as a way to stabilize the clients' addresses. Mailing List Discussions * Charlie Reitsma asked if any work had been done on migrating dumps from vtapes to real tapes. Dustin Mitchell, Gene Heskett, and Jon LaBadie replied with some pointers, and Charlie started work on an implementation to suit his needs. * Philip Weber sparked an interesting conversation about Amanda automatically detecting disks that are not in Amanda's disklist and thus are not being backed up. While the problem is difficult to solve in the general case, a few specific solutions were suggested as wrappers around Amanda. * Jon LaBadie tried running amtapetype on a vtape, and the results touched off an interesting discussion on what amtapetype should do in such a situation. * Marc Muehlfeld wondered how Amanda can fill a tape to more than 100% capacity. Cyrille Bollu and Paul Bijnens answered, pointing out that tapes differ in actual capacity, and that Amanda only uses the tapelength for planning purposes, but will happily consume any extra space it finds. * Robert P. McGraw, Chris Hoogendyk, and Brian Cuttler discussed the relative merits of hardware and software compression, noting that Amanda has a difficult time calculating the number of dumps it can fit on a tape when hardware compression is enabled. * Rudy Setiawan asked for advice setting up a large disk-to-disk configuration, and prompted a lengthy discussion about calculating space requirements of a configuration, optimizing a system for fast disk-to-disk backups, and ensuring sufficient redundancy for backup data in such a configuration. Chris Hoogendyk hijacked the thread to consider ways of running incremental backups only over a weekend. * Sebastian Marten asked about the relationship of runtapes to tape_splitsize. Marc Muehlfeld replied to say that splitting dumps across tapes is impossible with only one tape (runtapes=1). Sebastian does not have a changer, but nightly backups are larger than his media (DVD-RAM), so Marc suggested using multiple DVD drives, spooling some dumps to holding and
Re: amanda server on Mac OS X ?
On Wed, Jul 18, 2007 at 12:27:48AM +0200, Stefan G. Weichinger wrote:
> Any experience with amanda-server on OS X?
> Any infos regarding this newer than the mentioned link above?
http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X
I use Macs at home, so I did some work on this a while back. Everything
that I understand is summarized on that page.
To answer your specific question, you can run an Amanda server on a Mac,
with the caveat that Mac OS X itself doesn't support any tape drives.
Clients work great.
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: amanda server on Mac OS X ?
On Tue, Jul 17, 2007 at 10:42:40PM -0400, Chris Hoogendyk wrote: > When you say Mac OS X doesn't support tape drives, do you mean that the > specific type of implementation expected by amanda is not supported? I'm kind > of blindly waving my arms in > the air, but it just doesn't seem quite right as a blanket statement and > leads me to question further. Could you humor me and explain in more detail? > And what does that mean for > BSDs in general? Well, I base that opinion on findings around the web such as this: http://lists.apple.com/archives/darwin-dev/2005/Jun/msg00081.html http://lists.apple.com/archives/darwin-drivers/2003/Apr/msg00068.html And the fact that my Mac systems don't, in fact, have 'mt' or 'mtx'. I recall reading a much more authoritative source, but of course Google is not finding it for me now. In detail, the story is that there are no device drivers (and thus no /dev/ entries) or tape-related utilities (mt, etc.) on a Mac. Macs do have SCSI subsystems, and it's possible to attach most SCSI tape drives to a Mac. As you mention, Retrospect includes built-in drivers for various tape drives. It would probably be possible to write a Mac driver for a specific tape drive or even family of drives (and the messages linked above suggest folks have done so), but Amanda has been getting *away* from device-specific support for a long time, and I think that's served the project as a whole well. The Device API will, of course, make this kind of project a lot easier. My apologies for my own hand-waviness at throwing that information out there in my original email with no supporting evidence! As for BSDs in general -- Apple has basically *removed* support that's available in the base BSD systems, so no worries. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Last Day To Vote! - SourceForge "Community Choice Award"
Just a reminder that this is the last day for voting in the Community
Choice Award.
If you haven't already, please cast your vote at
http://sourceforge.net/awards/cca/vote.php
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: Multiple Tape Devices ?
On Wed, Jul 25, 2007 at 07:15:55PM +0200, Ralf Auer wrote: > I do not want to split my backup in two different configurations, so > maybe you know a way how to use both tapes simultaneously in one > configuration? I am pretty sure, it can be done, because otherways the > 'runtapes' option in amanda.conf would not make much sense, I think... Everything except "simultaneously" -- at present, a single Amanda config can only drive one tape drive at a time. Since your tape drives are the same size, chg-multi is an option. With different-sized tapedrives, even that doesn't work (since you can only specify a single tapetype). These are all limits we'd like to remove, but they're all also very difficult to remove. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Multiple Tape Devices ?
On Wed, Jul 25, 2007 at 08:11:21PM +0200, Stefan G. Weichinger wrote: > Ralf Auer schrieb: > > Hi everybody, > > > > I'm trying to use two physical tape drives (HP Ultrium 960) with > > Amanda. According to the manual, I could use a tape changer (e.g. > > chg-multi) to get the job done, but that would write only to one disk at > > a time, right? > > > > I do not want to split my backup in two different configurations, so > > maybe you know a way how to use both tapes simultaneously in one > > configuration? I am pretty sure, it can be done, because otherways the > > 'runtapes' option in amanda.conf would not make much sense, I think... > > > > Unfortunately I did not find anything helpful about that issue in the > > manual or the mailing list. > > > > At the moment I am using Amanda 2.4.5 on Ubuntu 5.10 & FC3 but I would > > not mind to upgrade if a newer Amanda version is needed for this feature. > > RAIT: > > http://www.amanda.org/docs/rait.html > http://wiki.zmanda.com/index.php/How_To:Set_Up_RAIT_(Redundant_Array_of_Independent_Tapes) I should have mentioned RAIT, but note that with two tape drives RAIT will only do mirroring, not striping. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amtypetype taking 51 hours??
On Sat, Jul 28, 2007 at 07:18:32PM -0500, Steven Osborn wrote: >I have a Dell Powervault 124T LTO-2 and I'm running amtapetype on it >and it is running incredibly slow. It estimates 51 hours to check the >tape. I'm new to amanda, but this seems absurdly slow to me. I don't know the details of your tape device, but keep in mind that amtapetype does things that are not usual for a tape device, and that for enormous tapes, it can, indeed, take a while. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Question to: Friday tape question - Top 10
On Wed, Aug 01, 2007 at 08:55:59PM +0200, Ralf Auer wrote: > > Not sure I know what part you feel is not true. You hypothesised > > a situation where normally every day's dump fit on one tape. Then > > on one particular day a single DLE grew enough to cause the day's > > run to require 3 tapes. That would only happen if that one DLE > > were now larger than a single tape (even for an incremental as the > > scenario is constructed). With runtapes == 1, amanda would not > > even start the dump of that DLE. > > Maybe I am completely wrong, but I thought, if the big dump is > distributed over several partitions, each one with a single entry in the > disklist and each partition size smaller than the tape capacity, the > backup should work. > For instance, my type capacity is 400GB, the specific client has three > partitions of 350GB each and each partition has its own entry in the > disklist. So I assumed, that one partition backup would go to the first > tape, anther one to the second and the third one onto the last tape. > Since 'tape spawning' is not necessary in this case, I thought that the > backup would be run by Amanda. But, as I said, I am not sure about that > and probably you're right... If I can try to summarize, you're discussing situations where Amanda is fairly massively oversubscribed; that is, Amanda has very little room to deal with unexpected circumstances, including an overlarge incremental, an unavailable client, etc. In the specific situation, under "normal circumstances", you expect Amanda to balance dumps into about 1 tape per run. You've set runtapes to a larger number, to allow Amanda to use more tapes if necessary, but you don't really have enough tape to support your full retention period with >1 run per tape. The "correct" calculation is: tapecycle = reundancy_factor * runtapes * runspercycle + epsilon where epsilon is 1 or 2 -- "spare" tapes to allow slack for damaged tapes, etc. The redundancy_factor is the number of full backups you'd like to have around at any time -- 1 is OK, 2 or more is recommended. Anything less than 1 is asking for trouble. In your case, if I remember the numbers correctly, you had: tapecycle 5 runspercycle 5 runtapes 3 epsilon 0 solving for redundancy_factor gives 5 = redundancy_factor * 3 * 5 + 0 redundancy_factor = 0.33 which is clearly suboptimal. This is not to say that this kind of configuration won't work -- Amanda will do her level best -- but it should not be a surprise that "level best" is not always good enough, especially when unexpected things happen. I think the bottom line is: this is your Wednesday email telling you to buy more tapes ;) Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: bugs: amanda server's ip have to add in client host file?
On Thu, Aug 02, 2007 at 02:59:56AM -0700, fedora wrote: > I found that for every clients I have, I need to map amanda server's ip in > /etc/hosts file. Otherwise it will return the error like this: > WARNING: mydomain.com: selfcheck request failed: timeout waiting for ACK Does reverse DNS work, too, for all machines? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Client backup fails with Timeout error
On Thu, Aug 02, 2007 at 09:48:20AM -0400, Vytas Janusauskas wrote: > Up to about a week ago all my clients (Linux) have been archiving properly. > For the past 5 runs of Amanda one client is not backing up. Below are the > error message I am getting. > Searching the list archives did not point me to anything that may be related > to my environment. Amanda server and clients are running Debian packages. > On the server I am running > Amanda-2.5.1p3 and on all clients Amanda-2.5.1p1. I have re-booted the > server and the client between runs with no success. As far as I can tell no > changes were made to the > troublesome client which may account for the failures. All computer are > inside the firewall. Any ideas of what may be going wrong? > Amstatus Message > hal2:/mnt/hdb1/Can_Fin_photos 1 driver: (aborted:"[request failed: timeout > waiting for REP]")(too many dumper retry) > > Amanda Report > hal2/mnt/hdb1/Can_Fin_photos lev 1 FAILED [cannot read header: got 0 > instead of 32768] Could you post the debug logs? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: index tee cannot write [Broken pipe]
On Thu, Aug 02, 2007 at 09:56:12AM -0400, Mike Gallant wrote: > I have an amanda (2.5.1p3) server (solaris10) with seven amanda clients > (2.4.4) and a new amanda (2.5.2) client on new hardware. I have been getting > a "index tee cannot write > [Broken pipe]" error message. I have looked at all the various aspects I can > think of but still no joy. Could someone point me in the right direction for > resolving this. > > I have included the sendbackup.debug (client) and a good part of the amandad > (client) missing the repetitive entries. > amandad: time 1800.842: stream_server: bind(in6addr_any) failed: Invalid > argument > amandad: time 1800.842: security_seterror(handle=30d90, driver=ff2dd95c (BSD) > error=can't create server stream: Invalid argument) This looks like an IPv6 networking problem. Several such problems were fixed in the 2.5.1 -> 2.5.2 upgrade. Perhaps you could try upgrading? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Client backup fails with Timeout error
On Fri, Aug 03, 2007 at 01:18:52PM -0400, Vytas Janusauskas wrote: > Dustin J. Mitchell wrote: > >Could you post the debug logs? > > Hi Dustin, > Attached are the log files. If there is anything else required please let me > know. Just FYI, those are the Amanda log files, not the debug logs. Anyway, around like 230005, I see: driver: result time 9260.882 from dumper0: FAILED 00-00218 "[data timeout]" I'm not sure what in your configuration would cause this, but you have a fairly large list of DLEs, even on that machine. It looks like your dumpers are constrained by bandwidth, which is good. Is 'hal2' a busy machine that may take a long time to begin a dump? You may want to increase 'dtimeout' to some much larger value; its default is a half-hour. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda 2.5.1.p1 & ssh-auth
On Sat, Aug 04, 2007 at 02:59:12PM +0200, Ralf Auer wrote: > I am just upgrading my Amanda from 2.4.5 to 2.5.1p1 (2.5.2p1 does not > compile at all). I am very happy about the new 'ssh-auth' feature in > 2.5. It works now in my test setup (only 2 DLEs). Do you mind expounding on the compilation problems with 2.5.2p1? What OS/architecture? What error(s) did you see? Thanks! Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda 2.5.1.p1 & ssh-auth
On Sat, Aug 04, 2007 at 09:30:55PM +0200, Ralf Auer wrote: > I am running Ubuntu 7.04 on i386 on the server host. Tried gcc-4.1 and > gcc-3.3. Downloaded 2.5.2p1 from Amanda website. > > This is how I configured 2.5.2p1 sources: > > ./configure > --prefix=/opt/amanda > --with-user=amanda --with-group=backup > --with-gnutar=/bin/tar --with-smbclient=/usr/bin/smbclient > --with-gnutar-listdir=/var/amanda/gnutar-lists > --with-tcpportrange=5,50100 --with-udpportrange=840,860 > --with-buffered-dump --with-debugging=/var/amanda/debug > --with-debug-days=10 --with-gnuplot=/usr/bin/gnuplot > --with-configdir=/opt/amanda/etc --with-ssh-security > > > When I go to make, this is what I get: > > gcc -Wall -Wextra -Wparentheses -Wdeclaration-after-statement > -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat > -Wsign-compare -Wfloat-equal -Wold-style-definition -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -o .libs/amoldrecover amrecover.o > display_commands.o extract_list.o help.o set_commands.o uparse.o uscan.o > -lfl ../client-src/.libs/libamclient.so > ../common-src/.libs/libamanda.so ../gnulib/.libs/libgnu.a -lm -ltermcap > -lnsl -lresolv -Wl,--rpath -Wl,/opt/amanda/lib > amrecover.o: In function `main': > amrecover.c:(.text+0x1cb1): undefined reference to `process_line' > uparse.o: In function `yyparse': > uparse.c:(.text+0x1ef): undefined reference to `yylex' > uparse.c:(.text+0x51a): undefined reference to `yytext' > uparse.c:(.text+0xcf8): undefined reference to `yylex' > collect2: ld returned 1 exit status > make[1]: *** [amoldrecover] Error 1 > make[1]: Leaving directory `/root/amanda-2.5.2p1/oldrecover-src' > make: *** [all-recursive] Error 1 uparse.c, which contains the missing process_line amrecover.c is referencing, is generated by 'flex' from uparse.y in that directory. I've only seen this error when uparse.c was generated on a *different* system, and thus things didn't line up between uparse.c and the rest of the object files. Could you try apt-getting the sources afresh, and checking whether uparse.c already exists? If it does, try deleting it first (and do the same in recover-src/) and then building again. If this works, then the problem is an ubuntu bug (the source distro contains files it shouldn't). If not, if you could tar up the build directory after the error occurs and place it somewhere I can download it, and give me the url in private email, I'll see if I can figure out what's going on. Thanks for the bug report -- ideally Amanda should build on just about anything that smells vaugely like UNIX. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda 2.5.1.p1 & ssh-auth
On Sun, Aug 05, 2007 at 10:56:31PM +0200, Ralf Auer wrote: > it's working now! Still kinda strange for me. What I did was the > following: > I purged the 'flex', 'bison' and 'libreadline5-dev' Ubuntu packages from > my office machine. (Those packages are not installed on my laptop, where > the sources cleanly compiled yesterday). > After this purging I re-downloaded the 2.5.2p1 tarball from the Amanda > download page, and voila! Everything is compiling now. So it looks like > probably the Ubuntu 'flex' package caused the trouble. Don't know, why, > but now I have a pretty nice up-to-date Amanda installation running on > my machines. *happy* Great! I'm not sure if the bug was in Amanda or Ubuntu, but I'm glad things are working for you now. Perhaps, as the testing process gets started in the community version (no, folks, I haven't forgotten!), you can help us out with Ubuntu testing. > By the way, maybe you could also answer this question: I need a > completely statically linked Amanda for some hosts. Is it enough to > append '--enable-dynamic=no --enable-static=yes' to configure, or do I > also have to set something like CXXFLAGS=CFLAGS=LDFLAGS=...FLAGS=-static ? I don't know the answer to that, except to say that Amanda pretty much lets automake and libtool worry about linking, so it "should" work. It'd be nice to hear a positive or negative result from trying it. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Status Update for July 2007
The July Monthly Status Update is available on the wiki at http://wiki.zmanda.com/index.php/Monthly_Status_Updates/July_2007 As always, feedback and comments are welcome and encouraged. July has been a quiet month for Amanda development, with development mostly focused on bug fixes. Developers are working hard on significant changes, including the Device API and Application API, although neither is quite ready for release yet. We are also beginning work on a new data-transfer architecture which will enable lots of exciting new functionality. Wiki Changes * Paddy added the page, "FAQ:How do I force Amanda to do a full backup?" to address a common question seen in the forums and on the mailing list. * Gavin added a link for the DLE term to "Amanda#DISKLIST_FILE", including a very brief description. * Squadra added a new story to Amanda user surveys and success stories, replete with a detailed performance analysis. * Cameron Matheson added instructions for running Amanda over SSH with a non-standard port. Forums and Mailing Lists The Amanda team provided support for users via the Zmanda forums and mailing lists, as did a number of helpful newcomers, including Andrew Rakowski. Thanks to all who helped out! Code Changes Among numerous small fixes and tweaks: * Stefan G. Weichinger noticed that 'amadmin Conf balance' output was misaligned; Dustin J. Mitchell committed a fix (r425) * Jean-Louis Martineau improved restore's performance by removing an unecessary fast-forward operation (r427) * Chris Hoogendyk and Olivier Nicole suggested better documentation for the -o configuration-override option (r429) * Paul Bijnens and Dimitri Gorokhovik submitted patches for bugs in chg-multi.sh (r431 and r442) * Dustin J. Mitchell fixed problems finding 'mt' and 'mtx' in chg-zd-mtx.sh (r438) * Dustin J. Mitchell modified all Amanda shell scripts to function correctly if internationalization support is not available (r444) * Terry Burton submitted an updated DLT tape label template (r452). Jean-Louis Martineau is working behind the scenes on the Application API, and Ian Turner is putting the finishing touches on the Device API. Hopefully, next month's status update will highlight the release of the Device API! -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Changed network address on server, and clients not working
On Mon, Aug 06, 2007 at 04:52:46PM -0400, stan wrote: > In an attempt to work around some network problems, I've added a 2nd NIC to > my Amanda server, that should provide a better route to some of the > clients. On those clients amcheck is not working. > > I added the IP address of the 2nd NIC to the .amandahosts file on the > clients, but that does not seem to be working. I don't have a DNS entry for > this address, and I'm wondering if that could be the problem. This sounds about right. BSD-flavored security is dependent on the identity of the remote *host* (rather than some cryptographic representation of a user identity). One of the requirements is that both forward and reverse DNS work for that IP <-> name. We've also had some unsubstantiated reports of problems with dual-homed Amanda servers, so if you run into further trouble after setting up forward/reverse DNS, please speak up. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: ssh tunneling from wherever
On Mon, Aug 06, 2007 at 11:29:40PM -0400, Steve Newcomb wrote: > Any clues to offer? I've never tried this, but I think you should take a look at the SSH documentation for port forwarding. Run on the client, ssh -l 10080:: 'sleep 7000' & means that connections to port on should be forwarded to port 10080 on the client. Making =10080 means that port 10080 is forwarded, but of course with auth-ssh Amanda doesn't listen at all. If you want to use auth-ssh inside this SSH tunnel (which seems redundant), you'll need to convince SSH to connect to the client on port , hostname 'localhost'. It would probably be more sensible to switch to bsdtcp authentication for this client, and select some otherwise-unused port on the server. Then just point your DLE to localhost: with auth "bsdtcp", and you should be OK. All in all, it sounds like a lot of work, unless this is a months-long conference :) Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Amanda client on SCO Openserver
On Tue, Aug 07, 2007 at 02:23:01PM -0500, Kenneth Berry wrote: > 1. Is SCO Openserver 5.0.7 a supported OS? I can find very little > discussion on the Internet. If you didn't get a warning beginning with * This machine, target type , is not known to be fully supported by this configure script. If the ... when you configured, then someone, somewhere, has once compiled Amanda on SCO Openserver. > 2. If it is not supported will it work anyway? Probably, but it may take some tweaking.. > 3. Any advice on configuration options? I've not touched a SCO machine, so I can't help you there. > My configuration...make fails with > > Making all in gnulib > make[1]: Entering directory `/u/tmp/amanda-2.5.2p1-20070606/gnulib' > make all-am > make[2]: Entering directory `/u/tmp/amanda-2.5.2p1-20070606/gnulib' > /bin/bash ../libtool --tag=CC --mode=link gcc -Wall -W -Wparentheses > -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat > -Wsign-compare -Wno-error -D_GNU_SOURCE-o libgnu.la lock.lo > asnprintf.lo printf-args.lo printf-parse.lo vasnprintf.lo -lm -lreadline > -ltermcap -lsocket -lnsl -lresolv -lintl -lsocket > false > cru .libs/libgnu.a .libs/lock.o .libs/asnprintf.o .libs/printf-args.o > .libs/printf-parse.o .libs/vasnprintf.o > make[2]: *** [libgnu.la] Error 1 > make[2]: Leaving directory `/u/tmp/amanda-2.5.2p1-20070606/gnulib' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/u/tmp/amanda-2.5.2p1-20070606/gnulib' > make: *** [all-recursive] Error 1 I'm not even sure how to interpret that. However, the Makefile in that directory (gnulib) is actually not written by us -- gnulib is a set of low-level utilities provided to make cross-platform compatibility easier, and pretty much comes with everything, including a Makefile. Unless a SCO user speaks up here (come out, come out, lurkers!), I think your best bet is to look for general advice on compiling from source, particularly relating to gnulib. Sorry I can't be more help.. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: a client disappeared
On Tue, Aug 07, 2007 at 04:39:24PM -0600, Glenn English wrote:
> One of the two clients on the DMZ has stopped responding to the server
> on the LAN -- both amcheck and amdump.
A few things to check:
- forward or reverse DNS doesn't work for the server or the client.
- firewall on the client changed
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: 2 tape drives?
On Wed, Aug 08, 2007 at 10:11:12AM +0200, Cyrille Bollu wrote: >Hi, >I just would like to know if Amanda is able to write 2 tapes at the >same time to improve tape dumping speed. >(For those who remember, I'm planing to buy a Dell TL2000 which can be >configured with 2 SAS tape drives) This actually just came up: http://marc.info/?t=118573739400001&r=1&w=2 Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: tar dumps, performance
On Wed, Aug 08, 2007 at 09:09:50AM -0400, Brian Cuttler wrote:
> What really happens when GTAR INDEXING is enabled ?
Briefly, the client 'tees' the tar output to another invocation of tar
with the -t (table of contents) option, which lists each file in the
dump, one per line. That information is sent to the server in a stream
parallel to the data stream, where the dumper writes it to the gnu-tar
index files directory, possibly compressing it first.
I hope that helps!
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
Re: 2 tape drives?
On Wed, Aug 08, 2007 at 04:08:19PM +0200, Cyrille Bollu wrote: >Sorry, I don't understand; This thread doesn't seem to speak about >writing on 2 tapes at the same time (like RAIT but without the >redundancy). The original question was the same, and the answer was that you can do that with RAIT with the third (parity) drive set to /dev/null, although that has certain disadvantages, too. This capability is something we'd like to add in a more permanent sense (so e.g., full dumps get written to each tape, instead of blockwise striping), but it's a fairly fundamental change and will not be here too soon. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: 2 tape drives?
On Wed, Aug 08, 2007 at 11:11:47AM -0400, Jean-Francois Malouin wrote: > > The original question was the same, and the answer was that you can do > > that with RAIT with the third (parity) drive set to /dev/null, although > > that has certain disadvantages, too. > > Don't want to hijack the thread but... > I've been considering implementing that on my local setup. > Can you give more details on what are the drawbacks? The data is striped over two tapes, so if either tape fails, you lose all of your data. Furthermore, the files on tape aren't just dumpfiles-with-headers anymore -- you have to use a similarly configured Amanda to recover your data. In particular, if one of your tape drives dies, you won't be able to[1] reassemble any of the dumps on striped tapes. All in all, none of these are showstoppers, but they're worth considering. Dustin [1] not easily, anyway. -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: how to notify syslog the backup execution result by amanda
The next release or two will have better support for this, but at the moment, the easiest way to do this is to add a wrapper around 'amdump' that uses 'logger' (a BSD utility that's also present on most Linuxes) to send a log line to syslog. Dustin On Thu, Aug 09, 2007 at 07:43:45PM +0900, Takashi Kurakata wrote: >Hello all, >I want to notify syslog(ex. /var/log/messages) the backup execution >result by amanda. >Has this been done?$B!!(BPlease teach how to have achieved it in case >of being. >Thanks in advance. >Takashi Kurakata -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amandates ?!
On Fri, Aug 10, 2007 at 12:06:36AM +0200, Ralf Auer wrote: > is there a way to tell Amanda-2.5.2p1 where to look for the 'amandates' > files instead of in '/etc/amandates'? I want to put it to > '/var/amanda/amandates' without creating links. Any suggestions? The 'amandates' option in amanda-client.conf should do the trick. http://wiki.zmanda.com/index.php/Amanda-client.conf You can change the default with a one-line patch to common-src/conffile.c, if you'd rather. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: tar dumps, performance
On Mon, Aug 13, 2007 at 04:25:47PM -0700, Aaron J. Grier wrote: > I was under the impression that everything (including the index) was > written to holding disk and moved into the indexdir _after_ the backup > dumped to tape. Nope -- dumper.c writes data from the indexfd directly to the index directory on the server, potentially via a compression pipe. The other info about the index process was accurate. sendbackup.c runs tar and, for every buffer of data it gets back, sends the data both to the server (on the datafd) and to a running shell invocation of tar -tf - | sed -e 's/^\\.//' the output of which is also sent to the server (on the indexfd). Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: gtar program still running after backup failed
On Wed, Aug 15, 2007 at 02:53:16AM -0700, fedora wrote: > When Amanda did not completed backup (failed), the gtar program is still > running in client server by checking run ps -ef|grep amanda. It will > increase the client server load. I have to manually kill the processes. > > May I know how to make it kill the failed gtar program automatically once > the Amanda server finished (failed to backup)?? In "normal" failure modes, this should be taken care of. Can you give some detail on the type of failure that's triggering this? Also, amcleanup should function as a second line of defense for killing such processes. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: gtar program still running after backup failed
On Wed, Aug 15, 2007 at 07:57:32PM -0700, fedora wrote: > > In "normal" failure modes, this should be taken care of. Can you give > > some detail on the type of failure that's triggering this? > > > > Also, amcleanup should function as a second line of defense for killing > > such processes. > > Here is the error in mail report: > FAILED [data timeout] > FAILED [cannot read header: got 0 instead of 32768] > FAILED [too many dumper retry: "[request failed: timeout waiting for ACK]"] It looks like you have a communication problem. What auth are you using for that client? This is, unfortunately, not the sort of error that amcheck will pick up on. It's usually caused by bad firewall settings. > Here is my cronjob: > 0 21 * * * /usr/local/sbin/amcleanup DailySet1 > 10 21 * * * /usr/local/sbin/amcheck DailySet1 > 30 21 * * * /usr/local/sbin/amdump DailySet1 > > I put amcleanup before amcheck and amdump. Was it a proper sequences? No -- you shouldn't need to run amcleanup regularly, but only when a failure occurs. Also, running amcheck 20 minutes before your dump doesn't give you much time to fix anything. Most people run amcheck in the late afternoon -- after any tape swapping is done, but with enough time to correct any errors before heading home for dinner. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amverify reports problems
On Tue, Aug 21, 2007 at 10:20:49AM -0400, Paul Lussier wrote: > So, I'm fairly confident that this file system was not properly backed > up. More disturbing to me though, are the 2 or more tapes which > reported "Too many errors". Is this a problem with the tape, the > drive, or amanda? And how do I prove which one it is? I'm leaning > towards the tapes, but haven't ruled out the drive. It sounds like you have the right probabilities assigned. You can rule out Amanda by using tools like 'mt' and 'dd' to manipulate tapes -- both the tapes in question and new tapes which haven't demonstrated these errors before. It's worth noting that amverify is basically a shell script that uses these tools itself. The "0+0 in" lines are from 'dd', and indicate that it couldn't read anything from the tape at that particular point. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
