Avid Interplay Production Failover Cluster Host Network Driver Update Procedure

Overview: The act of applying network interface driver updates may introduce an error into the settings for the network adapters. To execute the driver updates it has been found that if the host node has the cluster service stopped before hand, the updates can be applied with no negative affects to the system.

Microsoft has several server backup references and as always, having a proper backup will mitigate any pain should “a bad thing happen”.

References:

Backup and Recovery Overview for R2 https://technet.microsoft.com/en-us/library/dd979562(v=ws.10).aspx

You can create a backup using the Backup Schedule Wizard to enable backups to be run on a regular schedule or using the Backup Once Wizard to run a one- backup. You can access both of these wizards from the Windows Server Backup Microsoft Management Console (MMC) snap-in. You can also create regular or one-time backups using the Wbadmin or Windows PowerShell cmdlets for Windows Server Backup.

Here are the articles below about the basic steps, you could take a look.

https://technet.microsoft.com/en-sg/library/cc753528.aspx

Windows Server 2012R2 - Backup http://www.c-sharpcorner.com/UploadFile/cd7c2e/how-to-create-backup-in-windows-server-2012/

http://krypted.com/windows-server/use-windows-backup-to-back-up-windows-server-2012/

Page | 1

Network Driver Update Steps:

The updates will require a fail some point so please the times and actions to be when a fail over of the Avid Workgroup server service will have a minimal production impact.

Cluster Host Update Steps:

 Distribute the driver updates so as to be on the host local drives for safety (network updates over the network are not recommended by Avid Systems Engineering) .  Determine what host is active for the Avid Interplay Workgroup (applies to Archive Failover cluster instances as well).  Determine what host is the cluster services active node. Use the command line below to the services if there is a split setup in place (IE the Cluster service is active on the host that is not the active Avid Interplay Workgroup server). o command string -> cluster group “Cluster Group” /move  At the point in time where you are ready to execute the network driver on the idle node, from the Failover Cluster Administration tool, expand the on the left to expose the Nodes list.  Select with a right mouse click the host that will have the driver update applied, menu item “ Actions”, menu item “Stop Cluster Service”.  To confirm that the service has stopped, in the Failover Cluster Manager, the Status of the node should indicate down and if you again, right mouse click, select Advanced Settings, More Actions, the Stop Cluster Service should be showing as grayed out (IE The service is not running).

 Continued on the next page

Page | 2

Example Server 2012 R2

Example Server 2008

Page | 3

Now that the cluster service has been confirmed to be in a stopped state, it is now possible to perform the network interface upgrade as per the vendor’s instructions. In this time interval it is recommended that the host platform have the BIOS and Firmware attended to that the vendor recommends be applied. Since at this time the host is no longer active we recommend a restart or a power off and power on cycle to allow for the host’s self-test functions to execute and report to the host user console the startup actions for the system’s operational status review.

 This may be an opportune time to attend to both a physical inspection and dust/dirt removal operation. Execute confirmation that cable connections are secure (IE. Do a pull test, does the connector unseat? Don’t forget to inspect the power cords and any Uninterruptable power supplies that are a part of the environment)  Once the above have completed and the system is functionally operational, return to the Failover Cluster management tool and as above, select the node advanced settings and this time select the cluster service.  When it is appropriate from the production actions perspective, perform the Avid Interplay service Move command to test the updated driver host from the Failover Cluster management tool.  To test that the cluster management service is supported on the updated host, run the command line string -> cluster group “Cluster Group” /move to migrate the service to the updated driver host.  When the testing from the two steps above has completed and the confidence levels are high or some time interval has completed repeat the steps above on the now inactive node running the older network driver and firmware instances.

Document History

Version Date Status 1 20160831 Released first version

Page | 4