There is a need to create a stable backup of your VCSA or restore it properly.
To backup the VCSA with Veeam, it's important to understand that Veeam does not directly support Postgres SQL (VMware's embedded DB). Instead, it's optimal to perform backup in 2 parts:
Part 2 is not required, however, but please beware that restoring the image-level backup ensures the same state the Database was in at the point in time of the backup. VMware Best Practice shows to backup the database as regular maintenance. Then you would be able to restore the server from step 1, then restore the database to whichever point in time with the backup from step 2.
To backup the VCSA with Veeam (step 1):
To backup the VCSA Database (step 2):
When restoring the VCSA, there are some Considerations and Limitations from VMware. Once you understand the considerations and limitations, it's important to understand how to restore your vCenter when there is no vCenter in which to point Veeam. Then you are ready to perform a Full VM Restore or Instant VM Restore.
Once the VCSA is fully restored, if database backups were created, you are now ready to restore the Embedded Database to the desired point in time using the steps mentioned in the above KB.
Backup is the same as above with the difference that you may also create an image-level backup of the database server if you so choose. The benefit here is that you may restore the entire VM to a specified state. This state will be of the time in which the image backup was created and without capability of point-in-time database restores.
For Microsoft SQL and Oracle databases, Veeam can perform log backups to provide point-in-time restores.
The restore process is yet the same as the previous steps with these exceptions: