Caution: This procedure modifies the database. Ensure to take a backup of the database before proceeding.
Resetting from the vCenter Server Appliance 5.1/5.5 web console
Notes:
- This method removes all information from the vCenter Server database, including license key information. You must add your license key(s) again when the steps are completed.
- Stop
vpxd
before resetting the database.
To reset the embedded PostgreSQL database via the web console:
- Log in to the VMware vCenter Server Appliance Web console. For example, access a URL similar to:
https://vCenter_Server_Appliance_IP_address:5480
- On the vCenter Server tab, click the Summary tab.
- Click Stop to stop the vCenter Services.
- On the vCenter Server tab, click Database.
- Click Reset DB contents under Actions.
Note: This action generates the warning:
WARNING: WILL DELETE ALL RECORDS
- Click Start to start the vCenter Server database.
Resetting from the vCenter Server Appliance 5.0 web console
Note: This method removes all information from the vCenter Server database, including license key information. You must add your license key(s) again when the steps are completed.
To reset the embedded DB2 database via the web console:
- Log in to the VMware vCenter Server Appliance Web console. For example, access a URL similar to:
https://vCenter_Server_Appliance_IP_address:5480
- On the vCenter Server tab, click Status.
- Click Stop vCenter to stop the current instance of the vCenter Server database. You see the messages,
Operation was successful
and Service Status is Stopped
. - On the vCenter Server tab, click Database.
- Click Reset DB contents. You see the message, Operation was successful.
- On the vCenter Server tab, click Status.
- Click Start vCenter to start the current instance of the vCenter Server database.
- Connect to the vCenter Server with the vSphere Client.
- Check the vCenter Server Inventory objects.
Resetting from the command line
Note: This method does not remove license key information from the vCenter Server database.
To reset the embedded DB2 database via the command line:
- Use SSH or open a virtual machine console to the vCenter Server Appliance and log in as root.
- Run these commands:
# service vmware-vpxd stop
# /usr/sbin/vpxd -b
You see output similar to:
------ In-memory logs start --------
2012-02-01T15:13:50.019-07:00 [7FFFF3B09700 info 'Hooks'] Hooks Initialized
------ In-memory logs end --------
2012-02-01T15:13:50.071-07:00 [7FFFF3B09700 info 'Default'] Initialized channel manager
2012-02-01T15:13:50.176-07:00 [7FFFF3B09700 info 'Default'] Current working directory: /root
2012-02-01T15:13:50.176-07:00 [7FFFF3B09700 info 'Default'] Log path: /var/log/vmware/vpx
2012-02-01T15:13:50.176-07:00 [7FFFF3B09700 info 'Default'] Initializing SSL
2012-02-01T15:13:50.472-07:00 [7FFFF3B09700 info 'Default'] Vmacore::InitSSL:doVersionCheck = true, handshakeTimeoutUs = 120000000
2012-02-01T15:13:50.542-07:00 [7FFFF3B09700 info 'Default'] Registry Item DB 5 value is ''
2012-02-01T15:16:04.665-07:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running
2012-02-01T15:16:04.665-07:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Checking service ldap for running
2012-02-01T15:16:04.689-07:00 [7FFFF3B09700 info 'Default'] [LdapBackup] LDAP not started: 0x300
2012-02-01T15:16:05.789-07:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Started LDAP
# service vmware-vpxd start
# service vmware-vpxd status
You see output similar to output:
vmware-vpxd is running
tomcat is running
- Connect to the vCenter Server with the vSphere Client and check the vCenter Server Inventory objects.