Delphix Products

Hi everybody,

I have a question about VDB refreshs: 

When we start a refresh job and we get an error on a hook script localized in the post refresh section, does Delphix rollbacks the refresh or not?

Is there a documentation where i can find this information?

Thanks.

Hi everybody,

I have a question about VDB refreshs: 

When we start a refresh job and we get an error on a hook script localized in the post refresh section, does Delphix rollbacks the refresh or not?

Is there a documentation where i can find this information?

Thanks.

Hello,

If the hook fails, the VDB should not be accessible ( https://cd.delphix.com/docs/latest/sql-server-hook-operation-notes ):

Some customers do masking in their hooks and would not want their VDB provision/refresh to succeed and allow unmasked data out into the wild if the hook failed. There is a new feature request to make this configurable ( IDEA-1173 - Add switch to hooks to still allow provision to complete if hook fails ).

Once it has failed to provision/refresh Delphix won't allow control of it (start/stop/enable/disable).

There are other various feature requests like (IDEA-1855 - Provide ability for customer to mark a failed Oracle VDB provision/refresh as good) which would allow you to mark the VDB refresh as good despite the job failure. Or this one (IDEA-3187 - Provide an Option to Allow Auto Refresh of Disabled VDB (via VDB Refresh Policy)

) asks for a mechanism to try refreshing again after a failed refresh. It might make sense for transient issues to try the refresh again.

Often there are non-transient issues (password expired, memory shortages, etc.) that need to be fixed before trying again.

I hope this helps to answer your question.

Thanks,

Neal

Hi everybody,

I have a question about VDB refreshs: 

When we start a refresh job and we get an error on a hook script localized in the post refresh section, does Delphix rollbacks the refresh or not?

Is there a documentation where i can find this information?

Thanks.

Hello,

If the hook fails, the VDB should not be accessible ( https://cd.delphix.com/docs/latest/sql-server-hook-operation-notes ):

Some customers do masking in their hooks and would not want their VDB provision/refresh to succeed and allow unmasked data out into the wild if the hook failed. There is a new feature request to make this configurable ( IDEA-1173 - Add switch to hooks to still allow provision to complete if hook fails ).

Once it has failed to provision/refresh Delphix won't allow control of it (start/stop/enable/disable).

There are other various feature requests like (IDEA-1855 - Provide ability for customer to mark a failed Oracle VDB provision/refresh as good) which would allow you to mark the VDB refresh as good despite the job failure. Or this one (IDEA-3187 - Provide an Option to Allow Auto Refresh of Disabled VDB (via VDB Refresh Policy)

) asks for a mechanism to try refreshing again after a failed refresh. It might make sense for transient issues to try the refresh again.

Often there are non-transient issues (password expired, memory shortages, etc.) that need to be fixed before trying again.

I hope this helps to answer your question.

Thanks,

Neal

Hi everybody,

I have a question about VDB refreshs: 

When we start a refresh job and we get an error on a hook script localized in the post refresh section, does Delphix rollbacks the refresh or not?

Is there a documentation where i can find this information?

Thanks.