> For the complete documentation index, see [llms.txt](https://docs.higiocloud.vn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.higiocloud.vn/hi-gio-draas/failover-scenario/failover/step-3f-full-failover-vapp1-vm-app1-and-vm-db1-from-on-premise-site-to-hi-gio.md).

# Step 3F - Full failover vAPP1 (VM - APP1 & VM - DB1) from on-premise site to HI GIO

## <mark style="color:green;">**Overview**</mark> <a href="#overview" id="overview"></a>

If the protected site (on-premises) is **unavailable**. In the HI GIO cloud, you can perform a workload disaster recovery operation (full failover)

## <mark style="color:green;">**Procedure**</mark> <a href="#procedure" id="procedure"></a>

{% stepper %}
{% step %}
**Step 1:** Log on to the HI GIO portal.
{% endstep %}

{% step %}
**Step 2:** Expand **More** > Click on **Availability ()**

<figure><img src="/files/OmqP1e8qbfBSVlcfE4fN" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 3:** Click on **Incoming Replications >** Check the checkbox for VM **APP1** > Expand **ALL ACTIONS** > Click on **Failover**

<figure><img src="/files/quREPTLD4kkC3cnTisBY" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 4:** Configure Recovery Settings for Failover

**- Instances handing after recovery: Default.**

**- Power Settings: Power on recovered vApps.**

**- Network Settings: Apply preconfigured network settings on migrating.**

Click **NEXT**

<figure><img src="/files/tK2drBuXkHRYr6A7ca7M" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 5:** Configure Recovery Instance for Failover

Click **SELECT LATEST FOR EVERY VM** > **NEXT**

&#x20;

<figure><img src="/files/2FGSXGDd9GCNIDtkRIpj" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 6:** Review and **FINISH**

<figure><img src="/files/9DOZm5u23Y6EItbffW9j" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 7:** Expectation result:

1. Failover in Progress: In the Detailed Status, you will notice Failover **in Progress with %** progress.

<figure><img src="/files/wfqkZOJk2tgtAnOS6e5r" alt=""><figcaption></figcaption></figure>

2. Failover successfully: This process will take a couple of minutes. Please be patient.

After the failover task finishes, the failed over workload runs in the HI GIO cloud.

**Confirm that all VMs in vAPP1:**

**- Recovery State = Failed-Over.**

**- Replication Type = On-Premise Protection**

**- Overall health = Green**

<figure><img src="/files/8qzt696FQ6cdThjjAQSp" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***

## <mark style="color:orange;">Validate - vAPP1 (VM APP1 & DB1)</mark> <a href="#validate-vapp1-vm-app1-and-db1-on-hi-gio-cloud" id="validate-vapp1-vm-app1-and-db1-on-hi-gio-cloud"></a>

In this scenario, on-premise has issues: network, hardware host, and storage… that make it not available.

## <mark style="color:green;">**Procedure**</mark> <a href="#procedure.1" id="procedure.1"></a>

{% stepper %}
{% step %}
**Step 1:** Log on to the HI GIO portal: *select vAPP1* > **Virtual machines**.
{% endstep %}

{% step %}
**Step 2:** Confirm that 02 VMs, APP1 & DB1, were migrated to HI GIO and are running.

<figure><img src="/files/lAvlKl5PPm1jLsPFyB3f" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 3:** Change default gateway for APP1 & DB1 (on-prem network is problem)

Logon **APP1 & DB1** by admin local > change default gateway and validate that **APP1 & DB1** can be reachable.

<figure><img src="/files/2dVIZ4HARFfGUZY2MVcH" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/biNKK1IjLH2DvOMtqMOg" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 4:** Point domain name to APP1 (public DNS record if needed).
{% endstep %}

{% step %}
**Step 5:** Access to APP1 via the internet (in my case, I used a public IP).

<figure><img src="/files/c9BcCNr73hFGFgTUvUQM" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.higiocloud.vn/hi-gio-draas/failover-scenario/failover/step-3f-full-failover-vapp1-vm-app1-and-vm-db1-from-on-premise-site-to-hi-gio.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.