You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-84Lines changed: 9 additions & 84 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,52 +1,14 @@
1
-
# Vault - Site migration #
1
+
# Vault - Site backup and migration #
2
2
3
3
Vault allows you to make a **full backup of the site**, push it to the cloud and then **restore** on any Moodle site.
4
4
5
-
See also https://lmsvault.io/
6
-
7
-
### Features:
8
-
- Vault will export and import **database** structure, schema modifications, tables content and sequences.
9
-
- Vault can restore not only into a different DB version but also into a **different DB type**
10
-
(i.e. from mysql to postgres or vice versa);
11
-
- Vault plugin does not need to have access to mysqldump or pgdump, the database will be exported using Moodle DML.
12
-
- Vault will export and import all **files**, regardless of the file system (local disk, S3, etc), the file
13
-
system on the restored site can be different from the backup site;
14
-
- Vault will export and import additional folders in the **dataroot**.
15
-
- After restore Vault will perform some necessary **post-restore** actions, for example, purge caches, kill all
16
-
sessions, optionally reset site identifier, optionally uninstall missing plugins etc.
17
-
- Vault does not back up or restore Moodle code or add-on plugins code.
18
-
- Vault does not back up or restore its own tables.
19
-
- Other plugins can be excluded during backup/restore (with some limitations).
20
-
- All data transferred to or from tool_vault is encrypted during transit using SSL/TLS.
21
-
- In some plans you may choose to set a passphrase during backup which will be used to encrypt data stored
22
-
at rest in the cloud.
23
-
Vault API never has access to your passphrase, it is only used to sign the
24
-
requests to Amazon S3.
25
-
26
-
### Requirements:
27
-
- The site where you restore must have **Moodle installed**, it can be a fresh installation;
28
-
- Plugin **tool_vault** must be installed on both sites - where you back up and where you restore;
29
-
- The site where you are restoring to must have the same or higher Moodle version than the backed up site;
30
-
- Supported databases - **postgres**, **mysql** and **mariadb**. Other database types are not yet supported;
31
-
- There are some restrictions on database modifications, see below;
32
-
- You need to have **enough space** in your temp folder on the backed up site and enough space to store
33
-
downloaded files on the site where you plan to restore.
34
-
35
-
## Site backup with Vault
36
-
37
-
- Login as site administrator and navigate to **Site administration > Server > Vault - Site migration**
38
-
- Before backup, Vault performs a number of pre-checks. They can also
39
-
be executed independently. The results are displayed on the 'Site backup' page.
40
-
- Backup can be performed only when all pre-checks are successful, which means you have enough disk space,
41
-
and do not have (or excluded) incompatible database schema modifications. The pre-checks will run
42
-
again in the beginning of the backup process.
43
-
- If you want to make changes to what needs to be backed up, you can do it in the "Settings" section.
44
-
- When everything is ready, open the **"Site backup"** section, register with the LMSVault cloud (or enter existing
45
-
API key) and schedule a backup.
46
-
- Backup will be performed during the next cron run. Every step is logged and you can monitor the process
47
-
on the backup page.
48
-
49
-
### Protecting your backup site from accidental restores
5
+
<palign="center"><big><big><strong>
6
+
Find more information about Vault features at <ahref="https://lmsvault.io">https://lmsvault.io</a> or <ahref="https://moodle.org/plugins/tool_vault">https://moodle.org/plugins/tool_vault</a>
7
+
</strong></big></big></p>
8
+
9
+
This README file contains information for the **server administrators**.
10
+
11
+
### Protecting your site from restores
50
12
51
13
The ability to restore is disabled by default when `tool_vault` is installed. Restores are not
52
14
possible if you did not register an account, did not enter an API key, or your API key does not allow restores.
- Note that not all **field modifications** can be detected, for example, changing the length or precision
103
-
of the int/double/float fields.
104
-
- Some database modifications are not supported in the Moodle DML, for example, indexes
105
-
on text fields, varchar fields with length over 1333. If you have such modifications, the pre-check
106
-
will fail and Vault **will not be able to perform backup**.
107
-
- In the "Settings" section you can specify that some **modifications should be excluded**. You can re-run
108
-
the pre-check after you modified the settings to see if it passes.
33
+
- When you exclude plugins from backup or choose to preserve plugin data during restore, the settings from these plugins will not be backed up or restored.
Copy file name to clipboardExpand all lines: lang/en/tool_vault.php
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -175,7 +175,7 @@
175
175
$string['lastupdated'] = 'Last updated';
176
176
$string['loginexplanation'] = 'Create an account on {$a} to be able to backup or restore the site. With the <b>free account</b> you will be able to backup and restore small sites and store them up to 7 days in the cloud.';
177
177
$string['manageremoteaccount'] = 'Manage your account';
178
-
$string['messageprovider:statusupdate'] = 'Status update for Vault - Site migration';
178
+
$string['messageprovider:statusupdate'] = 'Status update for Vault - Site backup and migration';
179
179
$string['moodleversion_backupinfo'] = 'Backup made in version {$a->version} (Moodle {$a->branch})';
180
180
$string['moodleversion_fail'] = 'Site version number has to be greater than or equal to the version in the backup. This backup is {$a->version} and this site is {$a->siteversion}';
181
181
$string['moodleversion_fail_cannotupgrade'] = 'Restore is blocked because Moodle cannot upgrade from {$a->backuprelease} to {$a->currentrelease}. See the <a href="{$a->url}">environment page</a> for upgrade requirements. Vault is able to upgrade from this version if you choose "Automatically upgrade Moodle after restore" in the <a href="{$a->settingsurl}">settings</a>.';
$string['settings_backupexcludetables_desc'] = 'Vault will back up all tables that start with the prefix \'{$a->prefix}\' even if they are not listed in xmldb schemas of the core or installed plugins.<br>Here you can list extra tables that should not be backed up. Use an asterisk (\'*\') to exclude all extra tables.<br>You must include the table prefix when excluding tables.';
241
241
$string['settings_clionly'] = 'Allow to perform site backup and restore from CLI only';
242
-
$string['settings_clionly_desc'] = 'Checking this will hide the "Vault - Site migration" from the site administration and prevent access to backup and restore. ';
242
+
$string['settings_clionly_desc'] = 'Checking this will hide the "Vault - Site backup and migration" from the site administration and prevent access to backup and restore. ';
243
243
$string['settings_desc'] = "Vault plugin settings where you can configure what to exclude during backup or preserve during restore.";
244
244
$string['settings_forcedebug'] = 'Force debugging during backup and restore';
245
245
$string['settings_forcedebug_desc'] = 'Regardless of the site configuration, developer debugging and debug display will be enabled during backup and restore. This will affect the tool vault logs only, and will not change the values for these settings that are included in the backup.';
246
-
$string['settings_header'] = 'Vault - Site migration settings';
246
+
$string['settings_header'] = 'Vault - Site backup and migration settings';
0 commit comments