From c0ed808c9466863917559cc7b4b26ff406507b19 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Sun, 12 Dec 2021 23:58:57 +0000 Subject: [PATCH] --- docs/8.0/ayanova/docs/ops-form-backup.md | 5 +++++ docs/8.0/ayanova/docs/ops-maintenance.md | 14 +++++++++----- 2 files changed, 14 insertions(+), 5 deletions(-) diff --git a/docs/8.0/ayanova/docs/ops-form-backup.md b/docs/8.0/ayanova/docs/ops-form-backup.md index 8b379c81..626137f6 100644 --- a/docs/8.0/ayanova/docs/ops-form-backup.md +++ b/docs/8.0/ayanova/docs/ops-form-backup.md @@ -24,6 +24,11 @@ A backup only stored on the same server (or even in the same building) as the li 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. +### Backup the configuration + +AyaNova does not backup it's boot [configuration](ops-config-environment-variables.md) so it is an important part of disaster recovery to keep a copy of the AyaNova server configuration if it has been modified from it's default in case AyaNova needs to be re-installed again. + + ### 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. diff --git a/docs/8.0/ayanova/docs/ops-maintenance.md b/docs/8.0/ayanova/docs/ops-maintenance.md index 3849d971..dff81435 100644 --- a/docs/8.0/ayanova/docs/ops-maintenance.md +++ b/docs/8.0/ayanova/docs/ops-maintenance.md @@ -7,24 +7,28 @@ AyaNova server should require very little ongoing maintenance, however there are Operations specific tasks performed within the AyaNova user interface required the following [roles](ay-biz-admin-roles.md): - `System operations` full access -- `System operations - restricted` read only access +- `System operations - restricted` read only access The restricted role is ideal for giving access to a non technical staff member to monitor the server operations but not make changes that could break anything. -## Backup -The single most important ongoing task is ensuring the backup process is working properly and monitoring it. A full backup consists of a backup of the Postgres AyaNova database **and** a backup of the attachment files that are stored in the file system. It is not sufficient to merely allow AyaNova to backup to it's own drive, it's critically important that backups be stored **off-site** physically far away from the AyaNova server to ensure business recovery is possible in the event of a theft, fire or other disaster. +## Backup + +The single most important ongoing task is ensuring the backup process is working properly and monitoring it. A full backup consists of a backup of the Postgres AyaNova database **and** a backup of the attachment files that are stored in the file system. It is not sufficient to merely allow AyaNova to backup to it's own drive, it's critically important that backups be stored **off-site** physically far away from the AyaNova server to ensure business recovery is possible in the event of a theft, fire or other disaster. See the [backup guide](ops-form-backup.md) for details. ## Metrics -The AyaNova client [server metrics](ops-metrics.md) form in the AyaNova user interface is an important resource to monitor the ongoing health of the AyaNova server and ensure that it has enough resources to perform adequately. Metrics should be reviewed on an ongoing and regular basis to view changes over time and ensure the server isn't running out of resources like memory or disk space (for example) that could slow down or even prevent the server from performing it's tasks. + +The AyaNova client [server metrics](ops-metrics.md) form in the AyaNova user interface is an important resource to monitor the ongoing health of the AyaNova server and ensure that it has enough resources to perform adequately. Metrics should be reviewed on an ongoing and regular basis to view changes over time and ensure the server isn't running out of resources like memory or disk space (for example) that could slow down or even prevent the server from performing it's tasks. ## Logs + The AyaNova client [server logs](ops-log.md) are available primarily for when things go wrong however it is good practice to examine them from time to time from an ongoing maintenance perspective to ensure nothing unusual is recurring such as logins from an unexpected location or a recurring warning message. ## Notifications + AyaNova's notification system provides [several operations specific notifications](ops-notification-system.md#operations-specific-notification-events) of interest to people responsible for the AyaNova servers operations. ## Jobs -The server has a server job system which runs various tasks throughout the day in the background and also runs some tasks on demand from users. It's a good idea to monitor the [job queue](ops-jobs.md) from time to time to look for anything unusual. +The server has a server job system which runs various tasks throughout the day in the background and also runs some tasks on demand from users. It's a good idea to monitor the [job queue](ops-jobs.md) from time to time to look for anything unusual.