Your network contains a System Center 2012 R2 Configuration Manager Service Pack 1 (SP1) environment.
The environment contains a primary site server named Server1 and a server named Server2 that runs Microsoft SQL Server 2012. Server2 contains the
Configuration Manager database.
Server2 fails.
You install SQL Server 2012 on a new server. You name the server Server2.
You need to restore the Configuration Manager database to the new server.
What should you do?
A. From Server1, run the Configuration Manager 2012 Setup Wizard.
B. From Server2, run Microsoft SQL Server Management Studio, and then attach the backed up SQL Server database and log files.
C. From Server2, run Microsoft SQL Server Management Studio, and then restore the backed up SQL Server database and log files.
D. From Server1, run the Site Repair Wizard.
Correct Answer: A
Explanation/Reference:
Explanation:
Answer is From Server1, run the Configuration Manager 2012 Setup Wizard.
Recover a Configuration Manager Site
A Configuration Manager site recovery is required whenever a Configuration Manager site fails or data loss occurs in the site database. Repairing and resynchronizing data are the core tasks of a site recovery and are required to prevent interruption of operations. Site recovery is started by running the Configuration Manager Setup Wizard from installation media or by configuring the unattended installation script and then using the Setup command / script option. Your recovery options vary depending on whether you have a backup of the Configuration Manager site database.
Site Database Recovery Options
When you run Setup, you have the following recovery options for the site database:
* Recover the site database using a backup set: Use this option when you have a backup of the Configuration
Manager site database that was created as part of the Backup Site Server maintenance task run on the site before the site database failure. When you have a hierarchy, the changes that were made to the site database after the last site database backup are retrieved from the central administration site for a primary site, or from a reference primary site for a central administration site. When you recover the site database for a stand-alone primary site, you lose site changes after the last backup.
When you recover the site database for a site in a hierarchy, the recovery behavior is different for a central administration site and primary site, and when the last backup is inside or outside of the SQL Server change tracking retention period.
Reference: http://technet.microsoft.com/en-us/library/gg712697.aspx
Backup and Recovery in Configuration Manager