I created a bsr file with the names of all my volumes in order,
separated by |'s. There seem to be too many:
# bscan -s -m -b vols.bsr -v /var/spool/bacula -c /etc/bacula/bacula-sd.conf -P
xxx -h localhost
23-Apr 17:51 bscan: Fatal Error at parse_bsr.c:171 because:
Bootstrap file error: Keyword
0606|Inc2007-04-04_0607|Inc2007-04-06_0608|Diff2007-04-08_0609|Inc2007-04-09_0610|Inc2007-04-11_0611|Inc2007-04-13_0612|Diff2007-04-15_0613|Inc2007-04-16_0614|Inc2007-04-19_0615|Inc2007-04-21_0616|Diff2007-04-22_0617|Diff2007-04-22_0618
not found
: Line 2, col 236 of file vols.bsr
0606|Inc2007-04-04_0607|Inc2007-04-06_0608|Diff2007-04-08_0609|Inc2007-04-09_0610|Inc2007-04-11_0611|Inc2007-04-13_0612|Diff2007-04-15_0613|Inc2007-04-16_0614|Inc2007-04-19_0615|Inc2007-04-21_0616|Diff2007-04-22_0617|Diff2007-04-22_0618
bscan: butil.c:279 Could not find device "/var/spool" in config file
/etc/bacula/bacula-sd.conf.
23-Apr 17:51 bscan: bscan Fatal error: butil.c:168 Cannot find device
"/var/spool" in config file /etc/bacula/bacula-sd.conf.
# wc vols.bsr
1 1 736 vols.bsr
I set a shell variable to the list, and that seems to be working. I
don't trust wildcards to give me the right order.
The "could not find device" error is puzzling, since it all seemed to
work with a shorter bsr (without the -s -m options), or the longer
form with the shell variable.
The manual indicates that multiple passes are not a good idea, so it
would be nice if it were easier to do a single pass.
A few more comments below, based on further study of the manual.
On Mon, Apr 23, 2007 at 02:08:19PM -0700, Ross Boylan wrote:
> My main box, which had the bacula server and was also the subject of
> backups, just died. I thought I was well-prepared, but seem to have
> missed a few things. Specifically, I do not have a copy of the
> configuration files and I do not have a separate backup of the catalog
> or a bootstrap record for the same.
I do not need all the original job specifications; I just need a
restore job, and one is provided in the default install.
Also there is a wxWidgets based tool that may be useful for restore,
once the catalog is back.
>
> This seems to differ from the expected scenarios in the documentation,
> though I need to study it further. But I would appreciate any advice
> about how to proceed. It is not a "bare metal" scenario since the new
> box (I was going to move to it eventually) has a running system with
> all the bacula components. It is relatively empty otherwise.
The end of chapter 19 (on the console) discusses "Restoring when
things go wrong", which does pretty much cover this case toward the
end. "Solution without a job listing" is the case I'm in.
The first point is that one needs to restore the catalog before doing
any other restores (bextract doesn't need it, but it's use is discouraged).
I could either have restored the catalog database from the volumes
(perhaps using bextract) and then proceeded. Since inspection
did not immediately reveal the file, and since it's in an old format
(old for postgres and bacula) anyway, I skipped that. Also, I'm not
sure the backed up version would have all my files.
The instructions seem to recommend constructing a bsr by hand after
running bls, but this looked tedious and functionally equivalent to
running bscan, so I did that. The instructions for bscan begin with
"If you find yourself using this program, you have probably done
something wrong." Clearly, by not have a boostrap record for the
catalog I did something wrong. I'm not sure if the comment means it's
"wronger" to use bscan than one of the other methods.
I'm still not exactly sure where the job-based bsr's that I do have
play in this.
>
> I "have" the missing configuration files and catalog within the backup
> (though the catalog backup would not have the last round of stuff),
> but that doesn't help much in the first round.
>
> I've been backing upto disk (that is, each volume is a file on the
> disk) and I have those files and the bsr records for the individual
> jobs.
>
> The main problem is that I apparently need to define the jobs in
> bacula-dir.conf before I can proceed. I guess I can create
> approximations of what I had before (most of the details were in what
> files to exclude, and I don't need that for restore).
As noted earlier, this is a misunderstanding. One only needs a single
restore job specification.
>
> I think the next step is to use bscan to rebuild the catalog from the
> backup media.
>
> Then I run the restore jobs, pointing to the bsr files.
>
> I think at the end of this I have all my files back, and maybe some
> that I deleted as well (if I had a proper backup of the catalog would
> it take care of that problem?).
>
> There are two other possible issues. First, the name of the system
> has changed. Second, the old system ran bacula 1.3x (at 1.37), while
> the new is at 2.0. (Also postgres 7.4 v 8.1) I could downgrade if
> necessary.
So far the volumes created by 1.3x seem to be working with 2.0.
>
> So... will this work? Any suggestions?
>
> Thanks.
> Ross Boylan
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
