Hi!
Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
There is amtapetype, which will destructively write the tape till it
hits EOT, and will tell you the size it found. See the man page for
running options to help speed it up as its quite slow, doing 2
passes.
SYNOPSIS
amtapetype
Martin Oehler wrote:
Hi!
Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
There is amtapetype, which will destructively write the tape till it
hits EOT, and will tell you the size it found. See the man page for
running options to help speed it up as its quite slow, doing 2
passes.
On Monday 24 November 2003 03:46, Martin Oehler wrote:
Hi!
Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
There is amtapetype, which will destructively write the tape till
it hits EOT, and will tell you the size it found. See the man
page for running options to help speed it up as its quite
On Sun, 23 Nov 2003 at 7:46pm, Kurt Raschke wrote
I've recently begun to have trouble with the Linux system that is my
amanda server...when amdump runs, the load spikes to between 4.00 and
6.00, and the system becomes nearly unresponsive for the duration of
the backup. The server is backing
On Mon, Nov 24, 2003 at 09:46:31AM +0100, Martin Oehler wrote:
Hi!
Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
There is amtapetype, which will destructively write the tape till it
hits EOT, and will tell you the size it found. See the man page for
running options to help speed it
On Mon, Nov 24, 2003 at 10:23:12AM +0100, Paul Bijnens wrote:
Read on a few lines further in the man page. The most important
parameter for speed is the estimated size. It's the stop/start when
writing a filemark that slows down the most. The default estimated
size is 1 Gbyte. Amtapetype
Hello honourable readers of the list,
After some succesfull testing, I wanted to make a run for real. As
recommended in the FAQ I removed:
-curinfo
-any log files from the log directory
-tapelist
-reseted the changer state file
so I run the amcheck on a particular configuration and I
Hi,
I'm having strange problems with the include thingy in an
entry in my disklist:
bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
include ./0*
exclude ./[1-9]*
high-tar
} 1
Looking at what got written to tape (a full backup) I see only
directories (no files at
can someone give me some pointers about accessing my juke box using
mtx? I cannot figure out what device to use.
nwadmin reports the control port at [EMAIL PROTECTED] and the tape device as
/dev/rmt/1hbn , this is a link to :
/devices/[EMAIL PROTECTED],2000/[EMAIL PROTECTED],1/[EMAIL
Hello again,
Oups, forgot to mention one important fact: the gnutar version:
/usr/freeware/bin/tar --version
tar (GNU tar) 1.13.25
* Jean-Francois Malouin [EMAIL PROTECTED] [20031124 12:00]:
Hi,
I'm having strange problems with the include thingy in an
entry in my disklist:
bullcalf
We are building an amanda backup server and have a question regarding
memory requirements. My guess is that Amanda is more processor
intensive than memory intensive. Is this correct? For a dedicated
backup server that won't be doing much of anything else, is 512MB of
memory enough?
Thanks,
Cedric Boudin wrote:
Hello honourable readers of the list,
After some succesfull testing, I wanted to make a run for real. As
recommended in the FAQ I removed:
-curinfo
-any log files from the log directory
-tapelist
-reseted the changer state file
so I run the amcheck on a particular
We are building an amanda backup server and have a question regarding
memory requirements. My guess is that Amanda is more processor
intensive than memory intensive. Is this correct? For a dedicated
backup server that won't be doing much of anything else, is 512MB of
memory enough?
i
Paul Bijnens writes:
Cedric Boudin wrote:
Hello honourable readers of the list,
After some succesfull testing, I wanted to make a run for real. As
recommended in the FAQ I removed:
-curinfo
-any log files from the log directory
-tapelist
-reseted the
On Monday, November 24, 2003, at 01:04 PM, Tom Brown wrote:
We are building an amanda backup server and have a question regarding
memory requirements. My guess is that Amanda is more processor
intensive than memory intensive. Is this correct? For a dedicated
backup server that won't be doing
Remember that Amanda is a driver, a scheduling tool that invokes
tools on each of the amanda clients (except in the case of server
side compression).
Amanda queries each client (possibly having a client on the server
machine), determines answers to various space issues and then issues
commands
* Paul Bijnens [EMAIL PROTECTED] [20031124 13:02]:
Jean-Francois Malouin wrote:
Hi,
I'm having strange problems with the include thingy in an
entry in my disklist:
bullcalf /data/nihpd/nihpd1/data/assembly_0
/data/nihpd/nihpd1/data/assembly {
include ./0*
exclude ./[1-9]*
high-tar
Jon LaBadie wrote:
Might it be a good idea to have amtapetype note too many files
being written during the first phase and taking some action?
Maybe with an option to override the checking.
My idea was to write only one large file in the first pass, just
until it hits end of tape. Then rewind
On Mon, 2003-11-24 at 13:02, Bryan K. Walton wrote:
We are building an amanda backup server and have a question regarding
memory requirements. My guess is that Amanda is more processor
intensive than memory intensive. Is this correct? For a dedicated
backup server that won't be doing much
On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
Hi,
I'm having strange problems with the include thingy in an
entry in my disklist:
bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
include ./0*
exclude ./[1-9]*
high-tar
} 1
On Mon, Nov 24, 2003 at 12:15:26PM -0500, Alastair Neil wrote:
can someone give me some pointers about accessing my juke box using
mtx? I cannot figure out what device to use.
nwadmin reports the control port at [EMAIL PROTECTED] and the tape device as
/dev/rmt/1hbn , this is a link to :
On Mon, 2003-11-24 at 13:24, Jon LaBadie wrote:
On Mon, Nov 24, 2003 at 12:15:26PM -0500, Alastair Neil wrote:
can someone give me some pointers about accessing my juke box using
mtx? I cannot figure out what device to use.
nwadmin reports the control port at [EMAIL PROTECTED] and the
* Jon LaBadie [EMAIL PROTECTED] [20031124 14:15]:
On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
Hi,
I'm having strange problems with the include thingy in an
entry in my disklist:
bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly
We are building an amanda backup server and have a question regarding
memory requirements. My guess is that Amanda is more processor
intensive than memory intensive. Is this correct? For a dedicated
backup server that won't be doing much of anything else, is 512MB of
memory enough?
On Mon, Nov 24, 2003 at 07:14:56PM +0100, Paul Bijnens wrote:
Jon LaBadie wrote:
Might it be a good idea to have amtapetype note too many files
being written during the first phase and taking some action?
Maybe with an option to override the checking.
My idea was to write only one large
On Mon, Nov 24, 2003 at 07:29:03PM +0100, Cedric Boudin wrote:
I've cleaned everything up the amanda instalation is if a dare say
virginal. I can't figure out where amcheck does get the info. No
amanda process is runing and I' doubled checked theres is absolutely
no file whatsover in
On Mon, Nov 24, 2003 at 02:57:56PM -0500, Jean-Francois Malouin wrote:
* Jon LaBadie [EMAIL PROTECTED] [20031124 14:15]:
On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
Hi,
I'm having strange problems with the include thingy in an
entry in my disklist
On Mon, Nov 24, 2003 at 01:45:00PM -0500, Richard Morse wrote:
On Monday, November 24, 2003, at 01:04 PM, Tom Brown wrote:
We are building an amanda backup server and have a question regarding
memory requirements.
My amanda backup server is a pentium 90 with 32M of ram, running
FreeBSD
* Jon LaBadie [EMAIL PROTECTED] [20031124 15:23]:
On Mon, Nov 24, 2003 at 02:57:56PM -0500, Jean-Francois Malouin wrote:
* Jon LaBadie [EMAIL PROTECTED] [20031124 14:15]:
On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
Hi,
I'm having strange problems
Paul Bijnens writes:
Cedric Boudin wrote:
Hello honourable readers of the list,
After some succesfull testing, I wanted to make a run for real. As
recommended in the FAQ I removed:
-curinfo
-any log files from the log directory
-tapelist
-reseted
On Thu, 20 Nov 2003 at 8:26am, Rebecca Pakish Crum wrote
I'm running amanda 2.4.2p2 on a RH box as my backup server. I
installed the amanda client on my (sol8) firewall on
Friday, and set
up a rule for the server to get to the firewall for amanda
services -
amcheck runs fine and
On Mon, Nov 24, 2003 at 09:46:31AM +0100, Martin Oehler wrote:
Hmm, the only option that sounds like it could speed up the [amtapetype] process
is blocksize. Does anyone know a good value for this?
The same value as amdump will be using! With some tape
technologies, the tape's capacity
Jon LaBadie writes:
On Mon, Nov 24, 2003 at 07:29:03PM +0100, Cedric Boudin wrote:
I've cleaned everything up the amanda instalation is if a dare say
virginal. I can't figure out where amcheck does get the info. No
amanda process is runing and I' doubled checked theres is absolutely
On Mon, Nov 24, 2003 at 07:14:56PM +0100, Paul Bijnens wrote:
My idea was to write only one large file in the first pass, just
until [amtapetype] hits end of tape.
One problem with that is that the drive's internal buffering
might distort the results, by letting amtapetype think it has
On Monday 24 November 2003 13:29, Cedric Boudin wrote:
Paul Bijnens writes:
Cedric Boudin wrote:
Hello honourable readers of the list,
After some succesfull testing, I wanted to make a run for real.
As recommended in the FAQ I removed:
-curinfo
-any log files from the
Gene Heskett writes:
On Monday 24 November 2003 13:29, Cedric Boudin wrote:
Paul Bijnens writes:
Cedric Boudin wrote:
Hello honourable readers of the list,
After some succesfull testing, I wanted to make a run for real.
As recommended in the FAQ I removed:
On Monday 24 November 2003 20:42, Cedric Boudin wrote:
Gene Heskett writes:
[...]
Amanda at my place is called backup and belongs to grp backup
can read write in /var/lib/amanda/ 700 /etc/amanda 700
/var/backups/holdingdisk 700 /var/log/amanda 700
I don't think those '700' perms are kosher.
On Sun, Nov 23, 2003 at 07:46:32PM -0500, Kurt Raschke wrote:
...when amdump runs, the load spikes to between 4.00 and
6.00, and the system becomes nearly unresponsive for the duration of
the backup. The server is backing up several local partitions, and
also two partitions on remote servers.
On Mon, Nov 24, 2003 at 03:26:39PM -0500, Jon LaBadie wrote:
Anyone out there running amanda on a 386 or 486 with 16M of ram?
Not any more, but I did in 1995 or thereabouts :-) 486-DX33 (or
was it a DX2/66?) with 16 whole megabytes worth of 30-pin SIMMs.
It turned out that (a) that wasn't
39 matches
Mail list logo
