1/27/2024 0 Comments Veeam backup jobs best practices![]() ![]() This doesn't mean that you should have one VM per job, it depends on several factors. Yes, there are some benefits for several jobs (hence several VBK files) vs one single job. ![]() > Is there any benefit to having one VM per job vs multiple VM's per job? However I can respond to some of the questions: Run up to 14 backup jobs simultaneously on the Veeam proxy/repository serverįirst - I have no experience with 2012 dedup yet. Incremental backup with a Full on Friday Direct SAN connectivity ESXi LUNs (around 60 LUNs and set to read-only) Remember to account for a landing zone to be at least the same size of your total FULL backups and leave at least 1 TB for the dedup process. This allows time to complete the dedup process for all the full backups and still have enough time to catch up on deduping the incremental backups before the next set of full backup hits on the LUN. I also take into account that the total size of all the full backup jobs when added together per LUN is around 4 TB. I've opted to use Powershell to create and maintain my jobs to keep the VBK files around 400 GB and the VIB files around 50 GB. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |