> 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-user-guide-vn/hi-gio-draas/kich-ban-failover/failover/buoc-4-sao-chep-nguoc-reverse-replication-cua-may-ao-tu-site-hi-gio-cloud-ve-on-premises..md).

# Bước 4: Sao chép ngược (reverse replication) của máy ảo từ site HI GIO Cloud về On-Premises.

## <mark style="color:green;">**Tổng quan**</mark> <a href="#overview" id="overview"></a>

Sau khi site on-premises khôi phục và khả dụng, bạn có thể di chuyển tải công việc (APP1, DB1) từ cloud HI GIO về lại on-premises bằng cách đảo ngược bản sao (reverse replication).

## <mark style="color:green;">Quy trình</mark> <a href="#id-2.-guidance" id="id-2.-guidance"></a>

{% stepper %}
{% step %}
**Bước 1:** Đăng nhập vào HI GIO portal.
{% endstep %}

{% step %}
**Bước 2:** Mở rộng **More** > Nhấn vào **Availability ().**

<figure><img src="https://content.gitbook.com/content/dOZ82gj0wvhbAUlxBHpj/blobs/ZMqWcximRm5bfISVWsPw/image.png" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Bước 3:** Nhấn vào **Incoming Replications** > Tích chọn checkbox cho vAPP1 > Mở rộng ALL ACTIONS > Nhấn vào **Reverse**.

Bạn cũng có thể chọn từng VM riêng lẻ ở bước này.

<figure><img src="https://content.gitbook.com/content/dOZ82gj0wvhbAUlxBHpj/blobs/BsoS4yy7Mr9q8IlfWIOX/image.png" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Bước 4:** Xác nhận Reverse Replication từ cloud HI GIO về on-prem. Nhấn **REVERSE**.

<figure><img src="https://content.gitbook.com/content/dOZ82gj0wvhbAUlxBHpj/blobs/vvSJV9l50hoPPREaIYdJ/image.png" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Bước 5:** **Kết quả mong đợi:**

1. Reverse Replication is in progress. Bạn có thể theo dõi tiến trình của tác vụ đảo ngược trong phần **Last changed** và trạng thái replication.

<figure><img src="https://content.gitbook.com/content/dOZ82gj0wvhbAUlxBHpj/blobs/gUbMLZEwVQ8P6Q3qDhOp/image.png" alt=""><figcaption></figcaption></figure>

2. APP1 & DB1 đã được replicate lại về on-premises, và Recovery state là **Reversed**.

<figure><img src="https://content.gitbook.com/content/dOZ82gj0wvhbAUlxBHpj/blobs/NtgopyySTqcMk8Y3spb0/image.png" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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-user-guide-vn/hi-gio-draas/kich-ban-failover/failover/buoc-4-sao-chep-nguoc-reverse-replication-cua-may-ao-tu-site-hi-gio-cloud-ve-on-premises..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.