How to Configure SQL Server Reporting Service on Cluster (SSRS Cluster) for High Availability ?
We can configure SQL Server Database Engine, Analysis Services and Integration Services for High availability but how to Configure Reporting Services on Cluster (SSRS Cluster) for High Availability that too without using a any third party Load Balancing component.
The best way to configure SQL Services Reporting Services on cluster (SSRS Cluster) is to scale out Reporting services environment and have load balancer in place so that Load balancer can automatically forward the requests to multiple Reporting services, which are part of scale out deployment, using some algorithm like round robin etc.
I was being asked by one of my college, how can we configure SQL Server Reporting Services on a cluster (SSRS Cluster) so that an automatic failover can occur without using a Load balancer as the project was on low cost and a low number of active SSRS users.
Let’s take a quick example, where I going to go thru with a SQL Server Reporting Services Cluster Installation.
In the above solution all Users will be accessing Reporting Services by a virtual name “REPORTServer” which has it’s own IP Address : 192.168.5.99
This is the similar configuration as we have for Clustered SQL Server Instance.
STEP BY STEP VIDEO Tutorial to Configure Reporting Services for High Availability in Clustered environment.
STEP 1 – Install Reporting Services on both Nodes and Scale OUT solution, Please check my previous article, ” Installing & Configuring SQL Server Reporting Services on Cluster Environment for High Availability“, here you will find that step by step instructions to configure Both Reporting Services (Nodes) pointing to common Report Database Server.
STEP 2 – Create a Virtual Server Name / IP Address (Client Access Point) in Clustered Services or Application group where you have SQL Services / resources
Enter the Virtual Name, which you want to use for your reporting Services and Enter virtual IP address which you want to configure for reporting Services. In Demo I used “REPORTSERVER” as name and 192.168.5.99 as Virtual IP address for cluster Services.
I have created this Virtual name / IP address for Reporting services in same Resource group as SQL Server as I wanted to go for automatic failover of this Virtual IP / NAME of reporting Services with SQL Server.
If you want reporting services Virtual name should go with SQL Server then add a dependency of SQL Services on Reporting Services IP address.
NOTE - The limitation of this configuration is that SQL Services / Reporting services both will be used by users on Same NODE, which might result some resource contention.
To overcome this issue or in highly used reporting environment, create a dedicated resource group for Reporting services and add Virtual name / IP address in that group.
In this the limitation is you will not be able to create resource dependency and users will able to ping the name / address even if the SQL services are not running. But I believe that should be fine.
STEP 3 – Create a DNS Record and PTR record in DNS Server in my case this is “REPORTSERVER” and point that a Virtual Server Name / IP Address, which we created in previous step using (Client Access Point) in Clustered Services or Application group where you have SQL Services / resources.
That’s it, you are done with SQL Server Reporting Services Cluster Configuration (SSRS Cluster) without load balancer. Now you can access reporting Services on any machine using virtual name and that will support the automatic failover too.
If you have question to any step, check the video, which is inbuilt in this post, that has Step by step instruction and work flow of configuring SSRS cluster without load balancer.