Best practices for maintaining your Data360 Analyze Server

In an ideal situation, you would never need to bounce your Data360 Analyze server. If our Support team recommend you do, it is because a workaround is required. The leading cause of the Analyze application crashing is due to situations where the disk space is full. This aim of this article is to help you proactively manage your system to avoid this situation. 

STEPS TO MANAGE YOUR SYSTEM: 

1. Configure the automatic purging of scheduled run temp data. Open Data360 Analyze and select a data flow from the directory, then on the right-hand menu "Delete Run Data"
​

You'll need to do this on a per-data flow basis.

2. Monitor the overall usage of temp data disk space using the attached data flow, called Disk Usage.This data flow will identify temp data associated with adhoc executions by user so that the data can be deleted if no longer required. It shows the usage per user, age of the files, per data flow, and overall disk utilization. 

Usage per user:

This result set contains information on the size of temp files, and the log files that each user on the system has. It tells you the number of files a user has, and also how much space they are utilizing in MB's.

If an excessive amount of space is being given to temp / log files, then some of the older ones may need to be deleted.

Age of files / number of files per month:

This result set indicates how much log files and temp files are being retained by each user each month, as well as the total amount of space in MB's that they use. Any files older than 12 months are grouped together and presented in the 12 month column

Temp files by data flow:

This result set lists the total number of files per data flow, and the amount of space they use.

Disk Utilization:

This result set lists the total amount of space on the system, the amount that is used (in MB's and as a percentage) and the amount remaining.