This commit is contained in:
@@ -58,13 +58,11 @@ This table contains the available backups on the server and provides the link to
|
||||
#### 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 first 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. If the backup was triggered manually in the user interface it will be prepended with "manual" in the name.
|
||||
|
||||
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 second segment is the date and time of the backup.
|
||||
|
||||
The third segment is the date and time of the backup.
|
||||
|
||||
Attachment backups are zip files and database backups are Postgress standard .backup files.
|
||||
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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
# RESTORE BACKUP Placeholder
|
||||
|
||||
[under construction]
|
||||
|
||||
todo: how to restore, where the key is etc; this page is linked to from the client app when there is no license
|
||||
|
||||
Reference in New Issue
Block a user