SQL 2008 R2 mirror


I have a 2008 SQL R2 server running on Windows server 2008 enterprise. I would like to mirror it to 2008 SQL R2 server running on Windows server 2008 R2 std server. Is that possible since the OS is different?

Also, any tips or direct steps on mirroring would be great. Small database for our doc mgt system, about 150 GB. One server in the office, one in the datacenter.

Thx alot!
king daddyAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Eugene ZConnect With a Mentor Commented:
from OS point of view - you should be ok

about mirroring and setup

Database Mirroring Overview

Prerequisites, Restrictions, and Recommendations for Database Mirroring
 SQL Server 2008 R2  

Setting Up Database Mirroring
Carl TawnConnect With a Mentor Systems and Integration DeveloperCommented:
Mirroring between different OS versions is fine, it's the versions of SQL Server that need to be the same.
king daddyAuthor Commented:
thanks for clarifying guys. now on to planning this out. Thanks also for the links.
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

Carl TawnSystems and Integration DeveloperCommented:
Setting up mirroring is easy enough. Your main decisions will be around authentication, whether you want a witness server/automatic failover, and whether to use synchronous or asynchronous mode.
king daddyAuthor Commented:
Thanks Carl Tawn. I haven't yet decided on that. Do you have any suggestions? I have one SQL server in the office and the mirror would be in a datacenter. The entire database is about 150 GB. There is a change file (Veeam backup) ranging between 2 GB and 17 GB a night, depending on the day of the week, if that helps with the amount of use the db sees daily. Once I decide, I will need to speak with an integrator of the doc mgt system we use, or their support, to determine how failover (manual or auto) will affect end users. I have read from a few online sources regarding sync / async and also regarding auto / manual, but was planning on delving in a bit more this weekend.

thx again
Carl TawnSystems and Integration DeveloperCommented:
When I was working as a DBA in a data centre we always used to use manual failover and asynchronous. Manual failover because there were other systems in the loop, so automatic  failover of the databases wouldn't be enough in itself to keep systems running (plus we used local clustering for hardware redundancy, with mirroring as a DR solution). Asynchronous came down to latency between our primary data centre and the DR one 300 miles away. For us the latency was too high with synchronous and affected production - the caveat being a potential for data loss in the event of a failover, which is also partly why we didn't use automatic failover.
king daddyAuthor Commented:
Thanks Carl. The latency issue is one that I had thought of, based on having to tweak resources and increase the bandwidth about 1.5 years ago when I put our exchange servers at the data center, which is about 150 miles North of us. That said, it seems async is the way for us. Additionally, we have two other servers in the doc mgt system relying on the SQL server, so manual seems better for us.

Thanks again for the info.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.