Francis
 New Member Posts:2

 |
08/27/2012 2:51 PM |
|
We have an old DMX installation that keeps eating up disk space. It would appear that it's creating multiple *.resources files that have a file size of approximately 2GB. These files don't appear to have entries in the dmx_entries table so I don't believe its due to any of the synced folders containing such large files. In total the 2 synced folders in this installtion only contained 64GB of files, yet this morning the DMX repository contained 270GB. Any idea what is going on? |
|
|
|
|
Peter Donker
 Veteran Member Posts:4536

 |
08/27/2012 4:02 PM |
|
It looks like it is having a hard time comparing the files and importing them again. First question: which version of DMX is this? Secondly: what you could do is to set the versions to keep to 1 on the large files. This means that old versions get deleted. You can check if there are old versions just by selecting one of the files, by the way. You should see this when you opt to see the details. Peter |
|
|
|
|
Francis
 New Member Posts:2

 |
08/27/2012 5:09 PM |
|
The version of DMX the is being used is 5.1.3 I've set the versions to keep to 1 from the previous value of 0. However in the past 30 minutes it's still created 4 of these 2GB files. Should the VersionsToKeep column in the DMX_Entries table have NULL values? It seems that all but a handful of records is set to NULL. |
|
|
|
|
Peter Donker
 Veteran Member Posts:4536

 |
08/30/2012 10:35 AM |
|
VersionsToKeep should be 1 if you don't want it to create multiple versions. If I were you I'd also consider upgrading. Since 5.1.3 many improvements have been made to this part of the app. Peter |
|
|
|
|