You notice that the available free space on drive C:\ is decreasing. Troubleshooting points toward a folder with the path of C:\ProgramData\Gibraltar. You research the Knowledge database and note that the issue is related to AppAssure logging.
You determine that these logs can be deleted without stopping the core service from KB#129477 - How to clear out Appassure log files and event databases that are filling up C: drive.
You learn that logging can be disabled KB#117597 - Removing Gibraltar Logging and, even if disabled, logs continue to accumulate and the issue may be solved by following the rather complex KB#127008 - Gibraltar logs keep getting created after disabling logging in Registry.
You want a fail safe process that would keep the Gibraltar log accumulation down and does not require stopping the core service to be applied and does not require excessive administrative effort.
PowerShell Scripting Disclaimer:
This script is provided "as is" for the purpose of illustrating how product tasks may be performed in conjunction with PowerShell. Support shall not be liable for any direct, indirect, incidental, consequential, or other damage alleged in connection with the furnishing or use of this script or of the principles it demonstrates. See PowerShell Scripting Support for more information.
The simplest approach to deal with the Gibraltar logs issue is to have a scheduled task running a powershell script that deletes the unnecessary Gibraltar logfiles every time it runs. A powershell script to perform this action has been prepared.
If run manually, the script shows the number and the size (in GB) of the logs to be removed and, after they are removed, the number and total size of the logs that could not be deleted as they are locked by AppAssure. No parameters are required.
The script needs to be scheduled using Windows Scheduler. The best practices for using Windows Scheduler are found in KB#147472 How to use Windows Task Scheduler to run AppAssure PowerShell scripts (Best Practices).
Powershell 3.0 or later is required.
The script code is shown below between horizontal lines and attached to this KB.