Jump to content
Sign in to follow this  
jriggin

Cluster Backup

Recommended Posts

What are the best practices when backing up a cluster?

 

Currently I have 2 servers in Retrospect, each using the direct IP for the box (not the clustered IP). I have 3 backup sets. Server A will backup drives C & D to Backup Set 1, Server B will backup drives C & D to Backup Set 2, and the cluster currently lives on Server A. I have the clustered drives being backed up to Backup Set C. The issue is that if the cluster fails over, we get missing backups until either a) I update the script to backup the clustered drives on Server B or B) We fail the cluster back over to Client A.

 

If I try to add a third client using the cluster IP, it simply changes Client A to the clustered IP instead of adding a third client. What is the best way to configure this?

Share this post


Link to post
Share on other sites

We're not actually using a SQL license to back up data. The database admins have it configured on a schedule to dump backups to the drives, and then we back up the drive with the SQL selector.

 

In this scenario how should we have Retrospect configured?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×