From: DecaTec Date: Mon, 8 Oct 2018 08:59:58 +0000 (+0000) Subject: Updated links X-Git-Tag: v1.0.0~18 X-Git-Url: https://git.p6c8.net/nextcloud-backup-restore.git/commitdiff_plain/d6e40c61a35ea86523348c771f19867d433373cb?ds=sidebyside;hp=c255038f93ab4dae3a2733be5449d1dd7a5d3321 Updated links --- diff --git a/README.md b/README.md index 36f0394..c786062 100644 --- a/README.md +++ b/README.md @@ -16,10 +16,10 @@ The scripts take care of these three items to backup automatically. **Important:** - After cloning or downloading the repository, you'll have to edit the scripts so that they represent your current Nextcloud installation (directories, users, etc.). All values which need to be customized are marked with *TODO* in the script's comments. -- The scripts assume that Nextcloud's data directory is *not* a subdirectory of the Nextcloud installation (file directory). The general recommendation is that the data directory should not be located somewhere in the web folder of your webserver (usually */var/www/*), but in a different folder (e.g. */var/nextcloud_data*). For more information, see [here](https://docs.nextcloud.com/server/13/admin_manual/installation/installation_wizard.html#data-directory-location-label). +- The scripts assume that Nextcloud's data directory is *not* a subdirectory of the Nextcloud installation (file directory). The general recommendation is that the data directory should not be located somewhere in the web folder of your webserver (usually */var/www/*), but in a different folder (e.g. */var/nextcloud_data*). For more information, see [here](https://docs.nextcloud.com/server/14/admin_manual/installation/installation_wizard.html#data-directory-location-label). - However, if your data directory *is* located under the Nextcloud file directory, you'll have to change the scripts so that the data directory is not part of the backup/restore (otherwise, it would be copied twice). - The scripts only backup the Nextcloud data directory. If you have any external storage mounted in Nextcloud, these directories have to be handled separately. -- If you have enabled 4 byte support (see [Nextcloud Administration Manual](https://docs.nextcloud.com/server/13/admin_manual/configuration_database/mysql_4byte_support.html)) while backup, you have to enable 4 byte support on the target system *before* restoring the backup. +- If you have enabled 4 byte support (see [Nextcloud Administration Manual](https://docs.nextcloud.com/server/14/admin_manual/configuration_database/mysql_4byte_support.html)) while backup, you have to enable 4 byte support on the target system *before* restoring the backup. - If you do not want to save the database password in the scripts, remove the variable *dbPassword* and call *mysql* with the *-p* parameter (without password). When calling the scripts manually, you'll be asked for the database password. ## Backup @@ -29,4 +29,4 @@ This will create a directory with the current time stamp in your main backup dir ## Restore -For restore, just call *NextcloudRestore.sh*. This script expects one parameter which is the name of the backup to be restored. In our example, this would be *20170910_132703* (the time stamp of the backup created before). The full command for a restore would be *./NextcloudRestore.sh 20170910_132703*. \ No newline at end of file +For restore, just call *NextcloudRestore.sh*. This script expects one parameter which is the name of the backup to be restored. In our example, this would be *20170910_132703* (the time stamp of the backup created before). The full command for a restore would be *./NextcloudRestore.sh 20170910_132703*.