Integration Pack for System Center Data Protection Manager
Applies To: Opalis 6.3
The Integration Pack for System Center Data Protection Manager (DPM) is an add-in for Opalis Integration Server 6.3 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
Opalis, a Microsoft Subsidiary, is committed to protecting your privacy, while delivering software that brings you the performance, power, and convenience you want. For more information, seethe Opalis 6.3 Privacy Statement (https://go.microsoft.com/fwlink/?LinkID=202690).
The Integration Pack for System Center Data Protection Manager requires the following software to be installed and configured before you implement the integration. For more information abouthow to install and configure the Opalis Integration Server and System Center Data Protection Manager, see the documentation for each of the following products:
Opalis Integration Server 6.3
System Center Data Protection Manager 2010
Windows Management Framework (Windows PowerShell 2.0 and WinRM 2.0)
Downloading the Integration Pack
Registering and Deploying the Integration Pack
After you download the integration pack file, you can register it with the Opalis Management Server and then deploy it to one or more action servers or clients. For more information abouthow to install integration packs, see the "Deploying Hotfixes and Integration Packs" section of the Opalis Integration Server Administrator Guide.
To register and deploy the integration pack
Copy the IP_SystemCenterDataProtectionManager_1.0.OIP integration pack file to the Opalis Integration Server computer.
Click Start, point to Programs, point to Opalis Software, and then click Opalis Integration Server. Right-click Deployment Manager, and then click Run as Administrator.
In the left pane of the Deployment Manager, expand Management Server. Right-click Integration Packs, and then click Register IP with the Management Server.
In the Integration Pack or Hotfix Selection window, click Add. Locate and select the IP_SystemCenterDataProtectionManager_1.0.OIP file that you copied in step 1. Click Next.
Click Finish. The Log Entries pane displays a confirmation message when the integration pack is successfully registered.
In the left pane, right-click Integration Packs, and then click Deploy IP to Action Server or Client. Click Opalis Integration Pack for Microsoft System Center Data Protection Manager, and then click Next.
Click the action server or client computer on which you want to deploy the integration pack, click Add, and then click Next.
Select the Installation Configuration options that apply to this deployment, and then click Next.
Click Finish. The Log Entries pane displays a confirmation message when the integration pack is successfully deployed.
Windows Management Framework
The Integration Pack for System Center Data Protection Manager uses Windows PowerShell remoting on the Opalis Client and on the integration server and on the Data Protection Manager server. Perform the following tasks on the Opalis Client and Integration Server and on the Data Protection Manager server before you configure the Data Protection Manager connection in the Opalis client.
To confirm the Windows Management Framework prerequisites
Confirm that you have Windows PowerShell 2.0 installed on the Opalis Client and Integration 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 (https://go.microsoft.com/fwlink/?linkID=193574).
Confirm that you have Windows Remote Management 2.0 (WinRM 2.0) installed and configured on the Opalis Client and Integration 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.
For more information abouthow to install and configure WinRM 2.0, see Installation and Configuration for Windows Remote Management (https://go.microsoft.com/fwlink/?linkID=171111).
To enable Windows Remote Management Trusted Hosts
On the Opalis Client and Integration Server, open the Local Group Policy Editor. To do this, click Start, click Run, type gpedit.msc, and then click OK.
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.
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 (https://go.microsoft.com/fwlink/?linkID=113394).
To enable or confirm remote connection settings in Windows PowerShell
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 Opalis client computer to receive Windows PowerShell remote commands that are sent by the Opalis Integration 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.
Start Windows PowerShell with the "Run as administrator" option.
Type System Drive**:\PS>enable-psremoting**
You can use WS-Management quotas in Windows PowerShell remoting to protect the Opalis 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 (https://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
In the Opalis Integration Server Client, click the Options menu, and then select System Center Data Protection Manager.
In the Data Protection Manager dialog box, on the Configurations tab, click Add to begin the connection setup.
In the Name box, type the name of the Data Protection Manager computer that you want to connect to with this integration.
In the Type box, click the ellipsis button (...), and then click PowerShell Remoting.
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.
Setting up the System Center Data Protection Manager Workflows
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 Objects for links to configuration instructions for the objects in this integration.