Administrator Guide
Table Of Contents
- Dell Hybrid Cloud System for Microsoft Cloud Platform System Standard Version 1.5 Administrators Guide based on release 1803
- Overview
- Administration
- What to do first
- Next steps
- Managing Dell Hybrid Cloud System for Microsoft
- Creating tenant VM networks
- Adding tenant VM networks to the cloud
- Flagging the operating system VHD in the VM templates
- Enabling guest-specified IP addresses in VMM
- Creating additional tenant storage shares
- Using Windows Azure Pack
- Default Windows Azure Pack configuration
- Before you go into production
- Setting up tenant portal access on an isolated network
- Replacing self-signed certificates
- Disabling the tenant AuthSite and the admin Windows AuthSite websites
- Updating to a Security Token Service and re-establishing trust
- How to open the management portal for administrators
- How to open the management portal for tenants
- Offering services to tenants
- Optional configuration
- Automating tasks for efficiency
- Windows Azure Pack API reference content for developers
- Configuring disaster recovery protection
- Operations
- Monitoring
- Backup and recovery
- Onboard to Azure Backup
- Default backup schedule and retention policy
- DPM protection groups
- Disable machine account password rotation on management VMs
- Protecting tenant VMs
- Recovering VMs and databases—high level
- Recovering from management component failures
- Recovering a tenant VM
- Recovering DPM from DPM failures
- Adding extra disks to DPM
- Monitoring DPM
- Using the Dell Hybrid Cloud System for Microsoft data consistency runbooks
- Updating the Dell Hybrid Cloud System for Microsoft
- Shutting down and starting up the stamp
- Security
- Appendix A Expanding the stamp
- Appendix B Performing a factory reset
- Appendix C Retrieving cluster names, host names, and IP addresses
- Appendix D Ports and protocols
Recovering SMA
SMA reduces an administrator’s burden by providing the ability to automate many manual tasks. If all options for recovery from application
f
ailures are exhausted, you can recover SMA data to restore functionality.
Recovering the SMA database
1 From the VMM console, shut down the VM that is hosting SMA (<
Prex
>APA01).
2 Use the steps in Recovering a database to its original location to recover the following SMA database. To minimize data loss, select the
la
test recovery point.
Table 26. SMA Database Name
SQL Server Instance Database Name
SQLIN02 SMA
3 From the VMM console, restart the APA01 VM.
4 Detect and repair any data consistency issues by following the required steps in How to use data consistency runbooks
.
Recovering the APA VM—with SMA, SPF
1 In the VMM console, in the VMs and Services workspace, use the Connect via Console option to log on to the <
Prex
>APA01 VM.
2 Stop the Runbook service—rbsvc. To do this, start a Windows PowerShell session, and then run the following command:
Stop-Service rbsvc
The service can take up to 20 minutes to stop. Wait for the service to stop before you continue to the next step.
3 From the VMM console, shut down the VM.
4 Use the steps in Recovering a VM to its original location to recover the VM. To minimize data loss, select the latest recovery point.
5 From the VMM console, start the VM.
The Runbook service starts automatically.
6 Detect and repair any data consistency issues by following the steps in How to use data consistency runbooks.
Recovering SPF
If all options of recovering from SPF failures are exhausted, you can use DPM to recover SPF data to restore SPF functionality.
To recover the SPF database:
1 From the VMM console, shut down the VM that is hosting SPF (<
Prex
>APA01).
2 Use the steps in Recovering a database to its original location to recover the following SPF database.
Table 27. SPF Database Name
SQL Server Instance Database Name
SQLIN02 SCSPFDB
3 From the VMM console, start the VM.
4 Detect and repair any data consistency issues by following the required steps in How to use data consistency runbooks.
Operations 79