Show Table of Contents Hide Table of Contents English English Multi-page HTML Single-page HTML PDF ePub Maintaining Red Hat Hyperconverged Infrastructure for VirtualizationI. Configuration tasks1. Add compute and storage resources1.1. Expanding the hyperconverged cluster by adding a new volume on new nodes using Cockpit2. Configure high availability using fencing policies2.1. Configuring Fencing Policies in the Cluster2.2. Configuring Fencing Parameters on the Hosts3. Configuring backup and recovery options3.1. Prerequisites3.1.1. Prerequisites for geo-replication3.1.2. Prerequisites for failover and failback configuration3.2. Supported backup and recovery configurations3.3. Configuring backup to a secondary volume3.3.1. Prerequisites3.3.2. Create a suitable target volume for geo-replication3.3.3. Configuring geo-replication for backing up volumes3.3.4. Scheduling regular backups using geo-replication3.4. Configuring failover to and failback from a secondary cluster3.4.1. Creating a secondary cluster for failover3.4.2. Creating a mapping file between source and target clusters3.4.3. Creating a failover playbook between source and target clusters3.4.4. Creating a failover cleanup playbook for your primary cluster3.4.5. Create a failback playbook between source and target clusters4. Configure encryption with Transport Layer Security (TLS/SSL)4.1. Configuring TLS/SSL using self-signed certificates4.2. Configuring TLS/SSL using Certificate Authority signed certificates5. Configure performance improvements5.1. Improving volume performance by changing shard size5.1.1. Prerequisites5.1.2. Safely changing the shard block size parameter value5.2. Configuring a logical volume cache (lvmcache) for improved performance6. Configure monitoring6.1. Configuring event notificationsII. Maintenance tasks7. Basic Operations7.1. Creating a shutdown playbook7.2. Shutting down RHHI for Virtualization7.3. Starting up a hyperconverged cluster8. Upgrading to Red Hat Hyperconverged Infrastructure for Virtualization 1.58.1. Major changes in version 1.58.2. Upgrade workflow8.3. Preparing to upgrade8.3.1. Verify brick mount options8.3.2. Update to the latest version of the previous release8.3.3. Update subscriptions8.3.4. Verify that data is not currently being synchronized using geo-replication8.4. Upgrading Red Hat Hyperconverged Infrastructure for Virtualization8.4.1. Upgrading the Hosted Engine virtual machine8.4.2. Upgrading the virtualization hosts8.4.3. Cleaning up after upgrading9. Monitoring Red Hat Hyperconverged Infrastructure for Virtualization9.1. Monitoring Virtual Data Optimizer (VDO)9.1.1. Monitoring VDO using the command line interface9.1.2. Monitoring VDO using the Cockpit UI10. Add virtualization hosts to Red Hat Virtualization Manager11. Reinstalling a virtualization host12. Replacing the primary storage host13. Replacing a Gluster Storage Host13.1. Replacing a Gluster Storage Host (Different FQDN)13.2. Replacing a Gluster Storage Node (Same FQDN)14. Recovering from disaster14.1. Manually restoring data from a backup volume14.1.1. Restoring a volume from a geo-replicated backup14.2. Failing over to a secondary cluster14.3. Failing back to a primary cluster14.4. Stopping a geo-replication session using RHV Manager14.5. Turning off scheduled backups by deleting the geo-replication scheduleIII. Reference materialA. Fencing Policies for Red Hat Gluster StorageB. Example gdeploy configuration filesB.1. Example gdeploy configuration file for setting up TLS/SSLB.2. Example gdeploy configuration file for preparing a replacement hostB.3. Example gdeploy configuration file for scaling to additional nodesLegal Notice Part I. Configuration tasks Maintaining Red Hat Hyperconverged Infrastructure for Virtualization 1. Add compute and storage resources Where did the comment section go?Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.