OPERATIONAL DEFECT DATABASE
...
...
You cannot collect recovery media logs for Veeam Agent for Linux from the repository. In such a case, you can still manually collect recovery media logs from the Linux machine where the bare-metal restore is performed.
If the bare-metal restore is not completed, the recovery media does not export logs to the repository. As a result, the records must be manually gathered from the recovery media.
Boot the Veeam Recovery Media. Configure the network settings. In the Veeam Recovery Media menu, select Switch to command line. Run the command veeamconfig -v to determine the version of the Veeam Recovery Media. For 6.0 or newer, review the systemd-based Veeam Recovery Media section. For 5.0, run the command hostname to determine if the recovery media is init-based or systemd-based.For more details on the differences between Recovery Media image versions, refer to User Guide. If the hostname output is veeam-recovery-iso, review the systemd-based Veeam Recovery Media section. If the hostname output is veeam-recovery-media, review the init-based Veeam Recovery Media section. For 4.0 and older, review the init-based Veeam Recovery Media section.
The recovery media is not persistent across reboots. Rebooting resets all the settings and changes made in the steps above. The recovery media version can be determined by running the veeamconfig -v command from the shell after step 3. If the restore process is completed (regardless of the result), Recovery Media logs are automatically exported to the location of backup files.
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
