Comprehensive data protection for all workloads
Post Reply
eric
Enthusiast
Posts: 39
Liked: never
Joined: Jan 01, 2006 1:01 am
Contact:

Error in elavating to superuser....

Post by eric »

Hello All,

I have an older version of Veeam, 2.0 (i know's it's old but it (was) working fine) and trying to connect to a 4.1 ESX host. I am getting the following error; Error in elavating to superuser. Error sudo disabling sudo: sorry, you must have a tty to run sudo.

I can login with Putty and elevate fine. Am I missing something here?

~E

Bunce
Expert
Posts: 259
Liked: 8 times
Joined: Sep 18, 2009 9:56 am
Full Name: Andrew
Location: Adelaide, Australia
Contact:

Re: Error in elavating to superuser....

Post by Bunce »

Are you sure you can elevate OK via Putty? VMWare changed the security model in 4.1. If you google SSH Access vshpere 4.1 you'll get plenty of hits.

Gostev
SVP, Product Management
Posts: 26679
Liked: 4268 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Error in elavating to superuser....

Post by Gostev »

There was a change in ESX 4.0 that made old elevation code not working, so we had to address this in later Veeam Backup release (I can't remember which Veeam Backup release, it was over a year ago).

eric
Enthusiast
Posts: 39
Liked: never
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Error in elavating to superuser....

Post by eric »

Yes, I can elevate properly.

I checked the sudoers file and the user is in the file.

username ALL=(root) NOPASSWD: ALL

Is there anyway to manually work around this?

Vitaliy S.
Product Manager
Posts: 24243
Liked: 1859 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Error in elavating to superuser....

Post by Vitaliy S. »

I'm afraid you should either use the latest version of Veeam B&R or use root to connect to your ESX 4.0 host.

Gostev
SVP, Product Management
Posts: 26679
Liked: 4268 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Error in elavating to superuser....

Post by Gostev »

If I am not mistaken, commenting the following line in the sudoers file on ESX 4.0 will help:

Code: Select all

Defaults    requiretty
But I would highly recommend upgrating to the latest version anyway - 1000x times better reliability (due to transactional backup storage added in v4), and 20x faster backup (on ESX4, due to changed block tracking) alone should be enough to justify the upgrade from Veeam Backup 2.0... you really are not doing yourself any good by sticking with v2 (which will soon be 3 year old).

eric
Enthusiast
Posts: 39
Liked: never
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Error in elavating to superuser....

Post by eric »

Thanks, that got it.

As for upgrading, this is a small installation and 2.0 works fine for now. Going to 5.0 would add complexity that is not necessary right now...

Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 37 guests