none
Need Suggestion for Setting SQL Server(s)

    Question

  • We have an issue with the OS on SERVER1 which existed in some fashion or other at least since we migrated it to a Virtual Machine.

    We are planning on creating two new servers to replace this server:

    • SERVER2 – Primary replacement with log shipping

    • SERVER3 – Secondary server – recipient of logs

    Would like to have opinion on how to migrate the functions of the existing SERVER1 to these new servers and create a “Hi-Avail” type setup but staying inside our existing license structure.

    Additionally when we spin up these servers both the OS and SQL version will go to current versions.


    Dhiraj

    Wednesday, December 28, 2016 11:21 AM

All replies

  • I'm not sure what you mean by saying "functions"? Do you mean databases? Do you mean server level settings? Or all?

    I assume it's "all", server level settings + databases.

    This depends on your infrastructure and downtime period. For instance some environments do not serve to the end users whole weekends, so it's generally piece of cake to perform the migration. But sometimes seconds mean too much money, so you need to be quick as much as possible.

    If you can move your disks between your servers, you may want to perform a detach / attach method. Otherwise you can perform backup/restore if you have a lot of time. Or you can replicate your databases to the new one and after stopping the incoming transactions you can backup tail of the transaction log and apply to the new server and bring it on.

    Regarding to high availability solution, again it depends on your needs. If you are looking for a high availability Log Shipping is not the brightest idea. You may want to take a look at the Always On Availability Groups if your SQL Server is 2012 or higher, or Failover Clustering, or Database Mirroring. These solutions provide automatic failover option for a high availability scenario and if you do not leverage the secondary server, then you just need to license your primary server.


    http://ekremonsoy.blogspot.com | http://www.ekremonsoy.com | @EkremOnsoy

    Wednesday, December 28, 2016 12:49 PM
  • First and most important: backup the VM. No matter how bad the OS is you still need a point of return

    I'm not sure how you can move SQL from one machine to another though. 

    If you want to stay within the existing SQL licensing structure and achieve HA you can use StarWind VSAN.

    With VSAN you can mirror the storage of server 2 and server 3 and present it as shared storage to SQL cluster and then do SQL FCI.

    Here's a good video on the process: https://www.starwindsoftware.com/critical-sql-server-databases-provide-ha-with-sql-server-failover-clustering

    You can also do this with Free StarWind VSAN so no need to spend more money for storage.

      


    • Edited by Max Craft Friday, January 20, 2017 6:07 PM broken links
    Friday, January 20, 2017 6:06 PM