VMware vCenter recovery

vCenter database corruption can remove inventory and management while ESXi workloads continue running independently.

The vCenter Server Appliance stores inventory, tasks, events, permissions and service configuration in embedded PostgreSQL. Abrupt storage failure, full partitions or damaged database pages can stop vpxd and related services.

Understand the symptom

vCenter recovery separates management-plane state from the virtual machines and hosts it manages.

WHY

What is happening

A supported file-based backup can restore the appliance and embedded database to a compatible version. Database-level repair may expose readable tables, but corrupted system catalogs or missing transaction status can leave the appliance fundamentally inconsistent; running ESXi VMs should be protected independently.

What you may see

Symptoms that change the recovery path.

01

vpxd service will not start

The embedded database or a dependent service is unavailable.

02

PostgreSQL reports invalid pages or missing files

Relations, transaction status or tablespaces are damaged.

03

VAMI restore fails

The file-based backup itself is incomplete or corrupt.

04

Hosts run but inventory is unavailable

Workloads survive while centralized management data is offline.

Protect the source

Actions that can make the situation worse.

01

Redeployment loses historical management state

Inventory, permissions, tags, alarms and integration records may not be recreated automatically.

02

Database repair can remove rows

A service that starts is not proof that inventory relationships are complete.

03

Changing ESXi inventory complicates reconciliation

Avoid renaming, re-registering or deleting VMs while vCenter evidence is preserved.

Do this now

Safe steps before evaluation.

01

Power off and clone the appliance

Preserve the VCSA disks before service, vacuum or database repair attempts.

02

Collect version and service state

Record vCenter build, deployment size, failed services, partition usage and logs.

03

Preserve every backup

Keep file-based backups, appliance snapshots, certificates and external database or PSC context.

04

Protect ESXi workloads

Inventory hosts and running VMs without changing their files or registration unnecessarily.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Appliance and backup analysis

NEPFOSYS compares VCSA state, PostgreSQL files, service logs and file-based backups.

02

Compatible restore testing

Appliance restoration or database extraction is evaluated on protected copies.

03

Inventory validation

Hosts, VMs, permissions and priority management records are checked before cutover.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Will running VMs stop when vCenter is down?

Usually they continue on ESXi hosts, but centralized management, automation and some services are unavailable.

Can a VCSA file-based backup restore the database?

Yes, it is the recommended protection method when the backup is complete and version compatible.

Should I repair embedded PostgreSQL directly?

Preserve the appliance first. Unsupported or lossy repair can make a future supported restore harder.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case