Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By : Kevin Elder, Christopher Kusek, Prasenjit Sarkar
Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By: Kevin Elder, Christopher Kusek, Prasenjit Sarkar

Overview of this book

vSphere is a mission-critical piece of software for many businesses. It is a complex tool, and incorrect design and deployment can create performance related issues that can negatively affect the business. This book is focused on solving these problems as well as providing best practices and performance-enhancing techniques. This edition is fully updated to include all the new features in version 6.5 as well as the latest tools and techniques to keep vSphere performing at its best. This book starts with interesting recipes, such as the interaction of vSphere 6.5 components with physical layers such as CPU, memory, and networking. Then we focus on DRS, resource control design, and vSphere cluster design. Next, you’ll learn about storage performance design and how it works with VMware vSphere 6.5. Moving on, you will learn about the two types of vCenter installation and the benefits of each. Lastly, the book covers performance tools that help you get the most out of your vSphere installation. By the end of this book, you will be able to identify, diagnose, and troubleshoot operational faults and critical performance issues in vSphere 6.5.
Table of Contents (17 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Designing a highly available vCenter database


It does not really matter which platform or flavor of vCenter server you are using, but you must protect your vCenter server database. All configuration information about vSphere inventory objects, such as objects, roles, alarms, performance data, host profiles, and so on, are kept in the vCenter server database.

In case there are database failures, such as lost data or corrupted data, all this information may get lost and should be restored from a backup; alternatively, the entire inventory should be reconfigured manually. If you do not have a backup copy of your vCenter server database, then at the time of failure, you will lose the history of your tasks, events, and performance information apart from those already mentioned previously.

So, in a nutshell, you should use any of the available methods to maintain a backup copy of your vCenter server database. Some options are listed in the next section.

How to do it...

You can choose a number of solutions...