Note: This conversation was created from a reply on: Tip of the Day: Using the CLI to Migrate an Oracle VDB.
You can definitely do this via the CLI or the GUI, check out https://docs.delphix.com/display/DOCS43/Migrating+a+SQL+Server+VDB for both procedures!
I found this link:
I tried reattaching the source, but I am confused on what to put for some of the fields.
Like pptRepository, what goes in that field?
The pptRepository field needs to be set to the name of the SQL instance on the staging server. You can find a detailed description on how to run these CLI commands on our help article "CLI Cookbook: Detaching and Attaching a SQL Server dSource".
I hope this helps. Please let me know if you have any questions.
I did a quick test of backing up a source database and restoring it to the new server and then attempting the re-attach and found that it failed because the "Recovery Fork GUID" were different.
What I found though is that if you create the target database on the new server using the V2P functionality in Delphix that the "Recovery Fork GUID" is the same between the original Source and the new database.
Would you foresee any problems doing the following:
1) Begin downtime on current source and remove all users
2) Take Snapshot of current source
3) Create source database on target new server using V2P of most snapshot taken in step 2
4) Unlink dSource
5) Relink dSource to source on new server using CLI
Do you think that would work?