Backup FAQ

Can I configure the backup schedule?

GRAX is designed to back up your entire Salesforce organization without complicated tools to configure objects, fields or schedules.

To achieve this, GRAX periodically scans your Salesforce organization for new data. If it finds new data, it then automatically schedules smaller jobs to backup new data while staying within Salesforce API limits, and within system limits to keep Backups, Archives, Restores, Searches and History Stream working as expected.

GRAX offers an option to change the period of scans between "daily" and "continuous."

Daily scans for new data once a day, where continuous scans for new data many times a day in succession after the last scan completed.

How do I use daily backup? How does it work?

Contact GRAX support to enable Daily Backup for your deployment.

In the backup dashboard you will see continual activity during initial backup and "backfill." After that you will see activity where every object is scanned once a day but at times spread throughout the day.

No further configuration is necessary or possible on your part.

When is Legacy Backup being retired?

See the Legacy Backup Retirement page.

What does "INSUFFICIENT_ACCESS" mean?

Example: salesforce INSUFFICIENT_ACCESS: insufficient access rights on cross-reference id

Review your Integration User permissions for View All Data, View All Files and other required permissions. If the error occurs on Campaign or other marketing related objects, try enabling "Marketing User" for the integration user.

See the User Fields reference doc for more information.

How does Auto Backup handle records where a field is updated in SFDC, but the record's "SystemModStamp" remains unchanged?

For the most part, each time a record is modified within SFDC, SFDC updates the SystemModStamp to reflect the date/time of the modification, however, there are certain fields (including, but not limited to formula fields), that when changed, do not result in an updated SystemModStamp. This is a SFDC limitation, not a GRAX limitation.

Auto Backup relies on a change in a record's SystemModStamp in order to identify, and therefore backup, new or changed data. If a record is being backed up for the first time, GRAX will backup the record with the value stored in SFDC at the time of backup, but if the record is modified after the initial backup and SFDC does not update the record's SystemModStamp, GRAX will not back up the change.

There are several documented workarounds detailing how to "trigger" a SystemModStamp update when fields that do not update the record's SystemModStamp are modified, one of which can be found here.

What does "UNKNOWN_EXCEPTION" mean?

Example: UNKNOWN_EXCEPTION: sfdc.keystone.catalog.blobforce.KeystoneGetBlobFromStoresException: Failed to get a blob from all stores: orgId=00AbC000000DeM0 keyPrefix=05T entityId=05T2R000016VbmO blobId=0KF2R00002uQzDX extentId=F00D0b000000GaMp0KE2R00001MVoIw1 [...] there are no stores that currently contain the extent= F00D0b000000GaMp0KE2R00001MVoIw1, so we can't read it!)

An error has occurred within the Salesforce backend infrastructure, outside the scope of the GRAX app. Please contract Salesforce support to open a case and report the issue.

The Auto Backup dashboard offers a CSV export of all errors to include with your support case.