https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMDE5IiwiaGFzaCI6IjhlMjhjZjA5LTgzNWItNDkyMS1iNTY3LTM0MzI1ZTM0OGNiMSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Adding Linux repository to Veeam hangs on volume discovery and fails silently

Challenge

When connecting to a Linux repository with Veeam, the connection hangs on the volume discovery step and silently errors out. 

Cause

When Veeam connects to a Linux target the SSH session is opened without a TTY. In some versions of Linux (particularly recent releases of CentOS such as 6.6. and 7, and RHEL5 and higher), this is caused by RequireTTY being set as a default option in the /etc/sudoers file.

Solution

Note: A reboot may be required.
 
To disable RequireTTY globally:
1. Run visudo
2. Find the line for requiretty
3. Comment it out
 
To disable RequireTTY for a specific user:
1. Run the command visudo
2. Create a new line Defaults:<username> !requiretty
Where <username> is the Linux username given to Veeam Backup & Replication when adding the NFS repository.
KB ID:
2019
Product:
Veeam Backup & Replication
Version:
6.x, 7.x, 8.x
Published:
2015-03-26
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later