First off the "Purge" function does not remove entries, it marks them for deletion. The entries are deleted/removed during defragmentation, if you are using the CA VLB database. I would surmise the same holds true if you are using SQL instead of VLB. Todd
________________________________ From: Bill Krumel [mailto:[EMAIL PROTECTED] Sent: Thursday, December 27, 2007 10:03 AM To: NT System Admin Issues Subject: ArcServe 11.5 question We use ArcServe 11.5 to do our backups. I recently ran into a problem with the asdb_log.ldf file increasing to over 20 gig. At other times it is only about 504 KB. I thought it only increases after a backup but yesterday during mid-day the file increased from 504kb to over 20 gig. I have had purging setup in arcserve for some time now and this doesn't seem to be helping. (purges older then 15 days) CA has little documentation on this. I did end up setting up a job in MS SQL that does a shrink on the asdb_log.ldf file. (dbcc shrinkfile(asdb_log) ' After running this the file size goes from over 20 gig to 504 KB. I figured I could schedule the shrink right after the nightly backup is done and I wouldn't have any problems. However, the Arcserve purge ran last night at 12:30am and did not finish until about 6:30 am. The asdb_log was now over 20 gig. I ran the shrink and now the file is back to around 500 KB. Does anyone know what causes the asdb_log to become so big and does Arcserve prunes make this big in file size? I am considering moving the arcserve SQL database to another server with more drive space just so I never run out of space. Any ideas? thanks, Bill ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
