1

Key Points:

• Through using DPM, you will see if you have a failure, how would you recover

• DPM allows you to recover infrastructure due to failure in the datacenter

• DPM will help you provide Increased Service Levels, and decrease your RTO

• In this presentation, we will review System Center 2012 Data Protection Manager, along with how it works with the other System Center products including Orchestrator, Operations Manager, Virtual Machine Manager to ensure high availability of the cloud environment

• By using DPM you can protect your private cloud

2

3

Key points:

• System Center 2012 enables delivering IT as a Service between the App Owner and DC Admin personas that we defined.

• We have two personas: application owner, and the data center administrator

• Each have capabilities required to deliver a private cloud as well as leverage hybrid computing models

• For example, consider a self-service experience to enable your application owners to specify their service requirements; Let’s say the “consumer” trying to provision a SharePoint service.

• Understand the topology and architecture of the application service in question. An application deployed in cloud computing model is called a “service”. This would necessitate a “service model” that accurately binds the application’s architecture to the underlying resources where it will be hosted.

• The “service model” would be comprised of:

• Service definition information, deployed as “roles”. Roles are like DLLs, i.e. a collection of code with an entry point that runs in its own virtual machine

• Front end: e.g. load-balanced stateless web servers

• Middle worker tier: e.g. order processing, encoding

• Backend storage: e.g. SQL tables or files

• Service Configuration information

• Additionally, update domains, availability domains, and scale out rules

• You will need a set of process automation capabilities to break down this application provisioning request into the enterprise change requests that need to be implemented. This could include setting up the underlying infrastructure and then a set of application configuration/release requests that need to be tracked (and ideally implemented with orchestrated automation)

• Next you need a set of provisioning tools that actually configure and deploy the infrastructure and application layers.

• The underlying datacenter resources could be physical, virtual, private or public as per the requirements dictated by the application’s service model

• Once the application service is deployed, it would immediately need to be “discovered” and monitored for reporting and health tracking

• There you see how the System Center 2012 components offer these life cycle management capabilities in combination to help you deliver hybrid IT as a Service as per your organization’s requirements:

• App Controller 2012 would offer that self-service experience that allows your application owners manage their apps across private and public environments.

• Service Manager 2012 offers the standardized self-service catalog that defines “templates” for your applications and infrastructure.

• App Controller 2012, Virtual Machine Manager 2012, Service Manager 2012 and Operations Manager 2012 work together to maintain the service model through the application service life cycle.

• Orchestrator 2012 and Service Manager 2012 offer orchestrated automation for the process workflows required to drive your provisioning and monitoring tools

• Virtual Machine Manager 2012 and Configuration Manager 2012 can provision physical, virtual and cloud environments.

• Operations Manager 2012 monitors your application services end-to-end and offers deep application insight to help you deliver predictable SLA.

• Your datacenter resources could be deployed anywhere from physical boxes, to virtual, to private, to public with Windows Server/ Hyper-V and Windows Azure

• However, to get to this agile self-service end-state, you will have to start with abstracting your infrastructure and allocating it appropriately so that your business units can deploy and manage their applications on top.

How does System Center 2012 get you to this point where you can deliver IT as a Service?

1. Application Management: Deploying and operating your business applications

2. Service Delivery & Automation: Standardizing and automating service and resource provisioning; managing change and access controls

3. Infrastructure management: Deploying and operating all the underlying infrastructure on which your business applications and services run

4

Key points:

• DPM can be used to back-up and recover a wide range of Microsoft products. We have a few data points that we can leverage here as to how we have optimized our back-up and recovery solution:

For SQL: • We support any point in time recovery, we provide self service restores

• Up to 2000 SQL Databases can be protected using a single DPM server

• The change tracking is super storage efficient

For Exchange:

• We provide protection against total loss due to logical corruptions

• We can preserve data for point in time restores

For SharePoint:

• You can protect at a farm level, but can do granular level recovery. Recovery of a document takes only a few seconds now.

• New databases are automatically detected and protected

For Hyper-V:

• You can do item level recovery of VMs

• You can back-up the entire host

• You can seamlessly protect live migration of VMs

• DPM can back-up data from all these sources once every 15 minutes to a Tape or a Disk

• You can save this back-up in an offsite location again on a tape or a disk or in the cloud

5

7

Key Points:

There are three main areas that you can focus on as you talk about Protecting the private cloud

1. How our back-up and recovery solution is optimized for Microsoft Applications and for

Windows. You can talk about how Data protection Manager can do item level recovery in

SharePoint and Hyper-V in a matter of seconds. You can talk about extended support for any

Windows application that relies on VSS writer and our investments in support of Non Microsoft

products through customizable XML files.

2. Our back up and recovery story is ready for large enterprises. You can quote MSIT as an

example with us running 80 DPM servers running backing up 3.5 Peta bytes of data. We support

offsite back-up to cloud through partners like IronMountain. For machines that lie outside the

domain, which is a very common scenario, we support certificate based protection. We also have

protection of clustered work loads and we will see more of it in the next couple of slides. You

can also talk about having co-location where we can back-up more than one application side by

side on the same tape.

3. This is also a good place to reiterate how our System Center products work together to give a

good complete solution. Data Protection Manager integrates with Operations Manager and you

can monitor your back-up and recovery from the same console you use to monitor your

Application, your fabric and your infrastructure. If you have several DPM servers running, you can

view them all from a single pane of glass and the user can see only the information that he has

access to.

8

9

Key Points:

• We talk about the high-availability of resources in this slide.

• Our cluster failover solution in Windows Server 2008 R2 has ensured that servers are up and running all the time.

• If a specific node in the cluster fails over, another node automatically fired back up and we can then use VMM to bring the node back-up and things continue to work again.

• If the entire cluster goes down, we can recover the entire cluster and get it running on another physical machine till we bring the original cluster back-up.

• Thus we help ensure high availability within the Datacenter without any downtime.

5/17/2012

10

Key Points:

• There are many new automation capabilities in SC 2012.

• In addition to providing deep monitoring and diagnostic insight for your IT infrastructure, SC 2012 provides integration and automation capabilities which can be configured to support many different incident or error remediation scenarios.

• Orchestrator is the component providing automated runbook capabilities combined with connectivity to other management components (System Center and third party) with the use of Integration Packs.

• In this example we’re going to automatically migrate a SQL server database. After investigating the alert in Operations Manager, we should migrate the database on that VM to another SQL Server instance.

• As you can see in this screen, Orchestrator's runbook designer can be used to create automated workflows that perform several tasks while integrating with all the necessary management components. The icons and the interface are very user friendly so it’s easy to see what activities will happen and in what order.

Detailed flow for this automation example

• The SQL migration runbook can either be started from within the Orchestrator console, or triggered by Orchestrator pulling the alert information from Operations Manager.

• Once the process is kicked off, Orchestrator communicates with VMM, and then VMM checks for valid names of the source and destination servers, plus the database to be migrated.

• Next, Orchestrator communicates with Service Manager to create an incident ID associated with the database migration ensuring there’s a record of this process.

• At this point, Data Protection Manager is pulled into process to create a recovery point for the database and exports it to a designated network share.

• Now that the database is backed up, Orchestrator is going to kick-off a PowerShell script to run the actual database migration to the new SQL server VM.

• Once the migration is complete, Operations Manager will be put into maintenance mode for the source server we migrated the database from so that when VMM shuts it down, an error will not be thrown.

• Once the source VM is shut down the associated incident logged in SM will resolve.

This is just one example of the powerful integrated automation capabilities being delivered with SC 2012.

Other candidates for automation are:

• Incident Response

• Provisioning

• Disaster Recovery

• Compliance Requirements

• Change Control

• Capacity Management 11

12

13

14