Veeam B&R is unsuitable for use in multi-tennancy/DRaaS

[unsichtbarre]

We love Veeam! Don't get me wrong, but in 2015 clients are demanding access to the Veeam console that manages their replication.

I have just received word from Veeam support (Case # 00971924) that, in order to function, the vSphere permissions Veeam requires need to propagate from the vCenter or Datacenter level. What that means is that any user accessing the Veeam console will have access to every LUN/VMFS Volume/Resource Pool/ ESXi Host/Network in the entire vCenter!

With a non-propagating permission based on this document: http://veeampdf.s3.amazonaws.com/guide/ ... ssions.pdf we are able to allow clients access through the vSphere Client(s) where they can manage their and only their resources. Veeam will, however, not function unless that same permission is allowed to propagate!

That is, quite simply, a deal-breaker for any customer requiring access to Veeam as DRaaS/SaaS! We are actively seeking solutions or advice.

THX
-J

[Gostev]

DRaaS framework is coming in v9 with Cloud Connect Replication
See here for more info > http://go.veeam.com/v9