Hyper-V Plugin Version 201.5.1 (alpha) - Release Notes

Hyper-V Plugin Version 201.5.1 (alpha) - Release Notes

About Hyper-V Plugin

Hyper-V Plugin provides protection proactive monitoring for Microsoft Hyper-V Server environment’s configuration data, services, and application data files. 
Hyper-V Plugin automatically detects the Hyper-V role installed on the Windows server and protects its associated services, configuration, as well as all the managed VMs hard drive files (vhd(x), avhd(x)), configuration files, and snapshots stored locally on the server. 

Supported Versions

  1. Microsoft Hyper-V Server Role installed on standalone (non-clustered):
    1. Windows Server 2019 Standard and Datacenter (Desktop Experience)
    2. Windows Server 2016 Standard and Datacenter (Desktop Experience)

Monitoring

Hyper-V Plugin monitoring consists of the following:
  1. Service Availability Monitoring
  2. Application Monitoring
  3. Protected Data Monitoring and Replication

Service Availability Monitoring

Neverfail Continuity Engine monitors services specified by the plugins to ensure application availability. In the event a specified service stops or fails, Continuity Engine can take up to three pre-configured actions to remedy the issue.
When the plugin is being installed, all the protected services will be set to Manual startup type, unless otherwise stated.
This is the list of all services protected by this plugin:
  1. Hyper-V Virtual Machine Management - Automatic/Running (default)
  2. Hyper-V Host Compute Service - Automatic/Running (default)
  3. Hyper-V Data Exchange Service - Manual/Stopped (default)
  4. Hyper-V Guest Service Interface - Manual/Stopped (default)
  5. Hyper-V Guest Shutdown Service - Manual/Stopped (default)
  6. Hyper-V Heartbeat Service - Manual/Stopped (default)
  7. Hyper-V PowerShell Direct Service - Manual/Stopped (default)
  8. Hyper-V Remote Desktop Virtualization Service - Manual/Stopped (default)
  9. Hyper-V Time Synchronization Service - Manual/Stopped (default)
  10. Hyper-V Volume Shadow Copy Requestor - Manual/Stopped (default)

Application Monitoring

  1. Tasks - The following 'Tasks' are installed by Hyper-V Plugin:
  2. Pre Stop
  3. Post Start
  4. Periodic
    1. Protected Services Discovery
    2. File Filter Discovery
    3. Registry Filter Discovery
Hyper-V Pre Stop task
      Triggers a  powerShell cmdlet  that stops all the managed Hyper-V VMs. This task is triggered before Hyper-V service has been successfully stopped, and is intended to run before the protected application services are gracefully stopped, when switching the active server (during a switchover).
Hyper-V Post Start task
      Triggers a  powerShell cmdlet  that starts all the Hyper-V VMs. This task is triggered after Hyper-V service has been successfully started, and is intended to run after the protected applications are gracefully started, when switching the active server (during a switchover or failover).
To configure/modify Periodic 'Tasks', follow the steps below:
  1. Using the Neverfail Continuity Engine Management Service UI, go to Protected Server -> Tasks 
  2. Edit the desired 'Task'.
  3. Configure/modify the 'Interval' field.
  4. Click OK to save the changes.
Note: 'Interval' is the only field available for configuration/modification and is measured in seconds.
Note: One can also Enable/Disable the selected 'Task' (it is recommended to leave it Enabled)

Protected Data Monitoring and Replication

When the Hyper-V Plugin is being installed, it detects the Hyper-V feature configuration data files, registries, application and user data associated with the Hyper-V server as well as  all the managed VMs hard drive files (vhd(x), avhd(x)) . These data items will be detected then added to the protected set by the plugin's automatic filter discovery mechanism (their contents will be synchronized, and subsequent updates replicated to the passive server).
The plugin's filter discovery mechanism automatically detects and includes in data protected set only the in-use VMs virtual disk file which may be the vhd(x) (virtual disk files) or avhd(x) (snapshot files).  This is intended to be a replication optimization: i.e. the protected data set is dynamically updated to contain just the disk files which are subject to changes. All the other disk files not being in use should be already replicated on the passive nodes either via hosts' initial cloning (for files being created and not in use at the time Engine standby node was added) or via the replication mechanism (for disk files being in use at a previous moment, when Engine replication was on).

Installing the Hyper-V Plugin 

This is done automatically during Continuity Engine deployment driven from Engine Management Service if the Microsoft Hyper-V Server Role is detected as being installed on the target server. 

Known limitations

  1. Current design of Hyper-V Plugin defines Pre Stop and Post Start tasks which are starting/stopping all the managed Hyper-V VMs. More granular VM start/stop control can be achieved through user defined tasks (edited post-installation).
  2. Replication issues (Out of sync) are encountered when new VMs or VM Checkpoints are created from Hyper-V Manager: Automated Out Of Sync : Use of : Extended Attributes , has been detected for : *.vmcx and *.VMRS files.  Workarounds:
    1. (1) Manually triggering synchronize on the OOS files will put the server again in sync.
    2. (2) Disable the Extended Attributes unsupported features as suggested in How to Disable the Extended Attributes Unsupported Feature

Applies To

Hyper-V Plugin v201.5.1

 

 

 

 

 



    • Related Articles

    • Neverfail Continuity Engine 14 Release Notes

      Summary The following information applies to the v14 release of Continuity Engine. Continuity Engine 14.1 This point release supersedes Neverfail Continuity Engine v14.0. What's New Schneider Electric Security Expert Plugin v201.5.1 Schneider ...

    • Neverfail Continuity Engine 15 Release Notes

      Summary The following information applies to the v15 release of Continuity Engine. Continuity Engine 15 This release supersedes Continuity Engine v14.1. What's New EMS Alerting based on Managed Server Telemetry The first chapter in unlocking advanced ...

    • Neverfail Continuity Engine 13 Release Notes

      Summary The following information applies to the v13 release of Continuity Engine. Continuity Engine 13 This point release supersedes Continuity Engine v12.1. What's New Better User Experience Subscription's Payment Status Exposed in EMS UI Starting ...

    • Neverfail Continuity Engine 2021 (v9.0) - Release Notes

      Summary This knowledge base article provides information about the v9.0 release of Neverfail Continuity Engine and all subsequent updates to this release. Neverfail Continuity Engine 2021 (v9.0) Update 4 The following information applies to the ...

    • How to install and configure Continuity Engine in DR non-Identical Hyper-V nodes scenario

      How to install and configure Engine in DR non-Identical HyperV nodes scenario Instructions Prerequisites: Production HyperV node is up and running. All the HyperV VMs running on this node have both vhdx and config files hosted on a local storage. ...