Legacy Backup Retirement
What's being done?
GRAX is ending support for Legacy Backup, often referred to as "GRAX Scheduled Process" (GSP) backups. This also includes complete retirement of backup management from within the Salesforce Managed Package.
This feature let users schedule hourly, daily, weekly, or monthly backups for individual objects from within the GRAX SFDC package scheduling tab.
Why is GRAX retiring support for this feature?
GRAX backups are now accomplished through Auto Backup. This is a more straightforward and performative way to automate the backing up of your entire Salesforce org with an hourly RPO (Recovery Point Objective), without configuration or selection objects or schedule.
In comparison, Legacy Backup can run less frequently, resulting in longer durations between snapshots of your CRM data. With Auto Backup, your RPO is reduced due to more frequent backups.
How does this impact me?
We require all customers using Legacy Backup to update to the required SFDC permissions and enable Auto Backup. Any reported issues with legacy backup after the given date are to be met with update requests.
There is no required backup downtime to switch backup subsystems and no data is lost in the cut-over.
To enable Auto Backup, GRAX enforces a small list of high-level permissions including total access to all data within the Salesforce org. This is consistent with GRAX's mission of protecting your entire dataset and ensuring safety in destructive features like Archive. This means that objects cannot be hidden or excluded from GRAX backups.
Backing up all of your objects, regardless of number, has a very small incremental cost. Compression and de-duplication of Salesforce records continually work to consume the smallest amount of cloud storage possible and often achieves a 95% smaller overall dataset in storage than in Salesforce. For dollar-amount predictions based on real customers, see here. There is no expected cost impact of the change to Auto Backup unless you:
- don't today run files backups but have a large number of files.
- Backup files today, but don't use the proper "Query All Files" permissions which Auto Backup enforces.
The two cases above are specific to storing more files data, the binary component of which gets stored in the bucket at a size ratio of 1:1 with Salesforce. This is the only expected noticeable increase in cost of running GRAX on Auto Backup.
What's the recommended workaround?
To avoid interruptions or issues with unsupported features, change over to Auto Backup as early as possible. For assistance, contact GRAX Support.
GRAX support for Legacy Backup ends on December 31, 2022.
How do I get more information?
If you have questions or need more information, please open a support ticket.
Updated 4 months ago