We have a test environment with project collections which are identical copies of production ones - albeit a few months old.
After the test environment was setup (basically new, segregated App & Data tier with copies of project collections attached), Reporting, Lab Management, SharePoint, Build Configuration and Scheduled Backups werenot configured and if enabled they were immediately disabled.
The environments (VMs) were left running since 16th November 2015 after it was confirmed the environment was up and operational - around 2 weeks ago we noticed that the disk where the project collection reside has ran out of space. We believe that the growth has taken place from the moment the project collection was attached and until it ran out of disk space.
Test Environment
App-Tier - 12.0.31101.0 (Tfs2013.Update4)
Data-Tier - Microsoft SQL Server 2014 - 12.0.4416.0 (X64)
Prod Environment:
App-Tier - 12.0.31101.0 (Tfs2013.Update4)
Data-Tier - Microsoft SQL Server 2014 - 12.0.4416.0 (X64)
Before we delete the project collection and re-attach another copy, we would like to better understand how and what caused the sudden unexplainable growth of the "dbo.tbl_Content" table. As mentioned above as far as we know no TFS jobs are running which are managed from within the TFS console.
Some diagnostics output: