Restore Where

The Restore Where page specifies the destination directory for recovered files. Before attempting a restore, you may want to review the Requirements for Restore Clients section of the pre-installation checklist.

Restore Where Page Overview

Restore Where Overview 

The Restore Where defines where the data is to be restored. It also lets you control how the file restore operation proceeds. For example, you can choose whether to permit overwriting of existing files.

Restore Where Page Options

Restore Where

Restore Destination Settings Panel

The Restore Destination Settings panel (left) defines the following parameters:

Destination Host 
The Destination Host is the machine where you want restore the files. It need not be the same machine that originally contained the backed up data.
If no Destination Host is specified, the files are restored to the Amanda server machine. The Destination Host must have ssh available, and grant ssh access to the appropriate user (as explained in Destination Host Type below).
Destination Host Type 
Choose either Linux/Unix or Windows.
  • If the Destination Host is defined as Linux/UNIX the data will be restored as user root. You can specify a different user such as amandabackup to execute the restore.
  • If the Destination Host is running Windows, then the data will be restored as user amandabackup.
Warning: When the Host Directory is 'Linux/Unix and the Destination Directory is Windows, the Run Restore action returns the following warning message:
"WARNING: Permissions will not be preserved on the destination. Restore will appear to have failed"
You can usually ignore this message, as the files will be restored to the selected target.
Destination Username 
Specifies the OS user on the destination machine that will provide access to the restore process. If the Destination Host has Amanda client installed, the user has to be root.  
If you are restoring to a machine that does not have Amanda client installed, restoration will be done using ssh. ssh must be configured on the Destination Host and the ssh user can be specified as Destination Username.
Note: When the Restore process is run, the password will be required to access the destination host if the destination host does not have Amanda client installed.
Destination Directory 
The directory on the Destination Host where the files will be restored. If left empty, files are restored to their original location.
Warning: The Destination Directory MUST be specified as an absolute path.
Note: You cannot restore to a mapped drive. If you attempt to do so, the following error is returned:
Status of Restore: FailureClear Output
ERROR: Restore to Mapped Drives is Not Supported
ERROR: Error receiving Restore Session Info Acknowledgement from the Client
Error restoring the selected files
Temporary Directory 
A directory on the Destination Host that ZMC will use temporarily during the restore process.

Restoring to a Client Without Root Privileges

  1. If you have not done so, install the Zmanda client software as described here.
  2. Make sure that zmrecover is enabled on the client. Examine /etc/xinetd.d/zmrecover to make sure it includes the following line
  3. disable = no
    Or, on Mac OSX systems, run the following command:
            launchctl load -w /Library/LaunchDaemons org.amanda.zmrecover.plist.

    Regardless of client platform, the /etc/amanda/amanda-client.conf file must be edited on the client (if the client and server do not reside on the same machine). Specifically, the following entries must be edited:
    index_server "localhost"        # your amindexd server
    tape_server  "localhost"        # your amidxtaped server

    Change "localhost" to match to the hostname of the  Amanda backup server.

  4.  Launch the ZMC in your browser and go to the Restore-Where page. Select Linux/UNIX/Mac OSX as the Destination Host Type. For the Destination Username, specify ***ROOT***.  Complete the restore as you normally would; the restore procedes as ***ROOT*** without requiring a password.

Conflict Resolution

Conflict Resolution Panel 

The radio buttons in the right panel let you set how to handle filename conflicts in the destination directory (check one):

Keep Existing Files 
If checked (the default), ZMC does not overwrite any existing files on the destination directory. Conflicting files are simply skipped.
Overwrite Existing Files 
If checked, the entire pathnames of existing files on the destination will be overwritten by the backed-up versions, if any. Use with extreme caution.
Rename Existing Files 
If checked, name conflicts are resolved by renaming the existing file (and the entire directory path to that file) using the following convention: original_filename.original.timestamp.
Rename Restored Files 
If checked, name conflicts are resolved by renaming the existing file (and the entire directory path to that file) using the following convention: original_filename.original.timestamp.