On Monday 12 March 2007 17:20, Jeff Dickens wrote: > I need to move my bacula server to a new machine, and while I'm at it I > want to upgrade to 2.0.3. What would be the best approach - move and > then upgrade, or upgrade and then move, or install the new server with > 2.0.3 and then move/upgrade the database? >
There are many approaches, mostly, it depends on your own preferences. I've done this several times, and what I found that suited me the best was to move the conf files over to the new server, then install the new version (2.0.3) of Bacula, move and upgrade the database, then modify the conf files appropriately (typically a change of Director name, and possibly SD). Then after shutting down the old Bacula, but keeping everything in place, I could test the new server with *different* Volumes until I was happy. If it doesn't work, you simply shutdown the new Bacula restart the old Bacula and the next day, move and upgrade the database again and work on it until you are satisfied. Once it works, you either keep the new Volume you used for testing, or simply move and upgrade the old database again. Regards, Kern ------------------------------------------------------------------------- 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
