Restore ACS
You can make a backup of the database and restore the ACS in a SCOM server from another domain? I have a development environment and want to know if I can back up the ACS production and restore the ACS in development, it is possible?
May 3rd, 2012 10:44am

Hi What are you looking to achieve? You can in theory copy the database to another domain but all the logins will likely fail (as I assume the dev environment is completely seperate from Production). And if SQL is running as a domain user account then it is likely it will fail to start until this is changed (through SQL Configuration Manager and not through the Services applet). It will need some tweaking but if you want to play around with the reports and manipulate the data then this will work once you create some logins for the dev domain. Have a chat with your friendly DBAs and they should be able to arrange it all for you! Cheers Graham Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 10:55am

Hi Marcelo, As Graham mentioned, if yuo need to restore it in the Dev Lab, then you will deal with it as a Database with SQL Server Reporting Service interface, and you have to manage the logins for successful databse access / report usage and running..Regards, Mazen Ahmed
May 3rd, 2012 12:39pm

Graham wrote: ... What are you looking to achieve? ... ... In my opinion a strong contender is being able to test something in dev until it works and then to transfer it into production with the least amount of effort - and by the way avoid errors, which might creep in if the transfer is done manually (e.g. by repeating documented steps). Any recommandation for this? Regards, Carsten
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 1:05am

I definitely agree with having test, uat and production environments but the original posters question is about going the other way - from production to development. I can see some reasons for it as well e.g. testing upgrades .. but I want to make sure I understand the original posters requirements to make sure we could give some specific advice. For instance, if someone is looking to "copy" part of production to test upgrades then there is a great guide here: http://technet.microsoft.com/en-us/library/hh914226.aspx Although it relates to service manager 2010, the same principal can be applied to scom. For Dev \ Prod ideas: http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/815663c5-8051-4f90-bf5f-fa0ae90899fa "It is not uncommon for production instance of SCOM to monitor both production and test. If you need to have two SCOM instances, understand there are two management groups and two databases involved. Maintain the same sealed management packs between the two management groups. Custom management packs can be exported from the test management group and imported to the production management group. Keep in mind computer-specific overrides from the test group won't have effect in the production group. Production will maintain its own overrides." Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
May 4th, 2012 3:10am

Graham, you're right. I read the original posters question too fast and my brain put it the other way around - obviously my wish was father to my thought ;-)
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 3:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics