Well, it's more like a no brainer why. The job backs up all user DB's. So I have nothing to worry about and I'll catch the changes without any effort, if new reports are added.
On which circumstances to the mentioned files change? If those and the encryption key wouldn't change once configured I just do that once (manually) and the DB backup is the only thing running regularly. Is that the case? -R From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Dienstag, 24. Februar 2015 16:13 To: [email protected] Subject: RE: [mssms] Reporting service backup, automated Don't have a specific method for you except to ask why would want to do this regularly? The reporting services DB stores reporting services specific data like reports and subscriptions. Unless you are changing these regularly, there's no need to back up the DB. Once after you make changes is sufficient as the DB does *not* store ConfigMgr data. J From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Tuesday, February 24, 2015 2:22 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] Reporting service backup, automated Anyone has that automated? I have the DB backup running (from ola.hallengren.com), but then there is the encryption key and the files. Am I right, as long as the reporting services isn't reconfigured, backing up the encryption key once is sufficient? But those still need to be done regularly, right? * Rsreportserver.config * Rssvrpolicy.config * Rsmgrpolicy.config * Reportingservicesservice.exe.config * Web.config for both the Report Server and Report Manager ASP.NET applications * Machine.config for ASP.NET I'm thinking of adding this to the DB backup tasks, but maybe someone has already a solution for that? We may use Veeam in the future, would this be able to do all that? -R
