On Monday 27 January 2003 12:19 pm, Nigel Barker wrote:
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
Hi all,
After searching the archives, I can't seem to find an answer to a
nagging little problem-- one of my clients is a Solaris 8 machine
running software RAID, so its devices begin with /dev/md/dsk
However, AMANDA does not have this as one of her defined prefixes, so
I'm forced to put the
I usually backup stuff in Amanda by using the name of the
mount point rather than the device name.
Hi all,
After searching the archives, I can't seem to find an answer to a
nagging little problem-- one of my clients is a Solaris 8 machine
running software RAID, so its devices begin with
On 28 Jan 2003 at 8:54am, Eric Sproul wrote
Hi all,
After searching the archives, I can't seem to find an answer to a
nagging little problem-- one of my clients is a Solaris 8 machine
running software RAID, so its devices begin with /dev/md/dsk
However, AMANDA does not have this as one
On Tue, 2003-01-28 at 09:36, Joshua Baker-LePain wrote:
It looks like this is defined (as DEV_PREFIX and RDEV_PREFIX) in
config/config.h based on the results of ./configure. You could add the
check to the configure script or just change the values of (R)DEV_PREFIX
in config.h. I'm not
On 28 Jan 2003 at 9:59am, Eric Sproul wrote
On Tue, 2003-01-28 at 09:36, Joshua Baker-LePain wrote:
Well, IMO, mount points look a lit nicer than device names. They also
stay consistent should the underlying hardware/config change. Just my
$0.02.
I've gotten several responses to
On Tue, 2003-01-28 at 10:38, Joshua Baker-LePain wrote:
Indeed. My reasoning is that as users get confused rather easily
(poor users), it's best (for them, and more importantly, for you) to keep
their data in the same place regardless of the underlying hardware. :)
I'm in a different
On Sat, Jan 25, 2003 at 12:34:47PM -0500, John R. Jackson wrote:
The standard trick is to call either amtape CONFIG eject or
(what I do) amtape CONFIG slot advance after the amdump run. For
instance:
amdump CONFIG ; amtape CONFIG slot advance
So I did this last night, and today all
On Tue, 2003-01-28 at 09:36, Joshua Baker-LePain wrote:
It looks like this is defined (as DEV_PREFIX and RDEV_PREFIX) in
config/config.h based on the results of ./configure. You could add the
check to the configure script or just change the values of (R)DEV_PREFIX
in config.h. I'm not
I've copied my original amanda configuration into two
separate/new directories.
ie /usr/local/etc/amanda/ninfo becomes both
/usr/local/etc/amanda/newtonr and
/usr/local/etc/amanda/newtonl
(left and right drives, local and remote client, your pick).
I modified the files in newtonr to
On Tue, Jan 28, 2003 at 08:11:54AM -0500, Chris Dahn wrote:
On Monday 27 January 2003 12:19 pm, Nigel Barker wrote:
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
Hello everyone,
When I attempt to use amlabel to label a tape on a Tandberg/Quantum
SDLT 220, it produces the following error:
[amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100
rewinding, reading label, reading label: Value too large for defined data type
rewinding, writing label
Got this:
These dumps were to tape Indyme007.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: Indyme006.
FAILURE AND STRANGE DUMP SUMMARY:
cm
I don't think I quite grok the way amanda schedules backups.
I had three tapes for the DLT drive, and amanda seemed to be rotating
through them just fine. I got five more tapes, labelled them, and added
them to the rotation. The first weird thing is, it asked for tape 1,
then tape 8, then tape
On Tue, Jan 28, 2003 at 09:20:24AM -0800, John Oliver wrote:
I don't think I quite grok the way amanda schedules backups.
I had three tapes for the DLT drive, and amanda seemed to be rotating
through them just fine. I got five more tapes, labelled them, and added
them to the rotation. The
On Tue, Jan 28, 2003 at 10:07:21AM -0800, Jay Lessert wrote:
It uses tapes in whatever order they appear in tapelist.
Amanda doesn't care about your numerical order, the tapes
could be named tape_frog, tape_tree, tape_blue, they're
all just strings.
You can amrmtape, re-label, and
On Tue, 28 Jan 2003 at 9:20am, John Oliver wrote
I had three tapes for the DLT drive, and amanda seemed to be rotating
through them just fine. I got five more tapes, labelled them, and added
them to the rotation. The first weird thing is, it asked for tape 1,
then tape 8, then tape 7, then
On Tue, Jan 28, 2003 at 01:28:37PM -0500, Joshua Baker-LePain wrote:
dumpcycle 4 days
Amanda will get a full backup of every disk list entry (DLE) at least once
every four days. If you run backups M-Th, Monday is going to be a busy
day...
runspercycle 4
You'll run amanda 4 times
On Tue, 28 Jan 2003 at 10:16am, John Oliver wrote
On Tue, Jan 28, 2003 at 10:07:21AM -0800, Jay Lessert wrote:
It uses tapes in whatever order they appear in tapelist.
Amanda doesn't care about your numerical order, the tapes
could be named tape_frog, tape_tree, tape_blue, they're
all
...the number of times each tape has been used? So, after a given tape
has been used X times, amanda can send a reminder to replace it?
--
John Oliver, CCNAhttp://www.john-oliver.net/
Linux/UNIX/network consulting http://www.john-oliver.net/resume/
***
Solaris 8, Amanda 2.4.2p2 (plus /usr/local/libexec/chg-zd-mtx from 2.4.3)
SUN StorEdge 9,
/usr/local/sbin/mtx -f /dev/scsi/changer/c6t4d0 inquiry
Product Type: Medium Changer
Vendor ID: 'HP '
Product ID: 'C7145 '
Revision: '233S'
Attached Changer: No
Config works perfectly with
On Tuesday 28 January 2003 12:13, Tim Souder wrote:
Hello everyone,
When I attempt to use amlabel to label a tape on a
Tandberg/Quantum SDLT 220, it produces the following error:
[amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100
rewinding, reading label, reading label: Value too large
Hello Gene,
Unfortunately, the labelstr parameter is:
labelstr ^DailySet1[0-9][0-9]*$
Thanks though,
Tim
On Tue, 28 Jan 2003, Gene Heskett wrote:
On Tuesday 28 January 2003 12:13, Tim Souder wrote:
Hello everyone,
When I attempt to use amlabel to label a tape on a
Tandberg/Quantum SDLT
On Tue, 28 Jan 2003 at 10:39am, John Oliver wrote
On Tue, Jan 28, 2003 at 01:28:37PM -0500, Joshua Baker-LePain wrote:
dumpcycle 4 days
Amanda will get a full backup of every disk list entry (DLE) at least once
every four days. If you run backups M-Th, Monday is going to be a busy
On Tue, 28 Jan 2003 at 10:54am, John Oliver wrote
I run amanda each Tuesday, Wednesday, Thursday, Friday, and Saturday
mornings. I do want to get more tapes, so I have a multiple of 5.
Then your dumpcycle should be 1 week and your runspercycle should be 5.
You'll need more tapes
On Tue, Jan 28, 2003 at 03:27:11PM -0500, Joshua Baker-LePain wrote:
On Tue, 28 Jan 2003 at 10:39am, John Oliver wrote
On Tue, Jan 28, 2003 at 01:28:37PM -0500, Joshua Baker-LePain wrote:
dumpcycle 4 days
Amanda will get a full backup of every disk list entry (DLE) at least once
Hi,
i am a PhD student at RICE University. i need to use amanda to
take backup on a disk rather than tape. Do i need to change anything in
source code and recompile everything or there is some parameter which can
be set to specify this while installing Amanda.
I installed Amanda
On Tue, 28 Jan 2003 at 12:30pm, John Oliver wrote
On Tue, Jan 28, 2003 at 03:27:11PM -0500, Joshua Baker-LePain wrote:
On Tue, 28 Jan 2003 at 10:39am, John Oliver wrote
On Tue, Jan 28, 2003 at 01:28:37PM -0500, Joshua Baker-LePain wrote:
dumpcycle 4 days
Amanda will get a
On Tue, 28 Jan 2003 at 2:41pm, Ajay Gulati wrote
i am a PhD student at RICE University. i need to use amanda to
take backup on a disk rather than tape. Do i need to change anything in
source code and recompile everything or there is some parameter which can
be set to specify this while
On Mon, Jan 27, 2003 at 11:48:06PM -0500, Scott Mcdermott wrote:
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 ?
Hello,
I've been following tis great How To to set up a couple of OS X
machines as Amanda clients:
http://web.brandeis.edu/pages/view/Bio/AmandaMacOSXCompileNotes
It's rather comprehensive, but I've run into a question beyond the scope
of the document. In my disklist file, I want to add
On Tue, Jan 28, 2003 at 02:07:27PM -0500, Brian Cuttler wrote:
Solaris 8, Amanda 2.4.2p2 (plus /usr/local/libexec/chg-zd-mtx from 2.4.3)
SUN StorEdge 9,
/usr/local/sbin/mtx -f /dev/scsi/changer/c6t4d0 inquiry
Product Type: Medium Changer
Vendor ID: 'HP '
Product ID: 'C7145
First off, sorry for not being active on the list lately;
I've been really busy on other fronts...
Just to be clear, the RAIT code is basically RAID 4, The data for
*each block* written is striped on n-1 drives and the xor sum is written
on the last drive. This does have fallout, in particular
I am backing up two boxes, the server and one client, both linux redhat 8.0 on
the server and 7.3 on the client. don't seem to have a problem backing up,
when I try running amrecover I get:
[root@tigger testrest]# amrecover -s garfield -C Daily-Backup-Set1
AMRECOVER Version 2.4.2p2. Contacting
On Tue, 28 Jan 2003 at 5:56pm, Riccardo Parola wrote
I am backing up two boxes, the server and one client, both linux redhat 8.0 on
the server and 7.3 on the client. don't seem to have a problem backing up,
when I try running amrecover I get:
[root@tigger testrest]# amrecover -s garfield
Hi Tim,
Your tape drive is set to variable block size?
You didn't set '--with-maxtapeblocksize=' at configure?
Could you use 'dd if=/dev/nst0 of=/dev/null bs=32k' to read the tape.
Try erasing your tape.
Jean-Louis
On Tue, Jan 28, 2003 at 12:13:31PM -0500, Tim Souder wrote:
Hello everyone,
I install amanda on an server and two clients:
sever(tape server) - RedHat Linux 7.3
client_1 - RedHat Linux 7.3
client_2 - SunOS, Ultra-5_10
The installation on the clients are similar.
I have no problem to run amdump vs. the client_1.
I have trouble to run amdump vs.
Hello,
I'm new to amanda and need some direction.
I've installed the latest snap shot 2.5.0-20030127 and configured
everything the best I know how from the UNIX Backup and Recovery Book
and all the amanda docs.
However, when I run the amcheck, I immediately get a segmentation
fault. Should I
On 28 Jan 2003 at 10:37pm, Jeff Borders wrote
However, when I run the amcheck, I immediately get a segmentation
fault. Should I revert to a stable version and stay away from the snap
shot? Is 2.4.3-20030127 a corrected version of 2.4.3?
Yes. No. The dated 2.4.3 packages are snapshots of
On Tue, 28 Jan 2003, Riccardo Parola wrote:
[root@tigger testrest]# amrecover -s garfield -C Daily-Backup-Set1
AMRECOVER Version 2.4.2p2. Contacting server on garfield ...
220 garfield AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2003-01-28)
200 Working
e-mail
listemizden seçilmiþ kýsýtlý bir guruba
31.01.2003 akþamýna kadar özel indirim uyguluyoruz.
Ýnternette Tüm
Ýngilizce sayfalar þimdi Türkçe
Ýnternette
baðlandýðýnýz
Ýngilizce sayfalarý
Could someone please tell me how I can fix this? It's the only error I
have left when I run amcheck. Below is the xinetd amanda file.
Jan 29 02:06:54 curly xinetd[5434]: execv( /usr/local/libexec/amandad ) failed:
Permission denied (errno = 13)
Jan 29 02:06:54 curly xinetd[1460]: Deactivating
Hi,
We've been running amanda-2.4.2p2-tapeio for quite a while now and have been very
happy with it.
I'm now setting up a new backupserver and am planning to run 2.4.3 on it (of course) -
which leads me to this quick (and possibly dumb) question:
Is tapeio included with 2.4.3 or do I need extra
43 matches
Mail list logo
