Which version of your data can you recover?
A backup is a saved copy of data, perhaps taken before an import, a database migration or the deletion of old records. You can use it to restore that earlier state when current data is damaged or missing.
The time of the backup matters. Last night’s copy will not contain orders placed this morning. Before restoring it, account for the changes made since that copy was created.
Records and attachments belong together
An order may be a database record while its attachment is stored as a file. Restoring the database alone can leave a record pointing to a file that no longer exists. Back up and check both parts so they represent a consistent state.
A saved archive still needs a restore test
A backup policy sets how often copies are created and how long they are kept. Check their location too: a copy on the same disk will not protect you if that disk fails. Covering that failure requires another copy in a separate storage location.
Test restores regularly to check that the archive opens and the application works with the recovered data. Include a check that attachments are accessible.
Enabling Easy Backup in MainPath
For projects with a MySQL backend, you can enable Easy Backup in the project configuration. It runs in production and backs up the database and uploads on a schedule or on demand. The archives are stored on the server, so this alone does not create a copy outside that server.
The backup documentation covers setup, retention and restoration. Check whether Easy Backup is enabled for your project and which backups are actually available.