From 06ffd8f3ad4c92751de072a33bbb2ac23fa166bd Mon Sep 17 00:00:00 2001
From: Marco van Wieringen <marco.van.wieringen@bareos.com>
Date: Sat, 4 May 2013 13:14:53 +0200
Subject: [PATCH] Add copies to the allowed keyword for restore.

Its seems that you can use a set of copy jobs to do a restore when you
specify the copies keyword on the restore commandline.

e.g. restore copies will select instead of the normal
full/differential/incremental jobs the copies of those Jobs. When doing
offsite SD-SD replication this can be a good selection criteria when you
lost your primay storage daemon but can restore from the secondary
or standby storage daemon. As long as you have a working database this
is a good DR procedure. You still need a working director and database
but as the database can be replicated as an HA solution and a director
also have a cold standby this could be part of a solution.

Fixes #36: Implementation of restore using a set of copies of an original job
---
 src/dird/ua_cmds.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/dird/ua_cmds.c b/src/dird/ua_cmds.c
index 80a51fdc633..3d889db9fad 100644
--- a/src/dird/ua_cmds.c
+++ b/src/dird/ua_cmds.c
@@ -170,7 +170,7 @@ static struct cmdstruct commands[] = {
      NT_(""), false },
    { NT_("restore"), restore_cmd, _("Restore files"),
      NT_("where=</path> client=<client-name> storage=<storage-name> bootstrap=<file>\n"
-         "\trestorejob=<job-name> comment=<text> jobid=<jobid> done select all"), false },
+         "\trestorejob=<job-name> comment=<text> jobid=<jobid> copies done select all"), false },
    { NT_("relabel"), relabel_cmd, _("Relabel a tape"),
      NT_("storage=<storage-name> oldvolume=<old-volume-name>\n"
          "\tvolume=<new-volume-name> pool=<pool-name> [ encrypt ]"), false },