Comments
1 comment
-
Hi q_Sac,
The only real change you can make is to add the USESIMPLECOPY after the job is created. This will copy the file as part of the backup job and not use the log copy que. However the downside here is if the copy fails the whole job fails. It Would be advisable to split up the 200 DBS into smaller jobs with this approach.
Add comment
Please sign in to leave a comment.
I have an instance with 200 databases. When there is a lot of change and large log files, the pending queue gets large. And sometimes the log copy never catches up.
I know I am limited by latency between locations but was curious if there was anything I can do to tweak the way copies happen.
Thanks in Advance,
Steve