server IP change, does it affect anything?

  • Hi everyone!

    We need to change the IP of a sql 2005 box. It is the publisher in transactional replication. And it is the secondary database in log shipping. Will replication and log shipping be affected because of the change?

    Thanks!

    Kathleen

  • It depends on how you set things up. Some people have used IPs instead of the server name. IF it's by servername, it should be ok, SQL should start listening on the new IP, but I have seen it cause issues and a restart of SQL needed for the listened to pick up on the new IP.

  • Hi, Steve, thanks for the reply. Here is what I am thinking:

    For transactional replication, in our settings, the publisher (which will have a new IP) is also the distributor. The subscriber is referenced by IP. Here is the script to add subscription:

    exec sp_addsubscription @publication = N'db1', @subscriber = N'10.20.3.456', @destination_db = N'db1', @subscription_type = N'Push', @sync_type = N'automatic', @article = N'all', @update_mode = N'read only', @subscriber_type = 0

    Correct me if I am wrong, in our scenario, as long as the subscriber's IP does not change, replication wont break.

    For log shiping, I configured it using management studio, I am thinking, after the change, since the server is the secondary server, I can go in and change the IP, so new transaction logs will keep getting sent to the same server, as long as there is no missing transaction log backups, log shipping should still work fine.

    Thanks for your help.

    Kathleen

  • That makes sense and just be sure that the subscriber isn't looking for a certain IP on the distributor if it pulls data.

    Let us know if you have issues. We'd like to hear as well as help.

  • You should create an ALIAS for the subscriber to eliminate the need for the hardcoded IP. That way if the subscriber changes IP you just need to update the alias.


    * Noel

  • We made the change this morning, both log shipping and replication worked fine, as expected.

  • We made the change this morning, both log shipping and replication worked fine, as expected.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply