The counter-argument to this is, of course, that the enterprise db server is often the best equipped and configured in terms of high-availability, clustering, and replication, making it the system least likely to go down in the first place ;-)
Naturally, you don't want that DB server to be a dependency for the backup server that backs it up but that is just common sense. There is no single answer to this question. --PLB At 17:14 21.8.2007, Alan Brown wrote: >On Tue, 21 Aug 2007, Bob Hetzel wrote: > > > IMHO, it's somewhat of a design flaw to set up your backup system > > depending upon the enterprise db box. If the enterprise db server goes > > down you need to get that up and running, then restore the bacula > > catalog, then you can begin restoring everything else. > >Yes, we looked at putting the bacula database on the main DB server and >decided against it for exactly this reason. > > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >Bacula-users mailing list >Bacula-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
