Used with source Linux servers.
This article provides instructions on how to use a non-root account with PlateSpin Protect, Migrate, or Forge when using a supported Linux source server.
Note: SSH access is not required for ESX 3.5 and above or ESXi servers, there is no requirement for root or sudo access when working with these servers. For details on permissions required for ESX 3.5 and higher servers see the document linked at the bottom of this article.
PlateSpin v5.5 and higher includes the ability to use a non-root account. In order to use a non-root or "sudo" account, please use the below steps. In addition, please use the document "Minimum Privileges for ESX 3.5" attached to this article as another method to add a an account with the necessary permissions to your ESX 3.5 server -to download the instructions document please click here
- On the Linux server, create a new user account. As root, type the following command:
useradd -G wheel -m -d /home/psuser psuser -> where psuser is the name of the new user account
After creating the new user account, set a password by typing the following command:
- Add the new user account to the sudoers file to allow the user to run the "sudo" command. As root type:
The above command should display the following (necessary additions/changes are bold in red):
Linux Sample Sudoers file:
# sudoers file.
# This file MUST be edited with the 'visudo' command as root.
# See the sudoers man page for the details on how to write a sudoers file.
# Host alias specification
# User alias specification
# Cmnd alias specification
# Defaults specification
# User privilege specification
root ALL=(ALL) ALL
psuser ALL=(ALL) ALL ------> ADDING THIS LINE WILL ALLOW THE NEW USER TO RUN SUDO
# Uncomment to allow people in group wheel to run all commands
# %wheel ALL=(ALL) ALL ------> UNCOMMENT THIS LINE TO ALLOW WHEEL GROUP MEMBERS TO RUN SUDO
# Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
- Discover the Linux server using the new user account
In addition to this please review the following KB article which discusses the error which you may recieve if the accounts are not configured correctly.TID 7920795