If configuration files are changed the old version will usually be copied to a backup file (*.dpkg-old). Nevertheless it is a good idea to make a system backup yourself before upgrading.
Description how to upgrade
- Device names stay the same (eth0, ...). Debian 9 only uses a new naming scheme for new installations.
- So far I had no problems to connect bacula-fd v7.4.4 to a bacula server v7.0.5
- Major upgrade from version 2. The configuration will not be automatically merged. You have to do this manually.
- Basic configuration stays pretty much the same. Some configuration variables have been renamed or moved to a different position.
- New configuration directories:
- Basic configuration stays pretty much the same.
- Major upgrade from version 14.07
- Had no problems with a basic configuration and a couple of virtual mailbox domains.
- Almost no changes from previous version 2.10.1-2
- No need to change anything if you have a default installation
- New user/group "courier". File permissions need to be adjusted:
- Some configuration changes (pid file, certificates location, etc.)
- No longer subject to DRDoS Amplification Attack
- Option "limited" added (to default restriction in configuration file)
- Source restriction added (to configuration file)
- Major upgrade from version 6.7
- No longer subject to ssh client roaming problem (s. Qualys Security Advisory)
- New "AddKeysToAgent" client parameter (a private key that is used during authentication will be added to ssh-agent)
- Default for "PermitRootLogin" changed from "yes" to "prohibit-password".
- Default for "UsePrivilegeSeparation" changed from "yes" to "sandbox"
- Default for "UseDNS" changed from "yes" to "no"
- New option to require 2 different public keys for authentication; may be used for two-man rule / four-eyes principle (s. "AuthenticationMethods=publickey,publickey")