> 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/nas/volume-snapshots-restores.md).

# NAS Volume Snapshots and Restores

Volume-level snapshots allow for customizing snapshot schedule and retention rules per individual NAS volume and provide the option for a quiesced snapshot. (Non-quiesced NAS volumes can be imported from full system snapshots to be used for restore.)

## Quiesced Snapshots

Quiesced volume snapshots freeze file system I/O during the snapshot process. The quiesce option can be selected when taking a manual volume snapshot and can be enabled within the snapshot profile used for automated snapshots.

## Schedule Volume Snapshots

[Snapshot Profiles](/automate-protect-and-extend/backup-and-dr/snapshot-profiles.md) are used to schedule snapshots; assign a profile to a volume to perform automated snapshots.

### Assign a Snapshot Profile to a Volume

{% hint style="info" %}
**Snapshots can only be performed on volumes of type=local.**
{% endhint %}

1. From the **volume dashboard**, click **Edit** on the left menu.
2. In the ***Snapshot profile*** field, select the desired profile from the dropdown list.
3. Click **Submit** at the bottom of the page.

## Manual Volume Snapshots

### Take a Manual Snapshot of a Volume

{% hint style="info" %}
**Snapshots can only be performed on volumes of type=local.**
{% endhint %}

1. From the volume dashboard, click **Take Snapshot** on the left menu.
2. Enter a ***Name*** for the snapshot (required).
3. Enter a ***Description*** (optional).
4. The ***Quiesce*** option can be selected to freeze I/O during the snapshot process.
5. In the ***Expires*** field, select/enter a date and time for expiration.
6. Click **Submit** at the bottom of the page.

{% hint style="warning" %}
**Always consider vSAN Usage**

When selecting expiration for a snapshot it is important to consider vSAN space utilization. Initially source and snapshot are the same and thus there is no impact on storage utilization; however, as source data diverges more from the snapshot data, there is less deduplication between the two and thus more vSAN usage. The *Never Expires* option is not recommended unless necessary.
{% endhint %}

## Restore a Volume from Snapshot

{% hint style="info" %}
**To restore a volume from a full system snapshot, the volume must first be imported from the system snapshot as detailed below. To restore from an individual volume snapshot, skip the import section of instructions and continue to Restore to overwrite -OR- Restore to create new instructions**
{% endhint %}

### *Import Volume Snapshot from a System Snapshot (to make it available for a volume restore)*

1. From the **volume dashboard**, click **System Snapshots** on the left menu.
2. Click to **select desired system snapshot**.
3. Click **Import Snapshot** on the left menu.
4. \***Name, Description and Expiration fields** will default to the values from the system snapshot; make changes if desired; changes made will only apply to the import and will not affect the underlying system snapshot.
5. Click **Submit** to continue.
6. (If the process was continued) a message should appear stating the import process has begun. Click the **Ok** button to acknowledge.
7. When the import is complete, the snapshot will be available for restore using instructions below.

### *Restore a Volume (to overwrite existing current version of volume)*

1. From the **volume dashboard**, click **Snapshots** on the left menu.
2. A listing of available snapshots is displayed. Click to **select the desired snapshot**.
3. Select **Restore over Source** from the left menu.
4. A warning message will appear to caution that this will overwrite the existing volume and all of its data. *By default, **Restore Data Only** is selected; this option will restore over data within the volume, but not modify any current volume settings. The alternate option: **Restore Data and Settings** will both restore over volume data and will replace volume settings with those in the snapshot.*
5. Click the **Proceed** button to continue/ or **Cancel** to abort.

### *Restore a Volume (to create a new volume)*

1. From the volume dashboard, click **Snapshots** on the left menu.
2. A listing of available snapshots is displayed. Click to **select the desired snapshot**.
3. Click **Restore To New** on the left menu.
4. The **Destination Service VM** defaults to the NAS service of the source volume; if multiple NAS services exist on the system, a different service can be selected on which to restore the volume.
5. The **Volume Name** (for the new volume instance) will default to ORIGINALVOLUMENAME\_restored; change name if desired.
6. Click the **Submit** button to create the new volume from snapshot. The new volume is brought online automatically. To view the new volume's dashboard, return to *Volumes* and double-click on the volume in the listing.


---

# 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/nas/volume-snapshots-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.