trxlogs backup best practices
Can anyone get insight and recommendations on what other large enterprises with SQL Server are doing, specifically around trxlogs using sql agents. Our customer has 400+ SQL servers with some degree of trxlog backup requirement(90% based using SQL agents). The amount of jobs this generates puts a huge load on Netbackup master, causing us to scale out more which adds complexity to the environment. During peak times, the time it takes to run a single DB trxlog backup can vary greatly depending on master server load ( 30 seconds to several minutes ) which is a concern to the DBAs. There is also concern from DBA's on missing trxlog backups during maintenance windows ( OS patching(normal/emergency), NB patching, etc ).
I am looking at best practices for a very large implementation like ours (400+ servers). My questions are:
1. Are you using SQL agents to backup trxlogs
2. How many SQL servers have been implemented at your environment
3. What is trxlog backup requirement? Are you backing hourly, or 4, 6 ?