Eh? No, the cluster node has it's own backup IP Address as well. The software is annoying. So there are a few backup configurations. There is the base system OS backup for each node, then there is a seperate cluster node backup. It doesn't matter where the cluster is located.
On Mon, Oct 24, 2011 at 12:33 PM, Ben N <[email protected]> wrote: > so if you have a failover cluster, and it moves from one node to another, > do you have to do anything to make backups work again? I'm guessing your > client IP for the backup network changes with nodes, but that is acceptable > since it always hits the same backup server no matter which node it's on. > I'm not sure this will work for my Commvault though.. hmmm... > > -BenN > > On Mon, Oct 24, 2011 at 11:32 AM, Steven Peck <[email protected]> wrote: > >> Err. so. I will tell you how we do it. >> We use Tivolli Storage Manager. TSM uses a local configuration file with >> the IP Address of the backup server in it so we don't need to worry about a >> HOST file. >> Every system has a backup network and our main backup network is a /23, We >> name our backup NICs to Backup. Backup NICs do not get a gateway, they also >> don't get DNS or WINs and we make sure the 'register with DNS' box is >> unchecked. >> We also change the order to make sure the NIC is last in Advanced > >> Advanced Settings > Connection >> >> Occasional weird connectivity issues are often traced to someone forget to >> set some of the above right. Usually 'register with DNS' so other systems >> can't route to it properly. >> >> I suspect a HOST file would do something similar for you. As we don't >> manage TSM and it is hosted primarily on the UNIX servers here that's all I >> got. Hope something is useful >> >> Steven Peck >> http://www.blkmtn.org >> >> >> On Mon, Oct 24, 2011 at 11:10 AM, Ben N <[email protected]> wrote: >> >>> any ideas out there? >>> >>> -BenN >>> >>> On Thu, Oct 20, 2011 at 10:06 AM, Ben N <[email protected]> wrote: >>> >>>> I have some situations where i really need to start using a backup >>>> network so i'm not affecting network customers are using. Ideally i'd like >>>> to assign an IP address on a new network to a SQL Failover Instance to be >>>> used for this private backup network and would follow it no matter which >>>> node it ended up being on. I would then just use the local HOSTS file on my >>>> backup server and on each node to resolve to the new IP on this new backup >>>> server. Have you guys done this before? I haven't been successful with it >>>> yet. >>>> >>>> -BenN >>>> >>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >>>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >>>> >>>> --- >>>> To manage subscriptions click here: >>>> http://lyris.sunbelt-software.com/read/my_forums/ >>>> or send an email to [email protected] >>>> with the body: unsubscribe ntsysadmin >>>> >>> >>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >>> >>> --- >>> To manage subscriptions click here: >>> http://lyris.sunbelt-software.com/read/my_forums/ >>> or send an email to [email protected] >>> with the body: unsubscribe ntsysadmin >>> >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> >> --- >> To manage subscriptions click here: >> http://lyris.sunbelt-software.com/read/my_forums/ >> or send an email to [email protected] >> with the body: unsubscribe ntsysadmin >> > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
