> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/run-the-platform/tenants/share-vm-snapshot.md).

# Share a VM Snapshot between Provider and Tenant

The *Shared Objects* feature provides convenient, snapshot-based VM sharing between provider and tenant. The provider or tenant can make a specific VM snapshot available to the other to create a new VM within their own system.

## On the Sending System

1. **Establish desired VM snapshot**: [Take a manual snapshot of the VM](/automate-protect-and-extend/backup-and-dr/vm-snapshots-restores.md#take-a-manual-snapshot-of-a-vm) or determine an existing VM snapshot you wish to use.
2. Navigate to **System > Shared Objects**.
3. Click **New** on the left menu.
4. Provide a **Name** for the shared object; this will be used to name the imported VM on the receiving system.
5. (Optional) **Description** can be used to store additional information about the shared object.
6. Select ***Virtual Machine*** in the **Type** field.
7. Select desired **Snapshot** from the list. The selection list will include all snapshots of the selected VM.
8. Select **Recipient** (a tenant or your service provider).
9. Click **Submit** to make the VM image available for the recipient to import.

## On the Receiving System

1. Navigate to **System > Shared Objects**.
2. A listing of available shared objects is displayed. Objects shared from other systems will display as "Inbound".
3. Select desired VM objects and click **Import** on the left menu.
4. (Optional) Uncheck the **Preserve MAC Addresses** checkbox if new, unique MAC addresses should be created. Consider unchecking this option if:
   * The source VM will remain active
   * You are creating a test/dev copy
   * There are potential network conflicts

{% hint style="info" %}
**Guest network configuration may need adjustment after import with new MAC addresses.**
{% endhint %}

5. (Optional) Select a **Preferred Tier** on which to create the new VM(s). Otherwise, VM drives will be created on the system default tier.

{% hint style="warning" %}
**Before completing an import, ensure there is adequate space on the selected tier.**
{% endhint %}

6. Click **Import** to complete the operation. The VM is created with the name given to the shared object (the "Name" specified in step 4 of the sending process), not the original VM name from the source system.

{% hint style="success" %}
**Shared Object Reuse:**

* The shared object can be deleted after successful import.
* It cannot be reused with the same name (but can be renamed to allow another import).
  {% endhint %}

## Troubleshooting

{% hint style="warning" %}
**Common Issues**

* Problem: Error message *"You cannot import something that is not in the inbox."*
  * Solution: Verify only "Inbound" items were selected for import; "Outbound" items cannot be imported.
* Problem: Error message *"A virtual machine already exists with this name."*
  * The VM was already imported, or
  * an existing VM has the same name as the shared object.
  * Solution: Rename the shared object to create a VM with a different name.
    {% 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.vergeos-demo.com/run-the-platform/tenants/share-vm-snapshot.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.