We are planning to implement a backup solution in our environment using Windows Server Backup. Testing in our Test environment has been successful, but implementing a small-scale one-time test in our Production environment is not going as I expected.
Namely, as a test on our Production file server, I am using Windows Server Backup to back up a single folder with 6 files and is 512 KB in size (total). I used the Backup Once Wizard to back up this folder to another drive as a test. It has been running for almost 2 hours now on the "Scanning file system..." step. The drive that contains the small folder with the 6 files I am attempting to back up has 3.08 TB total of data (several thousands of files and folders).
Why is the "Scanning file system" step taking so long? Is it enumerating all files and folders in the drive, not just for the folder I want to back up?
When this "Scanning file system" step ends, will it take as long each subsequent time we try to do a "Backup Once" type of backup (using the GUI or using a Powershell cmdlet)? This was only a test, so I'm not going to set up any incremental backup based off of this small folder test.
Ultimately we are looking to do a weekly or monthly backup of a folder that contains about 1.5 TB in data total. If we were to kick this task off for the first time, generally how long can I expect it to take? Longer than 24 hours? The length of time it takes may dictate whether we end up using this tool for our backup solution or switch to something else.