> 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/releases/2026/v8.6.10/features-and-enhancements.md).

# Features and Enhancements

Generally available since February 3, 2026. Explore the new features and enhancements in Silk v8.6.10, including DataPod object tagging, SPDK on c.nodes, and Echo of Echo.

## Highlights

The most impactful changes in this release. Expand a highlight for a quick summary and a link to its full description.

<details>

<summary>Object tagging on DataPods</summary>

Tag volumes, hosts, snapshots, and more; tags are inherited by derived objects.

[Read more about object tagging on DataPods](#object-tagging-on-datapods-improves-data-organization-and-visibility)

</details>

<details>

<summary>Snapshot capacity visibility</summary>

See the capacity consumed by individual snapshots and clones in the SDP Management Console.

[Read more about snapshot capacity visibility](#snapshot-capacity-visibility-enhances-space-management)

</details>

<details>

<summary>Storage Performance Development Kit (SPDK) on c.nodes</summary>

A newer, faster storage processing engine on c.nodes delivers higher throughput and lower latency, with no configuration required.

[Read more about SPDK on c.nodes](#spdk-improves-storage-performance-on-c.nodes)

</details>

<details>

<summary>Increased c.node capacity</summary>

Maximum physical capacity per c.node rises from 250 TiB to 324 TiB.

[Read more about increased c.node capacity](#increased-c.node-capacity-enables-greater-scale)

</details>

<details>

<summary>Azure Pv2 CMK encryption</summary>

Customer-managed keys for Pv2 m.nodes and Pv2 c.node OS disks.

[Read more about Azure Pv2 CMK encryption](#azure-pv2-supports-disk-encryption-with-customer-managed-keys-cmk)

</details>

<details>

<summary>Faster NDUs on Azure</summary>

Shorter Flex upgrade downtime and maintenance windows.

[Read more about faster NDUs on Azure](#faster-ndus-reduce-upgrade-downtime-for-azure-based-environments)

</details>

<details>

<summary>Echo of Echo</summary>

Up to four generations of Echo databases derived from a single source.

[Read more about Echo of Echo](#echo-of-echo-enables-multi-generation-database-environments)

</details>

<details>

<summary>SQL Server 2022 restore and state awareness</summary>

Copy-only snapshots without VSS, NORECOVERY restores, and broader database state detection.

[Read more about SQL Server 2022 restore and state awareness](#enhanced-sql-server-2022-restore-and-database-state-awareness-improve-operational-safety)

</details>

## Component versions

<table><thead><tr><th>Silk Component</th><th width="148.8887939453125">Version</th><th>Image Version</th></tr></thead><tbody><tr><td><strong>Silk Flex</strong></td><td>2.10.105</td><td>—</td></tr><tr><td><strong>SDP Management Console</strong></td><td>8.6.10.21</td><td>k2c-cnode-8-6-10-19</td></tr><tr><td><strong>d.node</strong></td><td>8.6.10.35</td><td><p><strong>Azure</strong></p><p>azure-dnode-8-6-10-35<br><br><strong>Google Cloud</strong><br>gcp-dnode-8-6-10-35</p></td></tr><tr><td><strong>VSS</strong></td><td>2.0.18</td><td>—</td></tr><tr><td><strong>Host Agent</strong></td><td>1.0.22</td><td>—</td></tr></tbody></table>

## Flex and DataPods

{% embed url="<https://www.loom.com/share/80992f492778415694eb518f99167f71?_hsenc=p2ANqtz-84lrWUOob2Al0d8XQ97C_UvyYFvR5KsuLVfxJmFvLT92HiqKrzxKeFqliuYpMCXYQlKg6laLJJvPO3hN5_Mx4b1f9yYg&_hsmi=2&utm_content=2&utm_medium=email&utm_source=hs_email>" %}

### Object tagging on DataPods improves data organization and visibility

Silk now supports object tagging across key DataPod resources, allowing you to apply metadata to better organize, manage, and search your environments. Tags can be used to identify ownership, environment, application context, or operational purpose.

Tagging is supported for these object types:

{% columns %}
{% column %}

* Volumes
* Volume groups
  {% endcolumn %}

{% column %}

* Clones
* Hosts
  {% endcolumn %}

{% column %}

* Views
* Host groups
  {% endcolumn %}

{% column %}

* Snapshots
* Replication sessions
  {% endcolumn %}
  {% endcolumns %}

Tags are automatically inherited from parent objects to derived objects (like snapshots and views), enabling consistent metadata propagation across the data lifecycle. Multiple tags can be applied to a single object for flexible classification.

### Snapshot capacity visibility enhances space management

This release adds visibility into the capacity consumed by individual snapshots and clones directly within the SDP Management Console.

Users can view detailed capacity information from the Snapshots & Replication > Capacity Calculations tab, as well as via the Capacity dropdown in the toolbar for supported objects such as snapshots. These views make it easier to identify space-heavy resources, understand reclaimable capacity, and make more informed cleanup decisions.

This enhancement simplifies troubleshooting unexpected capacity usage and improves day-to-day storage and lifecycle management.

### SPDK improves storage performance on c.nodes

We now use Storage Performance Development Kit (SPDK) for storage processing on c.nodes, replacing the previous SCST-based implementation.

This update improves throughput, reduces latency, and enhances scalability for modern storage workloads. SPDK also enables more efficient multi-core processing and better performance consistency under load.

At this stage, this change applies to c.nodes only and requires no customer configuration.

### Increased c.node capacity enables greater scale

The maximum supported physical capacity per c.node has been increased from 250 TiB to 324 TiB.

This enhancement lets you scale to larger capacities with fewer nodes, improving efficiency and reducing infrastructure complexity. The increased limit applies automatically after upgrading to v8.6.10 and requires no configuration changes.

### Azure Pv2 supports disk encryption with customer-managed keys (CMK)

We now support customer-managed keys (CMK) for encrypting Azure Pv2 disks, enabling you to manually manage encryption keys for eligible nodes. CMK is available for:

* Pv2 m.nodes
* Pv2 c.nodes with OS disks (since OS disks include temporary data)

{% hint style="warning" %}
To enable CMK, you must define encryption keys in Azure before deploying a Silk cluster. A separate Azure Key Vault is required for each disk type. Flex securely references customer-defined keys to encrypt disks while allowing you to retain full control of key management.

Currently, CMK is only supported for new DataPod deployments and during NDU. Enabling CMK on an existing m.node requires live migration.
{% endhint %}

This feature lets you own and control disk encryption keys. This helps you meet internal security and compliance requirements while still allowing you to change how keys are created, managed, and rotated within Azure.

### Faster NDUs reduce upgrade downtime for Azure-based environments

Enhancements to the NDU process significantly reduce downtime during Flex upgrades on Azure.

These improvements shorten the time required to complete NDUs by streamlining how Flex is updated, allowing upgrades to complete more quickly while maintaining service availability.

This means you can apply updates with even less operational impact and shorter maintenance windows. No changes to existing upgrade workflows are required.

### Mini NDU (mNDU) expands management upgrade flexibility for Silk on Azure

We’ve extended our mNDU capabilities to support additional management components for Azure-based Silk deployments.

With mNDU, you can perform management-plane updates without running a full NDU, and without impacting I/O operations. This approach enables you to take advantage of the latest component updates sooner, accelerating time to value for new improvements, fixes, and enhancements.

### Azure Pv2 capacity expansion supports larger deployments

For Azure Premium SSD v2 (Pv2) configurations, we now support 120 TiB disks per m.node, enabling up to 360 TiB total capacity across three m.nodes.

This update aligns Silk with Azure’s expanded disk capabilities and provides additional flexibility for customers deploying large-scale or capacity-intensive workloads on Azure.

### Azure NAT Gateway support aligns deployments with Azure networking requirements

Silk now supports the use of an Azure NAT Gateway as an outbound connectivity option for Azure deployments.

{% hint style="info" %}
Explicit outbound internet access is required for the Flex subnet, regardless of the outbound connectivity method used. You may choose to use a NAT Gateway in alignment with Azure’s networking guidance, or continue using another supported outbound connectivity method that meets Azure’s networking and security requirements.
{% endhint %}

### Expanded VM support improves performance, scalability, and deployment flexibility across cloud platforms

This release introduces support for additional VM types across both Azure and Google Cloud, expanding infrastructure options for c.nodes and d.nodes and improving flexibility for a wider range of workloads.

New Azure VM support includes:

{% columns %}
{% column %}
**c.nodes**

* Standard\_D64as\_v6
* Standard\_E64as\_v6
* Standard\_D64as\_v5
* Standard\_E64as\_v5
* Standard\_Lsv4-series
  {% endcolumn %}

{% column %}
**d.nodes**

* Standard\_Las\_v3-series
* Standard\_Las\_v4-series
* Standard\_Lasv4-series
  {% endcolumn %}
  {% endcolumns %}

New Google Cloud VM support includes:

{% columns %}
{% column %}
**c.nodes**

* c4d-standard-64
* c4d-highmem-64
  {% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

These additions align Silk with newer VM generations across both cloud providers, enabling improved CPU performance, memory efficiency, and storage throughput.

### Pre-migration verification improves m.node live migration reliability

We’ve introduced a pre-migration verification step that runs automatically before performing m.node live migrations.

This verification validates system readiness and migration prerequisites ahead of time, helping identify potential issues before migration begins. By proactively checking conditions like resource availability and system state, this enhancement reduces the risk of migration failures and improves overall upgrade and scaling reliability.

This process is fully integrated into existing workflows and requires no additional customer configuration.

### Enhanced call home telemetry for d.nodes supports Silk diagnostics

Call home reporting now includes CPU and memory usage metrics for d.nodes, providing deeper visibility into node-level health and performance. This additional telemetry enables faster diagnostics and more proactive support without requiring any changes to customer configuration.

### Flex settings menu reorganization improves usability

The Flex UI now separates general settings and cluster-related actions into two distinct menus, making it easier to find and manage common configuration tasks.

{% columns %}
{% column width="16.666666666666664%" %}

<figure><img src="https://1557305422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFUE8J62COhtwFAOs7gSo%2Fuploads%2FWzt8mpi4GTy5Cxg6DoHH%2Fimage.png?alt=media&#x26;token=4052526b-e4ac-456c-b39d-c235a4e15f06" alt="" width="27"><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="83.33333333333334%" %}
The cogwheel menu in the top-right corner contains general settings.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="16.666666666666664%" %}

<figure><img src="https://1557305422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFUE8J62COhtwFAOs7gSo%2Fuploads%2FrLctQnQwtSzdDHFxXEJF%2Fimage.png?alt=media&#x26;token=45cdc40a-5e94-4bdf-b23f-e198535af240" alt="" width="23"><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="83.33333333333334%" %}
The three-dot action menu in the upper-right contains cluster-related actions.
{% endcolumn %}
{% endcolumns %}

### SDP GUI improvements streamline day-to-day resource management

This release delivers targeted improvements across the SDP Management Console, including:

* **Volume and snapshot management**: Faster interactions in replicated systems, improved sorting and capacity display, and more consistent naming and visibility.
* **Host and replication views**: Improved scrolling, clearer hostname display, and more intuitive representation of replication relationships.
* **Configuration and system feedback**: Better validation for DNS and IP configuration and clearer messaging during refresh and network operations.

These enhancements improve day-to-day operational efficiency and reduce friction when managing large or complex environments.

## Echo

{% embed url="<https://www.loom.com/share/ec25a6cffe8d453f9a17a8bc78ff06bc?_hsenc=p2ANqtz-8MGTvRuOTH3XaejHfvjNfsxH2DjtIzXG6hFVawg0UQ6DAN7XVPSemoBA7U8OqirVjUKYoHJxbz9T_Hd8jyLr2AUQ4UrQ&_hsmi=2&utm_content=2&utm_medium=email&utm_source=hs_email>" %}

### **Echo of Echo enables multi-generation database environments**

This release introduces Echo of Echo, which supports up to four generations of Echo databases derived from a single source. This capability enables advanced workflows like multi-stage development pipelines, progressive data masking, compliance validation, and A/B testing. By supporting deeper clone hierarchies, Echo allows teams to create more sophisticated test, development, and analytics environments while maintaining clear lineage between database generations.

### Enhanced SQL Server 2022 restore and database state awareness improve operational safety

This release expands Echo support for SQL Server 2022, introducing new capabilities that improve database protection, recovery flexibility, and operational safety:

<details>

<summary><strong>Database protection and recovery</strong></summary>

Echo now supports copy-only, application-consistent snapshots without VSS dependency, enabling reliable backups that preserve transactional consistency without disrupting existing backup chains. In addition, Echo supports restoring databases in `NORECOVERY` mode, allowing databases to be restored without being brought online so additional recovery steps (like log replay) can be performed.

</details>

<details>

<summary><strong>Database state and status</strong></summary>

To improve operational safety, Echo now provides enhanced database state and status visibility, detecting and displaying a broader range of SQL Server database states and preventing unsupported operations on databases that aren’t in a valid operational state. Databases in states like `RECOVERY_PENDING`, `SUSPECT`, or `EMERGENCY` are treated as offline, aligning Echo behavior with native SQL Server status reporting and reducing the risk of invalid actions during recovery workflows.

</details>

### Expanded clone depth supports advanced data workflows

Silk supports up to four levels of clone-of-clone depth, expanding the previous two-level limit.

This enhancement enables more complex development, testing, and staging workflows, including multi-stage pipelines and chained environments. It also aligns with advanced Echo use cases that rely on deeper snapshot and clone hierarchies.

### Echo user experience enhancements simplify host and snapshot management

The Echo interface includes improvements designed to streamline daily operations and improve navigation.

The Echo dashboard has been redesigned with a modern layout that simplifies navigation while retaining core host and database management capabilities.

In addition, a new dedicated snapshots view provides a flat, sortable grid for snapshot administration. This view makes it easier to identify unused snapshots, assess usage impact, and perform cleanup or optimization tasks efficiently.

### Echo APIs are updated to improve usability while maintaining backward compatibility

Silk Echo API documentation is now accessible directly within the Echo user interface via the **Settings** menu (**Settings > Echo API Docs**), making it easier for users to discover and work with Echo APIs without leaving the product.

The embedded API documentation features a modern, developer-friendly interface with a clean, dark-themed layout. APIs are organized in a searchable list by resource and operation, with clear visual indicators for HTTP methods. Selecting an API displays its details in a dedicated pane, allowing users to quickly review endpoints, parameters, and request behavior. Quick-access links to the OpenAPI JSON and GitHub documentation are also available for advanced workflows.

In addition to these documentation enhancements, Echo introduces updated API routes while **maintaining backward compatibility** with existing integrations. Previous APIs continue to be supported, giving you time to transition without disruption.

### Host unregistration validation protects Echo-managed resources

The Echo host unregistration workflow now includes a validation that prevents unregistering a host while Echo Databases or DB-snapshots remain associated with it. If dependent resources exist on the host, the system blocks the unregistration request and displays a detailed notification identifying:

* Which resources are blocking unregistration
* The order in which they must be removed

This validation ensures Echo-managed resources are removed safely before host unregistration, maintaining consistency across Echo.

### Bulk installation supports Echo Host Agent deployment at scale

A new bulk installation tool is now available to streamline deployment of the Echo host agent across multiple Windows hosts. This tool reduces manual effort, improves consistency, and accelerates large-scale or initial Echo deployments. This is especially useful for large environments, initial rollouts, and standardized DevTest or CI/CD infrastructure.


---

# 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/releases/2026/v8.6.10/features-and-enhancements.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.
