Hi,
Q1.2__SQL Cluster-with reporting service Installed or no it is recommended with separate instance for reporting server.
A2.2 -- You must have SQL reporting in order to install DPM. SQL Reporting server cannot be clustered, so it must be a standalone SQL instance to use for reporting.
Q2.2--For DPM Storage and Protection,
for example I have 10 VMs to Protect with DPM01 and DPM02
DPM01 will protect 5 VMs and DPM02 will protect 5 VMs.
but i have to calculate Storage requirement for 10 VMs for one dpm.
A2.2 - Yes, if you want cyclic protection for all 10 VM's then each DPM server must have storage in the storage pool to accommodate that. You can pick and choose what you want to add to secondary protection, maybe just critical VM's.
Q3.2 -- To Protect DPM and enabling Cyclic Protection., DPM02 agent will be installed on
DPM01 and DPM01 on DPM02.
That why DPM01 Storage will be equal to 10VMs as it is also protecting DPM02 Vms and all protcted VMs by DPM02 and Vice Verse.
A3.2- correct.
Q4.2 -- For SQL Server DBs.
DPM01 DB will be protected by DPM02 and DPM02 by DPM01.
if I am going well, what will be the failover process,
If DPM01 one goes offline.....
All load and protected VMs will be automatically transfer to DPM02 or no i have to do it manually
and DPM01 can be restored from DPM02? and what will be the procedure for Recovery of DPM01.
A4.2 - You can only install a single DPM agent on the SQL Cluster hosting the two DPM databases, so you will need to have one DPM server protect both DB's as primary protection, and the other DPM server can be the secondary DPM server. In case
DPM1 goes down, nothing is automatically switched - you must switch protection manually from the DPM2 server so the workloads protected by DPM1 continue to be protected by DPM2. After repairing DPM1 you can switch protection back.
Some useful links:
Back up DPM using a secondary server
Recover a backed up DPM server