Correct MS SQL backup job.

[staun]

I am trying to setup a backup job for our MS SQL and it seems to be working, but a bit confused about the report I get.

I followed this guide : https://helpcenter.veeam.com/evaluation ... store.html

Configured two jobs - One Full backup og the entire VM - being ApplicationAware (SQL - Truncate Logs) and another job again with ApplicationAware (Backup logs periodically)

I can restore but what about all these errors in the mail-report?

Code: Select all

Start timeEnd timeDurationDelayProtectedUnprotectedReadTransferredDetails
10:01:22 PM10:16:22 PM0:01:03 0:00:00 225.9 MB1.7 MB
10:16:22 PM10:31:22 PM0:00:59 0:00:00 2211.2 MB3.2 MB
10:31:22 PM10:46:23 PM0:00:32 0:00:00 224.4 MB1.2 MB
10:46:23 PM11:01:23 PM0:00:40 0:00:00 226.9 MB2.0 MB
11:01:23 PM11:16:23 PM0:00:35 0:00:00 227.1 MB2.1 MB
11:16:23 PM11:31:24 PM0:00:33 0:00:00 2210.1 MB2.8 MB
11:31:24 PM11:46:24 PM0:00:33 0:00:00 224.4 MB1.2 MB
11:46:24 PM12:01:24 AM0:00:52 0:00:00 229.9 MB2.9 MB
12:01:24 AM12:16:24 AM0:07:27 0:00:00 225.7 MB1.7 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
12:16:24 AM12:31:25 AM0:00:45 0:00:00 2210.7 MB3.1 MB
12:31:25 AM12:46:25 AM0:08:45 0:00:00 225.0 MB1.4 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
12:46:25 AM1:01:26 AM0:00:43 0:00:00 226.8 MB1.9 MB
1:01:28 AM1:16:28 AM0:01:07 0:00:00 225.7 MB1.7 MB
1:16:28 AM1:31:28 AM0:00:40 0:00:00 2211.4 MB3.2 MB
1:31:29 AM1:46:29 AM0:08:03 0:00:00 224.6 MB1.2 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
1:46:30 AM2:01:32 AM0:02:12 0:00:00 227.2 MB2.0 MB
2:01:42 AM2:16:42 AM0:05:03 0:00:00 228.2 MB2.4 MB
2:16:42 AM2:31:42 AM0:01:16 0:00:00 2210.5 MB3.0 MB
2:31:42 AM2:46:42 AM0:00:39 0:00:00 224.3 MB1.2 MB
2:46:42 AM3:01:43 AM0:00:44 0:00:00 227.8 MB2.2 MB
3:01:43 AM3:16:43 AM0:00:55 0:00:00 226.0 MB1.8 MB
3:16:44 AM3:31:44 AM0:07:49 0:00:00 2210.7 MB3.1 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
3:31:44 AM3:46:45 AM0:00:42 0:00:00 224.9 MB1.4 MB
3:46:45 AM4:01:45 AM0:02:26 0:00:00 226.9 MB2.0 MB
4:01:46 AM4:16:54 AM0:00:56 0:00:00 225.8 MB1.7 MB
4:16:54 AM4:31:54 AM0:07:18 0:00:00 2211.6 MB3.3 MBFailed to save SQL Server transaction log backup file for database model to repository Failed to connect clients
4:31:54 AM4:46:54 AM0:12:20 0:00:00 224.2 MB1.1 MBFailed to save SQL Server transaction log backup file for database model to repository Failed to connect clients
4:46:55 AM5:01:55 AM0:07:46 0:00:00 228.1 MB2.3 MBFailed to save SQL Server transaction log backup file for database model to repository Failed to connect clients
5:01:55 AM5:16:55 AM0:00:39 0:00:00 226.5 MB1.9 MB
5:16:55 AM5:31:56 AM0:07:38 0:00:00 2211.2 MB3.4 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
5:31:56 AM5:46:56 AM0:00:39 0:00:00 224.6 MB1.3 MB
5:46:56 AM6:01:58 AM0:00:46 0:00:00 228.7 MB2.6 MB
6:01:58 AM6:16:58 AM0:00:39 0:00:00 225.1 MB1.5 MB
6:16:58 AM6:31:58 AM0:00:44 0:00:00 2210.6 MB3.0 MB
6:31:58 AM6:46:59 AM0:00:48 0:00:00 224.9 MB1.4 MB
6:46:59 AM7:01:59 AM0:07:40 0:00:00 227.5 MB2.1 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
7:01:59 AM7:17:00 AM0:07:23 0:00:00 225.1 MB1.5 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
7:17:00 AM7:32:00 AM0:07:34 0:00:00 2211.5 MB3.2 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients
7:32:00 AM7:47:00 AM0:07:42 0:00:00 224.4 MB1.2 MBFailed to save SQL Server transaction log backup file for database model to repository Failed to connect clients
7:47:00 AM8:02:00 AM0:08:12 0:00:00 227.9 MB2.3 MBFailed to save SQL Server transaction log backup file for database VirtualManagerDB to repository Failed to connect clients

[veremin]

What's your support case number? It's requested by the forum`s rules while posting about technical issues. Thanks.

[staun]

Sorry, must have missed that reading the FAQ. I will create a support ticket at veeam support instead. - Just wanted to ask in a open forum about the setup before I created at support ticket.

[DerOest]

Sounds like you are doing it wrong - you should only have one job? At least, that's how we do it.
Full/Incremental backup at night, and the job will also start the periodic transaction log shipping throughout the next 24 hours.

Periodic transaction log backups will also truncate the logs (see screenshot Point 10 https://helpcenter.veeam.com/evaluation ... store.html).

[veremin]

Sorry, must have missed that reading the FAQ.

And I must have the line regarding two backup jobs.

DerOest is correct here, you need to have only one backup job with SQL periodic logs backup enabled. Try to stick with single job and see how it goes for you.

[staun]

Thanks guys,

Just reconfigured my SQL job, so I now only have one job in my backup job list and I can now see two jobs running (I may have mixed things up before when I saw to jobs in the running job-list)

I will see how it goes the next couple of days.

[veremin]

Good to know that you are up and running now. Keep us posted about how well it goes for you.

[staun]

Back on job again.

Our MS SQL job looks much better now - the log-backup shows no errors now.

Code: Select all

Start timeEnd timeDurationDelayProtectedUnprotectedReadTransferredDetails
9:01:05 PM9:16:05 PM0:13:46 0:00:00 2213.0 MB3.9 MB
9:16:05 PM9:31:05 PM0:06:38 0:00:00 223.6 MB986.8 KB
9:31:05 PM9:46:05 PM0:00:32 0:00:00 226.5 MB1.8 MB
9:46:05 PM10:01:05 PM0:00:38 0:00:00 225.1 MB1.4 MB
10:01:05 PM10:16:06 PM0:00:37 0:00:00 227.8 MB2.3 MB
10:16:06 PM10:31:06 PM0:00:44 0:00:00 229.2 MB2.7 MB
10:31:06 PM10:46:07 PM0:00:37 0:00:00 225.4 MB1.5 MB
10:46:07 PM11:01:07 PM0:00:39 0:00:00 225.6 MB1.5 MB
11:01:07 PM11:16:07 PM0:00:38 0:00:00 229.8 MB2.9 MB
11:16:07 PM11:31:08 PM0:00:40 0:00:00 226.7 MB1.8 MB
11:31:08 PM11:46:08 PM0:00:40 0:00:00 225.8 MB1.6 MB
11:46:08 PM12:01:08 AM0:00:39 0:00:00 228.7 MB2.7 MB
12:01:08 AM12:16:08 AM0:00:38 0:00:00 227.2 MB2.1 MB

Thank you very much for the assistance.

[veremin]

Great, so once there is only one backup job taking care about SQL VM transaction logs, everything starts working as expected.

Should other help be needed, don't hesitate to contact us.