Re: Request to nachine timed out.
You are using gnutar. It's slow (es. an incremental with gzip compression) Make sure you have set your timeout to something large I have dtimeout set to 1800 . Also, did you check /tmp/amanda on the client for debug files (sendbackup.*.debug ) ? If so, what's in the last (timewise) sendbackup.*.debug files ? There should be one for sdc1 and one for sda2. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 It's solved, I hope ;) I started this command manually time /bin/gtar --create --directory /raid --listed-incremental /usr/local/amanda242/var/amanda/gnutar-lists/machinesdc1_0.new --sparse --one-file-system --ignore-failed-read --totals --file /dev/null --exclude-from /usr/local/amanda242/exclude.gtar . /raid has about 17G and time said: real421m18.894s user223m18.650s sys 7m54.520s so I think I need to set dtimeout to more. thank you all tom
Re: Can I use only one tape for backing up all the week?
* John R. Jackson [EMAIL PROTECTED] (Wed, Feb 07, 2001 at 09:14:26PM -0500) Now, am not 100% certain on how taper does write the files to tape ... Very quick review: Rewind Read the label and verify Rewind Write a new label and tapemark Write a header, image and tapemark Write a header, image and tapemark ... Write the trailing label, tapemark and quit (leaving the tape where it is) ... Why not [save] the last one in tapelist, and/or amount of tape used? That's the plan. Why not go one step further, and write this information in the tapelabel. Of course, this breaks if fsf is broken ... so, now you are effectively doing an 'mt fsf last field' to get to end of tape ... True. The problem is that the drive may screw up. You may tell it to skip 37 files and it skips 36 (or 38, or 10, or 100 ...). So you have to Is this still the case with newer tape drives ? I cannot remeber ever having this probelm with exabyte , mammoth or LTO tapes. Come to think of it, I cannot even remeber it ahppening in the huge reel-to-reel tapedrive we used way back when, and that was a pretty bad piece of work ;) Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __0 Oh my God, the bomb has just dropped =`\, And everybody climbed right on top (=)/(=) Singing,"What a beautifull country
Re: Can I use only one tape for backing up all the week?
* Simon Mayr [EMAIL PROTECTED] (Thu, Feb 08, 2001 at 01:20:52PM +0100)
What would it take to have some sort of config option that did exactly
that? ...
Nothing. It's already there. Just leave the tape out of the drive and
make as many runs as you want into the holding disk.
eg
crontab:
15 0 * * * /path/to/smartscript
smartscript:
if holdingdisk space is to small
/path/to/amdump to_tape_config \
mt offline ( send extra big mail to the guy who changes the tape:)
else
/path/to/amdump to_holding_config
How about
As abovem 2 configs, each identical exept for allowed tapestring;
if(holdingdisk space is full){
amflush totape mt rewoffl alert-person-to-change-tape
}
amdump todiskconfig
also, finetune this so that if a holdingdisk is more full than fits a
single tape, you amflush oldest partitions first until tapefull
(e.g. by moving the latest dumps to a different dir, amflush nd move back).
Again:
See the note above and have in mind that this can only be usefull for
poeple whose backup device capacity is much more higher than the backup
load from a couple of days.
And for people who can afford to loose a couple of days worth of backups if
the holdingdisk crashes.
Q: what to do if "all" is to big, you have more than 26 areas and the
one you really want to flush is to new to be listed?
Whats the deal with the 26 areas ?
Cannot amflush flush more than 26 areas to tape ?
What do you mean with area ?
Gerhard, [@jasongeo.com] == The Acoustic Motorbiker ==
--
__O I spoke about wings ... You just flew
=`\, I wondered, I guessed and I tried ... You just knew
(=)/(=) I sighed ... And you swooned
I saw the crescent ... You saw the whole of the moon
Re: Amanda Client on FreeBSD
IMHO, on BSD, the culturally right way to set up AMANDA is to conform to the BSD Way as much as possible. This means: use dump(8). On FreeBSD 4.2 and NetBSD 1.5, /sbin/dump is sgid tty, but not suid: -r-xr-sr-x 2 root tty 331452 Nov 20 07:06 /sbin/dump leave the permissions on the raw devices intact, as 640 group operator, e.g. crw-r- 2 root operator 13, 0x0002 Jan 15 13:25 /dev/da0s1a crw-r- 1 root operator 17, 0 Dec 6 18:08 /dev/rsd0a put the user that amanda runs as in group operator. I run amanda as 'amanda', but some people run amanda as 'operator'. It really doesn't matter. Note that all you have to do for this part is put amanda/operator in group operator. The original scheme called for the people who ran dump and changed 9-track tapes to be in group operator; these people had permission to read the raw disks, but not necessarily root. All that said, I concur with the other debugging hints. Note particularly that there are two levels of permission checking: amandad on the client choosing whether to accept the check/dump request the operating system deciding whether to permit amanda to run dump and read from the disk In almost all cases I've seen, the problem is the first part. Once you get by that, amcheck will get you clear diagnostic output - one of the functions of selfcheck is to verify that user amanda can read/write dumpdates and read the raw disks (when the service is dump). For example, I just chmod'd a raw disk to 0600 on a client, ran amcheck, and got this output: Amanda Backup Client Hosts Check ERROR: [hostname]: [can not access /dev/rsd0a (sd0a): Permission denied] Client check: 6 hosts checked in 1.556 seconds, 1 problem found. Greg Troxel [EMAIL PROTECTED]
Re: Can I use only one tape for backing up all the week?
Le 07/02/2001 a 15:22 -0500 , John R. Jackson ecrivait : Second is that positioning sounds nice and logical to a programmer or someone only used to working with disk, but when you throw in the reality of a physical tape device, bad stuff starts to happen. On WinNt an Macs, that's the way Dantz's Retrospect works for years. I never, never, lost a tape. Otoh, mt(1) blows me a tape so badly that I had to physically open the DAT drive to eject it :-( -- Xavier HUMBERT - Systemes et Reseaux | [EMAIL PROTECTED] INJEP | [EMAIL PROTECTED]
Re: Planner - balance suggestions? FOLLOWUP
On Tue, 30 Jan 2001, Bill Carlson wrote: Hey all, I've got a puzzler here, any suggestions on how to handle this would be great (except using gnutar). I'm using amanda-2.4.2 on Solaris 2.6, works great. However, my file systems are such that I have three file systems that are an order of magnitude larger than the rest(18GB vs 2 GB). The problem comes to the balance calculation. The larger file systems never get promoted, so they are left to be dumped until they are actually due. That isn't a problem until 2 biggies are due on the same day, resulting in backup running until noon. :) I had thought no big deal, I'll set the dumpcycle on the biggies to a shortened interval and planner will figure it out. But, the balance size is calculated based on the estimated runspercycle and total size of level 0 dumps, so that adjustment didn't change anything other than increase the frequency of "overtime" backups. No help. As always, in the act of describing the problem, I think I see the solution. I should change my dumpcycle to shorter value and override that on my smaller filesystems to a longer value. That should bump up the balance calculation. I've been running with this scheme for a week now and it is working as I expected. The "biggie" file systems are getting promoted as time/space allow and amdump finished before 8 am every day. Yes! Bill Carlson -- Systems Programmer[EMAIL PROTECTED]| Opinions are mine, Virtual Hospital http://www.vh.org/| not my employer's. University of Iowa Hospitals and Clinics|
Re: Can I use only one tape for backing up all the week?
Gerhard den Hollander wrote:
How about
As abovem 2 configs, each identical exept for allowed tapestring;
if(holdingdisk space is full){
amflush totape mt rewoffl alert-person-to-change-tape
}
amdump todiskconfig
i think this should work.
btw:
how do you non-interactivly amflush ?
at my site, we do something like that, but instead of flushing (as it
should be) we leave the incrementals on disk and delete them together
with their index files, if the holding disk space is running low
also, finetune this so that if a holdingdisk is more full than fits a
single tape, you amflush oldest partitions first until tapefull
(e.g. by moving the latest dumps to a different dir, amflush nd move back).
to call it by name:
include some errorchecking and foolproofness
Again:
See the note above and have in mind that this can only be usefull for
poeple whose backup device capacity is much more higher than the backup
load from a couple of days.
And for people who can afford to loose a couple of days worth of backups if
the holdingdisk crashes.
That's true (!!). But at least the data is on two different machines.
And hopefully the holding disk is not crashing at the same time as the
backup client crashes.
Q: what to do if "all" is to big, you have more than 26 areas and the
one you really want to flush is to new to be listed?
What do you mean with area ?
John R. Jackson said:
At your convenience, run "amflush" and select "all" instead of a specific holding area.
and I picked up the word area :-)
it means the place where all the backup images of a run of amanda
reside. namely the directory in the holding disk named after the
corresponding date.
Cannot amflush flush more than 26 areas to tape ?
As amflush presents you a list with the directorys in the holding disk
all with a indicating letter (A-Z) there is a maximum of 26 visible
holding "areas". they are sorted by age (or alphabetically whats the
same in this case). So cou can't *see* the 27th area and therefore can
not flush it. (I DONT know if it WOULD be flushed when you select all)
Whats the deal with the 26 areas ?
Well, ... uh ... more than 26 unflushed backups ... ?!
As said above, we keep as many incrementals as possible in the holding
disk for no specific reason other than lazyness. As Incrementals are not
big, a large holding disk can hold a lot of them.
Gerhard, [@jasongeo.com] == The Acoustic Motorbiker ==
Simon
Re: Can I use only one tape for backing up all the week?
* Simon Mayr [EMAIL PROTECTED] (Thu, Feb 08, 2001 at 03:28:07PM +0100) how do you non-interactivly amflush ? echo "all" | amflush -f whatever-your-config-is (I think , I haven't tried it ) at my site, we do something like that, but instead of flushing (as it should be) we leave the incrementals on disk and delete them together with their index files, if the holding disk space is running low B ;) Cannot amflush flush more than 26 areas to tape ? As amflush presents you a list with the directorys in the holding disk all with a indicating letter (A-Z) there is a maximum of 26 visible holding "areas". they are sorted by age (or alphabetically whats the same in this case). So cou can't *see* the 27th area and therefore can not flush it. (I DONT know if it WOULD be flushed when you select all) OK, I never realized that . BTW I checked the source, and it looks like ALL will indeed dump all, so something like echo "all" | amflush -f whatever-your-config-is should do the trick (well actually, you have to type Y as well I think., Maybe you need to do something with expect ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
amrmtape
I'm trying to reuse a tape, so first i amrmtape its label: Viernes01, Semanal is the configuration directory. I get this output from amrmtape: amrmtape Semanal Viernes01 amrmtape:preserving original database in informacion.orig.2014(exported). amadmin: WARNING: input is from different org: Cirsa_Diario if after doing it i do amlabel Semanal Viernes01 rewinding, reading label Viernes01, tape is active rewinding tape no labeled so it didn't rm the label when i did amrmtape. can anybody helpme???
Re: Can I use only one tape for backing up all the week?
* Simon Mayr [EMAIL PROTECTED] (Thu, Feb 08, 2001 at 04:14:39PM +0100) something like echo -en "A\nY\n" | /path/to/amflush -f config is working. ( Arrrgh again! ;) Allright ... What about the amanda database if i set up a "flush to nirvana" config with /dev/null. Would it do any better or other than erase the images, the index files and the log files. dunno , according to the manpages it will ``update the databases, and send email similar to amreport'' It also makes a ncie printout if you have a label specified (though it's rather silly to stick a printout label to /dev/null ) I think I read somewhere that the behavior of amanda has changed about the meaning of /dev/null. Amanda didn't let me use the /dev/null device, ioctl error or something, cannot rewind, wrong tape etc., so I came up with the simply-delete-the-stuff solution ... Dunno, Solaris gives no tape loaded errors if you try to do mt commands on /dev/null , which is reasonable ;) (well actually, you have to type Y as well I think., Maybe you need to do something with expect ;) what's "expect" ? expect is a ltittle tool that lets you automate interactive programs expects sits there, reads the utput from the program, and feeds it the required input. e.g. UUCP uses it to talk to the dialout device Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Adic Scalar 1000
Just wondering if anyone has ever used Amanda with Adic's Scalar 1000 unit. The Adic uses DLT 8000 tapes. Server OS does not matter to me, I can use whatever flavor of Unix -Adrian
Re: need instructions for restore
I am trying to come up with a procedure to: 1) detect what tape the needed backup is on. amadmin config find hostname disk 2) mount the tape amtape config slot slot 3) perform the restore amrestore -p $TAPE hostname disk [date] | /the/restore/program ... Tal John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Failing on relatively large partition
First, quickly grab the amandad*debug file for this run. With luck, it will still be for the backup of /home. It has a command we'll use shortly. So, sendbackup for /home begins at 23:08, amanda quits and sends out the MAIL REPORT 30 minutes later at 23:38 with the "[data timeout]" error, Which makes sense. That's the 30 minute "the client stopped talking" timeout (dtimeout in amanda.conf). and sendbackup.debug records the "index tee cannot write [Broken pipe]" error at 00:16, well after amanda was done for the night. That's because the other end of the connection (dumper) was gone. It is interesting, though, that it may have actually run a while and finally tried to write something and that got the error, as compared with just another timeout but from the client side. Is it possible I've got some sort of timeout value wrong someplace? Any suggestions on where to look to change it? I'd sure like to know what the two tar's (the one dumping and the one generating the index) were doing all that time. You might try changing dtimeout in amanda.conf (this is 2.4.2, right?) to 3600 (one hour). That would cover the time from the start of the dump to the broken pipe message. You can test this ahead of time like this (and maybe catch it in the act of goofing off): * In amandad*debug will be some lines like this (yours will say GNUTAR, I think): SERVICE sendbackup OPTIONS hostname=fortress.cc.purdue.edu; DUMP /home/fortress/a 1 2001:2:5:4:48:48 OPTIONS |;bsd-auth;index; * Take the OPTIONS and DUMP/GNUTAR line and copy them to a file on the client. Add "no-record;" to the end of the DUMP/GNUTAR line you got above: DUMP /home/fortress/a 1 2001:2:5:4:48:48 OPTIONS |;bsd-auth;index;no-record; That will prevent sendbackup from updating the last dumped information. * Run sendbackup by hand as the Amanda user like this: /path/to/sendbackup -t /the/file /tmp/index.out The data stream (backup image) will go to /dev/null. Stdout will get the index. Stderr will get the messages stream (output from the backup program). * See below for how to run truss on the various processes. That may give you an idea if they are really running or not. Or you could run lsof to see if the file offsets are going up. If all this works, we need to go back to the server side and try from there: * Find the FILE-DUMP line in amdump.NN for this file system (if it says PORT-DUMP, I'll have to rethink this). Copy that line to a temp file and make the same "no-record;" change you did above. * The second argument on the line is the holding disk file name. Change that as needed. * Run dumper by hand as the Amanda user with the config name as an arg: /path/to/dumper config /file/dump/file * Remove the "log" file that driver created or your next real Amanda run will be unhappy. If it looks like nothing is happening, which would be indicated by the holding disk file not growing, go over to the client and attach a debugger to sendbackup, the GNU tar doing the dump (the one with the 'c' flag) and on the GNU tar doing the catalogue (the one with the 't' flag). Using gdb, it would be: gdb /path/to/sendbackup PID # or /path/to/GNUtar Once inside, do a "where" and save (copy/paste) the stack traceback for posting back here. Then "exit" to let it go again. It would be good if both Amanda and GNU tar were compiled with -g for this, otherwise the tracebacks may not be very useful. You might also run truss (truss -o /tmp/xxx.out -p PID) on each of the processes for a short period (enough to get some output) to see if and what they are doing. Chris Hobbs John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Failing on relatively large partition
His log also shows started index creator: "/usr/bin/gtar -tf - 2/dev/null |sed -e 's/ ^\.//'" index tee cannot write [Broken pipe] Might this be the reason ? No, that's a symptom. It says the other side of the connection (dumper on the server side) went away, which we knew. Chris, what happens if you try to run this manually (e.g. sh /usr/bin/gtar cf /home | /usr/bin/gtar -tf - 2/dev/null |sed -e 's/ ^\.//'" ) [John, is this the right way to test ?] See my other posting. It's very difficult to set up a shell based emulation of what sendbackup does, but is not all that hard to just run it itself. There is a lot of piping and multiplexing going on in this process. It is entirely possible we've got some kind of deadlock going on. Gerhard John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
AIT-1 tapetype, FAQ-O-Matic, and compression
Just in case no one has noticed yet, FAQ-O-Matic is currently broken.
Thus...
I just got a SDX-300C (35GB native AIT-1) drive for archival dumps. Does
anybody have any experience with these regarding a realistic guesstimate
of hardware compressed capacity? Tapetype?
Also, I'm running RedHat6.2 with an updated mt-st-0.6. Am I right in
assuming that, despite no obvious change in the output of 'mt stat',
'mt compression {0|1}' is actually turing compression off/on? There *is*
a bit of an increase in throughput with it "on".
Thanks, all.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: Failing on relatively large partition
1.13.17, which I understand is acceptable, correct? That's my understanding. I think 1.13.19 has some performance improvements and an obscure bug fix, but for what you're seeing I don't think they apply (I think you're seeing a hang, not a performance problem). Should have been more clear here - svhsfiles is the tapehost as well, so no networking issues ... OK. That simplifies things. There are still networking issues, though. Even with client and server on the same box, Amanda doesn't do anything special and still sends the data through "the network", it's just that in this case it's the loopback interface in the kernel. Total bytes written: 10240 (10kB, ?B/s) That seems a bit odd. I think I had you run it in a way that would do a full dump. [root@svhsfiles /root]# cat /tmp/empty 981646673 And that's not what I expected to see in the file, but I'm out of my area when it comes to GNU tar. Maybe someone else can chime in here? Chris Hobbs John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Request to nachine timed out.
It's solved, I hope ;) I started this command manually ... and time said: real421m18.894s user223m18.650s sys 7m54.520s so I think I need to set dtimeout to more. The dtimeout variable controls how long dumper will wait **with no input** from the client. A "data timeout" error means dumper waited 30 minutes (or whatever dtimeout is set to) and didn't hear *anything* from the client. It has nothing to do with the total time it takes to do the dump. Feel free to crank up dtimeout, and I hope that gets you going, but I'm not sure it will. tom John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: need instructions for restore
I am trying to come up with a procedure to: 1) detect what tape the needed backup is on. 2) mount the tape 3) perform the restore I am not sure what commands I need to run for each so I will be able to write a script to do the job. Tal "John R. Jackson" wrote: Does anyone have simple instructions on how to perform a restore with Amanda and a tape changer ? The Amanda restore programs (amrestore and amrecover) do not (yet) know about tape changers, so you have to use some other method (e.g. amtape) to get the tape mounted "by hand" before using them. Is that what you were looking for? Tal John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Tal Ovadia Jalan Network Services Inc. Phone: (818)-597-6301 --- Why Oh Why didn't I take the Blue Pill...
instructions
Help, Are there any good instructions on how to install, and restore using amanda ? Tal
Re: Adic Scalar 1000
I'm in the last stage of testing a script I wrote to use a Scalar 100 with Amanda. I would assume the hardware will respond in a similar fashion. I plan to post it to amanda-users tomorrow (need to comment some things better, etc). In the mean time, can you use the 'mtx status' program (ver. 1.2.10) and see if it shows output something like this: [root@reubens /root]# mtx -f /dev/sg2 status Storage Changer /dev/sg2:2 Drives, 31 Slots ( 1 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1 IMPORT/EXPORT:Empty Storage Element 2:Full :VolumeTag=01 Storage Element 3:Full :VolumeTag=02 Storage Element 4:Full :VolumeTag=03 Storage Element 5:Full :VolumeTag=04 Storage Element 6:Full :VolumeTag=05 Storage Element 7:Full :VolumeTag=06 Storage Element 8:Full :VolumeTag=07 Storage Element 9:Full :VolumeTag=08 Storage Element 10:Empty Storage Element 11:Empty Storage Element 12:Empty Storage Element 13:Empty Storage Element 14:Empty Storage Element 15:Empty Storage Element 16:Empty Storage Element 17:Empty Storage Element 18:Empty Storage Element 19:Empty Storage Element 20:Empty Storage Element 21:Empty Storage Element 22:Empty Storage Element 23:Empty Storage Element 24:Empty Storage Element 25:Empty Storage Element 26:Empty Storage Element 27:Empty Storage Element 28:Empty Storage Element 29:Empty Storage Element 30:Empty Storage Element 31:Full :VolumeTag=31 If it does, then hopefully with the chg-zd-mtx script I'm finishing up you will have full barcode support. That (and a 9 slot capacity) is what I had to modify. Let me know what you find... On Thu, 08 Feb 2001, Adrian Oneil wrote: Just wondering if anyone has ever used Amanda with Adic's Scalar 1000 unit. The Adic uses DLT 8000 tapes. Server OS does not matter to me, I can use whatever flavor of Unix -Adrian -- Jason Hollinden SMG Systems Admin
Re: Failing on relatively large partition
"John R. Jackson" wrote: * Run sendbackup by hand as the Amanda user like this: /path/to/sendbackup -t /the/file /tmp/index.out Two hours into this now and it seems to be running somewhat correctly - strace (no truss here) shows and has shown a lot of file activity on the first gtar process since beginning. However, the gzip process has only recently been showing any activity (as in well over an hour after the gtar process began). The second gtar shows lots of reads and writes now, but it doesn't appear to have begun doing anything until after the gzip started. This is based on the observation that for the longest time an strace on gzip and the second gtar only showed something like "read(0, ". My assumption is that the process looks something like the following (lots of switches stripped for brevity)? gtar -c /home | gzip | gtar -tf - /dev/null If this is the case, then the culprit appears to be the first gtar, as it has taken forever to start piping data into gzip, and thus nothing was written to the last pipe and dumper timed out. If these assumptions are correct, any suggestions? If I've messed up the logic, I'll be happy to try to provide more info. -- Chris Hobbs Silver Valley Unified School District Head geek: Technology Services Coordinator webmaster:http://www.silvervalley.k12.ca.us/chobbs/ postmaster: [EMAIL PROTECTED]
amanda mailing list
Just a little pet peeve I would like to ask about. Would it be possable to put an [amanda-users] in the subject of everything sent to the mailing list? I know that mailman is capable of this but I am not shure of the capabilitys of majordomo. Regards, Ryan Williams
Re: amanda mailing list
On Thu, 8 Feb 2001, Ryan Williams wrote: Just a little pet peeve I would like to ask about. And this request happens to be a pet peeve of mine. Would it be possable to put an [amanda-users] in the subject of everything sent to the mailing list? I know that mailman is capable of this but I am not shure of the capabilitys of majordomo. The list identification is already in the Sender: header. If you need to filter your mail, please use a mail filter. There are plenty of them out there, procmail is one popular choice. Cluttering the subject header with redundent information already present in another header only forces useful subject header data over leaving less of where it can be seen in everyone's inbox lists. Please use the right tool for the right job rather than inconveniencing the rest of us for your convenience. -Mitch
Re: does any one know the setting of HP DDS-4 SureStore DAT40i Internal DAT drvie in amanda.conf?
Dear all,
I have just bought a new HP DAT40i. May I know if someone can tell me its
setting for the amanda.conf file?
Thanks for your help.
Yours,
Richard Ao
Newsbook Limited
- Original Message -
From: "Mike O'Shaughnessy" [EMAIL PROTECTED]
To: "Bernhard R. Erdmann" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; "amanda-users" [EMAIL PROTECTED]
Sent: Tuesday, December 12, 2000 3:57 PM
Subject: RE: does any one know the setting of HP DDS-3 SureStore DAT24i
Internal DAT drvie in amanda.conf?
I have these drives - here is the tapetype
define tapetype HP-DAT24 {
comment "HP SureStore DAT24, no compression"
comment "DDS-3 125 meter tape"
comment "produced by tapetype program"
length 11703 mbytes # 12 GB
filemark 0 kbytes
speed 1000 kbytes
}
Re: amanda mailing list
The alternative is to do what my local LUG does would be to add: * X-Mailing-List: [EMAIL PROTECTED] archive/latest/4749 (naturally amand-users wouldn't claim to be linuxsa :-P) And filter on that...every now and then someone will send you something directly and it will end up in the wrong box if you only filter on sender. However, if that header is kept your filtering doesn't break regardless of where the mail is sent from. DL
Re: amanda mailing list
On Thu, Feb 08, 2001 at 09:17:35PM -0500, Ryan Williams wrote: Just a little pet peeve I would like to ask about. Would it be possable to put an [amanda-users] in the subject of everything sent to the mailing list? I know that mailman is capable of this but I am not shure of the capabilitys of majordomo. Regards, Ryan Williams Majordomo does it quite nicely. In amanda-users.config, add a line that says subject_prefix = [amanda-users] Tho I myself would prefer to see a more terse prefix ... maybe [AMU]. Many mailers display only the first xx characters of the subject line on the index screen. -- - Dan Wilder [EMAIL PROTECTED] Technical Manager Correspondent SSC, Inc. P.O. Box 55549 Phone: 206-782-7733 x123 Seattle, WA 98155-0549 URLhttp://www.linuxjournal.com/ -
Inappropriate ioctl for device
Dear all, When I try to rewind the tape, I have the following error message. Do you have any idea what is wrong? ./amlabel DailySet1 DailySet100rewindingamlabel: rewinding tape: Inappropriate ioctl for device Yours, Richard Ao Newsbook Limited
Re: Client Installation
On Feb 8, 2001, "John R. Jackson" [EMAIL PROTECTED] wrote:
It's too bad tar doesn't have a flag that enables certain errors to be
logged (which Amanda would note but not consider fatal) but not cause
a non-zero exit.
It does. It's called --ignore-failed-read. It was a bug in older
versions of tar that it caused non-zero exit. IIRC, it's fixed in
1.13.19.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Failing on relatively large partition
On Feb 8, 2001, Chris Hobbs [EMAIL PROTECTED] wrote:
If this is the case, then the culprit appears to be the first gtar, as
it has taken forever to start piping data into gzip
That's indeed the way GNU tar works.
If these assumptions are correct, any suggestions?
Increase dtimeout (new in 2.4.2).
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Inappropriate ioctl for device
On Feb 9, 2001, "richard" [EMAIL PROTECTED] wrote:
./amlabel DailySet1 DailySet100
rewinding
amlabel: rewinding tape: Inappropriate ioctl for device
What is the tape device configured in DailySet1/amanda.conf?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Inappropriate ioctl for device
Dear Alexandre,
Thanks for your email. I have found out that you are right to the type
setting in amanda.conf. I have not set
tapedev "/dev/nst0"
before. Now, it can be labelled.
Yours,
Richard Ao
Newsbook Limited
- Original Message -
From: "Alexandre Oliva" [EMAIL PROTECTED]
To: "richard" [EMAIL PROTECTED]
Cc: "amanda-users" [EMAIL PROTECTED]
Sent: Friday, February 09, 2001 12:37 PM
Subject: Re: Inappropriate ioctl for device
On Feb 9, 2001, "richard" [EMAIL PROTECTED] wrote:
./amlabel DailySet1 DailySet100
rewinding
amlabel: rewinding tape: Inappropriate ioctl for device
What is the tape device configured in DailySet1/amanda.conf?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
No Subject
Dear sir, I am using the amdump to do the backup. But, in my /home directory, the size is about 3 Gi and I would like to backup them into two part:Part(a): /home/a to k Part(b): /home/l to z How can I do this in my disklist file? Yours, Richard Ao
