Book Image

Disaster Recovery Using VMware vSphere Replication and vCenter Site Recovery Manager - Second Edition

By : Abhilash G B
Book Image

Disaster Recovery Using VMware vSphere Replication and vCenter Site Recovery Manager - Second Edition

By: Abhilash G B

Overview of this book

VMware vCenter Site Recovery manage is an orchestration tool used to automate disaster recovery in a manner that no other solution does. It is programmed to leverage array-based replication and VMware's proprietary vSphere Replication engine. The book begins by talking about the architecture of SRM and guides you through the procedures involved in installing and configuring SRM to leverage array-based replication. You will then learn how to protect your virtual machines by creating Protection Groups and validate their recoverability by testing recovery plans and even performing failover and failback. Moving on, you will learn how to install and configure vSphere Replication as a standalone disaster recovery solution. It also guides you through the procedures involved in configuring SRM to leverage vSphere replication. Finally, you will learn how to deploy and configure vRealize Orchestrator and its plugin for SRM and vSphere Replication.
Table of Contents (13 chapters)
Disaster Recovery Using VMware vSphere Replication and vCenter Site Recovery Manager Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Troubleshooting SRM and vSphere Replication


Like with any other software product, you will unavoidably run into issues that are product configuration issues, bugs or operational gotchas and so on. The section of the chapter will help you to get to SRM and vSphere Replication logs and also provide you with troubleshooting references.

Getting to the logs

To understand why a software functionality failed or exhibited abnormal behavior, it is important to know what exactly transpired during that occurrence. Although most modern software will expose events/errors in the GUI, it is impractical to present a more detailed view of the events/errors in the graphical user interface. Hence, all software products maintain logs. Logs are not just generated when something goes wrong but are constantly maintained. Logs might show errors and warnings even when everything is working fine.

The important fact is that not everything in the logs would make sense or help an administrator to troubleshoot an issue...