Backup limitations and considerations
KTH uses Code42 to back up the computers in the client platform.
These are the limitations and considerations for the service.
Code42 is designed to protect data on laptops and desktops using any type of Internet connection, for users of KTH's client platforms.
KTH backup service is not a replacement for a long-term storage or data archive strategy. It is intended to provide some security when files are accidentally deleted, a hardware component breaks or a computer is lost.
Code42 is designed for end-user devices, and does not support backup of servers.
Most computers at Campus will benefit from KTH's fast network for good performance. Home users with slow internet upload speed will get reduced performance during backup.
For best results, especially during the first backup, use KTH's wired (Ethernet) network, and make sure your computer doesn't go to sleep.
Code42 does not play well on computers with more than 2TB data or multiple million files. The real performance of the backup depends on the amount of physical RAM, network speed, disk speed, processor speed, and similar factors.
In order to avoid expensive mobile bills, users of mobile data networks ("tethering") on their computer should configure Code42 not to make backup via the mobile phone. See Code42 CrashPlan Network Configuration Documentation for how to adjust client network settings.
Because backup archives are encrypted with an algorithm that uses a person's personal KTH credentials, the backup files can not be transferred to another user.
Special considerations should be taken when backing up certain types of open files, such as databases. See Code42 CrashPlan support documentation for more information.
Microsoft Outlook users should exclude .pst files, as these can provide slow backup.
Do not back up virtual machines (VMWare Fusion, Parallels) by backing up the file for the virtual machine. Instead, install Code42 in the virtual machine itself.