Link to home
Start Free TrialLog in
Avatar of rufustmac
rufustmac

asked on

Enable transaction log backup for SQL db in Backup Exec

I run Backup Exec 12.5 and both my daily and weekly backups are failing on all of the SQL Servers with the following error message, "The transaction log for database 'mydbname' is full".  After doing some digging around, it seems that the regular Backup Exec backups do not backup the transaction log on the DB.  It instructs you to run a seperate backup job after the normal backup that will backup the transaction log for the DB.  However, I don't know how to configure this in Backup Exec.

Enable transaction log backup for SQL db in Backup Exec
Avatar of Syed Mutahir Ali
Syed Mutahir Ali
Flag of United Kingdom of Great Britain and Northern Ireland image

http://www.backupexecfaq.com/articles/concepts/backing-up-microsoft-sql-server.html
http://seer.entsupport.symantec.com/docs/300158.htm

To back up SQL transaction logs
On the navigation bar, click the arrow next to Backup.
Click New Backup Job.
On the Properties pane, under Source, click Selections, and then select the data you want to back up.

To select SQL data, click the domain name icon or icons that contain the SQL installations, and then click the actual Windows computer icon that contains the SQL installation. If you are using a cluster server, make backup selections from the virtual server.
A list of shared network directories appears, along with an icon that represents the SQL installation.
To select SQL backup job properties, on the Properties pane, under Settings, click Microsoft SQL.
After selecting job options, start the backup job or select other backup options from the Properties pane, and then start the backup job.




 
http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/
Following code always shrinks the Truncated Log File to minimum size possible.
USE DatabaseName
GO
DBCC SHRINKFILE(<TransactionLogName>, 1)
BACKUP LOG <DatabaseName> WITH TRUNCATE_ONLY
DBCC SHRINKFILE(<TransactionLogName>, 1)
GO
Reference : Pinal Dave (http://www.SQLAuthority.com),
I would suggest looking at policies within BE12.5; that way you can create a single policy (SQL Full, SQL Diff, SQL Log) and just create a new job from policy.

Simples.
ASKER CERTIFIED SOLUTION
Avatar of Vincedee
Vincedee

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rufustmac
rufustmac

ASKER

Very helpful answer with the picture included.  Exactly what I was looking for.

Thanks.