jriggin Posted April 27, 2010 Report Share Posted April 27, 2010 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 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? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 27, 2010 Report Share Posted April 27, 2010 http://kb.dantz.com/article.asp?article=5494&p=2 Quote Link to comment Share on other sites More sharing options...
jriggin Posted April 27, 2010 Author Report Share Posted April 27, 2010 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? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.