Re: Disabled hw compression
Just for your information, on my Linux mtx's version (Slackware 8.1 with a 2.4.18 kernel) there is no such option "nocompression" to mtx... But there are the options defcompression and compression which can be set to 0 then it looks like that compression is disabled... PS: thanks Joshua for your help Regards Russell Adams To: [EMAIL PROTECTED] Subject: Re: Disabled hw compression Sent by: owner-amanda-users@ amanda.org 02/18/03 04:54 PM Under Linux you can call the following to disable compression. mt -f /dev/st0 nocompression The other method would be the disable a DIP switch or jumper on the tape drive. I include the above line in my startup scripts. It would appear it only needs to be set at boot. Russell On Mon, Feb 17, 2003 at 11:27:11PM +0100, [EMAIL PROTECTED] wrote: > Hello, > > I am using an Exabyte Eliant 820 tape drive on Linux kernel 2.4.18 and > would like to make sure the hardware compression is disabled. Does anyone > know how I can check that ? > > Thanks > Regards
Disabled hw compression
Hello, I am using an Exabyte Eliant 820 tape drive on Linux kernel 2.4.18 and would like to make sure the hardware compression is disabled. Does anyone know how I can check that ? Thanks Regards
Re: AMANDA and the Windows world
Hi, I just wanted to thank you all who replied to my post !! Regards Marc Richard MorseTo: Joshua Baker-LePain <[EMAIL PROTECTED]> Subject: Re: AMANDA and the Windows world 02/12/03 05:01 PM On Wednesday, February 12, 2003, at 09:29 AM, Joshua Baker-LePain wrote: > The cygwin client is pretty new and thus less tested. > I'd just like to say that so far, it seems to work. I still need to do a test restore, and I don't know about ACLs, but the signs are that things are working correctly, given the amount of data that gets backed up every night I'm going to do a test restore today, and probably add another two clients, to get better testing results... Ricky
AMANDA and the Windows world
Hello, I wanted to ask how good is AMANDA to backup Windows servers ? One of the few issues I can think of is: - will it backup a windows file owner permissions and rights (ACL) ? - is it possible for AMANDA to restore directly to a Windows server ? - what needs to be put in place to backup windows servers ? Is there an amanda client for windows ? Thanks for the comments Regards
AMANDA and sencrypt/sst -> dump: Broken pipe
Hello, I am using an AMANDA 2.4.3 server patched with the sencrypt script from http://cns.utoronto.ca/~pkern/stuff/amanda-patch/ and also using sst to do the encryption from the same author. I am using exactly the same configuration on both the server and the client. The problem is that somehow dump returns Broken pipe with I turn sencrypt to on, if I don't use sencrypt it works pefectly. Here is the output of the sendbackup logfile on the client: sendbackup: debug 1 pid 21255 ruid 104 euid 104: start at Sun Feb 9 19:44:14 2003 /opt/amanda/libexec/sendbackup: version 2.4.3 parsed request as: program `DUMP' disk `/' device `/' level 1 since 2003:2:8:23:14:6 options `|;auth=bsd;sencrypt;compress-best;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.44864 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.44865 sendbackup: time 0.001: waiting for connect on 44864, then 44865 sendbackup: time 0.039: stream_accept: connection from X.X.X.X.57784 sendbackup: time 0.059: stream_accept: connection from X.X.X.X.51050 sendbackup: time 0.060: got all connections sendbackup: time 0.060: spawning /local/bin/sst in pipeline sendbackup: argument list: /local/bin/sst -celv sendbackup: time 0.061: spawning /bin/gzip in pipeline sendbackup: argument list: /bin/gzip --best sendbackup-dump: time 0.061: pid 21258: /bin/gzip --best sendbackup: time 0.063: dumping device '/dev/hda2' with 'ext3' sendbackup: time 0.064: spawning /sbin/dump in pipeline sendbackup: argument list: dump 1usf 1048576 - /dev/hda2 sendbackup: time 0.904: 91: normal(|): DUMP: Date of this level 1 dump: Sun Feb 9 19:44:14 2003 sendbackup: time 0.907: 91: normal(|): DUMP: Date of last level 0 dump: Sat Feb 8 23:27:22 2003 sendbackup: time 0.909: 91: normal(|): DUMP: Dumping /dev/hda2 (/) to standard output sendbackup: time 0.911: 91: normal(|): DUMP: Exclude ext3 journal inode 8 sendbackup: time 1.112: 91: normal(|): DUMP: Label: / sendbackup: time 1.115: 91: normal(|): DUMP: mapping (Pass I) [regular files] sendbackup: time 3.663: 91: normal(|): DUMP: mapping (Pass II) [directories] sendbackup: time 4.818: 91: normal(|): DUMP: estimated 139205 tape blocks. sendbackup: time 4.821: 91: normal(|): DUMP: Volume 1 started with block 1 at: Sun Feb 9 19:44:19 2003 sendbackup: time 4.864: 91: normal(|): DUMP: dumping (Pass III) [directories] sendbackup: time 5.756: 91: normal(|): DUMP: Broken pipe sendbackup: time 5.758: 91: normal(|): DUMP: The ENTIRE dump is aborted. sendbackup: time 6.059: error [compress got signal 13, sencrypt returned 33, /sbin/dump returned 3] sendbackup: time 6.059: pid 21255 finish time Sun Feb 9 19:44:20 2003 Does anyone know what could be wrong ? If you need more details or other log files let me know, I would be pleased to provide them... Thanks for the help ! Regards
RE: Running AMANDA over the Internet
I think the easiest way would be to use an SSH tunnel. Would this be easy to implement ? Any examples maybe or pointers on how to acheive that ? Thanks Regards "Bort, Paul" To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] <[EMAIL PROTECTED] cc: om> Subject: RE: Running AMANDA over the Internet Sent by: owner-amanda-users@ amanda.org 02/05/03 04:20 PM Amanda is a backup manager, not a security manager. There are no steps taken to ensure the security of the backups. Several solutions are available, though: - Use the Kerberos support built in to Amanda. I've never played with this. - Use tar with a wrapper script on the client that encrypts the backup before sending it. You might be able to find samples of this in the list archives. - Use an encrypted VPN (CIPE, FreeSWAN, SSHTunnel) between servers. This is the method I used, because I use the same tunnel for monitoring and file transfers. Search the list, think about what method fits your needs. Feel free to ask more questions. Good Luck. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 05, 2003 9:50 AM > To: [EMAIL PROTECTED] > Subject: Running AMANDA over the Internet > > > Hello, > > Let's take the scenario where I have got an AMANDA server > located at one > central site and have a few other servers located at various > places around > the globe which of course all need to be backed up by the > centraon site's > AMANDA server. My question is now more related about security and how > secure it is to run backups over the internet. Is AMANA > secure by default > to run over the internet or are there any optional compiling > options or > features which I should use to make the clients itself and > the dump secure > ? > > Many thanks for your opinion > > Regards > > > >
Running AMANDA over the Internet
Hello, Let's take the scenario where I have got an AMANDA server located at one central site and have a few other servers located at various places around the globe which of course all need to be backed up by the centraon site's AMANDA server. My question is now more related about security and how secure it is to run backups over the internet. Is AMANA secure by default to run over the internet or are there any optional compiling options or features which I should use to make the clients itself and the dump secure ? Many thanks for your opinion Regards
AMANDA tape device on Solaris
Hello, I wanted to know for an AMANDA backup server running on Solaris which tape device to use, currently I am using /dev/rmt/0bn but I saw some documentation especially the RESTORING documentation which mentions using /dev/rmt/0cn, so what would be the correct device to use ? Regards
Re: Tape labelling and strategy
First, thanks for your detailed opinion. You are right I could use 40 tapes in the config but then I would like to have at least a dump level 0 once per week, so how would I acheive that, I mean which config options in my amanda.conf to use ? is something like that correct: dumpcycle 5 days runspercycle 5 tapecycle 40 runtapes 2 also what's the strategy to adopt when the set of 8 tapes is finished, take it offsite and relabel the next ones ? Or should I label all 40 tapes in one go ? Regards Marc Gene Heskett To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Tape labelling and strategy 11/29/02 01:04 PM Please respond to gene_heskett On Friday 29 November 2002 04:16, [EMAIL PROTECTED] wrote: >Hello, > >I would like to rotate between multiple sets of 8 tapes because my > changer supports maximum 8 tapes. So I have defined the following > in my amanda.conf: > >dumpcycle 5 days >runspercycle 5 >tapecycle 8 >runtapes 2 > >When one set of 8 tapes is finished I will take it offsite and > then start up with the next set, I plan to have maybe 5 sets > which i will constantly rotate which means overwritting stuff. > What kind of labelling should I use for that ? I was thinking of > something like > >nameXX-Y > >where XX is the tape number >where Y is the set letter, for example: > >mysite03-B > >that would be tape number 4 from set B > >or should I simply use "nameXX" ? But then AMANDA won't keep any > history of the other sets... What do you think ? > >Regards >Marc What you propose is equ to having a tapecycle of 40, and would be much simpler for amanda to administer than it would be to maintain 5 different amanda configuration trees and remembering to do the configuration switches in your amanda crontab. What you do with the 8 tapes you take out each time the magazine is reloaded is up to you, and amanda won't care as long as they are back on-site in time to be re-used on schedule. If you changed the config each time the magazine was reloaded, then on the first run of each different config amanda is going to think everything is way behind and attempt to do fulls on everything because she is 32 days behind schedule *for the just switched in config*. It makes more sense to amanda to just give her marching orders and let her sort out the scheduleing. Amanda will then have an inventory list of everything on the tapes, all 40 of them once the tapecycle has been completed once. For your own organization, I'd imagine the regex expression for the tape label in amanda.conf could be modified to include an extra character to define which magazine group this tape belonged in, and amanda won't care since she will, unless something mucks the schedule (and I've had it happen here), use them in the order they were labeled anyway, NOT in the individual tapes order numerically. That runtapes = 2 if its used by amanda, will lead to some interesting human scheduleing 'adjustments' though. Will your system really need that once it "gets into the beat", which will take dumpcycle runs for the fulls, and tapecycle runs for the partials IIRC? Actually that will take longer if you follow a strategy of only compressing that which can be compressed, by setting everything for compression, reading the emails from amanda and turning off the compression via a change in the disklist entry for those directories/partitions that don't compress on a level 0 backup. Directories full of rpms and tar.gz or tar.bz2's & such don't compress, and may in fact expand somewhat if run through gzip a second time. That
Tape labelling and strategy
Hello, I would like to rotate between multiple sets of 8 tapes because my changer supports maximum 8 tapes. So I have defined the following in my amanda.conf: dumpcycle 5 days runspercycle 5 tapecycle 8 runtapes 2 When one set of 8 tapes is finished I will take it offsite and then start up with the next set, I plan to have maybe 5 sets which i will constantly rotate which means overwritting stuff. What kind of labelling should I use for that ? I was thinking of something like nameXX-Y where XX is the tape number where Y is the set letter, for example: mysite03-B that would be tape number 4 from set B or should I simply use "nameXX" ? But then AMANDA won't keep any history of the other sets... What do you think ? Regards Marc
Re: which tpchanger script to use
For a changer device on LUN 1 you need to edit the Solaris's generic SCSI driver /kernel/drv/sgen.conf. This works fine, did some tests with mtx. I was just more wondering what are the criterias to choose between chg-scsi or chg-zd-mtx... Regards Marc Gene Heskett To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: which tpchanger script to use 11/27/02 02:01 PM Please respond to gene_heskett On Wednesday 27 November 2002 03:53, [EMAIL PROTECTED] wrote: >Hello, > >I am currently setting up an amanda 2.4.3 server on Solaris 9 with > a Compaq TSL-9000 DDS-3 tape changer device and was wondering > which "tpchanger" script I should use, will chg-scsi work or do I > need to use chg-zd-mtx maybe ? The compaq tape changer uses one > target but then the tape runs on LUN 0 and the changer on LUN 1. > >Thanks > >Marc chg-scsi which seems to be right at home with a drive at lun0/robot at lun1 setup, is running one of the many variations of Seagate 4586 changers just fine here. This is the one that has either a 4 tape or a 12 tape(the drawer stays open and the magazine runs up and down the front of the computer) arranged so the tapes are horizontal. The drive is /dev/nst0, the robot is /dev/sg1. If this was linux, You'd have to build a kernel with the scsi option 'scan all luns' turned on else the robot won't be found. Its not on by default. I don't know about solaris though. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.19% setiathome rank, not too shabby for a WV hillbilly
which tpchanger script to use
Hello, I am currently setting up an amanda 2.4.3 server on Solaris 9 with a Compaq TSL-9000 DDS-3 tape changer device and was wondering which "tpchanger" script I should use, will chg-scsi work or do I need to use chg-zd-mtx maybe ? The compaq tape changer uses one target but then the tape runs on LUN 0 and the changer on LUN 1. Thanks Marc
Re: COMPAQ TSL-9000 DAT autoloader device
Well my drive is not a SDT-9000 but a COMPAQ TSL-9000, or are these drives the same ? Regards On Fri, Nov 22, 2002 at 10:18:46AM +0100, [EMAIL PROTECTED] wrote: > > Hi Jim, > > I will go and have a look on the Sony website for some PDFs, with the help > of some members of the AMANDA mailling list I've managed to get it working > fine on Solaris 9. I would be very pleased if you could send me the > tapetype as it isn't in the Faq-O-Matic. By searching for sony I found 6 entries for the SDT-9000 in the FOM. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: COMPAQ TSL-9000 DAT autoloader device
Hi Jim, I will go and have a look on the Sony website for some PDFs, with the help of some members of the AMANDA mailling list I've managed to get it working fine on Solaris 9. I would be very pleased if you could send me the tapetype as it isn't in the Faq-O-Matic. Regards Marc Jim Summers To: amanda-users <[EMAIL PROTECTED]> <[EMAIL PROTECTED] cc: s.ou.edu> Subject: Re: COMPAQ TSL-9000 DAT autoloader device Sent by: owner-amanda-users@ amanda.org 11/21/02 03:11 PM Marc, I am using just a Sony TSL-9000 with amanda. I use the chg-zd-mtx script. My os is linux though. I do have the sony docs and I will peruse through them to see if there is anything helpful. Also, I am pretty sure that I navigated through the Sony web and found pdf files for the 9000. If you need a tapetype respond back to the list and I will send one. Seems like the last one I ran was w/o HWCOMP so it is pretty accurate. Might save you about 5-7 hours of time. Jim On Thu, 2002-11-21 at 06:55, [EMAIL PROTECTED] wrote: > Hello, > > Does anyone have experience in configuration a COMPAQ/SONY TSL-9000 DAT > DDS-3 device with AMANDA ? I have only the device and no single > documentation about it. What I can tell is that it's an 8 DDS-3 tape > changer device which gets recognized on my Solaris 8 system under > /dev/rmt/0. Somehow it doesn't have two devices in it (as usual where you > have one device for the changer and one device for the tape) so that's > already something weird. I've tried to use mtx but mtx doesn't seem to like > the device at all. > > Any help would be appreciated. > > Regards > Marc >
COMPAQ TSL-9000 DAT autoloader device
Hello, Does anyone have experience in configuration a COMPAQ/SONY TSL-9000 DAT DDS-3 device with AMANDA ? I have only the device and no single documentation about it. What I can tell is that it's an 8 DDS-3 tape changer device which gets recognized on my Solaris 8 system under /dev/rmt/0. Somehow it doesn't have two devices in it (as usual where you have one device for the changer and one device for the tape) so that's already something weird. I've tried to use mtx but mtx doesn't seem to like the device at all. Any help would be appreciated. Regards Marc
Re: DAT hardware or software compression
Thanks for your quick answer. Ok it sounds clear to me that all points to the advantages of having software compression. I will then disable hardware compression. Regards Marc Joshua To: [EMAIL PROTECTED] Baker-LePain cc: [EMAIL PROTECTED] <[EMAIL PROTECTED] Subject: Re: DAT hardware or software compression u> 11/20/02 02:52 PM On Wed, 20 Nov 2002 at 2:13pm, [EMAIL PROTECTED] wrote > I have got here a DDS-3 tape drive which has per default hardware > compression enabled and was wondering what is the best deal with AMANDA. > Would you guys suggest hardware compression or should I disable hardware > compression and have software compression done for example with gzip ? It's personal preference, really. If you've got the cycles, software compression is generally better and (depending on CPU power of course) faster than hardware. It also allows amanda to better plan, as it knows *exactly* how big your tapes are and can keep a history of compression levels. Hardware compression, well, takes load off your server and/or clients, but you have to lie to amanda about your tapelength. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
DAT hardware or software compression
Hello, I have got here a DDS-3 tape drive which has per default hardware compression enabled and was wondering what is the best deal with AMANDA. Would you guys suggest hardware compression or should I disable hardware compression and have software compression done for example with gzip ? Regards Marc
Re: New amanda version
Hehe well it's just a matter of upgrading all the clients and server with the time but during the client/server upgrade there will be multiple versions running so I just wanted to make sure this will not create problems... Regards Marc Gene Heskett To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: New amanda version 10/14/02 03:48 PM On Monday 14 October 2002 08:50, [EMAIL PROTECTED] wrote: >Hi there, > >I saw that there is a new stable version of AMANDA out. Now is it > possible to run the old version as AMANDA as a server (2.4.2p2) > and use the newewst version as client ? Will that work ? > >Regards >Marc Its compatible. But there are things the new version does that the older one stumbles over occasionally. Thats why there are new versions you know. :-) -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.18% setiathome rank, not too shabby for a WV hillbilly
New amanda version
Hi there, I saw that there is a new stable version of AMANDA out. Now is it possible to run the old version as AMANDA as a server (2.4.2p2) and use the newewst version as client ? Will that work ? Regards Marc
netusage parameter in amanda.conf
Hello, Does the netusage parameter in amanda.conf really work ? I am asking this because I have changed it to 50 kByte/s and still see the backups taking the same amount of bandwidth on the MRTG graphs of the backup server... Regards Marc
Re: Comments in .amandahosts
Well looks like comments starting with # in .amandahosts works, I added a few line of comments in it and did an amcheck, no errors where returned... Marc Gene Heskett To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Comments in .amandahosts 09/18/02 03:19 PM On Wednesday 18 September 2002 08:01, [EMAIL PROTECTED] wrote: >Hi there, > >Is it possible to add some comments in the .amandahosts file ? For > example: > ># this is my comment bla bla bla bla >192.168.200.200 amandauser > >Regards >Marc Good Q Marc, all I can say is I don't have any in mine. You can add a line, and run amcheck to see if it complains I suppose. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Comments in .amandahosts
Hi there, Is it possible to add some comments in the .amandahosts file ? For example: # this is my comment bla bla bla bla 192.168.200.200 amandauser Regards Marc
Re: Strange dump details
Well, the weird thing is that I already replaced the hard drive once because I was thinking that it could only be a HD problem, but the problem still persists. What I also tryed is to do a manual dump on that machine and that works fine... So that sounds really strange... Any ideas ? Marc "Ueda, To: [EMAIL PROTECTED] Yoshiaki"cc: <[EMAIL PROTECTED] Subject: Re: Strange dump details om> Sent by: [EMAIL PROTECTED] m 07/11/02 09:50 AM It isn't caused by amanda. It is hard drive problem. You have to try repair command at your drive, or replase hard drive. On Thu, 11 Jul 2002 09:32:15 +0200 [EMAIL PROTECTED] wrote: [cut] > ? DUMP: bread: lseek fails > ? DUMP: bread: lseek fails > ? DUMP: bread: lseek fails > ? DUMP: bread: lseek fails > ? DUMP: short read error from /dev/hdc1: [block -909618816]: count=4096, > got=0 > ? DUMP: bread: lseek2 fails! > ? DUMP: short read error from /dev/hdc1: [sector -909618816]: count=512, > got=0 > [cut] Yoshiaki Ueda Cognex Corporation
Strange dump details
Hello, Backing up a partition on a Linux 2.2 kernel server gives me the following output on nearly every backups: FAILED AND STRANGE DUMP DETAILS: /-- analgesix /home lev 1 FAILED [/sbin/dump returned 3] sendbackup: start [analgesix:/home level 1] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | DUMP: Date of this level 1 dump: Thu Jul 11 00:20:38 2002 | DUMP: Date of last level 0 dump: Tue Jul 2 00:18:55 2002 | DUMP: Dumping /dev/hdc1 (/data/00) to standard output | DUMP: Added inode 7 to exclude list (resize inode) | DUMP: Label: none | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 39487 tape blocks. | DUMP: Volume 1 started with block 1 at: Thu Jul 11 00:20:56 2002 | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: short read error from /dev/hdc1: [block -909618816]: count=4096, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/hdc1: [sector -909618816]: count=512, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/hdc1: [sector -909618815]: count=512, got=0 ... ... ? DUMP: short read error from /dev/hdc1: [sector -2120113777]: count=512, got=0 ? DUMP: bread: lseek fails ? DUMP: short read error from /dev/hdc1: [block -909618816]: count=2048, got=0 ? DUMP: More than 32 block read errors from 134600080 ? DUMP: This is an unrecoverable error. ? DUMP: fopen on /dev/tty fails: No such device or address | DUMP: The ENTIRE dump is aborted. sendbackup: error [/sbin/dump returned 3] \Ä Does anyone know what the problem could be ? Thanks Regards
