This article illustrates many of the key best practices for the backup process on the Vault platform:
- Configure full backup that includes all the objects (standard and custom) in Salesforce Org. Recommended frequency is weekly, preferably on weekends.
- Configure a backup for special objects like history, system, audit logs, and KAV objects on a weekly basis. Can be set to a daily basis, if needed.
- Configure incremental backups to include all the objects in Salesforce. Recommended frequency for this backup is daily.
- Configure the scheduled time of full and incremental backups with enough time the gap between them to avoid any bottlenecks in Salesforce, that may be caused due to queries being executed on the same objects in parallel.
- Create backup schedules which are in sync with your production deployment schedules. Backup entire production instance or relevant instance data before deploying to a production instance
- Identify a set of business-critical objects. Configure a backup specifically to include these objects to run at higher frequency levels (recommended frequency is multiple times a day) depending on RPO and RTO requirements.
- Use the option to exclude formula fields in the case of objects with a large number of fields, without which it may result in Salesforce queries being errored out or giving results slowly.
- Configure email addresses of users who need to be notified upon completion or failure of backups. (By default, the user who configured the backup will be notified automatically).
- Go through logs and results of backups on a weekly basis to ensure that automated backups are happening as expected.
- Adjust frequency and scheduled time of backup configurations based on API call limit and API calls consumption by other systems.
- Salesforce user with which an org is registered on Vault should have admin-level permissions in the org. The recommendation is to create an admin user separately for Vault.