unsubscribe
unsubscribe
Press Release
For Immediate Release Incline Village, Nevada Contact Corporate Communications www.sugarpinellc.com Sugarpine Sierra West, LLC is proud to announce 4 additional services, Sports Memorabilia, Hair Raisers, Financial Services and Worlds-Best-4 the worlds largest virtual shopping mall featuring over 2.2 million products! Save time! Save money! Make money!!! These services and products are now available to everyone. To view these tremendous opportunities, please visit our website. Sports Memorabilia may be viewed simply by clicking on its front-page banner. Hair Raisers may be viewed by visiting our web site, www.sugarpinellc.com, and select our associatesÂ’ link. Our Financial Services is linked and bannered on our home page. As you all may already know, Sugarpine Sierra West, LLC is at its heart an asset hosting company. Please donÂ’t forget to look at our Asset Gallery to see some outstanding business and investment opportunities, as well as collectables and real estate. Sugarpine Sierra West, LLC would like to extend its sincere thanks and appreciation to all! Please visit us at our web site at: www.sugarpinellc.com. Corporate Communications: Sugarpine Sierra West, LLC Mr. Charles J. Armstrong II or Ms. Denise Pavlo Phone: 775-832-2552 E-Mail: [EMAIL PROTECTED] To be removed from our e-mail list, reply to this e-mail with "REMOVE" in the subject line of your reply.
AIX/HACMP/SSA
Hi, has anyone some experience using Amanda on AIX clusters using HACMP and volumes residing on a SSA subsystem?
Re: Estimates taking a long time.
Colin Smith <[EMAIL PROTECTED]> wrote: > I'm running backups on 3 Linux systems, one of the systems is a Cobalt > Qube. All the backups are done using GNU tar. It works OK but the try remounting those fs noatime during estimates: mount / -o remount,noatime
Re: Single-tape unit, multiple tapes per backup? (newbie)
>I am pretty new to Amanda ... Welcome! >I have a single-tape SCSI unit (DDS-2). I want to be able to backup >more than ~5GB per run. ... Keep in mind that a single backup image (i.e. the dump of one file system) cannot span a tape (yet), so you have to keep their size to under ~5GB. >Is there not a way to get Amanda to somehow >stop at the end of a tape, email a request for another tape, and then >continue when the tape has been changed? You want chg-manual. This uses a human to emulate a tape changer. Set tpchanger to "chg-manual" in amanda.conf, and set "changerfile" to the path of a set of files the changer will maintain. For instance, if you set it to "/etc/amanda/changer", the changer will create and update /etc/amanda/changer-clean, /etc/amanda/changer-access and so on. And if /etc/amanda/changer (no suffix) exists, it will be sourced into the script, which lets you override the request() function. That is what the script uses to request a new tape, so you can have it do whatever you need. The script has an example in the comments of using E-mail. >--Dan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: How to set correct access rights?-
"John R. Jackson" schrieb: > > >The syntax in .amandahosts > >DIFFERS from .rhosts in that you have to specify one user per line. > > I just looked at the code and ran a couple of tests and don't see > a difference. According to the docs I have, .rhosts allows one (and > only one) optional username on each line: > > hostname [username] > > That's exactly what .amandahosts does as well. If you leave off the > username, it defaults to the Amanda user (the one it is running as from > inetd/xinetd). This is different from .rhosts: If you leave off the username, it will accept any user. > So what was it in your .amandahosts file that didn't follow this pattern? Exactly. Reading the .rhosts manpage, I assumed any user would be accepted if I put only hostnames in there. > As I recall, it was just a list of host names without username fields. > Are you running a different user on the client and server? In fact, FreeBSD used until recently another default user. The backup server uses "operator:operator" as amanda user/group, while the (older) clients still utilize the "backup:operator" user. Thus, interoperatibility stopped after upgrading the backup server (for unrelated reasons). Thanks for all the explanations and your help -Christoph Sold
Re: Adaptec 2944, aic7xxx, 2.4.5-ac16 => Scsi errors?
> Jul 19 02:10:46 byerhope kernel: (scsi0:A:3:0): Unexpected busfree in >Data-in phase >... >Has anyone any thoughts on what to look for? Ummm, maybe a Linux mailing list? :-) I suspect you need to talk to the kernel driver writers and find out what this really means. It's way too deep to be an Amanda issue (other than Amanda happens to be doing application level I/O). Having said that, though, all the normal SCSI issues come up: * Do you have exactly one (no more, no less) termination on the chain and is it at the end of the chain? * Do you have a mix of wide and narrow devices on the chain, and if so, are they in the proper order (as I recall, all the narrow devices need to be at the end)? * Have you checked the cables to make sure they are seated properly? * Have you checked the controller board to make sure it is seated properly? >Chris Ritson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: dumper fails: "data write: Invalid argument"
Hi! John R Jackson writes: >> It's a Solaris 2.5.1 box. I didn't specify any chunksize, so my >> thinking was that the default of 1 Gb is fine. John> It should have been. You might set it explicitly just to be John> sure. I'll try that. John> You might also check the ulimit values (and maybe the disk John> quota) for your Amanda user to make sure you're not banging into John> that kind of problem. Ok, I'll check that, although my amanda user is root (probably not the best idea) and I didn't explicitly set any limits. >> However, thanks for the pointer! I'll play with a smaller chunksize, >> especially a chunksize smaller than the `use - xxx Mb' value... John> The "chunksize" and "use" values are not related, and John> "chunksize" certainly does not have to be smaller than "use". John> The "use" value determines how much total space Amanda has to John> work with in the holding disk. The "chunksize" value tells it John> how to split apart a single image. That's how I did understand the manual, as well. I was just thinking that there might be a problem with concurrent dumpers writing to the holding disk and the negative notation of the `use' parameter. Probably my next attempt will be to attach strace to a running dumper for a filesystem that I `expect' to fail and concurrently observing the holdingdisk space. -frank
