John,
amrecover: did not get a reserved port: 50014
When compiled I used the flag --with-portrange=5,50100
...
Any suggestions as to what I am doing wrong?
You didn't do anything wrong -- I did :-).
Like a true professional I waited until I needed to do a restore before
You're right. I think it's better to work with amanda numbering the
tapes with labels like 1, 2, 3, etc, and not with Monday, Tuesday, etc.
I have already considered this option, but we want to be sure of all
possibilities, and the option of labelling tapes with the names of the
days of the
Thanks everybody for your helpful responses. All of them had
different and useful tips. I'll try to summarize and add some
comments.
i) Regarding compression on FreeBSD: thanks John (Merryweath) for
reminding me of mt.
I have now turned HW compression ON host control ON and I can
manage it
Hi! Thanks to Jon LaBadie and John R. Jackson for helping me get gtar exclusion
lists up and running -- it seems to have worked!
Ricky
-
Richard MorseSystem Administrator
MGH Biostatistics Center 50 Staniford St. Rm
Reading John's excellent chapter got me to thinking...I should purge old
index files as well after I have completed my tape rotation. Since once
that tape is overwritten that index in null and void. Can anybody
contradict that thinking.
Don
Title: help had to reconfig disks on a server
One of my servers suffered a failure yesterday and out of that I had to move some disks around but now amanda is going to think they're new disks. For example the old disk was /dev/vx/dsk/rootdg/Compuset and it's now /dev/vx/dsk/sys_dg/Compuset.
You could try copying the info file of the old name to the info file of
the name. I'm not sure if you would need to adjust the /etc/dumpdates
as well on the server though.
Just a thought...
Stott, Trevor wrote:
One of my servers suffered a failure yesterday and out of that I
On Wed, 27 Mar 2002 at 10:26am, Stott, Trevor wrote
One of my servers suffered a failure yesterday and out of that I had to move
some disks around but now amanda is going to think they're new disks. For
example the old disk was /dev/vx/dsk/rootdg/Compuset and it's now
I´am running amanda 2.4.2p2 in debian linux (installing from apt-get
)
My error is :
ERRROR: backup: [access as backup not allowed from backup@backup]
amandahostsauth failed
Who is my problem?
Who is the diference in Debian and other linux distributions?
I am trying to get Amanda clients to not do copression, but have the
server do the compression. I had thought that this would happen by
changing the dumptype record for comp-root-tar to have:
compress server fast
instead of
compress client fast
When I watch the clients
Hi Pablo,
I believe the source of the error you mention is from the client. You
may need to check the .amandahosts file on the client for the user
under which the client runs. In other words, if in your INETD (or
XINETD) the amanda client runs as backup, the .amandahosts in
backup's home
On Wed, 27 Mar 2002 at 2:06pm, Pablo Miscevich wrote
I´am running amanda 2.4.2p2 in debian linux (installing from apt-get
)
One should always compile amanda from source. A lot of stuff gets
compiled in, and it helps one figure out what's going on.
My error is :
ERRROR: backup:
Pablo Miscevich wrote:
I´am running amanda 2.4.2p2 in debian linux (installing from apt-get
)
My error is :
ERRROR: backup: [access as backup not allowed from backup@backup]
amandahostsauth failed
Who is my problem?
Who is the diference in Debian and other linux distributions?
Using amrecover in 2.4.2p2 on Digital Unix 4.0, I'm getting a restore
error.
In the amrecover log I see:
Exec'ing /sbin/restore with arguments:
restore
xbf
2
-
/amanda_dev.orig
amrecover: pid 4113 finish time Wed Mar 27 10:48:36 2002
And I get a
On our systems, we ran into debian creating a local user named backup. That
caused problems with our NIS backup user. So we deleted the local and
everything worked.
I´am running amanda 2.4.2p2 in debian linux (installing from apt-get
)
My error is :
ERRROR: backup: [access as backup
v) Gene said: Any partition thats that much gzipped already, should have the
compression turned off, doing a straight tar of it.
Again, I'm a newbie, and if I decided not to use tar, was not based on
my own experience but from what I've read elsewhere.
Not trying to speak for Gene, but I don't
Like a true professional I waited until I needed to do a restore before
testing! ...
A real pro! :-)
This is a known problem from about a year ago. ...
Did I miss this in the FAQs or should I add this? I didn't see it on the
amanda bugs page.
Well, the theory was that it wouldn't be years
...I should purge old
index files as well after I have completed my tape rotation. ...
Amanda does this for you via a program called amtrmidx that is called
at the end of every amdump.
It figures out how long the tape cycle is, goes back to the level 0
preceeding that date, then throws away
If I issue the command as you've given it above, I get the same block
size error. ...
Good. That means you have a valid test case.
If I change the 2 to a 4, it does the same. ...
OK.
If I remove
the b and the 2 all-together, it them waits for the image file from
stdin (I guess). ...
Has anyone out there successfully configured amanda to backup to a spare
hard drive without backing up to tape?
Thanks in advance.
- db
Hi all,
I've heard of Amanda for some time, but am just now starting to look at it
as a potential backup solution. From what I've read so far, I'm not 100%
sure it will be of a big benefit to us. Here's what we are looking at it
for:
- single system (SPARCServer 1000)
- using Veritas Volume
Thanks very much John. The amadmin command helped out a lot. I found
that the one client that I was testing was still set to comp-user-tar.
Changing these to comp-root-tar fixed it for me. Sorry for wasting your
time. My eyes saw what they wanted to in disklist I guess.
It is working very
On Wed, 27 Mar 2002 21:45:26 + (GMT), Dan Barnes
[EMAIL PROTECTED]|said:
|Has anyone out there successfully configured amanda to backup to a
|spare hard drive without backing up to tape?
not a solution to your problem (sorry), but a question in regards to
media:
is there any chance of
On Wednesday, March 27, 2002, at 01:45 PM, Dan Barnes wrote:
Has anyone out there successfully configured amanda to backup to a spare
hard drive without backing up to tape?
I've set up a system using 2.4.2p2 to backup to nfs mounted drive space
just recently. If you are able to use 2.4.3,
I've heard of Amanda for some time, but am just now starting to look at it
as a potential backup solution. ...
Welcome!
From what I've read so far, I'm not 100%
sure it will be of a big benefit to us. ...
That's always a possibility, and you're wise to look before you leap.
Currently using
On Wednesday 27 March 2002 09:03 am, Fernan Aguero wrote:
Thanks everybody for your helpful responses. All of them had
different and useful tips. I'll try to summarize and add some
comments.
i) Regarding compression on FreeBSD: thanks John (Merryweath) for
reminding me of mt.
I have now turned
Hi! How stable is the Win32 Amanda Client found on SourceForge? I have a few
NT/Win2K boxes that I would like to add to my backup, and I'm looking at the
different options available...
Thanks,
Ricky
-
Richard MorseSystem
On Wednesday 27 March 2002 04:07 pm, John R. Jackson wrote:
v) Gene said: Any partition thats that much gzipped already,
should have the compression turned off, doing a straight tar
of it.
Again, I'm a newbie, and if I decided not to use tar, was not
based on my own experience but from what
28 matches
Mail list logo
