At 2003-06-17T19:20:28Z, Pete Poggione <[EMAIL PROTECTED]> writes:
> kirk is windowsNT server..
On behalf of people named Kirk everywhere:
Kiss my heiny.
Couldn't it at least have been a Sun box or something?
--
Kirk Strauser
pgp0.pgp
Description: PGP signature
On Tue, 17 Jun 2003 at 3:23pm, Jason Edgecombe wrote
> I'm trying to figure out why may backups and estimages take so long. I
> have a dual-processor machine with 4GB RAM. / and /boot are two software
> RAID1 drives and /home is a RAID5 hardware drive. My tape drive is an
> Overland Neo2000 L
Hi all,
I'm trying to figure out why may backups and estimages take so long. I
have a dual-processor machine with 4GB RAM. / and /boot are two software
RAID1 drives and /home is a RAID5 hardware drive. My tape drive is an
Overland Neo2000 LTO2 with 30 tape library.
I am using a 200GB holding
The subject says it all. My amanda tape server is running Mandrake 9.0.
Everything has been running great on this box for about a year backing
up a remote linux server and a remote windowsNT server.
2 days ago I did what I thought was an innocent system upgrade to patch
some security issues. After
On Tue, 17 Jun 2003 at 11:16am, Michael Packer wrote
> Well this time ... I removed the large disk so I could run it a couple
> times today and see what numbers I was getting. I also removed the
> holding disk since the tape and drives are all on the same machine...
>
> Dump time is down a good
Well this time ... I removed the large disk so I could run it a couple
times today and see what numbers I was getting. I also removed the
holding disk since the tape and drives are all on the same machine...
Dump time is down a good bit
1 more question...what is "estimate time"?
STATISTI
Hi All,
I've been using amanda 2.4.1 on Solaris 2.5.1 with a DLT4000 for several
years without many problems. I've recently upgraded to Solaris 9, amanda
2.4.4 and a Sun L280 (6-slot DLT7000). Most of the FS's are VxFS with a
few UFS. I'm just doing some test restores from the first night product
--On Tuesday, June 17, 2003 10:01:23 +0200 Stefan Noll <[EMAIL PROTECTED]> wrote:
> hi,
>
> 4 months ago I installed amanda 2.4.2p and it worked fine.
> but now I get following strange error:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> localhost /home/samba/projekte/Laufende lev 0 FAILED [too many
Sven Rudolph wrote:
Some approaches:
a) increase the "too many taper retries" limit (or make it configurable):
...
b) avoid this by never trying to write anything when a tape is full
...
c) don't count taper retries that happen after the tape is full
(according to tapetype entry)
d) make it onl
I'm having a problem which seems to be caused by a changed taping
order.
>From the log file (grepped):
DISK planner foo /data
SUCCESS dumper foo /data 20030615 0 [sec 10713.506 kb 16686543 kps 1557.5 orig-kb
22953940]
INFO taper retrying foo:/data.0 on new tape: [writing file: No space left on d
On Tue, 17 Jun 2003 at 8:22am, Michael Packer wrote
> The changes took it from 8+ hours to 4:45 still would like to get it
What changes?
> down a bit more... I still have a problem with compsec (made a typo) so
> I reformatted it by hand.
>
> Questions...
>
> would it be beneficial to bre
Michael Packer wrote:
The changes took it from 8+ hours to 4:45 still would like to get it
down a bit more... I still have a problem with compsec (made a typo) so
I reformatted it by hand.
The backup itself is now done in 2:35. The rest of the time is done
by taping the chunks.
You are in the
First step: clean the tape drive. Two or three times.
Second step: Try accessing the tape from outside Amanda. Using the
no-rewind device, dd(1) several dump files from the tape to /dev/null, just
to exercise the tape drive and make sure that cleaning the heads has
resolved whatever problem wa
The changes took it from 8+ hours to 4:45 still would like to get it
down a bit more... I still have a problem with compsec (made a typo) so
I reformatted it by hand.
Questions...
would it be beneficial to break /sda5 down into different disks
(I was looking at the sample disklist and saw y
Hi
As a newbie to amanda, i plan on
running it on linux. Platform is Redhat 8.0.
with apache webserver on Intel based server.
Looking to use Redhat 8.0 rpm to install
amanda.
Could someone please confirm the following
issues:
1.)Is there a hardware compatability list for
amanda?
I don't have
OFFLINE_BEFORE_UNLOAD=1 Does your tape driver require a
# 'mt offline' before mtx unload?
in my changer.conf. Did you find for some reason it was needed?
Ron
-Original Message-
From: Tom Brown [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June
unsuscribe
> $ more chg-zd-mtx.20030617110112.debug
> chg-zd-mtx: debug 1 pid 2176 ruid 11 euid 11: start at Tue Jun 17 11:01:12
> 2003
> 11:01:12 Arg info:
> $# = 2
> $0 = "/opt/amanda-2.4.4/libexec/chg-zd-mtx"
> $1 = "-slot"
> $2 = "next"
> 11:01:12 Running: /opt/mtx/sbi
> NOTES:
> taper: tape met053 kb 17996640 fm 21 writing file: No space left on device
> taper: retrying localhost:/home/samba/projekte/Laufende.0 on new tape:
> [writing file: No space left on device]
> taper: tape met055 kb 17488544 fm 1 writing file: Input/output error
> taper: retrying localhost
I had a similar problem with a Sony SDX-500C drive. I found the changer
script wasn't waiting for the tape to really become ready. Using 2.4.4,
chg-zd-mtx and adding this to changer.conf solved the problem:
offlinestatus=1 Set to 0 if 'mt status' gives an
#
I had a similar problem with a Sony SDX-500C drive. I found the changer
script wasn't waiting for the tape to really become ready. Using 2.4.4,
chg-zd-mtx and adding this to changer.conf solved the problem:
offlinestatus=1 Set to 0 if 'mt status' gives an
#
Gregor Ibic wrote:
I setup amanda config for test environment and enter:
dumpcycle 1
runspercycle 1
tapecycle 1 tapes
and doing always full backup
why I get problems on reusing the tape on the same day several times?
If you spell out the units in the parameter above:
dumpcycle 1 day
runperscycle 1
hi,
4 months ago I installed amanda 2.4.2p and it worked fine.
but now I get following strange error:
FAILURE AND STRANGE DUMP SUMMARY:
localhost /home/samba/projekte/Laufende lev 0 FAILED [too many taper
retries]
NOTES:
taper: tape met053 kb 17996640 fm 21 writing file: No space left on devic
M J wrote:
So what would be the reason(s) that one would force a level 0 backup?
e.g.
- You just reorganised a lot of software on a disk, (or reinstalled)
and you want to avoid that an incremental level takes just as much as
a level 0.
- You reorganised the disklist, and what was one entry before (
24 matches
Mail list logo
