> 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/products-and-core-concepts/silk-product-fundamentals/silk-echo-overview.md).

# Silk Echo Overview

Learn how Silk Echo creates fast, storage-efficient database copies without disrupting production.

## Echo Introduction

Silk Echo creates production-scale database copies in seconds without disrupting production workloads. Teams get writable, isolated environments while consuming additional storage only as data changes.&#x20;

Echo uses point-in-time database snapshots to provision thin, writable copies called **Echo Databases**. An Echo Database initially shares its underlying data with the snapshot and consumes additional storage only as its data changes. This approach allows teams to create database copies in seconds while reducing the capacity and operational overhead traditionally associated with full database copies.&#x20;

### How Echo works

Echo coordinates database workflows between your database hosts.&#x20;

{% stepper %}
{% step %}
Echo discovers a source database on a registered host.
{% endstep %}

{% step %}
Echo creates a point-in-time **DB-Snapshot** of the database.
{% endstep %}

{% step %}
Echo creates thin copies of the underlying volumes.
{% endstep %}

{% step %}
Echo maps the cloned volumes to a target host and presents them as a writable **Echo Database**.
{% endstep %}

{% step %}
The DB-Snapshot remains available for creating additional Echo Databases or refreshing existing ones.
{% endstep %}
{% endstepper %}

```mermaid
flowchart LR
    A["Source Database"] --> B["DB-Snapshot"]
    B --> C["Echo Database"]
    B --> D["Additional Echo Databases"]

    style A fill:#ffffff,stroke:#dc1e70,stroke-width:2px
    style B fill:#fce8f1,stroke:#dc1e70,stroke-width:2px
    style C fill:#fce8f1,stroke:#dc1e70,stroke-width:2px
    style D fill:#fce8f1,stroke:#dc1e70,stroke-width:2px
```

Since each Echo Database is writable and isolated, users can modify or refresh a copy without changing the source database or other copies created from the same snapshot.

### What you can do with Echo

<details>

<summary><strong>Create production-scale database copies</strong></summary>

Provision writable database copies for development, testing, analytics, and other secondary workloads without creating a full physical copy of the source database.

</details>

<details>

<summary><strong>Create reusable recovery points</strong></summary>

Capture point-in-time DB-Snapshots and reuse them to provision multiple Echo Databases. Echo supports both application-consistent and crash-consistent snapshots, depending on your database platform and configuration.

Recovery isn't limited to snapshot granularity — see [#restore-databases-from-snapshots](#restore-databases-from-snapshots "mention") for how to recover to a specific point in time between snapshots.

</details>

<details>

<summary><strong>Refresh databases</strong></summary>

Refresh an existing Echo Database from another DB-Snapshot without recreating the database or remapping its applications and hosts.&#x20;

{% hint style="warning" %}
Refreshing an Echo Database overwrites changes made to the database since its previous refresh.
{% endhint %}

</details>

<details>

<summary><strong>Create multi-generation database environments</strong></summary>

With **Echo of Echo**, an Echo Database can serve as the source for another Echo Database. This creates a traceable database lineage that supports layered development pipelines, parallel testing, progressive changes, and controlled experimentation.

Echo supports up to **four generations** of Echo Databases from an original source database. Multi-generation environments are intended for testing, validation, analytics, and experimentation rather than for performance-sensitive workloads.

</details>

<details>

<summary><strong>Restore databases from snapshots</strong></summary>

Use DB-Snapshots to create or upload Echo Databases for recovery, validation, and troubleshooting workflows.&#x20;

For supported SQL Server workflows, **Restore without Recovery** leaves the database in a `RESTORING` state so you can apply transaction logs using standard SQL Server tools and recover the database to a specific point in time.

{% hint style="warning" %}
**Restore without Recovery** is an advanced workflow and isn't the default restore behavior in Echo. Support for this workflow depends on the snapshot consistency method and SQL Server version.
{% endhint %}

</details>

<details>

<summary><strong>Understand database relationships</strong></summary>

Use **Echo Constellation** to visualize the relationships among hosts, source databases, DB-Snapshots, and Echo Databases.&#x20;

Constellation provides two complementary views:

* **System view:** Explore the overall Echo environment and see where hosts, databases, snapshots, and Echo Databases are located.&#x20;
* **Lineage view:** Trace the history and dependency chain of a database, including its snapshots and multiple generations of Echo Databases.

These views help you understand database lineage, indentify dependent resources, and manage Echo resources from a centralized visual workspace.&#x20;

</details>

### Common use cases

Echo supports database workflows that require fast, repeatable access to production-like data.&#x20;

<table data-search="false"><thead><tr><th width="246.3333740234375">Use case</th><th>How Echo helps</th></tr></thead><tbody><tr><td><strong>Development and testing</strong></td><td>Quickly create isolated, writable database environments for developers and testers.</td></tr><tr><td><strong>CI/CD validation</strong></td><td>Provide repeatable database environments for validating application, schema, and infrastructure changes.</td></tr><tr><td><strong>Troubleshooting</strong></td><td>Reproduce issues using production-scale data without affecting the source environment.</td></tr><tr><td><strong>Analytics</strong></td><td>Create separate database copies for reporting and analytical workloads.</td></tr><tr><td><strong>AI and machine learning</strong></td><td>Provide production-scale data environments for data pipeline development, feature engineering, model training, and experimentation.</td></tr><tr><td><strong>Recovery and validation</strong></td><td>Restore databases from known points in time and validate data or corrective actions before bringing workloads online</td></tr><tr><td><strong>Parallel experimentation</strong></td><td>Create multiple database branches from the same snapshot or Echo Database to test changes independently.</td></tr></tbody></table>

## Understand Echo architecture

Echo brings together Silk platform components and supported database technologies to coordinate snapshot and cloning workflows.

### Echo components

Echo works with Flex, DataPods, database hosts, and the Silk Host Agent.&#x20;

{% columns %}
{% column %} <i class="fa-joystick">:joystick:</i>

**Flex** provides access to the Echo interface and coordinates Echo management workflows.
{% endcolumn %}

{% column %} <i class="fa-sliders-simple">:sliders-simple:</i>

**DataPods** provide the underlying snapshot, volume, and thin-cloning capabilities used to create DB-Snapshots and Echo Databases.
{% endcolumn %}

{% column %} <i class="fa-server">:server:</i>

**Database hosts** host the source database and Echo Databases managed through Echo.
{% endcolumn %}

{% column %} <i class="fa-user-robot">:user-robot:</i>

The **Silk Host Agent** discovers databases and coordinates snapshot, cloning, refresh, restore, and host operations.
{% endcolumn %}
{% endcolumns %}

An Echo environment can include hosts connected to multiple DataPods. However, each Echo operation occurs within the context of a single DataPod.

### Supported database platforms

Echo capabilities and requirements vary by database platform.

<table><thead><tr><th width="236.962890625">Database platform</th><th width="173.3333740234375">Availability</th><th>Overview</th></tr></thead><tbody><tr><td><strong>Microsoft SQL Server</strong></td><td>Generally available</td><td>Supports thin database cloning and application-consistent or crash-consistent snapshot workflows on supported Windows and SQL Server versions.</td></tr><tr><td><strong>Oracle pluggable database (PDB)</strong></td><td>Beta</td><td>Supports Oracle PDB cloning workflows with additional host, storage, and database configuration requirements.</td></tr></tbody></table>

Review the installation documentation for your database platform before installing Echo.&#x20;

## Access Echo

Echo supports both interactive and automated management.&#x20;

* Use the **Silk Flex UI** to register hosts, explore databases, create and manage DB-Snapshots and Echo Databases, and view resource relationships.
* Use the **Silk Echo API** to automate host, snapshot, cloning, refresh, and database lifecycle workflows.&#x20;

Your assigned user role determines how you access Echo.

{% tabs %}
{% tab title="Flex user" %}
This role is recommended for administrators who manage Echo alongside the broader Silk environment and DataPod resources.
{% endtab %}

{% tab title="Echo user" %}
This role is recommended for database, DevOps, QA, or application users who require Echo access without broader DataPod management permissions.&#x20;
{% endtab %}
{% endtabs %}

Flex users can open Echo from the settings menu in Flex. Echo users can access Echo directly through the Flex address using their Echo credentials.&#x20;

## Manage Echo resources

Echo provides three primary workspaces:

* **Hosts** provide a host-centered view for managing registered hosts, databases, DB-Snapshots, or Echo Databases.
* **DB Snapshots** provides a searchable, centralized inventory of all DB-Snapshots, including their consistency type, creation details, usage, and dependencies.&#x20;
* **Constellation** visually maps Echo resources and their relationships across the environment.&#x20;

Resources created through Echo should also be managed and deleted through Echo. This allows Echo to track database relationships and dependencies and helps prevent orphaned or inconsistent resources.&#x20;

Administrators can use **cascade deletion** to remove an Echo Database or DB-Snapshot together with its dependent Echo resources. Echo displays the affected resources for review before the deletion is confirmed.

## Next steps

* **Deploy Echo** to prepare your environment, configure database hosts, and deploy the Silk Host Agent.
* **Use Echo** to access the dashboard and create and manage DB-Snapshots and Echo Databases.
* **Use the Echo API** to integrate Echo operations into automated workflows.
* **Deploy Oracle PDB on Echo** to learn about the requirements and workflows available for Oracle PDB environments.


---

# 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/products-and-core-concepts/silk-product-fundamentals/silk-echo-overview.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.
