# Ensure Old Snapshots Are Removed According to Retention Policy

- Source: https://support.icompaas.com/support/solutions/articles/a_1791826028594349-ensure-old-snapshots-are-removed-according-to-retention-policy
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [OVH Cloud](https://support.icompaas.com/support/solutions/c_1791819364512367) › [checks](https://support.icompaas.com/support/solutions/folders/f_1791819376721251)
- Last updated: 2026-10-12
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure instance and volume snapshots and backups older than the organization's retention period are deleted, so only the backups that are needed are kept.

**Rationale**

Old snapshots increase cost and may contain outdated sensitive data that should have been deleted under data retention rules. Keeping them longer than needed increases the amount of data that could be exposed. Removing them according to policy keeps storage clean and compliant.

**Impact**

-   Reduces storage costs
    
-   Removes outdated sensitive data
    
-   Deleted snapshots cannot be recovered
    

**Default Value**

Snapshots are kept until they are deleted. Automated backups created by workflows follow the rotation you choose.

**Pre-Requisites**

-   Permission to manage the Public Cloud project
    
-   A defined retention period
    

**Test Plan**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  Review instance backups in Instance Backup (under Compute), and volume snapshots and backups in Volume Snapshot and Volume Backup (under Storage).
    
4.  Identify any older than your retention period.
    
5.  If any are found, follow the implementation steps.
    

**Implementation Steps**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  For each old snapshot or backup, confirm it is not needed, then open its ⋯ menu and delete it.
    
4.  For automated backups, review the rotation of the workflow in Workflow Management (under Compute) so it matches your retention period.
    

**Backout Plan**

1.  Deleted snapshots cannot be restored. Create a new snapshot if one is needed.
    

**Reference**

-   [https://docs.ovhcloud.com/en/guides/public-cloud/compute/save-an-instance](https://docs.ovhcloud.com/en/guides/public-cloud/compute/save-an-instance)
    
-   [https://docs.ovhcloud.com/en/guides/public-cloud/compute/storage-create-volume-snapshot](https://docs.ovhcloud.com/en/guides/public-cloud/compute/storage-create-volume-snapshot)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
