Scenario SQL State VMM Server Recovery Steps State Single VMM SQL VMM Server Recover the failed VMM Library from a valid backup Library continues to continues to run source. server run crashes; good backup is available Single VMM SQL VMM Server All Library content (ISOs, VHDX, scripts, and so on) must Library continues to continues to run be repopulated or re-created. server run crashes; no good backup is available Active node SQL VMM Server The Library content and function will fail over to a of HA VMM continues to continues to run remaining node of the HA file-server cluster. Library run server crashes Integration Point Recovery As mentioned earlier, there are several additional points of integration within a complete Virtual Machine Manager implementation. These integration points include PXE servers, Windows Server Update Services (WSUS) servers and connectors to other System Center components. The following section specifically addresses recovery procedures and requirements for these elements. Distributed Key Management The requirement for implementing DKM for Virtual Machine Manager mitigates the need to separately ensure the availability and restoration of this key in a DR scenario. This is consistent for single-site or multisite implementations. Bare-Metal Provisioning If lost, the PXE Server supporting a Virtual Machine Manager site implementation must be restored using standard file-server recovery procedures, leveraging a known good backup source. In a multisite configuration, a PXE server must be deployed at every site at which provisioning is required. This increases the planning and effort that are required to recovery from a disaster scenario, because the preceding backup and recovery procedures and requirements must be implemented at each separate location. After recovery, each PXE server may require to be re-registered with the Virtual Machine Manager Management Server by using
Scenario SQL State VMM Server State Recovery Steps Single VMM Library server crashes; good backup is available SQL continues to run VMM Server continues to run Recover the failed VMM Library from a valid backup source. Single VMM Library server crashes; no good backup is available SQL continues to run VMM Server continues to run All Library content (ISOs, VHDX, scripts, and so on) must be repopulated or re-created. Active node of HA VMM Library server crashes SQL continues to run VMM Server continues to run The Library content and function will fail over to a remaining node of the HA file-server cluster. Integration Point Recovery As mentioned earlier, there are several additional points of integration within a complete Virtual Machine Manager implementation. These integration points include PXE servers, Windows Server Update Services (WSUS) servers and connectors to other System Center components. The following section specifically addresses recovery procedures and requirements for these elements. Distributed Key Management The requirement for implementing DKM for Virtual Machine Manager mitigates the need to separately ensure the availability and restoration of this key in a DR scenario. This is consistent for single-site or multisite implementations. Bare-Metal Provisioning If lost, the PXE Server supporting a Virtual Machine Manager site implementation must be restored using standard file-server recovery procedures, leveraging a known good backup source. In a multisite configuration, a PXE server must be deployed at every site at which provisioning is required. This increases the planning and effort that are required to recovery from a disaster scenario, because the preceding backup and recovery procedures and requirements must be implemented at each separate location. After recovery, each PXE server may require to be re-registered with the Virtual Machine Manager Management Server by using
IaaS%20Product%20Line%20Architecture%20Fabric%20Management%20Architecture%20Guide_v2_Download.docx