|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Yesterday @ 11:47 AM
Points: 380,
Visits: 1,014
|
|
Comments posted to this topic are about the item Reporting Services Disaster Recovery
_____________________________________________________________________________ MCITP: Business Intelligence Developer (2005)
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Tuesday, February 12, 2013 8:59 AM
Points: 20,
Visits: 55
|
|
| This was a great article thank you!
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 7:24 AM
Points: 5,266,
Visits: 11,198
|
|
Great job Dave, well done.
The automation of the process and use of proxies is a nice touch.
There is nowhere near enough information on SSRS DR out there and this is a much needed addition.
Its worth pointing out the reporting databases will need to be in full recovery mode to use mirroring, and in fact any HA solution could be used to get the database to the failover server,be it full copy and restores, log shipping or even SAN replication.
---------------------------------------------------------------------
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Yesterday @ 11:47 AM
Points: 380,
Visits: 1,014
|
|
absolutely. This is one possible scenario, but for me, the most appropriate.
Worth saying as well, that we use dns entries in our connection strings to the active report server and active database server, so it's a simple log off & log back on for users to pick up the new dns entry that would point to a different IP address.
Also another point, which I didn't cover in the article, as it's a different topic, is that if you intend on doing something similiar with dns entries, then it's quite likely that you will need to setup SPN's (Service Principle Names), in order to get Kerberos Authentication working.
Glad you liked it though and thanks for pointing me in the direction of the Knowledge Base article.
_____________________________________________________________________________ MCITP: Business Intelligence Developer (2005)
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 12:02 PM
Points: 1,058,
Visits: 2,574
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 12:32 AM
Points: 3,574,
Visits: 5,112
|
|
I use a simpler approach: Jasper Smith's Reporting Services Scripter (http://sqldbatips.com/showarticle.asp?ID=62). Keep everything saved off onto a separate machine and you can migrate pretty quickly. Clearly not as 'available' as mirroring but I think everyone should have this layer of recoverability scripted out and ready to go.
Best,
Kevin G. Boles SQL Server Consultant SQL MVP 2007-2012 TheSQLGuru at GMail
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, September 28, 2012 6:27 AM
Points: 42,
Visits: 170
|
|
| Nice article! Quick question, sorry if its silly. If use is accessing reports from a front end application using url's like http://SQLTEST01/ReportServer/Report1 or http://SQLTEST01/Reports/Report1, then if the failover happens to SQLTEST02, will the url's work? Will the same url's automatically point to SQLTEST02's reportserver? Or is this something which needs to be handle separately?
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, September 28, 2012 6:27 AM
Points: 42,
Visits: 170
|
|
Hi Dave, can you please let me know how you use DNS entries to point to correct server or change server? We currently hardcode the url's with server name which I think is a bad idea when using failover.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, December 20, 2012 7:04 PM
Points: 7,
Visits: 68
|
|
|
|
|
|
SSCoach
         
Group: General Forum Members
Last Login: Yesterday @ 1:07 PM
Points: 18,733,
Visits: 12,332
|
|
|
|
|