ExaGrid Tiered Backup Storage provides a disk-based backup storage solution designed for enterprise and hybrid data protection requirements. The ExaGrid’s tiered architecture enables fast backups and restores, scales easily, controls storage costs, and remains simple to operate.
The system supports scale-out growth without rebalancing upgrades. It also simplifies backup storage operations, requiring minimal tuning and no rehydration for restore. Additionally, the system can seamlessly integrate with Commvault Command Center, Commvault CommCell Console and Commvault SaaS.
Configuring ExaGrid Tiered Backup Storage System
The following configuration flow describes how to configure ExaGrid shares and integrate them with Commvault:
-
Use the ExaGrid user interface to create ExaGrid shares.
-
Present the ExaGrid shares to Commvault by using SMB or NFS.
-
In Commvault, define the ExaGrid shares as disk storage and enable Spill and Fill.
-
Create a dedicated storage policy and storage pool for ExaGrid.
-
Configure backup schedules and, if required, auxiliary copy workflows.
Backup
ExaGrid recommends the following backup schedules:
-
Initial full backup
-
Daily incremental backups
-
Weekly synthetic full backups
-
Periodic true full backups (Non-synthetic)
Encryption and Compression
Encryption
Validate any Commvault features that require client-side or third-party encryption during sizing and design.
Disable Commvault software encryption at all levels when backing up to ExaGrid system. This includes clients, subclients, storage policies, and deduplication engines.
Compression
Enable Commvault compression only if required by organizational policy or network bandwidth constraints. If enabled, apply compression consistently across all subclients and storage policies.
Deduplication
Storage policies when Commvault deduplication is enabled or disabled
Use the following guidelines when configuring storage policies for ExaGrid:
-
Use dedicated storage policies and storage pools for ExaGrid.
-
If Commvault deduplication is enabled, create a new, ExaGrid-specific Deduplication Database (DDB).
-
Enable Commvault deduplication only if it is included in the ExaGrid system sizing.
-
In most environments, disable Commvault deduplication and allow ExaGrid to handle all deduplication for better performance and simpler management.
Note
Enable deduplication only if it is included in the ExaGrid system sizing.
Sizing and Performance
Follow these guidelines to ensure optimal performance and reliability:
-
Size the system based on the volume of protected data, data change rate, retention requirements, and expected backup and restore performance.
-
Plan for peak workloads by considering backup windows, concurrency, and the number of Commvault MediaAgents writing to ExaGrid.
-
Use Commvault deduplication only when it is included in the ExaGrid sizing exercise. If it is not included, rely on ExaGrid native deduplication for best results.
-
Ensure sufficient network bandwidth between MediaAgents and ExaGrid to sustain backup and restore throughput. Low latency improves overall performance.
-
Optimize restore performance by recovering data from the ExaGrid Landing Zone whenever possible.
Auxiliary Copies and Replication
Supported Data Protection Strategies
Select the ExaGrid data protection strategy that best matches your retention requirements, available bandwidth, and operational preferences.
-
ExaGrid Replication – Replicates deduplicated data to another ExaGrid system or to the ExaGrid Cloud Tier in AWS or Azure for disaster recovery.
-
Commvault Auxiliary Copies (DASH or standard AUX) – Copies backup data from a primary ExaGrid system to a secondary target, which can include another ExaGrid appliance.
Disaster Recovery
-
Use an appropriate backup strategy – Maintain tertiary copies on two different media types, with at least one copy stored offsite.
-
Leverage offsite ExaGrid options – Use a secondary ExaGrid system or the ExaGrid Cloud Tier for offsite retention.
-
Protect Commvault infrastructure – Back up CommServe databases and other critical components to a separate ExaGrid share dedicated to disaster recovery.