70-247 Series: Part 9

Installing Orchestrator

In this blog post I will cover the steps required to install Orchestrator in a HA configuration. The following servers will be deployed:

ORCMGMT – Orchestrator Management Server

ORC1 – Runbook Server and Web Console Server

ORC2 – Runbook Server and Web Console Server

The Web Console component can be load balanced, the Runbook server component does not require load-balancing.

The steps I will complete to do this are:

1. Create Orchestrator Database Instance (Already completed outside of this procedure, you can use an existing instance if you wish)
2. Create Orchestrator Service Account
3. Create Orchestrator Users Group
4. Install Management Server
5. Install prerequisites
6. Run setup
7. Install combined Runbook Server and Web Service
   1. Install prerequisites
   2. Install Runbook server
   3. Install Web console
8. Repeat step 7 to install second Runbook Server and Web Service
9. Verify Runbook Servers

Alright, let’s get started.

Create Service Account

No permissions are required, the logon as a service right is assigned by the Orchestrator installation wizard.

Create Orchestrator Users Group

Install Orchestrator Management Server

Install Pre-requisites

The required prerequisites are:

.Net Framework 4.0

.Net Framework 3.5.1

Run Setup

This server will serve as a Management server.

See below, only the Management server is selected. The other roles will be installed on separate servers and the web service will be load balanced.

The remaining steps displayed below do not require any important configuration steps so I have reduced the size of the screenshots.

Install First Orchestrator Runbook Server and Web Service Server

Install Prerequisites

The required prerequisites are:

.Net Framework 4.0

.Net Framework 3.5.1 and IIS

Install Runbook Server

 

All future components added will use the existing database.

 

Install Web Service Server

 

 

Install Second Runbook Server and Web Service Server

The process for installing the second server is identical to installing the first server.

Verify Runbook Servers

Once all the Runbook servers are installed, it's a good idea to verify them in the Runbook Designer. You can install the Runbook Designer on any Server or Client. In this instance, I have installed it on the Management Server and I will also install it on a client.

70-247 Series: Part 8

Installing Data Protection Manager

System Requirements

Data Protection Manager will attempt to install pre-requisite software during installation. In cases where this fails, or to install pre-requisite software manually, the list of requirements is:

• At least 4GB RAM
• Windows Server 2008 R2 SP1 (Other versions can be used, but updates may be required)
• 64-Bit SQL Server Instance (more details below)
• The following software:
• Microsoft .Net Framework 3.5 SP1
• Microsoft Visual C++ 2008 Redistributable
• PowerShell 2.0
• Windows Installer 4.5
• Windows Single Instance Store (SIS)
• Microsoft Application Error Reporting

Protected Servers also may require software and/or hotfixes:

• File Servers
  • 2008 R2 - KB977381
• Hyper-V
  • 2008 R2 Non-clustered - KB975354
  • 2008 R2 Clustered - KB975921 and KB975354
• All protected computers will also require Microsoft .Net Framework 3.5 SP1 and Windows Server Backup installed (for 2008+ Servers)

Preparing the Database

A local or remote instance of SQL Server can be used with DPM. When specifying remote instance, a Domain Account is used to connect to the database. This account must be a Local Administrator and a member of the sysadmin role in the remote SQL instance. The Local Administrator privilege can be removed after installation.

A clustered instance of SQL Server cannot be used because SQL Server Reporting Services is required on the SQL Instance

Installation of Pre-requisites

Because the server I am installing DPM on has an Internet connection, I will let the installer configure the prerequisites for me. If the computer was offline, I would need to use this procedure: http://technet.microsoft.com/en-us/library/hh758058.aspx

Installation of DPM

Configuration of DPM

One of the first configuration tasks is to add Disks to the Storage Pool, to do this, attach disks to the DPM server and bring them online. Do not format the drive. Then Add disks using the Management workspace within DPM.

DPM requires disks that are dedicated to data protection. DPM can be installed on the OS disk or on a separate disk, but the disk that DPM is installed on, cannot be used to store protected volumes.

Disks added to Storage Pools will be changed to dynamic disks

Install and configure protection agents on each computer that will be protected

Configure protection groups

A protection group is a collection of servers that share the same protection configuration. In the example below, I am going to create a Protection Group for our Domain Controllers and add the first Domain Controller to that protection group.