This commit is contained in:
@@ -42,6 +42,24 @@ The attachments backup file starts with "at-" in the file name followed by a tim
|
||||
|
||||
The database backup file starts with "db-" in the file name followed by a timstamp and with the extension ".backup". AyaNova uses the [pg_dump](https://www.postgresql.org/docs/current/app-pgdump.html) PostgreSQL utility to backup the database and uses the `-Fc` command line switch to create a "custom" format backup which is compressed.
|
||||
|
||||
### Do I still need to backup even if I use AyaNova as a subscription service?
|
||||
|
||||
Yes! Accidents can happen. You must set up a backup routine and regularly download a copy of your backup for safe storage in your own custody.
|
||||
|
||||
We strongly recommend you read and follow the best practices outlined here to ensure the safety of your data.
|
||||
|
||||
We do not maintain a separate copy of your backup; it is your responsibility to ensure you have a recent copy of your backup available to provide to us should it ever be required to be restored.
|
||||
|
||||
## How to download your backup
|
||||
|
||||
Your backups are displayed on this backup form in a table and if you have sufficient Roles assigned you will see a download icon beside each backup file listed enabling you to download the backup.
|
||||
|
||||
Be sure to backup [both](#backup-format) the database and attachment backup files.
|
||||
|
||||
Note that you may not see an attachment backup file if there are no attachments in AyaNova but you will always see a database backup file unless there is a problem.
|
||||
|
||||
We recommend downloading and keeping [multiple copies](#10-backup-rotation) of your backup in a safe location.
|
||||
|
||||
## Failed backup
|
||||
|
||||
The most important step to detecting failed backups is to ensure several users are subscribed to the **Backup status notification** [subscription](home-notify-subscriptions.md). This is the best way to detect a failed backup in a timely manner and several people should be subscribed to this event to ensure it doesn't get missed.
|
||||
@@ -84,6 +102,8 @@ There should always be a non I.T. User assigned with `Operations - restricted` r
|
||||
|
||||
### Backup the configuration
|
||||
|
||||
(Not applicable to Subscription AyaNova service customers)
|
||||
|
||||
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
|
||||
|
||||
@@ -18,6 +18,16 @@ Yes! AyaNova database and attachment backups are compatible between Linux and Wi
|
||||
|
||||
## Restore steps
|
||||
|
||||
### AyaNova subscription server
|
||||
|
||||
The instructions below are for self-hosted AyaNova "Perpetual" licensed installations.
|
||||
|
||||
If you are using our AyaNova subscription service and need to restore a backup you have previously downloaded our support department will take care of that for you.
|
||||
|
||||
Reminder that we do not keep separate copies of your backup, we can only restore a backup if you are able to provide it to us or there is a copy available [on your server](ops-form-backup.md#do-i-still-need-to-backup-even-if-i-use-ayanova-as-a-subscription-service)
|
||||
|
||||
[Contact AyaNova support](https://contact.ayanova.com/contact) and we will initiate the restore process for you using a copy of the backup on your server or a if you have a backup set downloaded you would like to restore, support will provide instructions on how to upload your backup to us so we can restore it to your server.
|
||||
|
||||
### New AyaNova server installation
|
||||
|
||||
If this is a restoration to a new computer that doesn't have AyaNova installed and confirmed running; then the first step is to [install AyaNova](ops-install.md)
|
||||
|
||||
Reference in New Issue
Block a user