BackupExec 12.5 on hosts vSphere 4.0 agent

Similar Questions

• locked host vSphere Client Forum

  Hello

  I can't post in the new forum to host vSphere Client. Is he blocked?

  Thank you

  Hello

  Yes, it seems to be blocked for users, I will inform the administrator on this subject.

  Thank you

  Tim

• How to use vGPU and vSGA both on the same host vSphere 6.0

  I tested vGPU on a host vSphere 6.0 to 6.1 of the Horizon, and I would now add a vSGA pool to this host. Only two physical GPU is used with the two vGPU vm that I turned on.

  My question is, what should I do to make this Host allow compatible vSGA VM turning on and share resources on the other two other GPU?  I put the office pool to use the 'Material' 3D rendering engine and added a VM pool.

  When I try to turn on the virtual machine, I get this error message in vSphere client Web:

  "GPU hardware is required but not available. The virtual machine will not start until the GPU resources are available or the virtual machine is configured to allow software rendering. »

  It's the output of command line gpuvm and nvidia-smi:

  

  The host ESXi 6.0 has two cards of K2 of GRID for a total of 4 GPUS. Only two vGPU-enabled vm is turned on, it seems that I can use the other two GPU for vSGA VM, right?

  It is currently not possible since the Nvidia VIB:s vSGA and vGPU cannot be loaded at the same time.

  The driver will claim all compatible GPU:s (except those configured for passthrough, IE vDGA)

  An exception to this rule is if you have an AMD GPU for vSGA and a Nvidia GPU for vGPU.

  Can't comment on if, and when this will be resolved, perhaps krd can do.

  Linjo

• One migrated from my virtual machine to another host VSphere and it does not start

  I have a virtual machine that I've initially converted to Hyper-V to host VSphere. After I did it would start very well, but I got up two errors when starting.

  "An IDE controller is found but the VM does not support the option" and

  "A plate supporting the option not found."

  When I looked at the hard drive in the settings it looks like it is not supported. Is it because I badly converted to Hyper-V to VSphere using VMWare Converter?

  But now, I configure VCenter Server and tested a migration of these machines to another host and using the VSphere Client. It does not start now. I get an error message that says.

  "Device 'drive hard 1' uses a controller that is not supported." This is a general limitation of the compatibility of the virtual machine with the selected host ESXi version. »

  Remember that it is the same VSphere host it is running on initially. Any suggestion would be appreciated.

  If it works now - is that correct? n ' forget not to award points useful and/or correct

  I removed these entries;

  ide0:0. FileName = 'PIC-JVM-v0001 - 000001.vmdk ".
  IDE1:0. Present = 'TRUE '.
  IDE1:0.clientDevice = 'TRUE '.
  IDE1:0. DeviceType = "cdrom-raw"
  IDE1:0.startConnected = "FALSE".
  ide0:0. Redo = «»
  IDE1:0. FileName = ' / usr/lib/vmware/isoimages/windows.iso '.
  scsi0:0. DeviceType = "scsi-passthru.
  scsi0:0. FileName = ' / vmfs/devices/cdrom/mpx.vmhba1:C0:T0:L0 '.
  scsi0:0.allowGuestConnectionControl = "FALSE".

  And added to them;

  ide0:0.clientDevice = 'true '.
  ide0:0. DeviceType = "cdrom-raw"
  ide0:0.startConnected = "false".
  scsi0:0. FileName = 'PIC-JVM-v0001 - 000001.vmdk ".
  scsi0:0. DeviceType = "scsi-disk" hard
  scsi0:0. Redo = «»

  Although there is a high probability that the other six you have to do will be similar to this, they will have to be assessed individually and modified accordingly.

  See you soon,.

  Jon

• Connect hosts vSphere 4.1 again Virtual Center 5.0?

  We have Virtual Center 4.1 and all our hosts vSphere 4.1.

  I want to install a new VC 5.0 with dvSwitch 4.1.

  Then I whant to disconnect our hosts vSphere 4.1 4.1 VC, and reconnect them to our VC 5.0.

  I have not created any dvSwitch on the new VC 5.0.

  When I reconnect hosts vSphere 4.1 to the new VC 5.0, are the old dvSwitches then created 4.1 on the new VC 5.0, so I did not need to create them, before I have to reconnect?

  When you create the vDS on the new vCenter you will need to create it as a 4.1 vDS your host still being 4.1.

  You must disconnect and remove your host of your old VC (and former vDS) and then an add-in host on the new Victoria Cross.  After you have added the host of the new Victoria Cross you need to connect them to the new vDS.

  Best thing maybe create standard switches on hosts and migrate all your VMS and vmks to that.  Unplug and remove from current VC.  Add the host to the new CR.  Set and migration of networks to vDS.  This will reduce also any potential stop (against briefly during the network of back migration service VDS standard).

  Hope that makes sense.

  Hersey

  MauroBonder Posted the KB which describes the process a little better that I did.

  Post edited by: herseyc

• flow of traffic inside and off-host vSphere

  Our security team dislikes the vShield solution, we have in place, and they want to retire-

  Now, I need to understand exactly where the packages are forced out the virtual switch until the physical switch where our security can inspect the packages with its firewall of choice.

  Here's what I know:

  (1) the packets intended for one VLAN different will leave the port of the host group------vswitch via the uplink to the switch upstream vmnic - this allows deep packet inspection

  (2) I can create ports with different VLAN ID groups that rely on the same subnet addressing

  BUT - packages of VMS in port VLAN separate groups which are essentially on the same subnet actually leave the vswitch via the uplink to the physical switch?

  or the vswitch will recognize that the package is on the same subnet, regardless of the different VLAN ID and keep it in the host vswitch?

  Also, if I had to create multiple groups of ports with the same VLAN ID, moving between these port groups automatically packages would send to the switch upstream simply because they are in groups of different ports or will stay within the host vSwitch as the VLAN ID is the same?

  Thanks for help in advance!

  Hello

  Your security team should seriously rethink their thoughts all around security of virtualization. What they offer is a situation "Hairpin", which will treble the bandwidth required to operate a virtual environment. It also does not correctly account internal segmentation of virtual hosts. They need a solution that extends from their physical firewall solution in the virtual environment. I have been asked many times and frankly by using a physical Firewall in a virtual environment is just a horrible solution. It will not work in the cloud and it work well in a virtual environment, I know.

  I have layers of virtual switches within my environment and there is absolutely no physical firewall that can match what I do without resorting to tools that are not actually of security tools. VLANs are these tools actually. Instead I suggest using internal segmentation firewall or virtual firewall. Almost every manufacturer firewall is a virtual version of their firewall and I would go in that direction.

  Please check your security team a usable Secure Hybrid Cloud reference Architecture that extends from firewalls in virtual and cloud environments: Secure Hybrid Cloud Reference Architecture

  In response to your ideas:

  In general the different VLANS can leave the uplink or go to the following top switch, etc. Same VLAN ID implies the vswitch will route between these exchanges. So no, they wouldn't let me. So why you really need to integrate virtual firewalls in your environment.

  This isn't a construction of distributed firewall but place the edges between each of your security zones. There are 3 types of firewall distributed as well.

  The Ark of ref is a little dated, but the concepts have not changed. It is updated even as I write this.

  Let me know if you have any other questions.

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009-2015

  Author of the books ' VMWare ESX and ESXi in the business: Planning Server Virtualization Deployment, Copyright 2011 Pearson Education. ' Of VMware VSphere and Virtual Infrastructure Security: securing the virtual environment ', Copyright 2009 Pearson Education.

  Virtualization and Cloud Security Analyst: The Practice of virtualization, LLC - vSphere Upgrade Saga - virtualization security Table round Podcast

• Failed to connect to client host vsphere and Vcenter also esxi.

  Hi all

  I am trying to connect to the ESXi 5 of vsphere client host. I get the error message:

  vSphere client cannot connect to < ip > an unknown connection error has occurred. (The request has failed because the remote server has taken too long to respond. (L'opération a expirer)).

  and of VCENTR I am trying to add this host. I get the error. Of"request timed out".

  I can connect to the shell of ESXi and restart the vpxa services and spend. I can ping to esi IP host. but just cannot connect to it.

  earlier, he the host showed as disconnected in Vcenter. I tried to plug it failed. so I took it off I think can re add back. It did not work.

  I can just connect to client as esx host.

  kindly advice.

  Thank you

  Hello

  I am able to connect now.

  I noticed as I said previously, unable to connect to the localhost error when running esxcli. Unable to connect using the vsphere client. Unable to connect using VCenter.

  So I started to dig that's wrong with the OS esxi. and began running a few commands information esxcfg etc file system use of space, inode inconsistency, a few other commands such vdh, df to check the file system.  . and but has not changed anything. network configuration is correct.

  in these I run services.sh reboot, restart vpxa, pass reboot, restart host, check the logs, vmkernel, vpxa newspapers spend., check the date and time of the host.  I couldnot Firewall check since esxcli did not work. I haven't checked listed above step on the SSO.

  If you type esx and double tab, you will see many orders. I started testing on these orders.  so esxcli was a single command I tried later. It worked all of a sudden.

  Once esxcli has started working, I checked vsphere client to connect to esx host that it worked. then I was able to connect in Vcenter also.

  Thank you for your support

  -Caroline

  UNITED ARAB EMIRATES

• Recent update knocked out 5.1 client to access hosts vSphere

  Hello

  I have 2 hosts managed by vCenter in 5.1.  I had not applied the patches in a few months and decided to update via the Update Manager.

  After you apply the patches on 1 host, I found that I could not connect directly from the vSphere client.  Thought it was a fluke, so I applied the patches to the 2nd host this morning and it's the same thing.  Good thing vCenter still works. These are production areas.

  Patches/updates that I applied were the following:

  ESXi510-201401103-SG

  ESXi510-201401201-UG

  ESXi510-201401203-UG

  ESXi510-201401204-UG

  ESXi510-201401205-UG

  ESXi510-201401206-UG

  ESXi510-201401207-UG

  ESXi510-201401208-UG

  ESXi510-201401101-SG

  ESXi510-201401102-SG

  ESXi510-201401202-SG

  ESXi510-Update02

  Does anyone have any suggestions on how to correct this problem or find patch which plunged the connectivity?

  The error I get in return (what is now) is:

  vSphere Client could not connect to "10.0.0.5.

  A unknown connection error has occurred. (The client may not send a request to the server. (La connexion sous-jacente a été fermée: une erreur inattendue s'est produite sur un envoi.))

  I studied it in the KB and not to apply the usual steps, they said - I can ping the hosts, both via vCenter access and connect with root.

  It is even possible to regularize patches?

  -Ben

  It's actually the part 'ESXi' of Ko you want to watch. The other parts are associated with vCenter Server. According to this KB and several articles of MS, there is no patch for the edition of XP 32 - bit, so change the ESXi host is perhaps the only option.

  André

• VI3 vm LUN at the recommendation of hosts vsphere 4.1

  Hello

  "Note: virtual machines created in an environment of ESX 3.x will work perfectly on ESX 3.x and 4.x hosts." However, when you upgrade the virtual machine virtual material it can only run on ESX 4.x. If you have a mixed environment of hosts 3.x and 4.x, do not improve the virtual material until all ESX hosts have been improved in 4.x. "If the virtual hardware is upgraded before upgrading your ESX 3.x host, then your VMs can only lie on your hosts 4.x.

  I'm looking for the best way to get the VM manged VI3.5 platform, servers, and storage in vsphere 4.1 vsphere Platform of servers and storage.

  What that means I can the current map VI 3.5 to a newly configured LUNS ESXi 4.1 vsphere servers and re platforrm inventory the VM from the installed hosts recently updated?

  Can I map the new LUN storage system to the current VI3, 5 and use svmotion.pl to move them from the virtual computer to new LUNS, map the new LUNS to the new servers and re inventory them?

  What that means I can the current map VI 3.5 to a newly configured LUNS ESXi 4.1 vsphere servers and re platforrm inventory the VM from the installed hosts recently updated?

  Yes - there is a minimum change in VI 3.5 and ESXi 4.1 VMFS file system

  Can I map the new LUN storage system to the current VI3, 5 and use svmotion.pl to move them from the virtual computer to new LUNS, map the new LUNS to the new servers and re inventory them?

  You can it is not necessary

  Maybe support - upgrade to VMware vSphere 4 http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf Guide

• Unable to ping Virtual Machines within ESXi host (vSphere Home Lab)

  I'm using VMware workstation 9, I have 4 virtual machines created inside the workstation.
  (192.168.1.0 network is defined inside VMware workstation VM network editor)

  Domain controller - 192.168.1.1
  ESX1 - 192.168.1.11 (2 NICs - vmnic0 and vmnic1 connected to n/w)
  Esx2 - 192.168.1.12 (2 NICs - vmnic0 and vmnic1 connected to n/w)
  Management Server - 192.168.1.5

  I have 2 virtual computers created inside the machine Esx1

  machine to SQL - 192.168.1.4
  vcenter1 - 192.168.1.2

  I have 1 computer virtual created inside the Esx2 machine

  vcenter2 - 192.168.1.3

  I can ping all the machines in the administration server - no problem

  Question - I can not ping vcenter1 to sql, cannot ping vcenter1 to vcenter2, cannot ping vcenter2 to sql.
  There is basically no communication between virtual machines with the Esx host and in the whole of the host. Firewalls is disable on all these machines virtual esx internal hosts.

  Any ideas how to solve this problem?

  Make sure that virtual network on ESXi hosts maps are Sunrise promiscous mode networking.

• Using PowerCLI v5 on hosts vSphere 4.1

  Hi all

  Did anyone here tried PowerCLI v5?

  I wonder what would be the warnings to use it against ESX and ESXi 4.1 environment as I have no vSphere 5 installed immediately.

  I've been doing it for PowerCLI 5 came out.

  No obvious problems until now.

  See the Release Notes for known issues.

• host vsphere redimensionar c: sin tools do

  Hola

  How to use volume grow sin herramientas do?, the digo yo a UN disco una Máquina virtual than quiero increase knew tamano, luego en el discos del SO windows appears one administrator espacio no asignado, con extpart puedo hacerlo pero how the capabilities of vmware para extender en caliente?

  Gracias

  Hola,

  Hasta donde yo se not be you escapa none opcion en vSphere tal como comment.

  Las options than are para redimensionar los discos office son las that are conoces y hemos pointed el compañero y yo

  Best wishes / Saludos.

  Pablo

  Please consider providing any useful answer. Thank you!! - Por favor considered premiar las useful responses. ¡¡MUCHAS gracias!

  Virtually noob blog

• VSphere 5.0 agent vm

  Thank you all,

  What is the use of agent 5.0 vm. What is the best practice configuration.

  Thank you

  SIV

  A virtual agent is a virtual machine that performs a specific function for the virtual infrastructure. An example of a VM agent would be for example a vShield device Endpoint is an antivirus solution. By "tagging" this VM as VM agent ensure that this virtual machine gets power first in the event of a host failure. We do this to ensure that the service is available before all other virtual machines.

  It's the current order:

  • Agent of virtual machines
  • Secondary virtual machines of FT
  • Virtual machines configured with a reboot of the top priority,
  • Virtual machines configured with a medium restart priority
  • Restart of Virtual Machines configured with low priority

• BackupExec 2012 Agent for ESXi 5 host?

  We just move from ESX to ESXi 5 4.1.  We find that the BackupExec Agent of Linux is no longer talking to ESXi host 5.

  Just would like to ask you if there are any 2012 BackupExec for ESXi 5 Host Agent?

  Thank you

  As far as I know, we don't have Backup Exec for ESXi host agent. If you want to take a backup of the configuration files to can do this through the vCLI l command vicfg - cfgbackup.p

  http://pubs.VMware.com/vSphere-50/index.jsp?topic=/com.VMware.VCLI.GetStart.doc_50/cli_about.html

• Adding a VSphere 6 host to VCenter 5.5 device?

  Hi guys,.

  I have a VCenter 5.5 which I hope to use to handle a crowd of VSphere 6. Unfortunately, I can not add the host. I get the below error message:

  

  I made sure the hosts on the host files and the Center are correct, I've made sure to lock Mode is disabled on both, together, the time-out of handshake ssl on the two is set to 120000, rebooted several times on both, made sure the vCenter had a managed IP, administrators followed virtually everything in these articles :

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1005803

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1003735

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1027672

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1020210

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1008030

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003490

  Thus, this entire exercise was very informative for me, but has really got me anywhere.

  But then it came to me - can you even a 6 a 5.5 vCenter device host vSphere? I have to upgrade my vCenter?

  If I CAN manage the downtown v5.5-v6 host, what I am doing wrong or what should I be checking/do?

  Thanks in advance for you help.

  You first put your vCenter server to version 6, only then will you be able to manage 6 ESXi host.