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:
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.