Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
assume that from the message at the bottom of the report that - file
changed as we read it has caused a FAILURE AND STRANGE DUMP.
Have I got anything to worry about here!.
On the myserver machine, the file _.1.tmp: has changed
Jerome Pioux wrote:
Load tape monthly4 now
Continue [?/Y/n/s/t]?
EOF, check amidxtaped.timestamp.debug file on reddog.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
So I suppose that tar 1.13 can't read a backup
On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator
wrote:
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
assume that from the message at the bottom of the report that - file
changed as we read it has caused a FAILURE AND STRANGE DUMP.
Have I
Hi
Cheers for the reassurance.
I will make note of your comments to file.
Thanks
On Thu, 2005-09-29 at 07:15 -0400, Jon LaBadie wrote:
On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator
wrote:
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
Hi all
I have just been asked to add our email server to our Amanda server
backup.
I have installed the Amanda version 2.4.4p2 rpm using SuSE SLES 9 Yast2
and added the email server to disklist as below:
#/etc/amanda/DailySet1/disklist file:
# hostname diskname or mountpoint dumptype #
Chuck Amadi Systems Administrator wrote:
Thus enabled xinetd amanda, amadaidx and amidxtape.
Recheck the entries in /etc/xinetd.d (paths to binaries?) and make sure
that you also restarted xinetd.
Hi
I rechecked the /etc/xinetd/amanda file and the other two
# default: off
# description: Amanda backup client
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
Hi got a bit further I had on the emailserver SuSE's default firewall
running thus disabled
Now get this error:
Amanda Backup Client Hosts Check
ERROR: ktinga.smtl.co.uk: [access as amanda not allowed from
[EMAIL PROTECTED] amandahostsauth failed
Client check: 2
Chuck Amadi Systems Administrator wrote:
Hi got a bit further I had on the emailserver SuSE's default firewall
running thus disabled
Now get this error:
Amanda Backup Client Hosts Check
ERROR: ktinga.smtl.co.uk: [access as amanda not allowed from
[EMAIL
Hi again
Its that time for a monthly archive backup I have currently 80GB server
and using a DAT DDS-4 20GB native 40GB compression I am aware that I
cannot have both hardware compression and software compression on So
Amanda usually behaviour is to have hardware compression turned off
using the
I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive - I want
to disable hardware compression but I'm not sure of the best way to do that.
I can issue a command mt -f /dev/nst0 defcompression 1 which seems to work
(amtapetype doesn't give me the warning about hardware compresion)
I have a similar setup. I have HW compression turned off on the drive (HP
DAT24X6 changer).
In my monthly config:
dumpcycle 0 weeks
runspercycle 1
tapecycle 1000 tapes
runtapes 3
Also, record is turned off so my normal daily amanda config does not think
the level 0 has been completed after the
Are there any dip switches on the drive ? My HP DAT24x6 has a dip switch
bank on the bottom which turns off compression in the HW. I don't see any
indication of that in your drives manual.
Scott..
Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario,
I am having a weird problem with the portrange
specification. My situation is reversed from most configurations in the FAQ as
my host is behind the fw, while the backup server sits in front of it. There is
no NAT going on.
Amanda was compile from the source RPM, I added the
following
I recently had similar issues. Look for a post in the archives about 2 weeks
ago that discussed the same topic. A few people gave very helpful replies
already that should apply in your case, too.
Brief summary:
- --with-tcp-portrange is not needed
- you must configure the same values on both
There are no DIP switches that I can find - its a Sun Enclure (SDLT 220 unit)
around a Quantum TR-S13AA.
Chris
-- Original Message --
Received: Thu, 29 Sep 2005 10:33:50 AM MDT
From: Scott R. Burns [EMAIL PROTECTED]
To: Christopher Davis [EMAIL PROTECTED], amanda-users@amanda.org
I searched the archives and found your posts. I made it work, and I'll give
a quick rundown of what did not work until what did.
Default config, no go.
Tried --with-(tcp/udp)portrange=1,10100 also no go. The Amanda software
complained about insecure ports. Not much to go on there.
Tried
Brenckle, Nicholas wrote:
Finally worked with different ranges for udp and tcp (udp 850-854 and tcp
1 to 10100). Now it's happy.
My standard configure-script uses
--with-tcpportrange=5,50040 --with-udpportrange=890,899
which points to the same solution you just found.
Greets,
On Thursday 29 September 2005 07:15, Jon LaBadie wrote:
On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems
Administrator wrote:
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
assume that from the message at the bottom of the report that - file
changed as we
On Thursday 29 September 2005 12:08, Christopher Davis wrote:
I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive - I
want to disable hardware compression but I'm not sure of the best way
to do that.
I can issue a command mt -f /dev/nst0 defcompression 1 which seems to
work
The drive doesn't have any dip switches - I even took the drive out of the
encosure and couldn't find anything.
I copied the wrong mt command over -
Where I'm at now is looking at stinit ant the /etc/stinig.def file to create a
/dev/nst0l device which disables compression - I'm in the middle of
On Thu, Sep 29, 2005 at 03:06:44PM -0600, Christopher Davis wrote:
Where I'm at now is looking at stinit ant the /etc/stinig.def file to create a
/dev/nst0l device which disables compression - I'm in the middle of another
test right now and can't try it out just yet - but if this works for me
On Thursday 29 September 2005 17:06, Christopher Davis wrote:
The drive doesn't have any dip switches - I even took the drive out of
the encosure and couldn't find anything.
I copied the wrong mt command over -
Where I'm at now is looking at stinit ant the /etc/stinig.def file to
create a
Guys,
I would appreciate some help with this one, as it's freaking me out. I have
been getting backups for a while now of a particular host and file system. I
have tested the recovery before and it worked great.
This time, I put the necessary tape in, and run amrecover and it will only
I do not remember exactly what was a reason for this error, but I saw it
before :-)
1. Are you indexing this DLE?
2. What OS are you using? FC3 distributive had tar 1.14 with a bug - check
the amrecover log file and if error happens at the tar point, then simple
upgrade your tar RPM or
I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded to 1.15
and it didn't fix the issue. What do you mean by indexing DLE?
Thanks,
Steve
--- Vera [EMAIL PROTECTED] wrote:
I do not remember exactly what was a reason for this error, but I saw it
before :-)
1. Are you
On Thu, Sep 29, 2005 at 06:08:23PM -0600, Vera wrote:
I do not remember exactly what was a reason for this error, but I saw it
before :-)
I'm going to sound just like Vera :(
- Original Message -
From: Steve H [EMAIL PROTECTED]
To: amanda-users@amanda.org
Sent: Thursday,
On Thursday 29 September 2005 21:26, Steve H wrote:
I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded to
1.15 and it didn't fix the issue. What do you mean by indexing DLE?
Thanks,
Steve
I think he was referring to the DLE (DiskList Entry) pointing to a
dumptype that had a
I checked the amanda.conf file, and yes, I am indexing.
Thanks,
Steve
--- Gene Heskett [EMAIL PROTECTED] wrote:
On Thursday 29 September 2005 21:26, Steve H wrote:
I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded to
1.15 and it didn't fix the issue. What do you mean
On Thursday 29 September 2005 22:21, Steve H wrote:
I checked the amanda.conf file, and yes, I am indexing.
Thanks,
Steve
I'll be up for a little bit yet. Does the index file exist?
--- Gene Heskett [EMAIL PROTECTED] wrote:
On Thursday 29 September 2005 21:26, Steve H wrote:
I am on a Red
Gene,
Yes, the index file does exist, and I have two good backups to attempt to
restore from. However, in checking the Index files, I noticed that the actual
files had a different date on them (august 5th) while all the directories have
august 11th. This is bothering me because that
One more item to note. I attempted to use amrestore instead of amrecover, and
after specifying the command:
amrestore -p /dev/nst0 host.domain /home/public | restore -ivf -
I got this error:
Input block size is 32
restore: Tape is not a dump tape
Error 32 (Broken pipe) offset 32768+32768,
On Thursday 29 September 2005 23:01, Steve H wrote:
Gene,
Yes, the index file does exist, and I have two good backups to
attempt to restore from. However, in checking the Index files, I
noticed that the actual files had a different date on them (august 5th)
while all the directories have
33 matches
Mail list logo
