puzzle. If you recall, I switched from Amanda 2.5.1p3 on a Solaris 9 server on an E250 to Amanda
3.3.3 on an Ubuntu 12.04 server on SuperMicro around May 22. The transition seemed to run smoothly.
The old E250 is still running mail services, and the new Amanda server is still
backing that up.
The default index and tape server are set when amanda is compiled, at
the configure step.
You can overwrite the default different ways:
amrecover -s ... -t ...(man amrecover)
add them to amanda-client.conf (man amanda-client.conf)
you can also change the
from the session that I included,
supereclogite is the new 3.3.3 Amanda server, and
eclogite is the old 2.5.1p3 Amanda server.
The old server, eclogite, was added to the disklist on the new server, supereclogite, and has been
backed up there since.
My session is on the new Amanda server
Chris,
I think Jean-Louis nailed the problem with the server and
tape unit. I think amrecover will pass the data stream back
to the client and ufsrestore on the client side, I don't
think you will have any issues after taking JML's advise.
On Mon, Jun 17, 2013 at 02:30:50PM -0400, Chris
On Mon, Jun 17, 2013 at 03:00:44PM -0400, Chris Hoogendyk wrote:
hmm, didn't specify either of those in configure when I built Amanda 3.3.3.
However, now that you mention amanda-client.conf, I went and looked for
that. Turns out they were both specified there (I originally rsynced
hmm, didn't specify either of those in configure when I built Amanda 3.3.3. However, now that you
mention amanda-client.conf, I went and looked for that. Turns out they were both specified there (I
originally rsynced /usr/local/etc/amanda/ to the new server and then went about modifying stuff to
OK. I've got amrestore pulling files off the tape. Then I'll transfer those over to the Solaris
client and ufsrestore what I need locally there. That's less crude than going totally back to manual
basics, but I would still like to work out amrecover. I'll see if I can get that set up to run on
