November 8, 2012 at 3:41 am
[font="Verdant"]Dear Friends,
I need valuable suggestion to do the Servers Migration and SAN relocation in the below scenario:
SQL Server Setup in Windows Clustering: We are currently running with 3 physical Servers and hosted with 2 Node Cluster. I mean Server 1 is active for one Instance (Default Instance), Server 3 is active for another instance (Named instance) and Server 2 is passive for both the instances. All the system and user data files are hosted in SAN Drives. And also we have transactional replication configured for User databases from Server 1 & Server 3 to one more Standalone Server called XXXX. Due to performance issues with Servers and Storage we are planning to replace the old Servers with new Servers as well SAN Box.
As part of this Process we have 2 Physical Servers in place for replacement of Server 1, Server 3 & 1 Server will be taken from existing i.e. Server 3.
Now we are looking to build the setup with without changing any Static and Virtual IP’s. Can you please suggest the suitable solution to implement this PLZ?
1.We can build the new Server and the same can be added to cluster Group by removing of passive one (Server 2). After that we can failover from Server 1 to Server 2, I hope it will work, because all the installation was happened to SAN Disks. But when we are planning to migrate the SAN, can we able to move the System databases from one location to another location without any interruption?
2. After adding the Server in to Cluster Group, does it required SQL Installation again or failover will take care of it?
3.Normally whenever there was a change in System databases, and then we need to reinitiate the Replication process freshly. I hope we can also initiate the replication from Backup when we are doing the changes in same Server / instance within in the system databases.
4.It would better to have fresh Cluster setup with 2 new Servers with different IP’s. So that we can easily move the Data files and configure the Replication. But it’s going to be a time consuming process to configure the entire Replication and change in IP’s will cause the configuration changes. So application team expecting no changes in IP’s.
Please suggest the suitable solution to do this. Thanks in advance.
Regards, Thulasi. [/font]
November 9, 2012 at 5:55 am
trayalacheruvu (11/8/2012)
[font="Verdant"]Dear Friends,I need valuable suggestion to do the Servers Migration and SAN relocation in the below scenario:
SQL Server Setup in Windows Clustering: We are currently running with 3 physical Servers and hosted with 2 Node Cluster. I mean Server 1 is active for one Instance (Default Instance), Server 3 is active for another instance (Named instance) and Server 2 is passive for both the instances. All the system and user data files are hosted in SAN Drives. And also we have transactional replication configured for User databases from Server 1 & Server 3 to one more Standalone Server called XXXX. Due to performance issues with Servers and Storage we are planning to replace the old Servers with new Servers as well SAN Box.
You would be better off migrating to a new cluster.
trayalacheruvu (11/8/2012)
Now we are looking to build the setup with without changing any Static and Virtual IP’s. Can you please suggest the suitable solution to implement this PLZ?
Without taking the original equipment down it will be difficult as the IP and network names will already be claimed by the running services.
trayalacheruvu (11/8/2012)
1.We can build the new Server and the same can be added to cluster Group by removing of passive one (Server 2). After that we can failover from Server 1 to Server 2, I hope it will work, because all the installation was happened to SAN Disks. But when we are planning to migrate the SAN, can we able to move the System databases from one location to another location without any interruption?
What operationg system do the current and new machines use?
It may be possible to join the new server to the existing cluster and then do an in place upgrade on the instance. Its also possible to mirror the LUNs, but i think you're opening a can of worms here. I still recommend you perform a clean migration.
trayalacheruvu (11/8/2012)
2. After adding the Server in to Cluster Group, does it required SQL Installation again or failover will take care of it?
Yes any new node needs to have the SQL server software installed for the instance it is joining.
trayalacheruvu (11/8/2012)
3.Normally whenever there was a change in System databases, and then we need to reinitiate the Replication process freshly. I hope we can also initiate the replication from Backup when we are doing the changes in same Server / instance within in the system databases.
What do you mean here
trayalacheruvu (11/8/2012)
4.It would better to have fresh Cluster setup with 2 new Servers with different IP’s. So that we can easily move the Data files and configure the Replication. But it’s going to be a time consuming process to configure the entire Replication and change in IP’s will cause the configuration changes. So application team expecting no changes in IP’s.
I guarantee you, you are creating more work and potential problems by pursuing the route you are looking at.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 14, 2012 at 5:03 am
Hi Thanks for the reply.
1. What operating system do the current and new machines use?
Windows 2003 Server.
2. Yes any new node needs to have the SQL server software installed for the instance it is joining.
Yes , when we are doing SQL Install in stand alone Server it won't promote for Failover Option. we can do this only when we are logged in through VIP. But here we have Active Server running for Prod from Cluster Group , so we need to make the passive Server ready offline and need to failover from Active to passive. In this case if we install SQL in stand alone in different drives does this work to failover from Active to passive? consider that our Active server SQL was installed in Old SAN Disks and New Server can be connected to both SAN Disks.
3. Normally whenever there was a change in System databases, and then we need to re-initiate the Replication process freshly. I hope we can also initiate the replication from Backup when we are doing the changes in same Server / instance within in the system databases.
I mean , can we able to preserve the replication settings through backup file in different servers?
Regards,
Thulasi..
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply