From: Kern S. <ke...@si...> - 2006-02-22 18:52:05
|
On Wednesday 22 February 2006 19:07, Karl Hakimian wrote: > On Wed, Feb 22, 2006 at 05:17:20PM +0100, Kern Sibbald wrote: > > This possibly has to do with including the directory entries too -- I'd > > need to have an idea of what files/dirs are involved and look at the > > code. > > > > Now that I have a DSL connection, I can try to load the Perl modules that > > I don't have on my portable so that I can actually run recover.pl ... > > I will try to drill down to the actual files tonight. > > > Yes, sorry, you previously asked this. The answer is: between Volume= > > definitions, the order of the records is not important. However, the > > order of the Volume records is very important. They should be listed in > > the order the Volumes were written. For a given JobId, the Volumes were > > written in the order of VolIndex in the JobMedia table, with lower > > VolIndex values being the first volumes written. For different JobIds, I > > forget exactly how the Volume order is determined. I think it is by > > assuring that the JobIds are properly sorted by JobTDate. I'll try to > > look at the code later tonight. > > I wondered what that number was for. :-) OK will fix the order in my > .bsr file. I've now uploaded all the Perl modules I need to run recover.pl. Could you send me an example of the recover.pl conf file for MySQL? In particular, I am not sure what the dbconnect string should be. Also, if there is anything "tricky" I should know about running recover.pl, please let me know -- no need for long explanations, I can figure out most things with no problem. Thanks. Oh, if you send me a copy of your latest recover.pl that writes a bootstrap file, I'll try running it here too. |