Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
cloudappliance/backupbp [2018_01_30 17:23] – external edit 127.0.0.1 | cloudappliance:backupbp [2024_02_28 01:03] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Best Practices for File Fabric | + | # Appliance Backups |
- | ===== General Considerations | + | ## General Considerations |
- | * File Fabric | + | * Access Anywhere |
- | * Both the Web server component of the File Fabric | + | * Both the Web server component of Access Anywhere |
- | ===== Appliance | + | ## Appliance |
Because the contents of an Appliance that does not contain a database (perhaps better termed a "Web server" | Because the contents of an Appliance that does not contain a database (perhaps better termed a "Web server" | ||
Line 14: | Line 14: | ||
When several Appliances with identical configurations are used in an HA configuration, | When several Appliances with identical configurations are used in an HA configuration, | ||
- | ===== Database Backups | + | ## Database Backups |
- | ==== Ensuring Consistency | + | ### Ensuring Consistency |
To ensure consistency in the backed up data, the database should be backed up during periods when it is not being updated. While it is being backed up, both user access and scheduled processing (including cron jobs) should be suspended. | To ensure consistency in the backed up data, the database should be backed up during periods when it is not being updated. While it is being backed up, both user access and scheduled processing (including cron jobs) should be suspended. | ||
- | ==== Physical and Logical Backups | + | ### Physical and Logical Backups |
SME's MySQL (MariaDB) database can be backed up in two ways: | SME's MySQL (MariaDB) database can be backed up in two ways: | ||
Line 29: | Line 29: | ||
Logical backups are generally easier to work with than physical backups, but recovery may take longer with logical backups. | Logical backups are generally easier to work with than physical backups, but recovery may take longer with logical backups. | ||
- | You may wish to retain several generations of database backups so you will have a choice of points in time for recovery. To meet this requirement the database can be backed up to a timestamped file with several generations of backups retained on a rolling basis. | + | You may wish to retain several generations of database backups so you will have a choice of points in time for recovery. To meet this requirement the database can be backed up to a timestamped file with several generations of backups retained on a rolling basis. |
- | ==== Appliances with Internal | + | ### Appliances with Internal |
For Appliances with internal databases one backup can serve both purposes: Appliance backup and database backup. In this situation it is the database changes, which occur frequently and in large numbers on a typical system, that drive the backup frequency. | For Appliances with internal databases one backup can serve both purposes: Appliance backup and database backup. In this situation it is the database changes, which occur frequently and in large numbers on a typical system, that drive the backup frequency. | ||
- | ==== Appliances | + | ### Appliances |
Where the database is external, the Appliance and the database need to be handled separately. Database backup files can be made and rotated as described in the previous section, but stored on the database server or on some other reliable storage. | Where the database is external, the Appliance and the database need to be handled separately. Database backup files can be made and rotated as described in the previous section, but stored on the database server or on some other reliable storage. | ||
- | |||