I think another mentioned this. If you move the databases to a new server (not part of this problem) and you move the reporting services to a new server and you are not using the enterprise edition then you have to go into the keys database and remove one of the keys after you reactivate the system. In slq 2005 you can reactivate the system by adding the password, again, to the authentication in the reporting services config tool. I have to duplicate our production environment in QA and do this quite often.  I also back up the RS database everynight, along with the system databases. You can mirror these databases or put them on your cluster if you have one. Log shipping would work but it is not like you should be changing your production reports every 5 minutes.