When we talk about Veeam we are so focused on creating a well-defined backup and replication environment for our VMs that we can forget that Veeam Server itself also needs to be protected. In this post I'll talk a little bit about how we can protect our Veeam servers and what are the best practices Veeam recommends to do so.
First of all, if your Veeam server is virtual, do not create replicas or backup using Veeam itself for this. According to the Veeam best practices some data corruption problem may occur during the snapshot process used by Veeam, so it is not recommended.
The correct thing is to always back up Veeam settings that are already configured by default after installing Veeam for the first time, as in the image below:
This backup is nothing more than a file that contains all the settings of your Veeam server, this includes all objects, Jobs, sessions, etc. An example of the backup file:
With this file, if we lose our Veeam server we can reinstall on a new server and load the last backup. With this we will have all the settings and Jobs and the server will be fully functional. Although the backup is already set by default, it does not follow some recommendations of Veeam and so we must change some settings. The first and most important thing is that we should not record our backup on the Veeam server itself, or if a disaster strikes our Veeam settings backup files will also be lost.
The only option to burn our Veeam configuration backup files is by using Veeam repositories. So our first step is to create a repository that points to a location outside our server. It can be any of the available options in creating repositories. In this case I will use the "Shared Folder" option.
In "Backup Repositories" we will create a new repository by clicking "Add Backup Repository".
Define a name and click "Next."
Choose the option that best suits your environment, in which case I want to create a repository that is a shared folder. Click "Next" to proceed.
On the next screen just set the share where you want to save the backup files. If necessary we can also define the credentials to access this share. Click "Next" to proceed.
In the next screen we can define the amount of tasks that can run in this repository and also limit the I / O. Because this repository will only be used to write Veeam settings back up, I will keep everything in the tool's default. Click "Next" to proceed.
In the "Mount Server" screen you can keep the settings and click "Next".
Click "Finish" to finish creating the repository.
Now that we have the repository created we can change the backup settings. Select the new repository.
Set the amount of restore points you want to store in the repository. The default is 10, but I'll just keep 5. Also set the time that the backup of settings will start each day.
Lastly, we must encrypt this backup to keep it protected. If any backup job on your Veeam server already uses encryption then it is mandatory to enable encryption in the backup configuration as well.
By clicking "Backup Now" we can generate a backup file immediately. The file will be saved to the repository successfully.
That's it, people.
Any questions about the backup configuration can be checked in the Veeam documentation CLICKING HERE.