Protecting the Veeam Server and Database: Preparation and Considerations

KB ID: 2638
Product: Veeam Backup & Replication
Version: All
Published:
Last Modified: 2018-08-24

Challenge

When performing a Failover to a Replica containing the Veeam Database or restore that VM from a backup file, several steps must be taken before resuming normal operation of Veeam.

Cause

Veeam Database may not be consistent with changes made to the production database since the last run of the replication/backup job. Should a failover or restore be required, the VM may experience difficulties in taking over normal operations due to these inconsistencies. 

Solution

The server hosting the Veeam Database should be replicated/backed up in isolation from other jobs, ideally when no other data is processing. The server hosting the Veeam Database should have sufficient resources to ensure that VSS processing is fast and does not cause interruptions. 

It is recommended that you perform and rely primarily on the built in Configuration Backup as a means for backing up and recovering the Veeam Configuration. This will preserve the current state of the Veeam Database, and also preserve all job and infrastructure related configurations within Veeam. 
If the Configuration Backup was taken more recently than the last replica, be sure to Restore from the Configuration Backup to ensure that the most recent state of the Veeam Database is used.


You may need to contact Veeam Support for assistance should you experience any difficulties when failing over to a Replica of the Veeam Server or perform restore.
 

Rate the quality of this KB article: 
5 out of 5 based on 1 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Request new content

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Orphus system