For stand alone SQL boxes, I just do a standard forward incremental job. If you are concerned about disk space on the repository you can always do Forever incremental or transform previous chains to rollbacks. Either way, you can set up your tape job in such a way as to create a synthesized VBK for your "oh shit" moment when you have to restore from offline media. I do copy only on application aware for all of our SQL servers because we have a DBAs who do individual database backups/restores.
My "production" setup is considerably more intricate than most people's setups. We use a 3-headed always-on availability group for our production SQL boxes (2 synchronous with automatic failover in primary datacenter and 1 asynchronous in failover DC 150 miles away connected via a 10GB link). The two synchronous replicas are backed up in separate jobs which are chained to avoid both getting a snapshot stun at the same time which would make the core applications that use databases on those servers inaccessible for more than the momentary blip that happens when the AlwaysOn fails over.
Veeam Certified Architect