Relink a dSource after restoring the physical DB

  • 0
  • 1
  • Problem
  • Updated 3 years ago
  • Solved
We are trying to do the following:

  1. Restore a SQL DB onto a server from a production backup.
  2. Performing some cleardown of data via scripts
  3. Creating a dSource from this DB and allowing Devs to create VDBs
  4. Once a week, restore the DB again from production backup and perform the cleardown again.
We are having trouble with 4.
I can unlink the dSource fine and restore the DB on the SQL server (and take a backup for delphix)....but I cannot link that dSource back to the restored this something that should be possible? 

I'm using the CLI to relink but it's saying the dSource already exists.  This is now unlinked so I can't even delete it (and probably wouldn't be able to anyway due to VDBs hanging off it).

Basically we are trying to provide a cut down version of our large production DB for the dev teams but provide an up to date copy each week.
Photo of Mark Hayter

Mark Hayter

  • 766 Points 500 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Neal Stack

Neal Stack, Employee

  • 3,502 Points 3k badge 2x thumb
Official Response
Hi Mark,

Do you ever see a message like the following?
The recovery fork GUID "771A33E3-454E-4117-9F7D-A725CE3xxxxx" of the provided backupset does not match recovery fork GUID "7B7BA57C-74D6-47BC-8641-2CEB24Fxxxxx" of dSource "aceFT".
Delphix uses the database GUID as a way of identifying the database. If there is a change in the recovery fork GUID Delphix no longer feels it is the same database as it has been recovered from a backup.

If the development environment is refreshed from the production environment frequently (via LOAD DATABASE ...), you can:
  • Unlink the dSource
  • Rename the dSource
  • Link a new dSource
  • Any VDBs provisioned from the remaining dSource will remain
Doing this frequently will start to consume extra space in Delphix.

There is an outstanding feature request called "MSSQL Source Continuity" that would avoid the unlink/link. If I have correctly described the issue you are facing, you may want to mention to your account representative that you are interested in this feature. The more customers we have interested in a feature, more weight is added to the request.