Ensuring your data is safe and secure is an important part of your ongoing account security. Having a backup is not only for disaster recovery, but can also be useful for smaller scale accidental errors, or referencing historical data for time-based comparisons.
Whilst Beacon takes full platform-wide backups of all customers every day, backing up your own account's data is your responsibility. We provide a variety of methods for creating backups, depending on your organisation's processes and technical abilities.
Why do we need to back up data?
If there was a major system-wide disruption, don't worry, Beacon's got those backups covered! However, those backups aren't designed to make ad-hoc restorations for individual accounts or undo day-to-day changes, and are therefore not accessible to customers.
Keeping your own regular exports is the best way to protect against accidental deletions, bulk-edit mistakes, or integration errors, giving you complete control to recover your specific data whenever you need it.
Short-term historical data
Beacon provides a method for exporting data as it was any time in the last 7 days via our Time Machine feature. No need to dig through your backups - Time Machine makes data from the last week super accessible!
Creating backups
Backing up your record data - that is, the data stored in the fields and record types of your account - should be the primary information that you'll want to create a process for. You can access this data via CSV exports either manually from Beacon or automated via the API, or you can create custom configurations with Beacon Data Warehouse.
Manual exports
Manually exporting your data to a CSV file is the easiest way to take a copy of your record data and requires no setup. For each record type in your account, simply got to its list page, select all records, and choose to export using the ‘All fields’ export option.
Automated exports
If you would like to automate backups, you can either use Beacon's API to trigger a CSV export, or pull data directly from your account using Beacon Data Warehouse - likely via a connector to your storage location of choice.
Whichever option you choose, you would store the data in a secure location outside of your Beacon account.
Account schema
Though record data is the usual focus, you may also want to take a backup copy of your account’s structure and field configuration. This is available via our API, and will return a JSON structure with full field and record type configuration.
Backup considerations
Backup retention period
We recommend setting a fixed length of time that you retain your backups. For example, at Beacon we hold full platform backups for both our own as well as customer data for 30 days. Where possible, this should be automated so that it is not help for longer than it is meant to be.
GDPR Right to erasure or Subject access requests
As long as there is a process for managing retention time periods, backups are usually not in scope for right to erasure or subject access requests (SARs), but you should still consider communicating their existence and how that data is handled in your response to the requester.
Frequently asked questions
Are timeline activities able to be backed up?
Yes - activities in the timeline, such as emails, notes, meetings, etc. are stored as their own Activities record type and can be exported for backups like any other record type.
Are there items that I can't back up?
Yes - the following items are not available to export or access other than directly through the Beacon interface.
Dashboards
Relationships
Files in 'File upload' fields
Record audit logs
Template configuration (import, export, document, email)
Form configuration
Workflow configuration
Users
Roles and permissions
Other account settings

