If you run Team Server for long enough time it will eventually accumulate enough files that they will start filling up your Hard Drive Space. This article will go through the several places you can check to reduce that accumulation.
The first places to review are the Team Server Logs and Tomcat Logs, since they can grow significantly over time; if you need to keep them, they can be moved to another location or drive. The etlvar\logs folder can also be cleaned of dated folders, although that usually does not free up much space.
Team Server Logs
Location: <InstallDir>\Idera\Idera Team Server “version”\logs
Tomcat Logs
Location: <InstallDir>\Idera\Idera Team Server “version”\tomcat\logs
Etlvar logs
Location: <InstallDir>\Idera\Idera Team Server “version”\etlvar\logs
The Repository RepoIn, RepoOut, and application folders can accumulate temporary files as well. These files usually do not take up gigabytes of space, but it is still important to keep them cleaned out and check whether they are building up.
Repo In and Repo Out
<InstallDir>\Idera\ERStudio Repository “version”\RepoIn
<InstallDir>\Idera\ERStudio Repository “version”\RepoOut
Repository Application folder
<InstallDir>\Idera\ERStudio Repository “version”
File types that are temporary and can be deleted:
• .IN
• .OUT
• .PRI
• .PRO
• .IRW
• .IRO
• .ERR
• .CNL
PortalIntf can also collect temporary DM1 files that consume space, although they will reappear whenever a model is published, so the benefit from deleting them is usually limited. Similarly, etlvar\data is mostly temporary and will be recreated as models are published.
I would recommend to start with these recommendations and then move forward depending on how much the size was cut during this procedure.
Was this article helpful?
