On Mon, January 8, 2007 2:05 pm, Felix Schwarz wrote: > > Michael Nelson schrieb: >> 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? > > Instead of storing your sql database files directly, I suggest using > mysqldump.
Aaarrghhh. Of course. Maybe that's why I run automysqlbackup out of cron.daily every night. DOH! <grin> >> Has anyone else here done this 1.38.11 to 2.0 upgrade successfully on >> either CentOS4 or RHEL4? > > I have - allthough only on my very small installation at home. Currently > all other bacula > installations at various places are running just fine, so no reason to > upgrade. OK, I backed everything up and upgraded. The updatedb script died because it tried to log into mysql as root without a password, but I got that fixed and the dbs updated. So I will let it run tonight and see what happens. Thanks for the help. 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
