June 16, 2016 at 2:34 am
Morning All,
I've got a 4 node AlwaysOn arrangement.
Currently SSRS is installed on, and run entirely from the 4th node (N4).
N4 hosts the reportingservice database and reportingservicetempdb.
N4 also hosts the SSRS Windows Services.
This is obviously a single point of failure.
How would I make this more highly available? My inital thoughts are to add the two RS databases into a AG that can move between two of the nodes.
Secondly, set up scale out deployment of the SSRS service accross those same two nodes
Would this work in the event of losing the current reporting node?
Is there an alternative/better way?
Cheers
Alex
June 16, 2016 at 5:01 am
Not like cluster , always on is cluster aware, kindly go through the below link.
https://msdn.microsoft.com/en-us/library/hh882437%28v=sql.120%29.aspx
Regards
Durai Nagarajan
June 16, 2016 at 9:01 am
Thanks Durai.
It says, if I Am reading it correctly and not missing something that the reports service needs to be restarted.
Is there a way I can achieve this without needing to restart the SSRS Service?
I suppose worst case I could monitor for a fail over and use powershell to restart the services but that seems unnecessary.
Would scale out deployment not help here at all?
June 17, 2016 at 7:44 am
Putting your SSRS database in an Availability Group will increase the availability of the databases put not the availability of SSRS itself. If the N4 server dies. you have your databases running on another node but no SSRS services.
In order to get a better availability you need to add the DBs to an AG AND do a scale out scenario of your SSRS. For a scale out of your SSRS you need to create a NLB cluster or use an appliance like Citrix NetScaler or F5. I do not know if it possible to create a NLB on a cluster used for availability groups. If this is not possible you need an appliance or setup dedicated servers for SSRS.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply