How to / Nasıl Yaparım:
If a valid site backup exists:
Select Recover this site server using an existing backup, specify or Browse to the backup location.
If a site backup does not exist:
Select Reinstall this site server and the site server components will be reinstalled.
If a valid database backup exists:
Select Recover the site database using the backup set at the following location and specify or Browse to the backup location.
If a database backup does not exist:
Select Create a new database for this site and a new database will be created.
If the database has already been recovered:
If the database has been recovered through alternate methods, select Use a site database that has been manually recovered.
If the database is unaffected by disaster:
Select Skip database recovery (Use this option if the database was unaffected).
Site Recovery Information
Select the type of site (CAS or primary) that you want to recover.
Recover central administration site
Then specify the FQDN of a Reference primary site
When recovering a central administration site, you can specify a reference primary site to use as the authoritative source of data when a site backup does not exist. This option is disabled when Setup has detected that you are recovering a primary site.
Recover primary site
Then specify the FQDN of the Central administration site connection
Recovery in Configuration Manager 2012 then leverages SQL Server database replication from the reference sites to retrieve global data that was created by the failed site before it failed. This process minimizes data loss even when no backup is available.
Site Data Recovery Process
During recovery, a site goes through following states. These can be viewed in the RCMctrl.log.
· Recovered [from backup]
· Prepared For [Data] Recovery
· Recovery In Progress
· Replication maintenance (reinitializing)
· Recovering Data (re-synchronizing)
· Replication Active
· Data Recovered