Gostev wrote:From the architecture perspective, I don't like that VVols are not transportable. Basically, all metadata is stored inside vCenter Server, in the VASA 2.0 provider database. This means that if you lose vCenter, or get some unrecoverable database corruption - you will also lose access to all of your data. Forever! Because you can't just plug your VVols storage into another host to get to your data, such as the case with VMFS. Most people probably don't even realize this limitation, they take it for granted that their storage will be readable by any vSphere host (because this is the case with VMFS, and basically any other file system).
lukejf wrote:Hey Guys
We are about to move our new Nimble Storage into productions and trying to work out if we should use VVOls or not. I read on a feature request that VVOLS's and veeam using native storage snapshots does not work / is not supported. Could someone please elaborate on this one
Users browsing this forum: Google [Bot], Google Feedfetcher and 1 guest