vcenter6.7 Inventory issue after backup restore

[sachidamb]

hi there,

after restore vcenter6.7 from backup.. The restored vcenter does not shows the Host/Cluster inventory information with below error message appear in HTML UI ..

Unexpected error encountered while retrieving Hosts information

Unexpected error encountered while retrieving VM information.

Appreciate some one help, how to debug the issue further and address it. Please let me know.

Thank you,

Sakthivel Chidambaram.

[KevinDavis31]

I have the same problem. I've tried a few things I found online, but nothing really works..

[scott28tt · Accepted solution]

Thread reported, a moderator should move it to the vCenter Server area since this has nothing to do with Skyline.

[BigMike23]

Thanks for keeping the VMTN more organized and also for volunteering your spare time to answer our questions.

[ruthme]

If you are experiencing inventory issues after restoring a backup in vCenter 6.7, there are a few steps you can take to troubleshoot the problem:

1. Restart vCenter services: Sometimes, restarting the vCenter services can help resolve inventory-related issues. Log in to the vCenter Server using the vSphere Web Client or vSphere Client, go to the vCenter Server instance, and restart the services.

2. Verify backup integrity: Ensure that the backup you restored is valid and intact. Check for any errors or warnings during the backup restoration process. If the backup is corrupt or incomplete, consider restoring from a different backup or contacting the backup provider for assistance.

3. Check vCenter Server logs: Review the vCenter Server logs to identify any errors or warnings related to the inventory. The logs can provide valuable information about the issue and help you narrow down the cause. Look for entries related to inventory, database connectivity, or any specific error codes.

4. Verify database connectivity: Ensure that the vCenter Server is properly connected to the underlying database. Check the database connection settings in the vCenter Server configuration and ensure they are accurate. Verify that the database server is accessible and running.

5. Re-register inventory objects: If certain inventory objects are missing or not functioning properly, you can try re-registering them. This involves removing the affected objects from the inventory and then adding them back. Be cautious when performing this step and ensure you have a backup before making any changes.

6. Verify permissions: Make sure that the user account you are using to access vCenter Server has the appropriate permissions to view and manage the inventory. Check the user permissions and ensure they are correctly configured.

7. Consider VMware support: If the above steps do not resolve the issue, it may be necessary to reach out to VMware support for further assistance. Provide them with details about the backup restore process, any error messages or logs you have encountered, and the specific inventory issues you are facing.

Remember to exercise caution when making any changes to the vCenter Server or its inventory. It is always recommended to have proper backups and to consult with knowledgeable administrators or VMware support before performing any critical actions. 

[adamsmith_1626]

If you have restored a backup in vCenter 6.7 and are still having problems with your inventory, there are a few actions you may take to address the issue. These methods are as follows:

Restart the vCenter services. If you're having problems with your inventory, you may find that restarting the vCenter services helps. You can restart the services by logging in to the vCenter Server using either the vSphere Web Client or the vSphere Client. Once there, navigate to the vCenter Server instance.

Check the integrity of the backup by making sure that the copy of the data you just restored is accurate and complete. During the process of restoring the backup, it is important to check for any issues or warnings that may occur. If the backup is damaged or missing data, you should think about restoring the data from a different backup or getting in touch with the backup provider for assistance.

Check the logs on the vCenter Server: Go through the logs on the vCenter Server and look for any issues or warnings that are connected to the inventory. The logs have the potential to provide useful information about the problem and assist you in determining its root cause. Search for any entries that might be related to inventory, database connectivity, or specific error codes.

Check the database connection: Make sure that the vCenter Server is correctly linked to the database that is being used as a foundation. Verify that the vCenter Server setup contains correct database connection settings by performing a check on those settings. Check to see if the database server can be accessed and that it is operating normally.

[albertcarry]

After restoring a backup in vCenter 6.7, you may have inventory problems. There are several reasons for this and ways to fix them. Here are some things to try as you try to fix the problem:

Small configuration or synchronisation difficulties are frequently easily fixed by just restarting the vCenter Server services. You can use the vSphere Web Client or secure shell (SSH) to connect to the vCenter Server and issue the necessary commands to accomplish this.

Verify the vCenter Server and all of its supporting components are in good working order by performing a health check. See if there are any alerts or faults in the vCenter Server logs that could explain the inventory problem. vCenter Server logs are normally kept in the same directory as the server itself.

[jerrymark1626]

Inventory problems in vCenter 6.7 after a backup restore can be caused by a number of things. When recovering a vCenter backup, it's important to make sure the process is done right so that problems don't happen. Here are some things you can do to figure out what's wrong with the inventory:

Verify Backup Integrity: Before recovering a vCenter backup, make sure the backup file is complete and not damaged. If the backup is broken, it could cause problems when you try to recover it, which could cause inventory problems.

Check vCenter Services: After the restore, make sure that all vCenter services are running properly. If any services aren't working as they should, try to restart them and check the logs for any problems.

Check vCenter Database: Make sure that the vCenter database has been restored correctly and that all of the needed info is there. Inventory problems can sometimes be caused by an incomplete or failed database restart.

Reconnect ESXi Hosts: If the vCenter inventory shows that ESXi hosts are missing or offline, try to connect them to the vCenter server again. In the vSphere client, right-click on the server and choose "Connect."

Check VMs and Templates: Make sure that all virtual machines and templates are in the vCenter catalogue. Try adding them by hand if any are missing.

Check the datastores: Make sure that all of the datastores are correctly connected to the ESXi machines and that the vCenter server can reach them.

Review Logs: Check the vCenter Server logs (vpxd.log, vpxd-profiler.log, etc.) for any error messages or warnings about the inventory problems. Logs can tell you a lot about what could be causing the trouble.

Restart the vCenter Server: If nothing else works, try restarting the vCenter Server. But don't do this until you've carefully gone through the logs and made sure there are no active jobs or critical problems.

Check the version and compatibility of vCenter: Make sure that the saved file works with the version of vCenter you are using. Versions that don't match up can cause problems.

Contact VMware Support: If the steps above don't fix the inventory problems, you should contact VMware Support for more help. They can help you look at the logs, figure out what's wrong, and tell you how to fix it.

Remember that restoring files can be hard, and it's important to have a good backup and recovery plan in place. Always make regular backups and try the restore process in a non-production environment to make sure it works as expected before using it in a production environment.