Using Backupexec 12.5 to backup TRN logs

This issue has been solved. See solution.
Lozloz's picture

Hi,

I am trying to figure out the best way of using the SQL BE agent to backup our databases. It seems combining full Backupexec SQL backups with built in SQL transaction logs is not an option as BE will complain about the last backup not being taken using BE.
However, we are running hourly trn log backups but due to other backups utilising the tapes, we cannot back these up to tape every hour.
Has anyone got around this? I've thought about backing up the trn to disk using BE agent and then backing all the logs up once to tape at night. Would this cause any issues. Also I believe running a full backup does not truncate the log files. Would I need to therefore run a full backup and log file backup once a day as well as running the hourly trn log backups.Any comments would be helpful.

Thanks
Lozloz

BEsymc's picture

Why are you not using SQL

Why are you not using SQL Agent to perform log backup? It is a method of SQL backups. That ways, you will not require backup using any other utility, and just Backup Exec backups would be sufficient. These errors cannot be avoided, if you are using any other application or SQL internal utilities to perform log backup. So, other utilities or tools need to be avoided, and only Backup Exec should be used. Otherwise, restores would be an issue as some sets would not be controlled by Backup Exec. So, the only way out is to use Backup Exec as a single solution for your backup strategy. Or, you may do a full backup everytime you have done a log backup using other utility, so that the sequence can be re-established.

Please mark it a solution, if this is useful.
Thanks

Lozloz's picture

Hi, Thanks for responding. I

Hi,

Thanks for responding. I want to only use Backupexec agent, my question was: how do I run hourly backups of the trn logs if tape media is not available every hour?

Thanks
Lozloz

BEsymc's picture

You may run hourly backups to

You may run hourly backups to disk, and then towards the end of day, you can schedule a duplicate backup job to tapes. use policy for this implementation. So, create a policy and create following templates in it:
1. Full backup template.. target to tape.
2. Log backup template.. schedule every hour.. target to disk.
3. Duplicate backup template.. schedule every day.. may be and target to tape to duplicate incremental backup template.

Hope this answers.
Thanks

Lozloz's picture

Thanks Hemant, That does

Thanks Hemant,

That does answer my query. Can you offer any advice on my comments about full SQL backups in BE not truncating the trn logs. How do you get around this?

Regards
Lozloz

BEsymc's picture

Full backups in SQL, are

Solution

Full backups in SQL, are never meant to truncate logs. This is how SQL is designed, so really no workarounds there. MS SQL does not work like Exchange, in this regard. So, log backup is the only way out to truncate logs. Also, if you do not want to perform point in time recovery, and also want to save on space, you may want to change the recovery model to simple. Simple recovery model would take care of log truncation automatically. the downside to this would be that you will not be able to do transaction log backup, and hence no point in time recovery.

Please mark it a solution, if this resolves your query.
Thanks

Lozloz's picture

Thanks

Thanks