![]() QNAP have now introduced the WORM functionality on its shares, which can be used with SMB or NFS. The only issue with SMB is that Veeam advises against it as it can lead to data loss or backup file corruption? is this still the case with the latest version of SMB protocol? This way, the contents of the share will not be compromised if the backup server OS is infected with ransomware. SMB has built-in share-level authentication, so i can input the share password directly in Veeam to protect it. ![]() I can limit a particular IP address to connect to the backup share, but the NFS share can be compromised quite easily when the ransomware attacks the backup server. I tried using the NFS file system, which Veeam recommends when using a NAS as backup Repository but the issue is NFS authentication is not as secure. I don't wish to use the block file system as that would make it extremely easy for the ransomware to encrypt the backup files when the backup server gets infected. ![]() I can switch my backup's to Forward incremental with Synthetic Full or Active Full if that makes it possible to configure VEEAM with QNAP WORM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |