Delphix Products

  • 1.  What is the importance of V2P feature?

    Posted 02-27-2018 11:14:00 AM
    Creating a database through VDB and creating a database through V2P, both creates a database, only difference I find is VDB are Delphix managed(sync, snapshots etc) while V2P are not managed by Delphix. What is the usecase of V2P? Is it because of security or just saving space on Delphix machine? 

    #Virtualization


  • 2.  RE: What is the importance of V2P feature?
    Best Answer

    Posted 02-27-2018 11:18:00 AM
    V2P is to "hydrate" a virtual database onto another storage device so that it is a real physical database.  A common use case is to create a non-VDB for performance testing or in the case where you are creating VDB's on commodity hardware from an Exadata source (for instance) then you can put a version back onto an Exadata controlled storage.  Also useful for creating a physical database if you have migrated production to a new data centre or cloud.
    Some customers talk about the concept of a fast failover, whereby you have a fast failover to a VDB but then need to fail back to a physical database.  You can leverage the V2P capability in this kind of scenario where to establish planned downtime to fail back.
    Regards,
    Gary


  • 3.  RE: What is the importance of V2P feature?

    Posted 02-27-2018 11:18:00 AM
    Hi Anshul,

    Please refer to this article for more infos.  https://community.delphix.com/delphix/topics/delphix-v2p-capabilities

    Regards,

    Mouhssine


  • 4.  RE: What is the importance of V2P feature?

    Posted 02-28-2018 06:38:00 AM
    "V2P is to "hydrate" a virtual database onto another storage device so that it is a real physical database. "
    I might sound silly here as I am new to Delphix, do we not get a physical database when we create VDB? As when I created a VDB, I got a DB on staging machine too, so what's the difference between DB created through VDB process and V2P process?


  • 5.  RE: What is the importance of V2P feature?

    Posted 02-28-2018 05:20:00 PM
    Anshul,

    When you provision a VDB (virtual database) you get an NFS or ISCSI mountpoint on a target server,. With a set of private pointers to a shared compressed and de-duplicated copy of your source database, potentially adultered by hook scripts and masking jobs. Your private pointers take up a tiny fraction of the original database size. In effect you share the data file blocks with any other VDB provisioned from the same dSource. You can only access those data files through the Delphix Engine. It looks, smells, feels and tastes like a physical database and anything connected to it won’t be able to tell. But it’s not a physical database. When you hit the V2P button you effectively physically transport the data to the target machine file system that you point at. Those datafiles can be accessed outside the Delphix Engine as a physical database and you lose all the magical properties of a VDB. Namely bookmarking, branching, sharing, rewinding, refreshing, minuscule size and lightning fast portability.

    You have a lot to learn and wonder at, but we are glad you are here and hopefully so will you be! Welcome to the fine magic of Delphix!