- fixed setup.sh: which has parameter
useCompression
for compressed backups statically set - fixed setup.sh: which now asks if parameter
includeNextcloudDataDir
should be included in Backup - fixed Nextcloud Backup.sh which now exludes data dir if not wanted in backup
- Use rsync as default for backups
- Disabled compressed backups to enable incremental sync backups
- Remove tar commands from code
- Use RSync to be prepared for incremental backups
- New configuration option
includeNextcloudDataDir
(default:true
): This can be set tofalse
in order to exclude Nextcloud's data directory from the backups (not recommended). - Added hint to configuration file that
mariadb
andmysql
are equivalent for the variabledatabaseSystem
. - Some configuration options in
NextcloudBackupRestore.conf
are optional, e.g. are set to default values bysetup.sh
. These are potentially dangerous options which should usually not be changed (e.g.includeNextcloudDataDir
).
- Use parameter
--default-character-set=utf8mb4
when dumping the database on MySQL/MariaDB and the 4-byte support is enabled in theconfig.php
.
- When calling
NextcloudRestore.sh
without parameters, a list of available backups to restore is shown instead of error message.
- Variable
includeUpdaterBackups
inNextcloudBackupRestore.conf.sample
- Bugfix: The backup directory to use was not recognized when given by parameter
- Bugfix: When calling the backup script by cron, the configuration file
NextcloudBackupRestore.conf
could not be found
- Bugfix: Option to include/ignore backups from the Nextcloud updater was not set correctly during setup
- Backup/restore scripts now use a central configuration file (
NextcloudBackupRestore.conf
) - This configuration file includes all the settings which should be configured to match the specific Nextcloud instance. This simplifies the initial configuration of the backup/restore scripts
- The setup (
setup.sh
) creates this central configuration file (NextcloudBackupRestore.conf
) rather than modifying the backup/restore scripts - Bugfix: setup.sh won't set wrong database password if password contains slashes and/or backslashes
- While restore, only the contents of Nextcloud's data directory gets removed, rather than the whole directory (useful when the data directory is stored directly in a mounted drive)
- Update fingerprint after disabling maintenance mode
- Bugfix: Compression command on restore
- Hint for installing pigz when using compression
- Bugfix: Set variable
backupMainDir
correctly
- Bugfix: Unbound variable when no parameters are supplied
- The scripts now exit when any command fails.
- Defined the command for compression in the "TODO section" of the script for easier customization.
- Added section for setup in readme.
- Updated links.
- Document requirement pigz when using compression.
- Formatting.
- Bugfix: Fixed the double trailing slash for paths containing the variable
backupdir
.
- Better handling of external data directory: Backup/restore of external data direcrory is done automatically if the variable
nextcloudLocalExternalDataDir
is set.
- Added timestamps for every step.
- Use pigz for compression.
- Optimized cleaning up of old backups.
- Added a variable useCompression to use compression (.tar.gz) for file and data directory (enabled by default, this was also the default behavior before this option was implemented).
- You can disable compression of these directories (.tar) if you use some other (archiving) backup mechanism which utilizes the Nextcloud backup and restore scripts (e.g. Borg Backup, see here: https://codeberg.org/DecaTec/Linux-Server-Backup)
- Added script (
setup.sh
) for an (more or less) automated setup of the backup and restore scripts (utilizing OCC in order to gather information about Nextcloud instance).
- When a backup is cancelled, the webserver is restartet automatically.
- New variable ignoreUpdaterBackups: When set to true, the backups of Nextcloud's updater are not included in the backups (default: false).
- Versioning of Nextcloud-Backup-Restore.
- The database system (MySQL/MariaDB or PostgreSQL) is configured in the variable area of the scripts, so it's not necessary to comment/uncomment the specific database commands.
- Special characters for the database password can be used now.
- Single quotes for variables.
- The commands for restoring the database are checked at the beginning of the script. Is the specific database system is not installed, the restore is cancelled.
- The default main backup directory now is the same as in the backup script.