> 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-3p-partial-failover-vms-vm-app1-from-on-premise-site-to-hi-gio-site.md).

# Step 3P - Partial failover VMs (VM - APP1) from on-premise site to HI GIO site

## <mark style="color:green;">**Overview**</mark>

Use this step when your primary infrastructure (on-premise) is running well. After this step:

**- Workload is on the HI GIO cloud site.**

**- Source workload is powered off.**

## <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="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2FvXPYwfXbXx52UnZPKSWi%2Fimage.png?alt=media&amp;token=41c25582-90b6-4308-8287-a7f95a571765" alt=""><figcaption></figcaption></figure>
{% endstep %}

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

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2FH2RlnhW1NloaZCUuSYhz%2Fimage.png?alt=media&amp;token=745e0591-4807-4a14-9a12-1ff40a938aa5" alt=""><figcaption></figcaption></figure>
{% endstep %}

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

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

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

**- Network Settings: Apply preconfigured network settings on migrate (configured in step2)**

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2FxEg49K1Rhd136j5HdlvT%2Fimage.png?alt=media&amp;token=cd0dfdb4-2553-4982-8035-aed62148abc4" alt=""><figcaption></figcaption></figure>

**- Click NEXT**

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2F96jv5Xmqp0Ca3eYwGtmT%2Fimage.png?alt=media&amp;token=9f0ddd21-d6a4-40b9-a992-d36ec0fffa23" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 5:** Review and click **FINISH**

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2F5s6oWNEEe9viwUpPHP5M%2Fimage.png?alt=media&amp;token=58ff1e9c-9ac9-4f22-9584-c9fea3938af8" alt=""><figcaption></figcaption></figure>
{% endstep %}

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

1. Failover in Progress: You will notice Migrate **in Progress with %** progress in the Detailed Status.

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2F0C4x8TSwTeTnDFsR8zSx%2Fimage.png?alt=media&amp;token=2ba06ac4-335c-4774-b095-f528de6c33c9" alt=""><figcaption></figcaption></figure>

2. Once the migration task is completed, confirm on

**STATUS**, **VM**:

**APP1:**&#x20;

\- Recovery state = Failed-Over,&#x20;

\- Replication Type = On-Premise Protection,&#x20;

\- Overall health = Green.

**DB1:**&#x20;

\- Recovery state = Not stated,&#x20;

\- Replication Type = On-Premise Protection,&#x20;

\- Overall health = Green.

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2F0o56HMJLyQjJLUb7CIrf%2Fimage.png?alt=media&amp;token=d9390305-2b78-4c56-a04b-722df3c9a6e6" alt=""><figcaption></figcaption></figure>

Migrate completed successfully. The workload is running in the HI GIO cloud, and the workload is no longer protected.
{% endstep %}
{% endstepper %}

***

## <mark style="color:orange;">Validate - APP1</mark> <a href="#validate-app1" id="validate-app1"></a>

## <mark style="color:green;">**Procedure**</mark>

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

{% step %}
**Step 2:** Confirm that VM APP1 was migrated to HI GIO and powered on.

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2FYrkMV97YIIjcv7Utac01%2Fimage.png?alt=media&amp;token=20ac96ee-1c5b-4915-9a64-b963624d9be2" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 3:** Ping, tracert, HTTP to APP1 from on-premises site must be success.

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2F8i4wEuO1LAWwcN4I4cAB%2Fimage.png?alt=media&amp;token=c7dcc00b-733a-46e3-b75d-cd6e4b4b4f2f" alt=""><figcaption></figcaption></figure>

{% endstep %}

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

1. The VM APP1 is running on the HI GIO site now. The VM is no longer protected.
2. The VM APP1 is power off on-premises - automatic by vCDA.

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2FN1CMrtWU62VN38QCDJQ0%2Fimage.png?alt=media&amp;token=8cbcfe72-6968-4753-be54-20b0a83e7ae4" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.higiocloud.vn/hi-gio-draas/failover-scenario/failover/step-3p-partial-failover-vms-vm-app1-from-on-premise-site-to-hi-gio-site.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
