Scot Hetzel wrote:
Thanks for the hint to use amoldrecover, but I'm still having problems
with it:
# amoldrecover -C Daily -s backup -t backup
AMRECOVER Version 2.5.1p1. Contacting server on backup ...
220 backup AMANDA index server (2.4.4p3) ready.
200 Access OK
Setting restore date to today (
"Dustin J. Mitchell" <[EMAIL PROTECTED]> wrote: On Jan 4, 2008 3:29 PM,
Jean-Louis Martineau wrote:
> You must use the 'amoldrecover' command.
>
> The amrecover command (in 2.5.1 and newer) can only talk to 2.5.1 or
> newer server. amoldrecover must be used to talk to older server.
I just added
On Jan 4, 2008 3:29 PM, Jean-Louis Martineau <[EMAIL PROTECTED]> wrote:
> You must use the 'amoldrecover' command.
>
> The amrecover command (in 2.5.1 and newer) can only talk to 2.5.1 or
> newer server. amoldrecover must be used to talk to older server.
I just added some information about this to
You must use the 'amoldrecover' command.
The amrecover command (in 2.5.1 and newer) can only talk to 2.5.1 or
newer server.
amoldrecover must be used to talk to older server.
Jean-Louis
Scot Hetzel wrote:
We have an Amanda backup server running 2.4.4, we are able to run
amrecover on this sys
We have an Amanda backup server running 2.4.4, we are able to run amrecover on
this system:
# amrecover Daily
AMRECOVER Version 2.4.4p3. Contacting server on localhost ...
220 vpinew AMANDA index server (2.4.4p3) ready.
200 Access OK
Setting restore date to today (2008-01-04)
200 Working date set
