Default Backup Repository is created after finishing the Veeam Backup for Microsoft Office 365 setup; its location is C:\VeeamRepository folder on Veeam Backup for Microsoft Office 365 server. This default repository is associated with the default backup proxy that runs on the Veeam Backup for Microsoft Office 365 server. You can configure additional repositories associated with backup proxies, targeting them at local folders or shared folders. Direct Access Storage is a recommended storage type; others are SAN, SMB3 (with experimental support).
Please refer to the System Requirements section of this guide to plan for your Veeam Backup for Microsoft Office 365 infrastructure, including repositories.
Consider that it is not recommended to target Veeam Backup & Replication repositories as Veeam Backup for Microsoft Office 365 repositories.
During the initial backup job run Veeam creates the backup of mail datastore with the corresponding structure (including ADB database file, log and checkpoint files) in the appropriate subfolder in the target repository. The subfolders in repository are organized and named based on the last modification time of the mail items, so that a subfolder named <year_of_last_modification> stores mail items last modified in that year.
For example, an item that was last modified on 26 May 2015 will be backed up to the subfolder named 2015, all items last modified in 2016 – to the 2016 subfolder, and so on.
Repository.xml file stores configuration settings, including proxy and management server IDs.
Inside the repository subfolders you can see a specialized set of files:
- The repository.adb file – database file that stores the data of Exchange Organization mailboxes within the hierarchical structure (mailbox folders, subfolders, and items). This data is kept according to the retention policy you specify in the repository settings described later in this guide.
- Checkpoint and transaction logs – files required for log replay when bringing the database to specific state.
Repository database is accessed and managed using the Extensible Storage Engine (ESE).