INTRODUCTION
The recent release of Veeam Backup & Replication 13 has certainly brought a breath of fresh air to the Veeam world.
With the introduction of the Linux-based VSA (Veeam Software Appliance), we now have a new backup server concept, with many additional features and, above all, an extra eye on security.
But as with all new features, we need to pay attention to the prerequisites, carefully evaluating any integrations with what we had configured in our old and beloved Windows version.
An example that stands out: Custom Settings.
VSA – CUSTOM SETTINGS
In the standard version, whenever a particular setting needs to be applied that cannot be configured via the console, a registry key must be added.
In Windows, for example, the registry path that allows you to enter custom values for the backup server is HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\.
Among the most common configurations are, for example:
- Enable support for DDBOOST – Governance Mode
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: DDBoostSkipComplianceModeCheck
Value Type: DWORD (32-Bit) Value
Value Data: 1
- Force the priority use of networkless connections (VIX) for guest processing at disadvantage of the RPC protocol
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: InverseVssProtocolOrder
Value Type: DWORD (32-Bit) Value
Value Data: 1
In the Linux-based VSA, of course, we do not find a registry of this type.
These custom settings are saved in configuration files.
For example, the correspondence for the backup server section is:
| Registry Key | VSA Config File |
| HKLM\SOFTWARE\Veeam\Veeam Backup and Replication | /etc/veeam/veeam_backup_and_replication.conf |
If the parameter does not need to be entered in a subkey, the corresponding section will be [root].
The configuration files can be accessed via the new Veeam Host Management Console, a web interface for accessing the administrative management section of the appliance.
We recommend downloading the desired file, modifying it, and uploading it from the same console.
NB: if the Security Officer role is active, uploading a configuration file requires approval by a user with this role.
All changes made to configuration files are saved in a corresponding log file.
For example, for the backup server section, it is reported in /var/log/VeeamBackup/RegistryOptions/veeam_backup_and_replication.conf.log
CONCLUSION
We have seen how the new features of v13 are certainly interesting, but they require some further study and on-the-job training to be managed effectively.
PS: detailed information on VSA custom settings can be found in KB4779.
Enjoy! 💚