Update2 replication warning Failed to set storage profile

[VladV]

Hi,

We recently update VBR to Update 2 and immediately notice the following warning for all our replication jobs:

15/05/2017 14:23:10 :: Failed to set storage profile Default to disk [xxx_replica01:2000]

I am going to open a case and post the Case # here.

Thanks

LE: Case #02155907

[foggy]

Yes, please investigate with the help of support. Logs analysis is required.

[VladV]

I received a solution from support:

Code: Select all

Name: SupportPbmProfiles 
Type: REG_DWORD 
Value: 0 
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\ 

That did the trick.

[veremin]

Be aware that the provided key disables storage policy support altogether. So, if that is not something you want, kindly, re-open a case and let support team find out the root cause of the experienced problem. Thanks.

[masonit]

Hi

We are getting the same warnings after upgrade to u2.

\Masonit

[foggy]

Magnus, please let our engineers investigate.

[JoshuaPostSAMC]

I didn't open a support case and was only temporarily replicating something that I'm done with now, but I also started seeing this after upgrading to Update 2

[foggy]

Vlad's case is under investigation and gets escalated to track down the reasons of the warnings (which did exist even before, btw, but are not longer suppressed after the update).

[VladV]

Hey guys,

Just finished going back and forth with support. Unless there was a communication problem between me and support, it seems that this is a bug in Veeam in detecting profile-driven storage. You can use the reg key above to suppress it.

It should be fixed in the following releases.

Cheers,
Vlad

[unsichtbarre]

I have spoken with Veeam Support this morning (Case # 02250826) and they kindly provided me a hotfix. As a Veeam service provider, we run several Veeam servers against our vCenter 6.0 (VCSA), and I sought a more elegant solution then applying a hotfix to each Veeam instance.

The solution is, however, very simple. The granular permissions defined in: https://www.veeam.com/veeam_backup_9_0_ ... ons_pg.pdf do not contain permissions for Profile-driven Storage.

I added the following privileges to my Veeam Role, and now the jobs function without error or issue:

• Profile-driven storage update
• Profile-driven storage view

[bauke_plugge]

Hi All,

just encountered the same issue while replicating some VM's. I have contacted Veeam support about this and they acknowledge that this is a bug in the current release and that it will be fixed in version 9.5 update 3.


kind regards
Bauke

[paul_naglic]

@unsichtbarre, can you tell me how you were able to add those privileges? I am not seeing anything for those? All I see for Roles is the basics : Administrator, Operator, etc.

[unsichtbarre]

This is applied in vCenter.

In vCenter go to: Home > Roles

locate the role that applies to your Veeam user

add a checkbox in the item: Profile-driven storage

[Iain_Green]

Hi,

Running Update 3 and seeing this error, did a goolge and landed hear...as always

Question?

What is profile driven storage??

Also I am logging a case!

[ChrisGundry]

Seems that quite a long time has passed, this is still an issue these rights are still missing from the document. We followed it to configure backups with restricted access and the replication jobs are failing with this error.

Can someone get the document updated to contain this info please?

[Vitaliy S.]

I will ask our TW team to update it asap.

[l.scotti]

Seems that quite a long time has passed, this is still an issue these rights are still missing from the document. We followed it to configure backups with restricted access and the replication jobs are failing with this error.

Can someone get the document updated to contain this info please?

https://helpcenter.veeam.com/docs/backu ... sions.html