Discussions specific to the VMware vSphere hypervisor
Post Reply
jonathan.brown
Novice
Posts: 6
Liked: never
Joined: Apr 12, 2018 2:40 pm
Full Name: Jonathan Brown
Contact:

SQL Transaction Log Errors labeled as Warnings

Post by jonathan.brown » Mar 29, 2019 3:32 pm

Hello all,

Long time viewer, first time poster!

I recently resolved a case regarding some of my VMs not being backed up by my SQL Server Trans Log jobs. One of the bigger concerns that came out of this case was the fact that Veeam treats databases not backed up by trans log jobs as a Warning, not an Error.

Example:
Here is the "warning" message that shows up in the Statistics Windows for the trans log job:

Code: Select all

3/27/2019 1:33:04 AM :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 1:43:14 AM :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 1:43:14 AM :: SQL Server transaction log backup took longer than desired log backup interval
In my opinion, these should show up as Errors. Not Warnings. Is there a way for me to update our deployment so that these messages come across as errors? Or can I submit this as a Bug so that it can be fixed in a future release?

Thanks,
Jon

HannesK
Veeam Software
Posts: 3764
Liked: 454 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by HannesK » Apr 01, 2019 6:26 am

Hello Jon,
and welcome to the forums.

May I ask you for the case number you mention in the beginning? And would it be possible that you post a screenshot just to make sure we are talking about the same thing (I guess I know what you mean, but just to make sure)

Thanks,
Hannes

veremin
Product Manager
Posts: 16778
Liked: 1404 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by veremin » Apr 01, 2019 3:49 pm

It's by design behaviour, if during next interval the job is restarted successfully, then, the resulting status will be "Success".

If job fails to restart four times in a row, then, the resulting status will be "Failed".

Thanks!

jonathan.brown
Novice
Posts: 6
Liked: never
Joined: Apr 12, 2018 2:40 pm
Full Name: Jonathan Brown
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by jonathan.brown » Apr 10, 2019 3:51 pm

Hello Hannes,
The Case number is 03481733.

I can't see where I can attach an image. Can you tell me how to do that?

The logs are located under the statistics of the running Transaction Log Backup job.

I also understand that this is the designed behavior. My main point is that if a transaction log backup fails, it should be flagged as an error. It is very difficult to monitor our backups and report on them if we can't track errors like this.

Thanks,
Jon

HannesK
Veeam Software
Posts: 3764
Liked: 454 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by HannesK » Apr 12, 2019 7:56 am

Image

I use snaggy for image upload. See screenshot above from the full editor

jonathan.brown
Novice
Posts: 6
Liked: never
Joined: Apr 12, 2018 2:40 pm
Full Name: Jonathan Brown
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by jonathan.brown » Apr 12, 2019 11:37 am

Ah, gotcha. Thanks HannesK!
Here's the screenshot of what I am referring to.
Image

Most of the databases in the underlined 'Warning' message should have been backed up by the transaction log job. My main issue with this showing as a warning is that these databases are now outside the recovery service level agreement for our business. I also discussed this with the technical support analyst of the case I was working on, and he agreed that these type of messages should be flagged as errors instead of warnings.

Thanks,
Jon

veremin
Product Manager
Posts: 16778
Liked: 1404 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by veremin » Apr 12, 2019 5:12 pm

This is expected behaviour.

Doesn't a job get a Failed status after fourth restart?

Thanks!
It's by design behaviour, if during next interval the job is restarted successfully, then, the resulting status will be "Success".

If job fails to restart four times in a row, then, the resulting status will be "Failed".

jonathan.brown
Novice
Posts: 6
Liked: never
Joined: Apr 12, 2018 2:40 pm
Full Name: Jonathan Brown
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by jonathan.brown » Apr 12, 2019 5:18 pm

No, it never gets a failed status. It always is flagged as a warning.

According to the support analyst, the fact that it never gets flagged as an error is the expected behavior. I am requesting that the expected behavior be changed. If a transaction log backup fails, it should throw an error.

Thanks,
Jon

veremin
Product Manager
Posts: 16778
Liked: 1404 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by veremin » Apr 12, 2019 5:19 pm

Based on the information I have, it should be marked as Failed after series of retries. I will double check the case internally next week; will keep you updated. Thanks!

jonathan.brown
Novice
Posts: 6
Liked: never
Joined: Apr 12, 2018 2:40 pm
Full Name: Jonathan Brown
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by jonathan.brown » Apr 12, 2019 5:24 pm

Thank you!

Also, here is an example of a day's worth of logs for when we had the transaction log issues. You can see that the whole day, it could not backup all of the databases on the SQL Server, yet it never errored:

Code: Select all

3/27/2019 01:06:49 :: Transaction log backup interval 30 minutes
3/27/2019 01:06:49 :: New transaction log backup interval started at 3/27/2019 1:06:49 AM
3/27/2019 01:06:49 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 01:06:54 :: Using guest interaction proxy ORLVEEAMFTLPRX6 (Same subnet)
3/27/2019 01:07:19 :: Required backup infrastructure resources have been assigned
3/27/2019 01:07:19 :: Using Backup Repository SFA 04 scale-out repository extent
3/27/2019 01:12:41 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 01:12:46 :: Using guest interaction proxy ORLVEEAMFTLPRX6 (Same subnet)
3/27/2019 01:22:52 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 01:22:58 :: Using guest interaction proxy ORLVEEAMFTLPRX3 (Same subnet)
3/27/2019 01:33:04 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 01:33:10 :: Using guest interaction proxy ORLVEEAMFTLPRX3 (Same subnet)
3/27/2019 01:43:14 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 01:43:14 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 01:43:14 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 01:43:14 :: SQL Server transaction log backup interval has expired
3/27/2019 01:43:14 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 01:43:14 :: New transaction log backup interval started at 3/27/2019 1:43:14 AM
3/27/2019 01:43:15 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 01:43:22 :: Using guest interaction proxy ORLVEEAMFTLPRX3 (Same subnet)
3/27/2019 01:53:55 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 01:54:01 :: Using guest interaction proxy ORLVEEAMFTLPRX3 (Same subnet)
3/27/2019 02:04:19 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 02:04:24 :: Using guest interaction proxy ORLVEEAMFTLPRX3 (Same subnet)
3/27/2019 02:13:48 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 02:13:48 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 02:13:49 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 02:13:49 :: SQL Server transaction log backup interval has expired
3/27/2019 02:13:49 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 02:13:49 :: New transaction log backup interval started at 3/27/2019 2:13:49 AM
3/27/2019 02:13:56 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 02:14:02 :: Using guest interaction proxy ORLVEEAMFTLPRX5 (Same subnet)
3/27/2019 02:24:08 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 02:24:14 :: Using guest interaction proxy ORLVEEAMFTLPRX5 (Same subnet)
3/27/2019 02:34:13 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 02:34:19 :: Using guest interaction proxy ORLVEEAMFTLPRX5 (Same subnet)
3/27/2019 02:44:23 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 02:44:23 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 02:44:23 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 02:44:23 :: SQL Server transaction log backup interval has expired
3/27/2019 02:44:23 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 02:44:23 :: New transaction log backup interval started at 3/27/2019 2:44:23 AM
3/27/2019 02:44:25 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 02:44:30 :: Using guest interaction proxy ORLVEEAMFTLPRX5 (Same subnet)
3/27/2019 02:54:36 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 02:54:41 :: Using guest interaction proxy ORLVEEAMFTLPRX5 (Same subnet)
3/27/2019 03:04:47 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 03:04:52 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 03:14:57 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 03:14:57 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 03:14:57 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 03:14:57 :: SQL Server transaction log backup interval has expired
3/27/2019 03:14:57 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 03:14:57 :: New transaction log backup interval started at 3/27/2019 3:14:57 AM
3/27/2019 03:14:58 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 03:15:04 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 03:25:09 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 03:25:15 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 03:35:21 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 03:35:27 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 03:45:31 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 03:45:31 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 03:45:31 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 03:45:31 :: SQL Server transaction log backup interval has expired
3/27/2019 03:45:31 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 03:45:31 :: New transaction log backup interval started at 3/27/2019 3:45:31 AM
3/27/2019 03:45:32 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 03:45:38 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 03:55:43 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 03:55:49 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 04:05:55 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 04:06:01 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 04:16:06 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 04:16:06 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 04:16:06 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 04:16:06 :: SQL Server transaction log backup interval has expired
3/27/2019 04:16:06 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 04:16:06 :: New transaction log backup interval started at 3/27/2019 4:16:06 AM
3/27/2019 04:16:07 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 04:16:12 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 04:26:19 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 04:26:25 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 04:36:30 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 04:36:36 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 04:46:41 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 04:46:41 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 04:46:41 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 04:46:41 :: SQL Server transaction log backup interval has expired
3/27/2019 04:46:41 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 04:46:41 :: New transaction log backup interval started at 3/27/2019 4:46:41 AM
3/27/2019 04:46:42 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 04:46:48 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 04:56:54 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 04:57:00 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 05:07:06 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 05:07:11 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 05:17:16 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 05:17:16 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 05:17:16 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 05:17:16 :: SQL Server transaction log backup interval has expired
3/27/2019 05:17:16 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 05:17:16 :: New transaction log backup interval started at 3/27/2019 5:17:16 AM
3/27/2019 05:17:18 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 05:17:23 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 05:27:29 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 05:27:34 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 05:37:40 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 05:37:46 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 05:47:51 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 05:47:51 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 05:47:51 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 05:47:51 :: SQL Server transaction log backup interval has expired
3/27/2019 05:47:51 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 05:47:51 :: New transaction log backup interval started at 3/27/2019 5:47:51 AM
3/27/2019 05:47:52 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 05:47:58 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 05:58:04 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 05:58:09 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 06:08:15 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 06:08:20 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 06:18:25 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 06:18:25 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 06:18:25 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 06:18:25 :: SQL Server transaction log backup interval has expired
3/27/2019 06:18:26 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 06:18:26 :: New transaction log backup interval started at 3/27/2019 6:18:26 AM
3/27/2019 06:18:27 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 06:18:33 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 06:28:38 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 06:28:44 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 06:38:49 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 06:38:54 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 06:48:59 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 06:48:59 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 06:48:59 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 06:48:59 :: SQL Server transaction log backup interval has expired
3/27/2019 06:48:59 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 06:48:59 :: New transaction log backup interval started at 3/27/2019 6:48:59 AM
3/27/2019 06:49:00 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 06:49:06 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 06:59:12 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 06:59:18 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 07:09:23 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 07:09:28 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 07:19:33 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 07:19:33 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 07:19:33 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 07:19:33 :: SQL Server transaction log backup interval has expired
3/27/2019 07:19:33 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 07:19:33 :: New transaction log backup interval started at 3/27/2019 7:19:33 AM
3/27/2019 07:19:34 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 07:19:40 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 07:29:45 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 07:29:51 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 07:39:57 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 07:40:02 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 07:50:07 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 07:50:07 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 07:50:07 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 07:50:07 :: SQL Server transaction log backup interval has expired
3/27/2019 07:50:07 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 07:50:07 :: New transaction log backup interval started at 3/27/2019 7:50:07 AM
3/27/2019 07:50:09 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 07:50:14 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 08:00:20 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 08:00:26 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 08:10:31 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 08:10:37 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 08:20:42 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 08:20:42 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 08:20:42 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 08:20:42 :: SQL Server transaction log backup interval has expired
3/27/2019 08:20:42 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 08:20:42 :: New transaction log backup interval started at 3/27/2019 8:20:42 AM
3/27/2019 08:20:43 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 08:20:48 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 08:30:54 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 08:30:59 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 08:41:05 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 08:41:11 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 08:51:15 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 08:51:15 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 08:51:16 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 08:51:16 :: SQL Server transaction log backup interval has expired
3/27/2019 08:51:16 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 08:51:16 :: New transaction log backup interval started at 3/27/2019 8:51:16 AM
3/27/2019 08:51:17 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 08:51:22 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 09:01:28 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 09:01:34 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 09:11:39 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 09:11:45 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 09:21:50 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 09:21:50 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 09:21:50 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 09:21:50 :: SQL Server transaction log backup interval has expired
3/27/2019 09:21:50 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 09:21:50 :: New transaction log backup interval started at 3/27/2019 9:21:50 AM
3/27/2019 09:21:51 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 09:21:57 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 09:32:03 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 09:32:09 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 09:42:15 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 09:42:20 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 09:52:24 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 09:52:24 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 09:52:24 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 09:52:25 :: SQL Server transaction log backup interval has expired
3/27/2019 09:52:25 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 09:52:25 :: New transaction log backup interval started at 3/27/2019 9:52:25 AM
3/27/2019 09:52:26 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 09:52:31 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 10:02:38 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 10:02:44 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 10:12:48 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 10:12:54 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 10:22:58 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 10:22:58 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 10:22:59 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 10:22:59 :: SQL Server transaction log backup interval has expired
3/27/2019 10:22:59 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 10:22:59 :: New transaction log backup interval started at 3/27/2019 10:22:59 AM
3/27/2019 10:23:00 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 10:23:07 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 10:33:11 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 10:33:18 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 10:43:23 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 10:43:29 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 10:53:33 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 10:53:33 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 10:53:33 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 10:53:33 :: SQL Server transaction log backup interval has expired
3/27/2019 10:53:33 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 10:53:33 :: New transaction log backup interval started at 3/27/2019 10:53:33 AM
3/27/2019 10:53:34 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 10:53:40 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 11:03:45 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 11:03:50 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 11:13:56 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 11:14:01 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 11:24:06 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 11:24:06 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 11:24:06 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 11:24:06 :: SQL Server transaction log backup interval has expired
3/27/2019 11:24:06 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 11:24:06 :: New transaction log backup interval started at 3/27/2019 11:24:06 AM
3/27/2019 11:24:07 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 11:24:13 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 11:34:18 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 11:34:24 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 11:44:29 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 11:44:35 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 11:54:40 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 11:54:40 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 11:54:40 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 11:54:40 :: SQL Server transaction log backup interval has expired
3/27/2019 11:54:40 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 11:54:40 :: New transaction log backup interval started at 3/27/2019 11:54:40 AM
3/27/2019 11:54:41 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 11:54:47 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 12:04:52 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 12:04:58 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 12:15:03 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 12:15:09 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 12:25:13 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 12:25:13 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 12:25:13 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 12:25:13 :: SQL Server transaction log backup interval has expired
3/27/2019 12:25:14 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 12:25:14 :: New transaction log backup interval started at 3/27/2019 12:25:14 PM
3/27/2019 12:25:15 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 12:25:20 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 12:35:26 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 12:35:31 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 12:45:37 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 12:45:43 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 12:55:48 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 12:55:48 :: SQL Server transaction log backup took longer than desired log backup interval
3/27/2019 12:55:48 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 12:55:48 :: SQL Server transaction log backup interval has expired
3/27/2019 12:55:48 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 12:55:48 :: New transaction log backup interval started at 3/27/2019 12:55:48 PM
3/27/2019 12:55:49 :: Failed to prepare guest for SQL Server transaction log backup Details: Timeout to start agent
3/27/2019 12:55:55 :: Using guest interaction proxy ORLVEEAMFTLPRX9 (Same subnet)
3/27/2019 13:05:50 :: Removing guest components
3/27/2019 13:05:51 :: Transaction logs for the following databases were not backed up: master;model;msdb;Production;OBAPPS;Archive_CO
3/27/2019 13:05:51 :: Transaction log backup completed at 0.0 KB/s with bottleneck: N/A
3/27/2019 13:05:51 :: SQL Server transaction log backup interval has expired
3/27/2019 13:05:51 :: Backed up 0.0 B of transaction logs for 0 databases:  at 0.0 KB/s with bottleneck: N/A
3/27/2019 13:05:51 :: Network traffic verification detected no corrupted blocks
3/27/2019 13:05:51 :: Processing finished with warnings at 3/27/2019 1:05:51 PM
Screenshot example:
Image

veremin
Product Manager
Posts: 16778
Liked: 1404 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by veremin » Apr 13, 2019 11:25 am

Thanks for providing additional information, we will review the case closer next week, once we're in the office. So far it looks like unexpected situation, but let's wait till we take a thorough look at it.

jonathan.brown
Novice
Posts: 6
Liked: never
Joined: Apr 12, 2018 2:40 pm
Full Name: Jonathan Brown
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by jonathan.brown » Apr 22, 2019 8:29 pm

Hello v.eremin,

Were you able to take a closer look at this last week? Any updates?

Thanks,
Jon

tejko30
Lurker
Posts: 2
Liked: never
Joined: Feb 18, 2019 9:52 am
Full Name: Matej
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by tejko30 » Jul 15, 2019 11:47 am

Hello,

Is there any update on this?

Thanks!

oliverL
Enthusiast
Posts: 60
Liked: 6 times
Joined: Nov 11, 2016 8:56 am
Full Name: Oliver
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by oliverL » Sep 11, 2019 11:42 am

Any update on that?

veremin
Product Manager
Posts: 16778
Liked: 1404 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: SQL Transaction Log Errors labeled as Warnings

Post by veremin » Sep 11, 2019 5:17 pm

- To generate an error regarding failed SQL DB backup backup server needs to query the DBs first
- In the example above backup server didn't manage to process Guest server
- Without processing Guest server backup server cannot query the DBs
- Without querying the DBs backup server cannot provide an error regarding state of SQL DB backup (whether it was error or success)

So, the described behaviour looks expected.

Thanks!

Post Reply

Who is online

Users browsing this forum: No registered users and 8 guests