-
110 Points
- exicted
Posted 7 months ago
-
626 Points
This way you know when a rep' job is running (because the script started it) and can poll for a successful completion before running the refresh.
-
5,244 Points
Hi,
You have to take a look from the end-to-end approach to
choose the solution you will go with.
- You call control all the path from triggering replication
to refresh the VDB on receipt (the easy one and you have the full control on
all path steps, you can scale/change it as you need)
- The replication process is already automated by delphix
cron from admin console or other scheduler utility; In this case you have to
use API and check the status of last replication based on the result you decide
to refresh the receipt VDB or not.
But i still have one question normally VDB will be used by a
dev profile user automating it's refresh can destroy the ongoing job, at least
if it's also used as master on the receipt engine
Regards,
Mouhssine
-
110 Points
Ans: Actually we created a Master Copy for which no one is going to connect it.. we create the child VDB from that for all our clients. they will use that.
Related Categories
-
Delphix Virtualization
- 118 Conversations
- 5 Followers
-
API/Python/Open-Source Solutions
- 190 Conversations
- 3 Followers
Nithin Rayilla