Auto Backup
Last updated
Was this helpful?
Last updated
Was this helpful?
With GRAX Auto Backup, you’re just a few clicks away from securely backing up your entire Salesforce org.
Create an and configure their permissions
Once the integration user is connected, GRAX:
Periodically describes all the objects and schema in your org and adds them to the Auto Backup system.
Starts periodic jobs that pick an object and back up everything new or changed since the last backup.
To enable Auto Backup:
Navigate to the Auto Backup tab within the GRAX Application
You'll see the screen below, and will be prompted to choose one of the following options: Start Auto Backup to current bucket or Change the storage provider/bucket
When setting up Auto Backup for the first time, GRAX starts by backing up object data in Salesforce, beginning with the oldest modified records and progressing to the most recently modified ones. Once the initial backup is complete, Auto Backup seamlessly transitions to periodically capturing ongoing data changes.
The Auto Backup Dashboard in the GRAX Application serves as the central hub for tracking key metrics and statuses. It provides insights into the total volume of data backed up, the time frames covered by secure backups, and the historical progress of Auto Backup operations.
You can easily control Auto Backup behavior with the following options:
Backup Objects and Files: Capture all available data objects
Backup Objects, Pause Files: Exclude file data from the backup
Backups Paused: Disable all backup operations
Additionally, the dashboard displays detailed status information, as outlined below:
Backfilling: GRAX is backing up the history of your org, and at least one object has never been fully backed up
Behind: All objects were fully backed up previously, but backup has since fallen behind for at least one object
Running Continuously: GRAX is operating as expected and up to date on all objects within expected SLA
Paused:Auto Backup has been paused by a user for records, files, or both
Error: An error has been encountered by the app while backing up data
The dashboard also contains a list of files and objects being backed up along with record count and version count. Objects can have the following statuses:
Waiting: object is caught up and waiting for new data
Running: object is nearly caught up and backing up new data
Backfilling: object is still backing up initial data
Paused: object isn't being processed because Auto Backup has been turned off
Excluded: object isn't being processed because it has been explicitly excluded by the user
Unavailable: object isn't being processed because GRAX has lost access to the object in Salesforce
“There are two methods for excluding objects from backup: one on the Salesforce side and one within the GRAX Application.
Auto Backup is built to back up all possible Salesforce data by backing up every object the Integration User has permission to view. This design lets you manage what objects are backed up with standard Salesforce permissions and automatically backs up new custom objects or fields without the need to modify GRAX settings. If you don't want GRAX to back up an object or field because it isn't restorable, or isn't valuable to your data strategy, deny access to the object or field for the GRAX integration user.
On the Settings page, under General Settings, you’ll find the Auto Backup Exclusions field. Here, you can enter a comma-separated list of object API names to exclude from future backups. Once specified, these objects will be ignored in subsequent backups. However, if an object has already been backed up, it will still appear in the Objects list with an Excluded status.
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 Data Lake working as expected.
GRAX offers an option to change the period of scans between "daily" and "continuous."
Daily Auto Backup: scans for new data once a day
Continuous Auto Backup: scans for new data at a minimum of every hour
In the backup dashboard, you’ll observe continuous activity during the initial backup and ‘backfill’ process. Afterward, daily scans will occur for each object, with activity distributed throughout the day.
No further configuration is necessary, or possible, on your part.
Example: salesforce INSUFFICIENT_ACCESS: insufficient access rights on cross-reference id
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.
An error has occurred within the Salesforce backend infrastructure, outside the scope of the GRAX Application. Please contact Salesforce support to open a case and report the issue.
Additionally, the Excluded Objects tab displays objects that are not being backed up due to being unsupported; you can read more about supported objects .
to enable Daily Backup for your deployment.
While GRAX captures the definitions of formula fields as part of , it does not execute the formula logic when displaying field values or performing searches. Since formula fields are calculated in real time based on other field values and do not result in actual data changes, updates to these fields do not modify the SystemModStamp. As a result, changes to formula field values do not trigger the creation of a new record version. Therefore, the values displayed for formula fields reflect their state at the time of the most recent record backup.
Review your 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 for more information.
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 .
