John R. Jackson on Mon 27/01 21:37 -0500:
> > - the #ifdef NO_AMANDA stuff is pretty much exact duplication.
> > Anyone consider just moving this out into a library instead of
> > duplicating whole routines in rait-*.c ?
>
> Yes, but Marc Mengel really (really :-) wanted to keep the code
John R. Jackson on Mon 27/01 21:37 -0500:
> Correct. To do parallelism at user level would require something like
> a shared memory buffer and forked processes (ala the two halves of
> taper), or asynchronous I/O calls or threads, all of which use various
> levels of OS specific capabilities (and
> - it doesn't have any parallelism at all, so it gains no concurrency
> advantages; it simply loops among the data set members, does one
> write, blocks, does the other, etc then write the parity tape.
Correct. To do parallelism at user level would require something like a
shared memor
Hi all
Has anyone tried backing up os-x boxes using Amanda and hfspax?
I'd be happy to hack at it (in the most amateurish way) if someone would
kindly point out the pertinent points-of-interest, areas to poke at... :-)
WR
John R. Jackson on Sun 26/01 17:40 -0500:
> > You describe RAID4, probably the least commonly used RAID, since it
> > means only one write request can be satisfied at once, as there is a
> > only single drive doing parity writes. Much better is to rotate the
> > parity from one drive to the next w
On Monday 27 January 2003 16:42, Joshua Baker-LePain wrote:
>On Mon, 27 Jan 2003 at 1:53pm, Michael Kopach wrote
>
>> I have the odd tape that fills up from AMANDA. Since I have a
>> limited number of tapes on hand, how does one safely clean out
>> the contents of that tape and reuse it under AMAND
Opps, my mistake! Maybe I didn't clarify. AMANDA was running out of tape
at the end of a few runs. I think I will let it run *as is* and see if
it happens again. If so, I'll just run amflush and see if it fits on the
next tape.
Thanks ... Mike
>>> Joshua Baker-LePain <[EMAIL PROTECTED]> 01/27/03
On Mon, 27 Jan 2003 at 1:53pm, Michael Kopach wrote
> I have the odd tape that fills up from AMANDA. Since I have a limited
> number of tapes on hand, how does one safely clean out the contents of
> that tape and reuse it under AMANDA?
Err, I'm not quite sure what any of this means. By default,
Hi Guys!
I have the odd tape that fills up from AMANDA. Since I have a limited
number of tapes on hand, how does one safely clean out the contents of
that tape and reuse it under AMANDA?
Thanks ... Mike
>So, when I look in the amrecover debug file on the client, I find it's
>trying to execute /sbin/restore. This is wrong, it should be trying to
>execute /usr/sbin/vxrestore.
Here is the relevant part of the code in recover-src/extract_list.c:
#if defined(VXDUMP)
if (strcmp(file.progr
On Mon, Jan 27, 2003 at 09:59:13AM -0500, stan wrote:
> I;m having problems getting a backup restored. Here's the scenario.
>
> Tape server machine Debian GNU link "testing", running Amanda 2.4.3b4
>
> Client machine HP-UX 10.20 running Amanda 2.4.2p1, and with VXFS filesystems
> (I think this is
I was just curious if there was some information anyone could pass on to see
Amanda is right for my environment. I have Sun E150 with a 40 slot, 4 drive
Spectralogic 1 AIT Tape array. Will Amanda work with this equipment?
Anybody have some last minute do's and don'ts that I should follow? An
I run a cron script that runs the Oracle export utility and tar/gzips
the dmp and log files using a date named file. You can then use AMANDA
to backup the output.
The alternative is to purchase a third party interface for each Oracle
installation you wish to backup. Unfortunately, such warez ten
>... I'm trying to simply get a backup set off of a
>Amanda tape using amrestore (which I have never used before).
You have used it (via amrecover), you just didn't know it :-).
>I see the set I want going by in amverify, and amrestore. In amrestore it's
>listed as set 35 (phse7._vg00_lvol_19.20
>We are looking at a trival method of dividing up the amanda
>disks - group 1) local to server, group 2) remote clients.
That will work very easily. No special (source code) work required.
>Since one amanda will never actually touch the ethernet interface
>is there another method or work-around
On Sat, 25 Jan 2003, John R. Jackson wrote:
>Sorry it took so long to get back to you.
>
>I was able to reproduce (and even fix :-) the problem. Give the
>following patch a try.
Hi John.
This patch works great. Thanks for your time/efforts.
--david
Hi
Apologies for the level of this question, I'm sure the answer is around on
the web, but I can't find it!
(Is there a "Idiots Guide to setting up your first Amanda install"?)
Anyway, got a 10 tape Overland XB tape stacker, with a dlt 7000 drive, and
I'm looking to find a suitable chg-multi.conf
Since I'm having trouble with my tool of choice (amrecover) today (see my
previous mails on this(, I'm trying to simply get a backup set off of a
Amanda tape using amrestore (which I have never used before).
I see the set I want going by in amverify, and amrestore. In amrestore it's
listed as set
John,
This is exactly what we are thinking of doing at my site.
We are looking at a trival method of dividing up the amanda
disks - group 1) local to server, group 2) remote clients.
With lots of local disk, fiber channel... this sort of makes
sense and will allow us to utilize both of our (loca
Replying to my own messgae is bad form, I know, but I left out the fact
that when I run amverify on the tape(s0 in question, they recognize that
the dumps were created by vxfdump.
On Mon, Jan 27, 2003 at 09:59:13AM -0500, stan wrote:
> I;m having problems getting a backup restored. Here's the scen
I ran amtapetype -e 8192 (which should have been half of this) -f
/dev/nst0 -t SONY_SDT-7000
It took two days to run. Here are the results:
define tapetype SONY_SDT-7000 {
comment "hardware compression off"
length 114668 mbytes
filemark 910304 kbytes
speed 24 kps
I went trough the same yesterday...
turned out I didn't have amanda-client installed on the client AT ALL none the
less!!!
Obviously make sure you have amanda and amanda-client installed on the client,
make sure you have an entry for your server in ~amanda/.amandahosts (or
~/operator... depen
I;m having problems getting a backup restored. Here's the scenario.
Tape server machine Debian GNU link "testing", running Amanda 2.4.3b4
Client machine HP-UX 10.20 running Amanda 2.4.2p1, and with VXFS filesystems
(I think this is important).
I'm running amrecover on the client, and all is goi
Am Mon, 2003-01-27 um 09.54 schrieb Gerhard den Hollander:
> * Martin Oehler <[EMAIL PROTECTED]> (Fri, Jan 24, 2003 at 05:11:39PM +0100)
> > I'm sorry, I made a mistake. The hardware compression was off
> > all the time. :(
>
> That's exactly what it looked like ;)
Hehe, do you know what's funny?
On Sat, Jan 25, 2003 at 12:34:47PM -0500, John R. Jackson wrote:
> >Can amanda send a signal to my DLT IV to unload the tape after
> >backups are finished, so whoever goes back to swap tapes can
> >just do it without waiting to manually unload?
>
> The standard "trick" is to call either "amtape e
* Martin Oehler <[EMAIL PROTECTED]> (Fri, Jan 24, 2003 at 05:11:39PM +0100)
> Hi!
>
> Am Fre, 2003-01-24 um 16.22 schrieb Gene Heskett:
> > On Friday 24 January 2003 08:53, Martin Oehler wrote:
> > >Why is the length the same? Seems like switching the compression
> > > modes with mt is not working
26 matches
Mail list logo