Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SQL agent

Created: 16 Jul 2012 | 2 comments
Sidorenko Andrey's picture
0 Agree
0 Disagree
0 0 Votes
Login to vote

After update to BE 2012 i saw that there are some illogical workflows in SQL agent.

  1.  SQL full backup superside log backup if backups runs in one time. I understood that log backup its incremental backup and full backup must superside incremental/differential backup. But log backup job work with another data unlike DB data backup. To avoid this issue i must to create another backup jobs with only log incremental backup  job (full backup i put to hold)
  2. Why i can exclude databases from incremental backup? For example i have SQL server with 2 DB. One DB put in full recovery mode another DB puted in simple recovery mode. If i create one backup job with incremental backups i receive a warnings because i can't create incremental backup on simple recovery database.

Can anyone say when Symantec plans resolve these issues?

Comments 2 CommentsJump to latest comment

pkh's picture

1. Why do you have to do your log backups at the same time as your database backup?  You should run your log backups after your database backups.

0
Login to vote
Sidorenko Andrey's picture

Yes ofcourse.

My backups (Full and log) run with a difference 5 hourse. Olso in the same time with SQL DB backup runs other backups (Exchange, File Servers). Other backup may continued 10 hours or more. In this situations in  Backup Exec queue i have 2 jobs with one server FulL backup of SQL Server and inceremtal backup (LOG). Before i updated to 2012 version i need to create only another backup policy with same selection list.

0
Login to vote