Recover SQL

Applies To: System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator

The Recover SQL activity is used to configure a runbook that recovers a SQL database to its original location or to a network folder.

Be aware that the term Network Folder is used in this integration pack in the same way that it is used in the Data Protection Manager user interface. Choosing Network Folder recovers to a local path on a production server. Therefore, the selection of Network Folder requires the name of a production server and a local path on that production server. Also be aware that recovery to any SQL Instance is not a supported activity for this integration pack because Data Protection Manager does not support this scenario through its PowerShell API.

For the procedure to configure this object, see: Configuring the Recover SQL Activity.

The following tables list the properties and published data for this activity. The activity publishes all the data from the required and optional properties into published data.

Recover SQL Properties

Recover SQL Optional Properties

Recover SQL Published Data

Configuring the Recover SQL Activity

To configure the Recover SQL activity

1. From the Activities window, drag a Recover SQL activity to the active runbook. Double-click the Recover SQL activity icon.

2. On the Properties tab, click the ellipsis button (...), and select the Name of the Data Protection Manager computer that you want to connect to with this activity.

3. In the Properties section, the properties required to define the activity are listed. Select a property in the list, and enter a value for the property. Or, to automatically populate the value from the data published by any previous activity in the runbook, right-click the property box, point to Subscribe, and then click Published data. Click the published data element you want to use, and then click OK.

   The Recovery Type property has two options:

   • When the Recover to Network Folder option is used, the optional property Restore Security can be used. If not specified, this property defaults to Apply security settings of destination computer.

   • When the Recover to Original Instance option is used, the optional properties Database State and Copy Log Files can be used. If not specified, Database State defaults to Leave database operational and Copy Log Files defaults to False. For more information about the Copy Log Files option, see the Log Files section.

4. To use additional properties, click Optional Properties. In the Add/Remove Property dialog box, select the properties you want to apply to this activity from the Available list, and then click the right arrow button (>>). The properties appear in the Selected list. To remove a property from the Selected list, click the property, click the left arrow button (<<), and then click OK.

5. To automatically populate the value for the additional properties from the data published by any previous activity in the runbook, right-click the property box, point to Subscribe, and then click Published data. Click the published data element you want to use, and then click OK. For a list of the data elements published by each activity, see the Published Data tables in the activity topic.

6. For information about the settings on the General and Run Behavior tabs, see Common Configuration Instructions for all Activities.

7. Click Finish.

Log Files

When you create a recovery point by using express full backup and leave the database non-operational but able to restore additional logs, the Copy Log Files option is disabled. The Copy Log Files option is available only when you create a recovery point by using incremental backup. To copy log files in this configuration, perform the following procedure.

To copy log files when the database is set to non-operational but able to restore additional logs

1. On the Data Protection Manager server, create a protection group to protect the data source. Set Replica Creation to Now.

2. Create a recovery point for the data source. Select Create a recovery point by using incremental backup.

3. Configure the Recover SQL activity:

   1. Enter a valid Data Source ID and Recovery Source ID

   2. Set Recovery Type to Recover to Original Instance.

   3. Select Leave database non-operational but able to restore additional transaction logs.

   4. Select Copy SQL transaction logs between the selected recovery point and latest available recovery point.

   5. Enter or browse for a Copy Destination for the log files.

Other Activities

The Integration Pack for Data Protection Manager contains the following additional activities:

• Create Recovery Point

• Get Data Source

• Get DPM Server Capacity

• Get Recovery Point

• Protect Data Source

• Recover SharePoint

• Recover VM