System Information Volume folder, on Server 2003, filling up.

I have a Server 2003 with a volume which is running out of space.
The volume in question is a small volume used for MS SQL 2000 databases.
The folder causing problems, using space, is System Information Volume.

F:\System Volume Information>dir /aahs
Volume in drive F is DB
Volume Serial Number is 2A8C-7ECA

Directory of F:\System Volume Information

06/06/2005 11:02 PM 574,717,952
100{3808876b-c176-4e48-b7ae-04046e6cc752}
07/06/2005 11:02 PM 431,079,424
108{3808876b-c176-4e48-b7ae-04046e6cc752}
08/06/2005 11:02 PM 422,748,160
112{3808876b-c176-4e48-b7ae-04046e6cc752}
09/06/2005 11:02 PM 450,838,528
116{3808876b-c176-4e48-b7ae-04046e6cc752}
10/06/2005 06:01 AM 314,572,800
120{3808876b-c176-4e48-b7ae-04046e6cc752}
31/05/2005 11:01 PM 408,981,504
84{3808876b-c176-4e48-b7ae-04046e6cc752}
01/06/2005 11:01 PM 438,829,056
88{3808876b-c176-4e48-b7ae-04046e6cc752}
02/06/2005 11:02 PM 456,753,152
92{3808876b-c176-4e48-b7ae-04046e6cc752}
03/06/2005 11:02 PM 450,338,816
96{3808876b-c176-4e48-b7ae-04046e6cc752}
27/04/2004 05:02 PM 20,480 tracking.log
10 File(s) 3,948,879,872 bytes
0 Dir(s) 123,625,472 bytes free

I do not have System Restore points on this server, nor does this volume use
Shadow Copies.

All the files are created at around 11:00, which is when Backup Exec run a
backup for this volume.

Although I hate doing this, I'm going to delete the oldest file and free up
some space, I can;t have my dbs failing due to lack of space.

Any ideas ?

[bayo]

fix = seer.support.veritas.com/docs/269989.htm

To resolve the issue, stop the Volume Shadow Copy service.
a. Open Services from Start -> Programs -> Administrative Tools.
b. Locate the Volume Shadow Copy service, and Stop the service.
c. The files can be manually deleted after the service is stopped

[itprohelp]

I had the same problem. The Backup Exec jobs were not completing successfully and my System Volume folder grew to over 90GB. All I had to do was stop and start the Volume Shadow Copy service. All of the temp files were gone after the service started up again.