We have a Solaris E250 amanda server backing up two T1000 servers,
also Solaris, hosting Lotus Notes.
Over time, we decided on HW compression, runs where long but they
completed pretty reliably at the same time every day.
We tried an experiment, since we hadn't really tried SW compression
since
On Fri, Jul 25, 2008 at 01:18:40PM -0400, Brian Cuttler wrote:
We have a Solaris E250 amanda server backing up two T1000 servers,
also Solaris, hosting Lotus Notes.
Over time, we decided on HW compression, runs where long but they
completed pretty reliably at the same time every day.
We
Andre,
Yes, that is typical behavior for amanda. If you have sufficient
holding disk to store dumps they will be written to the work area
and wait their until either you run an # amflush or you run a
successfull # amdump AND have the autoflush parameter set to yes.
There is a reserve parameter
Unclear, you have two concurrent amdump tasks running or you have
two DLE's running concurrently (which is really the goal).
For concurrent amdump tasks.
I've had that problem only when sharing my holding partition with
other jobs, either users or with competing amanda jobs (yes, I do
do some
the finished one was completed. What is happening (so far) is
both DLEs are just hanging.
Thanks,
Jordan
On Apr 28, 2008, at 11:09 AM, Brian Cuttler wrote:
Unclear, you have two concurrent amdump tasks running or you have
two DLE's running concurrently (which is really the goal
On Mon, Apr 28, 2008 at 02:12:40PM -0400, Jordan Desroches wrote:
Well, it must have hit SOME timeout, because after a few hours, it
AMANDA did exactly as Jean-Louis said it would. So all's good :-)
That is good news, better than forcing single threading and
apparently not in the version I
** email thread greatly trimmed **
Chris,
amDump time changed from 48 hours to 14 hours
On Tue, Mar 18, 2008 at 06:29:46PM -0400, Chris Hoogendyk wrote:
Interesting that your LTO3 is doing no better than your LTO for speed. I
would guess you should be getting 3 times the speed you are
PROTECTED]
---
Erd?s 4
Brian Cuttler wrote:
Hi amanda users,
I'm running dumps on a SUN E250 server, this system has been
demoted from Lotus notes and local amanda server to just an
amanda server, but has picked up additional clients.
Rather than being client/server
it.
thanks,
Brian
On Fri, Feb 29, 2008 at 09:57:07AM +0100, Stefan G. Weichinger wrote:
Brian Cuttler schrieb:
Hello Amanda users,
I had the jukebox I use on one of my SGI/IRIX Amanda servers
done for
the machines our site will retain.
thanks,
Brian
On Fri, Feb 29, 2008 at 11:13:06AM -0500, Brian Cuttler wrote:
Stefan,
I didn't realize the amlabel command wrote a log, I have
Chris,
I _so_ love amanda!
thank you!
On Fri, Feb 29, 2008 at 02:43:50PM -0500, Chris Hoogendyk wrote:
Brian Cuttler wrote:
Stefan, et al,
We have decided that the standalone tape drive has failed, it
will not read nor write known
Hello Amanda users,
I had the jukebox I use on one of my SGI/IRIX Amanda servers fail
and we reverted to the attached standalone SDLT 220.
I modified amanda.conf to use the different tape drive and to
not use any changer config.
I was able to label (one/day) a few tapes (and write them that
On Fri, Feb 22, 2008 at 01:17:26PM -0500, Jon LaBadie wrote:
On Fri, Feb 22, 2008 at 11:48:02AM -0600, Gordon J. Mills III wrote:
I have recently run into a problem with restoring. I want to restore a
folder on a DLE that is about 100G. The folder I want to restore is small
but apparently
Hi, Solaris 9 Server with amanda 2.4.4
Client is a zone on a solaris 10 system running amanda 2.5.2p1.
amcheck -c info
Amanda Backup Client Hosts Check
ERROR: NAK squidzone1: user amanda from 199.184.30.36 is not allowed to execute
the service noop: Please add
:07:50PM -0500, Brian Cuttler wrote:
Craig,
On Tue, Nov 20, 2007 at 07:51:00AM +1100, Craig Dewick wrote:
On Mon, 19 Nov 2007, Brian Cuttler wrote:
Platform, Solaris 9, Amanda 2.4.4, MTX 1.3.9
Nope, not fixed, here are updated logs, any help would be apreciated.
Oddly... we seem ok
Opps, seem to have fixed the error myself, before bugging either
list, however I will present the following in case there is something
that might be generally helpful.
My fix was to disable the barcode reader in the amanda config
file that sets the mtx parameters. This is acceptable at my site
Stefan,
I think a related thread was discussed a couple of weeks ago.
In my case, this is not something I'm doing, not running amanda
within the virtual machine. Rather I am running amanda in the
(Solaris) global-zone and using it to backup the non-global zone
data, since its the partent/owner
and glue for
both configs...)
thanks,
Brian
On Mon, Nov 19, 2007 at 10:00:44AM -0500, Brian Cuttler wrote:
Opps, seem to have fixed the error myself, before bugging either
list, however I will present
Craig,
On Tue, Nov 20, 2007 at 07:51:00AM +1100, Craig Dewick wrote:
On Mon, 19 Nov 2007, Brian Cuttler wrote:
Platform, Solaris 9, Amanda 2.4.4, MTX 1.3.9
Nope, not fixed, here are updated logs, any help would be apreciated.
Oddly... we seem ok on the C2 jukebox but not the L9, same
Hello amanda users,
This isn't an issue of great import, I'm just trying to avoid
clutter in the config directory.
I must be using logdir in amanda.conf incorrectly...
I'd thought this would allow me to push my log files (log.YYMMDD
and amdump.N) into a subdirectory, but its not, I am finding
On Thu, Nov 08, 2007 at 11:15:19AM -0500, Jean-Francois Malouin wrote:
* Brian Cuttler [EMAIL PROTECTED] [20071108 11:12]:
Hello amanda users,
This isn't an issue of great import, I'm just trying to avoid
clutter in the config directory.
I must be using logdir in amanda.conf
Hi Marc,
I've been successfully runing amanda with L9/LTO (more than 5 years)
C2/LTO3 for, 2 years (?) and just (two weeks ago) installed a second
C2/LTO3 on another amanada server.
All installations are running well, though I did put in place a
modified file for mtx, will have to check and see
- Forwarded message from j. Chris Knight [EMAIL PROTECTED] -
Amanda-users:
I tried to recover a file that we backed up using gtar, which was
expected to be on the level 0 tape (WCNOTESX39). I've retrieved that
tarball but can't locate the file.
I'm concerned that I don't have an error
Trying to compile 2.5.2p1 on Solaris, the 2.5.2p1 release is not
compiling for me, not sure if its an compiler/library issue on
my build system or ... well, it has to be, right.
Not sure of the fix though, can someone guide me, or suggest an
alternate kit to use ?
I want to build with tcp/udp
Andy,
I had two config that ran concurrently on the same amanda
server, each having access to its own tape, also the tapes
where actually Storedge L9/LTO jukeboxes, so each config
owned a jukebox.
In order to avoid conflicts I was able to segregate my
clients into two groups, one having only
Amanda users,
I may have missed it in the mailing list... I know that
encryption came available in 2.5.0, either server side
or client side, or the channel (though I think encrypting
on the client provides an encrypted channel by default, true ?)
Anyway, I was wondering and haven't seen... how
I have a new client and installed 2.5.2p1 (because I'm going to
need the features and it compiled cleanly and quickly).
The server is still at 2.4.4, both the client and server run Solaris 10.
I was surprised that the client seemed to need a client.conf file, but
the man page was available... I
in degraded mode.
You don't allow full dump in degraded mode (see reserve option)
amanda can't dump the new disks.
Either set 'reserve' to a smaller value or put a tape.
The amanda-client.conf files are not needed, even if you get an error
message in the log files.
Jean-Louis
Brian
Craig,
Great, I see from the other messages that you made a lot of progress.
Don't know if you've worked with changers before, the mtx config file
in the amanda config directory has been updated to reflect the number
and ids of the tape drives and the correct number of slots and all ?
Mine
Craig,
Yes, looking at my /kernel/drv/sgen.conf file I also see that it
is pretty simple (simpler than I'd though/remembered).
All of the other lines are comments, these 3 lines seem to completely
cover both my L9 and my C2 changers.
device-type-config-list=changer;
name=sgen class=scsi
I'm sorry, missed this thread until this morning and don't know
your config or the actual problem.
I have an L9 on solaris and might be able to help.
See that you've configured sgen, the L9 uses different scsi id
for the robot and the tape, these have to be reflected in the
amanda.conf. This is
If the script looks to be your problem and the link is bad I
can email the script I use. It is about 2x the size of the script
that had come with MTX 1.2.17rel.
On Mon, Sep 17, 2007 at 09:38:31AM -0400, Brian Cuttler wrote:
I'm sorry, missed this thread until this morning and don't know
your config
What group is your amanda user in ?
Follow the links from the device /dev/rdsk/c0t1d0s5 to the
/devices/... and check the protections on that.
you may want amanda in a different group or something.
On Thu, Aug 16, 2007 at 10:04:42AM -0700, Brian Maxwell wrote:
Hi all,
I hope you can help!
Aaron,
On Mon, Aug 13, 2007 at 04:25:47PM -0700, Aaron J. Grier wrote:
On Mon, Aug 13, 2007 at 11:21:17AM -0400, Brian Cuttler wrote:
I may be wrong, but I'd have thought that the TEE was in memory, then
piped again to gzip and with the final output being put to an index
directory
Aaron,
I may be wrong, but I'd have thought that the TEE was in memory,
then piped again to gzip and with the final output being put to
an index directory specified in amanda.conf.
(or, since I haven't really worked with amrecover, I could be
completely wrong)
In our case, the amanda
Solaris 9, Amanda 2.4.4, gtar 1.15.1, gzip 1.3.5
A query,
We recently switched to tar rather than ufsdump for a large
partition on one of our systems (Thanks Jon LaBadie for working
through the exclude lists with me) and dumps are working well,
in terms of fitting on the tapes.
We had a problem
Jon,
On Wed, Aug 08, 2007 at 11:24:03AM -0400, Jon LaBadie wrote:
On Wed, Aug 08, 2007 at 11:09:34AM -0400, Brian Cuttler wrote:
Somehow I don't see my manager ok'ing reenable of the index function
to perform a scientific test.
Indexing is not an all or none situation
Jon, Gene, Dustin,
Actually I don't know that we need indexing on this box, Its a
Lotus Notes server, so any file that it touched by its owner or
receiving email will be backed up in its entirety, and some of
these files are big.
It would be nice if I understood things better though as we have
Interestingly I'm seen at my site that a large partition, which might
fit on a tape, can be not-the-first on a tape and hit EOT while being
written, it will then dump to a second volume (if jukebox == 1).
You can have a similar cascading failure if you try to put another
DLE on the end of the
Hi - stupid query for future development.
I realize I could probably nice these jobs, even from cron, would
it be worth having a switch that, I don't know, changed the number
of dump threads based on time-of-day ?
Something like After 5am only allow 2 active rather than 4 active dumpers ?
Is
Chris,
On Tue, Jul 31, 2007 at 01:36:49PM -0400, Chris Hoogendyk wrote:
So, you have sendmail and lotus notes running on it. Does the other
lotus notes server load balance with this one? Or do they serve
different groups? Does it spawn a mess of processes the way sendmail
does? The load
I'm runing amanda on solaris 9 and fairly recently ran into
a situation where the drive (RAID array) was too large to fit
on a single volume of tape.
We resolved this by dividing the partition into segments and
using gtar for backups.
(for /maildb2/one through /maildb2/five)
wcnotes
Good morning,
I've got a 2.4.4 amanda on Solaris 9...
We have this running well, consolidated all DLE to the single
L9/LTO rather than splitting them across the L9/LTO (L9 - Sun
StorEdge 9 slot jukebox) SDLT320, able to do this since we
replaced amanda with a version with gtar compile option.
Chris,
If I understand your question correctly...
Q1) I have asked Sun and the makers of the LTO2 drive and it seems
there is no way to turn hardware compression on or off on this unit,
it is always on. From my reading in the Amanda forum it seems that the
LTO2 drive will sense if the
Unable to create files in /tmp or /var/tm
You guys where so right! Thank you, confirmed via testing
that this is certainly client side and in all cases because
my disklist file on the server was incorrect. Either pointing
to links that did resolve to partitions or pointing to directories
that
I posted to the web -- but I don't know that it will find its
way back to amanda-users. Besides, the thread was 2 years old...
but its come back to haunt me.
--- In [EMAIL PROTECTED], Jon LaBadie [EMAIL PROTECTED] wrote:
On Thu, Feb 24, 2005 at 09:04:49AM -0500, Gil Naveh wrote:
Hello,
--- In [EMAIL PROTECTED], Jon LaBadie [EMAIL PROTECTED] wrote:
On Thu, Feb 24, 2005 at 09:04:49AM -0500, Gil Naveh wrote:
Hello,
Amanda is successfully running on our Solaris Servers. But on Amanda's
report (the E-mail it sends after amdump) I get the following STRANGE
message:
Jon,
I'm confused, apparently not parsing this correctly.
I believe you are saying that using strings you confirmed that
the message is generated from ufsdump, but that you would not
expect ufsdump to create /tmp/amanda, you would have expected
that from an amanda binary.
Is this a request to
Hello Amanda users,
We just did a quick head count at our site (we are updating our wiki)
and found the following
21 Amanda servers
over 70 amanda clients
over 293 DLEs
- We have Solaris, IRIX and Linux servers and clients.
- We have DLT, SDLT and LTO series tape units, we have obsoleted
Robert McCraw,
Dustin Mitcher,
Christopher McCrory,
Peter Kunst,
Amanda users,
I want to thank you for your help. I did find an older version of
gtar - that I believe to be working. Its a 1.13 but I don't see a
more specific version number (from SFW collection). I will replace
as suggested if I
Good morning amanda users,
I'm running amanda 2.4.4 on solaris 9, just built it on solaris 8.
Finding that my TAR dumptypes seem to be running compression though
I believe I've configured it not to.
The (ufs)DUMP DLEs properly perform compression none.
Not only that, but the default, I believe
).
thank you,
Brian
On Tue, May 22, 2007 at 11:38:37AM -0400, Jon LaBadie wrote:
On Tue, May 22, 2007 at 11:21:50AM -0400, Brian Cuttler wrote:
Good morning amanda users,
I'm running amanda 2.4.4 on solaris 9, just built it on solaris 8
LaBadie wrote:
On Tue, May 22, 2007 at 09:29:12AM -0400, Brian Cuttler wrote:
I want to thank you for your help. I did find an older version of
gtar - that I believe to be working. Its a 1.13 but I don't see a
more specific version number (from SFW collection). I will replace
as suggested
, 2007 at 11:22:20AM -0400, Jon LaBadie wrote:
On Tue, May 22, 2007 at 09:29:12AM -0400, Brian Cuttler wrote:
I want to thank you for your help. I did find an older version of
gtar - that I believe to be working. Its a 1.13 but I don't see a
more specific version number (from SFW collection). I
On Tue, May 22, 2007 at 04:07:32PM -0400, Jon LaBadie wrote:
On Tue, May 22, 2007 at 03:10:02PM -0400, Brian Cuttler wrote:
Jon,
Think I found a good kit for 1.15.1, which seems to be on the
good list at amanda.org.
Unless you advise otherwise I will try to build using
Sorry, hate to ask this, but one of my DLE's has outgrown the
tape drive and I want to divide it into multiple TAR-DLE entries
but I'm having trouble finding an installable version of gtar
that is a correct version for Amanda and my OS.
I'm running Solaris 9 and believe that I should use one of
On Fri, May 18, 2007 at 01:47:47PM -0500, [EMAIL PROTECTED] wrote:
On Fri, May 18, 2007 at 02:32:13PM -0400, Brian Cuttler wrote:
Sorry, hate to ask this, but one of my DLE's has outgrown the
tape drive and I want to divide it into multiple TAR-DLE entries
but I'm having trouble finding
know if this version of gtar is sufficient for amdump
and amrestore to work properly ? ** This gtar is apparently from
the Sun freeware kit.
thanks,
Brian
On Fri, May 18, 2007 at 02:52:50PM -0400, Brian Cuttler wrote:
On Fri, May 18, 2007 at 01:47:47PM -0500, [EMAIL PROTECTED] wrote:
On Fri
Dustin,
On Fri, May 18, 2007 at 02:29:06PM -0500, [EMAIL PROTECTED] wrote:
On Fri, May 18, 2007 at 02:52:50PM -0400, Brian Cuttler wrote:
On Fri, May 18, 2007 at 01:47:47PM -0500, [EMAIL PROTECTED] wrote:
On Fri, May 18, 2007 at 02:32:13PM -0400, Brian Cuttler wrote:
Sorry, hate
On Fri, May 18, 2007 at 12:54:00PM -0700, Christopher McCrory wrote:
Hello...
On Fri, 2007-05-18 at 14:32 -0400, Brian Cuttler wrote:
Sorry, hate to ask this, but one of my DLE's has outgrown the
tape drive
You might also try split/span
http://wiki.zmanda.com/index.php
Amanda users,
I'm sure this is addressed somewhere but I've never seen it
(perhaps because I missed it) explicitely discussed on the list.
My assumption on tape filling is that if dumps are still in
progress that amanda will try to write each DLE to tape as
it completes.
I have no idea what
I'm sorry to interject without having read the complete thread but
I wanted to share (remind of previous emails) that I had a problem
with my LTO on Solaris a while back. Turned out the HBA card was
failing, the A side was dropping in performance with no additional/errors
noticable which the B
Hello amanda users,
Question - we run multiple amanda servers and were wondering if
anyone had written (and might share) any kind of a summarizing tool
that would allow us to determine across all servers the amount of
disk under backup, typical nightly dump volume... that sort of thing.
I just
We are running the server on Solaris and a client on MAC OS X
but are seening that the launchd process seems to invalidate
the service.
So far I haven't found the actual line in /var/log/system.log
but I see these messages which show the intent, so I believe
I'm on track.
Jan 6 18:32:09 trel
Chris,
HW compression is great for preserving the server's cpu but
doesn't allow amanda to get an historical estimate of the
compressability of the partition.
I truely don't know what the official answer is...but what I
have done for a couple of my systems (I prefer SW compression
on the client
Paul,
On Wed, Dec 13, 2006 at 10:37:16PM +0100, Paul Bijnens wrote:
Brian Cuttler schreef:
An interesting but confusing (for me) read, but the wiki page
was very helpful.
http://wiki.zmanda.com/index.php/Splitting_dumps_across_tapes
We are will likely be implementing this shortly, I have
Jobst,
if your data grows you may actually run into an estimate timeout
after a long period of success, I did just the other day, had a
20 minute timeout and checking the /tmp/amanda logs on the client
I found that the estimate didn't finish for nearly 23 minutes.
I'm not saying you had the
An interesting but confusing (for me) read, but the wiki page
was very helpful.
http://wiki.zmanda.com/index.php/Splitting_dumps_across_tapes
We are will likely be implementing this shortly, I have a number
of jukeboxes with large DLE or many small DLE where I'm only
partially filling multiple
Evan,
On Thu, Dec 07, 2006 at 04:52:52PM -0600, Evan Harris wrote:
On Thu, 7 Dec 2006, Brian Cuttler wrote:
I've assumed that the spindle the amanda work area is on was dedicated
to the work area and not split, I know nothing about the architecture
That is correct. That disk is only
, Brian Cuttler wrote:
Evan,
What OS, type of tape, type of drive, HW platform ?
I'm unfamiliar with a parameter to do what your asking
for for good measure, what version of Amanda ?
Actually, how did you determine that a drive within a changer
was shoe-shining ? What else shares the bus
intensive that it was blocking the disk to tape IO and I don't know what
tool to suggest monitoring with.
Evan
On Thu, 7 Dec 2006, Brian Cuttler wrote:
On Wed, Dec 06, 2006 at 04:33:16PM -0600, Evan Harris wrote:
Debian testing, SDLT 110/220, Intel P4 2.8Ghz 3gig RAM. Amanda 2.5.1p1-2
Evan,
What OS, type of tape, type of drive, HW platform ?
I'm unfamiliar with a parameter to do what your asking
for for good measure, what version of Amanda ?
Actually, how did you determine that a drive within a changer
was shoe-shining ? What else shares the bus with the tape and
with the
Just did the survey and wanted to expend a bit.
We have 17 Servers, RH, Solaris and IRIX based with the clients
generally being Solaris and IRIX, but will backup the odd RH or
SUSE system and even one OS X box (want to piss of your MAC guy ?
ask him what version of Linux OS X is.)
We backup to
Amanda users,
Feature request, this came up in conversation this morning, a
feature request for amtape to have a mail-output option.
The solution I recommended for our site was a cron that will pipe
the output to mailx for our amanda distribution list.
Not by any means a high priority feature
I'm sorry, missed the early part of the thread.
You are doing amdump and getting no more holding disk ?
Amanda usually delays some partitions until it has enough
holding disk to capture the DLE. Problems can arise when
you run out of tape, a DLE is larger than estimated or something
else is
On Tue, Sep 19, 2006 at 02:13:55PM +1000, Craig Dewick wrote:
On Mon, 18 Sep 2006, Jon LaBadie wrote:
It won't be the script that sets up specific devices. The OS picks
the device names based on its scans and distorted logic. In case
you are not familiar with that naming scheme c1t2d3
Craig,
I know I posted, and exchanged information on this with others on
the list some time ago.
Give me a chance to look in my outbox, or you can check the list
archives, and we'll see what we can see.
What version of Solaris ?
I access the robot as /dev/scsi/changer/c6-something, I recall
Craig,
My L9 has an LTO drive, but no, I am not aware that the cables are
any different than LVD or SE. But I could be wrong, my cables came
with the card and drive, all purchased together.
I found the chg-zd-mtx drivers/glue the correct ones for my site.
I didn't place a cleaning tape in the
Hello Amanda users,
This is the Solaris 9 amanda server with the Solaris 8 client
(in addition to itself).
File protections must be on on the work area, else the smaller
partitions wouldn't use it.
Tried reserve parameter, 2.4 amanda.conf seemed to fail on
it (amcheck certainly reported an
Hello amanda users,
I'm running an old version of amanda 2.4 on a Solaris 9 system
with a Solaris 8 client.
Its come to my attention that the two larger client partitions
are not being moved through the work area but are being written
directly to tape.
The work area is a 70 Gig partition, the
Hello Amanda users,
I am running amanda VERSION=Amanda-2.4.4p1-20030716 on an SGI/IRIX
system v6.5.28 and saw something odd today.
The output from amstatus showed that for several partitions the
amount of data being dumped far exceeded the estimated size of
the data (300% dumped and still
, Frank Smith wrote:
Brian Cuttler wrote:
Hello amanda users,
I'm running an old version of amanda 2.4 on a Solaris 9 system
with a Solaris 8 client.
Its come to my attention that the two larger client partitions
are not being moved through the work area but are being written
Frank, et al,
FYI - amanda.conf choked on reserve apparently not a legal
parameter in v2.4.
While upgrading would help there should be a 2.4 solution, eh ?
good weekend all.
Brian
On Fri, Sep 08, 2006 at 03:02:44PM -0400, Brian Cuttler wrote:
Frank,
Good suggestion, it might
Oooh, Oooh, me, I am, I am !
We moved from the StorEdge L9 to the C2, it was a simple drop
in with only the predictable minor modifications to amanda.conf
for changerdev and tapedev, well, plus the OS mod to support it.
The L9 had discrete SCSI id for the robot and the tape drive, with
the C2
: +44 (0)7870 218 693
Fax: +44 (0)870 7060 056
CNA, CNE 6, CNS, CCNA, MCSE 2003
Brian Cuttler [EMAIL PROTECTED] 08/01/06 9:16 PM
The robot/picker/whatever is a different device on most systems
from the tape drive, I've seen it as a different device/SCSI ID
and as the same SCSI ID
Gil,
You wheren't by any chance using SW compression ?
You may have said earlier but I missed it if you did, if so
you will need to lengthen the pipe a little bit...
# dd | gunzip | ufsrestore
On Wed, Jul 19, 2006 at 04:20:25PM -0700, Pavel Pragin wrote:
Hello,
Can you please run this and
I got this... Now that I look at it the length seems a little short,
but we seem to be using only about 30% of the tape at this point (we
where running ok on the LTO1 but are constantly adding more DLEs).
define tapetype LTO3 {
comment just produced by tapetype prog
comment brc,
Hello All,
I've added more work area to amanda, have been trying to find
what other problems we may be seeing with the job, since it
still seems to take longer than it should.
Upon looking more closely at the amanda report from amdump I see
that the tape I/O rate is around 1800 KP/s where as 2
Joshua,
On Thu, Jul 06, 2006 at 11:12:39AM -0400, Joshua Baker-LePain wrote:
On Thu, 6 Jul 2006 at 10:24am, Brian Cuttler wrote
I've added more work area to amanda, have been trying to find
what other problems we may be seeing with the job, since it
still seems to take longer than
We initially had a problem with this also, I'm sure there
was a more subtle way - but we simply disabled the OS X
system's FW. Your problem and/or site policy may be different.
On Mon, Jul 03, 2006 at 06:54:26PM -0400, Josh Steadmon wrote:
On 2006.07.03 23:05, Paul Bijnens wrote:
30 seconds
Paul,
On Wed, Jun 28, 2006 at 10:38:45AM +0200, Paul Bijnens wrote:
On 2006-06-26 17:29, Brian Cuttler wrote:
# df -kh /amanda/work
Filesystem size used avail capacity Mounted on
/dev/dsk/c7t6d0s0 67G 118M66G 1%/amanda
With a reserve value of 10, we
this will be fun to schedule).
thank you,
Brian
On Mon, Jun 26, 2006 at 01:29:02PM -0400, Brian Cuttler wrote:
Jon,
Stefan,
Suddenly...
cd /amanda/
ls -l
total 46344
drw-rw-r-- 2 root root
Raymond,
I don't recompile all that often but will help as I can.
What version of IRIX ?
What architecture system ?
ie you may find that O2 systems do not have 64 bit libraries installed.
Since amanda is largely a driver, organizer, doesn't do a lot of
computational work on its own, you may be
}
thank you,
Brian
On Fri, Jun 23, 2006 at 01:59:27PM -0400, Jon LaBadie wrote:
On Fri, Jun 23, 2006 at 01:18:15PM -0400, Brian Cuttler wrote:
Hello amanda users,
I'm confused as to why these dumps, where are late
try this.
# chmod 770 work*
Lets see what tomorrow brings.
On Mon, Jun 26, 2006 at 12:12:24PM -0400, Jon LaBadie wrote:
On Mon, Jun 26, 2006 at 11:29:07AM -0400, Brian Cuttler wrote:
Jon,
Maybe someone can tell us the actual lines in log or debugging
files that would say why amanda
Hello amanda users,
I'm confused as to why these dumps, where are late in to be
dumped today (there are 50 some entries in the disklist) are
not making use of the work area.
The current partition is only provide 10 Gig and the work area
is 67 Gig and is completely free.
Once earlier/completed
.
thank you,
Brian
On Fri, Jun 23, 2006 at 01:59:27PM -0400, Jon LaBadie wrote:
On Fri, Jun 23, 2006 at 01:18:15PM -0400, Brian Cuttler wrote:
Hello amanda users,
I'm confused as to why these dumps, where are late in to be
dumped
Jon,
On Wed, May 24, 2006 at 07:25:46PM -0400, Jon LaBadie wrote:
On Wed, May 24, 2006 at 02:54:34PM -0400, Brian Cuttler wrote:
The -e made a huge difference in runtime.
# date ; amtapetype -e 400g -f /dev/rmt/3n ; date
Wed May 24 09:23:58 EDT 2006
Writing 2048 Mbyte compresseable
Jon,
On Thu, May 25, 2006 at 10:33:48AM -0400, Jon LaBadie wrote:
Well, actually a little different. I got my Ultrium 1 from ebay and
like a kid with a new toy ran several tapetypes on it. Three different
physical tapes (two brands), one two times, and with 3 different block
sizes, and a
Jon,
On Tue, May 23, 2006 at 05:40:02PM -0400, Jon LaBadie wrote:
On Tue, May 23, 2006 at 01:22:02PM -0700, Pavel Pragin wrote:
Brian Cuttler wrote:
Does anyone have the tape type for the LTO3 (Quantum) ?
Are there any other parameters I should tweak to get better
performance
401 - 500 of 776 matches
Mail list logo
