Backup of soft-raid device?

Is it possible to backup a device /dev/md0/, which is a software raid level 0, at all? I get the following messages: FAILED AND STRANGE DUMP DETAILS: /-- merten1.me md0 lev 1 STRANGE sendbackup: start [merten1.merten.lab:md0 level 1] sendbackup: info BACKUP=/sbin/dump sendbackup: info

Problem with chg-scsi

Hi, I have some Problems with chg-scsi. My machine is a Sun Ultra1 with Solaris 2.6. The Library is an Oveland-LXB Loader. This time I got a different error message when running chg-scsi -reset: DeviceCapabilitiesPage == NULL Amanda runs already with root-permissons and I use the modified

How can I tell what's happening?

How can I tell whether anything good is happening with my amanda backup? I'm new to amanda and trying to get it working on a system that I suspect has never been backed up. (I see messages in amdump like "isgadmin:/dev/hda1 overdue 11318 days for level 0.") My tapelist shows: su-2.03# cat

amreport

hello every body: i'm testing amreport with an amanda run i have just done. i go to the /usr/local/etc/amanda/Diario where i have amanda.conf i type amreport segmentation fault(core dump) why??

No Subject

lists

Re: How can I tell what's happening?

How can I tell whether anything good is happening with my amanda backup? ... The usual way is to look at the E-mail report you get after every run. You are getting those, right? If not, you'd better take a look at "mailto" in amanda.conf. Take a look at amanda.conf for the "logdir" variable.

Re: amreport

i type amreport segmentation fault(core dump) What version of Amanda are you using? Did you get a core file in that directory or /tmp/amanda? If so, what do you get when you run a debugger on amreport and the core file and enter the "where" command, e.g.: $ gdb /path/to/amreport

Re: How can I tell what's happening?

On Thu, 28 Dec 2000, KEVIN ZEMBOWER wrote: How can I tell whether anything good is happening with my amanda backup? I'm new to amanda and trying to get it working on a system that I suspect has never been backed up. (I see messages in amdump like "isgadmin:/dev/hda1 overdue 11318 days for

Re: How can I tell what's happening?

Thanks, John, for taking the time to try to give me a hand. I've only gotten one email report, but I did get that one, so I believe that the "mailto" is correct. That one came after the Dec. 21 run. It's also the one that gave me the idea that it took 60 hours. I can only "find" one log file:

VXA Tape V17

Anyone using Ecrix VXA V17 tapes? I found this config in the faq-omatic I have a question: This drive is supposed to write 66gb with hardware compression. This config only reflects "length 30609 mbytes" about half of that. define tapetype VXA { comment "Ecrix VXA-1 V17"

Re: How can I tell what's happening?

I've only gotten one email report, but I did get that one, so I believe that t he "mailto" is correct. ... OK, that's good. As to the errors: error result for host isgadmin disk /dev/hda2: isgadmin: [access as amanda not allowed from [EMAIL PROTECTED]] These are puzzling, since I have

Re: VXA Tape V17

Also Sprach Bradley Glonka: Anyone using Ecrix VXA V17 tapes? I found this config in the faq-omatic I have a question: This drive is supposed to write 66gb with hardware compression. This config only reflects "length 30609 mbytes" about half of that. define tapetype VXA {

Re: VXA Tape V17

This drive is supposed to write 66gb with hardware compression. This config only reflects "length 30609 mbytes" about half of that. Which is pretty close to correct, then. Manufactures reports twice the "native" density when giving the number for compression. I ran the tapetype utility with

Re: VXA Tape V17

Also Sprach John R. Jackson: - how do I take advantage of hardware compression? You fudge the length up from what you think it will do native based on the amount of compression you expect to get. And here's a tip -- **nobody** gets double :-). I typically see 20-35%. brad John R.

Re: VXA Tape V17

Also Sprach C. Chan: You fudge the length up from what you think it will do native based on the amount of compression you expect to get. And here's a tip -- **nobody** gets double :-). I typically see 20-35%. brad John R. Jackson, Technical Software Specialist, [EMAIL

Re: VXA Tape V17

... I think Amanda with software compression is smart enough not to compress if it means an increase in size ... I don't think so. Compression is always done in a pipeline so there is no chance to recover the original data if at the end it looks like it was a bad idea. C. Chan John R.

DLT7000 drive not streaming ?

I have a FreeBSD system running Amanda 2.4.2 with a DLT7000 tape drive. I notice that the drive doesn't stream continously. The tape shuttles back and forth. Is there a way to maximize tape drive throughput so that the tape drive will stream continously? Thanks, Joe DUMP SUMMARY:

Re: How can I tell what's happening?

I ran these test on the isgadmin box, one of the targets. isgback is the amand a server. Both seemed to work fine; both listed the contents of the file. OK so far. What I meant to say is that the userID 37 doesn't show up in the /etc/passwd f ile of isgback. Similarly, the groupID 102 doesn't