Backup & restore of the ReportServer and ReportServerTempdb is supported, and much easier if you have a lot of custom reports.
Moving Susdb is another issue that I'm working through now in our environment. Rebuilding it may cause existing software updates to show expired. This is the best article I have found on this topic: http://blogs.technet.com/b/mwiles/archive/2011/06/17/how-to-move-the-wsus-database.aspx Also, if you are moving to a new SQL Server instance, consider that your logins may need to be recreated on the target server: http://www.bidn.com/blogs/sqlscottgleason/sql-server/358/how-to-transfer-sql-logins-between-sql-servers From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, August 30, 2013 7:55 AM To: [email protected] Subject: RE: [mssms] Backup Restore SSRS/SUSDB Yes, that's exactly what I said - but you're over thinking it. You could re-backup the whole database when you create a new report *or* export the report to an .rdl file and just back it up *or* both. If nothing's changed, there's no reason to do anything. You can't robocopy the reports, because they are stored in the DB, not files, that's why you have to export them out first to get to the .rdl files using the web portal, report builder, or another third-party tool. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Keith Valenca Sent: Thursday, August 29, 2013 9:08 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Backup Restore SSRS/SUSDB Jason, so you said the reports are stored in the database, but then you said you only need to backup the reports when you change them. So if I make a brand new report, I do got to backup that report? Do you just do a robocopy of all your reports nightly? When you restore do you just overwrite the reports with the .rdl's you robocopied? ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Backup Restore SSRS/SUSDB Date: Fri, 30 Aug 2013 01:08:04 +0000 I typically recommend just rebuilding the SUSDB. There's absolutely nothing unique about it. Backing it up is easy to add to your SQL maintenance plan though - you are using a native SQL backup up now for 2012, correct? As for SSRS, same thing really. The reports are stored in the SSRS DB so backing it up is sufficient including the encryption key. You can also individually export the RDL files via the SSRS web portal (http://sql-articles.com/articles/general/download-export-rdl-files-from-report-server/), using report builder or a handful of third-party tools. Note that you only need to back up the encryption key once, ever, and reports only need to be backed up when you change them. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Keith Valenca Sent: Thursday, August 29, 2013 7:47 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Backup Restore SSRS/SUSDB I've searched the web, looked at blogs and I can't for the life of me figure out the following: I have SCCM2012 SP1 Primary with remote SQL and remote SSRS, with lots of custom reports. I read you need to backup the encryption key and also the .rdl files for SSRS, but it seems to be some manual process or I just don't understand how to do it. What is the process to backup SSRS so if the machine blows up I can restore it using the same machine name and have my primary still be able to access the reports without losing them all? I have the same sort of question for SUSDB. Do you backup and then restore that if your site blows up or just let it get re-created when you reinstall the site? I have the SUSDB on my remote SQL server. Thanks Keith
