IFor regular backups you can use a maintenance plan with the following schedule:
Take Full Backup for all User database at 5pm and another at 11pm
Between 11pm and 5pm you can create another maintenance (or add subplans) to take Log Backups.
It may work fine for you, but it cannot work for every single situation out there.
Consider 24x7 operations. Not running log backups for 6 hours will have unacceptable impact on database recovery (not to mention log growth).
What about huge databases that take 6+ hours to do a full backup?
If that's for a 9-5 operation, why two full backups each night? If it's for a 24x7 operation what about the impact of the backups on performance?
Backup and restore strategies tend to be very specific to the environment, the SLAs for downtime and data loss, the available maintenance windows, etc. There's no one-size-fits-all solution to backup/restore strategy.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass