Book Image

VMware vSphere 5.1 Cookbook

By : Abhilash G B
Book Image

VMware vSphere 5.1 Cookbook

By: Abhilash G B

Overview of this book

Amidst all the recent competition from Citrix and Microsoft, VMware's vSphere product line is still the most feature rich and futuristic product in the virtualization industry. Knowing how to install and configure vSphere components is important to give yourself a head start towards virtualization using VMware. If you want to quickly grasp the installation and configuration procedures, especially by using the new vSphere 5.1 web client, this book is for you.VMware vSphere 5.1 Cookbook will take you through all the steps required to accomplish a task with minimal reading required. Most of the tasks are accompanied with relevant screenshots with an intention to provide a visual guidance as well.The book has many useful recipes that will help you progress through the installation of VMware ESXi 5.1 and vCenter Server 5.1. You will learn to use Auto Deploy and Image Profiles to deploy stateless/stateful ESXi servers, configure failover protection for virtual machines using vSphere HA, configure automated load balancing using vSphere DRS and DPM. Finally, the book guides you through upgrading or patching ESXi servers using VMware Update Manager and also deploying and configuring vSphere Management Assistant (VMA) to be able to run scripts to manage the ESXi servers.
Table of Contents (20 chapters)
VMware vSphere 5.1 Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Creating a shared repository


We can export downloaded patch data from the repository used by the UMDS to a shared location so that the Update Manager server can be configured to use this shared location.

How to do it...

To export the downloaded patch data to a shared repository, issue the following command:

Syntax:

vmware-umds -E --export-store repository_path

Example:

vmware-umds -E --export-store C:\PatchRep
vmware-umds -E --export-store \\vcenter51\atvc

How it works...

The command copies the data from the patch store to the shared repository. You have to periodically export the patch data to keep the shared repository up to date. The shared repository folder should have full permissions (everyone) over the network.