Backed up data storage characteristics

CodeTwo Backup keeps backed up data in a local resource known as storage. A storage consists of folders tree that reassembles mailboxes’ structure and versioning. Items backed up by the software are saved in binary files. That means that contrary to common text formats it is not possible to see the files’ contents using e.g. a Windows Notepad, but still possible to view them from within the CodeTwo Backup. Those data files are accompanied by .xml configuration files and .sdf files - an MS SQL Server Compact format databases that contain items metadata as well as contents indexes. Storage files are encrypted by default and additionally, the administrator can enable Storage password protection on the top of that to stop other, less privileged admins from viewing the backed up messages bodies in the software’s Administration Panel.

CodeTwo Backup allows creating multiple Storages and sharing them between multiple Jobs - a few different Jobs can back up data to the same Storage. Also, data from one Job can be restored by a different Job to a different server. Storages can be easily archived with Archive and PST Archive Jobs.

Backup - Using different Storages.
Fig. 1. Different jobs using multiple Storages to create backups and restore them from.

Storages limitations

The only substantial limitation of the Storages in CodeTwo Backup is their location. The software allows choosing only a local resource as a Storage location. It is not possible to point at a network drive when creating a new Storage. Such a possibility was prohibited on purpose to make sure that the fastest and the most reliable drive (i.e. a local one) is used as a Storage location. Network drives are unfortunately prone to connectivity failures often offering unsteady transfer speeds or even dropping connections. Keep in mind that you can always archive Storage data to an external resource.

See also

Managing backup Storage - this article describes how to manage Storages (create new Storage, edit the existing Storages, mount the existing Storage, remove / archive Storage, monitor Storages' status).

Was this information useful?