41 Posts

October 30th, 2008 21:00

DX 5.60.025 has End of Support Life. You would need to upgrade to DX 6.x to get support.
What you are seeing on the C:\ are media clips for legacy media.


see esg64927 for more info

EMC DiskXtender 2000 writing files to an EMC Centera generates both Media Clips and File Clips on the EMC Centera. The Media Clips store information about every file that has been written to the EMC Centera by EMC DiskXtender for each EMC virtual media. The more files that are written to a particular piece of EMC Media, the larger the Media Clip for that media grows. The EMC Centera client SDK (FP_Library.dll) may generate temporary file on the EMC DiskXtender server if the Media Clips grow larger than 16 Kb. These temporary files are cached EMC Media Clips that are stored locally for performance reasons.



When the EMC DiskXtender server service is stopped, the EMC Centera client SDK deletes these files. When the EMC DiskXtender server service starts up and checks each piece of EMC Media, the EMC Centera client SDK may generate these files again if they exceed the 16 Kb size. The EMC Media Clips that are not larger then 16 Kb are stored in virtual memory.

In EMC DiskXtender versions 5.60.025 through 6.10.040, the temporary files are created on the root of the System Drive(C:\). These files have a naming format that starts with the letter 't' and a file extension that is a hexadecimal number such as 't3uc.13' or 'tek.b'.

In EMC DiskXtender versions 6.20.060 and later, the temporary files are created in the C:\Documents and Settings\[DxServiceAccount]\Local Settings\Temp\ folder and have a format similar to 'FPTemp2576_25156_2784'.


Fix: EMC DiskXtender versions 5.60.049 and later no longer store the Content Addresses for the migrated files on the Media Clip for new EMC Media. All new media created in EMC DiskXtender 5.60.049 will still have a Media Clip, but it should be very small and will be stored in memory and not as a temporary file on the disk.

6 Posts

October 31st, 2008 02:00

Thank you, this was the solution to my problem. It seems that the service crashed in the past and left behind the memory reservations on the C drive. This is what filled the drive.
No Events found!

Top