Add log rotation / size limit for cluster resource console.log (LogToFile), or disable it by default

The IBM Storage Protect Windows Failover Cluster resource (custom resource type registered by the IBM Storage Protect installer during cluster configuration) includes private properties LogToFile and ConsoleLogFile. When LogToFile=1 (the default value set automatically by the installer during cluster setup), the resource continuously redirects server console output to a flat file at the path specified in ConsoleLogFile, for as long as the resource remains online.

This file has no built-in size limit, rotation, or retention mechanism. It grows indefinitely for the entire uptime of the clustered server instance, in our environment it reached approximately 5 GB after a period of normal production operation, with no cap in sight. Left unmanaged, this creates a real risk of filling the volume hosting the instance directory, which could impact database logging, storage pool operations, or server availability entirely.

Why this matters:

• The setting is enabled by default during cluster configuration, without any prompt, documentation warning, or opt-in step, customers are not made aware this file has unbounded growth potential until they notice disk usage climbing.
• Because the file handle is held open continuously by the cluster resource process, standard external log-rotation approaches (rename-and-reopen, copytruncate-equivalents) are not feasible on Windows without taking the resource offline, meaning customers must build custom scheduled automation that stops the resource, archives the file, and restarts it, purely to manage a logging mechanism they did not explicitly choose to enable.
• We confirmed with IBM Support (case reference: TS022681333) that this is not currently a documented APAR or known issue, and that disabling the setting (LogToFile=0) is the only current mitigation, at the cost of losing console-level visibility during startup/failover events, which appears to be the original intent of this feature.

Suggested resolution:

Implement built-in size-based or age-based rotation for console.log within the cluster resource DLL itself

Business impact:

Risk of unplanned disk-full conditions affecting a production backup infrastructure component, and the operational burden of building/maintaining custom workarounds (including planned resource outages) to manage a file that was enabled without our explicit consent, for a supported out-of-the-box cluster configuration.

Environment:

IBM Storage Protect Server 8.2.1.000, Windows Server 2022, Windows Failover Cluster configuration (installed via IBM Storage Protect installer's cluster setup).