Avast_log.ldf is 2GB!

Avast Business Avast Distributed Network Manager
1

What is contained in c:\program files\microsft sql sever\MSSQL$AVAST\data\avast_log.ldf ??

It’s about 2GB!!!

How can I reduce its size??

Any help? It’s urgent.

Thanks

2

It’s the database transaction log.

What you could do is

  1. back up the database
  2. delete the files
  3. restore the database.

The tx log is so big because the DB is set to “Full Recovery” mode. We’re now thinking about switching it to the Simple Recovery mode instead that would greatly reduce the size of the log.

3

Well; we try to make the maintenance as you show.
During the operation:

  1. restore the database.

we encountered the following errors

“*: cannot initialize data source, error 0x80004005”

then
“Cannot check whether database exists, error 42000”

then
“Error while restoring the database , error 42000”

About future

About :“The tx log is so big because the DB is set to “Full Recovery” mode. We’re now thinking about switching it to the Simple Recovery mode instead that would greatly reduce the size of the log”

when will be ready the expected fix ?
What about waiting the fixes ? Any suggests?

4

Do you have MS SQL Server (full version)?

5

We use the MSDE version

6

Before restoring the DB, try stoping the avast Management Server service. You may also try dropping the DB first.

To reduce the size of the tx log, set the Tx Log Backup task schedule to run daily (instead of weekly). You can delete the backups (the files on your hard drive) as necessary. Backing up the tx log always removes it from the database so that it doesn’t grow.

Cheers,
Vlk

7

Try to make a bit clearify.

I have a lot of trouble because of my avast_log.LDF is growing very quickly. Now it’s about 2,5 GB !!!
The database avast.mdf is normal sized.

I need to drop the .ldf, because it’s growing so fast to hang my system. We don’t know why.
I did as you suggest. Since 23/7, the tx log has increased more than 500 MB !!

I try to:

  1. back up the database
  2. delete the files (bot ldf and mdf)
  3. restore the database

but unsuccessfully.

We could not restore the database, even with avast Management Server service stopped.

I use the AMS tool, database management to restore the database, but I got several errors, like

Cannot execute internal SQL command 0x80040E14
No permission to access the database avast

I need support.
What’ s the correct path?
Do I need to backup both database mdf and tx log and how often ?

Thanks

Sergio

8

So you dropped the DB. Well in this case, the ADNM is not running, right? How come the transaction log is then growing?

Or you were able to restore the DB?

Can you also check the \data\log folder? Especially the error.log file? Does it contain any entries related to the restore operation?

Haven’t you changed the database logon information (sa password, for example)?

Thanks

9

First of all please let me know what does it mean in your first sentence:

"So you dropped the DB. Well in this case, the ADNM is not running, right? How come the transaction log is then growing? "

If you intend drop equal to delete it then:

a) SQLAgent$AVAST stopped
b) avast! Management Server stopped

Delete the database (really, rename both ldf and mdf)

Trying to restore from backup

a) SQLAgent$AVAST started

Restoring using AMS Maintenance

Choose the last .bak file done
Errors like this mornig

Opening the error.log file

26/07/2004 16.20.35 1090851635
SBS\administrator 6112 Database check on SBS2003\avast server failed with 0000A410 error. Use AMS Tool to fix the problem.

I attach the file

No change were made about sa

If restore was made with b) avast! Management Server running I got error 42000 AMS While restoring the database.

The ldf and mdf have been created into the data folder, but the size of the files is the same

Thanks

Sergio

10

“Drop” means clicking the “Delete DB” button in the AMS Maintentance Tool.
Try with both the avast management server service stoped and running (the MSSQLServer$AVAST service must be running – otherwise it will fail).

11

Avast management server stopped

Delete DB from AMS. Successfully.
No files ldf and mdf in the E:\Program Files\Microsoft SQL Server\MSSQL$AVAST\Data

Restore from backup

Errors

Cannot execute Internal SQL command 0x80040E14
The database Abast doesn’t exist

Nothing change if restore was made with Avast management server running

In the error.log

26/07/2004 17.11.35 1090854695 SBS\administrator 2780 Database check on SBS2003\avast server failed with 0000A410 error. Use AMS Tool to fix the problem.

Sergio

12

Right. At this phase, first do Create DB, and then do Restore DB.
That should work.

13

Yes, I did as you wrote
Create DB
Restore DB from backup
Everything was ok but the size
The .ldf file has still the same size before backup it up.

Sergio

14

Do you have SBS 2003 Standard or Premium?

I.e. do you have access to a full SQL 2000 server tools?
The Enterprise manager, namely?

Thanks

15

SBS 2003 std edition
No access to Enterprise manager tool

Sergio

16

I’m here at server side in which the size of .ldf file is about 3 GB !!!

I have to reduce the ldf size.

a) First of all, when you suggest me to backup the database does it mean backup both database and transaction log ?

b) What does exactly contain the transaction log files. How often does it need to be backed up ?

c) Is it possible to put the ldf files in another path instead of C:\Program Files\Microsoft SQL Server\MSSQL$AVAST\Data
i.e. another disk

d) What happen if a ldf file is deleted ?

Sergio

17

Can you give me VPN/remotedesktop access to the machine?
That seems to be the easiest option.

Thanks.

18
Can you give me VPN/remotedesktop access to the machine?

I’m sorry, we can’t access to this server by remote machine.

Could you answer us to the previous post ?

Thanks

Claudio

19
a) First of all, when you suggest me to backup the database does it mean backup both database and transaction log ?

Each backup of the log effectively deletes its contents from the database. However, the ldf file is not shrinked because SQL reuses its space.

You can back it up daily, or even multiple times a day. You can delete the backup files of course (they’re in \data\backup by default). BTW this folder will be real big now if you haven’t deleted its contents yet.

b) What does exactly contain the transaction log files. How often does it need to be backed up ?

It’s a standard SQL thing. For a detailed explanation, see e.g. http://www.winnetmag.com/SQLServer/Article/ArticleID/9792/9792.html

The ADNM database was set to recovery mode full which makes the log really large. We’ll change this to recovery mode simple in the next update to reduce the size of the log (the trade-off is that the recovery possibilities in case of failure will be somewhat limited).

c) Is it possible to put the ldf files in another path instead of C:\Program Files\Microsoft SQL Server\MSSQL$AVAST\Data i.e. another disk

Sorry, this is not possible without the Enterprise manager (or some programming)

d) What happen if a ldf file is deleted ?

If the database is running, the file will be locked so you won’t be able to delete it.

20

I’m at the server side. We could not give you a remote access., but if possible we can make a phone call and try to solve the problem. I need to solve it.

Wait a response

Sergio