Re: re-labelling or duplicating a tape?
In a message dated: Mon, 03 Jan 2005 16:49:47 EST Jon LaBadie said: As an alternative, couldn't you change the human aspect of the problem? Sure, and that was my fall back plan in case a techical solution wasn't feasible. But I felt it was at least worth asking about :) Thanks! -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: re-labelling or duplicating a tape?
In a message dated: Tue, 04 Jan 2005 09:17:19 +0100 Gerhard den Hollander said: 2) even easier and cheaper when you store the tape, in the tape box (and on the tape and on the paper insert that comes with the tape) simply write that this set only has one tape. This is what my fall back plan was :) Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
re-labelling or duplicating a tape?
Hi all, Is there an easy way to change the amanda label of a tape that's been written to? Short of that, is there an easy way to recover the contents of the tape in amdump form, then re-label the tape and use amflush to get the contents on the newly/properly labelled tape? Thanks. Oh, and btw, the Faq-O-Matic seems to be offline at sourceforge... -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: re-labelling or duplicating a tape?
In a message dated: Mon, 03 Jan 2005 17:03:47 +0100 Gerhard den Hollander said: * [EMAIL PROTECTED] [EMAIL PROTECTED] (Mon, Jan 03, 2005 at 10:3 6:51AM -0500) Is there an easy way to change the amanda label of a tape that's been written to? Short of that, is there an easy way to recover the contents of the tape in amdump form, then re-label the tape and use amflush to get the contents on the newly/properly labelled tape? yes there is, but why would you want to do that ? Amanda will still think that tape with the old (now overwritten ) label is the one that has the data on it. so if you relabel the tape, amanda doesn;t know anything about it anymore at all .. I mis-labelled a tape. This tape is never really used in a sequence, it's strictly an archival tape that gets put in off-site storage indefinitely. I want to remove the tape entirely from amanda's knowledge. If I could just change the label name, and somehow update amanda's database, that would be fine. I suspect, however, that it's easier to just restore the tape to disk and flush to the next new tape and amrmtape the mislabelled one. But I'm not sure how to restore the tape to chunks that amflush will recognize. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: re-labelling or duplicating a tape?
In a message dated: Mon, 03 Jan 2005 13:14:02 EST Jon LaBadie said: Quick answer is sure, just overwrite the 32KB first file on the tape. Longer answer dependes on what you want to do with the tape and how much you expect amanda to remember about the tape, its contents, and its new label. To overwrite it, do a dd if=tapedevice of=sometmpname bs=32k. Maybe make a copy of sometmpname so if you mess up you can restore it. Next edit the file sometmpname to change the tape name. Then rewind the tape and do the same dd command with 'if' and 'of' reversed. Note, after doing this amanda has an invalid concept of what is on the tape. It still thinks the other tape exists and has valid contents. Depending on what new tape name you choose, the modified tape is either not known by amanda's index (a new tape name) or does not match the index's listing of the contents. Hmm, okay. Ideally I'd like amanda's knowledge of what's on the tape to change with the tape label. This is the problem: I have a configuration called 'archive', the sole purpose of which is be stored off site indefinitely. There a no-reuse policy on these tapes. The tape labels are of the form '-Q[1-4]-Tape-X/Y' This way, I need only know from which quarter I need to restore from should I ever need to pull one of these tapes from storage. Last week I ran this configuration and labelled the tape as 1/2, but we only used 1 tape, not 2. What want to accomplish is changing this tape to be 1/1 instead of 1/2. So, I can either edit the tape header and the amanda database, or dump the tape to disk, then flush it to a new tape, which actually sounds easier. So, how would I extract the contents of a tape so I could flush it to another tape? -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
amrecover failing
Debian/stable (2.4.22 kernel) Amanda-2.4.4p2 tar (GNU tar) 1.13.25 Hi all, I'm trying to use amrecover to restore a users homedir, and keep getting the following error when I answer 'Y' to the 'Load tape now' question: EOF, check amidxtaped.timestamp.debug file on space-monster.permabit.com. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 At first I thought maybe I had a bad tape, but I've tried on several tapes, all with the same results. I just did an 'amtape conf update' and that was able to correctly read the amanda labels off all of the tapes. Any ideas? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: amrecover failing
Thanks for the replies. Everyone who did so suggested that the tape was not rewound. Unfortunately, that's not case. I've made sure to eject the tape, reload the tape, and run mt -f /dev/st0 rewind, and then mt -f /dev/st0 status which shows: $ mt -f /dev/st0 status drive type = Generic SCSI-2 tape drive status = 1107296256 sense key error = 0 residue count = 0 file number = 0 block number = 0 Tape block size 0 bytes. Density code 0x42 (unknown). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Doh! [was Re: amrecover failing ]
grin=sheepish, emarrassment_level=extremely high I forgot to 'settape'. For some reason I thought this was automatically detected from the amanda conf file, but evidently not. /grin I could have sworn I set amanda up to automatically use my changer for this, and upon inspection of the amana.conf file, it appears I started. However, I just found the Faq-O-Matic answer to this question, which appears to imply I set this up incorrectly. I'll have another go at this, thanks a lot, and I apologize for wasting anyone's time. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: enabling hardware compression ?
In a message dated: Mon, 23 Aug 2004 15:12:52 EDT Frederic Medery said: Thanks, in fact what I want is to speed up my backup so i moved my tape charger to the biggest server, now I have a /amanda with 160 GB of free space. I thought that HW compression would also speed up my backup. I find that an illogical assumption. If you have N clients all streaming data to a central host, which then has to stream that data to a tape drive, and the tape drive then has to compress that stream, then the compression becomes the bottleneck. By using hw compression in that manner, you've inserted an additional hoop for the data to jump through before actually getting onto the tape. Therefore, by definition, the whole process will be slowed down some (even if only by a negligible amount). To actually speed up the backup process, it's probably better to perform client side compression, thereby distributing the process such that it is performed in parallel on the X clients you have. This way, when the data, when it arrives at the server, is already in the form it's meant to be on tape; i.e. there's no longer a bottleneck at the tape drive. Just my $.2 :) -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: AMANDA Documentation at www.oops.co.at
In a message dated: Tue, 24 Aug 2004 00:15:31 +0200 Stefan G. Weichinger said: I would prefer to just put the current pdf online, as I want to put the xml-stuff online in early september. I want to avoid the side-effects of distributing stuff per email ... I am very busy with other things these days, but I hope to get back to the AMANDA-docs in september. Just get the file at: http://www.oops.co.at/AMANDA-docs/index.html For some reason I didn't see that huge link staring me in the face yesterday pointing at the PDF :) That's all I wanted, I didn't realize you had already generated the PDF. Thanks! And note: this is still heavily ALPHA-stuff. Notes/corrections/additions welcome. That's what we're all here for, to make it as ready as amanda is :) (Thanks for getting this started) btw, the AMANDA-manpages will be added soon ... And I notice they already have been. Excellent! I'll be reading this on my commute tomorrow morning (It's tough to read on a bicycle, which is how I commuted today :) -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: AMANDA Documentation at www.oops.co.at
In a message dated: Tue, 24 Aug 2004 00:15:31 +0200
Stefan G. Weichinger said:
Just get the file at:
http://www.oops.co.at/AMANDA-docs/index.html
Hmmm, ghostscript seems to have trouble converting this to postscript:
$ pdf2ps amanda.pdf amanda.ps
Unknown operator: '.
Error: /syntaxerror in --token--
Operand stack:
365361 2546 0 4 --dict:9/9(ro)(G)-- --nostringval--
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2
%stopped_push --nostringval-- --nostringval-- --nostringval-- false 1
%stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop
--nostringval-- 94 1 206 --nostringval-- %for_pos_int_continue
--nostringval-- --nostringval-- --nostringval-- %array_continue
--nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push
--nostringval-- %loop_continue --nostringval-- --nostringval-- --nostringval--
Dictionary stack:
--dict:1049/1123(ro)(G)-- --dict:0/20(G)-- --dict:74/200(L)--
--dict:74/200(L)-- --dict:100/127(ro)(G)-- --dict:230/230(ro)(G)--
--dict:20/24(L)-- --dict:4/6(L)-- --dict:22/31(L)--
Current allocation mode is local
GPL Ghostscript 8.01: Unrecoverable error, exit code 1
--
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
If you're not having fun, you're not doing it right!
Re: advice please!
In a message dated: Wed, 11 Aug 2004 13:34:06 BST Maccy said: I'm after some advice, as I haven't had any experience of setting up a backup system before. I apologize for the delay in responding, I was on vacation when you posted this and am now just catching up on my Amanda mail :) I recently acquired a Overland Powerloader with 17 slots and 1 LTO-2 drive. Ahh, nice set up, that's what I have and really like it. Mine has a barcode reader in it too, though I've not spent the time to configure that yet (it's on the todo list when I find some more 'round tuits' :) I want to backup ~3TB of data, and I'd like to do it incrementally throughout the working week and fully Friday thru Sunday. Not overly complicated, just run 2 different configurations. (I'm assuming that the Fri-Sun backups are meant for offsite storage ?) Ideally I'd like 3 cycles on the full dump and 2 cycles of tapes for the incremental. I have a total of 25 LTO-2 tapes at my disposal. How would I go about labelling the tapes? Is there anything else I need to look for? As I said, I would use 2 different configurations, a 'daily' and a 'weekly' configuration. (this is exactly what I do, incidently). Set up 'daily' such that it runs Mon-Thu nights, and 'weekly' Fri-Sun. The big problem is going to be your full dumps. Do you really want to run a full dump Fri, Sat, and Sun? Or do you just want to run a single full dump of the data allowing it to run over those 3 days? If the former, then I'd recommend that you allow for incrementals of some file systems to be done on certain nights. The reason is, 3 TB is a lot of time, and if you can't get it all done in one night, then there's no way you'll be able to back it all up on each of 3 nights. For the tape division between the 2 configs, that really depends upon how many tapes a single night takes. LTO2 tapes hold about 400GB (compressed). You mentioned 3TB to back up, so you're talking, for a level 0 of everything, about 8 tapes. You can probably cut that in half for the daily incremental runs, since a level 0 doesn't need to be done of everything every night. You could, perhaps, cut that back to 2 tapes if you have a rather high bumpsize. You'll also probably want to slowly introduce different file systems into the backup strategy at first in order to avoid requiring 8 or more tapes to start with. In other words, say you have 10 file systems which comprise that 3TB. If your disklist contains them all that first night, amanda will want to perform a level 0 of all 10 that first night. Some will fail if you run out of room on the tape since it can't fall back to incremental (since it doesn't have a level 0 to base that incremental on!). Rather, pick 2 or 3 file systems to backup the first night, then add a couple more the second night. Since those backed up the first night now have a level 0 base, amanda can bump those to a level 1, thereby making room for level 0s of the new file systems. Continue this until all of your file systems are in the disk list and have been backed up. Then you can start playing with the bumpsize to tweak when amanda bumps different file systems to new levels in order to save room. So, assuming your able to get your daily incrementals onto 2 tapes per night, times 4 nights, that's 8 tapes per week. You wanted 2 cycles for the incremental runs, that would be 16 tapes. Add a few for good measure (to guard agains sudden expansion, or a bad tape) and you've got 18-20 tapes in your daily config. Since you stated you were limited to 25 tapes, you might want to keep it on the low side, like 17-18 tapes. Additionally, since it's a 17 slot carrier that fits in there, you probably want to occupy 16 slots with tapes, and keep a cleaning tape in the 17th slot. You can reserve slots 0-7 for the daily tapes and 8-16 for the weekly tapes. Now for the 'full dump' configuration. If you've allocated 18 tapes for the incrementals, that only leaves you with 7 tapes for the full dump configuration, which is pretty tight. There's almost no way you'll fit 3TB onto 7 tapes at 400GB each. Especially if that 300TB number is only going to grow. And you certainly won't be able to run with 3 sets of full backups that way. If you really need to do full backups Fri-Sun of all file systems, I'd invest in more tapes. However, another alternative is to run a weekend configuration which allows for incrementals. Essentially, this is just like the daily incremental configuration. At 2 tapes per day, times 3 days, that's 6 tapes. You've got 7, which will handle either a bad tape, or a sudden increase in data set size. Of course, this doesn't allow for maintaing 3 *sets* of weekend tapes, so you'll still need more tapes (I'd say at least 14; ( (2 tapes * 3 days) + 1 extra) * 2 weeks ) Well, that's a start anyway, and should give you something to think about. I hope it's helpful. Feel free to ask more questions (or provide
flushin the holding disk along with a backup?
Hi all, Is there anyway to flush backups on the holding disk prior to dumping new backups? I have a bunch of stuff sitting on a holding disk which will likely fit fine on the same tape as tonights backups. However, even if something it causes tonight's backups to be placed on the holding disk, I'd rather get the older stuff onto tape and deal with the new stuff later. Is there a variable somewhere which can tell amanda to look for data on the holding disk and prioritize writing that to tape before writing other newer stuff? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: flushin the holding disk along with a backup?
In a message dated: Mon, 23 Aug 2004 12:55:28 EDT Joshua Baker-LePain said: autoflush yes G! I hate it when I RTFM, but my v-grep fails me :) Thanks. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
getting amanda to dump AFS
(I've sent this to the amanda-afs list, but I appear to be the only person other than Mitch actually on it, and he's apparently really busy :( I've installed the amanda-afs utilities on my AFS server/amanda client, and I've installed amanda (with afs patches) on the same. amcheck returns fine, amdump fails. My guess is that the gtar-wrapper.pl script which is *supposed* to get called from runtar is not actually getting called, since runtar doesn't know to call it. I've tried on the amanda ./configure line to specify --with-gnutar=/usr/sbin/gtar-wrapper.pl however, that resulted in: WARNING: *** /usr/sbin/gtar-wrapper.pl is not GNU tar, so it will not be used. Does anyone else here have amanda backing up AFS, and if so, can you help me along? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
amanda and OpenAFS?
Is there anyone backing up OpenAFS using amanda? Is there anything special that needs to be done, or is it just like backing up any other file system? I'd like to use gnutar if possible. Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
/dev/null caused backups to fail
All file systems on one of my backup clients failed over the weekend. The dump summary thinks the system was offline, but it wasn't, and the amadad debug log had this in it: amandad: time 0.016: amandahosts security check passed amandad: time 0.016: running service /usr/lib/amanda/sendsize sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] sendsize: error [spawn /usr/lib/amanda/runtar: dup2 in: Bad file descriptor] amandad: time 0.566: sending REP packet: The sendsize debug log also reveals: # grep 'no size line' sendsize.20040605234503.debug sendsize[30741]: no size line match in /bin/tar output for /u1/backup/all sendsize[30742]: no size line match in /bin/tar output for /u1/backup/aog sendsize[30745]: no size line match in /bin/tar output for /u1/backup/archive sendsize[30747]: no size line match in /bin/tar output for /u1/backup/bfb sendsize[30749]: no size line match in /bin/tar output for /u1/backup/cvs-repos sendsize[30751]: no size line match in /bin/tar output for /u1/backup/pd sendsize[30753]: no size line match in /bin/tar output for /u1/backup/rt sendsize[30755]: no size line match in /bin/tar output for /u1/backup/sw After digging through all this, I tried seeing what amcheck revealed (which I should have done first :) It stated: ERROR: jpt: [can not read/write /dev/null: Permission denied] Evidently, from what I can tell, /dev/null's permissions were changed sometime on Friday (16:42 to be precise) after my cron-driven amcheck runs. Is there any way to have amanda mention in the summary report that the reason a backup failed was because /dev/null was not writeable? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: /dev/null caused backups to fail
In a message dated: Mon, 07 Jun 2004 16:15:47 +0200 Paul Bijnens said: Besides the fact that a LOT of programs will fail mysteriously when /dev/null has been tampered with, here is a patch for sendsize.c . Thanks! ps. Ever replaced /dev/null with a plain file by accident? :-) M, can I plead the 5th ? ;) PPS. patch not tested to verify it it really detects the problem :-) Thanks for the warning :) -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
holding disk not getting used?
Hi all, For some reason, when my backups fail, the holding disk isn't being used. I'm running a weekly full dump config, and have 'skip-incr' and 'holdingdisk yes' in my dumptypes. But the holding disk this morning is empty. What did I miss? Thanks. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: New to Amanda- discouraged by some absurd limitations..
In a message dated: Tue, 04 May 2004 05:43:42 EDT Gene Heskett said: But, some have setup two configurations, one that runs weekly and is forced to do fulls on everything in the disklist, and one that runs during the week that does the incrementals. I do not do that here, so I'l let someone that is doing that explain it better than I can. It's rather simplistic actually. I have 3 configurations: daily- runs Mon-Fri, rotates through 12 tapes which remain in the changer at all times. - this is a normal amanda config, running level 0s every so often and incrementals in between. weekly - runs each Saturday, uses the last 4 slots of the changer - forces a full dump every time - tapes get rotated out to be stored off-site. archival - runs once per quarter - is basically the identical as the weekly with no upper bound on the tapes - tapes get stored off-site indefinitely and never come back (or, at some later date, will be determined to be re-usable) Hope that's helpful to someone. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Printing tape labels
In a message dated: Wed, 03 Mar 2004 16:02:00 CST Russell Adams said: I ended up creating some scripts that use GNU Barcode and Label Nation to print DLT barcodes on Avery labels. Had it running for two years. ;] If you're interested, I'll share. Yes PLEASE :) (sorry for such a late response, but I'm *really* behind on my list reading :) -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Performance tweaking?
Hi all, What variables affect Run time as reported by amanda after a run is complete? For example, in my reports, I see the following: Estimate Time (hrs:min)2:49 Run Time (hrs:min)10:33 Dump Time (hrs:min)8:38 8:38 0:00 So, it took almost 9 hours to dump to tape, but 10.5 hours of actual run time. Does that imply that the first 2 hours were spent getting estimates and then spooling enough data to the holding disk before streaming to tape began (i.e. is the 8:38 in parallel with the 10:33) ? Currently I'm using hardware compression on an LTO2 drive. Presumably things might be faster if I turned off hw compression and used the clients to do compression before sending to the amanda server? Ideas, thoughts, commends, flames :) Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Amanda backup strategy thoughts, full and incremental backups to tape once a week.
In a message dated: Tue, 06 Apr 2004 12:12:05 BST William Hargrove said: I was thinking I could do the incremental backups to a hard disk area on the tape server each night and then run Amanda once a week to archive the full backups plus the HDD incremental ones. I did this once, way back when all I had was a single DLT drive and no autoloader. I would just leave the drive empty all week, and on Friday mornings I would pop that week's tape in then amflush everything to tape. When that was done, I would place the weekend tape in the drive and the full dumps on Saturday night would go direct to tape, or, if I forgot, end up on the holding disk for amflushing Monday morning. This worked quite well IMO for the small environment I had at the time. HTH, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
getting an index of what's backed up?
Hi all, Is there some way of getting an index of what's on a given tape? I'm using the long DLE format to break down my file system into smaller disks and am using 'exclude append' to exclude certain things. The mail report obviously tells me which disks were backed up, but since these are pseudo-disks anyway, I'd like to see what under each of them was backed up. Is there a way to get the file listing for each disk? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Kerberos 5 support?
Is this being worked on and likely to happen anytime in the reasonably near future? I really don't want to punch holes in my firewall if I don't have to :) Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Editing disklist
Thanks for such a quick response Stefan, it is greatly appreciated!
On Fri, 23 Jan 2004, Stefan == Stefan G. Weichinger wrote:
Stefan Have a look in the amanda-manpage. In the section DISKLIST
Stefan FILE you will find the explanation (yes, they are kind of
Stefan labels).
I actually found this yesterday, but mis-read it. I re-read it again
just after I sent my earlier mail and read more carefully. I think I
now understand.
Stefan Something like:
jpt /u1/backup/all /u1/backup {
# Exclude everything that's explicitly named
# if we add a directory later, but forget to add it here
# it will be picked up automagically
non-user-high-tar
exclude list /usr/local/etc/amanda/daily/backup-excludes
} 1
I had thought of this, but then realized that this would also require
the maintenance of these files on each client (not a big deal, as it's
all in cvs, I just need to restructure some things).
Stefan And after that you list the dirs to be INcluded like this:
So you EXclude before you INclude? Or does it not matter?
Stefan The dumpsize for /u1/backup should be nearly nothing and so
Stefan you can check if your excludes work out fine. If it gets
Stefan bigger maybe some new directory has been created
This is exactly the behavior I am trying to achieve.
Stefan or some exclude does not work as intended.
This I'd like to avoid ;)
So, assuming for the moment that there is no practical difference
between using exclude list file.name and
exclude [append] pattern I'll stay with the latter for now for
testing purposes and clarity, and move to the former at a later time
for ease of maintenance.
To clarify, do I want:
jpt /u1/backup/all /u1/backup {
exlude all subdirs which follow as separate disks
} 1
Followed by:
jpt /u1/backup/subdir /u1/backup {
include specific subdir
} 1
or:
jpt /u1/backup/subdir /u1/backup {
include specific subdir
exlude everything else
} 1
?
Thanks again!
--
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
If you're not having fun, you're not doing it right!
Re: Editing disklist
Again:
jpt /u1/backup/specific subdir dumptype spindle
is sufficient. No {stuff} needed here.
This seems to be the general concensus, so, I guess I'll just go with
that :)
Thanks again, I appreciate all the help!
--
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
If you're not having fun, you're not doing it right!
Re: Level 1 dumps acting like level 0 dumps
On Sat, 17 Jan 2004, Steve == Steve Manuel wrote: Steve The man page for amanda can be more explict about what backup Steve programs can be used and where they record the time-stamp. If Amanda is going to modular such that it can use different backup programs, it's probably a lot easier to say: # record - record the dump timestamp in the time-stamp-database of the # backup program. Check the documentation for the # backup program you are using for more information. rather than try to keep track of all the different versions of backup programs and their corresponding time-stamp db files. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Editing disklist
On Tue, 23 Sep 2003, Stefan == Stefan G. Weichinger wrote: Stefan I want to change some DLEs from Stefan /mydisk/bigdir Stefan to Stefan /mydisk/bigdir/smalldir1 Stefan /mydisk/bigdir/smalldir2 Stefan /mydisk/bigdir/smalldir3 On Tue, 23 Sep 2003, CScheeder == C.Scheeder wrote: CScheeder i would do the following: add an excludelist to the dle CScheeder /mydisk/bigdir excluding /mydsik/bigdir/smalldir[1-n] CScheeder and leave it in the disklist. How does one 'add an excludelist to the dle' ? (also, what is dle?) I currently have my dumptype definitions which 'exclude-list' option. Do I add these smalldirs to this existing list, or is there a way to specify on a per-disk basis? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Pre/Post-dump scripts?
Hi all, I need to back up a data base, but want to have it dump the tables first. I thought there was a way to have amdump trigger pre/post dump processes natively. Or, is the only way to wrap amdump in a script of the same name, and effectively hide the real amdump program? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Encrypted network traffic
In a message dated: Tue, 30 Dec 2003 08:52:13 EST Henson, George Mr JMLFDC said: Is there support to have the network traffic to be encrypted? We have several systems we would like to backup over the network, but we have a mandate from our management that all the data transfers need to be encrypted. A perfectly reasonable mandate IMO. The easy way to add it would be to use sslwrap: http://www.rickk.com/sslwrap/ The nice thing about sslwrap is that it can be layered onto any existing service without any modification to the services you wish to encrypt. The other, probably more complicated, though possibly more secure method is to tunnel amanda through ssh. Also, a Google search turned this up: http://cns.utoronto.ca/~pkern/stuff/amanda-patch/Readme I have no idea how well it works. HTH. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Backing up via NFS.
In a message dated: Mon, 15 Dec 2003 16:56:38 EST Ken D'Ambrosio said: Any idea on where I'm going astray? Ken, Try using GnuTar for your dump program instead. Running 'dump' over an NFS mount if it ever works, is likely to be frought with problems. To compile amanda, you may well need to install a bunch of things like gcc, automake/autoconf, etc. The other option might be attempting to cross-compile for HPUX from Linux, since Linux has all the necessary tools to begin with. HTH, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Debian/Woody backport of 2.4.4p1 ?
Hi all, Does anyone know if there's a backport of amanda 2.4.4p1 to Debian Woody? I could use the packages in testing, but the require an upgrade of libc, which I really want to avoid on my production servers right now. Thanks! -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
using gnutar and file permissions
Hi all, I'd prefer to use tar to perform backups, primarilly for portability of restores. However, amanda is running as user 'backup' which doesn't seem to have read permissions in many places. How have others solved this problem? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
chunksize no longer a valid keyword?
Hi all, I'm trying to specify a 'chunksize' for my holding disk and I keep getting errors stating: /etc/amanda/daily/amanda.conf, line 45: configuration keyword expected I'm running 2.4.4p1-1 on Debian testing. I also noticed that there seems to be no 'holding disk' config area any more (based on the example amanda.conf file), yet the man pages seem to not reflect these changes. Is this just a case of the docs not keeping up with the code, or is the example amanda.conf file incorrect? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Having trouble with chg-scsi
Hi all, I'm having trouble coming up with a chg-scsi config file. I'm hoping someone can tell me what I'm missing. Hardware config is an Overland Storage PowerLoader with a 17 slot library and a single Ultrium LTO2 drive connected to a Debian Linux system. Amanda 2.4.2p2 is installed via Debian package. The tape drive is on SCSI ID 4 and the Library on SCSI ID 6. In amanda.conf I have: tpchanger chg-scsi changerfile /etc/amanda/test/overland.cfg tapedev 0 In overland.cfg I have: dev 0 drivenum 1 scsitapedev /dev/st0 tapeident 4 changerident 6 startuse 0 enduse 16 cleancart 0 eject 1 statfile /etc/amanda/test/overland.stat cleanfile /etc/amanda/test/overland.clean usagecount /etc/amanda/test/overland.usage tapestatus /var/log/amanda/tapestatus labelfile /etc/amanda/test/overland.label Yet this doesn't seem to work. Can anyone help me out? Thanks in advance! -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Overland Autoloaders?
In a message dated: Wed, 10 Sep 2003 09:25:39 EDT Joshua Baker-LePain said: That's at FAQ-O-Matic (linked from the amanda home page, possibly down). I attempted to search there, but didn't find it. I'm also rather dismayed at the condition of the Amanda F-O-M. It's been about 2 and a half years since I was last involved w/ amanda (it's an on-again,off-again relationship, but we keep coming back to each other ;) And the state of of F-O-M then wasn't that great. It needs some cleaning up (I'll gladly volunteer to do this if whomever is in charge of it will grant me the sufficient access). The thing to keep in mind, though, is that it's really your OS and other tools (e.g. media changer (like mtx)) which drive compatibility. Amanda, when it comes down to it, is just a backup scheduler. I'm aware of that. I will be using Linux (Debian) with which I've had good luck in the past with when using Amanda. However, LTO technology is new to me, and I've never used anything from Overland, so I figured I'd ask to see what kind of results others using amanda have had with this hardware. Is there such a list, if so where? If not, does anyone have anything good or bad to say about the Overland Storage PowerLoader? I've got a Library Pro with an AIT3 drive which worked out of the box on Linux with mtx, barcodes and all. Amanda works quite nicely with it, and I've had no problems with the unit. Nice box. Great! Thanks! Once I get my hardware in and configured, I'll be sure to share my experiences :) Thanks again!
Re: Overland Autoloaders?
In a message dated: Wed, 10 Sep 2003 15:42:24 +0200 Peter Kunst said: using an Overland Powerloader connected to a Solaris8 box works fine here, but might not help you with your Debian setup. We drive the changer itself using stc (http://www.cs.pdx.edu/~eric/stctl) ...just a hint. Great! Thanks, for the data point! -- Seeya, Paul
Overland Autoloaders?
Hi all, It's been a while since I've used amanda, but I thought at one time, there was a list of drives and/or library/autoloaders known to work with amanda. I've searched amanda.org, but couldn't find anything. Is there such a list, if so where? If not, does anyone have anything good or bad to say about the Overland Storage PowerLoader? Thanks,
