Double-Take Availability for VMware Infrastructure can use non-root accounts to set up and configure protection jobs. Double-Take Availability for VMware Infrastructure uses the sudo (super user do) program provided in ESX to set up a non-root account that can be used to setup and configure Double-Take Availability for VMware Infrastructure jobs.
Note:
|
VirtualCenter is required when configuring protections using non-root credentials. If VirtualCenter is not being used, then you must enter the root account credentials of the source and target ESX servers.
|
Before sudo can be used, it needs to be configured on any ESX server that is using a non-root account. Each host should have a non-privileged account configured. It does not have to be the same account.
To add a new user, perform the following steps on each host to be used as source or target.
- Log in as
root
, or login with a non-root account and use the sudo
command to transition to the root.
- Execute
adduser <username>
to create a user.
- Set a password for the newly created user:
passwd <username>
Configure sudo access for the newly-created user.
- Execute visudo. This should bring up the sudo configuration file (/etc/sudoers). Note that you should not edit that file directly.
- Add the following line to the sudo configuration file:
username ALL=(ALL) NOPASSWD: ALL
- Save the file and exit (
:w!
).
Verify that the sudo account has been configured correctly.
- Log out and re-login as a sudo account.
- Execute the following command to make sure you can access VMWare datastores on /vmfs/volumes/.../.... If the command succeeds (prints the contents of the root home folder), then sudo is configured correctly. If it fails with a “permission denied” error or prompts for a password, then sudo is misconfigured.
sudo ls ~root