On Wed, Oct 5, 2011 at 8:39 PM, Ben Walton <bwalton AT artsci.utoronto DOT ca> 
wrote:
>
> Hi All,
>
> I'm going to be adding a new pair of boxes to the network shortly.
> One box will be a primary server and the other a hot standby.  The hot
> standby will sync the live system nightly.
>
> As I see it, I've got a few options for backup here:
>
> 1. Backup both boxes, pay the heavy price of duplicated data (or use a
>   base job, etc)
> 2. Backup only the failover system and the config for the live system,
>   making the failover the primary recovery source.
> 3. Backup only the primary system and config on the failover.
> 4. Attempt to backup only a single system, determined by which one is
>   holder the virtual IP that will run the service.
>
> I'm inclined toward either 2 or 3 but am curious what the experts
> think.
>
> Thanks
> -Ben
> --
> Ben Walton
> Systems Programmer - CHASS
> University of Toronto
> C:416.407.5610 | W:416.978.4302
>
>

With most active/passive paired servers that I have implemented,
backup is run on the "passive" server and is the primary recovery
source.

Historically this was because of the backup load on the active server,
and in some cases backup windows.

You mention having a shared IP, for "clustered" systems, I would
probably look to have a more frequent sync than daily unless you can
"replace" the daily "changes" via a different method.

Cheers

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users