@@ -121,22 +121,130 @@ A simple way of restoring a given client to a given point in time is
to use the option. So:
1. enter `bconsole` in a shell on the director
2. call the `restore` command
2. call the `restore` command:
*restore
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
First you select one or more JobIds that contain files
to be restored. You will be presented several methods
of specifying the JobIds. Then you will be allowed to
select which files from those JobIds are to be restored.
3. you now have a list of possible ways of restoring, choose: `5:
Select the most recent backup for a client`
Select the most recent backup for a client`:
To select the JobIds, you have the following choices:
1: List last 20 Jobs run
2: List Jobs where a given File is saved
3: Enter list of comma separated JobIds to select
4: Enter SQL list command
5: Select the most recent backup for a client
6: Select backup for a client before a specified time
7: Enter a list of files to restore
8: Enter a list of files to restore before a specified time
9: Find the JobIds of the most recent backup for a client
10: Find the JobIds for a backup for a client before a specified time
11: Enter a list of directories to restore for found JobIds
12: Select full restore to a specified Job date
13: Cancel
Select item: (1-13): 5
4. you will see a list of machines, pick the machine you want to
restore from by entering its number
restore from by entering its number:
Defined Clients:
1: alberti.torproject.org-fd
[...]
117: yatei.torproject.org-fd
Select the Client (1-117): 87
5. you now get dropped in a file browser where you use the `mark` and
`unmark` commands to mark and unmark files for restore. the
commands support wildcards like `*`. use `mark *` to mark all
files in the current directory, see also the [full list of
commands](https://www.bacula.org/9.4.x-manuals/en/main/Restore_Command.html#SECTION0026130000000000000000). do not use the `estimate` command as it can take a
8. this doesn't restore the backup immediately, but schedules a *job*
that does so, like such:
...
...
@@ -145,16 +253,73 @@ to use the option. So:
You can see the status of the jobs on the director with the `status
director`, but also see specifically the status of that job with
`llist jobid=107693`. The `JobStatus` column is an internal database
field that will show `T` ("terminated normally") when completed or `R`
or `C` when still running or not started, and anything else if, well,
anything else is happening. The full list of possible statuses is
[hidden deep in the developer documentation](https://www.bacula.org/9.4.x-manuals/en/developers/Catalog_Services.html#SECTION001015000000000000000), obviously.
`llist jobid=107693`:
*llist JobId=107697
jobid: 107,697
job: RestoreFiles.2019-08-02_16.43.40_17
name: RestoreFiles
purgedfiles: 0
type: R
level: F
clientid: 9
clientname: dictyotum.torproject.org-fd
jobstatus: R
schedtime: 2019-08-02 16:43:08
starttime: 2019-08-02 16:43:42
endtime:
realendtime:
jobtdate: 1,564,764,222
volsessionid: 0
volsessiontime: 0
jobfiles: 0
jobbytes: 0
readbytes: 0
joberrors: 0
jobmissingfiles: 0
poolid: 0
poolname:
priorjobid: 0
filesetid: 0
fileset:
hasbase: 0
hascache: 0
comment:
The `JobStatus` column is an internal database field that will show
`T` ("terminated normally") when completed or `R` or `C` when still
running or not started, and anything else if, well, anything else is
happening. The full list of possible statuses is [hidden deep in the
