SQL Server DR, mirroring or virtualise and mirror
I have a client with a small business server 2008 Premium installation.
This obviously includes SQL Server 2008 standard on a seperate 2008
server. On the SQL we run several line of business applications.
The client has got the the size where if we were to have a failure it
would cripple the business. We have ample backups protecting the data, but
it would obviously take time to get a new server up and running etc.
What we want is a stand by server in a remote office, but i need to know
the best way of replicating the SQL server. I see there are different
ways, snap shot or transactional etc, but i havent found a descent article
describing the pros and cons of them.
I dont want to put much more stress onto the SQL server as it is quite
busy with both reads and updates. I dont want the primary server waiting
on the secondary server to update before it commits a write.
Also the table structure and views change fairly regularly as new
features/updates are added to the LOB applications.
Im wondering if anyone has any opinion on what method may help.
Also wondering if we would be better off virtualising the server and
mirroring this, which i believe is quite good with the new hyper V.
No comments:
Post a Comment