Cloud and Datacenter Management Blog

Microsoft Hybrid Cloud blogsite about Management

Leave a comment

#Microsoft System Center DPM 2019 and #Azure Backup

Microsoft System Center Data Protection Manager 2019 (DPM)

In a Earlier blogpost I wrote about Backup – Restore – DR Strategy in a fast changing world

Microsoft Products for Backup – Restore -DR, we have:

  1. Microsoft System Center Data Protection Manager
  2. Microsoft Azure Backup
  3. Microsoft Azure Site Recovery (DR)

1. Microsoft System Center Data Protection Manager (DPM)

You can install Microsoft SCDPM on different solutions, like:

  • As a physical standalone server
  • As a Hyper-V virtual machine
  • As a Windows virtual machine in VMWare
  • As an Azure virtual machine

If you don’t want to manage hardware like a physical Server, you can virtualize your DPM Server on-Premises on Hyper-V or VMware but you can also install DPM into the Cloud as an Azure VM.

Here you can read What’s New in System Center DPM 2019

Before you begin you should know what Microsoft System Center Data Protection Manager support and can protect by Backup. Here you find the highlights.

For Customers there are different installation scenarios possible :

  • You already have DPM Installed for years but you have to renew the hardware.
  • A complete New Installation of System Center Data Protection Manager 2019
  • Upgrade existing System Center DPM solution.

For the first bulletpoint, when you behind with Upgrading to the latest System Center DPM 2019 and you are still using DPM 2012 R2 for example with a SQL 2012 Database on old hardware, you have to follow a work flow.
When you installed Windows Server 2019 on your new hardware, you have to install DPM 2012 R2 and the same SQL version as before and then restore the latest DPM 2012 R2 database of your old hardware. When that’s done you can proceed with upgrading to DPM 2016 and with the right SQL version. You can’t upgrade from DPM 2012 R2 straight to DPM 2019. Here you can read more about Upgrading your System Center DPM Solution

The Second bullitpoint is installing a brand new Windows Server 2019 with System Center Data Protection Manager on new hardware or on a Virtual Machine. Here you find the Prerequisites and the installation on Microsoft Docs.

He wrote this blogpost which can help you out with the installation of System Center DPM 2019.

The third bullitpoint, is upgrading your existing DPM Backup Solution. Important is that you have a Backup of the DPM database on a other Server or storage then the Server your are going to Upgrade. You must have a rollback scenario if something went wrong. Read more about Upgrade path of System Center DPM

2. Microsoft Azure Backup

Use Azure Backup to protect the data for on-premises servers, virtual machines, virtualized workloads, SQL server, SharePoint server, and more. Because this is a Microsoft Cloud Service, you don’t have to buy expensive hardware like Physical Servers, Storage, Tape Library, you just pay for what you are using in Azure, Here you find the Microsoft Azure Calculator to calculate your Backup costs.

First you have to create a Recovery Services Vault :

Click on Review + Create a Recovery Services Vault.

Security features to help protect cloud workloads that use Azure Backup

When you Click on Create, the Microsoft Azure Recovery Services Vault will be made.
I already made a Azure Recovery Services Vault.

Overview of the Azure Recovery Services Vault.

In the following print screen shots you can see the Azure Backup Options :

You can backup of course Azure Virtual Machines.

You can Backup SQL Server in a Azure VM

You can Backup Azure FileShares. ( Preview)

You can Backup AzureStack workloads

You can backup On-premises workloads.

Azure Backup Policies to set different policies for the right Backup Job

Example of creating a Backup Policy with retensions

Here you see the backup en snapshots of an Azure Virtual Machine.

When you start with Microsoft Azure backup, begin with reading the backup Documentation here

3. Microsoft Azure Site Recovery (DR)

Site Recovery helps ensure business continuity by keeping business apps and workloads running during outages. Site Recovery replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary location. When an outage occurs at your primary site, you fail over to secondary location, and access apps from there. After the primary location is running again, you can fail back to it.

Here you can read everything about Azure Site Recovery (ASR)

Hope this Backup – Restore – DR Microsoft Overview is helpful for you and your Business.
Cheers @JamesvandenBerg 😉

Leave a comment

Backup – Restore – DR strategy in a Fast changing World #Data #Management

The world of data is moving and changing a lot with new IT technologies coming up like leaves on a tree.
Data is everywhere, on Servers, workstations, BYOD Devices in the Cloud but how do you keep your data save and protected for your business today and in the future? There are a lot of reasons why you should Backup your data :

  • One of your employees accidentally deleted important files for example.
  • Your data got compromised by a virus.
  • Your Server crashed
  • You have to save your data for a period of time by Law
  •  And there will be more reasons why you should do backup…………….

A lot of Enterprise organizations are moving to the Cloud with workloads for the Business, but how is your Backup and Disaster Recovery managed today? A lot of data transitions are made but what if your Backup and Disaster Recovery solution is out dated or reaching end of Life? You can have a lot of Questions like :

  • What data should I backup?
  • Should I just upgrade the Backup Solution?
  • How can I make my Data Management Backup -DR Solution Cheaper and ready for the future?
  • How can I make my new Backup-DR Solution independent? ( Vendor Lockin)

And there will be more questions when you are in this scenario where you have to renew your Backup – DR Solution.
Here we have the following Great Backup Solution from 2014 :

Offsite Microsoft DPM Backup Solution since 2014

Here we have 3 System Center Data Protection Manager Backup Pods with a Tape library and One DPM pod connected with a Microsoft Azure Backup Vault in the Cloud. You do the Security updates and the Rollups for Windows Server 2012 R2 and System Center Data Protection Manager 2012 to keep the Solution save and running.

Long Time Protection to Tape

DPM 2012 Server with direct attached Storage for Short time protection

The four DPM Backup Pods have the same Storage configuration for short time protection with a retention time of 15 days. After that Longtime protection is needed with Backup to tape and Backup to Microsoft Azure Backup Vault.
Since 2014 the Backup data is depending on these solution configurations.

Tape Management cost a lot of time and money

The fourth DPM Backup pod got a Azure Backup Vault in the Cloud to save Tape Management time.

DPM Backup to Microsoft Azure Cloud Backup Vault.

So this is the Start of the Journey to a New Data Management Backup – DR Solution transformation. The next Couple of weeks I will search for the different scenarios and solutions on the Internet and talk with the Community looking for Best Practices. I will do Polls on Social Media and a Serie of blogposts for the Data Management Backup – DR Solution to keep the business continuity.

Magic Quadrant for Data Center Backup and Recovery Solutions

Will it be a Cloud Backup – DR Solution?
Will it be a Hybrid Cloud Backup – DR Solution?
Everything in One Management Console?
Or More then One Backup -DR Solution for the right Job?

We will see what the journey will bring us based on Best Practices  😉

Leave a comment

Protect Virtual Machines with #SCVMM and Microsoft #Azure Site Recovery #HybridCloud


This Blogpost is about Deploying Microsoft Azure Site Recovery Manager to replicate and failover virtual machines on Hyper-V host servers that are located in System Center Virtual Machine Manager (VMM) clouds. It’s not Microsoft Hyper-V alone protection anymore, they have managed to protect VMWare and Physical Servers on Primary Sites too.

SCVMM to AzureSCVMM 2012 R2 to Azure



ASR Start Configs

Microsoft Azure Site Recovery Quick Start

On April 30, 2015. You could choose from the Quick Start page the following configurations :

  • Between an On-Premises VMM Site and Azure
  • Between Two On-Premises VMM Sites
  • Between an On-Premises Hyper-V Site and Azure
  • Between Two On-Premises VMWare Sites
  • Between Two On-Premises VMM Sites with SAN Array Replication.

I choose the first one, Microsoft System Center 2012 R2 Virtual Machine Manager RU6 and Microsoft Azure.
Before we begin :  information about Azure Site Recovery prerequisites and supported scenarios. 

When Your Microsoft Azure Subscription is Active and you have created a Storagepool in Azure, you can follow the next step.



Quick Create a Site Recovery Vault by giving it a Name and choose a Region


This is my Azure Site Recovery called HybridCloud

From here start the Quick Start Page of your Azure Site Recovery Vault by clicking on



Choose option

I Choose for SCVMM to Azure


Just Click on the links for a Registration key and the SCVMM Provider Software

ASR3ASR4Click on Install


Set the Proxy settings when you behind an Proxy Server


Browse to your downloaded Registration key of the Azure Site Recovery


Give the directory path for the Certificate


Registration software in SCVMM is completed


Here you see your SCVMM Server in the Azure Site Recovery Vault


In System Center 2012 R2 Virtual Machine Manager RU6 is ASR also Active

Next Step is to install the ASR Agent on Hyper-V :

ASR Agent 1a

Choose your Cache Location with Enough Storage

ASR Agent 2

Set your Proxy Settings and Click Next

ASR Agent 3

Click Install

ASR Agent 4

Click on Proceed to Registration

ASR Agent 5

Next Step in Virtual Machine Manager

If you don’t have your Virtual Machines in a SCVMM Cloud, you have to make Cloud(s) with Virtual Machine Manger.
The next step is to make a Cloud if you don’t have any.

Create Cloud


Give your Private Cloud a Name and Mark the Checkbox for ASR Protection


Select your Resources


Choose the right network


Click Next


Choose the right Storage pool(s) for this Cloud


Check the Summary and make your Private Cloud with SCVMM


When you have a VM in your Cloud Click on Manage Protection


Select the Replication settings


The SCVMM Cloud is in the Azure Recovery Site


Configure now the network Maps

MAP Network

Map the Azure VNET to your Local Network

When you protect the Virtual Machine you will see this in Azure :

Saving 1

And after this Hyper-V Replica to Azure is replicating the VM to the Microsoft Cloud :

Saving 2

When the Sync is completed we can make an Azure Recovery Plan :

Recovery Plan

In my Next blogpost I will write more about Microsoft Azure Recovery Plans.


The Latest (april 2015) Azure Team Blog information about Microsoft Azure Site Recovery you can find it here

Leave a comment

FREE WhitePaper : System Center 2012 R2 Configuration Manager – Disaster Recovery #sysctr #SCCM

System Center 2012 R2 Configuration Manager

Configuration Manager 2012 R2 disaster recovery is a complex process. It requires sufficient knowledge of the Configuration Manager Product & dependent components. This document describes the steps to recover a full Configuration Manager 2012 R2 hierarchy in case of disaster. This document also describes the steps to recovery either CAS or Primary sites as well as additional steps that Configuration Manager Administrators should follow in order to restore a Configuration Manager Hierarchy or Sites without data loss. This document also provides some helpful troubleshooting tips.
At a higher level, there are the following few steps described below to recover an entire hierarchy in the event of disaster. Please note that the steps are different for recovering an entire hierarchy and individual site servers such as CAS or Primary sites. Please refer to appropriate sections within this document to recover appropriate site servers. The approximate time noted below in each of the tasks may vary significantly as there are many factors involved when recovering an entire hierarchy so use this timing as an example ONLY.

  1. Collect CAS & Primary Site Information (~1 hour)  In this step, collect & document all the necessary information required from the existing hierarchy. This task should be followed regularly whenever there are updates/changes at the site level so that it will save time at the time of disaster recovery.
  2. Backup Sites – CAS & Primary (~3 hrs.)  This section describes backup options.
  3. Recover CAS Site (~3 to 48 hrs.) This section provides the steps to recover the CAS Site server. Global data can be recovered within 3-4 hours but for site data it can take up to 48 hours.
  4. Recover Primary Site(s) (~3 to 48 hrs.)  This section provides the steps to recover Primary Site servers. Global data can be recovered within 3-4 hours but for site data it can take up to 48 hours.  Recover from supplemental backups (~2 hrs.)
  5. This section describes the steps to recover the additional components of Configuration Manager.

You can download this Microsoft System Center 2012 R2 Configuration Manager WhitePaper here

Leave a comment

Rebuilding and Upgrading Microsoft Testlab and Start with #Hyperv Recovery Manager with #Azure #HybridCloud

With our testlab ICTCUMULUS we made awesome Microsoft solutions with Private and Public Cloud and learned a lot.
Here are some blogposts I made earlier :

Starting : From Microsoft Private Cloud to Hybrid Cloud Services

From Microsoft Private Cloud to Hybrid Cloud Services: Hyperv Clustering

From Microsoft Private Cloud to Hybrid Cloud Services : SCVMM 2012 R2

Making a NVGRE Gateway with System Center 2012 R2 Virtual Machine Manager

SQL 2014 Guest Cluster with Shared VHDX on Hyperv 2012 R2 Cluster for WAPack

Windows Azure Pack for Windows Server 2012 R2 Guide

Now it’s time for upgrading and rebuilding our Testlab ICTCUMULUS with extra memory and new Microsoft Hyper-v 2012 R2 Hypervisors.

Upgrade 1

Upgrade 2We have enough Memory now 😉

Here are the Visio drawings of ICT CUMULUS and we Changed some things like :

  • A Dedicated Hyper-V Cluster 2012 R2 for a virtual SQL 2014 Guest Cluster.
  • A Dedicated Switch for I-SCSI storage traffic.

Memory Upgrades


When we are ready with rebuilding ICTCUMULUS Testlab, we will start with Microsoft Azure Site Recovery Manager and my next blogpost:

Azure replication

Leave a comment

Migrate On-Premise Virtualized Workloads to Azure using Azure Site Recovery #Azure #Hyperv #DR #SCVMM



Here you can read more about Azure site Recovery on this blogpost of Microsoft Azure to migrate virtualized workloads to Azure to reduce downtime of production.

Leave a comment

UPDATED : Microsoft Azure Site Recovery deployment guides #Azure #Hyperv #SCVMM #HybridCloud

Azure replication

Deploy Microsoft Azure Site Recovery Manager to replicate and failover virtual machines on Hyper-V host servers that are located in System Center Virtual Machine Manager (VMM) clouds. You can set up replication and failover from one on-premises VMM server to another, or from an on-premises VMM server to Microsoft Azure. To perform the replication that the service orchestrates, VMM uses Hyper-V Replica, a replication mechanism that is built into Hyper-V in Windows Server 2012.

Here you find all the information you need for Microsoft Azure Site Recovery :

Transform your Datacenter