Jump to content


Can't see Hyper-V Virtual Machines

This topic has been archived. This means that you cannot reply to this topic.
3 replies to this topic

#1 Admin Haehl

Admin Haehl
  • Members
  • 0 posts

Posted 07 September 2010 - 11:31 AM

After move the database from Server1 to Server2 (who was before a tapeware-client) i can`t see the Hyper-V Connector any more !On Server2 i uninstalled YSB and installed it new (as backup-domain-server).With YSB-service disabled i moved then database-folder from server1 to server2.on server2 i corrected the ytconfig.ini
[configuration]nodeName=SERVER1 databaseServerAddress=SERVER2isDatabaseServer=No[domainList]SERVER2
After Restart On both Servers everything is okexcept the Hyper-V Connecter don't show up(for the VM on server2)What can i do ?Regards,Roland

#2 Ben Kloos

Ben Kloos
  • Barracuda Team Members
  • 10 posts

Posted 07 September 2010 - 03:39 PM

On this server could you run 'vssadmin list writers'In your list you should see the Hyper-V writer similar to my example bellow. If it is listed YSB should see it.C:UsersAdministrator>vssadmin list writersvssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool© Copyright 2001-2005 Microsoft Corp.Writer name: 'Microsoft Hyper-V VSS Writer' Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Instance Id: {f74936a6-8530-45ae-a82f-557ed350d085} State: [1] Stable Last error: No error

#3 Harald Steindl

Harald Steindl
  • Members
  • 15 posts

Posted 23 May 2014 - 09:07 AM

Sorry to hijack this old thread but I just added a Server2012 (non-R2) to my setup and it does not show Hyper-V under Selection while creating a new backup job.

So I am not only missing the Actual VMs but the whole Hyper-V section.


Running 10.2 and seeing all my Server2008 Hyper-V guests. And YES, I vssadmin also lists the "Mircosoft Hyper-V VSS Writer" with 0 errors.


Honestly dont know anymore, but could it be, that I installed the backup software before I the installed Hyper-V role?? Re-install the YT-software?


thanks for your support.

#4 Matt Orme

Matt Orme
  • Moderators
  • 463 posts

Posted 27 May 2014 - 09:59 AM



Could you try restarting the service on the Hyper-V host?