Gene's Virtualization Blog
You'll never know if you don't lab it out….
  • Home
  • About
  • YouTube Channel
  • Twitch Channel
  • Privacy Policy
  • Home
  • About
  • YouTube Channel
  • Twitch Channel
  • Privacy Policy
  • Home
  • /
  • Site Recovery Manager
  • /
  • Troubleshooting

SRM 6.1 POC Update & PSC Problems

I recently ran into some problems during my first attempt at pairing the two sites in my SRM POC, which resulted in a failure, and some misleading error messages.  Since help on this was pretty scarce on the ‘net, I opened a case with VMware Support.  After about a week’s worth of troubleshooting – repairing the installation, re-installing SRM with a fresh database, and certificate regeneration/registration provided no resolution.

srm_psc_error_1

As I was waiting for an escalation from VMware, we discovered that one of the PSCs in this environment stopped replicating changes to the other. Upon further analysis, I discovered that it had been about a month since that particular platform service controller had stopped replicating changes. What made it tough to find the problem here was that we were still able to get into vCenter and manage it just fine, but taking a peek under the covers proved there was definitely an issue.  It was by chance a license change to vCenter exposed this problem when we saw that the change didn’t make it from one vCenter to the other.

The following command will provide you with the results seen below, which indicate the synchronization problem:

On each PSC, run the following command from the vmdird directory: 

  • .\vdcrepadmin.exe -f showpartnerstatus -h localhost -u administrator -w [password]

Partner: psc1.domain.local
Host available: Yes
Status available: Yes
My last change number: 872590
Partner has seen my change number: 10846
Partner is 861744 changes behind.

Partner: psc2.domain.local
Host available: Yes
Status available: Yes
My last change number: 2147483197
Partner has seen my change number: 2147483197
Partner is 0 changes behind.

 

Since this had been discovered, the support engineer and I agreed that we should put the site recovery pairing on hold until the PSC issue was resolved, just so we didn’t have too many variables involved in our troubleshooting. To make a long story short, the PSC synchronization was the root cause of SRM not being able to pair the sites, and I’ve also written up a series on re-creating the environment in isolation, and performing the PSC replacement to provide the ultimate solution.

Share This:
Posted on October 14, 2016 by Gene Torres. This entry was posted in Site Recovery Manager, Troubleshooting and tagged SRM Site Pairing Failure, vCenter External PSC. Bookmark the permalink.
VMware Site Recovery Manager 6.1 Diagram
Deploying Windows vCenter with External PSCs in Enhanced Linked Mode: Part 1

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

    Search

    Recent Posts

    • Update: Migrate VM from Hyper-V to vSphere with Pre-Installed VMware Tools (vSphere 7 and 8 Edition)
    • Zerto 9.0 Introduces New Enhancements to LTR with Amazon S3, and Here's What you Need to Know
    • Reduce the Cost of Backup Storage with Zerto 8.5 and Amazon S3
    • Using the AWS Storage Gateway to Backup to S3 using Zerto
    • Migrate VM from Hyper-V to vSphere with Pre-Installed VMware Tools

    Archives

    • February 2023
    • July 2021
    • December 2020
    • November 2020
    • June 2020
    • January 2020
    • September 2018
    • March 2018
    • February 2018
    • October 2017
    • August 2017
    • June 2017
    • February 2017
    • November 2016
    • October 2016

    Meta

    • Log in
Powered by