Reporting Services Disaster Recovery

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Dave Lumley » Reporting Services Disaster Recovery

18 posts, Page 2 of 2

««1 2

Reporting Services Disaster Recovery

Rate Topic

Display Mode

Topic Options

Author

Message

dave-dj

Posted Thursday, April 22, 2010 2:50 AM

Old Hand

Group: General Forum Members
Last Login: Monday, May 20, 2013 11:47 AM
Points: 380, Visits: 1,014

there are a few things you need to do to use a single address such as http://LiveRS.domain.net/Reports working.

1 - both the servers will need to have a fixed IP address.

2 - you need to install dnscmd (if it's not already installed on the servers)

3 - You will need to amend Reporting Services – Activate RS
to include an additional 'Operating System (CmdExec) job step to add a DNS entry for the server that you would be switching live, eg sqltest01 might need:

dnscmd DNSServer.domain.net /RecordAdd domain.net LiveRS 60 A 192.168.10.1

and sql test02:

dnscmd DNSServer.domain.net /RecordAdd domain.net LiveRS 60 A 192.168.10.2

Also, on each respective server for the Reporting Services Switch Live – Maintenance and Reporting Services Force Live – DR add a job step to remove the dns entry for the server that was live and is now becoming the standy / mirror or has become unavailable.

so sqltest01 would be:

dnscmd DNSServer.domain.net /RecordDelete domain.net LiveRS 60 A 192.168.10.2 /f

and sql test02:

dnscmd DNSServer.domain.net /RecordDelete domain.net LiveRS 60 A 192.168.10.1 /f

4 - you'll have to setup host headers on the SSRS sites. (we tend to set up both the server name as a host header, i.e. sqltest01.domain.net and also the live references you want to use i.e. http://LiveRS.domain.net/Reports.

5 - Then you will have the unenviable task of setting up Kerberos authentication. Tongue

(this is likely to frustrate the hell out of you, if you haven't done this before, as there are lots of 'moving parts'). In breif, you'll need to setup SPN's for SQL Server and http service (for RS) and trust the servers....

it's better explained in the following locations:

Configuring Kerberos Authentication - http://www.sqlservercentral.com/articles/Security/65169/

Kerberos, Delegation and SQL Reporting Services - http://callumhibbert.blogspot.com/search?q=kerberos+delegation

Troubleshooting Kerberos Delegation (Very useful article)- www.microsoft.com/DownLoads/details.aspx?FamilyID=99b0f94f-e28a-4726-bffe-2f64ae2f59a2&displaylang=en

_____________________________________________________________________________
MCITP: Business Intelligence Developer (2005)

Post #908398

l543123

Posted Thursday, April 22, 2010 5:48 AM

SSC Rookie

Group: General Forum Members
Last Login: Friday, September 28, 2012 6:27 AM
Points: 42, Visits: 170

thanks Dave, will try this out. will try with 2 test servers.

Post #908488

Gaius Baltar

Posted Wednesday, May 19, 2010 3:29 PM

Grasshopper

Group: General Forum Members
Last Login: Thursday, January 17, 2013 8:00 AM
Points: 20, Visits: 293

I am wondering the same thing. Did you ever get an answer to this?

Post #924714

dave-dj

Posted Thursday, May 20, 2010 2:15 AM

Old Hand

Group: General Forum Members
Last Login: Monday, May 20, 2013 11:47 AM
Points: 380, Visits: 1,014

sorry answer to what?

What was the question?

_____________________________________________________________________________
MCITP: Business Intelligence Developer (2005)

Post #924889

lilyahuff

Posted Friday, July 02, 2010 11:54 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, March 30, 2011 10:30 AM
Points: 9, Visits: 89

did this with ssrs 2008 R2.
kinda works, jobs do not create (msdb has changed some). manual fail-over steps on same old keys.

have to do good old
C:\Users\sqlinstalladmin>rskeymgmt -l
QASQL2008M\MSSQLSERVER - 87d8f5f3-ca94-4a81-94c4-5f477ee03cd6
QASQL2008\MSSQLSERVER - bd25cc94-4826-43b1-a9ea-7fc4524d3dd5
The command completed successfully

C:\Users\sqlinstalladmin>rskeymgmt -r 87d8f5f3-ca94-4a81-94c4-5f477ee03cd6
Are you sure you want to delete this key? Yes (Y)/ No (N): y

The command completed successfully

to kill one of the keys to force SE to work and do not complain that
Reporting Services "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported)

does anyone know how to make rskeymgmt work in silent mode and do not ask?

Post #947032

Simon-413722

Posted Monday, November 15, 2010 10:08 PM

SSCrazy

Group: General Forum Members
Last Login: Yesterday @ 7:50 AM
Points: 2,117, Visits: 1,291

Hi Dave,
Its a wonderful steps you've provided in your article.

I've been SSRS admin for quite some time. Reading through your article, I was particularly looking for the section where you apply permission scripts from the principal to the DR server but couldnt find it.

Particularly, I'm referring to RSExecRole being created on the DR. Would switch to DR still work without this database role in msdb?

Simon

Simon Liew
Microsoft Certified Master: SQL Server 2008

Post #1021206

dave-dj

Posted Tuesday, November 16, 2010 2:53 AM

Old Hand

Group: General Forum Members
Last Login: Monday, May 20, 2013 11:47 AM
Points: 380, Visits: 1,014

Hi Simon.

the RSExecRole wasn't something I ever really considered - most likley because I never encountered an issue with security and accessing the report server db.

As you mention it, my initial process was to install Reporting Services on both the servers that you want to use in the DR solution, following that i dropped one of the Reporting Server databases and then set up mirroring etc etc as per article. I believe as I done the standard install on both servers, it took care of the RSExecRole for me.

The area where you will need alot of consideration (and I haven't got around to doing this yet) is RS scheduled report jobs.

As the scheduled report jobs are created on th SQL server instance, you will need a mechanism for copy the Principle Report Servers scheduled report jobs to the backup server. I'll document this once I've done it, but my initial thoughts are to look at what jobs are listed in the report server db and those that are in the msdb sysjobs table, copying / deleted the sql agent jobs as appropriate.

let me know it I've not answered your question

_____________________________________________________________________________
MCITP: Business Intelligence Developer (2005)

Post #1021321

Simon-413722

Posted Tuesday, November 16, 2010 4:01 AM

SSCrazy

Group: General Forum Members
Last Login: Yesterday @ 7:50 AM
Points: 2,117, Visits: 1,291

I see. That definitely answered my question.

The installation would've taken care of the permissions.

thanks,
Simon

Simon Liew
Microsoft Certified Master: SQL Server 2008

Post #1021349

« Prev Topic | Next Topic »

18 posts, Page 2 of 2

««1 2

Permissions