Administration Manual for UrBackup Server 2.2.x Martin Raiber February 19, 2018 Contents 1 Introduction 4 2 Installation 4 2.1 Server installation . 4 2.1.1 Server installation on Windows . 4 2.1.2 Server installation on Ubuntu . 5 2.1.3 Server installation on Debian . 5 2.1.4 Server installation on other GNU/Linux distributions or FreeBSD . 5 2.1.5 GNU/Linux server installation hints . 6 2.1.6 Operating system independent server installation steps . 6 2.2 Client installation . 6 2.2.1 Windows/Mac OS X client installation . 6 2.2.2 Automatic rollout to multiple Windows computers . 7 2.2.3 Client installation on Linux . 7 3 Architecture 8 3.1 Server architecture . 8 3.2 Client architecture . 8 4 Security 9 4.1 Server webinterface rights management . 9 4.2 Make webinterface accessible via SSL . 9 4.2.1 Apache conguration . 9 4.2.2 Lighttp conguration . 10 4.3 Client security . 10 4.4 Transfer security . 11 4.5 Internet mode security . 11 5 Client discovery in local area networks 11 6 Backup process 12 6.1 File backup . 12 6.2 Image backup . 13 6.3 Collision probabilities . 13 6.3.1 File backup collision probability . 13 6.3.2 Image backup collision probability . 13 6.4 Pre and post backup scripts on client and server . 14 6.4.1 Client pre and post backup scripts . 14 6.4.2 Server post backup scripts . 14 1 7 Internet clients 15 7.1 Automatically push server conguration to clients . 15 7.2 Download a precongured client installer . 15 7.3 Manually add and congure clients . 15 7.4 File transfer over Internet . 15 8 Server settings 16 8.1 Global Server Settings . 16 8.1.1 Backup storage path . 16 8.1.2 Server URL . 16 8.1.3 Do not do image backups . 16 8.1.4 Do not do le backups . 16 8.1.5 Automatically shut down server . 16 8.1.6 Download client from update server . 16 8.1.7 Show when a new server version is available . 17 8.1.8 Autoupdate clients . 17 8.1.9 Max number of simultaneous backups . 17 8.1.10 Max number of recently active clients . 17 8.1.11 Cleanup time window . 17 8.1.12 Automatically backup UrBackup database . 17 8.1.13 Total max backup speed for local network . 17 8.1.14 Global soft le system quota . 18 8.2 Mail settings . 18 8.2.1 Mail server settings . 18 8.2.2 Congure reports . 19 8.3 Client specic settings . 19 8.3.1 Backup window . 21 8.3.2 Advanced backup interval . 21 8.3.3 Excluded les . 22 8.3.4 Default directories to backup . 22 8.3.5 Virtual sub client names . 23 8.4 Internet settings . 23 8.4.1 Data usage limit estimation . 24 8.5 Advanced settings . 24 8.5.1 Enabling temporary le buers . 24 8.5.2 Transfer modes . 24 8.5.3 Incremental image backup styles . 25 8.5.4 Full image backup styles . 25 8.5.5 Database cache size during batch processing . 25 8.6 Use symlinks during incremental le backups . 25 8.7 Debugging: End-to-end verication of all le backups . 25 8.8 Debugging: Verify le backups using client side hashes . 26 8.9 Periodically readd le entries of internet clients to database . 26 8.10 Create symbolically linked views for each user on the clients after le backups . 26 8.11 Maximum number of simultaneous jobs per client . 26 8.12 Volumes to snapshot in groups during image backups . 26 8.13 Volumes to snapshot in groups during le backups . 26 8.14 Windows components backup conguration . 26 9 Restoring backups 26 9.1 Restoring image backups . 27 9.2 Restoring le backups . 27 2 10 Miscellaneous 28 10.1 Manually update UrBackup clients . 28 10.2 Logging . 28 10.3 Used network ports . 28 10.4 Mounting (compressed) VHD les on GNU/Linux . 28 10.5 Mounting VHDs as a volume on Windows . 29 10.6 Decompress VHD les . 29 10.7 Assemble multiple volume VHD images into one disk VHD image . 29 10.8 Migrate non-btrfs backup storage . 29 11 Storage 30 11.1 Nightly backup deletion . 30 11.2 Emergency cleanup . 30 11.3 Cleanup for servers with le backups with lots of les . 30 11.4 Cleaning the storage folder of les not known by UrBackup . 31 11.5 Archiving . 31 11.5.1 Archival window . 31 11.6 Suitable le systems . 32 11.6.1 Ext4/XFS . 32 11.6.2 NTFS . 32 11.6.3 btrfs . 32 11.6.4 ZFS . 32 11.7 Storage setup proposals . 33 11.7.1 ZFS . 33 11.7.2 Btrfs . 34 3 1 Introduction UrBackup is a client/server backup system. This means there is a server which backs up clients. Accordingly UrBackup is divided into a client and server software. The client software currently runs on Windows, Linux and Mac OS X with only the Windows client being able to perform image backups. The server part of UrBackup runs on Windows, GNU/Linux and FreeBSD. A lot of eort in UrBackup was made to make setup as easy as possible. If you are okay with the default settings (see section 8) the only thing you need to dene on the server side is where backups should be stored. On the clients you only need to say which directories should be backed up. If server and clients are in the same subnet the server will automatically discover the clients and then start backing them up (for details see section 5). This also makes building a decentralized backup strategy very easy, as e.g. one backup server per subnet is responsible for backing up all clients in this subnet. If a computer is moved from one subnet to another this new client is discovered and the server in the new subnet automatically takes over backing it up. If you want to implement something like this, you should also read the section on security (see 4) for details on when a client accepts a server. Installation instructions are in section 2. The interested administrator should also read up on the general UrBackup architecture (section 3), how the backups are stored.