4 \section*{The Bacula Console Restore Command}
5 \label{_ChapterStart13}
6 \index[general]{Command!Bacula Console Restore }
7 \index[general]{Bacula Console Restore Command }
8 \addcontentsline{toc}{section}{Bacula Console Restore Command}
11 \index[general]{General }
12 \addcontentsline{toc}{subsection}{General}
14 Below, we will discuss restoring files with the Console {\bf restore} command,
15 which is the recommended way of doing it. However, there is a standalone
16 program named {\bf bextract}, which also permits restoring files. For more
17 information on this program, please see the
18 \ilink{Bacula Utility Programs}{bextract} chapter of this manual.
19 You will also want to look at the {\bf bls} program in the same chapter, which
20 allows you to list the contents of your Volumes. Finally, if you have an old
21 Volume that is no longer in the catalog, you can restore the catalog entries
22 using the program named {\bf bscan}, documented in the same
23 \ilink{Bacula Utility Programs}{bextract} chapter.
25 In general, to restore a file or a set of files, you must run a {\bf restore}
26 job. That is a job with {\bf Type = Restore}. As a consequence, you will need
27 a predefined {\bf restore} job in your {\bf bacula-dir.conf} (Director's
28 config) file. The exact parameters (Client, FileSet, ...) that you define are
29 not important as you can either modify them manually before running the job or
30 if you use the {\bf restore} command, explained below, Bacula will
31 automatically set them for you. In fact, you can no longer simply run a restore
32 job. You must use the restore command.
34 Since Bacula is a network backup program, you must be aware that when you
35 restore files, it is up to you to ensure that you or Bacula have selected the
36 correct Client and the correct hard disk location for restoring those files.
37 {\bf Bacula} will quite willingly backup client A, and restore it by sending
38 the files to a different directory on client B. Normally, you will want to
39 avoid this, but assuming the operating systems are not too different in their
40 file structures, this should work perfectly well, if so desired.
41 By default, Bacula will restore data to the same Client that was backed
42 up, and those data will be restored not to the original places but to
43 {\bf /tmp/bacula-restores}. You may modify any of these defaults when the
44 restore command prompts you to run the job by selecting the {\bf mod}
48 \subsection*{The Restore Command}
49 \index[general]{Command!Restore }
50 \index[general]{Restore Command }
51 \addcontentsline{toc}{subsection}{Restore Command}
53 Since Bacula maintains a catalog of your files and on which Volumes (disk or
54 tape), they are stored, it can do most of the bookkeeping work, allowing you
55 simply to specify what kind of restore you want (current, before a particular
56 date), and what files to restore. Bacula will then do the rest.
58 This is accomplished using the {\bf restore} command in the Console. First you
59 select the kind of restore you want, then the JobIds are selected,
60 the File records for those Jobs are placed in an internal Bacula directory
61 tree, and the restore enters a file selection mode that allows you to
62 interactively walk up and down the file tree selecting individual files to be
63 restored. This mode is somewhat similar to the standard Unix {\bf restore}
64 program's interactive file selection mode.
66 If your Files have been pruned, the {\bf restore} command will be unable
67 to find any files to restore. See below for more details on this.
69 Within the Console program, after entering the {\bf restore} command, you are
70 presented with the following selection prompt:
74 First you select one or more JobIds that contain files
75 to be restored. You will be presented several methods
76 of specifying the JobIds. Then you will be allowed to
77 select which files from those JobIds are to be restored.
78 To select the JobIds, you have the following choices:
79 1: List last 20 Jobs run
80 2: List Jobs where a given File is saved
81 3: Enter list of comma separated JobIds to select
82 4: Enter SQL list command
83 5: Select the most recent backup for a client
84 6: Select backup for a client before a specified time
85 7: Enter a list of files to restore
86 8: Enter a list of files to restore before a specified time
87 9: Find the JobIds of the most recent backup for a client
88 10: Find the JobIds for a backup for a client before a specified time
89 11: Enter a list of directories to restore for found JobIds
96 \item Item 1 will list the last 20 jobs run. If you find the Job you want,
97 you can then select item 3 and enter its JobId(s).
99 \item Item 2 will list all the Jobs where a specified file is saved. If you
100 find the Job you want, you can then select item 3 and enter the JobId.
102 \item Item 3 allows you the enter a list of comma separated JobIds whose
103 files will be put into the directory tree. You may then select which
104 files from those JobIds to restore.
106 \item Item 4 allows you to enter any arbitrary SQL command. This is probably
107 the most primitive way of finding the desired JobIds, but at the same time,
108 the most flexible. Once you have found the JobId(s), you can select item 3
111 \item Item 5 will automatically select the most recent Full backup and all
112 subsequent incremental and differential backups for a specified Client.
113 These are the Jobs and Files which, if reloaded, will restore your
114 system to the most current saved state. It automatically enters the
115 JobIds found into the directory tree. This is probably the most
116 convenient of all the above options to use if you wish to restore a
117 selected Client to its most recent state.
119 There are two important things to note. First, this automatic selection
120 will never select a job that failed (terminated with an error status).
121 If you have such a job and want to recover one or more files from it,
122 you will need to explicitly enter the JobId in item 3, then choose the
125 If some of the Jobs that are needed to do the restore have had their
126 File records pruned, the restore will be incomplete. Bacula currently
127 does not correctly detect this condition. You can however, check for
128 this by looking carefully at the list of Jobs that Bacula selects and
129 prints. If you find Jobs with the JobFiles column set to zero, when
130 files should have been backed up, then you should expect problems.
132 If all the File records have been pruned, Bacula will realize that there
133 are no file records in any of the JobIds chosen and will inform you. It
134 will then propose doing a full restore (non-selective) of those JobIds.
135 This is possible because Bacula still knows where the beginning of the
136 Job data is on the Volumes, even if it does not know where particular
139 \item Item 6 allows you to specify a date and time, after which Bacula will
140 automatically select the most recent Full backup and all subsequent
141 incremental and differential backups that started before the specified date
144 \item Item 7 allows you to specify one or more filenames (complete path
145 required) to be restored. Each filename is entered one at a time or if you
146 prefix a filename with the less-than symbol (\lt{}) Bacula will read that
147 file and assume it is a list of filenames to be restored. The filename entry
148 mode is terminated by entering a blank line.
150 \item Item 8 allows you to specify a date and time before entering the
151 filenames. See Item 7 above for more details.
153 \item Item 9 allows you find the JobIds of the most recent backup for
154 a client. This is much like option 5 (it uses the same code), but
155 those JobIds are retained internally as if you had entered them
156 manually. You may then select item 11 (see below) to restore one
159 \item Item 10 is the same as item 9, except that it allows you to enter
160 a before date (as with item 6). These JobIds will then be retained
163 \index[general]{Restore Directories}
164 \item Item 11 allows you to enter a list of JobIds from which you can
165 select directories to be restored. The list of JobIds can have been
166 previously created by using either item 9 or 10 on the menu. You
167 may then enter a full path to a directory name or a filename preceded
168 by a less than sign (\lt{}). The filename should contain a list
169 of directories to be restored. All files in those directories will
170 be restored, but if the directory contains subdirectories, nothing
171 will be restored in the subdirectory unless you explicitly enter its
174 \item Item 12 allows you to cancel the restore command.
177 As an example, suppose that we select item 5 (restore to most recent state).
178 It will then ask for the desired Client, which on my system, will print all
179 the Clients found in the database as follows:
193 Select Client (File daemon) resource (1-9):
198 You will probably have far fewer Clients than this example, and if you have
199 only one Client, it will be automatically selected. In this case, I enter
200 {\bf Rufus} to select the Client. Then Bacula needs to know what FileSet is
201 to be restored, so it prompts with:
205 The defined FileSet resources are:
208 Select FileSet resource (1-2):
213 I choose item 1, which is my full backup. Normally, you will only have a
214 single FileSet for each Job, and if your machines are similar (all Linux) you
215 may only have one FileSet for all your Clients.
217 At this point, {\bf Bacula} has all the information it needs to find the most
218 recent set of backups. It will then query the database, which may take a bit
219 of time, and it will come up with something like the following. Note, some of
220 the columns are truncated here for presentation:
224 +-------+------+----------+-------------+-------------+------+-------+----------
226 | JobId | Levl | JobFiles | StartTime | VolumeName | File | SesId |
228 +-------+------+----------+-------------+-------------+------+-------+----------
230 | 1,792 | F | 128,374 | 08-03 01:58 | DLT-19Jul02 | 67 | 18 |
232 | 1,792 | F | 128,374 | 08-03 01:58 | DLT-04Aug02 | 0 | 18 |
234 | 1,797 | I | 254 | 08-04 13:53 | DLT-04Aug02 | 5 | 23 |
236 | 1,798 | I | 15 | 08-05 01:05 | DLT-04Aug02 | 6 | 24 |
238 +-------+------+----------+-------------+-------------+------+-------+----------
240 You have selected the following JobId: 1792,1792,1797
241 Building directory tree for JobId 1792 ...
242 Building directory tree for JobId 1797 ...
243 Building directory tree for JobId 1798 ...
249 Depending on the number of {\bf JobFiles} for each JobId, the {\bf Building
250 directory tree ..."} can take a bit of time. If you notice ath all the
251 JobFiles are zero, your Files have probably been pruned and you will not be
252 able to select any individual files -- it will be restore everything or
255 In our example, Bacula found four Jobs that comprise the most recent backup of
256 the specified Client and FileSet. Two of the Jobs have the same JobId because
257 that Job wrote on two different Volumes. The third Job was an incremental
258 backup to the previous Full backup, and it only saved 254 Files compared to
259 128,374 for the Full backup. The fourth Job was also an incremental backup
262 Next Bacula entered those Jobs into the directory tree, with no files marked
263 to be restored as a default, tells you how many files are in the tree, and
264 tells you that the current working directory ({\bf cwd}) is /. Finally, Bacula
265 prompts with the dollar sign (\$) to indicate that you may enter commands to
266 move around the directory tree and to select files.
268 If you want all the files to automatically be marked when the directory
269 tree is built, enter the command {\bf restore all}.
271 Instead of choosing item 5 on the first menu (Select the most recent backup
272 for a client), if we had chosen item 3 (Enter list of JobIds to select) and we
273 had entered the JobIds {\bf 1792,1797,1798} we would have arrived at the same
276 One point to note, if you are manually entering JobIds, is that you must enter
277 them in the order they were run (generally in increasing JobId order). If you
278 enter them out of order and the same file was saved in two or more of the
279 Jobs, you may end up with an old version of that file (i.e. not the most
282 Directly entering the JobIds can also permit you to recover data from
283 a Job that wrote files to tape but that terminated with an error status.
285 While in file selection mode, you can enter {\bf help} or a question mark (?)
286 to produce a summary of the available commands:
292 cd change current directory
293 count count marked files in and below the cd
294 dir long list current directory, wildcards allowed
295 done leave file selection mode
296 estimate estimate restore size
297 exit same as done command
298 find find files, wildcards allowed
300 ls list current directory, wildcards allowed
301 lsmark list the marked files in and below the cd
302 mark mark dir/file to be restored recursively in dirs
303 markdir mark directory name to be restored (no files)
304 pwd print current working directory
305 unmark unmark dir/file to be restored recursively in dir
306 unmarkdir unmark directory name only no recursion
307 quit quit and do not do restore
312 As a default no files have been selected for restore (unless you
313 added {\bf all} to the command line. If you want to restore
314 everything, at this point, you should enter {\bf mark *}, and then {\bf done}
315 and {\bf Bacula} will write the bootstrap records to a file and request your
316 approval to start a restore job.
318 If you do not enter the above mentioned {\bf mark *} command, you will start
319 with an empty slate. Now you can simply start looking at the tree and {\bf
320 mark} particular files or directories you want restored. It is easy to make
321 a mistake in specifying a file to mark or unmark, and Bacula's error handling
322 is not perfect, so please check your work by using the {\bf ls} or {\bf dir}
323 commands to see what files are actually selected. Any selected file has its
324 name preceded by an asterisk.
326 To check what is marked or not marked, enter the {\bf count} command, which
331 128401 total files. 128401 marked to be restored.
336 Each of the above commands will be described in more detail in the next
337 section. We continue with the above example, having accepted to restore all
338 files as Bacula set by default. On entering the {\bf done} command, Bacula
343 Bootstrap records written to /home/kern/bacula/working/restore.bsr
344 The restore job will require the following Volumes:
348 128401 files selected to restore.
350 JobName: kernsrestore
351 Bootstrap: /home/kern/bacula/working/restore.bsr
352 Where: /tmp/bacula-restores
358 OK to run? (yes/mod/no):
363 Please examine each of the items very carefully to make sure that they are
364 correct. In particular, look at {\bf Where}, which tells you where in the
365 directory structure the files will be restored, and {\bf Client}, which
366 tells you which client will receive the files. Note that by default the
367 Client which will receive the files is the Client that was backed up.
368 These items will not always be completed with the correct values depending
369 on which of the restore options you chose. You can change any of these
370 default items by entering {\bf mod} and responding to the prompts.
372 The above assumes that you have defined a {\bf Restore} Job resource in your
373 Director's configuration file. Normally, you will only need one Restore Job
374 resource definition because by its nature, restoring is a manual operation,
375 and using the Console interface, you will be able to modify the Restore Job to
378 An example Restore Job resource definition is given below.
380 Returning to the above example, you should verify that the Client name is
381 correct before running the Job. However, you may want to modify some of the
382 parameters of the restore job. For example, in addition to checking the Client
383 it is wise to check that the Storage device chosen by Bacula is indeed
384 correct. Although the {\bf FileSet} is shown, it will be ignored in restore.
385 The restore will choose the files to be restored either by reading the {\bf
386 Bootstrap} file, or if not specified, it will restore all files associated
387 with the specified backup {\bf JobId} (i.e. the JobId of the Job that
388 originally backed up the files).
390 Finally before running the job, please note that the default location for
391 restoring files is {\bf not} their original locations, but rather the directory
392 {\bf /tmp/bacula-restores}. You can change this default by modifying your {\bf
393 bacula-dir.conf} file, or you can modify it using the {\bf mod} option. If you
394 want to restore the files to their original location, you must have {\bf
395 Where} set to nothing or to the root, i.e. {\bf /}.
397 If you now enter {\bf yes}, Bacula will run the restore Job. The Storage
398 daemon will first request Volume {\bf DLT-19Jul02} and after the appropriate
399 files have been restored from that volume, it will request Volume {\bf
402 \subsection*{Selecting Files by Filename}
403 \index[general]{Selecting Files by Filename }
404 \index[general]{Filename!Selecting Files by }
405 \addcontentsline{toc}{subsection}{Selecting Files by Filename}
407 If you have a small number of files to restore, and you know the filenames,
408 you can either put the list of filenames in a file to be read by Bacula, or
409 you can enter the names one at a time. The filenames must include the full
410 path and filename. No wild cards are used.
412 To enter the files, after the {\bf restore}, you select item number 7 from the
417 To select the JobIds, you have the following choices:
418 1: List last 20 Jobs run
419 2: List Jobs where a given File is saved
420 3: Enter list of comma separated JobIds to select
421 4: Enter SQL list command
422 5: Select the most recent backup for a client
423 6: Select backup for a client before a specified time
424 7: Enter a list of files to restore
425 8: Enter a list of files to restore before a specified time
426 9: Find the JobIds of the most recent backup for a client
427 10: Find the JobIds for a backup for a client before a specified time
428 11: Enter a list of directories to restore for found JobIds
434 which then prompts you for the client name:
442 Select the Client (1-3): 3
446 Of course, your client list will be different, and if you have only one
447 client, it will be automatically selected. And finally, Bacula requests you to
456 At this point, you can enter the full path and filename
460 Enter filename: /home/kern/bacula/k/Makefile.in
465 as you can see, it took the filename. If Bacula cannot find a copy of the
466 file, it prints the following:
470 Enter filename: junk filename
471 No database record found for: junk filename
476 If you want Bacula to read the filenames from a file, you simply precede the
477 filename with a less-than symbol (\lt{}). When you have entered all the
478 filenames, you enter a blank line, and Bacula will write the bootstrap file,
479 tells you what tapes will be used, and proposes a Restore job to be run:
484 Automatically selected Storage: DDS-4
485 Bootstrap records written to /home/kern/bacula/working/restore.bsr
486 The restore job will require the following Volumes:
489 1 file selected to restore.
491 JobName: kernsrestore
492 Bootstrap: /home/kern/bacula/working/restore.bsr
493 Where: /tmp/bacula-restores
498 When: 2003-09-11 10:20:53
500 OK to run? (yes/mod/no):
504 It is possible to automate the selection by file by putting your list of files
505 in say {\bf /tmp/file-list}, then using the following command:
509 restore client=Rufus file=</tmp/file-list
513 If in modifying the parameters for the Run Restore job, you find that Bacula
514 asks you to enter a Job number, this is because you have not yet specified
515 either a Job number or a Bootstrap file. Simply entering zero will allow you
516 to continue and to select another option to be modified.
517 \label{CommandArguments}
519 \subsection*{Command Line Arguments}
520 \index[general]{Arguments!Command Line }
521 \index[general]{Command Line Arguments }
522 \addcontentsline{toc}{subsection}{Command Line Arguments}
524 If all the above sounds complicated, you will probably agree that it really
525 isn't after trying it a few times. It is possible to do everything that was
526 shown above, with the exception of selecting the FileSet, by using command
527 line arguments with a single command by entering:
531 restore client=Rufus select current all done yes
535 The {\bf client=Rufus} specification will automatically select Rufus as the
536 client, the {\bf current} tells Bacula that you want to restore the system to
537 the most current state possible, and the {\bf yes} suppresses the final {\bf
538 yes/mod/no} prompt and simply runs the restore.
540 The full list of possible command line arguments are:
543 \item {\bf all} -- select all Files to be restored.
544 \item {\bf select} -- use the tree selection method.
545 \item {\bf done} -- do not prompt the user in tree mode.
546 \item {\bf current} -- automatically select the most current set of backups
547 for the specified client.
548 \item {\bf client=xxxx} -- select the specified client.
549 \item {\bf jobid=nnn} -- specify a JobId or comma separated list of JobIds to
551 \item {\bf before=YYYY-MM-DD HH:MM:SS} -- specify a date and time to which
552 the system should be restored. Only Jobs started before the specified
553 date/time will be selected, and as is the case for {\bf current} Bacula will
554 automatically find the most recent prior Full save and all Differential and
555 Incremental saves run before the date you specify. Note, this command is not
556 too user friendly in that you must specify the date/time exactly as shown.
557 \item {\bf file=filename} -- specify a filename to be restored. You must
558 specify the full path and filename. Prefixing the entry with a less-than
560 (\lt{}) will cause Bacula to assume that the filename is on your system and
561 contains a list of files to be restored. Bacula will thus read the list from
562 that file. Multiple file=xxx specifications may be specified on the command
564 \item {\bf jobid=nnn} -- specify a JobId to be restored.
565 \item {\bf pool=pool-name} -- specify a Pool name to be used for selection of
566 Volumes when specifying options 5 and 6 (restore current system, and restore
567 current system before given date). This permits you to have several Pools,
568 possibly one offsite, and to select the Pool to be used for restoring.
569 \item {\bf yes} -- automatically run the restore without prompting for
570 modifications (most useful in batch scripts).
573 \subsection*{Restoring Directory Attributes}
574 \index[general]{Attributes!Restoring Directory }
575 \index[general]{Restoring Directory Attributes }
576 \addcontentsline{toc}{subsection}{Restoring Directory Attributes}
578 Depending how you do the restore, you may or may not get the directory entries
579 back to their original state. Here are a few of the problems you can
580 encounter, and for same machine restores, how to avoid them.
583 \item You backed up on one machine and are restoring to another that is
584 either a different OS or doesn't have the same users/groups defined. Bacula
585 does the best it can in these situations.
586 \item You are restoring into a directory that is already created and has file
587 creation restrictions. Bacula tries to reset everything but without walking
588 up the full chain of directories and modifying them all during the restore,
589 which Bacula does and will not do, getting permissions back correctly in
591 situation depends to a large extent on your OS.
592 \item You selected one or more files in a directory, but did not select the
593 directory entry to be restored. In that case, if the directory is not on
595 Bacula simply creates the directory with some default attributes which may
596 not be the same as the original. If you do not select a directory and all
598 contents to be restored, you can still select items within the directory to
599 be restored by individually marking those files, but in that case, you
601 individually use the "markdir" command to select all higher level
602 directory entries (one at a time) to be restored if you want the directory
603 entries properly restored.
608 \subsection*{Restoring on Windows}
609 \index[general]{Restoring on Windows }
610 \index[general]{Windows!Restoring on }
611 \addcontentsline{toc}{subsection}{Restoring on Windows}
613 If you are restoring on WinNT/2K/XP systems, Bacula will restore the files
614 with the original ownerships and permissions as would be expected. This is
615 also true if you are restoring those files to an alternate directory (using
616 the Where option in restore). However, if the alternate directory does not
617 already exist, the Bacula File daemon (Client) will try to create it. In
618 some cases, it may not create the directories, and if it does since the
619 File daemon runs under the SYSTEM account, the directory will be created
620 with SYSTEM ownership and permissions. In this case, you may have problems
621 accessing the newly restored files.
623 To avoid this problem, you should create any alternate directory before doing
625 restore. Bacula will not change the ownership and permissions of the directory
626 if it is already created as long as it is not one of the directories being
627 restored (i.e. written to tape).
629 The default restore location is {\bf /tmp/bacula-restores/} and if you are
630 restoring from drive {\bf E:}, the default will be
631 {\bf /tmp/bacula-restores/e/}, so you should ensure that this directory
632 exists before doing the restore, or use the {\bf mod} option to
633 select a different {\bf where} directory that does exist.
635 Some users have experienced problems restoring files that participate in
636 the Active Directory. They also report that changing the userid under which
637 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
641 \subsection*{Restoring Files Can Be Slow}
642 \index[general]{Slow!Restoring Files Can Be }
643 \index[general]{Restoring Files Can Be Slow }
644 \addcontentsline{toc}{subsection}{Restoring Files Can Be Slow}
646 Restoring files is generally {\bf much} slower than backing them up for several
647 reasons. The first is that during a backup the tape is normally already
648 positioned and Bacula only needs to write. On the other hand, because restoring
649 files is done so rarely, Bacula keeps only the start file and block on the
650 tape for the whole job rather than on a file by file basis which would use
651 quite a lot of space in the catalog.
653 Bacula will forward space to the correct file mark on the tape for the Job,
654 then forward space to the correct block, and finally sequentially read each
655 record until it gets to the correct one(s) for the file or files you want to
656 restore. Once the desired files are restored, Bacula will stop reading the
659 Finally, instead of just reading a file for backup, during the restore, Bacula
660 must create the file, and the operating system must allocate disk space for
661 the file as Bacula is restoring it.
663 For all the above reasons the restore process is generally much slower than
664 backing up (sometimes it takes three times as long).
666 \subsection*{Problems Restoring Files}
667 \index[general]{Files!Problems Restoring }
668 \index[general]{Problems Restoring Files }
669 \addcontentsline{toc}{subsection}{Problems Restoring Files}
671 The most frequent problems users have restoring files are error messages such
676 04-Jan 00:33 z217-sd: RestoreFiles.2005-01-04_00.31.04 Error:
677 block.c:868 Volume data error at 20:0! Short block of 512 bytes on
678 device /dev/tape discarded.
686 04-Jan 00:33 z217-sd: RestoreFiles.2005-01-04_00.31.04 Error:
687 block.c:264 Volume data error at 20:0! Wanted ID: "BB02", got ".".
692 Both these kinds of messages indicate that you were probably running your tape
693 drive in fixed block mode rather than variable block mode. Fixed block mode
694 will work with any program that reads tapes sequentially such as tar, but
695 Bacula repositions the tape on a block basis when restoring files because this
696 will speed up the restore by orders of magnitude when only a few files are being
697 restored. There are several ways that you can attempt to recover from this
698 unfortunate situation.
700 Try the following things, each separately, and reset your Device resource to
701 what it is now after each individual test:
704 \item Set "Block Positioning = no" in your Device resource and try the
705 restore. This is a new directive and untested.
706 \item Set "Minimum Block Size = 512" and "Maximum Block Size = 512" and
707 try the restore. Again send me the full job report output. If you are able
709 determine the block size your drive was previously using, you should try
710 that size if 512 does not work.
711 \item Try editing the restore.bsr file at the Run xxx yes/mod/no prompt
712 before starting the restore job and remove all the VolBlock statements.
714 are what causes Bacula to reposition the tape, and where problems occur if
715 you have a fixed block size set for your drive. The VolFile commands also
716 cause repositioning, but this will work regardless of the block size.
717 \item Use bextract to extract the files you want -- it reads the Volume
718 sequentially if you use the include list feature, or if you use a .bsr file,
719 but remove all the VolBlock statements after the .bsr file is created (at
721 Run yes/mod/no) prompt but before you start the restore.
724 \subsection*{Example Restore Job Resource}
725 \index[general]{Example Restore Job Resource }
726 \index[general]{Resource!Example Restore Job }
727 \addcontentsline{toc}{subsection}{Example Restore Job Resource}
732 Name = "RestoreFiles"
735 FileSet = "Any-FileSet"
736 Storage = Any-storage
737 Where = /tmp/bacula-restores
744 If {\bf Where} is not specified, the default location for restoring files will
745 be their original locations.
748 \subsection*{File Selection Commands}
749 \index[general]{Commands!File Selection }
750 \index[general]{File Selection Commands }
751 \addcontentsline{toc}{subsection}{File Selection Commands}
753 After you have selected the Jobs to be restored and Bacula has created the
754 in-memory directory tree, you will enter file selection mode as indicated by
755 the dollar sign ({\bf \$}) prompt. While in this mode, you may use the
756 commands listed above. The basic idea is to move up and down the in memory
757 directory structure with the {\bf cd} command much as you normally do on the
758 system. Once you are in a directory, you may select the files that you want
759 restored. As a default no files are marked to be restored. If you wish to
760 start with all files, simply enter: {\bf cd /} and {\bf mark *}. Otherwise
761 proceed to select the files you wish to restore by marking them with the {\bf
762 mark} command. The available commands are:
767 The {\bf cd} command changes the current directory to the argument
769 It operates much like the Unix {\bf cd} command. Wildcard specifications are
772 Note, on Windows systems, the various drives (c:, d:, ...) are treated like
774 directory within the file tree while in the file selection mode. As a
775 consequence, you must do a {\bf cd c:} or possibly in some cases a {\bf cd
776 C:} (note upper case) to get down to the first directory.
780 The {\bf dir} command is similar to the {\bf ls} command, except that it
781 prints it in long format (all details). This command can be a bit slower
783 the {\bf ls} command because it must access the catalog database for the
784 detailed information for each file.
787 \index[dir]{estimate }
788 The {\bf estimate} command prints a summary of the total files in the tree,
789 how many are marked to be restored, and an estimate of the number of bytes
791 be restored. This can be useful if you are short on disk space on the
793 where the files will be restored.
797 The {\bf find} command accepts one or more arguments and displays all files
798 in the tree that match that argument. The argument may have wildcards. It is
799 somewhat similar to the Unix command {\bf find / -name arg}.
802 The {\bf ls} command produces a listing of all the files contained in the
803 current directory much like the Unix {\bf ls} command. You may specify an
804 argument containing wildcards, in which case only those files will be
806 Any file that is marked to be restored will have its name preceded by an
807 asterisk ({\bf *}). Directory names will be terminated with a forward slash
808 ({\bf /}) to distinguish them from filenames.
812 The {\bf lsmark} command is the same as the {\bf ls} except that it will
813 print only those files marked for extraction. The other distinction is that
814 it will recursively descend into any directory selected.
818 The {\bf mark} command allows you to mark files to be restored. It takes a
819 single argument which is the filename or directory name in the current
820 directory to be marked for extraction. The argument may be a wildcard
821 specification, in which case all files that match in the current directory
822 are marked to be restored. If the argument matches a directory rather than a
823 file, then the directory and all the files contained in that directory
824 (recursively) are marked to be restored. Any marked file will have its name
825 preceded with an asterisk ({\bf *}) in the output produced by the {\bf ls}
827 {\bf dir} commands. Note, supplying a full path on the mark command does not
828 work as expected to select a file or directory in the current directory.
829 Also, the {\bf mark} command works on the current and lower directories but
830 does not touch higher level directories.
832 After executing the {\bf mark} command, it will print a brief summary:
841 If no files were marked, or:
850 if some files are marked.
854 The {\bf unmark} is identical to the {\bf mark} command, except that it
855 unmarks the specified file or files so that they will not be restored. Note:
856 the {\bf unmark} command works from the current directory, so it does not
857 unmark any files at a higher level. First do a {\bf cd /} before the {\bf
858 unmark *} command if you want to unmark everything.
862 The {\bf pwd} command prints the current working directory. It accepts no
867 The {\bf count} command prints the total files in the directory tree and the
868 number of files marked to be restored.
872 This command terminates file selection mode.
876 This command terminates file selection mode (the same as done).
880 This command terminates the file selection and does not run the restore
886 This command prints a summary of the commands available.
889 This command is the same as the {\bf help} command.
892 \subsection*{Restoring When Things Go Wrong}
893 \index[general]{Restoring When Things Go Wrong }
894 \addcontentsline{toc}{subsection}{Restoring When Things Go Wrong}
896 This and the following sections will try to present a few of the kinds of
897 problems that can come up making restoring more difficult. I'll try to
898 provide a few ideas how to get out of these problem situations.
902 Your catalog has been damaged and Bacula either doesn't work or prints
905 For SQLite, use the vacuum command to try to fix the database. For either
906 MySQL or PostgreSQL, see the vendor's documentation. They have specific tools
907 that check and repair databases.
909 Assuming the above does not resolve the problem, you will need to restore
910 or rebuild your catalog.
912 How do I restore my catalog?
914 If you have backed up your database nightly (as you should) and you
915 have made a bootstrap file, you can immediately load back your
916 database (or the ASCII SQL output). Make a copy of your current
917 database, then re-initialize it, by running the following scripts:
922 After re-initializing the database, you should be able to run
923 Bacula. If you now try to use the restore command, it will not
924 work because the database will be empty. However, you can manually
925 run a restore job and specify your bootstrap file. You do so
926 by entering the {bf run} command in the console and selecting the
927 restore job. If you are using the default bacula-dir.conf, this
928 Job will be named {\bf RestoreFiles}. Most likely it will prompt
929 you with something such as:
933 JobName: RestoreFiles
934 Bootstrap: /home/kern/bacula/working/restore.bsr
935 Where: /tmp/bacula-restores
940 When: 2005-07-10 17:33:40
943 OK to run? (yes/mod/no):
946 A number of the items will be different in your case. What you want
947 to do is: to use the mod option to change the Bootstrap to point to
948 your saved bootstrap file; and to make sure all the other items
949 such as Client, Storage, Catalog, and Where are correct. The
950 FileSet is not used when you specify a bootstrap file.
951 Once you have set all the correct values, run the Job and
952 it will restore the backup of your database. You will then
953 need to follow the instructions for your database type to
954 recreate the database from the ASCII backup file.
958 If you did save your database but did not make a bootstrap file, then
959 recovering the database
960 is more difficult. You will probably need to use bextract to extract the
962 First you should locate the listing of the job report from the last catalog
963 backup. It has important information that will allow you to quickly find
964 your database file. For example, in the job report for the CatalogBackup
965 shown below, the critical items are the Volume name(s), the Volume Session Id
966 and the Volume Session Time. If you know those, you can easily restore your
971 22-Apr 10:22 HeadMan: Start Backup JobId 7510,
972 Job=CatalogBackup.2005-04-22_01.10.0
973 22-Apr 10:23 HeadMan: Bacula 1.37.14 (21Apr05): 22-Apr-2005 10:23:06
975 Job: CatalogBackup.2005-04-22_01.10.00
978 FileSet: "CatalogFile" 2003-04-10 01:24:01
981 Start time: 22-Apr-2005 10:21:00
982 End time: 22-Apr-2005 10:23:06
985 FD Bytes Written: 210,739,395
986 SD Bytes Written: 210,739,521
988 Software Compression: None
989 Volume name(s): DLT-22Apr05
990 Volume Session Id: 11
991 Volume Session Time: 1114075126
992 Last Volume Bytes: 1,428,240,465
993 Non-fatal FD errors: 0
995 FD termination status: OK
996 SD termination status: OK
997 Termination: Backup OK
1001 From the above information, you can manually create a bootstrap file,
1002 and then follow the instructions given above for restoring your database.
1003 A reconstructed bootstrap file for the above backup Job would look
1007 Volume="DLT-22Apr05"
1009 VolSessionTime=1114075126
1013 Where we have inserted the Volume name, Volume Session Id, and Volume Session
1015 correspond to the values in the job report. We've also used a FileIndex of
1017 which will always be the case providing that there was only one file
1018 backed up in the job.
1020 The disadvantage of this bootstrap file compared to what is created when you
1021 ask for one to be written, is that there is no File and Block specified, so
1022 the restore code must search all data in the Volume to find the requested
1023 file. A fully specified bootstrap file would have the File and Blocks
1028 Volume="DLT-22Apr05"
1030 VolSessionTime=1114075126
1037 You don't have a bootstrap file, and you don't have the Job report for
1038 the backup of your database, but you did backup the database, and you
1039 know the Volume to which it was backed up.
1042 Use {\bf bls} to indicate where it is on the tape. For example:
1046 ./bls -j -V DLT-22Apr05 /dev/nst0
1049 Might produce the following output:
1052 bls: butil.c:258 Using device: "/dev/nst0" for reading.
1053 21-Jul 18:34 bls: Ready to read from volume "DLT-22Apr05" on device "DLTDrive"
1055 Volume Record: File:blk=0:0 SessId=11 SessTime=1114075126 JobId=0 DataLen=164
1057 Begin Job Session Record: File:blk=118:0 SessId=11 SessTime=1114075126
1059 Job=CatalogBackup.2005-04-22_01.10.0 Date=22-Apr-2005 10:21:00 Level=F Type=B
1060 End Job Session Record: File:blk=118:4053 SessId=11 SessTime=1114075126
1062 Date=22-Apr-2005 10:23:06 Level=F Type=B Files=1 Bytes=210,739,395 Errors=0
1065 21-Jul 18:34 bls: End of Volume at file 201 on device "DLTDrive" (/dev/nst0),
1066 Volume "DLT-22Apr05"
1067 21-Jul 18:34 bls: End of all volumes.
1070 Of course, there will be many more records printed, but we have indicated
1071 the essential lines of output. From the information on the Begin Job and End
1072 Job Session Records, you can reconstruct a bootstrap file such as the one
1076 How can I find where a file is stored.
1078 Normally, it is not necessary, you just use the {\bf restore} command to
1080 most recently saved version (menu option 5), or a version saved before a given
1082 option 8). If you know the JobId of the job in which it was saved, you can
1084 option 3 to enter that JobId.
1086 If you would like to know the JobId where a file was saved, select restore
1090 You can also use the {\bf query} command to find information such as:
1096 2: List up to 20 places where a File is saved regardless of the directory:
1097 3: List where the most recent copies of a file are saved:
1098 4: List last 20 Full Backups for a Client:
1099 5: List all backups for a Client after a specified time
1100 6: List all backups for a Client
1101 7: List Volume Attributes for a selected Volume:
1102 8: List Volumes used by selected JobId:
1103 9: List Volumes to Restore All Files:
1104 10: List Pool Attributes for a selected Pool:
1105 11: List total files/bytes by Job:
1106 12: List total files/bytes by Volume:
1107 13: List Files for a selected JobId:
1108 14: List Jobs stored in a selected MediaId:
1109 15: List Jobs stored for a given Volume name:
1110 Choose a query (1-15):