Running amflush to a Separate Tape
I am new to both Linux and Amanda, so please be gentle. I've recently come over from the dark side of Windoze. I've inherited a small net from a previous sysop. He was using Amanda on two servers, and I would like to continue use, but I'm finding it a bit challenging. I've gotten as far as determining there are a large number of Amanda directories left on the holding disk. I would like to flush those to an entirely separate tape, outside of my Daily config, but am unsure how to do this. I would like to flush those directories today if possible, so that I can move on to resolving errors on the amreport I receive (and which I will ask about in a separate email). Any help would be greatly appreciated. Tom -- View this message in context: http://www.nabble.com/Running-amflush-to-a-Separate-Tape-tp14318108p14318108.html Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: Running amflush to a Separate Tape
On Thu, Dec 13, 2007 at 07:33:25AM -0800, Tom Herrera wrote: I am new to both Linux and Amanda, so please be gentle. I've recently come over from the dark side of Windoze. I've inherited a small net from a previous sysop. He was using Amanda on two servers, and I would like to continue use, but I'm finding it a bit challenging. I've gotten as far as determining there are a large number of Amanda directories left on the holding disk. I would like to flush those to an entirely separate tape, outside of my Daily config, but am unsure how to do this. I would like to flush those directories today if possible, so that I can move on to resolving errors on the amreport I receive (and which I will ask about in a separate email). Any help would be greatly appreciated. The phrase outside of my Daily config gives me trouble. These files on the holding disk represent completed, but untaped, backups of file systems and directory trees that amanda's logs have already recorded. If needed, they are available for restoration whether on the holding disk or taped to a Daily config tape. Were it feasible to amflush to a different config you might lose this ability. That said, if you just want it taped in case you want or need it, simply tar or dd the holding disk to a blank, non-amanda tape. My alternative recommendation, seeing as you seem to have available tapes, is to amflush them within your Daily config. If you don't want to upset the current set of tapes use amlabel to add a few newly labeled tapes to your Daily config tapelist file. If your current tapes go from ?Daily?-001 to ?Daily?-050, maybe do a few in the -100 range. Then when you amflush make sure only your newly labeled tapes are in the drive/library. Amanda will always happily use a new tape. Note, depending on the volume of data on the holding disk and the runtapes parameter in your amanda.conf file it may be necessary to make multiple runs of amflush. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Running amflush to a Separate Tape
On Thursday 13 December 2007, Tom Herrera wrote: I am new to both Linux and Amanda, so please be gentle. I've recently come over from the dark side of Windoze. I've inherited a small net from a previous sysop. He was using Amanda on two servers, and I would like to continue use, but I'm finding it a bit challenging. I've gotten as far as determining there are a large number of Amanda directories left on the holding disk. I would like to flush those to an entirely separate tape, outside of my Daily config, but am unsure how to do this. I would like to flush those directories today if possible, so that I can move on to resolving errors on the amreport I receive (and which I will ask about in a separate email). Any help would be greatly appreciated. Tom Generally speaking, Tom, anything that's left in the holding disk, probably due to a tape error, is still part of the database amanda keeps, so they should be flushed to the next available tape in the rotation. Otherwise you are miss-placing valuable info that amanda may need in the future. The real question is why they were not properly flushed originally. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) AMAZING BUT TRUE ... There is so much sand in Northern Africa that if it were spread out it would completely cover the Sahara Desert.
Re: Running amflush to a Separate Tape
Gene Heskett wrote: Generally speaking, Tom, anything that's left in the holding disk, probably due to a tape error, is still part of the database amanda keeps, so they should be flushed to the next available tape in the rotation. Otherwise you are miss-placing valuable info that amanda may need in the future. The real question is why they were not properly flushed originally. Gene and Jon, Thanks for the quick replies. I am not at all sure why there are so many directories to be flushed - they range in age from March thru last week, and they all, but the last, apply to a time before I became sysop here. So I am not all that concerned about the ancient ones, I'd just like to flush the last one (recent) and move ahead. So it would be okay for me to tar/gzip all the other directories? If I remove them Amanda won't get mad at me? Or do I somehow need to tell Amanad hey, those aren't so important anymore. Tom -- View this message in context: http://www.nabble.com/Running-amflush-to-a-Separate-Tape-tp14318108p14320406.html Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: Running amflush to a Separate Tape
Gene Heskett wrote: On Thursday 13 December 2007, Tom Herrera wrote: I am new to both Linux and Amanda, so please be gentle. I've recently come over from the dark side of Windoze. I've inherited a small net from a previous sysop. He was using Amanda on two servers, and I would like to continue use, but I'm finding it a bit challenging. I've gotten as far as determining there are a large number of Amanda directories left on the holding disk. I would like to flush those to an entirely separate tape, outside of my Daily config, but am unsure how to do this. I would like to flush those directories today if possible, so that I can move on to resolving errors on the amreport I receive (and which I will ask about in a separate email). Any help would be greatly appreciated. Tom Generally speaking, Tom, anything that's left in the holding disk, probably due to a tape error, is still part of the database amanda keeps, so they should be flushed to the next available tape in the rotation. Otherwise you are miss-placing valuable info that amanda may need in the future. The real question is why they were not properly flushed originally. One other point to check. Since Tom is coming new into an existing setup, and didn't specify in his original post, it's possible those are from another amanda configuration that is not being run. The names of the files should indicate when and what they are from. I mean, if the daily is running and writing a tape, and there are still things being left on the holding disk, then Tom needs to figure out why they are still there. First step is to know for sure where they came from. Then, if they are from the daily that is currently being run, why were they left on the holding disk? --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst [EMAIL PROTECTED] --- Erdös 4
Re: Running amflush to a Separate Tape
Chris Hoogendyk wrote: One other point to check. Since Tom is coming new into an existing setup, and didn't specify in his original post, it's possible those are from another amanda configuration that is not being run. The names of the files should indicate when and what they are from. I mean, if the daily is running and writing a tape, and there are still things being left on the holding disk, then Tom needs to figure out why they are still there. First step is to know for sure where they came from. Then, if they are from the daily that is currently being run, why were they left on the holding disk? I checked, and all the directories on the holding disk are associated with the one and only amanda config file on the system, named Daily. Since I was not here for the bulk of the directories listed I am not sure why they were never flushed. Still curious if it is okay, amanda-wise, to just remove the ancient directories, or if I have to do something more than that. -- View this message in context: http://www.nabble.com/Running-amflush-to-a-Separate-Tape-tp14318108p14323017.html Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: Running amflush to a Separate Tape
On Thu, Dec 13, 2007 at 11:24:53AM -0800, Tom Herrera wrote: Chris Hoogendyk wrote: One other point to check. Since Tom is coming new into an existing setup, and didn't specify in his original post, it's possible those are from another amanda configuration that is not being run. The names of the files should indicate when and what they are from. I mean, if the daily is running and writing a tape, and there are still things being left on the holding disk, then Tom needs to figure out why they are still there. First step is to know for sure where they came from. Then, if they are from the daily that is currently being run, why were they left on the holding disk? I checked, and all the directories on the holding disk are associated with the one and only amanda config file on the system, named Daily. Since I was not here for the bulk of the directories listed I am not sure why they were never flushed. Still curious if it is okay, amanda-wise, to just remove the ancient directories, or if I have to do something more than that. When you run amflush it will ask which directories/dates you wish to flush. After you have done the one(s) you want, I think it is safe to blow away the ones you don't want. The logs will rotate and be deleted on their own. Or archive them; or if space on holding disk is not a problem, leave them for later. After doing the above I'd also suggest running amcleanup. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Running amflush to a Separate Tape
Tom Herrera wrote at 11:24 -0800 on Dec 13, 2007: Still curious if it is okay, amanda-wise, to just remove the ancient directories, or if I have to do something more than that. Try 'amadmin config_name holding delete ...' (see the amadmin man page) I think this is a new feature in amanda 2.5.2 This is a little better than just blowing the dirs away. If you do that, you could leave some log index turds. Usually this stuff is cleaned up over time, but not always.
Please add amdump to the line in .amandahosts
Hi, Solaris 9 Server with amanda 2.4.4 Client is a zone on a solaris 10 system running amanda 2.5.2p1. amcheck -c info Amanda Backup Client Hosts Check ERROR: NAK squidzone1: user amanda from 199.184.30.36 is not allowed to execute the service noop: Please add amdump to the line in /export/home/amanda/.amandahosts on the client WARNING: panther: selfcheck request timed out. Host down? Client check: 16 hosts checked in 30.356 seconds, 2 problems found I didn't see a clear answer to this on the net/lists so I thought I'd throw my 2cents in. Issue was not (In my case) file ownerships nor protections on the client, but rather seems to be that the zone is not able to resolve the IP of the amanda server. I've defered that to the admin for this particular box, in the mean time I've added the IP address to .amandahosts on the client and have gotten clean output from amcheck. Nothing earth shaking here, just a matter of top-down problem solving and making sure that all of the assumptions, like DNS working correctly, where actually true. --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
