> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/learn/data-management-concepts/volumes-and-volume-groups.md).

# Volumes and Volume Groups

Learn how volumes provide application storage and how volume groups organize related resources for capacity management, snapshots, and replication.

Volumes provide storage to your applications, while volume groups organize related volumes and establish shared boundaries for capacity management, snapshots, and replication.

Understanding how these resources work together helps you organize application data, apply protection policies consistently, and manage capacity across a DataPod.

## Volumes and host access

A volume is a logical storage resource that applications can read from and write to after the volume is mapped to a host.

Silk distributes volume workloads across the DataPod's c.nodes automatically. You don't need to select specific nodes or manually distribute volumes to balance performance.

Each volume:

* Belongs to one volume group
* Has a defined provisioned capacity
* Can be exposed as read/write or read-only
* Can be mapped to one or more hosts
* Can serve as the source for snapshots and clones
* Uses either **thin provisioning** or **thin provisioning with deduplication**, based on its volume group

Creating a volume doesn't automatically make it accessible to a host. You must map the volume to the appropriate host or host group before the host can use it.

{% hint style="info" %}
A volume's provisioned capacity represents the logical capacity available to the application.

Physical capacity is consumed as data is written and is affected by Silk data reduction.
{% endhint %}

## Organize storage with volume groups

A volume group is a collection of volumes and clones that share capacity, snapshot, and replication settings. You might group resources by application, business unit, environment, or protection requirements.

A volume group serves a role similar to a consistency group in other storage systems, allowing related volumes to be managed and protected together.

Volume groups provide three important management boundaries:

<table><thead><tr><th width="237.0369873046875">Function</th><th>How the volume group is used</th></tr></thead><tbody><tr><td><strong>Capacity management</strong></td><td>Establishes a capacity quota and associates the resources with a capacity policy.</td></tr><tr><td><strong>Snapshot management</strong></td><td>Allows Silk to capture the volumes and clones in the group together.</td></tr><tr><td><strong>Replication</strong></td><td>Defines the collection of storage resources included in a replication session.</td></tr></tbody></table>

Each volume can belong to only one volume group, but you can move a volume to another group when its management requirements change.

{% hint style="warning" %}
Moving a volume between volume groups deletes its existing snapshots.

Review any snapshot or data-protection dependencies before moving a volume.
{% endhint %}

## Organize volumes by application

Whenever practical, place volumes that belong to the same application or workload in the same volume group. This approach helps you:

* Capture related storage resources together in a volume group snapshot.
* Apply consistent capacity and protection settings.
* Replicate the application's storage as a coordinated collection.
* Monitor capacity and performance for a logical workload.
* Manage permissions across multiple volumes when necessary.

For example, an application with separate data, log, and configuration volumes could place all three volumes in one volume group. A snapshot of that group would then represent the application's related storage at a common point in time.

Avoid grouping unrelated workloads solely for convenience. Since volume groups define snapshot, capacity, and replication boundaries, resources with different protection or lifecycle requirements may be easier to manage in separate groups.

## Volume group capacity and quotas

Each volume group has a capacity quota governed by a capacity policy. Volume group capacity includes the allocated capacity used by its volumes, snapshots, and clones.

When capacity usage reaches a configured threshold, Silk performs the action defined by the associated capacity policy. Depending on the policy, this may include generating notifications or removing eligible copy data resources.

Volume groups also maintain a separate threshold for snapshot capacity. This allows administrators to monitor and manage the amount of capacity consumed by data-protection resources independently from active volume data.

You can configure a volume group with an unlimited quota if you don't want to impose a group-level capacity limit. The resources remain subject to the DataPod's overall capacity policies and available physical capacity.

## Enable deduplication selectively

All volume groups use thin provisioning, which allocates physical storage as data is written. Deduplication is disabled by default and can be enabled when you create a volume group that is likely to benefit from it.

When deduplication is enabled, Silk stores identical data blocks only once across the volume group's resources. This can reduce physical capacity consumption for workloads with substantial duplicate data, but it introduces some performance overhead. Enable it selectively based on the workload's data patterns and performance requirements.

All volumes within a volume group use that group's deduplication setting. Moving a volume between deduplication-enabled and deduplication-disabled volume groups doesn't retroactively change how its existing data is stored.

## Independent volume groups

Each DataPod includes default volume groups for independently managed deduplicated and non-deduplicated volumes:

* `INDEPENDENT_DEDUP_VOLUMES`
* `INDEPENDENT_NON_DEDUP_VOLUMES`

These groups cannot be modified or deleted, and they don't support snapshots or replication. Use them for independently managed volumes that don't require coordinated data protection.

When a volume is created through the CLI or API without a specified volume group, Silk places it in the appropriate default independent volume group.

For workloads that require coordinated data protection, capacity controls, or replication, create a dedicated volume group instead.

## Control access to volume data

Volumes can be exposed as read/write or read-only.

{% tabs %}
{% tab title="Read/write" %}
Read/write access allows mapped hosts to read and modify the volume's data.
{% endtab %}

{% tab title="Read-only" %}
Read-only access allows mapped hosts to read the data without changing it.
{% endtab %}
{% endtabs %}

You can change permissions for an individual volume or apply a permission change across all volumes in a volume group. Before changing a group to read-only, confirm that its mapped hosts and applications no longer need to write to the volumes. Otherwise, write operations may fail and application functions may be disrupted.

Volume exposure settings don't replicate host mapping. A host must still be mapped to the volumes before it can access the data.

## Related resources

{% content-ref url="/spaces/zRoeFiUtkaS7g8f3vjz5/pages/FXudgU7rJdcdoOSoDNH5" %}
[Plan DataPod Capacity](/deploy/plan-your-deployment/plan-datapod-capacity.md)
{% endcontent-ref %}

{% content-ref url="/pages/bE7CIdjb9q4cwFW2CkWX" %}
[Cloud Efficiency with Copy Data Management](/learn/data-management-concepts/cloud-efficiency-with-copy-data-management.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/learn/data-management-concepts/volumes-and-volume-groups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
