Do we *really* have to always have a full backup as part of a backup job?
We're trying to backup our SQL server 2008 DBs. I got frustrated with the lack of options in this new version and called tech support have them create the backup jobs for me for the SQL DBs. The first call the tech tried telling me what to do but it just didn't make sense (part my fault for being unable to understand what he was saying with his heavy accent, and the other part being he was giving me directions for some over version that wasn't 2012). So I called back a second time to get it working and after the tech spoke to another tech on how to schedule jobs for SQL he created a plan.
The plan isn't fitting our needs. What I would like is the following:
Daily incremental backups of SQL starting at 6AM then repeating again every two hours till 4PM on Monday - Friday. Then at 5PM (or anytime really after 4P) we'd run a full SQL DB backup. Doesn't seem hard to build this but it's a different story in 2012.
The attached pic shows how the tech support agent configured this portion of BE. He said it has to do a full backup daily in order for the differentials to work -- ok, fine, but why only a single differential and why does it run after the full? Then it has to run another full on the weekend so it can truncate the logs. This schedule doens't seem to fit our needs yet the scheduler doens't have the options we need. It doens't make sense to run a full backup then a differential right after. (does it?!)