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
However, if a signican
t amount of time has passed between the original order and the expansion, it is likely that image versions and/or
rmware versions may be dierent. Before beginning the expansion deployment, it will then be necessary to bring the existing environment
up to a solution release level that is compatible with the images provided on the expansion chassis. The Patch and Update (P&U) process
can be used to update the solution stack.
For more information about P&U, go to the Dell support website at
support.dell.com. Click Choose from all Products > Servers, Storage,
& Ne
tworking
> Engineering Solutions > Microsoft Cloud Solutions > Dell Hybrid Cloud System for Microsoft. P&U packages and
documen
tation are released to that site when available.
NOTE
: Because they require imaging before they are delivered, compute nodes and backup nodes are shipped from the Dell
Integration Centers. All other components ship directly to the customer without any customization.
Physical installation
Install the compute chassis into the rack unit above the upper-most chassis that is currently deployed in the solution. Run the power cables
fr
om the chassis to the PDU, and connect the 10GbE ports on each C6320 server to the appropriate ports on the Dell Networking S4048-
ON switches.
Deploying compute expansion nodes
The Deployment user interface remains installed on the console VM (<
prex>CON01) and is used to start the DeployDriver for compute
expansion. Consult with your Dell technical support representative to nd out how to deploy compute expansion nodes for your
implementation of the Dell Hybrid Cloud System for Microsoft.
NOTE: Compute expansion is implemented by Dell Services.
Adding another server to backup infrastructure
You can add DPM backup servers to an existing Dell Hybrid Cloud System for Microsoft backup infrastructure. Deployment of the backup
serv
ers is implemented by Dell Services. You can expand up to three backup servers.
After you run the BackupDeployDriver script, run the Complete-BackupDeployment runbook. You do not have to run the Protect-
ManagementComponents runbook.
Then, you may have to run P&U to ensure that the latest updates are applied, and that the stamp and backup infrastructure are at the
same version.
Use the following guidance to determine if and when a P&U run is required:
Table 41. Conditions for P&U run
Conditions P&U run required?
Stamp is at same version as the new backup host. A P&U run is not required after you add the backup host.
Stamp has a later version than the new backup host. Run a required P&U after you add the backup host.
NOTE
: Starting with Update 1611, you can target P&U to
run against only the new backup hosts. For more
information, see the current version of the
DHCS Patch
and Update Framework
document at the location where
you nd approved updates.
New backup host has a later version than the stamp. Before
you add the backup host, run a required P&U to update the
stamp to the same version as the new host.
Appendix A Expanding the stamp 141