Doing a full backup of a SQL database does not truncate the transaction logs.  You have to run another job to backup the transaction logs and truncate them. In the SQL section of your job properties, select "Log - Back up transaction log." as the SQL backup method.

Can we do truncate SQL by one job. It doesn't make sense if I would like to use Full Backup everyday and run another job for backup log for truncate.

If you just don't want to back up the transaction logs, you can set the recovery model for all your databases to 'simple'. In this case, performing a full backup will essentially flush the transaction log at the same time. You do this through SQL Server Management Studio - right-click the database, select Properties, open the Options page, and select "Simple" from the Recovery Model dropdown.

I would only recommend doing that if your databases are small enough that you can regularly do full backups of them. I have jobs set up to run full backups every night, and transaction log backups every hour, which gives us only a small window where data would be lost if the database exploded.

So this exception is not effect to our restore job, isn't it? If so, I will leave it.

It will not affect your restore, but your transaction logs will keep growing.  When they are full, you would not be able to update your database.

Right. This exception will not affect the restore. But I would recemmend that you perform a log backup for following reason.

This exception is designed to help customers manage the size of SQL databases and transaction logs. Symantec recommends scheduling regular log backups of databases this will help keep the transaction logs at a manageable size.

Thanks,

-Sush...