I've inherited a two-node Windows Failover Cluster (SAN storage) with a SQL Cluster configured (Standard Edition) but where SSRS had been rather hopefully installed on both nodes as well. If the SQL Cluster Role is on Node 1 then SSRS works but once it fails over to Node 2 it doesn't. Once failed back to Node 1, it comes back to life.
I'm very much a SQL n00b but had a look in ReportServer DB's "Keys" table. It has an entry for each server, with both having an InstallationID and PublicKey but only the node SSRS works on having a SymmetricKey. I thought having more than one server listed would have caused a Scale Out warning - or is that only if more than one has a symmetric key listed?
The supplier of the system that uses this says we could export the SSRS encryption key off the working SSRS and in the event of failover, import it into SSRS config on the other node... is that the case?
Is there really some nearly-highly-available-SSRS workaround doable like this??
Many thanks for any thoughts!