# Configure and validate backups for BigCommerce

Set up and validate backups for BigCommerce.

Service provider configurations

Before onboarding BigCommerce backups, service providers must complete the following configurations:

- Add an access node
- Create a workload resource pool for SaaS applications

For instructions, see Configure SaaS applications for service providers.

## Onboard BigCommerce

Onboard a BigCommerce store to begin protecting your BigCommerce data. During onboarding, you connect to BigCommerce, choose the content to protect, assign a backup plan, and create the backup configuration.

### Start the configuration

1. From the Command Center navigation pane, go to Protect > SaaS applications.
2. Click Add SaaS Application.
3. Select BigCommerce, and then click Next.

### Specify credentials

Cloud App Connection Details

- In the Name field, provide a display name for this BigCommerce backup configuration.

Configure Credential

- Store Hash: Enter your BigCommerce store hash (for example, `ptwj8fgzwt`). You can find this value in the BigCommerce Admin Panel under Settings > API > API Accounts.
- API Access Token: Enter the V2/V3 API access token you created with the required scopes. For details on creating the token, see Configure BigCommerce user and permissions.

### Choose the backup content

- Click the pencil (edit) icon next to Content.
- The backup scope is always the full store (all 20 resource types). You cannot exclude individual resource types at this stage. After the backup completes, you can restore individual resource types selectively if needed.

### Select a backup plan

- Select an existing backup plan, or click + to create a new one.
- After you create a backup plan, you can select it when you onboard additional BigCommerce stores.

/// important Use a backup plan created on Commvault Air Gap Storage (Amazon S3, Azure Blob Storage, or Google Cloud Storage). ///

### Review summary

- Review the store name, plan name, schedule, and backup content.
- Click Submit.

## Run a backup

1. From the Command Center navigation pane, go to Protect > SaaS applications.
2. For the BigCommerce store that you want to back up, click the action button , and then click Back up now to run a Full backup.
3. Monitor job progress in the Jobs view.

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. Backups can take longer if the rate limit is reached frequently. The job log shows when the backup is waiting for the rate limit to reset.

## Validate the backup

### Verify the configuration

After you assign the backup plan, confirm that:

- The BigCommerce store appears in the Protect > SaaS applications list with the name you provided.
- The Content column shows the full store scope (all resource types).

### Confirm that the backup completed successfully

1. From the Command Center navigation pane, go to Job controller > All jobs.
2. Locate the completed backup job for your BigCommerce store.
3. Verify that the job status is Completed.
4. Check the job details to confirm:
5. All 20 resource types were backed up (products, customers, orders, marketing assets, storefront theme, content pages, fulfillment configuration).
6. The total number of objects backed up matches your store size (for example, 142 products, 87 customers, 203 orders).
7. The job log shows the storage used (typically 5 MB to 500 MB for a mid-size store, including product image binaries).

### Test a restore

1. From the Jobs view, select the completed backup job.
2. Click Restore.
3. Choose the restore destination:
4. Same store (in place): restores to the original BigCommerce store.
5. Different store (out of place): restores to a different BigCommerce store. You must provide the target store hash and API access token for the target store.
6. Select the resource types to restore (for example, restore only Products and Customers, or restore all 20 resource types).
7. Choose the restore mode:
8. missing-only (default): creates items that do not exist in the target store, skips items that already exist.
9. full-overwrite: creates new items and updates existing items with backup data.
10. wipe-and-restore: deletes all existing data in the target store before restoring (destructive operation; use with caution).
11. Click Submit.
12. Verify that the restore completes with status Completed and that the data matches the original.

For complete restore procedures, see Restore BigCommerce data.

## Common causes of failures and what to check first

If a backup or restore fails, check the following:

Authentication and permission issues:

- The store hash is correct and matches the BigCommerce store you are protecting.
- The API access token is valid and has not been revoked.
- The API token has the required scopes with the appropriate permission level (Read-only for backup, Modify for restore).
- The token type is Store-level V2/V3 API (not Account-level or Storefront API).

Network access issues:

- The access node can reach `api.bigcommerce.com` on port 443.
- The access node can reach the backup storage destination (Air Gap Storage) on port 443.
- If you use a Commvault-managed access node, the access node IP address is allowlisted in your BigCommerce store settings.

Backup job failures:

- The backup plan is created on Commvault Air Gap Storage (Amazon S3, Azure Blob Storage, or Google Cloud Storage).
- The job log shows whether the failure occurred during API retrieval or during storage write. If the failure is during API retrieval, check authentication and rate limits. If the failure is during storage write, check the MediaAgent and storage destination configuration.

Restore failures:

- For out-of-place restores, the target store hash and API access token are correct and the target token has Modify permission on all required scopes.
- For wipe-and-restore mode, confirm that the target store has deletable data. Some resource types (tax classes, store information, currencies, shipping zones, themes) cannot be deleted via the BigCommerce API and are overwritten instead.
- If variant images fail to restore, check whether the original CDN image URLs have expired. Variant images are restored using the original URL only because the BigCommerce variant image endpoint rejects direct binary uploads.

×

Loading...