We use NetBackup here at Stack Exchange, and I'm working on revamping our backup policy to be more efficient.
Currently, we use SQL 2008 R2 and have the SQL run maintenance plans to backup the data to a .bak file. Once that file is written, we then backup the directory that the .bak files are stored in.
We don't use the SQL Agent for NetBackup since we use the .bak files for other things beyond just simple backups.
I was thinking of doing a schedule of Weekly/Diff/Cume rotations but considering the fact that the directories will have large files that are guaranteed new every day, and given that our system automatically ages out backups that are older than a certain number of days, I'm thinking that the standard "office fileserver" scenario is probably less efficient than other methods.
Is there a "most efficient" way to handle this?