Issue with indexing on shared folder

Hello,

I am currently working with a server where Copernic has been installed, and a shared folder named "indexfolder" has been configured.

The user who installed the Copernic client uploads files to be indexed into this shared folder.

At the moment, I have identified two possible configurations:

Option 1:
Map the folder locally on the server using the path:
D:\indexfolder
With this setup, as soon as files are uploaded to the share, they are indexed automatically, regardless of the index refresh timeout.

Option 2:
Map the folder using the network path:
\\srvname\indexfolder
In this case, the client is able to preview files and copy them locally. However, this requires setting a very low index refresh timeout, which has a significant impact on system resources.

Issue details:

• With Option 1:

  • The client can perform searches and retrieve results.

  • However, users cannot preview files.

  • Users are also unable to copy files locally.

• With Option 2:

  • File preview and local copy work correctly.

  • But indexing depends on frequent refresh cycles, increasing resource consumption.

Question:

How can I resolve the limitations observed in Option 1, while maintaining immediate indexing of newly uploaded files?

Thank you for your support.

Best regards

0 Votes