How do you make RtReports Server redundant?
It isn't specifically designed for clusters or for high availability. You probably can use a few scripts to give it 99% availability using to Rtreports servers and accepting minimal downtime as you transition between RtReport servers. The editor, I will ignore.
You can't load balance an RtReports server since it can read/write from one RtReports MDB configure mostly due to it requiring local security groups. You can switch servers easily and have a second server ready to go within minutes by running the securitysettings.exe. Obtain the correct migration procedure from technical support as running this script correctly is critical. You also will want identically named local user groups on the "secondary" RtReports server.
Of course switching servers should be avoided since the RtReports server acts as a massive cache uses both a persisted storage of old reports and a memory cache.
I'm pretty curious what is driving this.
Can you give more info on switching to a second server?
First off, you should be aware of known issue 119209. Also, in the RtReports admin guide, there is a nice section on how to create a new RtReports server with a new name. I believe the procedure is as simple as making sure that the web-configs are correct (pointed to the correct module), importing the security, modifying it, and exporting it. Once this is done, perform an IIS reset. The RtReports editors will also have to be updated to point to the new server.
Do you have a more specific question?
Retrieving data ...