I am interested in trying 2.0. I am currently running 1.38.11 successfully on two different backup servers, but honestly it has been quite a chore trying to keep the one with the Autochanger running.
I understand that it is necessary to convert the database format (mysql) when moving from 1.38 to 2.0, and that a script is provided to do that. Further, I understand that if the upgrade is done via rpm that the db upgrade will happen automagically with a post-install script. I am nervous though. If 2.0 doesn't work out, will I have a way to get back to what does work (1.38.11)? If I just make copies of all the stuff in /etc/bacula and /var/lib/mysql/bacula and /var/bacula will that be enough to let me get back to where I am now? Has anyone else here done this 1.38.11 to 2.0 upgrade successfully on either CentOS4 or RHEL4? Thanks Michael -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
