Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
Next revisionBoth sides next revision
cloudappliance/backupbp [2018_01_30 17:23] – external edit 127.0.0.1cloudappliance/backupbp [2021_07_14 01:18] – [Deployment Options] steven
Line 1: Line 1:
-====== Best Practices for File Fabric Appliance Backups ======+# Appliance Backups
  
-===== General Considerations =====+## General Considerations
  
-  * File Fabric Appliance administrators should implement backup strategies that are consistent with their organisations' RPO and and RTO requirements.+  * File Fabric Appliance administrators should implement backup strategies that are consistent with their organisations' Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
   * Both the Web server component of the File Fabric Appliance and the database - which may be internal or external to the Web server VM - should be backed up.   * Both the Web server component of the File Fabric Appliance and the database - which may be internal or external to the Web server VM - should be backed up.
  
-===== Appliance Backups =====+## Deployment Options 
 + 
 +The File Fabric platform uses a service-oriented or component-based architecture.  Data and application service components can be co-located on a single virtual machine, or deployed as across many nodes. For small to mid-size production environments, the solution is typically deployed as a single virtual machine instance or "software appliance". 
 + 
 +This table compares single-node and multi-node deployment options and the impact they have on the Recovery Point Objective (RPO) and Recovery Time Objective (RTO). 
 + 
 +^ Deployment ^ Single Node ^ Multiple Nodes (e.g. Multi-AZ) ^ 
 +| Nodes | 1 | 4 minimum (2 app + 2 data) | 
 +| Database | Embedded | Active/Passive | 
 +| Backup Method | Instance Snapshot | Database Backup | 
 +| Recovery Point Objective (RPO) | Application data* – 1 day | Application data* – 0 seconds | 
 +|           | Files/objects – 0 seconds | Files/objects – 0 seconds | 
 +| Recovery Time Objective (RTO) | Several hours | App node - No loss of service | 
 +| | | Data node - Under an hour | 
 + 
 +* Application data includes configuration settings, cached storage metadata, user collaboration data (shared links, comments), and activity logs. 
 + 
 + 
 + 
 +## Appliance Backup
  
 Because the contents of an Appliance that does not contain a database (perhaps better termed a "Web server") change infrequently, RPO is generally a less significant driver for appliance backups than is RTO. A backup should be made of an Appliance with an external database when the Appliance level configuration has changed or when the branding has been revised. A static snapshot will work well for this purpose and will allow the Appliance to be recovered to a recent state quickly in the event of VM failure. Because the contents of an Appliance that does not contain a database (perhaps better termed a "Web server") change infrequently, RPO is generally a less significant driver for appliance backups than is RTO. A backup should be made of an Appliance with an external database when the Appliance level configuration has changed or when the branding has been revised. A static snapshot will work well for this purpose and will allow the Appliance to be recovered to a recent state quickly in the event of VM failure.
Line 14: Line 33:
 When several Appliances with identical configurations are used in an HA configuration, making Appliance backups may not be necessary. When several Appliances with identical configurations are used in an HA configuration, making Appliance backups may not be necessary.
  
-===== 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 31: Line 50:
 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. SME can provide professional services to automate this process. 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. SME can provide professional services to automate this process.
  
-==== Appliances with Internal databases ====+### Appliances with Internal Databases
  
 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 With External Databases ====+### Appliances with External Databases
  
 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.
- 
  
© Copyright 2024 Nasuni.