Skip to main content
commvault.com commvault.com

I’ve got a TrueNAS server with a bunch of CIFS shares.  I setup a Windows File System client to do the backups of the CIFS shares, using our CommCell master to do the backups.  Unfortunately, no matter what, it backups up all the same files for both Full and Incremental backups, which slows things down and screws up temp disk space usage.  

 

So what’s the process to figure out why this is happening?  This is around 1.7Tb of data and 2+ million files, so it really slows things down.

 

CommVault 11.36.5?  something, pretty new.  The TrueNAS is Enterprise 13.0-U6.2 release.  The Windows backup server is running Windows Server 2016 (I know, I know...) 

 

The TrueNAS runs Samba internally to do CIFS shares.  Not sure where the disconnect is here.  Has anyone else got this working properly?  

Hey JFS,

CIFs typically doesn’t concern itself much with the platform hosting it. From Commvault’s perspective it’s a network asset to protect but it cannot inherently track changes on the file system, instead it uses markers to flag mtime and ctime of files and can use access time and archive bit checking too.

To determine why this is occurring I’d be looking at the logs for the ifind process (FileScan.log) on an incremental job. Here it should list how many files qualified for backup, if any errors occurred with determining mtime/ctime, if there’s a reason it reset to a full scan etc.

If you cannot gather anything from the logs I would suggest raising a support incident to have our support team investigate further as this is not normal behaviour.

Hopefully this helps.

Reply


Terms & ConditionsCookie settings