I’m using log shipping for a database with filestream. The filestream file size on the secondary doesn’t correlate with the original file on the primary server.

The filestream on the secondary server only grows larger, while the filestream on the primary stays small in size.

I tried sp_filestream_force_garbage_collection but it returns an error:

Access to the FILESTREAM tombstone table for the database ‘***‘
cannot be performed at the moment because it conflicts with another
activity, such as background GC operation, backup operation, DBCC
CHECK operation or on-going snapshot creation

no backup operations performed.
no dbcc operations performed.

The database is in standby when not performing restores – for BI purposes.

I tried sp_filestream_force_garbage_collection. I also tried restarting the servers and setting up the log shipping from scratch – the problem persists.