Jump To Close Expand all Collapse all Table of contents Maintaining Red Hat Hyperconverged Infrastructure for Virtualization Making open source more inclusive I. Configuration tasks Expand section "I. Configuration tasks" Collapse section "I. Configuration tasks" 1. Add compute and storage resources Expand section "1. Add compute and storage resources" Collapse section "1. Add compute and storage resources" 1.1. Creating new bricks using ansible 1.2. Creating new bricks above VDO layer using ansible 1.3. Expanding volume from Red Hat Virtualization Manager 1.4. Expanding the hyperconverged cluster by adding a new volume on new nodes using the Web Console 2. Configure high availability using fencing policies Expand section "2. Configure high availability using fencing policies" Collapse section "2. Configure high availability using fencing policies" 2.1. Configuring Fencing Policies in the Cluster 2.2. Configuring Fencing Parameters on the Hosts 3. Configuring backup and recovery options Expand section "3. Configuring backup and recovery options" Collapse section "3. Configuring backup and recovery options" 3.1. Prerequisites Expand section "3.1. Prerequisites" Collapse section "3.1. Prerequisites" 3.1.1. Prerequisites for geo-replication 3.1.2. Prerequisites for failover and failback configuration 3.2. Supported backup and recovery configurations 3.3. Configuring backup to a secondary volume Expand section "3.3. Configuring backup to a secondary volume" Collapse section "3.3. Configuring backup to a secondary volume" 3.3.1. Prerequisites Expand section "3.3.1. Prerequisites" Collapse section "3.3.1. Prerequisites" 3.3.1.1. Enable shared storage on the source volume 3.3.1.2. Match encryption on source and target volumes 3.3.2. Create a suitable target volume for geo-replication 3.3.3. Configuring geo-replication for backing up volumes Expand section "3.3.3. Configuring geo-replication for backing up volumes" Collapse section "3.3.3. Configuring geo-replication for backing up volumes" 3.3.3.1. Creating a geo-replication session 3.3.3.2. Verifying creation of a geo-replication session 3.3.3.3. Synchronizing volume state using the Administration Portal 3.3.4. Scheduling regular backups using geo-replication 3.4. Configuring failover to and failback from a secondary cluster Expand section "3.4. Configuring failover to and failback from a secondary cluster" Collapse section "3.4. Configuring failover to and failback from a secondary cluster" 3.4.1. Creating a secondary cluster for failover 3.4.2. Creating a mapping file between source and target clusters 3.4.3. Creating a failover playbook between source and target clusters 3.4.4. Creating a failover cleanup playbook for your primary cluster 3.4.5. Create a failback playbook between source and target clusters 4. Configure encryption with Transport Layer Security (TLS/SSL) Expand section "4. Configure encryption with Transport Layer Security (TLS/SSL)" Collapse section "4. Configure encryption with Transport Layer Security (TLS/SSL)" 4.1. Configuring TLS/SSL using self-signed certificates 4.2. Configuring TLS/SSL using Certificate Authority signed certificates 5. Configure performance improvements Expand section "5. Configure performance improvements" Collapse section "5. Configure performance improvements" 5.1. Improving volume performance by changing shard size Expand section "5.1. Improving volume performance by changing shard size" Collapse section "5.1. Improving volume performance by changing shard size" 5.1.1. Changing shard size on replicated volumes 5.1.2. Changing shard size on arbitrated volumes 5.2. Configuring a logical volume cache (lvmcache) for an existing volume 6. Configure monitoring Expand section "6. Configure monitoring" Collapse section "6. Configure monitoring" 6.1. Configuring event notifications II. Maintenance tasks Expand section "II. Maintenance tasks" Collapse section "II. Maintenance tasks" 7. Basic Operations Expand section "7. Basic Operations" Collapse section "7. Basic Operations" 7.1. Creating a shutdown playbook 7.2. Shutting down RHHI for Virtualization 7.3. Starting up a hyperconverged cluster 8. Monitoring Red Hat Hyperconverged Infrastructure for Virtualization Expand section "8. Monitoring Red Hat Hyperconverged Infrastructure for Virtualization" Collapse section "8. Monitoring Red Hat Hyperconverged Infrastructure for Virtualization" 8.1. Monitoring Virtual Data Optimizer (VDO) Expand section "8.1. Monitoring Virtual Data Optimizer (VDO)" Collapse section "8.1. Monitoring Virtual Data Optimizer (VDO)" 8.1.1. Monitoring VDO using the command line interface 8.1.2. Monitoring VDO using the Web Console 9. Freeing space on thinly-provisioned logical volumes using fstrim 10. Add hyperconverged hosts to Red Hat Virtualization Manager 11. Reinstalling a hyperconverged host 12. Replacing hosts Expand section "12. Replacing hosts" Collapse section "12. Replacing hosts" 12.1. Replacing the primary hyperconverged host using ansible 12.2. Replacing other hyperconverged hosts using ansible Expand section "12.2. Replacing other hyperconverged hosts using ansible" Collapse section "12.2. Replacing other hyperconverged hosts using ansible" 12.2.1. Replacing a hyperconverged host to use a different FQDN 12.2.2. Replacing a hyperconverged host to use the same FQDN 12.3. Preparing a replacement hyperconverged host using ansible 13. Recovering from disaster Expand section "13. Recovering from disaster" Collapse section "13. Recovering from disaster" 13.1. Manually restoring data from a backup volume Expand section "13.1. Manually restoring data from a backup volume" Collapse section "13.1. Manually restoring data from a backup volume" 13.1.1. Restoring a volume from a geo-replicated backup 13.2. Failing over to a secondary cluster 13.3. Failing back to a primary cluster 13.4. Stopping a geo-replication session using RHV Manager 13.5. Turning off scheduled backups by deleting the geo-replication schedule III. Troubleshooting Expand section "III. Troubleshooting" Collapse section "III. Troubleshooting" 14. Self-heal does not complete Expand section "14. Self-heal does not complete" Collapse section "14. Self-heal does not complete" 14.1. Gluster File ID mismatch IV. Reference material Expand section "IV. Reference material" Collapse section "IV. Reference material" A. Fencing Policies for Red Hat Gluster Storage B. Glossary of terms Expand section "B. Glossary of terms" Collapse section "B. Glossary of terms" B.1. Virtualization terms B.2. Storage terms B.3. Hyperconverged Infrastructure terms Legal Notice Settings Close Language: 日本語 English Language: 日本語 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Language and Page Formatting Options Language: 日本語 English Language: 日本語 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Part IV. Reference material Previous Next
