Show Table of Contents Hide Table of Contents English 日本語 English Multi-page HTML Single-page HTML PDF ePub Self-Hosted Engine Guide1. Introduction2. Deploying the Self-Hosted Engine2.1. Deploying the Self-Hosted Engine Using Cockpit2.2. Deploying the Self-Hosted Engine Using the Command Line3. Troubleshooting a Self-Hosted Engine Deployment3.1. Troubleshooting the Manager Virtual Machine3.2. Cleaning Up a Failed Self-hosted Engine Deployment4. Administering the Self-Hosted Engine4.1. Maintaining the Self-Hosted Engine4.2. Administering the Manager Virtual Machine4.3. Configuring Memory Slots Reserved for the Self-Hosted Engine on Additional Hosts4.4. Installing Additional Self-Hosted Engine Nodes4.5. Reinstalling an Existing Host as a Self-Hosted Engine Node4.6. Removing a Host from a Self-Hosted Engine Environment4.7. Updating the Manager Virtual Machine5. Migrating from a Standalone Manager to a Self-Hosted Engine5.1. Backing up the Original Manager5.2. Restoring the Backup on a New Self-Hosted Engine5.3. Enabling the Red Hat Virtualization Manager Repositories5.4. Reinstalling an Existing Host as a Self-Hosted Engine Node6. Backing up and Restoring a Self-Hosted Engine6.1. Backing up the Original Manager6.2. Restoring the Backup on a New Self-Hosted Engine6.3. Enabling the Red Hat Virtualization Manager Repositories6.4. Reinstalling Hosts6.5. Removing a Storage Domain7. Recovering a Self-Hosted Engine from an Existing Backup7.1. Restoring the Backup on a New Self-Hosted Engine7.2. Enabling the Red Hat Virtualization Manager Repositories7.3. Reinstalling Hosts7.4. Removing a Storage Domain8. Upgrading the Self-Hosted Engine8.1. Upgrading a Self-Hosted Engine from 3.6 to Red Hat Virtualization 126.96.36.199. Enabling Global Maintenance Mode8.1.2. Updating the Red Hat Virtualization Manager8.1.3. Upgrading the Self-hosted Engine from 3.6 to 4.08.1.4. Upgrading the Manager from 4.0 to 188.8.131.52. Upgrading the Manager from 4.1 to 184.108.40.206. Disabling Global Maintenance Mode8.1.7. Updating the Hosts8.1.8. Changing the Cluster Compatibility Version8.1.9. Changing the Data Center Compatibility Version8.1.10. Replacing SHA-1 Certificates with SHA-256 Certificates8.2. Upgrading a Self-Hosted Engine from 4.0 to Red Hat Virtualization 220.127.116.11. Enabling Global Maintenance Mode8.2.2. Updating the Red Hat Virtualization Manager8.2.3. Upgrading the Manager from 4.0 to 18.104.22.168. Upgrading the Manager from 4.1 to 22.214.171.124. Disabling Global Maintenance Mode8.2.6. Updating the Hosts8.2.7. Changing the Cluster Compatibility Version8.2.8. Changing the Data Center Compatibility Version8.2.9. Replacing SHA-1 Certificates with SHA-256 Certificates8.3. Upgrading a Self-Hosted Engine from 4.1 to Red Hat Virtualization 126.96.36.199. Enabling Global Maintenance Mode8.3.2. Updating the Red Hat Virtualization Manager8.3.3. Upgrading the Manager from 4.1 to 188.8.131.52. Disabling Global Maintenance Mode8.3.5. Updating the Hosts8.3.6. Changing the Cluster Compatibility Version8.3.7. Changing the Data Center Compatibility Version8.3.8. Updating OVN Providers Installed in Red Hat Virtualization 184.108.40.206. Replacing SHA-1 Certificates with SHA-256 Certificates9. Migrating the Self-Hosted Engine Database to a Remote Server DatabaseA. Upgrading a RHEV-H 3.6 Self-Hosted Engine to a RHVH 4.2 Self-Hosted EngineB. Upgrading from RHEV-H 3.6 to RHVH 4.2 While Preserving Local Storage Self-Hosted Engine Guide Red Hat Virtualization 4.2Installing and Maintaining the Red Hat Virtualization Self-Hosted EngineRed Hat Virtualization Documentation Team Red Hat Customer Content Services firstname.lastname@example.orgAbstract A comprehensive guide to the self-hosted engine. 1. Introduction 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.