Start with configuring three concurrent tasks per CPU core and adjust based on load of the server, storage and network.ĭependent on the used storage too many write threads to a storage might be counter productive. You can consume both layers by setting up a backup copy job from the first to the second repository, or leverage Scale-out Backup Repository. A repository with more capacity, but using a cheaper and slower storage, storing long-term retention points.A high-performance repository hosting several recent retention points for instant restores and other quick operations. In such scenarios, you may configure two backup repositories: Organization policies may require different storage types for backups with different retention. It also needs to be scalable, allowing the backup to grow as needed. We should consider following while building the backup repository:Īs a basic guideline, a repository should be highly resilient, since it is hosting customer data. This site uses Just the Docs, a documentation theme for Jekyll.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |