SQL Backups and 9.5U3

[bjesteadt]

I have already applied the workaround, but with no success.

As I mentioned, I have no access to the SQL databases or instance to modify the permissions.

[Gostev]

The patch provided in the KB article does solve the issue, so please work with our technical support to verify that you have applied it correctly.
If your engineer can't find the reason why it does not work for you, he will escalate to a higher support tier for further investigation.

[unsichtbarre]

Hi all-
I am a big fan of Veeam but right now I couldn't be more disappointed. Veeam Backup & Replication 9.5.0.1922 (Update 3a) is completely unacceptable due to the way it changes the required SQL Permissions required for Application Aware Image Processing. There are two KB articles (KB2447 and KB2689) and a long thread here on the communities regarding the issues and fix(es) possible, but that's not actually the problem.

My company is a Veeam Service provider. That means we don't necessarily have access to our customers AD or SQL instances. The problem is that, without asking or notifying, Veeam has now required that I contact each and every customer and request a support session where we will have to:

A. Modify AD and/or Group Policy
B. Run queries against their SQL Server instances
C. Connect to their Veeam proxy instance to replace files installed by the update

Not only is this intrusive, but administrators tend to be highly protective of their AD and SQL Databases. Just the fact that I need to ask for 'local' access to resources (whether that be the Proxy or SQL database) is enough to raise questions on the part of customers who simply want their backup and DR solution to function silently.

We need a hotfix that will allow automatic update of our Veeam Proxies remotely, and we need it ASAP!

At the moment, Veeam no longer just works!

[Gostev]

Hello, you should contact support for any hot fixes, or if you need help deploying them. Thanks!

[unsichtbarre]

Gostev,

#1, I did not add my post to this thread (it was MERGED) because it is not about the fix - it is about the irresponsible nature which Veeam allowed 3a intio customers hands. Especially Service Providers.
#2. I have sought a hotfix via ticket 03199036 - with no ETA at this time

[Gostev]

Hello, your post was merged into this thread to prevent duplicate discussions, because the topic of "the irresponsible nature which Veeam allowed 3a into customers hands" has already been discussed here earlier. And I too shared my own frustration about this earlier in this thread.

[Regnor]

Regarding the Hotfix; https://www.veeam.com/kb2689

I've just noticed that the Veeam console distinguishes between U3a and U3a+Hotfix. Connection will only work to one of Veeam instance and the other will try to update the console.
Also when installing Enterprise Manager on U3a+Hotfix, the setup installed U3a and reverted the hotfix.

Are those known issues?

[foggy]

Connection will only work to one of Veeam instance and the other will try to update the console.

I would expect this, since Veeam B&R tries to automatically update all its remote components.

Also when installing Enterprise Manager on U3a+Hotfix, the setup installed U3a and reverted the hotfix.

Seems like setup rewrites some of the hotfix files. I believe you can install hotfix once again after that.

[Regnor]

I wasn't sure about that as I thought the hotfix changes only the SQL behaviour.
I have now installed the hotfix on both installations so the console works on both.

[foggy]

Hotfix replaces a bunch of Veeam B&R files that are used for other tasks as well. For proper operation, all components need to be on par in terms of their build numbers.

[jrbaumann]

Just to verify, i should backup the files listed in KB2689 on the backup server AND all 9 of my proxy servers then replace the files with the files in the hotfix on each of them?


JB

[foggy]

...backup server AND all 9 of my proxy servers...

Guest interaction proxies, not backup proxies.

[tom_nl]

Will the hotfix be included in update 4?

[wishr]

Hi Tom,

Sure thing, the hotfix will be a part of the B&R U4 release. Just in general all the public hotfixes are usually included into nearest releases as well as in further ones.

Thanks,
Fedor

[quintero]

Hi,

I have the following issue when backing up VMs with SQL servers on them:

[TDB]Unable to update SQL backupset for instance : Code = 0x80040e09

I am not the database admin so am not familiar enough with SQL. I have seen a blog post stating that the user with the relevant permissions should be added to the 'logon as batch user' and then as sysadmin on the SQL server itself but was wondering if there was any other way that this issue could be rectified

Many thanks!

[DGrinev]

Hey Gareth,

You will find a plenty of useful information about the issue in this big thread.
Please review the KB article mentioned in the posts above, it should solve the issue. Thanks!

[mike.r]

Hi,

I have installed the Hotfix and it works as described.
SQL Database backup is now successful again and the error message is now an "info message".
So far so good.
But what does the message "Transaction logs backup will not be possible..." mean exactly ?
Is the transaction log of the SQL Database backuped or not ?
And did Veeam truncate the transaction log (just as it did before Update 3a) or not ?

[Gostev]

This talks about transaction log backup functionality specifically
https://helpcenter.veeam.com/docs/backu ... tml?ver=95

Log truncation functionality will not be affected.

[hwelvaar]

Is this fixed in 9.5 Update4 ?
(or is the hotfix for U3 integrated in U4) ?

[wishr]

Hi Hwelvaar,

As I have already mentioned on the previous page, the hotfix is included in the U4 release.

Regards,
Fedor