Hello @rebajs 

Has the data size changed or is there any change in number of files? How much data and number of files are being backed up after being in scan for 19 hours as compared to the 3 jobs earlier? Is there a difference? 

Have you tried splitting the data into various subclients? 

Best,

Rajiv Singal

Hi @Rajiv 

Yes, it’s guaranteed that the data size changed and new files were added. The backup job did end up finishing after 28 hours, which a final application size of 10.21 TB. The previous jobs were much smaller, but we did have a 19.8 TB job finish earlier in the week after 15 hours.

We have our Linux FS split into two subclients, currently.

I’m not really sure why this particular incremental took so long (I have ideas) but I guess I’m no longer worried since it did eventually finish.

Thanks!

Hi @rebajs 

Altering the schedule should have no effect on the scan time.

Posting few questions below -

#1 - Are the subclients utilizing Filesystem-based backups (recursive / optimized scan) or intellisnap or block level technologies?

#2 - In the case of the incremental job in question being classified as a trueup job or a reconcile backup operation, it's expected for this particular job to take longer due to the additional operations carried out to ensure file synchronization between the index and client.

#3 - Could you please provide the FileScan logs from the client for both of the jobs in question (the one that took 3-7 hours and the one that took 15 hours)? This will allow us to conduct a detailed analysis and draw out a comparison.

Moreover, if you have a substantial number of folders, you can consider enabling the "Folder Level Multithreading" property at subclient level to further reduce the scan time.

Thanks,

Sparsh