Delphix Products

Expand all | Collapse all

Migrate dsource from engine1 to engine2

  • 1.  Migrate dsource from engine1 to engine2

    Posted 06-02-2017 05:33:00 PM
    I see that there is an option to migrate vdb from one environment to another environment. But, is there a way to migrate dSource that is created in Engine1 to another delphix engine-2?
    We are using replication option to bring a dsource copy from engine1 to engine2 but we don't want to keep a copy in engine1. dSource sync will not work if we remove a copy from source engine. 
    Please suggest

  • 2.  RE: Migrate dsource from engine1 to engine2

    Posted 06-02-2017 09:00:00 PM

    This is a pretty common operation, usually for the purpose of switching a dSource from an Oracle DataGuard primary to a standby, or from one standby to another standby, or from a standby to the primary.  Please bear in mind that it is necessary that a detached dSource can only be attached to a source database with the same Oracle DBID.

    There is a step-by-step walk-through in a "cookbook" recipe in the Command-Line Interface (CLI) section of the documentation HERE.  In this recipe, the CLI commands to first detach a dSource are described;  this can also be done from the graphical interface using the "unlink dSource" icon.  Then, the CLI commands to next re-attach the dSource to another source database in another source environment are described.

    Whenever using the CLI, it is always helpful to remember to make heavy use of the tab-completion and tab-list-of-values functionality, similar to the UNIX/Linux BASH shell, in addition to knowing that

    Hope this helps!


  • 3.  RE: Migrate dsource from engine1 to engine2

    Posted 06-02-2017 11:30:00 PM
    Hi Viswas-

    I believe in your example, if the dSource is replicated from Engine1 to Engine2, then all you should need to do is detach (unlink) the source on Engine1, and fail over the namespace on Engine2, then Enable, which will cause Engine2 to start syncing with the configured source.  detachSource and attachSource operations are relevant if you are moving the source database to another host, but remaining on the same Engine, which I don't think is your end goal.  

    However, the detachSource operation IS relevant on Engine1 once the failover occurs, so you do not have two engines attempting to sync data from the same host (unless this is what you want).  You can also choose to simply disable the dSource, but if the intention is for Engine1 to no longer sync data at any point, then the detachSource (unlink) is probably most appropriate.

    Any existing VDBs provisioned from the source on Engine1 are unaffected by this operation, and new VDBs can also be provisioned from the dSource on Engine1 (with consideration for data retention, etc).

    The following documentation links may also be of value.