Skip to main content

How the backup works

KTH uses Code42 to back up the computers in the client platform.
This is how Code42 works.

Continuous backup

Code42 provides "continuous backup" that differs from other, more traditional backup applications. Instead of launching a resource-intensive backup session a few times a day, it's much easier and more discreet.

Code42 uses the computer's own notification system to alert you to changes in data on the drive. It is listening to your operating system to see when files have been added, deleted or changed. It queues the current files to then compress and encrypt data before sending it over the network. This is done by default once a hour.

To ensure that no files are missed, the entire disk is scanned once a day to capture any changes missed. This usually happens around noon every day. If the computer is turned off, the scan will occur later in the day.

Initial backup, subsequent protection

Once the first backup is complete, only modified bits of a given file will be sent on later backup. In addition, Code42 offers, per device, deduplication (= multiple identical files only saves one of them and other similar files in the backup archive refers to this) provides backups more efficiently.

The integrity of your backups is periodically checked by the software. Any errors in the backup archive are identified and the original files are backed up to ensure protection.

To restore data, the secure web interface is used for a few files, and the dedicated program for larger readings. Refer to the Code42 documentation to learn more about file reinstallation.

Resource efficient

Code42 uses minimal processor and network resources when using your computer. Users can customize the network usage for the backup to prevent home network interference as well.

Did you find this page useful?
Thank you for helping us!
Belongs to: KTH Intranet
Last changed: Sep 25, 2018