Do you have any patches applied? If you don't or at one time were running a patch earlier than Patch 8, you may be affected by this problem:

Windows changed "setinfo" so that when setting File Time to allow -1 to be passed in for the Time to indicate no change to this attribute. Previously the value could be 0 or the actual time to be used when setting info on the file. Our code checked for 0 to indicate use the same time. If the number is non-zero, it is assumed to be a valid time and used in our EAs as the new time. -1 is not a valid time for a file so when filtering I/O and passing this data back we would see in correct values for the file times. This also caused application errors in the Explorer Add-ons. This change is new with Win2k3 SP1. All versions prior to Win2k3 SP1 did not use negative values for this parameter

Resolution: DxDm5.60.049 - Patch 8 addresses this issue. These changes will also be contained in all future releases of DiskXtender.

What ends up happening is that the 'Last Write Time' value in the DiskXtender properties for the file is blank. Because of this, Dx cannot compare the last write time on the file on the extended drive, to the file on the media. Therefore, the file cannot be purged.

You will need to apply patch 8 or later (Dx 5.60.049 is up to patch 18) to prevent this issue from re-ocurring to new files. This patch, however, is not retroactive, meaning you will need to remove your media from the Media Folder, perform a drive scan, and then add the media back to the Media Folder and perform a File Restore Task. This is needed in order to re-populate the 'Last Write Time' field in the DiskXtender file properties for your files.

You can check to see if this is your issue by doing the following:

Go to the file: I:\IMAGING\APIMAGE\0\190\195414.BIN.
Right click on that file, choose DiskXtender -> View File Properties, from the fly-out menu.
Click on the "Media" tab.
If you get a message stating 'Please enter valid date and time', then you are affected by the issue described above.

Hope this helps,

-Mike

DX is 5.60.049

Server is running Windows 2003 SP1

Terry ....

Is there some way to tell what patch level we are running at?

terrry ....

Terry,

Yes, this is most likely the reason why files aren't purging and you are running out of disk space on your Extended Drive.

What version of DiskXtender are you running, and what is the OS version and Service Pack?

Thanks,

-Mike

the timestamp is 12-14-2004 1:10 PM

Terry

What's the timestamp on your DxDmService.exe file located in the C:\Program Files\Legato\DiskXtender\Bin directory?

-Mike

Then you have the base install of Dx 5.60.049. There are no patches applied. The first version of Dx that supports Win2k3 SP1 is DiskXtender 5.60.049 SR1, which is DiskXtender 5.60.049 Patch 11 or higher.

You are most likely affected by the problem I described in my previous post.

You'll need to download Patch 11 or higher (I recommend Patch 18), install the patch, and perform the instructions I listed above.

-Mike

I know how the drive scan and file restore utilities work. the question I have is how do we remove the media from the Media Folder?

Terry .....

If we had additional space available on the SAN where the extended drive is store is there an easy way that we could take advantage of it?

Terry ..