How to use SFTP with Multi-OS FLR

KB ID: 2062
Product: Veeam Backup & Replication
Version: 7.x, 8.x, 9x
Published: 2015-09-08
Last Modified: 2020-08-13
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.

Purpose

This article documents how to use SFTP with Multi-OS FLR. This may be performed when the native Backup Browser is slow to react to folder changes or when use of a third-party tool such as rsync is desired.
 
Please note version Veeam Backup & Replication 8.0.0.817 through 8.0.0.2018 are not compatible with this method. Update 2 for v8 must be installed. http://www.veeam.com/updates.html

Solution

Prior to performing the Multi-OS FLR the helper appliance root password must be set.
https://helpcenter.veeam.com/docs/backup/vsphere/credentials_edit_delete.html?ver=95u4
https://helpcenter.veeam.com/docs/backup/hyperv/credentials_edit_delete.html?ver=95u4

User-added image

──────────────────────────────────────────────────────────
1. Launch Multi-OS FLR
──────────────────────────────────────────────────────────
 
Launch the Multi-OS FLR, and wait for the backup browser to appear.

Note: You do not need to enable the FTP server on appliance option unless you wish to connect via the Windows File Explorer.
https://helpcenter.veeam.com/docs/backup/vsphere/guest_restore_linux.html?ver=95u4
https://helpcenter.veeam.com/docs/backup/hyperv/guest_restore_linux.html?ver=95u4

 
──────────────────────────────────────────────────────────
2. Get IP address of helper appliance (if DHCP was used)
──────────────────────────────────────────────────────────
 
Connect to the console of the VeeamFLR appliance that was created as part of the restore.
 
Log in using the user name root and the password set in the credentials section.
 
Note: In VMware environments you can also find the IP address of the VeeamFLR appliance on its summary tab.

User-added image

──────────────────────────────────────────────────────────
Step 3. Connecting to the FLR appliance
──────────────────────────────────────────────────────────

User-added image

Connect to the appliance IP using an FTP tool such as Filezilla or WinSCP, though Windows File Explorer may also be used if the FTP option has been selected. Use the username root and the password configured for the Helper Appliance set in the first step. The example above uses the information from our examples in steps 1 and 2.

Navigate to /media/ and select the appropriate drive.
 
In Linux drives start with “sd”, then a letter “a-z” the drive, then each partition on that drive is represented by a number.
 
So first drive, first partition would be sda1.


 
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.