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
chevron up
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
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

Comparing types of server virtualization software

We have discussed why we need to learn server virtualization and how virtualization works, so are you curious about how many types of major virtualization software are on the market? What are the differences between them? Let's take a deep look at it:

  • Proxmox VE: As mentioned before, Proxmox VE is an open source hypervisor based on GNU/Linux (Debian-based) with a RHEL-based kernel and published under GNU AGPL v3. It differs from the alternative virtualization software as Proxmox provides a central web-based management without further installation. The underlying technologies used are Open Virtuozzo (OpenVZ) and Kernel-based Virtual Machine (KVM), which will be described in Version 1.6. Subscription plans are available for accessing enterprise repository, software updates, and user support.
  • XenServer: This is a native hypervisor based on GNU/Linux developed by the Xen Project and published under GNU AGPL v2 as open source. For XenServer, a concept of domain is used for all virtual machines, and the most privileged domain (for example, a domain that allows direct access to hardware)—dom0, is used by the hypervisor to manage other domU virtual machines. It supports para-virtualization, which allows a user to run virtualized guests on a CPU without support for virtualization; for example, no Intel VT-x or AMD-V is needed. Amazon Web Service (AWS) is a production example of using XenServer.
  • VMware ESX/ESXi: This is a bare-metal hypervisor developed by VMware based on a customized kernel called vmkernel, which is a microkernel developed by VMware.

    The difference between ESX and ESXi is that ESXi is a free version of ESX with some resource limitations. ESX has a hardware compatibility list that includes many drivers for network cards and SCSI cards. An extra hardware driver can be added to the base installation if needed. On top of the para-virtualization and hardware-assisted virtualization, ESX provides full virtualization as another option.

    There are two management tools available: vSphere client and vCenter server. VSphere client is enough for normal administration operation on one ESX while vCenter server allows the user to manage multiple ESXs, including the configuration of advanced features such as high availability and live migration.

  • Hyper-V server: This is a proprietary virtualization platform produced by Microsoft Corporation running under the Windows platform starting from Windows Server 2008. If you are mainly using a Windows platform as your virtualized guest, it is recommended that you use Hyper-V, especially if you have enabled an Active Directory domain services.

    Hyper-V provides better migration options to users; it not only provides live migration, but also provides unlimited guest movements between hosts. The benefit of the features of an Active Directory domain is that Hyper-V provides replica on virtual machines, which allows a user to copy a specific VM from the source's site to the target site asynchronously via a WAN or a secure VPN.

Comparison table of hypervisors

We have learned that there are many virtualization platforms on the market, so what are the differences between them? Let's take a look at the following table:

Virtualization platform

Proxmox

XenServer

VMware ESX/ESXi

Hyper-V server

Latest version

3.2

6.1

5.5

Server 2012 R2

License

GNU GPL v3

GNU GPL v2

Proprietary

Free

Open Source

Yes

Yes

No

No

Base OS

Linux

Linux

Vmkernel

Windows

Console OS

No

Yes

Yes

No

Management tools

Web GUI

XenCenter

vSphere Client vCenter

Hyper-V Manager

Host HA

Yes

Yes

Yes (vCenter)

Yes

Guest HA

Yes

Yes, (XenMotion)

Yes, (vMotion)

Yes (Live Migration)

Supported storage

LVM groupNFS, iSCSI, RBD, NAS, and SAS

NFS, iSCSI, fiber channel, NAS, SAS, and CIFS

Fibre Channel, iSCSI, NAS, and SAS

SMB, iSCSI, Fibre channel, NAS, and SAS

Supported virtualization technology*

  • FV (KVM)
  • OpenVZ
  • PV
  • HV
  • FV
  • PV
  • HV
  • PV
  • HV

License model

Per CPU

Per CPU

Per CPU

Per VM and host

In the previous table, FV stands for full virtualization, PV stands for para-virtualization, and HV stands for hardware-assisted virtualization.

End of Section 5
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