Q: .amandahosts failed
Hi! I've problems with my amanda (and my first backup). The original problem was this (from amreport): xaloc /.furvbackup lev 0 FAILED [xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed I've created into /home/dump (the home dir of my user backup which is the default configuration from my linux debian) the file .amandahosts with these lines: localhost backup xaloc backup and I've changed the permissions to 660. Now, amreport says the following: ERROR: xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed ... basically the same. Why??? Can anyone help to me? Best regards, Raúl [EMAIL PROTECTED]
Re: .amandahosts failed / Solved!!!
Sorry!!! It seems I needed to specify a fully-qualified name. Now with: xaloc.stq.urv.es backup amcheck don't says amandahostsauth failed thanks again and sorry, Raúl [EMAIL PROTECTED] - Original Message - From: Raúl Wild-Spain [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 10:06 AM Subject: Q: .amandahosts failed Hi! I've problems with my amanda (and my first backup). The original problem was this (from amreport): xaloc /.furvbackup lev 0 FAILED [xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed I've created into /home/dump (the home dir of my user backup which is the default configuration from my linux debian) the file .amandahosts with these lines: localhost backup xaloc backup and I've changed the permissions to 660. Now, amreport says the following: ERROR: xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed ... basically the same. Why??? Can anyone help to me? Best regards, Raúl [EMAIL PROTECTED]
Q: amanda documentation / soft links vs backups
Hi! I've found into the amanda documentation (FAQ.gz) various ways to perform a backup. I've some doubts because my english is a little bad ( I'm spanish and my alternative language is french) and I would like to make some questions about this. The FAQ says the following: -- You may create short-named links in some directory closer to the root (/) so as to reduce the length of names. I.e., instead of backing up /usr/home/foo and /usr/home/bar, create the following links: /.foo - /usr/home/foo /.bar - /usr/home/bar then list /.foo and /.bar in the disklist. Another approach is to group sub-directories in backup sets, instead of backing up them all separately. For example, create /usr/home/.bkp1 and move `foo' and `bar' into it, then create links so that the original pathnames remain functional. Then, list /usr/home/.bkp1 in the disklist. You may create as many `.bkpN' directories as you need. -- then, my doubt is the following: if I create a hidden directory /.furvbackup and into this a make some soft-links to the areas I want to backup, does it will work right? and another, I suppose there isn't problem to backup directories ( not partitions or disks) with amanda, is it right?, example, into disk list -mypc /path/to/directory always-full Best regards, Raúl [EMAIL PROTECTED]
out of tape and amverify returns success
Hello everybody, Last night amdump failed to write the last file to tape. However, amverify, which always runs after the amdump, reported that the tape was fine. To make things more odd, gzip is used to compress dumps. Any clues? Cheers! Dejan P.S. Please cc to me.
Re: [ragnar@sysabend.org: Recent upgrade issue.]
On Tue, 4 Mar 2003, Stephen D. Lane wrote: Don't know if this is useful to you or not, but I just (two days ago) downloaded installed 2.4.2p2 from freeware.sgi.com with no problems under 6.5.18m it works great! I went ahead an compiled 2.4.4, which appears to have fixed the problem I was seeing with 2.4.3. Jamie Bowden -- It was half way to Rivendell when the drugs began to take hold Hunter S Tolkien Fear and Loathing in Barad Dur Iain Bowen [EMAIL PROTECTED]
Re: DLT 7000 tapetype
On Tue, 4 Mar 2003, Terri Eads wrote:
I ran the tapetype program from 2.4.3 on a DLT 7000
drive in an Overland MiniLibrary Xpress and got the
following:
define tapetype DLT7000 {
comment just produced by tapetype program
length 29668 mbytes
filemark 0 kbytes
speed 1700 kps
The filemark 0 kbytes just doesn't look right to me.
Does anyone else have something else for a DLT7000?
Looks normal from here. I use the following:
define tapetype Tandberg-DLT-7000 {
comment Tandberg DLT 7000 on QLogic UltraWide SCSI on Origin200
length 5 mbytes
filemark 0 kbytes
speed 4680 kbytes
}
The only thing that I changed from what tapteype (2.4.1p1) generated for
me is the length. I originally ran tapetype against the drive without
using hardware compression. I came up with 50GB for hardware compressed
after setting it to 70GB and watching where it typically ran out of tape
and then setting it a couple GB low just for breathing room (it's still
not perfect, the compression ratio is variable depending on data of
course). I should probably rerun tapteype, but it took over a week the
first time and I can't have the drive offline that long. And this works.
Jamie Bowden
--
It was half way to Rivendell when the drugs began to take hold
Hunter S Tolkien Fear and Loathing in Barad Dur
Iain Bowen [EMAIL PROTECTED]
Re: Tape mark error on LTO drive/tapes
From discussions on the list last week I'd understood* that
the tape length and I assume** by extension the filemark size
are used only to estimate tape capacity and determine what needs
to be bumped or if a level zero could be advanced.
What is the speed value used for ?
* Note, phrase I'd understood has no confirmed relevance to reality
and may not be worth the electrons it was written with.
These dumps were to tape Daily001.
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
I am getting regularish error as below.
It seems to be related to a long pause in the cycles as the
last halfcut partition is dumped prior to taping
Here is my tapetype
define tapetype Ultrium {
comment Ultrium LTO
length 101632 mbytes
filemark 10 kbytes
speed 13884 kbytes
}
NB filemark WAS 0 kbytes, and as someone else has just queried -- is
this OK?
I set it up to 10 kbytes to actually 'make a space'
And no the actual dump size is not bigger than the tape size
(unless I am badly miscounting something...)
8-
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: Daily005.
FAILURE AND STRANGE DUMP SUMMARY:
halfcutda0s3f lev 1 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)1:25
Run Time (hrs:min) 4:19
Dump Time (hrs:min)2:45 0:15 2:30
Output Size (meg) 20657.3 774.219883.1
Original Size (meg) 36118.5 1854.034264.5
Avg Compressed Size (%)57.2 41.8 58.0 (level:#disks
...)
Filesystems Dumped 10 8 2 (1:1 2:1)
Avg Dump Rate (k/s) 2133.4 864.7 2262.7
Tape Time (hrs:min)0:15 0:02 0:13
Tape Size (meg) 6360.2 774.6 5585.6
Tape Used (%) 6.30.85.5 (level:#disks
...)
Filesystems Taped 9 8 1 (2:1)
Avg Tp Write Rate (k/s) 7066.8 5633.7 7325.2
NOTES:
planner: Incremental of wombat.bytecraft.au.com:da0s3f bumped to level
2.
planner: Full dump of spyder.bytecraft.au.com:da0s4e promoted from 3
days ahead.
planner: Full dump of spyder.bytecraft.au.com:da0s3g promoted from 3
days ahead.
planner: Full dump of halfcut:da0s2f promoted from 3 days ahead.
planner: Full dump of halfcut:da0s2a promoted from 3 days ahead.
planner: Full dump of spyder.bytecraft.au.com:da0s2f promoted from 3
days ahead.
planner: Full dump of wombat.bytecraft.au.com:da0s2a promoted from 3
days ahead.
planner: Full dump of wombat.bytecraft.au.com:da0s2f promoted from 3
days ahead.
planner: Full dump of spyder.bytecraft.au.com:da0s2a promoted from 3
days ahead.
taper: tape Daily001 kb 6512800 fm 9 writing filemark: Input/output
error
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
halfcut da0s2a 0 59380 19968 33.6 0:151304.8
0:082597.4
halfcut da0s2f 0 483220 188640 39.0 3:18 954.2
0:286696.1
halfcut da0s3f 1 2365768014640698 61.9 98:502469.0 FAILED
spyder.bytec da0s2a 0 122080 97888 80.2 0:581696.8
0:185434.3
spyder.bytec da0s2f 0 637700 159936 25.1 2:291074.1
0:266130.4
spyder.bytec da0s3g 0 820224 27.3 0:00 696.3 0:02
104.2
spyder.bytec da0s4e 0 216370 174880 80.8 2:011444.1
0:286205.7
wombat.bytec da0s2a 0 79410 38752 48.8 0:44 872.9
0:103730.8
wombat.bytec da0s2f 0 299500 112864 37.7 5:32 340.1
0:205611.1
wombat.bytec da0s3f 2 114291505719648 50.0 51:091864.0
13:017325.2
(brought to you by Amanda version 2.4.3b4)
Murray Taylor
Special Projects Engineer
-
Bytecraft Systems Entertainment
Phone: 61 3 8710 2555
Fax: 61 3 8710 2599
Direct: 61 3 9238 4275
Mobile: 61 0417 319 256
Email: [EMAIL PROTECTED]
or visit us on the web
http://www.bytecraftsystems.com
http://www.bytecraftentertainment.com
This Email has been scanned for Viruses by MailMarshal.
Re: Tape mark error on LTO drive/tapes
On Wed, 5 Mar 2003 at 9:23am, Brian Cuttler wrote From discussions on the list last week I'd understood* that the tape length and I assume** by extension the filemark size are used only to estimate tape capacity and determine what needs to be bumped or if a level zero could be advanced. Yes. What is the speed value used for ? Nothing. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Amanda 2.4.4 + Cygwin = loss of hair...
Hi all I`ve used Cygwin before, and I have used Amanda for a while now, but trying to get Amanda on Cygwin to work happily is beginning to drive me nuts... I thought I`d get more helpful answers on here than on the Cygwin forums/lists. I followed the HOWTO-CYGWIN.html doc to the letter, got inetd running from services on XP Pro, but running amcheck on the XP/Cygwin host on the tape server keeps spitting out WARNING: hostname: selfcheck request timed out. Host Down if I run inetd -d from Cygwin bash shell, i see amandad getting started,stopped,started,stopped, over and over again I have spent most of today banging my head against this... and when I wasnt banging my head, I was trawling the web (with no result that helps) Has anyone got this setup running correctly? Many thanks in advance for any help... -- Steve - Steve Loughran, Network Infrastructure Manager Sony Computer Entertainment Europe (Cambridge) Yamaha YZF1000R Thunderace ICQ#: 104426046
host down on server
Hello, I think I have an unusual problem. I am running amanda 2.4.3 on a Solaris 8 box as server. I am trying to back up the server itself, but amcheck keeps telling me that the host is down. How can the server itself be down? I am using the local interface. I've checked everything. Any help would be appreciated. Jeff Parker -- --Jeffrey W. Parker --Unix/Linux System Administrator mailto:[EMAIL PROTECTED] http://home.xnet.com/~jwp/ -
powervault 120T on redhat 8
hi, does someone use a powervault 120t on à linux redhat 8 ? thanks S.El Mamouni
Re: host down on server
On Wed, 5 Mar 2003 at 9:25am, Jeffrey Parker wrote I think I have an unusual problem. I am running amanda 2.4.3 on a Solaris 8 box as server. I am trying to back up the server itself, but amcheck keeps telling me that the host is down. How can the server itself be down? I am using the local interface. Lots of ways. Have you gone through http://amanda.sourceforge.net/fom-serve/cache/140.html? I've checked everything. Any help would be appreciated. More details, please. What exactly does amanda say? What are the messages in /tmp/amanda/amandad*debug? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amanda and xfs
Hi,
I'm using amanda to back up 2 xfs filesystems. the 2 xfs filesystems
reside on 2 logical volumes, made with LVM.
one succeeds, one fails.
but the summary isn't very clear about what the problem might be.
the system is a redhat 7.3 system running a xfs enabled kernel build by SGI
could someone shed some light on this ?
TIA
roger
These dumps were to tape Solidair006.
The next tape Amanda expects to use is: Solidair008.
FAILURE AND STRANGE DUMP SUMMARY:
localhost /samba lev 1 FAILED [no estimate]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 0:36
Dump Time (hrs:min)0:20 0:11 0:09
Output Size (meg) 999.7 683.9 315.8
Original Size (meg) 2305.1 1783.4 521.8
Avg Compressed Size (%)43.4 38.3 60.5 (level:#disks ...)
Filesystems Dumped6 1 5 (1:4 3:1)
Avg Dump Rate (k/s) 856.2 1095.7 581.1
Tape Time (hrs:min)0:21 0:13 0:08
Tape Size (meg) 999.8 683.9 315.9
Tape Used (%) 10.47.13.3 (level:#disks ...)
Filesystems Taped 6 1 5 (1:4 3:1)
Avg Tp Write Rate (k/s) 830.5 902.3 708.6
NOTES:
planner: Incremental of localhost:/ bumped to level 2.
planner: Full dump of localhost:/ promoted from 5 days ahead.
taper: tape Solidair006 kb 1023840 fm 6 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
191-198.bbne / 3 309530 177376 57.3 4:24 673.0 3:21 884.1
191-198.bbne hda11 46060 29696 64.5 1:31 324.8 0:44 679.4
191-198.bbne hda21 10 32 320.0 0:00 76.5 0:50 1.3
localhost/ 0 1826170 700288 38.3 10:391095.7 12:56 902.3
localhost/samba 1 FAILED ---
localhost-amba-users 1 178679 116224 65.0 3:19 583.3 2:15 863.9
localhosthdb11 20 32 160.0 0:02 17.3 0:28 2.3
(brought to you by Amanda version 2.4.2p2)
Re: host down on server
Joshua, I had to add amandad to inetd.conf; chmod the /etc/dumpdates file and chmod the raw devices files to allow the dump user to write. amcheck has no errors. I am attempting a dump now. Thanks for your help. Jeff Parker On Wed, Mar 05, 2003 at 11:18:52AM -0500, Joshua Baker-LePain wrote: CCed back to the list -- please keep all discussions there, for the archives and so others can jump in. On Wed, 5 Mar 2003 at 10:13am, Jeffrey Parker wrote Thanks for getting back to me. I HAVE checked the above. Here's where I am puzzled. I get no /tmp/amanda/amandad*debug? because (I thought) that amandad is not configuired for the server. All docs I have make no entry for amandad in inetd.conf. I assumed ?? That's not what docs/INSTALL says. You need to set up (x)inetd entries for amanda for all clients. I would not used amandad because the FS's are local. Just for the Even if it's the server, it's still also a client. heck of it, however, I tried putting the amandad entry for the clients in the server inetd.conf and then I would get errors from dump saying that the specified filesystems are not readable. So now you've got permissions problems. The user amanda is running as needs to have read permissions on the raw disk devices. BTW, it woule *really* help if you included the actual error messages when asking for help. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University -- --Jeffrey W. Parker --Unix/Linux System Administrator mailto:[EMAIL PROTECTED] http://home.xnet.com/~jwp/ -
DLT 7000 tapetype (fwd)
Forwarded message:
I ran the tapetype program from 2.4.3 on a DLT 7000
drive in an Overland MiniLibrary Xpress and got the
following:
define tapetype DLT7000 {
comment just produced by tapetype program
length 29668 mbytes
filemark 0 kbytes
speed 1700 kps
The filemark 0 kbytes just doesn't look right to me.
Does anyone else have something else for a DLT7000?
--
Terri EadsUNIX Systems Administrator
[EMAIL PROTECTED] Research Applications Program
303-497-8425 National Center for Atmospheric Research
Well, I downloaded 2.4.4 and ran amtapetype and here are
the results from that:
define tapetype DLT7000 {
comment just produced by tapetype prog (hardware compression on)
length 29871 mbytes
filemark 26 kbytes
speed 1701 kps
}
So I think I'll use that one. I may rerun it with the hardware
compression off to see what that does, but it looks like amtapetype
is giving better results.
--
Terri Eads UNIX Systems Administrator
[EMAIL PROTECTED] Research Applications Program
303-497-8425National Center for Atmospheric Research
Re: host down on server
CCed back to the list -- please keep all discussions there, for the archives and so others can jump in. On Wed, 5 Mar 2003 at 10:13am, Jeffrey Parker wrote Thanks for getting back to me. I HAVE checked the above. Here's where I am puzzled. I get no /tmp/amanda/amandad*debug? because (I thought) that amandad is not configuired for the server. All docs I have make no entry for amandad in inetd.conf. I assumed ?? That's not what docs/INSTALL says. You need to set up (x)inetd entries for amanda for all clients. I would not used amandad because the FS's are local. Just for the Even if it's the server, it's still also a client. heck of it, however, I tried putting the amandad entry for the clients in the server inetd.conf and then I would get errors from dump saying that the specified filesystems are not readable. So now you've got permissions problems. The user amanda is running as needs to have read permissions on the raw disk devices. BTW, it woule *really* help if you included the actual error messages when asking for help. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Amanda 2.4.4 + Cygwin = loss of hair...
On Wednesday, March 5, 2003, at 10:01 AM, Steve Loughran wrote: Hi all [snip] I followed the HOWTO-CYGWIN.html doc to the letter, got inetd running from services on XP Pro, but running amcheck on the XP/Cygwin host on the tape server keeps spitting out WARNING: hostname: selfcheck request timed out. Host Down if I run inetd -d from Cygwin bash shell, i see amandad getting started,stopped,started,stopped, over and over again Hi! I have it on Win2K -- not XP. However, in my experience, the inetd -d option doesn't do anything for you -- all that it does is allow you to see that something is, indeed, asking for amanda. Does it work if you run it as a service? Ricky
Re: Tape mark error on LTO drive/tapes - SCSI problem ?
On Wed, 5 Mar 2003 at 10:45am, Murray Taylor wrote Mar 5 03:48:35 svlto /kernel: (sa0:ahc0:0:3:0): SCB 0x6 - timed out I don't know FreeBSD at all, but this looks like a SCSI bus issue. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: powervault 120T on redhat 8
I use the PV122T, is that close enough. Why? Mine is the DLT version w/o barcodes if that makes any difference to you. On Wed, Mar 05, 2003 at 04:25:09PM +0100, Said El Mamouni wrote: hi, does someone use a powervault 120t on à linux redhat 8 ? thanks S.El Mamouni -- Michael Murph Robbert System Administrator for Math/CS Colorado School of Mines, Golden, CO 80401-1887 Office: SH220 Office phone: 303-273-3786 Pager: 303-461-6543 or Text messages: [EMAIL PROTECTED] Email: [EMAIL PROTECTED]
Re: DLT 7000 tapetype (fwd)
On Wed, 5 Mar 2003 at 9:38am, Terri Eads wrote So I think I'll use that one. I may rerun it with the hardware compression off to see what that does, but it looks like amtapetype is giving better results. amtapetype=tapetype -- it just got renamed. And you *never* want to run (am)tapetype with hardware compression. (am)tapetype uses /dev/random (or equivalent) as a data source, and random data does not compress. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Compiling on Slackware 8.1
Hi all, I've been using Amanda-2.4.2 for several months and decided to upgrade. I configured 2.4.4 without any obvious problems (to me) but it fails on the make. Any ideas about the errors? Thanks! John /bin/sh ../libtool --mode=link gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o alloc.o clock.o debug.o error.o util.o file.o versuff.o -lm -lreadline -ltermcap -lnsl gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o alloc.o clock.o debug.o error.o util.o file.o versuff.o -lm -lreadline -ltermcap -lnsl file.o: In function `sanitise_filename': /usr/src/amanda-2.4.4/common-src/file.c:330: undefined reference to `__ctype_b' collect2: ld returned 1 exit status make[1]: *** [genversion] Error 1 make[1]: Leaving directory `/usr/src/amanda-2.4.4/common-src' make: *** [all-recursive] Error 1 [EMAIL PROTECTED]:/usr/src/amanda-2.4.4# --
Re: Using only one tape, full dump delayed
Ok Guys You're so smart and kind. I do hope 'dude' is not too rude (since it's not my native language). I found it after disassembling the drive (some of you may have a notch at the bottom of the case, the SUN-Version does not). BTW it does work fine for days already, and I like it. Cheers Urs On Mon, Mar 03, 2003 at 04:39:05PM +0100, Urs Forster wrote: The '72-144 Gbyte 4mm DDS-3 Autoloader Installation and User's Guide' says that a DDS-3 125m tape would hold 72GB uncompressed and 144GB compressed. Dude, that's the capacity of the whole *Library*! 6*12GB = 72GB, 6*24GB = 144GB. The tape itselfes says: 12GB native Capacity. That is correct, for a a DDS-3 tape drive with 125m tape. There is no switch inside the drive to enable/disable compression, Really? Not like this? http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg51068 so I assume when not using the 'c,u' option, it wont compress. You have some sort of front-panel display that will indicate compression during data write, don't you? Then there is the density switch (l,m,h) for low, medium and high. I don't think this has to do with compression. I believe this depends on the made of the tape? (I am not using any) HP has what seems to be a pretty good Solaris install doc here: http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg51069 -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Compiling on Slackware 8.1
I may have just answered my own question. Apparently it doesn't like installing over an old version. I installed it just fine on another Slackware box that didn't have the server or client on it before. I read something about it not liking the libs from the previous install so I tried the --disable-libtool but still got errors. I'm gonna get rid of the old installation and give it a try. John At 02:16 PM 3/5/2003 -0500, John Williams wrote: Hi all, I've been using Amanda-2.4.2 for several months and decided to upgrade. I configured 2.4.4 without any obvious problems (to me) but it fails on the make. Any ideas about the errors? Thanks! John /bin/sh ../libtool --mode=link gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o alloc.o clock.o debug.o error.o util.o file.o versuff.o -lm -lreadline -ltermcap -lnsl gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o alloc.o clock.o debug.o error.o util.o file.o versuff.o -lm -lreadline -ltermcap -lnsl file.o: In function `sanitise_filename': /usr/src/amanda-2.4.4/common-src/file.c:330: undefined reference to `__ctype_b' collect2: ld returned 1 exit status make[1]: *** [genversion] Error 1 make[1]: Leaving directory `/usr/src/amanda-2.4.4/common-src' make: *** [all-recursive] Error 1 [EMAIL PROTECTED]:/usr/src/amanda-2.4.4# --
Re: Tape mark error on LTO drive/tapes
On Wed March 5 2003 09:23, Brian Cuttler wrote:
From discussions on the list last week I'd understood* that
the tape length and I assume** by extension the filemark size
are used only to estimate tape capacity and determine what needs
to be bumped or if a level zero could be advanced.
What is the speed value used for ?
We have been told it is not used. Its just informational.
* Note, phrase I'd understood has no confirmed relevance to
reality and may not be worth the electrons it was written with.
These dumps were to tape Daily001.
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output
error]]. I am getting regularish error as below.
It seems to be related to a long pause in the cycles as the
last halfcut partition is dumped prior to taping
Here is my tapetype
define tapetype Ultrium {
comment Ultrium LTO
length 101632 mbytes
filemark 10 kbytes
speed 13884 kbytes
}
You may want to rerun the above after shutting the drives
compression off.
NB filemark WAS 0 kbytes, and as someone else has just queried
-- is this OK?
I set it up to 10 kbytes to actually 'make a space'
This also has little real effect. Since you have a fast drive, I'd
guess that you are not using a holding disk, so while the next hunk
is being compressed, the tape soldiers on, writing null bytes till
new data becomes available, thereby wasting storage space on the
tape. But thats just a SWAG, and no more connection to reality
than yours :)
And no the actual dump size is not bigger than the tape size
(unless I am badly miscounting something...)
Also, if you are compressing, and the drive is also compressing, the
data will grow by 10-20% and overflow the tape. We do not
recommend the use of the drives compressor since it hides the true
capacity of the tape from amanda.
8-
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: Daily005.
FAILURE AND STRANGE DUMP SUMMARY:
halfcutda0s3f lev 1 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)1:25
Run Time (hrs:min) 4:19
Dump Time (hrs:min)2:45 0:15 2:30
Output Size (meg) 20657.3 774.219883.1
Original Size (meg) 36118.5 1854.034264.5
Avg Compressed Size (%)57.2 41.8 58.0
(level:#disks ...)
Filesystems Dumped 10 8 2 (1:1
2:1) Avg Dump Rate (k/s) 2133.4 864.7 2262.7
Tape Time (hrs:min)0:15 0:02 0:13
Tape Size (meg) 6360.2 774.6 5585.6
Tape Used (%) 6.30.85.5
(level:#disks ...)
Filesystems Taped 9 8 1 (2:1)
Avg Tp Write Rate (k/s) 7066.8 5633.7 7325.2
NOTES:
planner: Incremental of wombat.bytecraft.au.com:da0s3f bumped
to level 2.
planner: Full dump of spyder.bytecraft.au.com:da0s4e promoted
from 3 days ahead.
planner: Full dump of spyder.bytecraft.au.com:da0s3g promoted
from 3 days ahead.
planner: Full dump of halfcut:da0s2f promoted from 3 days
ahead. planner: Full dump of halfcut:da0s2a promoted from 3 days
ahead. planner: Full dump of spyder.bytecraft.au.com:da0s2f
promoted from 3 days ahead.
planner: Full dump of wombat.bytecraft.au.com:da0s2a promoted
from 3 days ahead.
planner: Full dump of wombat.bytecraft.au.com:da0s2f promoted
from 3 days ahead.
planner: Full dump of spyder.bytecraft.au.com:da0s2a promoted
from 3 days ahead.
taper: tape Daily001 kb 6512800 fm 9 writing filemark:
Input/output error
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s
MMM:SS KB/s
-- -
halfcut da0s2a 0 59380 19968 33.6 0:151304.8
0:082597.4
halfcut da0s2f 0 483220 188640 39.0 3:18 954.2
0:286696.1
halfcut da0s3f 1 2365768014640698 61.9 98:502469.0
FAILED
spyder.bytec da0s2a 0 122080 97888 80.2 0:581696.8
0:185434.3
spyder.bytec da0s2f 0 637700 159936 25.1 2:291074.1
0:266130.4
spyder.bytec da0s3g 0 820224 27.3 0:00 696.3
0:02 104.2
spyder.bytec da0s4e 0 216370 174880 80.8 2:011444.1
0:286205.7
wombat.bytec da0s2a 0 79410 38752 48.8 0:44 872.9
0:103730.8
wombat.bytec da0s2f 0 299500 112864 37.7 5:32 340.1
0:205611.1
wombat.bytec da0s3f 2 114291505719648 50.0 51:091864.0
13:017325.2
(brought to you by Amanda version 2.4.3b4)
[... sig thats an infommercial, so I muted it :) ]
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.24%
question about upgrade
I was testing with amanda 2.4.3, but now need to use 2.4.4 for testing again. I compiled 2.4.3 and run make install. To get to 2.4.4, Do I need to uninstall/delete the old version?? Or just compile 2.4.4 and make install will overwrite the old files?? Thanks
Re: Selam
Title: Size Ozel Video Yeni porno filmi izlemek isterseniz BURAYA TIKLAYINIZ (18 yasinizdan buyuk olmaniz gerekmektedir)
Re: Amanda 2.4.4 + Cygwin = loss of hair...
Hi! I have it on Win2K -- not XP. However, in my experience, the inetd -d option doesn't do anything for you -- all that it does is allow you to see that something is, indeed, asking for amanda. inetd -d is shwoing something... rather a lot of something... Does it work if you run it as a service? I ran inetd --install-as-service (or whatever the command is) and the XP services control panel shows it as installed and running, but I am still getting the problem Steve
Re: Win32 Backup?
I've used Amanda before in a Unix-only shop, but now am interested in backing up Win32 clients. I see Amanda.Org still seems to hold the official line of use smbclient to backup Win32 clients, but there's a port of Amanda client to Win32 at http://sourceforge.net/projects/amanda-win32 which appears to have about 5-15 downloads daily for the last week or two. I can't tell you much, but I can tell that the official 2.4.4 version supports the cygwin environment. There have been a number of messages on this recently -- search the archives. Okay, I searched the archives. There is some conjecture that the Win32 client is not too recent, but there doesn't seem to be anything concrete. Someone else said the 'sbmclient' method gives problems when the user setup to do the backups on the Win32 client don't have permissions to back up the machine. Cygwin method requires first installing Cygwin on every client, right? smbclient method requires only creating a user on every client. So unless every Win32 client has Cygwin installed... would it be safe to say that The One Right Way to do Win32 backups is: - Setup a local administrator on the client (say, amanda) - Use smbclient at the server to backup - Don't use the Win32 client at SourceForge (it's out-of-date) ? -- pv
Re: Compiling on Slackware 8.1
At 10:47 PM 3/5/2003 +0100, Paul Bijnens wrote: John Williams wrote: I've been using Amanda-2.4.2 for several months and decided to upgrade. I configured 2.4.4 without any obvious problems (to me) but it fails on the make. Any ideas about the errors? Thanks! I run Amanda 2.4.4 on slackware 8.1 too. It's my tapeserver. It compiled without a hitch. You did make a make distclean before you did ./configure ..., did you? Just in case... Paul Yep, tried that. I even backed down to the original binutils, gcc, make, etc.. that came with Slackware 8.1. I've also removed the old version of Amanda but make still dies in the same place. It must be something I've installed on my Slackware tapeserver because it compiled fine on another Slackware 8.1 box. Thanks! John --
help on amrecover
Hi My machine runs amanda-2.4.4. amrecover reports: EOF, check amidxtaped.debug file on barracuda amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract list - child returned non-zero status: 1 amidxtaped.*.debug: amidxtaped: debug 1 pid 12985 ruid 550 euid 550: start at Wed Mar 5 14:19:03 2003 amidxtaped: version 2.4.4 amidxtaped: time 0.000: SECURITY USER root amidxtaped: time 0.000: bsd security: remote host barracuda user root local user general amidxtaped: time 0.001: amandahosts security check passed amidxtaped: time 0.001: CONFIG=testSet amidxtaped: time 0.001: LABEL=testSet1 amidxtaped: time 0.001: FSF=1 amidxtaped: time 0.001: HEADER amidxtaped: time 0.001: DEVICE=/home/general/testSet1 amidxtaped: time 0.001: HOST=^barracuda$ amidxtaped: time 0.001: DISK=^/junk$ amidxtaped: time 0.001: DATESTAMP=20030305 amidxtaped: time 0.001: END amidxtaped: time 0.002: amrestore_nargs=0 amidxtaped: time 0.002: Ready to execv amrestore with: path = /usr/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = /home/general/testSet1 argv[4] = ^barracuda$ argv[5] = ^/junk$ argv[6] = 20030305 amrestore: error reading file header: Is a directory amidxtaped: time 0.006: amrestore terminated normally with status: 2 amidxtaped: time 0.006: rewinding tape ... amidxtaped: time 30.105: tape_rewind: rewinding tape: /home/general/testSet1: Inappropriate ioctl for device amidxtaped: time 30.105: pid 12985 finish time Wed Mar 5 14:19:34 2003 Could anyone please give me an interpretation and how to correct it?? This is a tapeless backup. (That's why it has /home/general/testSet1) Thanks in advance.
Re: Win32 Backup?
I've never had to do this, but an approach that I'd probably persue would be to use Symmantec/Norton Ghost to create occasional disk images that would get xferred via Samba to a *ix filesystem. I'd try real hard to keep important data off of the M$ machine's local disks.
