From 1fcbe2a3e799aa426d039960e767a26d964490bc Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 31 Aug 2021 23:04:51 +0000 Subject: [PATCH] --- .../ayanova/docs/ay-biz-admin-import-v7.md | 8 ++- docs/8.0/ayanova/docs/ops-form-backup.md | 69 ++++++++++++++++++- 2 files changed, 75 insertions(+), 2 deletions(-) diff --git a/docs/8.0/ayanova/docs/ay-biz-admin-import-v7.md b/docs/8.0/ayanova/docs/ay-biz-admin-import-v7.md index df1bfeda..b6200a6a 100644 --- a/docs/8.0/ayanova/docs/ay-biz-admin-import-v7.md +++ b/docs/8.0/ayanova/docs/ay-biz-admin-import-v7.md @@ -117,7 +117,13 @@ If you have any customized report templates they will need to be re-created or r ### RI / WBI Client access settings -The V8Migrate utility is not able to access settings in the optional add-on's RI and WBI and so is not able to automatically migrate their settings to AyaNova 8. +The V8Migrate utility is not able to access settings in the optional add-on's RI and WBI and so is not able to automatically migrate their settings to AyaNova 8. Instead it will automatically choose safe defaults for those settings and lock out Customer access. In v7 you would make those settings within the interface provided by those optional add-on's, in AyaNova 8 all those settings can be found under Administration -> Global Settings in the "Customer Access" section and need to be set manually. +### Enable Backup +AyaNova 8 has a built in [backup system](ops-form-backup.md) that will back up to the local drive automatically. It is disabled by default and must be enabled to work. + + + + diff --git a/docs/8.0/ayanova/docs/ops-form-backup.md b/docs/8.0/ayanova/docs/ops-form-backup.md index 3851700b..0826b5d6 100644 --- a/docs/8.0/ayanova/docs/ops-form-backup.md +++ b/docs/8.0/ayanova/docs/ops-form-backup.md @@ -1,3 +1,70 @@ -# DOCUMENTATION Placeholder +# OPERATIONS BACKUP FORM [Incomplete - under construction] + +AyaNova can automatically back up to the local file system once per day at a selected time. + +The backup form is where you can configure how the backup works, perform a test backup and download backups for offsite storage. + +The backup form is available to any User with the Operations Role selected and is located in the navigation panel under `Server Operations -> Backup` + +## Best practices for disaster recovery +AyaNova backs up to it's own server's **local** drive only. This is **not a full backup solution** only a partial one; you also need to store copies of the backups **off site** from the AyaNova server in case of hardware failure, natural disaster, theft etc. + +A backup only stored on the same server (or even in the same building) as the live data is no backup at all if hardware fails or a server is stolen or burns down in a fire. + +You should regularly download the backups for storage to a secure off-site location from the AyaNova server. Also keep in mind recovery time, if the data is stored in a location that is hard to access it will add to the time taken to recover the server and be back in business should there be a loss of data. + +### 10 backup rotation +Unless your industry has a different specific legal requirement that must be followed; we recommend the standard business practice of a 10 backup rotation system of retaining 10 copies of the daily backup. + +You would download the most recent backup to a secure offsite location daily, naming and rotating them by replacing the oldest one each in the following pattern: + +4 Daily backups Monday to Thursday ("Monday", "Tuesday", "Wednesday", "Thursday") +3 Weekly backups each Friday ("Friday1", "Friday2", "Friday3") +3 Monthly backups on the first of each month ("Month 1", "Month 2", "Month 3") + +This means you will have 10 secure, off-site backups available in total to restore from at all times going back as far as three months or as recently as the last business evening. + +The reason to keep so many backups is that there can be cases where critical data was lost but not noticed for some time, this system gives as much as three months to recover anything lost. + +It is also a reasonable precaution to keep a yearly offsite backup going back as many years as is practical to store or appropriate to your business (and any potential legal requirements for your industry). + + +## Configuration + +### Backup time +Choose a time for the automatic backup when the server will be least busy. Usually this will be set to a value just before midnight for most sites. + +### Backup attachment files + +Attached files are stored by the AyaNova server separately from the AyaNova database in a special location in the file system. + +Checking this box will cause AyaNova to also back up the attached files in addition to the database backup. + +### Number of backups to keep + +The backup system will automatically remove old backups depending upon this setting. If it is set to 3 then the most recent three days worth of backups are kept. + +If you are following a policy of 10 backup rotation as suggested above then you would really only need to keep 1 or 2 current backups. + +### Active + +Backups won't run if set to inactive. This is a control to turn on or off the Backup job entirely. + +### Backup Files +This table contains the available backups on the server and provides the link to download them for off site storage. + +#### Backup names +The listed backups have particular names: + +The first segment of the name identifies if the backup is a manual one or an automated one. + +The second segment of the name identifies the data in the backup file: Database backups will have "db" in their name, attachment backups will have "at" in their name. + +The third segment is the date and time of the backup. + +Attachment backups are zip files and database backups are Postgress standard .backup files. + +### Menu option: Backup now +The Backup now menu option does exactly that: an on demand instant backup. This is useful for testing purposes or after large changes are made that you would like to ensure have been backed up. This will generate a manual backup that is not part of the normal automated backup process.