Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

System Center Integration Pack for System Center Data Protection Manager 2010

Updated: November 1, 2013

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

The System Center Integration Pack for System Center Data Protection Manager 2010 is an add-in for System Center 2012 - Orchestrator that enables you to automate the protection of virtual machine hosts and virtual machine guests. You can use the objects in this integration pack to create workflows that provide the following:

  • Automated virtual machine protection and recovery

  • Automated SharePoint Farm protection and recovery

  • Automated system state protection

  • Ad hoc backups

System Requirements

The DPM Integration Pack requires the following software to be installed and configured before you implement the integration. For more information about how to install and configure the Orchestrator and System Center Data Protection Manager, see the documentation for each of the following products:

  • System Center 2012 - Orchestrator

  • System Center Data Protection Manager 2010

  • Windows Management Framework

Downloading the Integration Pack

For information about how to obtain this integration pack, see System Center 2012 – Orchestrator 2012 Component Add-ons and Extensions.

Registering and Deploying the Integration Pack

After you download the integration pack file, you can register it with the Orchestrator and then deploy it to one or more action servers or clients. For more information about how to install integration packs, see How To Install an Integration Pack.

To register and deploy the integration pack

  1. Copy the Data_Protection_Manager_2010_Integration_Pack.OIP integration pack file to the Orchestrator computer.

  2. Confirm that the file is not set to Read Only as this can prevent unregistering the integration pack at a later date.

  3. Click Start, point to All Programs, point to Microsoft System Center 2012, and then click Orchestrator. Right-click Deployment Manager, and then click Run as Administrator.

  4. In the left pane of the Deployment Manager, expand Orchestrator Management Server. Right-click Integration Packs, and then click Register IP with the Management Server.

  5. In the Select Integration Pack or Hotfix window, click Add. Locate and select the Data_Protection_Manager_2010_Integration_Pack.OIP file that you copied in step 1. Click Next.

  6. In the Completing the Integration Pack Wizard dialog box, click Finish. The Log Entries pane displays a confirmation message when the integration pack is successfully registered.

  7. In the left pane of Deployment Manager, right-click Integration Packs, and then click Deploy IP to Action Server or Client. Click Data Protection Manager 20120 Integration Pack, and then click Next.

  8. Click the action server or client computer on which you want to deploy the integration pack, click Add, and then click Next.

  9. In the Installation Options dialog box, select the options that apply to this deployment, and then click Next.

  10. To choose a time to deploy the integration pack, select Schedule installation check box, and then select the time and date from the Perform installation list box.

  11. Select one of the following:

    1. Stop all running runbooks before installing the integration pack to stop all running runbooks before deploying the integration pack.

    2. Install the Integration Packs without stopping the running Runbooks to install the integration pack without stopping any running runbooks.

  12. Click Next.

  13. In the Completing Integration Pack Deployment Wizard dialog box, click Finish.

  14. When the integration pack is deployed, the Log Entries dialog displays a confirmation message.

WarningWarning
If you did not configure a deployment schedule, the integration pack deploys immediately to the computers that you specified. If you configured a deployment schedule, verify that the deployment occurred by verifying the event logs after the scheduled time has passed.

Windows Management Framework

The DPM Integration Pack uses Windows PowerShell remoting on the Runbook Designer and on the integration server and on the Data Protection Manager server. Perform the following tasks on the Orchestrator server and on the Data Protection Manager server before you configure the Data Protection Manager connection in the Runbook Designer.

To confirm the Windows Management Framework prerequisites

  1. Confirm that you have Windows PowerShell 2.0 installed on the Orchestrator server and on the Data Protection Manager server. One way to do this is to open Registry Editor. Expand the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine subkey. Confirm that the value of the Runtime Version entry begins with v2.0. If this value begins with 1.0, or if the subkey is not present, install Windows PowerShell 2.0 using the instructions in article 96829 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?linkID=193574).

  2. Confirm that you have Windows Remote Management 2.0 (WinRM 2.0) installed and configured on the Orchestrator server and on the Data Protection Manager server. One way to do this is to confirm your configuration is in the Local Group Policy Editor.

  3. For more information abouthow to install and configure WinRM 2.0, see Installation and Configuration for Windows Remote Management (http://go.microsoft.com/fwlink/?linkID=171111).

To enable Windows Remote Management Trusted Hosts

  1. On the Orchestrator computer, open the Local Group Policy Editor. To do this, click Start, click Run, type gpedit.msc, and then click OK.

  2. In the Local Group Policy Editor, under Local Computer Policy, expand Administrative Templates, expand Windows Components, expand Windows Remote Management, expand WinRM Client, and then double-click Trusted Hosts.

  3. On the Setting tab, click Enabled. Add the name or IP address of the Data Protection Manager Server to the Trusted Hosts List. Click OK.

To set the execution policy in Windows PowerShell

  • The execution policy in Windows PowerShell determines which scripts must be digitally signed before they will run. By default, the execution policy is set to Restricted. This prohibits loading any configuration files or running any scripts.

    To run the scripts in this integration pack, you must set the execution policy to RemoteSigned. Use the following command: <System Drive>:\PS>set-executionpolicy remotesigned. For more information abouthow to configure the Windows PowerShell execution policy, see Set-ExecutionPolicy in the Microsoft TechNet Library (http://go.microsoft.com/fwlink/?linkID=113394).

To enable or confirm remote connection settings in Windows PowerShell

  1. This integration pack uses Windows PowerShell remote commands to communicate with the Data Protection Manager server, regardless of whether the DPM server is remote or local. If you have not already done so, you must configure the DPM server and the Orchestrator client computer to receive Windows PowerShell remote commands that are sent by the Orchestrator server.

    Run the following command only one time on each computer that will receive commands. You do not have to run it on computers that only send commands. Because the command activates listeners, we recommend that you run it only where it is needed.

    1. Start Windows PowerShell with the "Run as administrator" option.

    2. Type System Drive:\PS>enable-psremoting

    For more information abouthow to use the Enable-PSRemoting cmdlet, see Enable PSRemoting in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?linkID=144300).

  2. You can use WS-Management quotas in Windows PowerShell remoting to protect the Orchestrator and DPM computers from excessive resource use, both accidental and malicious. The MaxConcurrentOperationsPerUser quota setting in the WSMan:\ComputerName\Service node provides this protection by imposing a limit on the number of DPM objects that can run concurrently.

    By default, MaxConcurrentOperationsPerUser is set to 5. This means that you can run a maximum of five DPM objects (shells) concurrently across all DPM policies.

    If this default setting does not meet the needs of your organization, see About_Remote_Troubleshooting in the Microsoft TechNet Library (http://go.microsoft.com/fwlink/?linkID=135188) for information about how to configure remote operations in Windows PowerShell.

Configuring the System Center Data Protection Manager Connections

To set up the System Center Data Protection Manager connections

  1. In the Runbook Designer, click the Options menu, and then select System Center Data Protection Manager.

  2. In the Data Protection Manager dialog box, on the Configurations tab, click Add to begin the connection setup.

  3. In the Name box, type the name of the Data Protection Manager computer that you want to connect to with this integration.

  4. In the Type box, click the ellipsis button (...), and then click PowerShell Remoting.

  5. In the Properties pane, the elements that are required to define this integration are displayed. Enter a value for each element, and then click OK.

  6. Click Finish.

Setting up the System Center Data Protection Manager Workflows

WarningWarning
If you have to run multiple instances of an object, make sure that the activities run in series (not in parallel) so that Data Protection Manager performance is not adversely affected.

See System Center Data Protection Manager Activities for links to configuration instructions for the objects in this integration.

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.