8

We're in the process having our SQL Server instances backup to a network share, but our network admins want to try and divert the bandwidth from the backups through a different network segment. I was curious if it were possible to configure SQL Server to run all backups through a secondary NIC?

Most of our servers are virtualized (so presenting the NIC isn't a problem) and we're running on SQL Server 2008 R2, 2012, & 2014 throughout our infrastructure.

Improve this question
3
  • 4
    You could use a unique name for the target computer that is only visible over the alternate NIC. If the primary Nic is 192.168.0/24 and the alternate is 192.168.1/24 then the share could have an alternate ip of 192.168.1.x - then you'd backup to \\192.168.1.x\sharename
    – Hannah Vernon ♦
    Commented Mar 10, 2015 at 21:42
  • 2
    @MaxVernon I'll work with my sysadmin to get that configured and get back with the results. That seems like it should work. :)
    – JohnS
    Commented Mar 10, 2015 at 22:58
  • 4
    Joe Chang talks about Dedicated Network Adapter(s) for transferring SQL backups to the tape archival system. You should also follow the same though. @MaxVernon is right on spot.
    – Kin Shah
    Commented Mar 10, 2015 at 23:05

1 Answer 1

Reset to default
3

Yes, see the Microsoft whitepaper A Technical Case Study: Fast and Reliable Backup and Restore of Multi-Terabyte Database Over the Network (DOC). On page 15, they explain how to separate out the backup targets onto multiple subnets and volumes.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.