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.
Collect the gzip log bundles created in Steps 2 and 3 from the /tmp/ folder:
For init-based Veeam Recovery Media
Run the cd /tmp command.
Run the veeamconfig grablogs (for the Veeam Recovery Media version 4.0 or later) or veeamconfig config grablogs (for Veeam Recovery Media versions up to 3.0.2) command to create the veeam_logs_<date>_<time>.tar.gz archive in /tmp directory.
Run the tar -zcvf VeeamRecoveryMediaLogs.tar.gz /var/log command.
Run the /etc/init.d/sshd start command.
Run the passwd command and enter a temporary password for accessing the Veeam Recovery Media.
Run the ip a command to determine the ip address of the Veeam Recovery Media.
Connect to the Veeam Recovery Media from another machine using the SCP protocol through a program such as WinSCP or FileZilla. Use the root account with password from step 5 and the information gathered from steps 2 (/tmp/veeam_logs_<date>_<time>.tar.gz) and 3 (/tmp/VeeamRecoveryMediaLogs.tar.gz). (The log bundle will be in /tmp).
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.
To submit feedback regarding this article, please click this link: Send Article Feedback To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Your feedback has been received and will be reviewed.