We have had some customers who have had issues with their GigaStor systems c: drive fill up with unwanted old Trending files and trace extractions from Apex. While these files can be and\or should be automatically managed by Observer and Apex on the GigaStor, sometimes something happens and it doesn’t. We had this issue with CloudLab too at one point. But Benoit created some Tasks through Task Scheduler to automatically delete these files once a day. I have attached the files to this email to make it easy to setup for your customers. Simply open Task Scheduler and import them. You will have to import each one at a time and you will have to do this on each GigaStor individually.
The Network Trending file has three parameters which you may need to change for your customer.
If your customer has more than one trending instance, you will need to have more than one scheduled task. So, create a copy of the file for each trending instance.
BLUE = Name of Rule – Should be different for each trending instance.
RED = Path to where trending data is located. Each trending instance will be in a different Instance0X directory.
GREEN = Number of days of data to keep. -3 says, delete trending data older than 3 days. This does not delete GigaStor packet data, only metadata already sent to Apex. Unless Apex has been down for more than 3 days or there is a catastrophic failure, there is no need to keep data on the GigaStor longer than a short period of time. For customers with a Failover Apex, you may want to set this number to 10, as this is the oldest data the Failover Apex will automatically grab.
Please log in or sign up to comment.