We have Sql servers set up to Log ship - One source, one destination, one monitor, roles never change.
Sometimes the restore log job will fail because the source log has not finished copying to the database server.
The logs are typically 25K-2MB. However, sometimes they will jump up to between 60MB and 300MB. Is there a specific reason for this, related to log shipping ? That amount of data isn't getting loaded into the database, which is only about 2.2GB total. Plus, these size jumps don't follow any set pattern, sometimes happening in the early morning hours. I was thinking possibly a transaction-log intensive reindex or similar, but I don't see any scheduled jobs that match this.
Even at 300MB, does ~20 minutes seem very sluggish ? Copying over a 300 meg file only takes about 45 seconds manually.