Client discovers an increase in transaction log size and is running out of space on the Log file drive.
Database log files are different to the application logs generated by ClickHome3. Regular back up of the transaction log eliminates growth. Each time the log is backed-up, it resets the internal use of the log, and the new logs just overwrite.
When ClickHome is deployed, the database is set to full recover mode, this allows data to be restored to a specific point in time to reduce data loss. However this can lead to large transaction logs if regular backups are not performed.
Please ensure above is done in a safe way.
Maintaining proper backup routines are paramount in case of data corruption. Please read below a few articles on best practices.
Some Suggested Links on Backup methodology are below:
MSDN Overarching Backup Article: https://msdn.microsoft.com/en-us/library/ms187048.aspx
SQL Authority Blog: http://blog.sqlauthority.com/2012/12/18/sql-server-select-the-most-optimal-backup-methods-for-server/