SOURCE can be a remote location (use the ssh:// syntax), if you use that syntax only one SOURCE can be used. When using this syntax the files are pulled from the remote server using 'ssh'.

There is no provisioning for ssh so unless you have configured ssh to work without a passphrase you will be asked to supply one. Also note that the PATH on the remote host should be set in such a way that all the rdup-utils can be found.

Multiple local sources are allowed, so that:

rdup-restore /backup/home /backup/etc /tmp

Will restore both `/backup/home' and '/backup/etc' to `/tmp'.

Restoring from a backup is as simple as:

rdup-restore /vol/backup/elektron/200604/home /tmp/restore

Note: The restored files "inherit" the `/vol/backup/elektron/200604' prefix. So the restored files are found in the directory: `/tmp/home/vol/backup/elektron/200604/home'.

-k keyfile

Decrypt the files while restoring with keyfile. This option inserts rdup-crypt -d keyfile in the pipeline. If both -z and -k are given files are first decrypted and then uncompressed.

-z

Decompress the files while restoring. This option inserts rdup-gzip -d in the pipeline. If both -z and -k are given a file is first decrypted and then unzipped. This the opposite of what rdup-simple does.

-a

Enable extended attributes. Read the uid/gid to the extended user attributes r_uid and r_gid. See rdup(1) for a more detailed explanation.

-v

Echo the files processed to standard error.

-h

Show a short help message.

-V

Show the version.

-S

Restore a rdup-snapshot backup. This is a hardlinked backup, so one can also restore these with 'cp'. Consider this a convient function.

-D

Restore a rdup-dump backup. Due to the way this backup is made, you can only restore to the latest version of your backup. -D is the default for rdup-restore.

rdup-restore /vol/backup/elektron/200604/home/miekg/bin /tmp/restore

rdup-restore ssh://miekg@remove/home/miekg/bin /tmp/restore