February 20, 2013 at 12:22 am
With this new concept, is there any new approach regarding SQL database replication/mirroring in the virtual server concept?
As today, we have 2 physical servers (primary and secondary), but with virtual servers is kind of different, and we don’t know if there is a different way to manage database replication concept on this.
Any information will be much appreciated.
Thanks
jerry
February 25, 2013 at 8:00 pm
You don't treat the concepts replication/mirroring any differently with a virtual environment. The most important aspect with virtualization is making sure you configure the physical host(s), hypervisor, and VMs to best practices and then test & validate its performance. There are plenty of guidelines out for each major hypervisor on the market.
One of the main purposes of virtualization is abstraction and thus nothing from the OS level up nothing should be treated different 🙂
February 26, 2013 at 4:35 am
All of my organisation's database servers are running in AWS and therefore virtual. We use both SQL P2P and standard transactional replication in just the same way as we did on physical kit. Later this year we plan to exploit Always On, and see no reason to do anything special for this just because we are running on AWS.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply