Loading...
Loading...
This article documents the configuration files on the Veeam Software Appliance that correspond to registry locations in Windows used for custom settings in Veeam Backup & Replication. Custom registry-based settings for Veeam Backup & Replication on Windows can also be applied to the Veeam Software Appliance. However, because the appliance runs on Linux, which does not use a registry hive, these settings must be placed in configuration files. These files can be customized through the Veeam Host Management Console.
Veeam Software Appliance configuration files are managed using the Veeam Host Management Console. For more information, review the following user guide page: Managing Configuration Files. Accessing Configuration Files Access the Veeam Host Management Console Web UI Select Logs and Services in the left-side Navigation panel. Select Host Configuration within the Logs and Services view. From here, you can search for a specific configuration file.See the table below for the registry to configuration file equivalent to know which one to edit.
Example This example uses the registry value shared and discussed on KB1230. Windows-based Registry Value Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\Value Name: InverseVssProtocolOrderValue Type: DWORD (32-Bit) ValueValue Data: 1 Veeam Software Appliance Configuration Value File: /etc/veeam/veeam_backup_and_replication.confSection: [root]Value: InverseVssProtocolOrder=1 Explanation As shown in the table above, the equivalent of HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\ is /etc/veeam/veeam_backup_and_replication.conf . Since the registry value is not being added to a subkey, the appropriate section header in the conf file is [root]. So the registry Value Name is entered into that section with an equal symbol (=) and the value needed, "1".
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.