2.4.x -> 2.5.x

• Settings exchange between older clients (<=2.4.x) and 2.5.x server might not be optimal
• Other than that client 2.3.x/2.4.x works, but update to client 2.5.x is recommended

2.3.x -> 2.4.x

• Full compatibility
• Client 2.1.x/2.2.x/2.3.x works, but update to client 2.4.x is recommended

2.2.x -> 2.3.x

• Full compatibility
• Client 2.1.x/2.2.x works, but update to client 2.3.x is recommended

2.1.x -> 2.2.x

• Full compatibility
• Client 2.1.x works, but update to client 2.2.x is recommended

2.0.x -> 2.1.x

• Full compatibility
• Linux/FreeBSD: Binary is only installed to PREFIX/bin and not PREFIX/sbin anymore. Please adjust any e.g. startup scripts you have. (If you followed the FreeNAS instructions e.g. in /etc/rc.local in the jail.)

1.4.x -> 2.0.x

• Before the upgrade please shut down your server and create a copy of C:\Program Files\UrBackupServer\urbackup (Windows) or /var/urbackup (Linux), so you can roll back to 1.4.x in case the upgrade process fails
• 2.0.x server with 1.4.x client full compatibility
• 2.0.x client with 1.4.x server works only in local network mode (not via internet mode)
• 2.0.x client does not support Windows XP or Windows Server 2003
• 1.x restore does not work with 2.0.x servers
• The database is completely rebuild during upgrade. This may take up to three times the current space. The upgrade will fail if there is not enough space.
• On first startup UrBackup server will have to build the new file entry index. This might take some time and needs two times the usual database space usage. On Linux you can significantly speed up the file index creation by allowing more dirty pages in RAM:

  
  echo 90 > /proc/sys/vm/dirty_ratio
  echo 70 > /proc/sys/vm/dirty_background_ratio
  echo 360000 > /proc/sys/vm/dirty_expire_centisecs
  echo 0 > /proc/sys/vm/dirty_writeback_centisecs
  mount -o remount,commit=3600 / (volume of database)
   

  Reset the changes to the defaults after the file index creation has finished (e.g. by reboot), because those non-default values can lead to data loss.

• File backups will have a lot of warnings and/or errors until you run a full file backup with the new version
• Linux notes: The wrapper scripts start_urbackup_server and start_urbackup_client have been removed. Please use the executable directly. The executable has been renamed to urbackupsrv (from urbackup_srv), the client to urbackupclientbackend (from urbackup_client) There is a new command line interface for the client urbackupclientctl. All the plugins are now statically linked into one executable. This simplifies the compilation, debugging and packaging on Linux. Run the UrBackup server on Linux with e.g. urbackupsrv run -v debug.

1.3.x -> 1.4

On non-btrfs file systems unchanged folders are symlinked per default now. This behaviour can be disabled in the advanced settings if it causes problems with other tools.

1.0 -> 1.1

Windows/Linux:

Per default UrBackup does not use files in the temporary folder as buffer anymore. Reenable this in the “Advanced” tab in settings if your main backup storage is slow and if you have enough temporary space available.

0.24 -> 0.25

Windows/Linux:

There are a lot of optimizations of UrBackup’s internal database. These require some indices to be rebuild. This may take a while. Please be patient.

0.23 -> 0.24

Windows:

Nothing.

Linux:

Debian based systems: The path in wich UrBackup’s data resides has changed. You have to manually copy over the files of the previous version in order to keep your data. The path changed from /var/lib/urbackup to /var/urbackup. The best way to keep your old settings and backups is to first uninstall the old package (apt-get remove urbackup_srv), move the files by executing

mv /var/lib/urbackup /var/urbackup

And then to install the new version.