Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Proxmox High Availability
  • Toc
  • feedback
Proxmox High Availability

Proxmox High Availability

By : CHENG MAN
4.3 (4)
close
Proxmox High Availability

Proxmox High Availability

4.3 (4)
By: CHENG MAN

Overview of this book

If you want to know the secrets of virtualization and how to implement high availability on your services, this is the book for you. For those of you who are already using Proxmox, this book offers you the chance to build a high availability cluster with a distributed filesystem to further protect your system from failure.
Table of Contents (10 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Basic Concepts of a Proxmox Virtual Environment
1. Basic Concepts of a Proxmox Virtual Environment
Introduction to Proxmox Virtual Environment
Introduction to server virtualization
Server virtualization basics – guest versus host
Comparing types of server virtualization software
Basic administration on Proxmox VE
Virtualization options in Proxmox VE
Virtual disk options under Proxmox VE
Introducing the OpenVZ template
Summary
2
2. Getting Started with a High Availability (HA) Environment
2. Getting Started with a High Availability (HA) Environment
What is a high availability (HA) environment?
Introducing a Proxmox VE cluster
System requirements for the Proxmox cluster
HA capability for Proxmox with a two-node cluster
Summary
3
3. Key Components for Building a Proxmox VE Cluster
chevron up
3. Key Components for Building a Proxmox VE Cluster
Key component 1 – shared storage
Key component 2 – reliable network
Key component 3 – a fencing device
Key component 4 – quorum disk
Summary
4
4. Configuring a Proxmox VE Cluster
4. Configuring a Proxmox VE Cluster
Configuring a network for a Proxmox VE cluster
Preparing storage for a Proxmox cluster
Configuring a Proxmox VE cluster
Network fencing with a Cisco switch via SNMP
Building a Gluster filesystem for a Proxmox cluster
Building a Ceph filesystem for a Proxmox cluster
Summary
5
5. Testing on a Proxmox Cluster
5. Testing on a Proxmox Cluster
Storage preparation for an LVM shared storage
Demonstration of live migration
Building an HA-protected VM
Testing with the cluster environment
Setting up a failover domain
Summary
6
6. System Migration of an Existing System to a Proxmox VE Cluster
6. System Migration of an Existing System to a Proxmox VE Cluster
System migration of an existing Linux platform
Live migration of a physical machine to a KVM
System migration of a Windows platform
System migration from VMware to Proxmox
System migration from XenServer / Hyper-V Server to Proxmox
Summary
7
7. Disaster Recovery on a Proxmox VE Cluster
7. Disaster Recovery on a Proxmox VE Cluster
Backup process for VMs in Proxmox
The restore process of VMs in Proxmox
Setting up a scheduled backup for the VMs
System recovery of a Proxmox cluster failure
Summary
8
8. Troubleshooting on a Proxmox Cluster
8. Troubleshooting on a Proxmox Cluster
Troubleshooting system access problems
Troubleshooting system migration problems
Troubleshooting system storage problems
Troubleshooting Proxmox cluster problems
Summary
9
Index
Index

Key component 3 – a fencing device

So, we have talked about the two key components of a Proxmox HA cluster; they are the storage devices and reliable network. Do you remember that I mentioned a fencing device when I introduced DRBD? Do you know what a fencing device is and how it works? We'll learn more about this in the following section.

What is a fencing device?

A fencing device, as the name suggests, is a virtual fence that prevents communication between two nodes. It is used to separate the failed node from accessing shared resources. If there are two nodes that access shared resources at the same time, a collision occurs; this might corrupt the shared data, which is the data inside the VM.

Such fencing is done automatically based on the configuration defined, because we cannot identify a real failure or a temporary hang on a node. If a node is really down, then a fencing action is not needed, but if it is a temporary hang due to a network delay or temporary resource shortage...

End of Section 4
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete