Re: AMLABEL
Jon LaBadie wrote: With the ultrium it is less important about considering HW or SW compression. But be aware that on Solaris whether HW compression is turned on or not is determined by the device you choose. You will find lots of /dev/rmt/0xyz devices. The xyz determines the properties of the device the driver will set upon opening it. Don't be fooled into assumptions about the various devices. The c device is listed as compressed. But that is the conventional use. There is no certainty that it turns compression on for every device, or that devices without the c are no compression. You will even have a c device for drives that are not capable of HW compression ;-) Only way to tell is check the docs for the drive and settings for the driver. And then I'd check it if I could. Indeed. And check the file st.init, where the letters get their meaning. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: client version varies from server
On Mon, 7 Feb 2005 22:01:32 -0500 Gene Heskett [EMAIL PROTECTED] wrote: On Monday 07 February 2005 14:40, Don Carlton wrote: On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7 and on the client I'm running amanda-client-2.4.4p1-0.3E (RedHat ES). I keep getting selfcheck request timed out when I try to run amcheck on the server? Is this caused by the different versions?? I've never seen that be the case. Normally when you get a selfcheck request timeout, something has gone gaga in the networking or the server setup. Is this a new install? The client is a new install. -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: client version varies from server
On Mon, 7 Feb 2005 15:46:20 -0600 [EMAIL PROTECTED] wrote: The message indicates that the self-check portion of the amcheck command timed out while communicating with either itself or the client. Make sure that xinetd configuration files are set up correctly to respond to the Amanda commands sent over the Amanda UDP port. 1. Check your /etc/services file on each machine to ensure that you have the amanda UDP 10080 service defined in the file. Did this already everything looks fine. I set it up just like another client that works to this server. 2. Check your /etc/inetd.conf file or /etc/xinetd.d file(s) have the appropriate entries for amanda (I use Amanda at work on a Tru64 UNIX system and my home server is Fedora Core 3, your mileage may vary) I also did this already, again everthing looks good. 3. Check the contents of the /tmp/amanda debug files from the amcheck from the server's debug file: amcheck: debug 1 pid 26575 ruid 33 euid 0 start time Mon Feb 7 21:11:33 2005 amcheck: dgram_bind: socket bound to 0.0.0.0.932 amcheck: pid 26575 finish time Mon Feb 7 21:12:03 2005 I get the following in the client's secure log file? Feb 7 21:13:32 clients name xinetd[1338]: START: amanda pid=17335 from=server ip I substituted client name and server ip for the actual server and client operation to get more detailed explanations of why the operation is failing. Best wishes, Don Donald L. (Don) Ritchey Information Technology Exelon Corporation -Original Message- From: Don Carlton [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 1:41 PM To: amanda-users@amanda.org Subject: client version varies from server On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7 and on the client I'm running amanda-client-2.4.4p1-0.3E (RedHat ES). I keep getting selfcheck request timed out when I try to run amcheck on the server? Is this caused by the different versions?? This e-mail and any of its attachments may contain Exelon Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Exelon Corporation family of Companies. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You.
#amanda freenode irc channel
Hi all, Who hangs aroung here, and what are your nicks? I'm G2 -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1467 624141 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E [EMAIL PROTECTED] Open Source. Open Solutions(tm). http://www.suretecsystems.com/
Re: client version varies from server
On Tuesday 08 February 2005 06:25, Don Carlton wrote: On Mon, 7 Feb 2005 22:01:32 -0500 Gene Heskett [EMAIL PROTECTED] wrote: On Monday 07 February 2005 14:40, Don Carlton wrote: On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7 and on the client I'm running amanda-client-2.4.4p1-0.3E (RedHat ES). I keep getting selfcheck request timed out when I try to run amcheck on the server? Is this caused by the different versions?? I've never seen that be the case. Normally when you get a selfcheck request timeout, something has gone gaga in the networking or the server setup. Is this a new install? The client is a new install. Does it have the proper ~/.amandahosts file? And, is the user:group defined for the client the same as for the server? -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved. -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL
And assuming that c does enable compression on your solaris system the difference (at least on my drives) between h and u is also the HW compression, though both are highest density (on devices where its offered). On Mon, Feb 07, 2005 at 10:48:27PM -0500, Jon LaBadie wrote: On Mon, Feb 07, 2005 at 10:06:09PM -0500, Gene Heskett wrote: On Monday 07 February 2005 18:31, Paul Bijnens wrote: Gil Naveh wrote: Gene - thanks for trying to help, Currently the only reason that I can think of is that Amanda has not read correctly our tape drive so I am re-running #amtapetype -f /dev/rmt/0n Add an estimate value! And it takes about 5 hours only. Without an estimate it takes a week or so. Like this: amtapetype -f /dev/rmt/0n -e 200g On the other hand, writing a few bytes is enough to see it the drive works. About the problem: you did specify that device in your amanda.conf ? (I believe that was what Gene was hinting about.) Chuckle, yup. Sometimes I get my tongue tangled up with my eyeteeth, and can't see what I'm writing... Corrections in that case are always welcome. :-) With the ultrium it is less important about considering HW or SW compression. But be aware that on Solaris whether HW compression is turned on or not is determined by the device you choose. You will find lots of /dev/rmt/0xyz devices. The xyz determines the properties of the device the driver will set upon opening it. Don't be fooled into assumptions about the various devices. The c device is listed as compressed. But that is the conventional use. There is no certainty that it turns compression on for every device, or that devices without the c are no compression. You will even have a c device for drives that are not capable of HW compression ;-) Only way to tell is check the docs for the drive and settings for the driver. And then I'd check it if I could. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) --- 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
RE: AMLABEL - might be a bug in amtapetype
Hello and thanks,
So it turn out that my suspicious were correct.
After rerunning amtapetype twice on our Solaris 9 server I got the
configuration for Ultrium2-LTO slightly different and with the new results
amlabel worked fine :)
In the first run I got the following result:
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 207465 mbytes
filemark 939 kbytes
speed 17489 kps
}
But Amanda could not identify my tape drive.
In the second run I got the following results:
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 206819 mbytes
filemark 918 kbytes
speed 17477 kps
}
which worked fine.
Anyway, I'll publish the results for the Ultrium-LTO2 tape drive on Amanda's
website.
Thx,
gil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon LaBadie
Sent: Monday, February 07, 2005 10:48 PM
To: amanda-users@amanda.org
Subject: Re: AMLABEL
On Mon, Feb 07, 2005 at 10:06:09PM -0500, Gene Heskett wrote:
On Monday 07 February 2005 18:31, Paul Bijnens wrote:
Gil Naveh wrote:
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has
not read correctly our tape drive so I am re-running
#amtapetype -f /dev/rmt/0n
Add an estimate value! And it takes about 5 hours only. Without
an estimate it takes a week or so. Like this:
amtapetype -f /dev/rmt/0n -e 200g
On the other hand, writing a few bytes is enough to see it the drive
works.
About the problem: you did specify that device in your amanda.conf ?
(I believe that was what Gene was hinting about.)
Chuckle, yup. Sometimes I get my tongue tangled up with my eyeteeth,
and can't see what I'm writing... Corrections in that case are
always welcome. :-)
With the ultrium it is less important about considering HW or SW
compression. But be aware that on Solaris whether HW compression
is turned on or not is determined by the device you choose. You
will find lots of /dev/rmt/0xyz devices. The xyz determines
the properties of the device the driver will set upon opening it.
Don't be fooled into assumptions about the various devices. The
c device is listed as compressed. But that is the conventional
use. There is no certainty that it turns compression on for every
device, or that devices without the c are no compression. You
will even have a c device for drives that are not capable of
HW compression ;-) Only way to tell is check the docs for the
drive and settings for the driver. And then I'd check it if I
could.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: AMLABEL - might be a bug in amtapetype
The issue I had was that the first time I run amtapetype the result was a
little off.
Which was painful because it takes a few hours to run it.
yet, it might not be a bug - the reason I put it in the subject was that
people would notice it.
Thx,
gil
-Original Message-
From: Paul Bijnens [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 08, 2005 9:27 AM
To: Gil Naveh
Cc: amanda-users@amanda.org
Subject: Re: AMLABEL - might be a bug in amtapetype
Gil Naveh wrote:
Hello and thanks,
So it turn out that my suspicious were correct.
Which suspicions?
After rerunning amtapetype twice on our Solaris 9 server I got the
configuration for Ultrium2-LTO slightly different and with the new results
amlabel worked fine :)
In the first run I got the following result:
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 207465 mbytes
filemark 939 kbytes
speed 17489 kps
}
But Amanda could not identify my tape drive.
In the second run I got the following results:
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 206819 mbytes
filemark 918 kbytes
speed 17477 kps
}
which worked fine.
Anyway, I'll publish the results for the Ultrium-LTO2 tape drive on
Amanda's
website.
And what kind of bug have you found, as the subject seems to imply?
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: client version varies from server
It looks like it might be a firewall issue on the server? Does anyone know what the minimum server rules and client rules would be in iptables/ipchains? On Tue, 8 Feb 2005 07:44:25 -0500 Gene Heskett [EMAIL PROTECTED] wrote: On Tuesday 08 February 2005 06:25, Don Carlton wrote: On Mon, 7 Feb 2005 22:01:32 -0500 Gene Heskett [EMAIL PROTECTED] wrote: On Monday 07 February 2005 14:40, Don Carlton wrote: On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7 and on the client I'm running amanda-client-2.4.4p1-0.3E (RedHat ES). I keep getting selfcheck request timed out when I try to run amcheck on the server? Is this caused by the different versions?? I've never seen that be the case. Normally when you get a selfcheck request timeout, something has gone gaga in the networking or the server setup. Is this a new install? The client is a new install. Does it have the proper ~/.amandahosts file? And, is the user:group defined for the client the same as for the server? -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved. -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL - might be a bug in amtapetype
Gil Naveh wrote: The issue I had was that the first time I run amtapetype the result was a little off. Which was painful because it takes a few hours to run it. yet, it might not be a bug - the reason I put it in the subject was that people would notice it. No, it's not a bug. That's real life with tapes. Not all tapes have exactly the same length. Even the temperature has a measurable influence on tapecapacity. Also when writing to tape, the drive verifies the data, and rewrites any block that contains an uncorrectable error, up to a certain time (15 sometimes). These soft errors also take up tape capacity. Furthermore, if the drive has to pause, because the data is not delivered fast enough to the drive, it takes a few inches to stop the tape, rewind and restart again, leaving a little gap between the blocks again. That's why you should specify a little lower value than the one that amtapetype measured. All that said, when using an LTO drive, you may have hardware compression enabled anyway, because the hw compr algorithm in those drives does not expand uncompressable data. Which gives you the opportunity to mix hardware and software compression, using whatever method for each host/disk that fits best (slow host= only hardware compression, slow network = software compression on client etc.) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
amdump: timeout
Hi all, amcheck detects no problem on the server and on client maxwell. But amdump stops after a timeout: FAILURE AND STRANGE DUMP SUMMARY: maxwell/data/backup/Sat lev 0 FAILED [Estimate timeout from maxwell] What can this be? Thank you, Wim Zwitser
Re: VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]
On Mon, Feb 07, 2005 at 04:41:17PM -0500, Jon LaBadie wrote: Can on look at the device connectors, or better yet, the external connectors, and tell if a device is LVD or SE? Or does one have to check the HW doc? I have no idea. Sorry. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The animal that coils in a circle is the serpent; that's why so many cults and myths of the serpent exist, because it's hard to represent the return of the sun by the coiling of a hippopotamus. - Umberto Eco, Foucault's Pendulum
Re: client version varies from server
On Tuesday 08 February 2005 10:00, Don Carlton wrote: It looks like it might be a firewall issue on the server? Does anyone know what the minimum server rules and client rules would be in iptables/ipchains? I believe all that is covered in the docs, and of late there is a special iptables module just for amanda if you are running on linux, 2.6 series kernels newer than 2.6.8-1 have it I think. But don't make me lay my hand on the good book to say that, I could be wrong as I've not had to contend with that here, everything I'm doing is behind the firewall. On Tue, 8 Feb 2005 07:44:25 -0500 Gene Heskett [EMAIL PROTECTED] wrote: On Tuesday 08 February 2005 06:25, Don Carlton wrote: On Mon, 7 Feb 2005 22:01:32 -0500 Gene Heskett [EMAIL PROTECTED] wrote: On Monday 07 February 2005 14:40, Don Carlton wrote: On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7 and on the client I'm running amanda-client-2.4.4p1-0.3E (RedHat ES). I keep getting selfcheck request timed out when I try to run amcheck on the server? Is this caused by the different versions?? I've never seen that be the case. Normally when you get a selfcheck request timeout, something has gone gaga in the networking or the server setup. Is this a new install? The client is a new install. Does it have the proper ~/.amandahosts file? And, is the user:group defined for the client the same as for the server? -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved. -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved. -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL - might be a bug in amtapetype
On Tue, Feb 08, 2005 at 09:47:17AM -0500, Gil Naveh wrote: The issue I had was that the first time I run amtapetype the result was a little off. I would not consider them different at all. capacity, differed by 0.31 percent filemark, differed by 3.41 percent (and only 0.00045% of capacity) speed,differed by 0.06 percent -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL
On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote: Jon LaBadie wrote: With the ultrium it is less important about considering HW or SW compression. But be aware that on Solaris whether HW compression is turned on or not is determined by the device you choose. You will find lots of /dev/rmt/0xyz devices. The xyz determines the properties of the device the driver will set upon opening it. Don't be fooled into assumptions about the various devices. The c device is listed as compressed. But that is the conventional use. There is no certainty that it turns compression on for every device, or that devices without the c are no compression. You will even have a c device for drives that are not capable of HW compression ;-) Only way to tell is check the docs for the drive and settings for the driver. And then I'd check it if I could. Indeed. And check the file st.init, where the letters get their meaning. Paul, I'm unfamiliar with the file st.init. Nor do I find one on my system. Did you mean the st.conf file in /kernel/drv? If the st.conf file, I don't find an entries for any lto's I recognize. One poster said it was builtin to the driver, another said they had to edit the file and add an entry. The drive docs would probably still be needed to interpret the entry. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL - might be a bug in amtapetype
On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote: All that said, when using an LTO drive, you may have hardware compression enabled anyway, because the hw compr algorithm in those drives does not expand uncompressable data. Maybe the amtapetype message should be revised to something like: hardware compression off (or drive uses a dynamic compression algorithm) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amdump: timeout
On Tuesday 08 February 2005 10:44, Wim Zwitser wrote: Hi all, amcheck detects no problem on the server and on client maxwell. But amdump stops after a timeout: FAILURE AND STRANGE DUMP SUMMARY: maxwell/data/backup/Sat lev 0 FAILED [Estimate timeout from maxwell] What can this be? An indication that maxwell is too slow, and you need to increase 'etimeout' in the amanda.conf? In which event, dtimeout may also need an increase from the default 10 minutes (600 seconds). Or that the DLE's are too big and should be further divided into smaller pieces maybe? This last would shrink the estimate times per DLE. Personally, I'd like to see, just because data grows forever, an increase in these defaults, I think our average system has about outgrown them. Storage capacities of the commodity drives of today have grown at 4x the clock speeds of the cpu managing them in the last 5 years. Thank you, Wim Zwitser -- 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) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL - might be a bug in amtapetype
Jon LaBadie wrote: On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote: All that said, when using an LTO drive, you may have hardware compression enabled anyway, because the hw compr algorithm in those drives does not expand uncompressable data. Maybe the amtapetype message should be revised to something like: hardware compression off (or drive uses a dynamic compression algorithm) Actually the message is still correct. amtapetype does detect if hw compr is enabled. And you would notice the effect if you wrote without software compression. The fact that the algorithm does not expand data is something else. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: AMLABEL - might be a bug in amtapetype
On Tue, Feb 08, 2005 at 05:53:43PM +0100, Paul Bijnens wrote: Jon LaBadie wrote: On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote: All that said, when using an LTO drive, you may have hardware compression enabled anyway, because the hw compr algorithm in those drives does not expand uncompressable data. Maybe the amtapetype message should be revised to something like: hardware compression off (or drive uses a dynamic compression algorithm) Actually the message is still correct. amtapetype does detect if hw compr is enabled. And you would notice the effect if you wrote without software compression. The fact that the algorithm does not expand data is something else. My misreading of your statement. I missed the when using an LTO drive and thought you meant hardware compression might have been on when amtapetype was run but could have been fooled. Sorry bout dat. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amdump: timeout
Wim Zwitser wrote: FAILURE AND STRANGE DUMP SUMMARY: maxwell/data/backup/Sat lev 0 FAILED [Estimate timeout from maxwell] What can this be? Parameter etimeout in amanda.conf? To see how large to set it to, have a look on the client maxwell in the debug files /tmp/amanda/sendsize.DATATIME.debug and see how long the estimate did take. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Amanda security with Kerberos
hi, I am a little confused regarding adding security to Amanda. In the past I posted a question regarding adding security to Amanda - We have a Solaris 9 machine which is Amanda server and a remote Solaris 9 machine which is Amanda client. We need the data that is transferring from the client to the server be secure. People have kindly answered my question but I am still confused. Some have suggested to use sftp or ssh - bring those files to the server and then backing it up locally. However, by implementing this technique I am over loading the network - because I have to ssh or sftp all files daily instead of letting Amanda get only the changes (level 0,1 etc). But is there a way to implement ssh/sftp with Amanda? Anyway I am trying to implement Kerberos and I have a few questions about it. I am trying to follow the documentation in Amanda for kerberos - so far I downloaded the file amanda-krb4-2.4.0p1.tar.gz - I unzipped it and tared it (tar xvf). Yet I don't know what the next step should be - configure+make??? Additionally the KERBEROS doc for Amanda under the INSTALLATION section says: 2. INSTALLATION The kerberized Amanda service uses a different port on the client hosts. The /etc/services line is: kamanda 10081/udp Then what should be the host on the server site? Finally how can I test that Kerberos encryption works with Amanda? Please note that our Amanda server and client are Solaris 9 boxes but in the future we might implement it on Win boxes (is it feasible to implement Kerberos on Win box?) Thanks much, gil __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail
Re: Amanda security with Kerberos
On Tue, Feb 08, 2005 at 12:05:06PM -0800, gil naveh enlightened us: I am a little confused regarding adding security to Amanda. In the past I posted a question regarding adding security to Amanda - We have a Solaris 9 machine which is Amanda server and a remote Solaris 9 machine which is Amanda client. We need the data that is transferring from the client to the server be secure. People have kindly answered my question but I am still confused. Some have suggested to use sftp or ssh - bring those files to the server and then backing it up locally. However, by implementing this technique I am over loading the network - because I have to ssh or sftp all files daily instead of letting Amanda get only the changes (level 0,1 etc). But is there a way to implement ssh/sftp with Amanda? Anyway I am trying to implement Kerberos and I have a few questions about it. I am trying to follow the documentation in Amanda for kerberos - so far I downloaded the file amanda-krb4-2.4.0p1.tar.gz - I unzipped it and tared it (tar xvf). Yet I don't know what the next step should be - configure+make??? Additionally the KERBEROS doc for Amanda under the INSTALLATION section says: 2. INSTALLATION The kerberized Amanda service uses a different port on the client hosts. The /etc/services line is: kamanda 10081/udp Then what should be the host on the server site? Finally how can I test that Kerberos encryption works with Amanda? Please note that our Amanda server and client are Solaris 9 boxes but in the future we might implement it on Win boxes (is it feasible to implement Kerberos on Win box?) As far as I know, that only works with Kerberos 4, and I don't think much stuff uses v4 anymore. You might take a look at http://security.uchicago.edu/tools/gpg-amanda/ Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpNojKfU08Wh.pgp Description: PGP signature
Amanda security +Kerberos
hi, I am a little confused regarding adding security to Amanda. In the past I posted a question regarding adding security to Amanda - We have a Solaris 9 machine which is Amanda server and a remote Solaris 9 machine which is Amanda client. We need the data that is transferring from the client to the server be secure. People have kindly answered my question but I am still confused. Some have suggested to use sftp or ssh - bring those files to the server and then backing it up locally. However, by implementing this technique I am over loading the network - because I have to ssh or sftp all files daily instead of letting Amanda get only the changes (level 0,1 etc). But is there a way to implement ssh/sftp with Amanda? Anyway I am trying to implement Kerberos and I have a few questions about it. I am trying to follow the documentation in Amanda for kerberos - so far I downloaded the file amanda-krb4-2.4.0p1.tar.gz - I unzipped it and tared it (tar xvf). Yet I don't know what the next step should be - configure+make??? Additionally the KERBEROS doc for Amanda under the INSTALLATION section says: 2. INSTALLATION The kerberized Amanda service uses a different port on the client hosts. The /etc/services line is: kamanda 10081/udp Then what should be the host on the server site? Finally how can I test that Kerberos encryption works with Amanda? Please note that our Amanda server and client are Solaris 9 boxes but in the future we might implement it on Win boxes (is it feasible to implement Kerberos on Win box?) Thanks much, gil
