Case # 02333855:
Dear Ladies and Gentlemen,
on 29.09 we have updated our vSphere Client Version from 6.0. to 6.5.0.10000.
Since than we cannot backup the SQL transaction logs.
Veeam Support provided us a workaround to set a server as logshipper which is in the same subnet as the SQL Server. Unfortunately we
cannot implement this solution.
Do you have any further workaround.
Would be possible from R&D to provide us a fix for this issue?
Please let me know if you need a further information.
Thanks in advance.
Best Regards,
Dimitar Lazarevski
Dimitar Lazarevski
Infrastrukture Counsultant
Infrastruktur und Operation Services
Scheer GmbH | Bismarckallee 17 | 79098 Freiburg
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Oct 11, 2017 8:31 am
- Full Name: Dimitar Lazarevski
- Contact:
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: vSphere 6.5 - SQL Transaction logs ERROR
Hi Dimitar, at this stage it is not clear where the issue is and whether it exists actually. Please continue looking into this with the help of support engineer. Simply updating the vSphere Client shouldn't affect logs backup, but if you've upgraded vSphere itself, there could be issues if VIX was used to connect to the guest OS, since vSphere uses WEB API instead.
Who is online
Users browsing this forum: micoolpaul and 71 guests