October 29, 2013 at 10:08 pm
We are gearing up to deploy SP 2013 on SQL 2012. As HA/DR is required, we are looking at Synchronous DB mirroring and log shipping on a physical database platform. The OS is either going to be Windows 2008 R 2 or Windows 2012.
The desire is to virtualize the db platform. However, we want to know if performance (IO to be more specific) would be acceptable especially during a crawls that searche through most indexes. Also, any problems you see with the overall HA/DR setup.
I would welcome any recommendations from any one who has already deployed SP2013 or SQL 2012
Thanks in advance for your help.
October 30, 2013 at 4:07 am
layakali.sql (10/29/2013)
We are gearing up to deploy SP 2013 on SQL 2012. As HA/DR is required, we are looking at Synchronous DB mirroring and log shipping on a physical database platform. The OS is either going to be Windows 2008 R 2 or Windows 2012.The desire is to virtualize the db platform. However, we want to know if performance (IO to be more specific) would be acceptable especially during a crawls that searche through most indexes. Also, any problems you see with the overall HA/DR setup.
I would welcome any recommendations from any one who has already deployed SP2013 or SQL 2012
Thanks in advance for your help.
Synchronous Mirroring of SharePoint can cause slowness and performance issues due to having to move the massive tlog data that can be created by all the blobs that get loaded into SP. You get one thread to read the tlog and send it over the wire and one on the secondary to write it. This can be a throttle on some busy systems. Virtualization, if done correctly (which VERY few shops do) will only place a small overhead to your existing physical-layer IO capabilities. The problem (other than people not knowing what they are doing from a virtual standpoint) is that VERY few shops out there have sufficient IO bandwidth to begin with.
I will add that if you are asking such basic questions you should be forewarned that designing, implementing and maintaining an HD/DR construct is NOT EASY and there are MANY ways you can go wrong.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply