Enable the option (for instance,Truncate database log

for the SQL Server plugin) to truncate transaction logs after each backup

protects against unfettered growth of logs filling the server disk and eventually

hindering database functionality.

BR

Thanks for answer.

Now for testing purpose we set SQL plugin options as below:

backup type: incremental.

force incremental: false

Log truncation: Default

force full: false.

In log I can see that backup was finished with success:

2011-02-18 15:30:51 avsql Info <7028>: Working on target '(local)/VCM_Szam/i-1'
2011-02-18 15:30:51 avsql Info <7029>: Creating manager for '(local)/VCM_Szam/i-1' (hcount 453)
2011-02-18 15:30:51 avsql Info <6649>: Process 3876 (C:\Program  Files\avs\bin\avtar) for workorder MSSQL-1298039205425#2 started
2011-02-18 15:32:11 avsql Info <6446>: SQL VDI transfer of  '(local)/VCM_Szam/i-1' to  '(local)_VCM_Szam_MSSQL-1298039205425#2-3006-SQL' successful
2011-02-18 15:32:11 avsql Info <7401>: physical: D:\MSSQL\DATA\VCM_Szam.mdf
2011-02-18 15:32:11 avsql Info <7402>: logical : VCM_Szam
2011-02-18 15:32:11 avsql Info <7401>: physical: D:\MSSQL\LOGS\VCM_Szam_log.ldf
2011-02-18 15:32:11 avsql Info <7402>: logical : VCM_Szam_log
2011-02-18 15:32:16 avsql Info <6651>: Process 3876 (C:\Program Files\avs\bin\avtar) finished (code 0: Success)

Unfortunately size of log file for this database is still growing without any control.

Could anyone tell me what is going on ?  Because according to my knowledge, backup performed with those settings should reduced size of log file, am I right ?

Hello Ernesto,

Try change database log truncation for Suppress log truncation, mark show advanced options and change this.

Regards,

Luis Rogerio

hello

According to User Guide for SQL plugin, this option means:

"Suppress log     Database transaction log will not
truncation            occur under any circumstances"

...so, in what way this setting could be helpful in this case ?

Regards

Ernest

Sorry, I replied in the name "suppress" intuition.
You right.

Do you try force incremental?

Regards

Luis Rogerio

Yes, I tried force incremental option with full backup, and result was the same - still growing SQL log file.

any other suggestions ?

...after many tests and combinations of settings in SQL plugin properties I have doubts that it could works.

Maybe there is anyone who has different experience with SQL backup by Avamar ?

Regards

Ernest

Log truncation not supported for SQL 2008 for full backup, need to schedule incremental just after full backup.

For SQL 2000 and SQL 2005, leave force full and force incremental checkd as a best practive.

its recommended to run shrink database command from SQL server to shrink the log size. Ensure initial size of log file is not set to high value for databases and you are expecting it to go down to 0 kb. Minumum size of the log file (ldf) will be the initial size of ldf file as seen in SQL enterprise manager or management studio..

hope it helps