SQL transaction log

[panzer]

I recently enabled "Backup logs periodically" every 60 minutes on my MS SQL 2008 server. Viewing the SQL statistics in Veeam I see that "Uploading transaction logs backup to shipping server" failes after almost 4 hours. Error Message is "Transaction log backup took longer than desired log backup interval", followed by "Cannot run program [C:\Users\xxxxxx\AppData\Local\Temp\{1d653095-e176-433a-8043-ca6fab1b2187}]. VIX Error: The virtual machine needs to be powered on Code: 3006"
The backup interval cannot be set longer than 60 minutes, so what do I do?

[foggy]

Stig, how many databases does the affected SQL server hold?

[panzer]

The affected SQL server holds 7 databases. I have set 6 of them as "simple recovery model" to exclude them from transaction log backup. I only need transaction log backup every 60 minutes for the remaining database. The database file is 190GB and the logfile is 17B.

[Gostev]

I would investigate this issue with support, as everything points out at some environmental issue in your case. Also, don't see how the issue of log backup from a single fairly small database is relevant to performance problems of backing up 200 databases - someone from moderators has made a wrong call with the topic merge here

[foggy]

It was not clear that the server is fairly small at the time the merge occurred. The error looked similar, so I merged the post. Splitting it back then...

[panzer]

Solution: Support asked me to change log shipping server from the backupserver to a server in the same subnet as the SQL-server. Now the backupjob runs in a couple of minutes.

[foggy]

Thanks for getting back with the resolution, much appreciated.