SQL 2008 R2 mirror
Greetings,
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!
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!
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
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.
ASKER
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
thx again
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.
ASKER
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.
Thanks again for the info.
Microsoft SQL Server
Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.
171K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER