Nowadays, the number of network services is rapidly increasing, due to which service availability has become a concern. With the help of the easy-to-use tools provided by Proxmox, users can easily improve their service by building their own clusters. The support of various storage options provides flexibility with different forms of network storage.
Chapter 1, Basic Concepts of a Proxmox Virtual Environment, explains the concept of virtualization and compares Proxmox with other virtualization software.
Chapter 2, Getting Started with a High Availability (HA) Environment, includes the functions provided by a Proxmox cluster and explains how it achieves high availability.
Chapter 3, Key Components for Building a Proxmox VE Cluster, explains all the components required when building a Proxmox cluster environment.
Chapter 4, Configuring a Proxmox VE Cluster, demonstrates the actual installation and configuration of a Proxmox cluster.
Chapter 5, Testing on a Proxmox Cluster, includes testing on a configured Proxmox cluster.
Chapter 6, System Migration of an Existing System to a Proxmox VE Cluster, explains how to migrate existing running systems, including Windows, Linux, and other virtualization software file formats to a Proxmox cluster.
Chapter 7, Disaster Recovery on a Proxmox VE Cluster, talks about the backup of a Proxmox cluster. The chapter also introduces the system restore process when a Proxmox cluster fails.
Chapter 8, Troubleshooting on a Proxmox Cluster, introduces all the troubleshooting content.
The list of hardware components required is given as follows:
A minimum of two servers are required. Three servers are needed if you want to test a Gluster filesystem.
A shared storage that is accessible on all the servers as a quorum disk and as VM storage.
Two network cards on each server.
Two network switches.
The software needed for this book are as follows:
Proxmox Virtual Environment 3.2 or above
NAS4Free 188.8.131.52 or an alternative to build a software-based NAS storage
DRBD 2:8.3.13-2 or above
GlusterFS 3.5.1 or above
CEPH (built with Proxmox)
This book is intended for those who want to know the secrets of virtualization and how network services provide high availability. This book is suitable for beginners and advanced users who are interested in virtualization and cluster technology. For those who are already using Proxmox, it is a great chance to build a high availability cluster with a distributed filesystem to further protect your server system from failure. If you are a beginner, this book also gets you up to speed on what is happening from conception to implementation. For this book, it will be better if you have some experience in network and system administration, while experience in Proxmox is not necessary.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "Create a new file under
/etc/init.d/tty.conf with vi or any text editor you like."
A block of code is set as follows:
<fencedevices> <fencedevice agent="fence_ifmib" community="Mycluster_community" ipaddr="192.168.1.45" name="fence_ifmib_SW1" snmp_version="2c" /> <fencedevice agent="fence_ifmib" community="Mycluster_community" ipaddr="192.168.1.46" name="fence_ifmib_SW2" snmp_version="2c" /> </fencedevices>
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
</rm> <failoverdomains> <failoverdomain name="myfailover" nofailback="1" ordered="1" restricted="1"> <failoverdomainnode name="vmsrv01" priority="1"/> <failoverdomainnode name="vmsrv02" priority="2"/> </failoverdomain> </failoverdomains> <pvevm>
Any command-line input or output is written as follows:
sudo apt-get install lshw
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Click on the Content tab and choose Templates, as shown in the following screenshot:"
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to
<[email protected]>, and mention the book title via the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at
<[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at
<[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.