Error Validating Hyper-v Machine Name
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Error Validating Hyper v Machine name Windows 2012... VOX : Backup and Recovery : NetBackup : Error Validating Hyper v Machine name Windows 2012... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Error Validating Hyper v Machine name Windows 2012 r2? (-1) error inn_kam Level 6 Partner Accredited 12-07-2014 09:53 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi windows 2008 Server NB 7.5.0.7 Netbackup Master Server Windows 2012 Server R2 Hyper V Clients NB 7.5.0.7 Host name entry on Master server of all 3 vms include in Hyper V Already added Now when making policy and adding in Client list it is giving this error error Validating Hyper v Machine name Server failed to list VM's (-1) So how will i resolve this error? Do i have to install nb7.5.0.6 Special Client agent on Hyper V ? As it is windows 2002 server R2? Solved! Go to Solution. Labels: 7.5 Backup and Recovery Error messages NetBackup Patch Windows Server (2003-2008) 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Correct. Normal NBU Client is Marianne Moderator Partner Tr
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : https://vox.veritas.com/t5/NetBackup/Error-Validating-Hyper-v-Machine-name-Windows-2012-r2-1-error/td-p/686512 Please enter a valid Hyper-V machine name VOX : Backup and Recovery : NetBackup : Please enter a valid Hyper-V machine name Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Please enter a valid Hyper-V https://vox.veritas.com/t5/NetBackup/Please-enter-a-valid-Hyper-V-machine-name/td-p/605438 machine name thesanman Level 6 12-02-2013 08:34 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I have a Hyper-V server running a number of VM's. Server is running 2012 R2 Hyper-V Core version; the powershell only one. Server has had the NBU v7.5.0.6 client installed and configured. Master server and Media server is also v7.5.0.6. When I try and configure a Hyper-V policy it fails when trying to validate the client as a Hyper-V host with the pop up box "Please enter a valid Hyper-V machine name". Examining the bpVMutil logs on the Hyper-V server shows the following: 15:19:22.263 [2680.3780] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpVMutil.exe 768 _NONE_ _NONE_ 15:19:22.263 [2680.3780] virt_test_log: log function is called 15:19:22.263 [2680.3780] <2> bpVMutil main: cmd = 3 ESXMount = _NONE_ ESXserver = _NONE_, flags = 0 15:19:22.263 [2680.3780] <2> bpVMutil main: ListHyperVVMs returned -1 15:19:22.263 [2680.3780] <2> bpVMutil main: EXIT STA
this channel Embed this content in your HTML Search confirm cancel Report adult content: click to rate: Account: (login) More Channels Showcase RSS Channel Showcase 3128385 RSS Channel Showcase 5465523 RSS http://backing89.rssing.com/chan-13942457/all_p34.html Channel Showcase 8612086 RSS Channel Showcase 9598298 Channel Catalog Subsection Catalog Articles on this Page (showing articles 661 to 680 of 1694) 12/19/13--05:51: _Reducing Media Set ... 12/19/13--06:05: _Backup to USB disk ... https://support.turbonomic.com/hc/en-us/articles/200681426-How-to-add-Microsoft-Hyper-V-Targets-to-the-VMTurbo-appliance 12/19/13--06:06: _A communications fa... 12/19/13--07:02: _Status 156 Snapshot... 12/19/13--07:10: _Backup 2012 SP3 wil... 12/19/13--07:45: _BUEXEC 2012 Servers... 12/19/13--08:26: _SQL Restore Failed 12/19/13--10:10: _current bprd log go... 12/19/13--13:02: _User Script is not ... 12/20/13--01:03: error validating _AOFO Error when not... 12/20/13--01:24: _Max Parent Job or m... 12/20/13--01:36: _BE 12.5 sometimes n... 12/20/13--04:16: _BusyBox Images 12/20/13--04:21: _support for Hyper-V... 12/20/13--06:10: _partial successful ... 12/20/13--07:06: _probleme backup new... 12/20/13--08:58: _Errors trying to ba... 12/20/13--13:41: _What is this file u... 12/21/13--05:34: _Backup Exec 2012 - ... 12/21/13--11:55: _Differential_Full_B... (showing articles 661 to 680 of 1694) Browse the Latest Snapshot Browsing All Articles (1694 Articles) error validating hyper-v Live Browser older | 1 | .... | 31 | 32 | 33 | (Page 34) | 35 | 36 | 37 | .... | 85 | newer 0 0 12/19/13--05:51: Reducing Media Set Size Contact us about this article I need a solution I am using Backup Exec 2010 R3. I have a media set that was set to hold 8 weeks of retetention. I now need space cleared on the drive its on (its not full yet, but i need space). I have lowered the retention to 4 weeks. The previous 4 weeks is not marked as over writable, but i need to delete it to free up space. I beleive Backup Exec is using deduplication. read more
0 0 12/19/13--06:05: Backup to USB disk on remote Server Contact us about this article I need a solution I have 500 GB share which increases in size very less. I was looking to backupo this share via symntec B2d to USB disk attched on same server with Share. What would be take less network bandwidth:- USB attached to media server with and agent on server with share? OR USB attached to Sermust provide 'domain\username' in the User Name field. In addition, the user that you specify must be one of the target server's "WBEM Scripting Locator" owners. Each Hyper-V server requires specific permissions to allow management via WMI. These permissions are set in the host’s WBEM Scripting Locator registry key. To set the permissions, you edit the registry key to add owners and grant them full control. To add an owner to the Hyper-V server’s registry key: Launch regedit on that machine as Administrator Find the following registry key: HKEY_CLASSES_ROOT\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6} Right click the key and choose Permissions Click Advanced and display the Owner tab In the owners list, add the user you want to allow to connect to the machine Click Ok Highlight the user and grant Full Control Note: For some versions of Windows (including Windows 2012 R2), there is also a second registry key that needs to be updated as shown above. Search for the following key in the registry: HKLM\Software\Classes\Wow6432Node\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6} If it exists, follow steps 1-7 above, for this key also. Once you have carried out the above steps, you can specify the Hyper-V server as an appliance target, using credentials for an owner that has Full Control privileges. If the discovery is still unsuccessful, you may have problems with firewall setup. There are many different firewalls, so we can offer the following general advice: The WMI protocol, communicates initially on port 135 (from VMTurbo to the Hyper-V server) Additionally, port 445 needs to be opened. Next, a random non-privileged port is chosen, to continue the conversation on (for example, 9942) Most firewalls are aware of this and 'follow' the conversation so allowing communications Microsoft's own default firewall setup does NOT allow this 'port change' So, you have two choices - either, lock down the WMI configuration on each target HyperV server so that a static port is chosen (see the following link for advice): MSDN - Configure WMI for a fixed port (opens in a new window) The firewall would then need to be opened for the VMTurbo appliance to talk on the port you chose. Alternatively, you may wish to instead configure the firewall to track WMI's 'port changing'. Most commercial firewalls already support this, but for Microsoft, the following command can be used to set enable this 'tracking': netsh advfirewall firewall add rule name = VMTurbo dir = in protocol = tcp action = allow localport = rpc remote