question

MikeLeger-3427 avatar image
0 Votes"
MikeLeger-3427 asked ErlandSommarskog commented

SQL Jobs on SQL Server 2014 seem to fail while Veeam backup runs overnight. Task shows successfull, however job does not run.

Some overnight SQL Agent jobs on Guest machine fail when Veeam Backup is running.
This is not 100% of the time, but most of the time.

However during the time, when checking windows event log we do see some volsname event id 25 errors that only seem to show up during the time veeam backup is running.

It is triggering on the G and F drives, which are the main SQL DB Files

Unable to find any other alarms/errors/alerts that point to an issue

EventLog: 5/4/2021 12:47:33 AM & 5/2/2021 4:17:17 AM & 4:18:52 AM
The shadow copies of volume F: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
The shadow copies of volume G: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

SQL Agent Log:
Executed as user: IRDEV\svc_sqlserver. The step succeeded.
The job succeeded. The Job was invoked by Schedule 1125 (15 minutes). The last step to run was step 1 (Run Sproc).

sql-server-general
· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Maybe it is because I don't know Veeam, but I don't really understand.

You say that "task show successul, however job does not run". How do you conclude that the job does not run? What sort of job is this? What job type is it?

0 Votes 0 ·

The job just imports some data from another DB into a table in DB [SERVER1.DB1 -> server2.db2], it is not a replication, but its just some data. it runs every 15 minutes.
the issue here is, there are no job logs for the time that veeam runs. and in the morning the job has to be manually started before it will kick off again.

0 Votes 0 ·

You did not say what type of jobs this is. T-SQL job step? CmdExcc= SSIS Package?

You say that there are no job logs. What logs are you referring to?

You say that the job has to be started manually in the morning?

Where is reported that the job has been executed successfully?

I think it could help to clarify to include some screenshots.

0 Votes 0 ·
Show more comments

Hi MikeLeger-3427,
How are things going on? Was your issue resolved?
If not, please don't hesitate to let us know and tell us the more information in order to provide further help.
If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
Best Regards,
Amelia

0 Votes 0 ·
AmeliaGu-msft avatar image
0 Votes"
AmeliaGu-msft answered

Hi MikeLeger-3427,
Was your issue resolved?
If not, please share us more information about your issue. And also suggest you open a thread in the Veeam forum to get more help.
Bet Regards,
Amelia


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MikeLeger-3427 avatar image
0 Votes"
MikeLeger-3427 answered ErlandSommarskog commented

what other information could i provide here?

I have a active open case with Veeam, who do not understand the issue.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

As I said earlier, it could help to see some screen shots of the job definition and the Agent history so that we get a better understanding of the issue.

0 Votes 0 ·