Hi,
I have VRanger configured to work with a single esx host and we are using Virtual centre.
When I start the backup of a live vm it sits on performing backup and nothing appears in thedestination folder
Any ideas?
Did you create user accounts on your ESX server(s) for vRanger to use?
Are you connecting directly to the ESX server(s) or to the VC server?
Are you behind a firewall?
________________________________
Jason D. Langdon
Hi,
thanks for the fast responce
no I am using the root account. If I create a new account and add it to the ESX host what permissions should I give it?
It is connecting to the VC
No firewall
Does ROOT have SSH access to your ESX server(s)?
________________________________
Jason D. Langdon
yes it does. I just tried putty to the ESX host and could login
Try this:
1) Create a standard user account on the ESX server called vRanger wit a standard password. (useradd vRanger / passwd vRanger password)
2) Create a standard user account on the VC server called vRanger with the same password as the account created above
3) Make the Windows vRanger account an administrator of Virtual Center
4) Reconfigure vRanger to use the vRanger account instead of ROOT
5) Disable ROOT SSH access to the ESX host server
This may not solve your problem but it will rule out an authentication issue.
________________________________
Jason D. Langdon
Hi,
I get the following:
:: esxRanger PRO CLI Backup Commencing ::
Version: 3.0.2574.21666
"C:\Program Files\vizioncore\esxRanger Professional\esxrangerprocli.exe" 10.1.2.241 "[VMSANSTORE] SOLSEARCH/SOLSEARCH.vmx" -copylocal "Z:\SolSearch\new" "-drives:all" -zipname "[config]_[weeknum]" -compratio 1 -noquiesce -retendays 31 -totalasync 10 -hostasync 2 -lunasync 3 -nospacecheck -vmkey vm-542 -temp /
The TarBall name will be: SOLSEARCH_2.
Compression Ratio: 1
Not checking free space!
VirtualCenter VM Key: vm-542.
Caught Exception : Name : SoapException Message : Permission to perform this operation was denied Trace : at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Vizioncore.Vmware.Vim.VimService.Login(ManagedObjectReference _this, String userName, String password, String locale)
at Vizioncore.Vmware.Vim.SvcConnection.Connect()
at ClientUtils.ServiceUtil.ClientConnect()
Unable to Find The VM: SOLSEARCH/SOLSEARCH.vmx
Is this before or after creating the user accounts I suggested?
________________________________
Jason D. Langdon
after creating the user account you suggested.
no errors when I did use root as the account
How is your vRanger deployed? What OS do you have it installed on? That SOAP error to me sounds like something on the vRanger host is not correct. Also, on that host are there any utilities like CSA or other application level firewalls that would stop a process from running?
Regards...
Jamie
If you found this information useful, please consider awarding points for "Correct" or "Helpful".
Remember, if it's not one thing, it's your mother...
How is your vRanger deployed? What OS do you have it installed on? That SOAP error to me sounds like something on the vRanger host is not correct. Also, on that host are there any utilities like CSA or other application level firewalls that would stop a process from running?
My thinking is that the problem lies with the accounts he's using. Since authentication is not shared between VC and ESX he needs to ensure that the account he's using has the correct level or permissions to connect to the device he's attempting to connect to. I founf that the easiest way to do this is to create both an ESX account and a VC account with the same name and password combination.
________________________________
Jason D. Langdon
vRanger only uses VC to know what pHosts are there, where a VM resides, etc. There are two modes. It sounds like he is using VC mode. Now, as far as authentication, you are correct. He did indicate that he was using root, which is not the best practice. So if he creates a new user on the host he can config vRanger to use that account but he still must provice the root password so that vRanger can SU to perform the functions it needs to do the backup.
I would suggest installing vRanger on another box, like an XP workstation just to test. If a simple backup works from that install them something on his primary vRanger install isn't correct.
Regards...
Jamie
If you found this information useful, please consider awarding points for "Correct" or "Helpful".
Remember, if it's not one thing, it's your mother...
It is installed on a physical server running server 2003 standard. The VC is installed on the same server.
We don't have any application level firewalls and no CSA
should I try a reinstall?
Hello,
Moved to the ESX forum.
I would suggest contacting Vizioncore Support about this one either directly or via their Forum.
Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast
When you created the accounts that I suggested, did you reconfigure your HOIST servers to use the new account? If not, then you are trying to SSH to the host using the ROOT account which has not been disabled.
________________________________
Jason D. Langdon
Check you event logs on the windows server. look for any .net framework errors. also, check out this thread from vizioncore:
It has some similar issues to you.
Regards...
Jamie
If you found this information useful, please consider awarding points for "Correct" or "Helpful".
Remember, if it's not one thing, it's your mother...
yes I changed the account
thanks for your help
And you've also changed the VirtualCenter configurations in vRanger to use an account that has full administrative access to VirtualCenter, correct?
________________________________
Jason D. Langdon
yes, it is using an admin account
nothing of interest in the windows logs