# Plan your Snowflake deployment

Plan how Commvault protects your Snowflake data. In most environments, you can start with recommended defaults and adjust only if your environment requires it.

## Start with your Snowflake environment

Your Snowflake deployment determines how you configure protection.

If you use a single account, you can usually manage protection with a single configuration. If you use multiple accounts for isolation—such as by region, environment, or business unit—plan to configure protection separately for each account.

Also consider the following factors, which affect storage placement, performance, and restore options:

- Regions and cloud providers used by your Snowflake accounts

- Whether data is distributed across regions or accounts

## Align storage with your Snowflake region

Where you store backups has the biggest impact on cost and performance.

Recommended approach: Use backup storage in the same cloud provider and region as your Snowflake account.

This approach:

- Minimizes latency

- Avoids egress charges

- Improves backup and restore performance

If you use a different region for resilience or compliance, expect higher costs and longer backup and restore times.

## Understand backup behavior

Backups are incremental after the initial full backup, and behavior depends on how your tables are defined.

Tables without primary keys are protected only during full backups. If you need regular protection for these tables, create separate subclients and assign a plan with scheduled full backups.

## Decide how to scope your data

Define what data you want to protect and at what level.

Recommended approach: Start with broader scopes, such as databases or schemas.

Use more granular scopes only when required, such as:

- Different retention requirements

- Different access controls

- Separate compliance boundaries

Overly granular configurations can increase management overhead without improving protection.

## Organize protection logically

Use subclients to organize protection based on how your organization manages data.

Common approaches include grouping in the following ways, which helps you apply consistent policies and simplifies monitoring and reporting:

- Environment, such as production, test, or development

- Business unit or application

- Data sensitivity or compliance requirements

## Plan for performance

Backup and restore performance depends on data size, change rate, and region alignment.

To optimize performance:

- Align storage with your Snowflake region

- Avoid unnecessary fragmentation of protection scopes

- Schedule backups to avoid peak workload periods

Large datasets or high change rates can increase processing time.

## Confirm permissions early

Make sure the required Snowflake permissions are in place before configuring protection.

For details, see Configure Snowflake user and permissions.

## Understand key limitations

Be aware of the following constraints when planning your deployment:

- Cross-region backups can increase latency and cost

- Highly granular protection scopes can increase management overhead

- Restore operations depend on permissions and target environment readiness

- Some Snowflake configurations or features might not be fully supported depending on your deployment

×

Loading...