vspace software is corrupted please reinstall it

It might take a little longer, but you'll have more insurance that your backup is actually a non-corrupted backup. Even better: before upgrading your VCSA, be sure to make a new file-level backup.Īnother backup option to point out is an option that allows you to enable DB Health Check before the periodic execution of the backup. You should make sure that each time you upgrade your VCSA, you immediately make a backup (if not scheduled periodically). What happens is that if the file-level backup was taken on a different version of VCSA, you'll get an error message: (The installation ISO for restores must be identical.) If, for example, you have file-level backups that were created on a certain version number of VCSA, they can only be used on the same version. The restore process is not really difficult, but there is some information you should know.īefore we start, I'd like to point out that the VMware file-level backup/restore utility needs to have the same versions on both ends. In this post, we'll show you the steps for restoring vCenter Server via the built-in wizard. All these elements can be restored to a freshly deployed VCSA if the restore from image-level backup fails for some reason. With the file-level backup, you back up the stats, events, and tasks as well as inventory and configuration. The best practice is usually to keep separate backups of your VCSA, with the configuration backup (file level) done via the VAMI user interface on one side, and an image-level backup of the full virtual appliance (VA) with all its settings on the other.

Vspace software is corrupted please reinstall it