cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec SQL backup transaction logs backup method full

jerkens
Level 3

Hey, good morning,

i want to backup SQL database including transaction logs.

I already did a backup of the database and restored it successfully.

But i am not sure if there was a transaction log backup... i found an article, where is written that i have to choose or change the backup method ... edit the backup, choose the Microsoft SQL tab and change the method, but i have only FULL and FULL COPY

nothing with Logs, Transaction, Truncate, etc. like here:

https://www.veritas.com/support/en_US/article.000048648

 

How can i get it? is it another agent? or am i using the wrong version?

Maybe i am blind, or something... but i could not find it.

 

Thanks!

5 REPLIES 5

VJware
Level 6
Employee Accredited Certified

First, check if transaction log backups are required or not. If the recovery model of the DBs is set to Simple, then they are not required.

If they are required, then in addition to the Full Backup, click on "Add a backup job". Then you can choose Log etc.

jerkens
Level 3

hey,

unfortunately not, that is what i was trying to say...

if i create a new backup job, i can go to the Microsoft SQL tab and can only choose

FULL - back up databases

FULL COPY - back up databases (copy)

 

there is no chance to choose Log etc.

where can i do that?

 

like here: https://www.veritas.com/support/en_US/article.000048648

 

 

pkh
Moderator
Moderator
   VIP    Certified
This is correct. This is the initial full backup. You need to add another job to your scheduled job and then you will be allowed to choose log backup which is something like an incremental job

pkh
Moderator
Moderator
   VIP    Certified

Also, read my article below

https://www.veritas.com/community/articles/how-backup-sql-logs-and-truncate-them-be-2012

It is still valid for BE 15

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Just to explain the reason for this.

The method we use to backup SQL involves making use of Microsoft provided mechanisms and these mechanisms do not truncate the logs for a full backup, therefore you have to run a specific log backup at least once after a full, although best practice kind of depends on how busy your SQL server is. For instance a busy SQL server you might do a daily full backup with  2 hourly log backups during business hours. For a less busy SQL server you might do a weekly full backup with daily log backups in between. Your SQL administrator (DBA) is probably best placed to help decide what frequency is best for your SQL instance.

Note: If you compare this with how an Exchange server backup process works then because Microsoft did provide a process that truncates the logs during a full backup we can truncate Exchange logs during a full.