vCenter Restore Fails with "Current PNID does not match the backup PNID"

Products

• VMware vCenter Server

Issue/Introduction

When restoring vCenter you get an error in Stage 2 that the PNID does not match with below error.

Metadata and system validation failed.
Current PNID 'XXXXXXXX' does not match the backup PNID 'XXXXXXXX'

Environment

• VMware vCenter Server 8.x
• VMware vCenter Server 9.x

Cause

• The vCenter Primary Network Identifier (PNID)—typically the FQDN used during initial deployment—must match the backup exactly. This failure is commonly caused by:

• • • • Case Sensitivity or Typos: Mismatches in the string characters or subtle spelling errors in the domain.

        • Example PNID that will cause a failure: [e-mail] and [e-mail].

        • Example PNID that will work: [e-mail] and [e-mail].

      • DNS Resolution Mismatch: The FQDN/PNID resolves via DNS to an IP address that does not match the static IP assigned to the new appliance shell.

        • During validation, the installer performs a lookup on the PNID.

        • If the returned "resolved IP" is the old IP (e.g., 192.168.###.###) while the local machine is configured with a new IP (e.g., 10.1.###.###), validation fails.

Resolution

1. Review PNID:

   • Validate the source vCenter PNID. 
   • Check the PNID of the vCenter you are restoring to ensure it matches the configured PNID with the source vCenter.
   • Initiate the restoration process, ensuring the PNID is accurately configured on restored vCenter.

2. Power Off the Source vCenter:

   • Safely shut down the source vCenter, stopping all dependent services.

3. Confirm Static IP Configuration:

   • Verify that the VM is set to use a static IP address and ensure this address is reserved on the network.

4. Restore VM with Static IP:

   • Proceed with the VM restoration, ensuring it retains the specified static IP address.
     
     

5. Verify DNS A-Records:

   • Perform a DNS Lookup: Ensure the FQDN/PNID of the vCenter resolves to the exact static IP assigned to the new appliance being deployed.

   • Update DNS Records: If the DNS query returns an old or incorrect IP, update the DNS A-record and Reverse Lookup (PTR) record to match the new IP address before proceeding with Stage 2.