#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
TRY NOW
book meeting
BACK TO KB LIST

How to Manually Collect Recovery Media Logs for Veeam Agent for Linux

KB ID: 4013
Product: Veeam Agent for Linux | 3.0 | 4.0 | 5.0 | 6.0 | 6.1 | 6.2 | 6.3 | 6.3.1 | 6.3.2 | 13
Published: 2020-09-16
Last Modified: 2024-09-11
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

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.

Cause

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.

Solution

  1. Boot the Veeam Recovery Media.
  2. Configure the network settings.
  3. In the Veeam Recovery Media menu, select Switch to command line.
  4. Run the command veeamconfig -v to determine the version of the Veeam Recovery Media.
    1. For 6.0 or newer, review the systemd-based Veeam Recovery Media section.
    2. 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.
    3. For 4.0 and older, review the init-based Veeam Recovery Media section.

For systemd-based Veeam Recovery Media

  1. Navigate to the /tmp directory.
cd /tmp
  1. Run the following command to generate Veeam logs in the current directory.
    The file created will be named veeam_logs_<date>_<time>.tar.gz
sudo veeamconfig grablogs
  1. Collect additional logs using the following command:
sudo tar -zcvf VeeamRecoveryMediaLogs.tar.gz /var/log
  1. Start the SSH service.
sudo service ssh start
  1. Assign a password to the veeamuser. In later steps, you will use this account and password to connect to the machine.
sudo passwd veeamuser
  1. Identify the IP address assigned to the Veeam Recovery Media live session.
 ip a
  1. Using WinSCP, or your preferred application, connect to the Veeam Recovery Media live session from another machine using the veeamuser account and the password you assigned in step 5.
  2. Collect the gzip log bundles created in Steps 2 and 3 from the /tmp/ folder:
    • veeam_logs_<date>_<time>.tar.gz
    • VeeamRecoveryMediaLogs.tar.gz

For init-based Veeam Recovery Media

  1. Run the cd /tmp command.
  2. 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.
  3. Run the tar -zcvf VeeamRecoveryMediaLogs.tar.gz /var/log command.
  4. Run the /etc/init.d/sshd start command.
  5. Run the passwd command and enter a temporary password for accessing the Veeam Recovery Media.
  6. Run the ip a command to determine the ip address of the Veeam Recovery Media.
  7. Connect to the Veeam Recovery Media from another machine using the SCP protocol through a program such as WinSCP. 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).

More Information

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.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

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

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.