Start by adding a File Share in the Inventory tab. If there is no shared folder added when you try to select Backup File Share you get the following error: The NFS/SMB Share needs to be added to Inventory – Files Shares.
To start the NAS Backup, there is some simple requirements that need to be in place. To create the files I used two small scripts (each one create 250 thousandths of files with 1Gb each): Files have different sizes (from 1Kb, 1Mb, 1oMb, 1Gb, and 10Gb) all create for this testing backup. In this test environment was created exactly 4.25 Milton files.
We can think the Changed File Tracking (CFT) like the VMware Changed Block Tracking (CBT) is a process that tracks all the file backup and files or object changes that are store in the Cache Repository that had to happen between backups. These are the components that are part of the Veeam NAS Backup. Since this is just a simple explanation of how the NAS Backup process works, I will just show two components of the process that start trough file proxies and also the Changed File Tracking that is stored in the Cache Repository. We can backup from the following sources:
Note: This first blog post about Veeam Backup NAS will be a bit longer than the other two since we also explain how to adding File Share and File Proxies.īefore we go through the backup process, let us go through a quick review of how the Veeam NAS Backup works. In this blog post, we will backup directly from a file share.
All data in the 4.25M files is around 7Tb. This is 4,25 million files, divided trough 10 folders (not many folders here). The plan by testing Veeam Backup NAS is to check how the Veeam works while we are back up a large number of files and folders. Now is time to share some of my tests in this How to backup 4M files with Veeam Backup NAS blog post that I did in my home lab.
This topic was on my list for a long time but had been a little bit busy and also in AWS training in the last two weeks, plus a lot of issues in work that needs a lot of troubleshooting hours.