On 10/27/11 15:44, Kern Sibbald wrote:
>> Looks like the DB upgrade scripts for 5.2.0 can upgrade the DB from
>> v5.0, but not from v5.1.  I have a v13 database.  I'm patching the DB
>> manually right now, but this may leave people who've been experimenting
>> with 5.1 stranded.
>>
>> Anything I need to watch out for here...?

> I recommend diffing the make_xxx_tables.in script you have for the 5.1 
> that you used
> to the current 5.2.0 script.  That should tell you pretty clearly what 
> you need to do.

I just compared what the script was doing to the existing schema and
made the necessary changes by hand.  Wasn't a problem, and nothing
non-obvious showed up.

5.2.0 compiled on the first try on Solaris 10u9 x86_64 once I got
32/64-bit build issues resolved (I hate the hybrid 64+32-bit default
Solaris build, and wish I could install it 64-bit only).  Fired up
without any problems and appears to be working fine so far.  I do notice
that 5.0.3 BAT seems to have some slight problems talking to a 5.2.0
Director; specifically, the restore browser in the 5.0.3 BAT doesn't
work properly against a 5.2.0 director.  There's probably nothing I can
do about that until I can find, or make, a Bacula-5.2.0 Gentoo ebuild.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  ala...@caerllewys.net   ala...@metrocast.net   p...@co.ordinate.org
  Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to