Configuring Log and Cache Repositories
To protect Microsoft Entra ID tenant data and logs, you require the following repositories:
- Cache repository that stores temporary cache files for log processing.
- Primary log backup repository.
- [Optional] Secondary log backup repository that stores copies of log backups.
By default, the backup server can perform the role of a cache and primary log backup repositories.
You can also configure other types of repositories to keep data in another location. The following types of repositories are supported for all repositories (the cache, primary and secondary repositories):
- Direct attached storage: Microsoft Windows and Linux virtual and physical machines. For the cache repository only 64-bit versions are supported.
- Network attached storage: SMB (CIFS) shares and NFS shares.
The following types of repositories are supported only for the primary and secondary log backup repositories:
- Direct attached storage: Hardened linux server
- Deduplicating storage appliance: ExaGrid, Quantum DXi, Dell Data Domain and others
- Object storage repository: Amazon S3, S3 compatible, Google Cloud and others
- Scale-out backup repository (SOBR)
Note |
You cannot use Veeam Cloud Connect repository as cache repository, primary or secondary backup repositories. To learn more about this repository, see the Cloud Repository section in the Veeam Cloud Connect Guide. |