Fail Over is a process of switching the replica machine on, while the source machine is affected because of a disaster or the source is in maintenance mode. During the failover the replica machine will act as source machine and handle all the processes.

If the replica job configured with Network and IP-Remapping then the replica will up and run with that Network & IP configurations during the FailOver state, If not you have to manually assign Network and IP for the replica.

It is possible to FailOver the replica to any of its available recovery point. It is also possible to FailOver group of replicas which are actually dependant on one another that are available in the configuration.

The data added during the FailOver state will be maintained in a snapshot delta file which will be committed later based on the need.

If you are interested in perceiving the process of FailOver & FailBack you can go through my blog “FailOver & FailBack – A Deep Insight Throughout The Process“.

Why FailOver

FailOver and FailBack are the significant recovery processes of virtual machine replication which are actually involved in the Backup and Disaster Recovery process. If you are curious about FailOver & FailBack and want to know “Why do we need FailOver and FailBack” go through my blog “FailOver & FailBack – A Significant Process During Disaster”.

Lets us have a brief overview of the Planned FailOver, the substance of this blog.

Planned FailOver

Planned FailOver is a process switching the workload to the replica by performing FailOver at a specific time in a pre-planned manner. Let’s say, you know that your source VMs are about to go offline at a specific point of time due to network maintenance and you don’t want your business to be interrupted, then you can plan your FailOver at the specific point of time where in the case of you knowing the timing details prior.

Circumstances where planned failover plays vital role

There are several scenarios that the Planned FailOver could play a key role.

If your datacenters are going for maintenance, network maintenance on datacenter site, or you are going to migrate the data centers you can use Planned FailOver process. Also if you know that you are about to face a disaster and the datacenters are supposed to go offline to avoid the impact of disaster on datacenter, and also you want to run the business without any interruption you can go for Planned FailOver.

The Process go through the below steps to achieve the Planned FailOver

1→ Perform an Incremental for the VM’s that has been configured for planned FailOver to get the latest disk state.

2→ Perform FailOver process

3→ Power On the replica

Unlike the normal FailOver process, the Planned FailOver does not requires to select the recovery point since the Planned FailOver intended to handle the current workload. Once everything gets normal at the onsite then you switch back to the normal working mode using your primary VM’s.

At Vembu the “Planned FailOver” feature is under development, and Vembu Unveils this effective process soon.

Interested in trying Vembu BDR suite?, Try Now on a 30-days free trial: https://www.vembu.com/vembu-bdr-suite-download/

Got questions? Email us at: vembu-support@vembu.com for answers.

Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.

Like what you read? Rate us