advertisement
Appendix A: Expanding the stamp
When customers initially purchase the Dell Hybrid Cloud System for Microsoft, the solution may be configured with fewer than the maximum number of compute nodes, storage JBODs, network switches, or backup hosts. The following figure outlines the components that may be ordered to expand the scale and/or functionality of the solution after it has already been deployed. This section outlines procedures for adding these components and integrating them into the solution.
Figure 53. Expansion of Dell Hybrid Cloud System for Microsoft
Topics:
•
•
Adding another server to backup infrastructure
Compute expansion workflow
The number of compute nodes in the solution can scale from a single chassis (with four PowerEdge C6320 servers) up to four chassis (for a total of sixteen servers). The unit of scalability is a complete chassis, so nodes must be added four at a time. The chassis must go through the Dell Integration Center and be pre-configured and imaged in the same manner as the original nodes.
134 Appendix A: Expanding the stamp
However, if a significant amount of time has passed between the original order and the expansion, it is likely that image versions and/or firmware versions may be different. 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 support.dell.com>Servers, Storage and Networking >Engineered Solutions >Dell Hybrid Cloud
System for Microsoft . P&U packages and documentation will be 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 from 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 (< prefix >CON01) and is used to start the DeployDriver for compute expansion. Consult with your Dell technical support representative to find 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 servers 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 40. Conditions for P&U run
Conditions
Stamp is at same version as the new backup host.
Stamp has a later version than the new backup host.
New backup host has a later version than the stamp.
P&U run required?
A P&U run is not required after you add the backup host.
Run a required P&U after you add the backup host.
Before you add the backup host, run a required P&U to update the stamp to the same version as the new host.
To check the Microsoft update version on a new node, open the file C:\Program Files\Microsoft Cloud Solutions\Version.xml on the host.
To check the Microsoft update version on the stamp, see
How to check which update package is installed .
Appendix A: Expanding the stamp 135
advertisement
Related manuals
advertisement
Table of contents
- 3 Dell Hybrid Cloud System for Microsoft Cloud Platform System (CPS) Standard Version 1.1 Administrators Guide, based on release 1603
- 7 Overview
- 7 What is installed for Dell Hybrid Cloud System for Microsoft?
- 7 On-premises software
- 9 Cloud services (optional)
- 9 Compute cluster
- 9 Storage cluster
- 10 Backup infrastructure
- 10 Virtual machines
- 11 Network configuration
- 12 Cloud configuration
- 12 VMM library configuration
- 13 About Dell Hybrid Cloud System for Microsoft licensing
- 13 License requirements for the Dell Hybrid Cloud System for Microsoft infrastructure
- 14 License activation
- 14 Active Directory requirements
- 14 Connecting to DVM
- 15 Running the script
- 15 Check Group Policy settings
- 16 Administration
- 16 What to do first
- 16 Next steps
- 17 Verify the product license key
- 19 Review known issues in this release
- 24 Ensure that the stamp has the latest approved updates
- 24 Managing Dell Hybrid Cloud System for Microsoft
- 24 Accounts to use for management
- 25 Connecting to management tools
- 26 How to run runbooks
- 26 Creating tenant VM networks
- 27 Configuring VLANs for tenant use
- 27 Adding tenant VM networks to the cloud
- 28 Flagging the operating system VHD in the VM templates
- 28 Enabling guest-specified IP addresses in VMM
- 29 Creating additional tenant storage shares
- 33 Using Windows Azure Pack
- 34 Default Windows Azure Pack configuration
- 34 Before you go into production
- 35 Setting up tenant portal access on an isolated network
- 38 Replacing self-signed certificates
- 38 Disabling the tenant AuthSite and the admin Windows AuthSite websites
- 39 Updating to a Security Token Service and re-establishing trust
- 41 How to open the management portal for administrators
- 41 How to open the management portal for tenants
- 41 Offering services to tenants
- 47 Optional configuration
- 48 Automating tasks for efficiency
- 48 Windows Azure Pack API reference content for developers
- 48 Configuring disaster recovery protection
- 49 Step 1: Onboard to Azure Site Recovery
- 52 Step 2: Enable protection on a plan or add-on
- 53 Step 3: Tenants create resources
- 53 Step 4: Configure network mapping
- 54 Step 5: Run a failover
- 57 Step 6: Access replicated VMs
- 58 Operations
- 58 Monitoring
- 58 Onboarding to Operational Insights
- 59 Using Operations Manager
- 61 Using Operational Insights
- 61 Backup and recovery
- 61 Onboard to Azure Backup
- 65 Default backup schedule and retention policy
- 66 DPM protection groups
- 66 Disable machine account password rotation on management VMs
- 66 Protecting tenant VMs
- 68 Recovering VMs and databases (high level)
- 73 Recovering from management component failures
- 77 Recovering a tenant VM
- 81 Recovering DPM from DPM failures
- 89 Adding extra disks to DPM
- 91 Monitoring DPM
- 92 Using the Dell Hybrid Cloud System for Microsoft data consistency runbooks
- 95 Updating the Dell Hybrid Cloud System for Microsoft
- 95 Overview of the Patch and Update framework
- 96 How to check which update package is installed
- 96 How to obtain the update packages
- 97 When to run the update package
- 97 Preparing the patching environment
- 98 Update the computers
- 101 Monitoring the Patch and Update process (optional)
- 102 Post update cleanup
- 102 Shutting down and starting up the stamp
- 103 Before you begin
- 103 Shutting down the stamp
- 106 Starting up the stamp
- 110 Recovering after a power outage
- 115 Security
- 115 User accounts and groups that are added by default
- 115 User accounts
- 116 Service accounts
- 118 Groups
- 118 Resetting service account passwords
- 118 How service accounts are managed
- 119 Important information about the password reset script
- 120 How to run the MCPasswordReset script
- 121 Viewing MCPasswordReset script logs
- 122 Troubleshooting the MCPasswordReset script
- 125 Rotating Windows Azure Pack encryption keys
- 125 Managing antivirus and antimalware
- 125 Overview of default antimalware configuration
- 126 How to run unscheduled antimalware scans
- 126 How to view scan results and respond to malware incidents
- 127 How to update antimalware definitions manually
- 127 How to verify that updates are working
- 127 Managing certificates
- 128 Viewing the certificates
- 128 Replacing self-signed certificates with CA-signed certificates
- 133 Updating certificates about to expire
- 134 Appendix A: Expanding the stamp
- 134 Compute expansion workflow
- 135 Physical installation
- 135 Deploying compute expansion nodes
- 135 Adding another server to backup infrastructure
- 136 Appendix B: Performing a factory reset
- 136 Access and account requirements
- 137 Resetting the backup servers
- 143 Resetting the standalone backup host
- 146 Resetting the storage cluster (<Prefix>-SCL)
- 148 Resetting the compute cluster (<Prefix>CCL)
- 151 Clean up Active Directory and DNS records
- 151 Clean up artifacts created by Azure Site Recovery
- 152 Delete the VMM server
- 152 Delete the IaaS VMs from failover if needed
- 152 Optionally delete the vault and the associated storage account
- 153 Appendix C: Retrieving cluster names, host names, and IP addresses
- 153 Get cluster names
- 153 Get the cluster IP addresses
- 153 Example 1: Compute clusters
- 153 Example 2: File server clusters
- 154 Example 3: SQL Server clusters
- 154 Get host names and IP addresses for cluster hosts
- 154 Compute cluster host
- 154 File server cluster
- 154 SQL Server cluster
- 155 Get infrastructure VM names and addresses
- 156 Appendix D: Ports and protocols