Bit of an idea to ponder:
I have a server with 15 user databases ranging in size, the largest being 120GB. There is a blanket 'Backup Transaction Log' job with does all DBs and runs every 15 mins. The job generally takes about 1 minute to complete. What I have noticed however is that sometimes (when there seems to be some batch jobs running unsurpirisingly :rolleyes
the complete tx backup job will take up to 40 mins, and some of the backup files will be as large as 40GB. This is a bit confusing but I'm unsure if I can do anything specific from a strategy point of view:
1) Presumably more regular backups would keep any logging tuncated so the jobs should be a bit quicker?
2) Would the knockon effect of a shorter period between backups not mean that a lot would be ignored? For instance every 15 mins means if I have one that starts at 20:00 but takes 41 mins, the next one won't kick-in till 20:45. Shortening the schedule won't be much benefit?
3) Maybe the tx backups need to be split into their own jobs, rather than having one job which runs through the databases in turn? Would there be any implications to potentially multiple tx backups occuring simultaneously?
4) Am I worrying about nothing?