Re: condense many tapes to few
On Wed, 11 Jul 2001, Toby Bluhm wrote: >Date: Wed, 11 Jul 2001 09:14:53 -0400 >From: Toby Bluhm <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: condense many tapes to few > >What would be the best way to pull full backups from several different >tapes & reassemble them onto one or two tapes? These tapes would then be >archived. Ideally, it would be nice if amrestore would work in the >normal ways with the reassembled tapes. I have a script which tries to do this. It assumes you have enough space on your holding disk to hold an entire archive set. I do, but I run two backup sets (one for servers, one for workstations.) I'm not entirely certain the script still works for amrestore. It used to, but I've enhanced that section recently so that it recognizes sessions still on the holding disk, and I haven't tested those changes yet. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: scsi card for dat drive on linux
On Wed, 27 Jun 2001, Tom Strickland wrote: >Date: Wed, 27 Jun 2001 11:40:42 + >From: Tom Strickland <[EMAIL PROTECTED]> >To: amanda <[EMAIL PROTECTED]> >Subject: scsi card for dat drive on linux > >In my previous post I mentioned that we're looking to get an HP >Surestore. The suppliers said that nothing less a rather expensive >Adaptec card would do. If we need to buy an expensive Ultra-Wide card, >we will. I would have thought that it was overkill for the speed that >such a drive can manage? Am I missing something? Are the lower priced >cards of such inferior quality that it would be a mistake to buy them? >BTW - no SCSI hard drives in use at the moment - cannot afford them. Well, one thing I learned is if your device is an UltraWide, and your interface card is a slow-narrow, you'll have to buy expensive adapters and cables to connect them together. The costs of these additional items and the instability they can add to your system (ie in time debugging the scsi chain, having the connectors fall off the back of the card due to the extra weight, etc) can drive your costss beyond what the UltraWide card would have cost you in the first place. I had to run a Scsi2 tape from a Scsi1 controller at a previous job, and even that small step was a pain. The on-device terminators didn't work and I had to add a second external terminator. The whole chain tended to hang and I'd have to powercycle the whole box to free it. (Luckily the system itself was IDE-disk based so I could always gracefully unmount everything except the scsi holding disk. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: another problem from upgrading server to 2.4.2p2
On Mon, 7 May 2001, John R. Jackson wrote: >Date: Mon, 07 May 2001 17:28:33 -0500 >From: John R. Jackson <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: Paolo Supino <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED] >Subject: Re: another problem from upgrading server to 2.4.2p2 > >> Yesterday, the daily amcheck run gave me the following error: >>sh: /tmp/amanda/amcheck.main.16130: No such file or directory >>amcheck: mail command failed: /usr/bin/Mail -s " AMANDA PROBLEM: FIX > Isn't "/usr/bin/mail" usally lowercase? -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Local Filesystem
On Sun, 8 Apr 2001, Marty Shannon, RHCE wrote: >True enough. (Though with all the other things that have been said >about Linux dump, I'm not sure I would trust it to do that correctly.) > >> But, the version I'm using doesn't >> store dump levels for anything except a full partition or mountpoint. >> A subdirectory below the mountpoint can be backed up with dump but the >> dump timestamps aren't recorded. Or something like that. > >But using it that way would render it useless with Amanda. Only if the directory involved demands incremental dumps. On my previous workstation I had an 8gig partition that was used mostly for holding disk and cdrom burner workspace, but I had one directory there I needed to backup. It was a perl database used by the machine's website and doing a full-backup of the whole directory was needed, anyway. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Local Filesystem
On Sat, 7 Apr 2001, Marty Shannon, RHCE wrote: > >Dump can *only* access the local filesystem: it reads the actual >partition, and thus only sees mount points as directories. > This depends upon the version of dump and the platform. Linux dump groks directories anywhere on the disk, not just partition device names or mount points. But, the version I'm using doesn't store dump levels for anything except a full partition or mountpoint. A subdirectory below the mountpoint can be backed up with dump but the dump timestamps aren't recorded. Or something like that. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: self check request timed out
On Tue, 23 Jan 2001, Ben Hyatt wrote: > >amcheck returns the following on my tape server host (atsun01) e450 2.7 >solaris: > >(*insecure*)amanda@atsun01:/usr/local/etc/amanda/atlab$ amcheck atlab >Amanda Tape Server Host Check >- I could be smoking something here, but I seem to recall seeing this (*insecure*) crap on my Solaris 2.6 box here, and my amchecks failed until I got rid of the (*insecure*) by fixing my hostname lookups for my own host. I didn't anyone mention that (*insecure*) flag. I think Solaris doesn't like its hostname and it's being pissy about launching amandad or something. Then again, I could be thinking of something else completely, too. It's been months since I touched that box after I got it working. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Amanda should know better...
I've got a 2.4.2 amanda server using samba to backup the C:\ drive
of an NT workstation. That user's machine has C:\ set as one 8gig
partition, and it's 6gig full. My tapes have just over 4 gig
capacity compressed. (Of course there are many other partitions in this
backup set, but those aren't the problem.)
Amanda pulls the data from the NT disk, and writes it to 5 gigs
worth of compressed disk, in 6 chunks. Now, the compressed sum
of all these sections is already well beyond what the tapetype
says my tape can handle.
So, why is amanda even trying to write 5 gigs worth to a tape it
knows can only hold 4 gig? Isn't it checking?
It keeps running into EOT (like, duh) and it reschedules the same
machine the next day. I've looked at the past week's backups and
all I have is one or two very small incrementals, and repeated failed
attempt to backup this same NT box.
I thought the planner was supposed to be more intelligent than this?
Here's the line for this disk from the amstatus report:
joi://janet/c$0 5619328k writing to tape (18:04:52)
Here's the end of the dump log:
| tar: dumped 55234 files and directories
| Total bytes written: 6937226240
sendbackup: size 6774635
sendbackup: end
INFO taper tape DailySet201 kb 4824992 fm 3 writing file: No space
left on device
FAIL taper joi //janet/c$ 0 [out of tape]
ERROR taper no-tape [[writing file: No space left on device]]
And here's the tapetype:
define tapetype EXABYTE-Eliant-820 {
comment "EXABYTE-Eliant-820 ( EXB-85058HE- Rev 01 ), 120m
tape, Adaptec AIC-7860 Ultra SCSI host adapter"
length 4403 mbytes
filemark 102 kbytes
speed 909 kbytes
lbl-templ "/usr/local/etc/amanda/DailySet2/EXB-8500.ps"
}
Here's the schedule:
GENERATING SCHEDULE:
joi //janet/c$ 11344 0 1970:1:1:0:0:0 3445388 114846
joi //treacy/c2$ 11344 0 1970:1:1:0:0:0 849557 28318
joi //mheitkamp/backupd$ 11343 0 1970:1:1:0:0:0 0 0
Why is amanda blowing the tape size by 25%? Why is it being
stubborn about doing this disk, a low-priority user workstation,
instead of doing the medium and high-priority file servers?
--
Joi EllisSoftware Engineer
Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED]
No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried. Anything
that kicks a monopoly in the pants has got to be good for something.
- Chris Johnson
Re: Weird illustration of peculiar interactions :-}
On Thu, 18 Jan 2001, Martin Apel wrote: >On Wed, 17 Jan 2001, Joi Ellis wrote: > >> >> I amflush these to tapes to send to offsite storage. >> I've already done two tapes from this batch, I have four >> left to do. > >That's a nice idea, but I have more data to back up than fits on the >holding disk, so I have to flush some dumps to tape in order to dump >all filesystems completely. > >Martin So? I was trying to point out that simply selecting the biggest dump may not give you the best packing. Often, the few tapes contain four or five smaller dumps and can obtain a 99.8% usage rate. The total amount of data to be backed up has no effect, since you can only flush what's on the holding disk. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Changing OS of amanda server
>On Jan 17, 2001, "Anthony A. D. Talltree" <[EMAIL PROTECTED]> wrote: > >>>> change the OS on my amanda server from RH Linux to Solaris 8 x86. >>> Bad move :-) :-) > >> I've never had to set up a cron job on a SunOS 5 machine that runs every >> minute, ifconfig'ing down and up the ethernet interface and re-adding >> the default route. This is what I have to do on my laptop when running >> RH Linux to keep the ethernet working. Well, something must be broken with that machine's drivers. I have Red Hat on a laptop and I don't have to do that! -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: what tape device does amanda support?
On Thu, 18 Jan 2001, Takayuki Murai wrote: >Date: Thu, 18 Jan 2001 10:39:21 +0900 >From: Takayuki Murai <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: what tape device does amanda support? > >Hello all, > >I am considering to get tape drive "SONY TSL-A500", and wondering if amanda >supports it. It's not up to amanda. Check your platform's own list of supported scsi tapes and go from there. Amanda will use either gnu tar, samba, or your platform's native dump utility. It's those items which have to talk to your tape. Robots are a slightly different story. Amanda comes with a number of scripts you can adapt for use with your particular robot. As long as you can get a robot control script going, you're all set. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Weird illustration of peculiar interactions :-}
On Mon, 15 Jan 2001, Martin Apel wrote: >I implemented some changes in the driver that cause it to gather dumps >until a certain threshold is reached. Afterwards it will always write >the biggest dump still fitting on the tape. This works quite nicely for me >and improves tape utilization a lot. Unfortunately it also increases the >total dump time a bit, if your tape is slow. >I haven't released it yet, because I implemented it in Amanda 2.4.1p1 >and didn't come around to porting it to 2.4.2. >But if you like I can post the patches for 2.4.1p1. I have a perl script which will go through my holding disk and spit out a list of backup sets to select to best pack tapes. here's an example: [amanda@joi amanda]$ pack -C OffSite 138530/140906 ( 98%) /home/amanda/mnt/holdingdisk/OffSite/20010106 /home/amanda/mnt/holdingdisk/OffSite/20010114 116784/140906 ( 82%) /home/amanda/mnt/holdingdisk/OffSite/20010107 /home/amanda/mnt/holdingdisk/OffSite/20010108 114088/140906 ( 80%) /home/amanda/mnt/holdingdisk/OffSite/20010111 99327/140906 ( 70%) /home/amanda/mnt/holdingdisk/OffSite/20010112 Nothing left to pack! I amflush these to tapes to send to offsite storage. I've already done two tapes from this batch, I have four left to do. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: HP COLORADO 8GB tapetype
On Wed, 10 Jan 2001, [iso-8859-1] Adolfo Pachón wrote: >Date: Wed, 10 Jan 2001 16:12:14 +0100 >From: "[iso-8859-1] Adolfo Pachón" <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: HP COLORADO 8GB tapetype > >¿Have someone the tapetype definition for an HP COLORADO 8GB streamer? >Thanks. > Perhaps http://amanda.sourceforge.net/cgi-bin/fom?file=111 There are more HP Colorado models on page: http://amanda.sourceforge.net/cgi-bin/fom?file=46 -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: again: amanda version 2.4.2 and NT
On Mon, 8 Jan 2001, Alexander von Homeyer wrote: >Just to be sure once again the question: >does version 2.4.2 support file exclusion on NT clients? I didn't think Samba's tar command supported exclude lists? If Samba doesn't, Amanda can't. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: cleaner tapes
On Fri, 5 Jan 2001, [iso-8859-1] Monserrat Seisdedos Nuñez wrote: >Date: Fri, 5 Jan 2001 15:21:02 +0100 >From: "[iso-8859-1] Monserrat Seisdedos Nuñez" <[EMAIL PROTECTED]> >To: "Amanda-Users (E-mail)" <[EMAIL PROTECTED]> >Subject: cleaner tapes > >Hello: >i wander how to use cleaner tapes??? Assuming that's what your drive's documentation says to do: Stick the tape in the drive. The unit will go through one clean cycle and automatically eject the tape. This can take anywhere from 10 seconds to a minute or two depending upon the drive. The cleaning tape should have a label on it that contains a bunch of check boxes or numbers. These reflect the number of times your tape has been used. When they're all checked off, toss the tape and buy a new one. You shouldn't reuse cleaning tapes, and some drives won't rewind them. That's how all the DAT and 8mm drives I've cleaned have worked. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
RE: [/sbin/dump returned 3]
On Thu, 21 Dec 2000, Shane T. Ferguson wrote: >Date: Thu, 21 Dec 2000 17:05:34 -0400 >From: Shane T. Ferguson <[EMAIL PROTECTED]> >To: Bernhard R. Erdmann <[EMAIL PROTECTED]> >Cc: Amanda-Users <[EMAIL PROTECTED]> >Subject: RE: [/sbin/dump returned 3] > >I got the latest dump from sourceforge about 2 weeks ago. Did you get the static rpm, or the dynamic one? RH5.2 was a libc5 platform, but the current rpms assume you're using glibc. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Using Removable Hard Drives for Backup
On Tue, 12 Dec 2000, Chris Karakas wrote: >Sigh...another O'Reilly book I'll have to buy. CVS - no matter how often >kind members of this list post the cryptic incantations for this temple, >I _will_ want to know it all when I enter it. I just ask myself why I >didn't buy all those fine manuals (BTFM) at once... ;-) Unless it came out within the last two months, there isn't a full-sized CVS book from O'Reilly yet. There's a pint-sized pocket reference of 75 small pages, which I bought a few months ago. Full-sized books are available in postscript (and pdf, I think) right from cvshome.org, for free. I downloaded and printed two of them. "Open Source Development With CVS" by Karl Fogel is pretty good, but the definitive reference is "Version Management with CVS" by Per Cederqvist et al. The later is often referred to simply as "The Cederqvist". This is also very good. I stuck each of them into 2" 3-ring binders and have many bookmarks in each. If the CVS Desktop Reference doesn't answer the question, one of the other two does. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: amlabel hangs up
On Wed, 13 Dec 2000, Stephen Walton wrote: >Date: Wed, 13 Dec 2000 10:09:25 -0800 (PST) >From: Stephen Walton <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: amlabel hangs up > >On Tue, 12 Dec 2000, Olaf Seidel wrote: > >I had a roughly similar problem. I found that amlabel put the tape drive >into a state where I had to power-cycle the drive to allow the system to >talk to it again if I failed to specify the '-f' switch. All was well if >I specified '-f'. This was on an HP 735/99 running HP-UX 10.20 with all >of HP's latest SCSI patches, connected via its narrow single-ended >interface to an Exabyte 8505XL drive, and Amanda 2.4.2 release. Since all >of my subsequent Amanda backups to this drive have succeeded without >incident, I don't think there are any hardware problems. For what it's worth, I have the same problem with an Eliant 820 (which seems to refer to itself as an 8505 occasionally.) Occasionally, I'll insert a tape, and at the first IO attempt the tape goes into an infinite shoeshine on the tape header. I have to powercycle the whole system to get control back. It really sucks. My older 8500 never did this. I think it's the drive, not the driver. I've sent email to Exebyte's support address several times and have never gotten an answer from them. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Rebuilt Tape Server
On Thu, 7 Dec 2000, Harri Haataja wrote: >> So what? The one that really matters is amandad, and for God knows >> what reason, the Linux folks don't appear to install that. > >Actually, I hear it's in the client kit in RH's rpms. >So this unbelievable generalization that Linux users don't install the >amanda(-no-dee) service config in xinetd.d would be false. =) Sigh. So Linux users are coming to be held in the same low regard as AOL users? -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: hardware errors on disk
On Thu, 7 Dec 2000, Chris Karakas wrote:
>Date: Thu, 07 Dec 2000 14:37:51 +0100
>From: Chris Karakas <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: Olaf Seidel <[EMAIL PROTECTED]>
>Cc: amanda-users <[EMAIL PROTECTED]>
>Subject: Re: hardware errors on disk
>
>>
>> hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
>> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=259647, sector=259584
>> end_request: I/O error, dev 03:01 (hda), sector 259584
>>
[snip]
>
>These errors have to alarm you, not just concern you! They mean
>"physical error in your hard drive sectors, cannot read!". Read - and
>print! you will not have it when you boot from floppy - the manual on
>fsck and make sure you understand the options. Then go on as above - and
>good luck!
Run, don't walk, to your local Best Buy and purchase a replacemet for
/dev/hda. Every time I see these errors, they herald the start of much angst
and file lossage.
--
Joi Ellis
[EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: amanda to blame for NT crashes?
On Mon, 4 Dec 2000, Chris Karakas wrote: >I've been trying for 6 months now to get the Windows partitions on the >backup server to be backed up correctly while running Linux and AMANDA. >I first tried it as follows: I told AMANDA to backup the SAMBA shares >that a SAMBA server made available on the backup server. The SAMBA >server got those shares from as mounted vfat partitions. This is where >SAMBA came into play. It did not work - incrementals were almost as big >as full backups. Then I said myself "why have this SAMBA stuff at all? >Just mount the vfat partitions and tell AMANDA to use tar and backup the >mount point directory". This did not work either for the same reason. I >am still looking for a solution. My amamda server is an Intel box which dual-boots NT and Linux Red hat 6.2. /dev/hda1 is the NT C: boot partition /dev/hda5 is the NT D: extended partition However, I have the mounted RO on the linux side because I often use them with VMWare from Linux, effectively multi-booting my box. ;) Mounted RO, Gnu tar sees them as /mnt/doscb and /mnt/dosdb. I could have accessed them via samba instead, since my VMWare appears to my Linux personality as a completely separate system with its own Hostname and IP Address. I played with this and it does work, but I don't use it because I rarely leave VMWare running for long periods of time. (It consumes half my ram and degrades my native Linux JBuilder application, which also consumes half my ram. Running them both causes my machine to start swapping heavily, and since I spend most of my time doing Java development, I launch VMWare only when I need to do excel stuff.) You could try a VMWare-hosted smbtar backup. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: amanda to blame for NT crashes?
On Mon, 4 Dec 2000, Harri Haataja wrote: >Date: Mon, 4 Dec 2000 09:28:57 +0200 (EET) >From: Harri Haataja <[EMAIL PROTECTED]> >Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> >Subject: Re: amanda to blame for NT crashes? > >On 2 Dec 2000, Marc SCHAEFER wrote: > >Fynnily enough I have some first hand information (that I can't cite >=) that says opposite. M$ has a very fine-grained, big-budget, efficient >(?) testing scheme but somehow that doesn't seem to do the job. Not all >bugs are discovered by testing. With the mess M$ has made of the smb protocols, it's a wonder it still works at all. Every release of windows has come with a changed protocol. There's all sorts of oddness in each version to allow it to talk smb-like with all previous versions. It's a horrible mess. (An ex-Microserf told me this.) I'm surprised Samba works at all! >I presume you mean windos clients are used to test smb shares? > >This is quite likely to be a culprit. But then again m$ has a history of >breaking standards and protocols on purpose and always blaming the other >end. This thread (the start) seems to have proven that the idea has gone >through very well -- their users have absolute faith in them and always >blame someone (-thing) else. Boy, can I tell you some stories about Microsoft re-writing email internet standards! And F77 language standards, too... >Nevertheless, I agree that if windows crashes, windows has a >bug/flaw/lacking (depending on wheather what made it crash was >use/unexpected_use/downright_cruel_use) there. Yes. But then, M$ has never felt that a GPF was anything to avoid. :p -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Amanda broke my tape drive!
On Sun, 3 Dec 2000, John R. Jackson wrote: >Assuming you're talking about me, thanks, but that brand doesn't even >faze me any more. You'll need something seriously industrial strength >to calm me down. :-) :-) Courvoisier ? Armagnac ? www.bbr.com has some nice ones... at 1075 British Pounds per bottle! (Yikes...) -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Amanda broke my tape drive!
On Sun, 3 Dec 2000, Bernhard R. Erdmann wrote: >I'm pretty sure Amanda shot the tape drive to death! :-) Let's all chip in and get John a big bottle of Prozac for the holidays! -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: MT
On Sat, 2 Dec 2000, John R. Jackson wrote: [snip] >>... mt is missing from my system. Before I >>reinstalled 2.4.2 the second time, due to it not installing over 2.4.1p1 >>cleanly the first time, I used turbopkg to remove 'amanda, amanda-client, >>amanda-server and taper' all listed under a broader heading of 'System - >>Backup'. Do you know which of these removed mt as well? ... > [snip] >If I had to guess, it would be "taper". I would have thought what >Amanda calls taper would be part of amanda-server. On my Red Hat systems, mt is provided by its own RPM. It isn't bundled with amanda. mt is not in 6.2's taper package, either. mt-st-0.5b-7.i386.rpm -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: amanda to blame for NT crashes?
On Fri, 1 Dec 2000, John R. Jackson wrote: >Date: Fri, 01 Dec 2000 18:31:07 -0500 >From: John R. Jackson <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: Eric Wadsworth <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED] >Subject: Re: amanda to blame for NT crashes? > >[ My apologies in advance for the following. I normally brag about how >little heat there is on this mailing list, but I'm sure going to break >that mold below. If it helps, pretend I'm trying to be funny. --JJ ] > >>... My co-workers are saying that it is amanda's fault ... > I just searched through samba.org's mail archive, and there are reports there of NT blue-screening during a smbtar pull from Unix hosts. I haven't come across a response to that, someone who has more time may want to search harder through the archives for an answer. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Completely Stuck :-(
On Fri, 24 Nov 2000, John Cartwright wrote: >Date: Fri, 24 Nov 2000 09:52:55 -0500 >From: John Cartwright <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Completely Stuck :-( > >Hi > >I'm hoping someone can shed some light on this one, basically I'm >convinced amandad never runs from inetd, and I"ve spent days on this >so far :-( > >I'm trying to install Amanda on a Solaris 8 x86 box, where the client >and server are one and the same. Installation options were --with- >user=amanda, --with-group=sys, --with-amandahosts. > >/etc/services contains (amongst other things): >amanda 10080/udp >amandaidx 10082/tcp >amidxtape 10083/tcp > >and inetd has (on one line!): > >amanda dgram udp wait >amanda /opt/local/libexec/amandad amandad > >If I run the above manually (as root or amanda), the /tmp/amanda/ >directory is created, as well as the debug file. So I delete that, >kill-HUP inetd just to be safe, and then run amcheck. > >Nov 24 12:00:27 hostname inetd[168]: [ID 858011 >daemon.warning] /opt/local/libexec/amandad: Hangup >Nov 24 12:00:28 hostname last message repeated 38 times >Nov 24 12:00:28 hostname inetd[168]: [ID 667328 daemon.error] >amanda/udp server failing (looping), service terminated > >amcheck comes up with the timeout error (selfcheck failed) >ls -lu on amandad shows it never ran in the first place. So I'm very >confused - help! > >Also I'm not 100% as to what should be going on with .amandahosts, at >present I have it in ~amanda, containing 'hostname amanda' and this >seems OK. > >Thanks >- John > -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: amanda using ssh
On 21 Nov 2000, Alexandre Oliva wrote: >How about CIPE? This will probably work without messing up with the >Amanda protocol. CIPE will take care of the VPN encryption in the IP >level, so both UDP and TCP, used by Amanda, will work. I've never heard of CIPE. Where is it? I have a few remote linux boxes I'd love to backup to my home tape via amanda. (Yeah, over y 64k link will suck, but it's better than driving across down with the tape drive and buying extra scsi controllers...) -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
RE: Backing up Oracle database
On Tue, 21 Nov 2000, Tuthill, Ed wrote: >So if you'd like to look at a perl version of this, let me know >and I can ship a copy your way. I'd love to have a copy of your perl script when you're finished with it. I have MySql on my box supporting my own private website search engine and our internal bugzilla. Not a real high-traffic server but I'd still like to get the bugzilla backed up better than it is now. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: linux filesize limit and amanda?
On Tue, 21 Nov 2000, Yura Pismerov wrote: >The only problem I can see here is large files (if any) inside of the >archive. Then it will be a problem and you only can do it on foreign >solaris filesystem >by piping the stream to there through, for example, ssh. Here's what I did the last time I had to pull an image >2gig from a tape: cd (someplace with enough disk space) dd if=/dev/nst0 | split -b2000m cat x?? | restore ... -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Problems with amstatus
On Wed, 22 Nov 2000, Mike Hendrix wrote: >Date: Wed, 22 Nov 2000 10:33:47 -0500 (EST) >From: Mike Hendrix <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Problems with amstatus > >I have just installed another backup server here and am having problems with >amstatus. I have done the configuration correctly I believe but every time >while the backups are running and I try to run a status for the Daily2 >dumpset I get the following error: > >bash-2.03$ amstatus Daily2 >Using /var/adm/amanda/Daily2/log/amdump > >Modification of a read-only value attempted at >/usr/local/amanda/sbin/amstatus line 98, chunk 53. > >Does anyone have a clue as to what the problem might be with amstatus on >this machine? I am running solaris 7 x86 with perl 5.00503 installed on the >box. Is line 98 of /usr/local/amanda/sbin/amstatus an assignment to $$host? If it is, comment it out. That's a bug in amstatus where it assumes every host name is in fact a name and not an ip address. I think this is fixed in 2.4.2. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Weird Block Size, Tapertype, Something Error
On Mon, 20 Nov 2000, David Lloyd wrote: >Hi There! > >On the weekend I built, installed and ran the tapetype program on my >system. Unfortunately I had to change tape drives before I did this but >it was exactly the SAME model (Seagate STT2-RCVT a Travan drive) as >was taken out. Tapetype doesn't control anything in your amanda configuration. It's a one-time tool you use to test your drive and your tapes and generate a tapetype entry which you place in your amanda.conf file. If you swap drives and the replacement is a duplicate of the original, you don't need change your tapetype or rerun the tapetype tool. > Anyway, the person I work with adjusted the tapetype and >the first odd thing that occured was: > >* st0: incorrect block size Many tape drives support block sizes of various sizes. My drive supports size 0, and 1k sizes all the way up to 64k. Once a tape is written with a particular size, the drive must be told what block size to use for reading that tape. My drive defaults to 1k blocks. If I manually create a tape with 32k blocks, then powercycle the drive, it will drop back to 1k and won't read my 32k block tapes until I manually set the drive's block size back to 32k. I have an mt command in my nightly script which sets the drive's block size before launching amanda. > >We amrmtaped the tape and relabeled it again. The dumps appeared to go >the tape correctly. However, the next morning (we did another dump but >this time to holding disk) the amflush reported an incorrect block size. > >I went in and investigated and discovered the following things: > >* amanda was wholly unable to read any of the "pre change block >size/tape device" tapes Yes. Your drive isn't smart enough to figure out what the old block size setting was. You'll have to set it manually to read those tapes. > - amverify would complain about the block size Yup. > - forcing the block size to 0 caused amverify to read but it came up >with things like "short header 412 bytes" Dunno about this, I don't use block size 0. > - amrestore would complain that there was an EOF and that it had >reached end of tape when the tapes, even when rewinding, take at least 5 >minutes to go from one end to another and the tape I was restoring was >very full Well, 5 minutes to rewind a large tape isn't bad, that's about how long it takes for my drive to rewind from EOT. > >* tar could read and write to tape > - tar could read and write to the tape nicely Sure, since it's reading and writing while the block size is stable. >I thought "this is a tapetype" mismatch. So I reset the tapetype back to >the above and got the same errors. This of course implies one of our >backup systems (we run two for safety purposes) is simply a) failing or >b) almost impossible to restore. We have tried forcing compression on >and off with still the same results. Nah. Tapetype is a oneshot process, it doesn't affect this drive block size setting issue you're having. (Mind you, it's possible that changing the blocktype to what you intend to stick with and rerunning tapetype once to get a new setting wouldn't be a bad idea. My drive's capacity changed slightly when I switched from 1k to 23k blocks.) -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Do you think we are going to run out of holding disk space..
On Sat, 18 Nov 2000, Denise Ives wrote: >Subject: Do you think we are going to run out of holding disk space.. > > >for tonight's level 0 dump? Yes. Ignoring /tmp and swap partitions, your two machines have more than twice as much disk space in use as exists on your holding partition. I summed everything (ignoring swap, /tmp, and /dump), and then subtracted the size of /dump. The remainder was 12959432, which is still bigger than /dump by quite a bit. Unless your compression is enabled and getting a lot better than 2/1, your full dumps won't fit. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: overdue 7 days for level 0
On Sat, 18 Nov 2000, Denise Ives wrote: >I forced a level 0 dump and left the tape out of the tape drive - as you >all know amanda failed to dump because of a tape error. Why didn't >amanda put the dump image into the holding disk? Is this expected >behavior? Yes, this is expected behavior given the default settings in the amanda.conf file. [snip] >ANALYZING ESTIMATES... >pondering sundev1.corp.walid.com:c0t0d0s7... next_level0 -7 last_level -1 >(due for level 0) (new disk, can't switch to degraded mode) > curr level 0 size 3444532 total size 3444928 total_lev0 3444532 >balanced-lev0size 430566 Amanda has never seen this disk before. You can't take an incremental dump of a new disk, you can only take a full dump. (Incrementals are, by definition, files which changed since a previous full dump. So if there is no full dump to refer to, an incremental dump is impossible.) > >driver: adding holding disk 0 dir /dump/amanda size 10932533 >reserving 10932533 out of 10932533 for degraded-mode dumps Your amanda.conf file has told amanda to reserve 100% of the disk to degraded incrementals. Because Amanda needs to take full dumps first, and all of the holding disk is reserved for degraded incrementals, there is no space on the disk available for non-degraded full dumps. Edit your amanda.conf file to say something like "reserve 10". Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: forced a full dump for Sat AM - it failed (fwd)
On Sat, 18 Nov 2000, Denise Ives wrote: >Actually - I left the tape out of the tape drive on purpose. I was trying >to get amanda send the full dump image to the holding disk. > > >When you force a full dump and there is a tape error - amanda doesn't >send the dump to the holding disk? Find the 'reserve' parameter in your amanda.conf file and set it to a low number. I have mine set to 30, but I have a 30gig holding disk and a 4 gig tape unit. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: forced a full dump for Sat AM - it failed
On Sat, 18 Nov 2000, Denise Ives wrote: >Date: Sat, 18 Nov 2000 21:20:03 + (GMT) >From: Denise Ives <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: forced a full dump for Sat AM - it failed > >Any ideas on how/why this happened? Amanda couldn't find a tape in the drive. It would normally default to doing incrementals, but because full dumps had been forced for all clients, Amanda couldn't degrade to incrementals. Find out why Amanda couldn't see a tape in the drive. Maybe there wasn't one, or maybe the drive reported an error trying to read it. Check your system's syslog or kernel log for tape error messages... Don't forget you have to 'amlabel' each new tape before Amanda will write to it. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Sony TSL-11000
On Sat, 18 Nov 2000, Jonathan F. Dill wrote: >Date: Sat, 18 Nov 2000 15:30:47 -0500 >From: Jonathan F. Dill <[EMAIL PROTECTED]> >To: "Marty Shannon, RHCE" <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED] >Subject: Re: Sony TSL-11000 > >"Marty Shannon, RHCE" wrote: >> Someone will undoubtedly correct me if I'm wrong on this, but I'm pretty >> sure you need to enable disconnect from Adaptec's BIOS settings page >> (type control-A to get there). > >Thanks for the tip--I looked up the user reference for the AHA-2940U2W >from adaptec.com and it is indeed one of the BIOS settings. It's on by >default, and I doubt that I changed it, but I'll have to check. Would enabling disconnect on the scsi controller be a good thing to do generically? I have a similar card on my machine, perhaps I could reconfigure it to enhance performance over what I see now? -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: your mail
On Fri, 17 Nov 2000, David Lloyd wrote: >It appears that AMANDA must write to: > >* its config directories >* /etc/dumpdates (if you're using dump) >* /etc/amandates >* /usr/adm/amanda or wherever you've set the log directories to >* /tmp > >If it can't write to any of them it can simply die silently. No error. >Nothing - especially if /tmp fails. amrecover and the index server seem >to be the most susceptible to non-writable directories, although amandad >and almost anything else that logs to /tmp can fail silently. > >I'm inclined to hack the source and stop it from dying without a trace; >maybe a syslog of messages.critical saying there is no AMANDA logs would > Amcheck tests and reports on all of these conditions. Didn't you put it into your nightly backup script as suggested in the install guide? /tmp itself is supposed to be world read/write, even user nobody can write there under most unixes. If /tmp isn't world writable all kinds of things break. I wouldn't hold this one against Amanda... -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Using Amanda to backup a NFS mounted FS.
On Thu, 16 Nov 2000, Nate Eldredge wrote: >> Can Amanda be used to backup an NFS mounted filesystem ? I have a >> Network Appliance >> box and have mounted the exported filesystem to a mount point on the >> Amanda server >> The Sun is running Solaris 7. > >Yes, it's working fine here. You just have to use tar. Obviously you >can't use dump, because you don't have access to the raw disk (and even if >you did, Solaris wouldn't have any idea what to do with it). > >Another hint: If you have snapshots enabled, you will probably want to >exclude them (amanda documentation explains how to exclude directories). Be aware that running backups over NFS can really saturate an ethernet and noticibly degrade performance. It's also prone to problems should the backup machine lose its mount during the backup run. I've seen admins resort to rebooting their backup box because the NFS-mounted partition went south and the backup process hung. At my previous job the net-nazies decided they didn't like the backup traffic and unilaterally, without consulting the users or admins involved, firewalled NFS traffic. They wouldn't even allow us to route from our A subnet to our B subnet. Dump programs don't generally read NFS partitions, since NFS <> UFS or ext2 or whatever your physical filesystem really is, so yeah, you're restricted to using tar to do it. You may also have to play games with your fstab to give the backup machine root write rights on the NFS mount so that incrementals can function. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: What the heck happened to /etc/dumpdates?
On Thu, 16 Nov 2000, Denise Ives wrote: >Anyone seen this happen before? Yes. >Email Response from peer admin: >I am thinking this happened because of the update of dump I made >yesterday to overcome the security glitch. I don't know if I have made any >mistake but I have followed the procedure given in the site. It did not >give me any errors, yesterday, when the rpms were being installed. >Any clues, anyone? [snip] >Your "cron" job on sundev1 >/sbin/su amanda -c "/usr/local/pkg/amanda-2.4.1p1/sbin/amcheck -c daily" > >ERROR: admin1.corp.walid.com: [can not read/write /etc/dumpdates: No such >file or directory] /etc/dumpdates is provided as part of the dump package, and rpm undoubtedly replaced your amanda-writable permissions with root-only permissions, which are the usual default. Go chown /etc/dumpdates back to user amanda and it will be fine. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: your mail
On Thu, 16 Nov 2000, Matt Glaves wrote: >Date: Thu, 16 Nov 2000 10:37:08 -0500 (EST) >From: Matt Glaves <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] > > >I have just inherited a system running Amanda. I have performed a few >test restores and it appears that the system is only backing up files >which are world readable. User backup should be added to the same group which owns the disks, and that group should have read or read-write access to the physical devices. (I'm not positive about the read-write, but it definately needs read.) -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
RE: hostname lookup failed
On Thu, 16 Nov 2000, David Wolfskill wrote: >I'm pretty sure that all (UNIX) versions of nslookup uses gethostbyname(); >I'm less confident about their use of gethostbyaddr(). (I'm pretty sure >that there have been some versions of nslookup that would try to do a >gethostbyname() using an IP address as an argument, if you gave it an IP >address. But the machine I have where that was likely the case stopped >working a few months ago, and I don't have the time to get a Sun 3/60 running >again... and I'm digressing. For those versions of nslookup, it was >generally necessary to feed it something of the form >ddd.ccc.bbb.aaa.in-addr.arpa (assuming an IP address "aaa.bbb.ccc.ddd").) I'm not sure of this at all. On our internal machines, various breeds of linux and solaris, nslookup doesn't return an answer if there is no DNS entry for the name in question, EVEN IF that host is named in the /etc/hosts file. gethostbyname() follows the rules specifed in /etc/nsswitch.conf, which is where gethostbyname() finds out in what order to search, files, dns, nis, etc. Some versions of nslookup will accept an IP address, ie the Linux flavor will, but default Solaris flavors won't. I've found that simply adding entries to /etc/hosts files was sufficient to get amanda running. As long as each machine can 'ping othermachine' and there isn't a conflict with DNS entries, it's fine. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
re: sugestion for tape labeling Yea or Nea?
On Tue, 14 Nov 2000, David Wolfskill wrote: >>There is an admin here who suggested I >>modify the labelstr. Will this work? > >>- you should modify >>labelstr to "$[0-9][0-9][0-9]" > >Changing the labelstr may be useful. > >But since it's a (Perl) regex, I'd be rather surprised if a string with >non-terminating "$" characters would be useful for anything: that >character is used to provide an "anchor" for the right-hand side of the >string. It looks to me like the admin who suggested that is an SQL guru. $ is a wildcard character for Oracle, I think. Replace that chain of pattern with the simpler perl pattern: ".\d\d\d" "." means any one character, "\d" means any digit. A safer pattern, the one I use, is "DailySet1\d\d". -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: version 2.4.2 where to get?
On Sat, 4 Nov 2000, Edwin Chiu wrote: >Where can I get 2.4.2? >How stable is it? > >If it's in CVS can someone tell me how to check it out? There is an entry in the online Amanda FAQ with step-by-step instructions for getting the current CVS snapshot. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Is it possible to run an amanda client without inetd?
On Wed, 25 Oct 2000, Jeff Silverman wrote: >Date: Wed, 25 Oct 2000 21:29:40 -0700 >From: Jeff Silverman <[EMAIL PROTECTED]> >To: Amanda Users List <[EMAIL PROTECTED]> >Subject: Is it possible to run an amanda client without inetd? > >I don't see anywhere in the documentation where it says how to run >amandad without an inetd, but I don't see anywhere where it says you >can't. I don't know if amandad is written to be a full-time server process. The logic behind such a server is different than one designed for use with inetd, so I wouldn't make any assumptions about this. >I think I want to setup inetd on this machine (because I think inetd is >more secure), but I want an authoritative statement along the lines of, >"You must run inetd or amandad won't work" (because setting up inetd is >some work). Inetd or a close relative is a standard fixture on unix machines. The only inetd configuration you must do to support amanda is add three lines to the inetd.conf and kill HUP the inetd process. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: strangely slow amrecover
On Wed, 25 Oct 2000, peanut butter wrote: >Yet, though I can't explain this, I believe I >witnessed twice the oddity of constantly checking the directory size >unchangingly and then, when convinced nothing was happening and so >aborted amrecover, the directory size would "suddenly" 'du' as 20 >megs or so larger than the entire time I was checking it during the >restore. Is there any reasonable explanation for this? > >So, I believe things were being restored but it was taking a >painfully long time (yet, as a possibility you mentioned, the dump file >itself was large, about 7 gigs) and eventhough I couldn't detect any >increase in size of the directory being restored, after aborting the >restore, the directory would be significantly larger. Many file systems do not update the size value in an inode's directory entry until the file is closed. You want to be watching the free space drop in "df -k ." rather than watching "du thefile" -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: tape-type defs needed for an ADIC DLT 40/80
On Wed, 25 Oct 2000, David McCall wrote: >Date: Wed, 25 Oct 2000 16:35:29 -0700 >From: David McCall <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: amanda-users <[EMAIL PROTECTED]> >Subject: tape-type defs needed for an ADIC DLT 40/80 > >checked existing list >thanks ahead of time > >dmc Did you check the online faq? There are a pile of DLT tapetypes in there. It's likely some of them match your drive's specs, if not its exact brand/model name. http://www.amanda.org/cgi-bin/fom?file=93 -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Changing a tape's density
On Wed, 25 Oct 2000, Chris Karakas wrote: > >I think he means the density on the magnetic medium, as measured in bits >per inch. I don't think you can change this (at least not set a higher >density for a medium constructed with a lower one), because it has to do >with the density of the magnetic particles on the tape, i.e. the >physical quality and specs. That's what I was referring to, as well as compression on/off. Some drives let you adjust the BPI to fit the media. I'm thinking more of old 9-track tapes, the numbers which float to the top are 800, 1600, and 6250 bpi, and you told the drive what density to use. I had an old DAT tape drive about 10 years ago which had density controls as well. This was before the DDS-n standards came into common usage. You can try to write any density your drive is capable of, and if the media doesn't have case notches, your drive will do it, but you may experience higher error rates if the media isn't up to the task. On my drives, once a tape is written with compressesion/density settings, that tape will forever retain those values until forcibly erased, usually with an 'mt weof' or something similar. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: trouble with samba2-20000418.diff/second.edition
On Tue, 24 Oct 2000, Frank Rippert wrote: >Date: Tue, 24 Oct 2000 19:25:12 +0200 >From: Frank Rippert <[EMAIL PROTECTED]> >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, > "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: trouble with samba2-2418.diff/second.edition > >I described that i have problems with the samba2-2418.diff patch. I >copied the changes with hand (means that i deleted/paste the lines >manually). Could this be the mistake. Patch is extremely sensitive to changes in the content of a patch file, including whitespace, blank lines, etc. Even downloading a patch with a browser improperly is enough to mangle the patch file. It looks like you used the correct patch command syntax. I suspect your patch file was corrupt. Patch could also be confused if you have a patch file for, say, Version 1.1 of a source file, but you're applying it against Version 1.3. Sometimes Patch gets it right, sometimes it just can't. If you can't get it to work, tell me where you found your patch file, and send my your two input files (sendbackup-gnutar.c, sendsize.c) and I'll try it. >I tried to use the patch instruction >with no success. Only the following message appears: > >patching file 'sendbackup-gnutar.c' >Hunk #1 FAILED at 63. >Hunk #2 FAILED at 90. >Hunk #3 FAILED at 298. >Hunk #4 FAILED at 305. >4 out of 4 hunks FAILED -- savings rejects to sendbackup-gnutar.c.rej >patching file 'sendsize.c' >Hunk #1 FAILED at 571. >Hunk #2 FAILED at 918. >Hunk #3 FAILED at 948. >Hunk #4 FAILED at 958. >4 out of 4 hunks FAILED -- savings rejects to sendsize.c.rej >patching file 'config.h.in' > : > : > > >Can anybody tell me the right patch instruction (mean the right options or >better the exact syntax). >Thanks a lot >farnk Rippert > > -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Changing a tape's density
On Tue, 24 Oct 2000, Paul Tomblin wrote: >Date: Tue, 24 Oct 2000 18:33:11 -0400 >From: Paul Tomblin <[EMAIL PROTECTED]> >To: Amanda <[EMAIL PROTECTED]> >Subject: Re: Changing a tape's density > >So far nothing has worked. I've tried "mt weof 10", "mt erase" and "mt >setdensity 0x24", and nothing has worked. Perhaps we're missing something... DAT cartridges com in various flavors, right? DDS1 vs DDS2, etc. Perhaps your media knows it isn't tested for compressed drives and doesn't have the proper notches. IE I know there are notces in some types of cartridges to indicate length and/or maximum write density. And there are special notches on cleaning tapes. Perhaps your drive isn't cooperating because it doesn't like the media. Find a new cartridge you know is compatible with all your drive's features and see if your mt commands work better with the new cartridge. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Using a cname for the amanda server
On Fri, 20 Oct 2000, Dean Pentcheff wrote: >Joi Ellis wrote: >> On Tue, 17 Oct 2000, Jonathan D. Proulx wrote: >... >> I'm also not sure I'd want the identity of my tape backup server >> visible with simple DNS queries, either. That makes it a juicy >> target. >> >You should be aware that a trivial port scan of the network will reveal >the Amanda hosts, so there's not much to be gained by a simple name >obfuscation. An example from our network: Well, yes, except that, until just last month, our DNS was managed by our ISP, and they published the entries for everything we gave them. The only service-like name we gave them was 'mail', everything else was simple host names. Now that we have our own internal DNS, we have fewer machines published. I hope.. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Changing a tape's density
On Tue, 24 Oct 2000, Bernhard R. Erdmann wrote: >Paul Tomblin wrote: [snip] >> reformat? I don't have a bulk eraser. I tried using "mt setdensity >> DDS-2", but it didn't take. > >mt weof 5 >or >mt erase >or >dd if=/dev/zero bs=32k of=$TAPE In my own experience, using only a dd won't change the tape's format. My drives all see and use the original drive blocksize and compressions setting and use it until I overwrite it with a weof. I don't know if the erase will do it or not. I know when my drive is shoeshining on a tape header, an erase won't do it. I'm certain the dd won't... (4mm DAT of various vintanges, EXB-8500, EXB-8505). (Did you mean for the dd to overwrite the whole tape? Usually just whacking the header is sufficient. If not, add a count=NN to it.) -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: A solution for taper and dumps larger than a single tape?
On Mon, 23 Oct 2000, Bernhard R. Erdmann wrote: > "Brian J. Murrell" wrote: > [...] > > So why not stop writing before getting the EOT? If Amanda stops writing > > after the last full block before the expected physical EOT (or sooner if > > you want) and resumes on the next tape, is that problem no longer a > > problem? > > > > What am I missing? > > How do you know the exact EOT when using hardware compression? You don't. That's why it's preferrable to use Amanda's software compression, instead. Since this way the chunks are already compressed, amanda knows exactly what size they will be on tape and can plan much better. When I play games with my own offsite backup extractor/packer and amflush, I regularly achieve 99.9% tape utilitization using my standard tapetype. I haven't had one hit EOT, yet. I don't use hardware compression. -- Joi EllisSoftware Engineer Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED] No matter what we think of Linux versus FreeBSD, etc., the one thing I really like about Linux is that it has Microsoft worried. Anything that kicks a monopoly in the pants has got to be good for something. - Chris Johnson
Re: Changing a tape's density
On Mon, 23 Oct 2000, Paul Tomblin wrote: > I just bought a DDS-2 drive to replace my DDS-1 drive (anybody want to buy > it?). Anyway, I tried one of my 120m tapes that had been used in the > DDS-1 drive, and it appears that the new drive recognizes the old format > and won't write to it at the higher density. How can I force it to > reformat? I don't have a bulk eraser. I tried using "mt setdensity > DDS-2", but it didn't take. Try 'mt erase' or 'mt weof', then change your drive settings, then write some foo and see if it took. I like to do: $ cat /home/amanda/bin/init32k #!/bin/bash mt rewind &&\ mt weof && \ mt setblk 32768 && \ dd if=/dev/zero of=/dev/nst0 bs=32k count=1000 && \ mt rewind I use this to change the block size on my drive from its default of 1k bytes to 32k bytes, which makes my workstation run a lot smoother when taper is active. Most of my existing tapes are at 1024, so I run this each night to reset the tape format before Amanda sees it. (I also amrmtape and amlabel the thing so Amanda's db doesn't get confused.) Once I cycle through all my tapes, I won't have to do this any longer since the drive checks a tape for such settings when it loads it. I use the dd to make sure the whole header is clean, because otherwise my tape drive is likely to start shoeshining on the tape's physical header. I don't know why It hasn't done it since I started using the dd, though. -- Joi EllisSoftware Engineer Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED] No matter what we think of Linux versus FreeBSD, etc., the one thing I really like about Linux is that it has Microsoft worried. Anything that kicks a monopoly in the pants has got to be good for something. - Chris Johnson
