meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
backups [2023/09/17 12:55] – [Database] wrongecho | backups [2025/01/26 10:03] (current) – [Database] indent old wrongecho | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Backups ====== | ====== Backups ====== | ||
- | As ITFlow will hold essential data about you and your clients, it is essential that you take (and test) regular backups, in addition to on-demand backups before performing updates. | + | As ITFlow will hold essential data about you and your clients, it is essential that you take (and test) regular |
- | {{backups.png? | + | Summary: |
- | Backups are likely best achieved by creating some sort of image/ | + | **1. You should regularly back up up the __entire Virtual machine__ running ITFlow.** |
+ | * The terminology for this may differ depending on your virtualization platform, but essentially you want an image/ | ||
+ | * This allows you to easily capture | ||
- | ITFlow is split into three main areas - all of which need backing up: | + | **2. You should retrieve and securely store your __master encryption key__** |
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | ITFlow is split into three main areas. If you are unable to backup the entire VM, you' | ||
* Files | * Files | ||
* Database | * Database | ||
* **Master Encryption key** | * **Master Encryption key** | ||
+ | |||
+ | {{backups.png? | ||
===== Files ===== | ===== Files ===== | ||
- | You should regularly take copies of the PHP files that power ITFlow. As updates are released, these files may reference new database fields. Your file backups | + | * You should regularly take copies of the PHP files that power ITFlow. |
- | + | * As updates are released, these files may reference new database fields. | |
- | Additionally, | + | |
===== Database ===== | ===== Database ===== | ||
* Your MariaDB database will contain all information entered into ITFlow. | * Your MariaDB database will contain all information entered into ITFlow. | ||
* Each database update will change the schema - restoring an older backup may fail or not work as intended as fields will have been added/ | * Each database update will change the schema - restoring an older backup may fail or not work as intended as fields will have been added/ | ||
- | * It is essential that you back up the databse | + | * It is essential that you back up the database |
- | * You can take one-off database backups at ''/ | + | * You can take one-off database backups at ''/ |
+ | * **NOTE:** Older installations may reference ''/ | ||
+ | * Recommended: | ||
===== Master Encryption key ===== | ===== Master Encryption key ===== | ||
- | ITFlow allows you to store login credentials for assets, websites, etc. Usernames and passwords entered are encrypted in the database using a //master encryption key//. This key is never stored in plaintext on the disk or in the database. You'll need this key if you ever need to recover encrypted passwords from the database. | + | * ITFlow allows you to store login credentials for assets, websites, etc. |
- | + | * Usernames and passwords entered are encrypted in the database using a //**master encryption key**//. This key is never stored in plaintext on the disk or in the database. You'll need this key if you ever need to recover encrypted passwords from the database. | |
- | You can retrieve your key at ''/ | + | |
+ | * **NOTE:** Older installations may reference ''/ |