Sunday, October 22, 2017

Joining the VM to a domain

After the VM is created, wait for it to boot up and reach the Running state, and then connect to the VM over RDP with the username and password that you provided at the time of VM creation.

When you are logged in, join the machine to the same domain that the yet-to-be-protected workloads are joined to. This trust relationship allows DPM to discover the servers easily and makes the backup agent installation process simple. Alternatively, you can use certificate-based authentication and manual installation of the agent.


Adding backup storage
All backup products need storage media to keep the backup data and the recovery points, and DPM is no exception. There are two broad types of storage media supported by DPM: disk and tape. When it is deployed on-premises or in your datacenter, there are multiple ways to make disk storage available to DPM:
Direct attached storage (DAS)
iSCSI disks
VHDs on an SMB Share
Fiber channel attached SAN storage

However, when DPM is running as a VM in Azure, the only type of storage that can be used is a VHD. The VHDs that are created and attached to the VM together form the backup storage pool for DPM consumption. The following steps walk you through the process of creating a VHD using the Azure management portal and attaching it to the DPM VM.

1. Go to http://manage.windowsazure.com and log in to the Azure management portal.

2. In the left pane, click the Virtual Machines tab.

3. From the list of VMs displayed, select the VM that will host DPM.

4. From the menu bar at the bottom, click Attach and select Attach Empty Disk.

5. A dialog box with details about the disk that needs to be attached appears. Enter a file name and the size of the disk.

6.Azure creates the empty disk and attaches it to the VM. When the operation iscomplete, use the Disk Management tool in the guest to see the disk. Right-click thedisk and select Online. Later, you will configure this disk as backup storage for DPM.

Source of Information : Microsoft System Center

No comments: