I'm not sure what happens to the log when it hits the restriction size. If you lose your database you can create an empty one or get a empty one from CA. Then you would use each backup set to rebuild the database by way of a "Inventory Job". Hope this helps. Todd
________________________________ From: Bill Krumel [mailto:[EMAIL PROTECTED] Sent: Thursday, December 27, 2007 12:21 PM To: NT System Admin Issues Subject: RE: ArcServe 11.5 question My asdbdat.dat (Arcserve SQL database) is around 25 gig. The log would asdb_log.ldf would get up to about 23 gig. The max file size on both was set to unrestricted growth with file growth done auto at 10%. I ended up restricting the file growth for the asdb_log.ldf to 3 gig. I understand the Transaction log (asdb_log.ldf) is used to restore the database. With me restricting the asdb_log.ldf to 3 gig what will happen if this log hits the restriction? We do have full nightly backups of the asdbdat.dat. thanks, BILL KRUMEL | Technical Support Specialist WorldView Ltd. | 402.330.0210 Ext. 1304 worldviewltd.com <blocked::http://www.worldviewltd.com/> Put documents in their place. ________________________________ From: Todd Lemmiksoo [mailto:[EMAIL PROTECTED] Sent: Thursday, December 27, 2007 10:53 AM To: NT System Admin Issues Subject: RE: ArcServe 11.5 question 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> ~
