no different dumpsize between level 0 and 1

Here an abstract of tho mail reports amanda send after a backup. The first time it makes dumplevel 0 of backupdisk. The second time it makes dumplevel 1 of the same disk. Why differs the size that less? Looks more like if both were complete backups. Someone can help? -backupdisk 0 20166900 2016690

Re: no different dumpsize between level 0 and 1

On Thu, Feb 03, 2005 at 01:17:10PM +0100, Rainer Hackel wrote: > Here an abstract of tho mail reports amanda send after a backup. The first > time it makes dumplevel 0 of backupdisk. The second time it makes dumplevel > 1 of the same disk. Why differs the size that less? Looks more like if both > w

Re: barcodes in Exabyte 230D

thank you for your advice to reinstall amanda using the tarball. The installation was simple. I use chg-zd-mtx as the recommanded changer with barcodereader, both in rpm-amanda and in tar-amanda, but still without success. But suddenly I ran into another problem. I could unload or eject a tape from

AW: no different dumpsize between level 0 and 1

Backupdisk was just a dummy-name. The true name is an other. It's a smb-share with office-files on it. I'm sure the users did not touch them all... Perhaps any running process??? Other smb-shares from the same hosts don't have this problem. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED]

mounting/identifying a new tape drive

Hello, I have a Solaris 9 box and we bought a new tape drive model Certance LTO-2. Currently, I am trying to identify the tape drive using amtapetype command but it does not work. Let me go a step back and describe what I did so far. I connected the new tape drive to our Solaris 9 server and I r

Re: barcodes in Exabyte 230D

On Thursday 03 February 2005 10:24, Wim Zwitser wrote: >thank you for your advice to reinstall amanda using the tarball. >The installation was simple. >I use chg-zd-mtx as the recommanded changer with barcodereader, >both in rpm-amanda and in tar-amanda, but still without success. > >But suddenly I

Re: AW: no different dumpsize between level 0 and 1

On Thursday 03 February 2005 10:27, Rainer Hackel wrote: >Backupdisk was just a dummy-name. The true name is an other. It's a >smb-share with office-files on it. I'm sure the users did not touch > them all... Perhaps any running process??? Other smb-shares from > the same hosts don't have this prob

Re: mounting/identifying a new tape drive

On Thu, Feb 03, 2005 at 11:53:36AM -0500, Gil Naveh wrote: > Hello, > > I have a Solaris 9 box and we bought a new tape drive model Certance LTO-2. > Currently, I am trying to identify the tape drive using amtapetype command > but it does not work. > > > Let me go a step back and describe what I

/etc/stinit.def file for the Exabyte VXA-2 tape drive

I need to properly create an /etc/stinit.def file for the Exabyte VXA-2 tape drive for purposes of initializing the tape drive using mt-st prior to usage by AMANDA.   Currently, AMANDA cannot write to the tape drive since it is initialized incorrectly.  A first attempt at the initialization loo

Re: mounting/identifying a new tape drive

On Thu, Feb 03, 2005 at 12:47:34PM -0500, Jon LaBadie wrote: > rm -f /dev/rmt/* > devfsadm -c tape Does that do (the tape-related subset of) the same thing as a reconfiguration boot, i.e. with "-r"? -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The anim

Re: mounting/identifying a new tape drive

On Thu, Feb 03, 2005 at 01:18:44PM -0500, Eric Siegerman wrote: > On Thu, Feb 03, 2005 at 12:47:34PM -0500, Jon LaBadie wrote: > > rm -f /dev/rmt/* > > devfsadm -c tape > > Does that do (the tape-related subset of) the same thing as a > reconfiguration boot, i.e. with "-r"? Eric, I believe

Re: no different dumpsize between level 0 and 1

Jon LaBadie <[EMAIL PROTECTED]> writes: > On Thu, Feb 03, 2005 at 01:17:10PM +0100, Rainer Hackel wrote: >> Here an abstract of tho mail reports amanda send after a backup. The first >> time it makes dumplevel 0 of backupdisk. The second time it makes dumplevel >> 1 of the same disk. Why differs t

Re: mounting/identifying a new tape drive

On Thu, Feb 03, 2005 at 12:47:34PM -0500, Jon LaBadie wrote: > On Thu, Feb 03, 2005 at 11:53:36AM -0500, Gil Naveh wrote: > > Hello, > > > > I have a Solaris 9 box and we bought a new tape drive model Certance LTO-2. > > Currently, I am trying to identify the tape drive using amtapetype command >

Re: Running multiple instances of amanda

I got a little further on my attempts to run backups via the new install. It appears to backup using the new binary except that the changes to /etc/inetd.conf seem to have caused some of the backups not to work. For some reason, amcheck is reporting that there is no .amanda-exclude file on each ent

Re: Running multiple instances of amanda

On Thu, Feb 03, 2005 at 01:59:04PM -0500, Vicki Stanfield wrote: > I got a little further on my attempts to run backups via the new > install. It appears to backup using the new binary except that the changes to > /etc/inetd.conf seem to have caused some of the backups not to work. > For some reaso

RE: mounting/identifying a new tape drive

Great, Thanks much for the help :) According to the manufacture I have to add in the file st.conf the tape device configuration and then reboot -r. But do I realy have to reboot -r? or does typing "devfsadm -c tape" would be enough? After modifying the file dt.conf according to manufacture spec I

VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]

I am getting scsi sense errors using the new drive about 1-2 minutes after an amdump or amflush starts.  Below are the reommendations from Exabyte tech support to fix it. Any comments ?  Forwarded Message From: James D. Freels <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED]

Re: mounting/identifying a new tape drive

On Thu, Feb 03, 2005 at 03:02:36PM -0500, Gil Naveh wrote: > but I don't think it identified the new tape drive... > >mt -f /dev/rmt/0n > I got: > >/dev/rmt/0n: no tape loaded or drive offline On the contrary, I think that means your devfsadm command *did* work. You're now getting a tape-specific

Re: configure for amanda server and client coordinations

On Thu, 3 Feb 2005 at 12:50pm, Nina Pham wrote > Please help? Nina, I think that you would greatly benefit from a read of "the chapter" on how to set up Amanda. A lot of your questions are on the basic level that would be well served by this exercise. You can find the chapter at

Re: VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]

On Thu, Feb 03, 2005 at 03:03:22PM -0500, James D. Freels wrote: > Here is what [drive vendor's Tech Support said] is needed: > > 1) need a separate scsi chain; they said I already have too many scsi > devices on this chain to make it reliable. See recent threads re. SCSI cables, bus lengths, etc

RE: mounting/identifying a new tape drive

YE, thank you Eric,Jon, and Brian :) It's the first time I'm doing it so I needed some help. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Eric Siegerman Sent: Thursday, February 03, 2005 4:03 PM To: Amanda-Users Subject: Re: mounting/identifying

Re: barcodes in Exabyte 230D

thank you Nick, that's the solution. mtx is working properly again. Now I can return to the main experiment: try to read barcodes! As far as I understand the documentation and the several reactions this way is not yet very clear. I feel myself a kind of explorer:), but I am still open for a good su

Re: VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]

No.  It should be still Alpha compatible.  The problem is that the firmware upgrade utilities for Linux are binary-only so I cannot compile them for the alpha nor run them on the alpha. On Thu, 2005-02-03 at 16:19 -0500, Eric Siegerman wrote: On Thu, Feb 03, 2005 at 03:03:22PM -0500, James

Re: configure for amanda server and client coordinations

On Thu, Feb 03, 2005 at 12:50:55PM -0800, Nina Pham wrote: > Please let me setup the scenerio first for 2 unix machines. The amanda > server machine(amserver) is running redhat linux 9, the amanda > client(amclient) machine is running FC2. In addition to serve the client > machine, amserver also

Amrecover problems

Has anyone ran across a issue while running amrecover where the file that is requested and extracted from recover is not at all the file you ended up with. The filename/extension are correct but the actual content is not at all what the original was. So to illustrate what I am trying to say here is

Re: configure for amanda server and client coordinations

On Thursday 03 February 2005 15:50, Nina Pham wrote: >Please let me setup the scenerio first for 2 unix machines. The > amanda server machine(amserver) is running redhat linux 9, the > amanda client(amclient) machine is running FC2. In addition to > serve the client machine, amserver also backups s

Re: barcodes in Exabyte 230D

On Thursday 03 February 2005 16:50, Wim Zwitser wrote: >thank you Nick, that's the solution. >mtx is working properly again. > Thanks for echoing that message, Wim. I for some reason didn't get a copy. >Now I can return to the main experiment: try to read barcodes! >As far as I understand the do

Re: VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]

On Thursday 03 February 2005 17:49, James D. Freels wrote: >No. It should be still Alpha compatible. The problem is that the >firmware upgrade utilities >for Linux are binary-only so I cannot compile them for the alpha nor > run them on the alpha. Are you saying its not a case of dd if=inputfile

Re: VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]

--On Thursday, February 03, 2005 15:03 -0500 "James D. Freels" <[EMAIL PROTECTED]> wrote: I am getting scsi sense errors using the new drive about 1-2 minutes after an amdump or amflush starts. Below are the reommendations from Exabyte tech support to fix it. I seem to remember doing FW upgrade