I've been running bacula on solaris since December of '06. It started out as a single-box backup solution, with the dir, sd and fd running on a single box. Since then we've scaled it up to include a second sd and fd on another Sun box, the an fd-only on a ubuntu machine, and the fd on a WinXP machine.
Now, because of the expanding use of bacula, we're going to virtualize the director. What kinds of issues might I encounter? I have already thought of: With the new name, all configs will have to be tweaked to allow communications from the new director. The old director will have to be decommissioned. Not explicitly necessary, I know SD and FD can be controlled by multiple directors, but it's the intent in my case. I'm wondering about the following: I've been using mySQL. I know how to get a dump of the database out, and how to read that database back in. I intend to use that to "migrate" the database to the mySQL server on the new director. I don't think that will cause any problems. I'm open to being corrected. With the director moving off of the original sun machine, I'm going to rename the sd and fd on that machine. If I have to do restores, I know that I'll have to change the restore-from devices and such. Currently their named bacula-sd and bacula-fd. I intend to change them to [hostname]-fd/sd. Are there any snafus I might encounter there? Anything else? -- -- Flak Magnet (Tim) www.flakmagnet.com ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
