We are using 2008 R2 in an active/passive failover cluster. The failover is working properly. When we fail over from our primary server (server1) to the secondary server (server2), the SSRS reports are still available and functioning properly.
We are testing using timed subscriptions to send reports to users via email. We have found that they are very inconsistent. While testing, we have them scheduled to run every hour during the work day. We receive the emails about half of the time. While going through different logs, tables, etc. I found the ExecutionLog table. It is very consistent that when the job runs that creates the SSRS event, it gets logged here in the ExecutionLog table. It is also very consistent that when the reports get delivered properly, I see Server1\MSSQLSERVER in the InstanceName field. However, when the reports do not get delivered, I see Server2\MSSQLSERVER in the InstanceName. It looks like that even though we are running on Server1, Server2 is trying to process the reports. I assume this is due to load balancing seeing Server1 being busy processing other reports so it sends them to Server2. So how can I prevent this from happening? If we are running on Server1, then only Server1 should be processing the reports. If it is not a load balancing issue, what could it be?