> For the complete documentation index, see [llms.txt](https://docs.trilio.io/kubernetes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trilio.io/kubernetes/user-guide/getting-started-with-management-console/index/restoring-backups/cross-cluster-restores.md).

# Cross-Cluster Restores

## Overview

As part of the management console, Trilio provides the ability to browse targets that have been connected to a cluster. This feature can be leveraged when a backup reference is not available locally and the application needs to be restored from the target directly. This is particularly useful in cross-cloud or cross-distribution migration use cases.

## Enabling Target Browsing

Target browsing can be enabled by using the toggle switch provided within the target page next to each target. Once browsing has been enabled, a target browser pod is spun up in the namespace the target resides that enables the user to browse through the data present on the target via the management console. The enabling process can take a couple of minutes to become ready.

![Enabling Target Browser](/files/4uWmkTylz2tk0pQJnUit)

## Browsing Targets and Restoring Backups

After browsing has been enabled, users can view the various backupPlans that have been placed on that target from multiple sources. Selecting a backupPlan further drills down into the backups and snapshots available for it.

Users have the ability to restore a backup and snapshot, view metadata, view status log, or view the YAML of the backup and snapshot directly from the target. This is no different than how a user would interact with a backup and snashot reference that is available locally, hence keeping the experience the same.

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

Upon clicking 'Restore' the restore workflow is initiated.\
refer [namespace-and-application-scoped.md](/kubernetes/user-guide/getting-started-with-management-console/index/restoring-backups/namespace-and-application-scoped.md) and [cluster-scoped.md](/kubernetes/user-guide/getting-started-with-management-console/index/restoring-backups/cluster-scoped.md)

For detailed information about restore flags that can be configured during the restore process, see the [Restore Flags Guide](/kubernetes/user-guide/getting-started-with-management-console/index/restoring-backups/restore-flags-guide.md).

{% hint style="info" %}
If you restore a VM on the destination cluster that uses Multus CNI, ensure that the **NetworkAttachmentDefinition** (NAD) exists with the same name and namespace before starting the restore process. Without the **NetworkAttachmentDefinition**, the VM's networking may fail after restoration. If the destination cluster does not have the required NetworkAttachmentDefinition (NAD), you must perform a transformation to remove the secondary interface from the VM YAML.
{% endhint %}


---

# 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:

```
GET https://docs.trilio.io/kubernetes/user-guide/getting-started-with-management-console/index/restoring-backups/cross-cluster-restores.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.