![]() Backup from storage snapshot is optional. These points make me question the scalability of Veeam in this scenario and wondering wether I am not building a big house of cards here. Full Name: Hannes Kasparick Location: Austria Re: Immutable Backup best practice and settings to follow by HannesK Fri 6:36 am Hello, backup jobs and backup copy jobs work with Hardened Repository. ![]() 32983.html suggests that when adding capacity we will always face calculation of digests and fingerprinting (which will get worser and worser as the virtual machine grows.), I guess this is true for replication as well as for backup jobs and copy jobs first concerning the defrag of the backup files, but I guess having a Win2016 ReFS repository will help alot here (with synthetics and GFS)īut this thread here vmware-vsphere-f24/large-fileserver-rep. ![]() I plan on expanding this virtual machine capacity little by little to meet users usage (~+30% a year) As we are soon replacing our NetApp filers we will be transitionning our file shares (currently at ~8 TB) from native NetApp CIFS (with additionnal SnapMirror offsite) to a Windows Server 2016 VM that will be backed up by Veeam.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |