Retomando este problema le comento algunos puntos :
No estamos usando el link simbolico para copiar los archivos , se hace en forma directa al D:\CCC , el link simbólico solo se usa para lectura .
Respecto al uso, es a travez de un simple copy del SO
Instale la ultima version 3.18.1125 y el problema parece haberse incrementado.
Existe alguna forma desde la linea de comando para conectar y desconectar la unidad ..de forma de liberar periódicamente la memoria
Thank you for your patience. Based on your request, you can use NetDrive’s Command Line Interface (CLI) to periodically connect and disconnect the drive to help manage memory usage.
Here’s how you can use nd3cmd:
To connect the drive:
nd3cmd connect -n "Your Drive Name"
(Replace "Your Drive Name" with the actual drive name.)
To disconnect the drive:
nd3cmd disconnect -n "Your Drive Name"
This will disconnect the mapped drive.
To automate this process, you can create a batch script (.bat file) and schedule it to run at regular intervals using Windows Task Scheduler.
Additionally, we would like to gather more details about your memory usage issue:
How long does it take for memory usage to increase significantly?
How much data is being copied or transferred when the memory increases?
You can also find more details about the NetDrive CLI nd3cmd in the following guide: NetDrive CLI Manual
If the memory issue persists after trying these methods, please let us know so we can investigate further.
Buenas tardes , gracias por la información de NetDriveCli , con esto
podre mitigar los efectos , en breve les proporcionare mas información
sobre el uso , pero para que tengan una aproximación se copian
diariamente 200 archivos por un total de 80 Mbytes
We are glad to hear that the NetDrive CLI commands have been helpful in mitigating the issue.
When you send us additional information, please also include the log files so we can analyze them further. This will help us understand the root cause of the memory issue and provide a more precise solution.
To send the log files, please follow these steps:
Please set the log level to VERBOSE
Reproduce the problem.
Afterward, please follow the instructions in the following link to send us the debug log file:
Please be aware that the log file does not contain any login credentials.
We appreciate your cooperation and look forward to your update.
