###BeginCaseStudy###
Case Study: 3
Northwind Traders
Overview
Northwind Traders is an IT services and hosting provider.
Northwind Traders has two main data centers in North America. The data centers are located
in the same city. The data centers connect to each other by using high-bandwidth, low-latency
WAN links. Each data center connects directly to the Internet.
Northwind Traders also has a remote office in Asia that connects to both of the North
American data centers by using a WAN link. The Asian office has 30 multipurpose servers.
Each North American data center contains two separate network segments. One network
segment is used to host the internal servers of Northwind Traders. The other network segment
is used for the hosted customer environments.
Existing Environment
Active Directory
The network contains an Active Directory forest named northwindtraders.com. The forest
contains a single domain. All servers run Windows Server 2012 R2.
Server Environment
The network has the following technologies deployed:
• Service Provider Foundation
• Windows Azure Pack for Windows Server
• System Center 2012 R2 Virtual Machine Manager (VMM)
• An Active Directory Rights Management Services (AD RMS)
cluster
• An Active Directory Certificate Services (AD CS) enterprise
certification authority (CA)
All newly deployed servers will include the following components:
• Dual 10-GbE Remote Direct Memory Access (RDMA)-capable
network adapters
• Dual 1-GbE network adapters
• 128 GB of RAM
Requirements
Business Goals
Northwind Traders will provide hosting services to two customers named Customer1 and
Customer2. The network of each customer is configured as shown in the following table.
Planned Changes
Northwind Traders plans to implement the following changes:
• Deploy System Center 2012 R2 Operations Manager.
• Deploy Windows Server 2012 R2 iSCSI and SMB-based
storage.
• Implement Hyper-V Recovery Manager to protect virtual
machines.
• Deploy a certificate revocation list (CRL) distribution point
(CDP) on the internal network.
• For Customer 1, install server authentication certificates issued
by the CA of Northwind Traders on the virtual machine in the hosting
networks.
General Requirements
Northwind Traders identifies the following requirements:
• Storage traffic must use dedicated adapters.
• All storage and network traffic must be load balanced.
• The amount of network traffic between the internal network
and the hosting network must be minimized.
• The publication of CRLs to CDPs must be automatic.
• Each customer must use dedicated Hyper-V hosts.
• Administrative effort must be minimized, whenever possible.
• All servers and networks must be monitored by using
Operations Manager.
• Anonymous access to internal file shares from the hosting
network must be prohibited.
• All Hyper-V hosts must use Cluster Shared Volume (CSV)
shared storage to host virtual machines.
• All Hyper-V storage and network traffic must remain available
if single network adapter fails.
• The Hyper-V hosts connected to the SMB-based storage must
be able to make use of the RDMA technology.
• The number of servers and ports in the hosting environment to
which the customer has access must be minimized.
Customer1 Requirements
Northwind Traders identifies the following requirements for Customer1:
• Customer1 must use SMB-based storage exclusively.
• Customer1 must use App Controller to manage hosted virtual
machines.
• The virtual machines of Customer1 must be recoverable if a
single data center fails.
• Customer1 must be able to delegate self-service roles in its
hosted environment to its users.
• Customer1 must be able to check for the revocation of
certificates issued by the CA of Northwind Traders.
• The users of Customer1 must be able to obtain use licenses for
documents protected by the AD RMS of Northwind Traders.
• Certificates issued to the virtual machines of Customer1 that
reside on the hosted networks must be renewed automatically.
Customer2 Requirements
Northwind Traders identifies the following requirements for Customer2:
• Customer2 must use iSCSI-based storage exclusively.
• All of the virtual machines of Customer2 must be migrated by
using a SAN transfer.
• None of the metadata from the virtual machines of Customer2
must be stored in Windows Azure.
• The network configuration of the Hyper-V hosts for Customer2
must be controlled by using logical switches.
• The only VMM network port profiles and classifications
allowed by Customer2 must be low-bandwidth, medium-bandwidth, or
high-bandwidth.
• The users at Northwind Traders must be able to obtain use
licenses for documents protected by the AD RMS cluster of
Customer2. Customer2 plans to decommission its AD RMS cluster
during the next year.
###EndCaseStudy###
DRAG DROP
You need to implement a Hyper-V Recovery Manager solution in the hosting environment of
Northwind Traders.
Which four actions should you perform in sequence? To answer, move the appropriate actions from
the list of actions to the answer area and arrange them in the correct order.
Answer: See the explanation
Explanation:
-From the Windows Azure Management Portal, create a Hyper-V Recovery Manager vault.
-From the Windows Azure Management Portal, upload a .cer file.
-On the VMM server, download and install the Hyper-V Recovery Manager Provider.
-From the Virtual Machine Manager console, select the Synchronize cloud data with the vault option.
4th step :
“send configuration data about this cloud to the windows azure hyper-v recovery manager”
“http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx”
synchronize cloud data is an option of provider installation (3rd step)
I agree with this answer, however it is difficult to confirm. If you are correct, then it implies you checked the ‘synchronize cloud data’ box during installation on the VMM server. Also, the answers specify installing Recovery Manager Provider on the VMM *Server*, and then says “synchronize cloud data with the vault” from Virtual Machine Manager *Console*. I do not think you would do that step from the Console, so 4th step should be as you said “Send configuration data about this cloud to the windows azuer hyper-v recover manager”.
@ OSA/Billy – Agreed that the option to “synchronize cloud data with the vault” is a part of Provider installation and not done from VMM Console
Step I – 3 are correct
OSA has provided correct answer to step 4
Billy here is a good article explaining complete procedure (Page 2 explains/confirms step 4)
To protect a private cloud, you must right-click on the private cloud within the Virtual Machine Manager console (assuming the cloud isn’t already being synchronized) and select the Properties command from the shortcut menu. When the cloud’s properties sheet appears, go to the General tab and select the Send Configuration Data About this Cloud to the Azure Hyper-V Recovery Manager checkbox, and click OK.
https://redmondmag.com/Articles/2014/12/01/Azure-Recovery.aspx?Page=1
Good video (about 45 min mark is related to this question but whole video is instructive and informative)
https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/DCIM-B322#fbid=?hashlink=fbid
– From the Windows Azure Management Portal, create a Hyper-V Recovery Manager vault.
– From the Windows Azure Management Portal, upload a .cer file
– On the VMM server, download and install the Hyper-V Recovery Manager Provider.
– “send configuration data about this cloud to the windows azure hyper-v recovery manager”
http://www.tech-coffee.net/make-vmm-cloud-failover-hyper-v-recovery-manager-azure/
According to: http://www.tech-coffee.net/make-vmm-cloud-failover-hyper-v-recovery-manager-azure/
I think the right answer is:
– From the Windows Azure Management Portal, create a Hyper-V Recovery Manager vault.
– From the Windows Azure Management Portal, upload a .cer file
– On the VMM server, download and install the Hyper-V Recovery Manager Provider.
– From the Virtual Machine Manager console, select the Synchronize cloud data with the vault option.
The option “send configuration data about this cloud to the windows azure hyper-v recovery manager” is used when you create private clouds and does not make sense in this case.
I Agree with FSM
Please refer to the link below :
http://kristiannese.blogspot.co.za/2013/12/how-to-setup-hyper-v-recovery-manager.html
“Synchronize cloud data…” is used during the Azure Recovery setup when installing the provider on VMM. This is used on the recovery cloud setup.
The “Send Configuration data….” option is used when you create the protected cloud.
This comes after creating the recovery cloud. This could be step 5
http://www.tech-coffee.net/make-vmm-cloud-failover-hyper-v-recovery-manager-azure/
– Create fault
– Upload CER
– Install Provider
– Synchronize cloud data
i believe the correct actions in order are:
– From the Windows Azure Management Portal, create a Hyper-V Recovery Manager vault.
– From the Windows Azure Management Portal, upload a .cer file
– On the VMM server, download and install the Hyper-V Recovery Manager Provider.
– From the Virtual Machine Manager console, enable the “send configuration data about this cloud to the windows azure hyper-v recovery manager” option
http://kristiannese.blogspot.co.ke/2013/12/how-to-setup-hyper-v-recovery-manager.html
—
refer to this:
“~VMM server prerequisites:
· If you are running one VMM server, it will need two clouds configured (where the DR will occur between the clouds). If you have two or more VMM servers, at least one cloud should be configured on the source VMM server you want to protect, and one cloud on the destination VMM server that you will use for recover. The primary cloud you want to protect must contain the following:
o One or more VMM host groups
o One or more Hyper-V hosts servers in each host group
o One or more Hyper-V virtual machines on each Hyper-V host~”
—
so you do need to set up that cloud and enable the “send