> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Incremental Snapshots instead of Full SSD Snapshots

> Replace full SSD managed disk snapshots with incremental snapshots, which are stored at the cheaper Standard HDD rate.

A full snapshot of a Premium SSD or Standard SSD disk is billed at the SSD snapshot price for the full size of the disk. Incremental snapshots are always stored at the Standard HDD snapshot price and bill only the data that changed since the last one. nOps finds full SSD snapshots and estimates the saving from replacing them with incremental snapshots.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Storage |
| **Service** | Managed Disks |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | No |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Full snapshots are the default in older scripts and templates, and each one is a full-price copy of the disk.

## How nOps finds it

nOps reads your pay-as-you-go managed disk snapshot billing. A snapshot is flagged when it was billed on the Premium SSD or Standard SSD snapshot price on at least 7 of the last 14 complete days. The saving is its cost over the last 7 days, scaled to a month, times the difference between the Standard HDD snapshot list price and its current list price in the same region and redundancy. Incremental snapshots usually cost even less, so this is a lower bound. The Standard HDD price must be at least 10% lower, and the saving at least \$5 a month. Snapshots old enough to delete are left to that recommendation instead.

## Before you start

Permission to create and delete snapshots, and access to the source disk.

## How to implement

1. Check the snapshot is still needed and that its source disk still exists.
2. Take an incremental snapshot of the source disk: `az snapshot create --resource-group MY_RG --name MY_SNAPSHOT --source DISK_ID --incremental true`, or in the portal choose **Create snapshot** and set **Snapshot type** to **Incremental**.
3. Delete the full snapshot (`az snapshot delete --resource-group MY_RG --name OLD_SNAPSHOT`).
4. Update the scripts, pipelines or templates that create snapshots so they use incremental snapshots.

## Risks and considerations

* An incremental snapshot needs its source disk. If the disk has been deleted, keep the full snapshot or delete it if not needed.
* Deleting the full snapshot is permanent, so take the incremental snapshot first.

## FAQs

> [accordion] Are incremental snapshots slower to restore?
>
> You restore a disk from an incremental snapshot the same way as from a full one. Check the restore time for your disk size before relying on it.

## Related

* [Delete Azure Snapshots Older than 90 Days](https://help.nops.io/inform/supported-recommendations/delete-azure-snapshots-older-than-90-days)
* [Delete Disks of Stopped Azure VMs](https://help.nops.io/inform/supported-recommendations/delete-disks-of-stopped-azure-vms)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.