-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 11, 2017 7:15 am
- Full Name: Ciska Marais
- Contact:
Back ends with a warning - Failed to truncate SQL server tra
Hi there
We are in the process of implementing VEAAM on all our MS SQL servers. Each host has a number of instances on which the backup completes successfully, except for this one instance where we are seeing the following warning:
Failed to truncate SQL server transaction logs for instances: MSSQLSERVER. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
In the log file the following is logged:
Failed to truncate SQL server transaction logs for instances: MSSQLSERVER. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (System.Runtime.InteropServices.COMException)
Error at VeeamEndpointSysUtilsDllLib.IVeeamEpSqlMethodsProvider.TruncateSqlLogs(String sqlLogin, String sqlPwd)
Error at Veeam.EndPoint.SysUtils.CEpGuestSubsystemSqlMethods.TruncateSqlLogs(CCredentials creds)
Error at Veeam.EndPoint.CSnapshotGuestAppProcessor.TruncateSqlLogs(CEpGuestSubsystem guestSubsystem)
Has anybody come across such an error and what did you do to resolve this?
We are running the VeaamAgent for Windows 2.-.0.700.
We are in the process of implementing VEAAM on all our MS SQL servers. Each host has a number of instances on which the backup completes successfully, except for this one instance where we are seeing the following warning:
Failed to truncate SQL server transaction logs for instances: MSSQLSERVER. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
In the log file the following is logged:
Failed to truncate SQL server transaction logs for instances: MSSQLSERVER. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (System.Runtime.InteropServices.COMException)
Error at VeeamEndpointSysUtilsDllLib.IVeeamEpSqlMethodsProvider.TruncateSqlLogs(String sqlLogin, String sqlPwd)
Error at Veeam.EndPoint.SysUtils.CEpGuestSubsystemSqlMethods.TruncateSqlLogs(CCredentials creds)
Error at Veeam.EndPoint.CSnapshotGuestAppProcessor.TruncateSqlLogs(CEpGuestSubsystem guestSubsystem)
Has anybody come across such an error and what did you do to resolve this?
We are running the VeaamAgent for Windows 2.-.0.700.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Back ends with a warning - Failed to truncate SQL server
Hi Ciska,
First: Welcome to the forums!
Second: Did you look at the requirements for that instance? These are the requirements (bottom of the page) https://helpcenter.veeam.com/docs/backu ... tml?ver=95. I know this is for VBR but I can't find the page for VAW at this moment. But they are the same.
If those are OK, please log a support case. Post the support case ID here and keep us informed on the follow-up
Thanks
Mike
First: Welcome to the forums!
Second: Did you look at the requirements for that instance? These are the requirements (bottom of the page) https://helpcenter.veeam.com/docs/backu ... tml?ver=95. I know this is for VBR but I can't find the page for VAW at this moment. But they are the same.
If those are OK, please log a support case. Post the support case ID here and keep us informed on the follow-up
Thanks
Mike
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 11, 2017 7:15 am
- Full Name: Ciska Marais
- Contact:
Re: Back ends with a warning - Failed to truncate SQL server
I have opened a support case - 02307299.
Will update the forum with solution.
Will update the forum with solution.
-
- Veteran
- Posts: 389
- Liked: 54 times
- Joined: Sep 05, 2011 1:31 pm
- Full Name: Andre
- Contact:
[MERGED] VAW SQL Server TRN processing on VBR Server
Good Day
Have a new physical VBR Server.
First installed SQL Server Express 2019, then installed VBR 10a and confgured it to use SQL Express 2019.
VAW Job does Backup OS from VBR Server. This works well, expect for Application processing of the SQL DB:
10.09.2020 10:28:19 :: System (C:) (446.5 GB) 1.1 GB read at 792 MB/s [CBT]
10.09.2020 10:28:27 :: Finalizing
10.09.2020 10:28:27 :: Truncating transaction logs
10.09.2020 10:28:28 :: Unable to truncate SQL server transaction logs. Details: Failed to truncate SQL server transaction logs for instances: SQLEXPRESS. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
10.09.2020 10:29:32 :: Incremental backup created
10.09.2020 10:29:32 :: Collecting recovery media files
Checked the Account Settings in SQL. Account has sysadmin rights. Also i can see in the sql logs that sql db backup is successful. no entry about trn errors.
any idea how this can be fixed?
Thanks
Have a new physical VBR Server.
First installed SQL Server Express 2019, then installed VBR 10a and confgured it to use SQL Express 2019.
VAW Job does Backup OS from VBR Server. This works well, expect for Application processing of the SQL DB:
10.09.2020 10:28:19 :: System (C:) (446.5 GB) 1.1 GB read at 792 MB/s [CBT]
10.09.2020 10:28:27 :: Finalizing
10.09.2020 10:28:27 :: Truncating transaction logs
10.09.2020 10:28:28 :: Unable to truncate SQL server transaction logs. Details: Failed to truncate SQL server transaction logs for instances: SQLEXPRESS. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
10.09.2020 10:29:32 :: Incremental backup created
10.09.2020 10:29:32 :: Collecting recovery media files
Checked the Account Settings in SQL. Account has sysadmin rights. Also i can see in the sql logs that sql db backup is successful. no entry about trn errors.
any idea how this can be fixed?
Thanks
-
- Veteran
- Posts: 1143
- Liked: 302 times
- Joined: Apr 27, 2020 12:46 pm
- Full Name: Natalia Lupacheva
- Contact:
Re: Back ends with a warning - Failed to truncate SQL server tra
Hi Andre,
I've moved your post to the existing thread.
Please open a support case for our Support team to be able to analyse your logs.
Thanks!
I've moved your post to the existing thread.
Please open a support case for our Support team to be able to analyse your logs.
Thanks!
-
- Veteran
- Posts: 389
- Liked: 54 times
- Joined: Sep 05, 2011 1:31 pm
- Full Name: Andre
- Contact:
Re: Back ends with a warning - Failed to truncate SQL server tra
Hi Natalia
Thanks, i have opened a case #04381908
Best Regards
Thanks, i have opened a case #04381908
Best Regards
-
- Veteran
- Posts: 389
- Liked: 54 times
- Joined: Sep 05, 2011 1:31 pm
- Full Name: Andre
- Contact:
Re: Back ends with a warning - Failed to truncate SQL server tra
Problem solved by Veeam Support, thanks
Solution: add the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\UseSqlNativeClientProvider (DWORD type, value 1) on the Agent computer, and restart the Veeam Agent for Windows
Solution: add the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\UseSqlNativeClientProvider (DWORD type, value 1) on the Agent computer, and restart the Veeam Agent for Windows
-
- Veteran
- Posts: 1143
- Liked: 302 times
- Joined: Apr 27, 2020 12:46 pm
- Full Name: Natalia Lupacheva
- Contact:
Re: Back ends with a warning - Failed to truncate SQL server tra
Hi Andre,
thank you for sharing the solution!
Cheers!
thank you for sharing the solution!
Cheers!
Who is online
Users browsing this forum: No registered users and 35 guests