Re: very large dumps in holding area
Alexander Jolk wrote: Vicki Stanfield wrote: I have searched the list archives and don't see a way (using GNU mt 2.4.2) to permanently disable hardware compression. I thought I had seen a post on it fairly recently, but I didn't find it with my search. I see the mt option defcompression, but that apparently isn't supported in my version of mt. There seem to be a few different versions of mt, with slightly different syntax. Mine uses `mt datcompression 0', other, as you say, `defcompression', and there also seems to be a version that uses plain `compression'. You are on Linux, or something else? Alex I am on Debian Woody (Linux). The version I have doesn't seem to support the defcompression or the compression options, so I am unsure how to make the change permanent. In the meantime, I am tracking down what has made the dumps I mentioned so large. Hopefully, I will be able to split them up. Vicki
slightly more secure...
I would like to add an additional level of authentication to AMANDA. I really don't want to setup kerberos, but want something to keep someone from hacking into one of our internal machines, taking over the amanda servers IP and backing up one of the other machines. Also, I want it to be simple to setup. I know it is a longshot that it would ever happen, but that is what I have been asked to protect us from.
Re: mail.vh.org is re-sending old mail to amanda-users list
On Fri, 22 Apr 2005, Mitch Collinsworth wrote: Todd, mail.vh.org is re-sending old messages (from earlier today) to the amanda-users mailing list. Example below. It should probably be blocked from posting until this is fixed. vh.org postmaster, please fix your system. My apologies, due to an IO error (Incompetent Operator) this day's worth of messages were blasted to the mailing list, among others. System fixed, user chastised, wet newspaper applied with force. Thanks, Bill Carlson -- Systems Administrator[EMAIL PROTECTED] | Anything is possible, Virtual Hospital http://www.vh.org/ | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. |
mail.vh.org is re-sending old mail to amanda-users list
Todd, mail.vh.org is re-sending old messages (from earlier today) to the amanda-users mailing list. Example below. It should probably be blocked from posting until this is fixed. vh.org postmaster, please fix your system. -Mitch -- Forwarded message -- Return-Path: [EMAIL PROTECTED] Received: from mercury.ccmr.cornell.edu [128.84.231.97] by twin.ccmr.cornell.edu with POP3 (fetchmail-6.2.1) for [EMAIL PROTECTED] (single-drop); Fri, 22 Apr 2005 17:01:01 -0400 (EDT) Received: from guinness.omniscient.com (guinness.omniscient.com [64.134.101.78]) by mercury.ccmr.cornell.edu (8.13.1/8.12.10) with ESMTP id j3MKweY8010571 for [EMAIL PROTECTED]; Fri, 22 Apr 2005 16:58:40 -0400 Received: from guinness.omniscient.com (localhost [127.0.0.1]) by guinness.omniscient.com (8.13.3/8.13.1) with ESMTP id j3MKwcgb020690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Apr 2005 16:58:38 -0400 (EDT) Received: from localhost ([EMAIL PROTECTED]) by guinness.omniscient.com (8.13.3/8.12.11/Submit) with SMTP id j3MKwcws000871; Fri, 22 Apr 2005 16:58:38 -0400 (EDT) Received: by guinness.omniscient.com (bulk_mailer v1.13); Fri, 22 Apr 2005 16:47:40 -0400 Received: from guinness.omniscient.com (localhost [127.0.0.1]) by guinness.omniscient.com (8.13.3/8.13.1) with ESMTP id j3MKTGfl024158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Apr 2005 16:29:17 -0400 (EDT) Received: (from [EMAIL PROTECTED]) by guinness.omniscient.com (8.13.3/8.12.11/Submit) id j3MKTFfB006444; Fri, 22 Apr 2005 16:29:15 -0400 (EDT) X-Authentication-Warning: guinness.omniscient.com: majordom set sender to [EMAIL PROTECTED] using -f Received: from sapphire.omniscient.com (sapphire.omniscient.com [64.134.101.71]) by guinness.omniscient.com (8.13.3/8.13.1) with ESMTP id j3MKTCE3005050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for amanda-users@amanda.org; Fri, 22 Apr 2005 16:29:12 -0400 (EDT) Received: from mail.vh.org (mail.vh.org [129.255.233.40]) by sapphire.omniscient.com (8.13.1/8.13.1) with SMTP id j3MKTAhG015538 for amanda-users@amanda.org; Fri, 22 Apr 2005 16:29:10 -0400 (EDT) Received: (qmail 2652 invoked by uid 501); 22 Apr 2005 20:28:54 - MBOX-Line: From [EMAIL PROTECTED] Fri Apr 22 15:28:54 2005 Received: (qmail 22870 invoked by uid 18); 22 Apr 2005 19:48:55 - Received: from [EMAIL PROTECTED] by mail by uid 131 with qmail-scanner-1.20rc4 (clamuko: 0.80 Clear:RC:0:. Processed in 0.052428 secs); 22 Apr 2005 19:48:55 - Received: from guinness.omniscient.com (64.134.101.78) by mail.vh.org with SMTP; 22 Apr 2005 19:48:55 - Received: from guinness.omniscient.com (localhost [127.0.0.1]) by guinness.omniscient.com (8.13.3/8.13.1) with ESMTP id j3MJms5R026943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Apr 2005 15:48:54 -0400 (EDT) Received: from localhost ([EMAIL PROTECTED]) by guinness.omniscient.com (8.13.3/8.12.11/Submit) with SMTP id j3MJmph5013477; Fri, 22 Apr 2005 15:48:51 -0400 (EDT) Received: by guinness.omniscient.com (bulk_mailer v1.13); Fri, 22 Apr 2005 15:46:55 -0400 Received: from guinness.omniscient.com (localhost [127.0.0.1]) by guinness.omniscient.com (8.13.3/8.13.1) with ESMTP id j3MJktuc020306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Apr 2005 15:46:55 -0400 (EDT) Received: (from [EMAIL PROTECTED]) by guinness.omniscient.com (8.13.3/8.12.11/Submit) id j3MJktwA005561; Fri, 22 Apr 2005 15:46:55 -0400 (EDT) X-Authentication-Warning: guinness.omniscient.com: majordom set sender to [EMAIL PROTECTED] using -f Received: from sapphire.omniscient.com (sapphire.omniscient.com [64.134.101.71]) by guinness.omniscient.com (8.13.3/8.13.1) with ESMTP id j3MJkscn021387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for amanda-users@amanda.org; Fri, 22 Apr 2005 15:46:54 -0400 (EDT) Received: from loncoche.terra.com.br (loncoche.terra.com.br [200.154.55.229]) by sapphire.omniscient.com (8.13.1/8.13.1) with ESMTP id j3MJkqeK016062 for amanda-users@amanda.org; Fri, 22 Apr 2005 15:46:53 -0400 (EDT) Received: from estero.terra.com.br (estero.terra.com.br [200.154.55.138]) by loncoche.terra.com.br (Postfix) with ESMTP id 6DA4EE78AF6 for amanda-users@amanda.org; Fri, 22 Apr 2005 16:46:46 -0300 (BRT) X-Terra-Karma: 0% X-Terra-Hash: 3f16c97bdda1a80776a43a2705e3fcab Received-SPF: pass (estero.terra.com.br: domain of terra.com.br designates 200.154.55.138 as permitted sender) client-ip=200.154.55.138; [EMAIL PROTECTED]; helo=terra.com.br; Received: from terra.com.br (tupiza.terra.com.br [200.176.3.182]) (authenticated user vlpg) by estero.terra.com.br (Postfix) with ESMTP id 59282728025 for amanda-users@amanda.org; Fri, 22 Apr 2005 16:46:45 -0300 (BRT) Date: Fri, 22 Apr 2005
Amanda security
Hi all, I would like to know if amanda use some kind of crypthography. Do I have some problem of security when I use amrecover from client ? Thanks for the help - Vinicius
Re: Modify Schedule
On Fri, Apr 22, 2005 at 11:35:59AM -0400, Jingchun Chen wrote: Hi There, I plan to change amanda backup schedule due to reduction of the size of the working group. Currently dumpcycle=6Days; runspercycle=3 (runs every other day), using 4 tapes (on disk). I just want to change dumpcycle to one month. Here is the list of changes I think I should do. 1. amanda.conf dumpcycle 30 days runspercycle 15 tapecycle 16 # (15+1) ### Do I need to change this? The backup disk has 200G, that's why the length was set to 48G (200/4). If I change it to 12G (200/16), it's not enough to hold a full dump. Since this is vertual tape, I can probably set to 30G and hope there will be no more than 6 full dump per cycle. define tapetype HARD-DISK { comment Backup to disk - not tape length 48000 mbytes } 2. chg-multi (tapechanger) firstslot 1 lastslot 16 slot 1file:/xxx ... slot 16 file: /xxx 3. Add tape directories T5-T16 on backup disk. 4. cron xxx My questions are: 1. Do I miss anything I should change? 2. When will this change take effect? 3. Will amanda do this transition seamlessly? Depending on where you are in using your tapecycle, it may not start immediately with the new vtape in slot 5. Unlikely there will be 6 full dumps of anything in a month as you have only asked for 'at least 1' a month. But you won't know until you've tried. I suspect leaving the tape size large is not going to be a problem. Monitor the disk usage for a while to be certain. I'd be scared with only 1 tape more than the minimum. Suppose something is 'off-line' the day it is due for a full backup. On the next amdump run, the tape containing your only full dump will be overwritten. Consider the possibility that the DLE is still off-line or an error occurs. You will have no full dump for that DLE. Now you have only incrementals. I'd feel better with 32 tapes or 14 day dumpcycle. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: very large dumps in holding area
Hi, Joshua, on Donnerstag, 21. April 2005 at 19:03 you wrote to amanda-users: JBL OK, so it looks like its time for the amanda and compression lecture. I think this topic should go into the FAQ (where it already is mentioned) and/or into the Top10Questions ... Added this to my list ... thanks, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Modify Schedule
Hi There, I plan to change amanda backup schedule due to reduction of the size of the working group. Currently dumpcycle=6Days; runspercycle=3 (runs every other day), using 4 tapes (on disk). I just want to change dumpcycle to one month. Here is the list of changes I think I should do. 1. amanda.conf dumpcycle 30 days runspercycle 15 tapecycle 16 # (15+1) ### Do I need to change this? The backup disk has 200G, that's why the length was set to 48G (200/4). If I change it to 12G (200/16), it's not enough to hold a full dump. Since this is vertual tape, I can probably set to 30G and hope there will be no more than 6 full dump per cycle. define tapetype HARD-DISK { comment Backup to disk - not tape length 48000 mbytes } 2. chg-multi (tapechanger) firstslot 1 lastslot 16 slot 1file:/xxx ... slot 16 file: /xxx 3. Add tape directories T5-T16 on backup disk. 4. cron xxx My questions are: 1. Do I miss anything I should change? 2. When will this change take effect? 3. Will amanda do this transition seamlessly? Thanks in advance. Jingchun
Re: New Estimate Parameter
Hi, Jim, on Freitag, 22. April 2005 at 19:00 you wrote to amanda-users: JS I was wondering if the new estimate parameter is available in the JS recently released 2.4.5 or if I need to get the 2.4.5b1 from JS sourceforge? This will allow for the calcsize or server estimates. It's in there, yes. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: slightly more secure...
Nods to those smarter than I am, but if that is your specific concern you might do better to just set up arpwatch. It pairs up ipaddresses with the mac address of the card in each machine on your network. After set up it will monitor the network and can email/page you if a different mac address pops up with a different ip address. Best, Mike Brown Mike wrote: I would like to add an additional level of authentication to AMANDA. I really don't want to setup kerberos, but want something to keep someone from hacking into one of our internal machines, taking over the amanda servers IP and backing up one of the other machines. Also, I want it to be simple to setup. I know it is a longshot that it would ever happen, but that is what I have been asked to protect us from.
Amanda ssh
Simple question, can I push amanda over SSH, and If I can, where is the how-to
Re: very large dumps in holding area
Vicki Stanfield wrote: I am on Debian Woody (Linux). The version I have doesn't seem to support the defcompression or the compression options, so I am unsure how to make the change permanent. On my Debian woody system, mt has the `datcompression' option. The associate Debian package is `cpio'. Alex
New Estimate Parameter
I was wondering if the new estimate parameter is available in the recently released 2.4.5 or if I need to get the 2.4.5b1 from sourceforge? This will allow for the calcsize or server estimates. Apologies for the confusion. TIA -- Jim Summers School of Computer Science-University of Oklahoma -