licensing be vray
Created: 15 Jan 2013 | Updated: 16 Jan 2013 | 8 comments
This issue has been solved. See solution.
There is some hosts on which spining VM with exchange server e .t.c If one host droped it connect to other.So the question ,i must have license on each host or mb some other ways?
Discussion Filed Under:
Comments 8 Comments • Jump to latest comment
Hi,
Yes, you license per host...just conform to what Symantec's licensing requirements are and you should be fine.
Check below:
http://eval.symantec.com/mktginfo/enterprise/fact_...
Thanks!
If you find this is a solution, please mark it as such.
Thx.Is there no way to circumvent this?
I'm not quite sure why you would short-change your protection of your virtual environment? If the VMs VMotion onto an unprotected host, the backups fail...if they'd even run in the first place. You license per CPU per host...if you have 2 licenses but 4 CPUs, I don't think V-Ray is going to run correctly.
Take the plunge, buy the necessary licenses and you won't get nailed for backups that don't run when the chips are down!
If you find this is a solution, please mark it as such.
Can u please tell more about licensing per host, symantec connect straight to host or connect to VMs on the host?thx )
Licensing is per CPU on a host...2 hosts with 2 CPUs (physical sockets) = 4 V-Ray licenses.
You would connect through the Virtual Center server, not through an individual host.
If you find this is a solution, please mark it as such.
About licensing understand. Try to find information about technical information about communication with hosts, but very little information about it,can u give a bit information? Thx a lot for help )
V-Ray is the same as AVVI...it will do backups the same way. You can check the Admin Guide for further information.
Thanks!
If you find this is a solution, please mark it as such.
With the V-Ray licence, you don't have to worry about the number of hosts that you have. You pay for the total number of CPU sockets in all your VM hosts (one V-Ray licence per socket) and you are covered. See this blog
https://www-secure.symantec.com/connect/blogs/what...
Would you like to reply?
Login or Register to post your comment.