Hi Guys
I am using amrecover on a remote machine to restore a file from my file server. The
file I am trying to restore is on a Solaris server and is mount on /.5. I run the
following command :
amrecover setdisk c1t2d0s0 /.5
200 Disk set to c1t2d0s0
I get the following error when trying to
hello,
my Amanda backup server mounts some NFS filesystems
exported from machines that are in fact
Amanda backup clients.
Should I better install the Amanda client software
on the backup machines, or may I directly
make a reference to the NFS filesystems into the
disklist as if it
Use the gtar and the exclude-list option. Add something like this to your
dumptype:
options exclude-list "/some/dir/you/choose/file_name"
In this file you must refence the directories you don't want from the
directory they live in. For example if you have /var on a partition and
did not want
Thanks for the help.
As it turns out, I had the wrong machine ("ozzy") in the share directory
location. The share name is "ozzybkup" and is located on vedder. I
updated
the following and it works:
disklist contains: vedder //vedder/ozzybkup windows-test
/etc/amandapass contains:
We just built 242p1 and are getting errors contacting the index server from
amrecover. We get the following error:
% amrecover -C DailySet1 -s localhost -t localhost -d /dev/nst0
AMRECOVER Version 2.4.2p1. Contacting server on localhost ...
amrecover: Unexpected server end of file
Here's
Are there perhaps index file incompatibilities between 242 and 242p1?
amrecover is working fine on the machine it was built on, but not on the
machine below, which has been running 242
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Carey Jung
Is there a way to set amanda to only backup certain directories inside a
file system instead of a whole partition?
In addition to the comments from Mike and Andrew, you can also look at:
ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper.*
Among other things, (the ideas behind) that wrapper
Should I better install the Amanda client software
on the backup machines, or may I directly
make a reference to the NFS filesystems into the
disklist as if it was a local filesystem?
I suspect you'll get better performance if you install the Amanda client
software on those machines and
I thought this was working ... any idea what to check?
How about the FAQ (www.amanda.org)? This comes up almost weekly and is
covered there in detail.
FAILURE AND STRANGE DUMP SUMMARY:
mars sdb2 lev 0 FAILED [mars: [access as amanda not allowed from
[EMAIL PROTECTED]]
This says mars
I've been using amanda for about five years now, with pretty much flawless
operation.
Thanks.
Jamie Bowden
--
"It was half way to Rivendell when the drugs began to take hold"
Hunter S Tolkien "Fear and Loathing in Barad Dur"
Iain Bowen [EMAIL PROTECTED]
Well, I found out the source of my problem through
amcheck - dump was trying to stat /dev/root (instead
of /dev/hdaxx) which didn't work, since /dev/root
doesn't exist.
Now that this problem is solved, though - anybody have
some idea about this /dev/root and why dump sees that
while df etc. see
We just ran across the same problem. It's fixed in 2.4.2p1.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Shreedeep Bhachech
Sent: Monday, March 19, 2001 3:59 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Failed backup of /
I can not get amrecover to work from any clients. ...
When I try to run amrecover, I get the following error:
#amrecover -C daily -s tapeserver
amrecover: Error connecting to server: Invalid arguement.
That section of code has been reworked in the latest 2.4.2 sources to
deal with
i have already installed amanda succesfully i just
need to know how to run the program if i use a
tapedrive can you pls give me a documentation on how
to use the amanda program.Both as standalone servers
or remote server.But the basics will help me a lot!
Have you read "the chapter"?
gethostbyaddr: Success
Hmmm. Have you been playing in the sources? I don't see where this
message would be coming from.
We trussed up amindexd with strace and see the following. ...
amandaidx stream tcp nowait root /usr/bin/strace amindexd -fo
/tmp/amandaidx.strace
On Mon, 19 Mar 2001, John R. Jackson wrote:
I can not get amrecover to work from any clients. ...
When I try to run amrecover, I get the following error:
#amrecover -C daily -s tapeserver
amrecover: Error connecting to server: Invalid arguement.
That section of code has been
I am using amrecover on a remote machine to restore a file from my file server
Are the server and remote machine running the same OS, and are they the
same OS as the client that was backed up? The dump format is not (in
general) compatible between OS's (e.g. Linux and Solaris). Your "Doing
I am using 2.4.2p1. Should I try a development release?
The changes I'm thinking of were done after 2.4.2p1 and are in the
amanda-242-branch of CVS. I'd give you a set of patches except they were
a little more extensive than just a few lines of diffs because they got
tangled up in some other
--- Carey Jung [EMAIL PROTECTED] wrote:
We just ran across the same problem. It's fixed in
2.4.2p1.
Funny you should mention that - I am using 2.4.2p1!
:-/
=
-+
Shreedeep [EMAIL PROTECTED]
__
Do You
Funny you should mention that - I am using 2.4.2p1!
When you ran ./configure, did it say it found setmntent? What do you
get when you run this:
grep SETMNT config/config.h
What does your /etc/fstab line look like for /? What about /proc/mounts?
Shreedeep [EMAIL PROTECTED]
John R.
Actually, now that I think about it a bit more, I'm sure the strace
output you got does not reflect reality. You got a couple of messages
in amindexd*debug that indicate it got further than the strace says.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
On Mar 19, 2001, Terry Koyama [EMAIL PROTECTED] wrote:
disklist contains: vedder //vedder/ozzybkup windows-test
This must be wrong. Is vedder a Unix machine, configured as an Amanda
client? In this case, what's the point of naming is as the SMB server
too?
--
Alexandre Oliva Enjoy
22 matches
Mail list logo
