Qlik Replicate Disk Space Utilization

[guilherme-matte]

Hello team

Regarding Replicate Disk Space utilization.

Does it require a manual cleanup of the logs or any kind of archived file or it deletes older unused files automatically?

I ask because our disk space seems to in an ever-increasing trend. Even reducing log retention down to 5 days seems to do almost nothing. We have some around 13 tasks at the moment and the around 320GB for disk.

Getting the following issue:

[DATA_STRUCTURE ]E: SQLite general error. Code <13>, Message <database or disk is full>. [1000505] (at_sqlite.c:484)

I've asked for a breakdown of the logs since i do not have direct access to the server. Going to check the tswap files next as per the following thread: Qlik Replicate task fails with Database or disk is... - Qlik Community - 2053207

Cheers

[sureshkumar]

Hello @guilherme-matte 

You can select the option "Setting automatic roll over and cleanup"

n the Log File Management sub-tab, you can define when Replicate should roll over the server log files (repsrv and repcmd) and tasks log files (reptask_<task_name>) and when to delete old log files from the system.

Setting automatic roll over and cleanup #Setting automatic roll over and cleanup | Qlik Replicate He...

Regards,

Suresh

[Heinvandenheuvel · Accepted solution]

>> I ask because our disk space seems to in an ever-increasing trend. 

That's wonderful no? But perhaps you meant USAGE is ever increasing.

>>  i do not have direct access to the server. 

That's really annoying (stupid!), and serves very little purpose. You can probably more  easily to damage using Replicate than using access to the server. I urge you to work with management to get access to be able to support Replicate better. 

>> Even reducing log retention down to 5 days seems to do almost nothing. 

Are you referring to Log File management? "automatic cleanup" ? What are the other log management settings? If you don't roll-over then there is nothing to purge.

Log File Management
Define and manage roll over and cleanup policies for task logs and server logs.
Automatic Rollover
- Roll over the log if the log file is larger than (MB): 1  (1 - 1,024 MB)
- Roll over the log if the log file is older than (days):1  (1 - 100)
- Automatic Cleanup Delete log files that are older than (days): 45 (1 - 365)

Besides task ( and server) log, the other two potential diskspace hogs are per task SORTER  subdirectories where active CDC transactions are stored and the Log_stream target endpoints which each have their own 'Storage path:' option and its control:

Retention
Delete files after (hours): 48 (10,000)
Delete oldest files when the total size of all files exceeds (MB): 100000
(0 - 1,000,000,000)

From your limited problem and configuration description it's hard to give more detailed advice.

Try to get server access and/or have your server admin provide disk usage details with tools like TreeSizeFree for windows.

Good luck,

Hein.