Plan how Commvault protects your BigCommerce data. In most environments, you can start with recommended defaults and adjust only if your environment requires it.
Start with your BigCommerce environment
One BigCommerce configuration covers one BigCommerce store. If your organization operates multiple BigCommerce stores for isolation by region, environment (production, test, development), or business unit, configure protection separately for each store.
Align storage with your BigCommerce region
BigCommerce is a SaaS API workload. The access node and the backup storage destination have no regional placement requirements. You can use an access node and storage in any region without affecting backup or restore performance.
Understand backup behavior
Every backup is a full backup of the entire store. Incremental backup is not supported because the BigCommerce API does not expose a change-delta or event log that Commvault can use to detect changes. Each backup job retrieves all 20 resource types (products, customers, orders, marketing assets, storefront theme, and fulfillment configuration) regardless of what has changed since the previous backup.
Decide how to scope your data
Backup scope is always the full store. You cannot exclude individual resource types at backup time. After a backup completes, you can restore individual resource types selectively (for example, restore only Products, or only Customers) if you do not need to restore the entire store.
Organize backups logically
Use subclients to organize the backups based on how your organization manages BigCommerce data. Common approaches include grouping by environment (production, test, or development), business unit or application, or data sensitivity or compliance requirements — whichever helps you apply consistent policies and simplifies monitoring and reporting.
Plan for performance
Backup and restore performance depends on data size, change rate, and API rate limits. To optimize performance, avoid unnecessary fragmentation of protection scopes, and schedule backups to avoid peak store activity periods. BigCommerce enforces API rate limits that vary by plan tier (typically 150–500 requests per minute on Standard and Pro plans). Commvault applies adaptive throttling to stay within the rate limit automatically.
Confirm permissions early
Make sure the required BigCommerce permissions are in place before configuring protection. For details, see Configure BigCommerce user and permissions.
Understand key limitations
Key limitations include: - Incremental backup is not supported. Every backup is a full backup. - Customer passwords cannot be restored. - Payment gateway credentials must be reconfigured manually after a restore. - Tax class IDs are read-only and can differ across stores.
For the complete list of limitations, see BigCommerce.