Continuity Cloud Procedure for Switchover/Failover - SELF MANAGED

Follow

Neverfail Technical Support assists with any break-fix scenarios and also with switchover/failover requests.

Whenever the customer needs to contact Technical Support he can do this in two ways:

  1. From the Neverfail main portal https://portal.vpdc.us/User/Login by navigating to Help Center\Go To Support Portal and log a ticket for Neverfail Continuity Engine
  2. Directly emailing support@neverfail.com

For a switchover/failover scenario the steps to be performed are the followings:

  1. If virtual machine resources on the passive nodes are configured as a minimum viable computer resource configuration, please follow the following instructions to hydrate the VM resources on the passive node. Alternatively a customer can open a ticket describing the desired operation and providing DR VM details and requirements (CPU, RAM, etc.) for becoming Active (production).
  2. Customer or Cloud Support hydrates the DR VM (passive node) with necessary resources.
  3. Customer can then switchover/failover by promoting the passive node to active status. Alternatively, Software Support can engage the customer in a remote session and assist them in performing the switchover/failover.

MAKING THE SECONDARY ACTIVE

  1. Switchover will be done from EMS (Engine Management Server) console so the customer will need to have credentials to EMS
  2. Failover (e.g. Primary – On premise server down) will be done from Engine thick client of the DR VM so the customer will need to have credentials for DR VM.

 

Dehydration of Cloud Resources After Continuity Event Has Completed

For a switchback scenario the steps to be performed are the followings:

  1. If virtual machine resources on the passive nodes are configured with production compute resources, please follow the following instructions to dehydrate the VM resources on the passive node. Alternatively a customer can open a ticket describing the desired operation and providing DR VM details and requirements (CPU, RAM, etc.) for becoming passive.
  2. Customer or Cloud Support dehydrates the DR VM (passive node) with necessary resources.
  3. Customer can then switchback by promoting the passive node to active status (Primary). Alternatively, Software Support can engage the customer in a remote session and assist them in performing the switchback.

MAKING THE PRIMARY ACTIVE

  1. Switchback will be done from EMS (Engine Management Server) console so the customer will need to have credentials to EMS
  2. Switchback (e.g. Secondary) will be switched from Engine thick client of the DR VM so the customer will need to have credentials for DR VM.

 

 For more details on roles and responsibility for Continuity Cloud please see the following KB article:

Roles and Responsibility on Continuity Cloud Tier 1 and Tier 2 - Self-Managed

 

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.