Instance Cloning -- Notifications disablen?

[simonvolkwe]

Hello together,

I have a question about cloning from a LIVE instance to a DEV instance.

In this article, which describes post-clone and pre-clone activities very well, it says that I should disable notifications before cloning.(Post-Cloning Checklist - Support and Troubleshooting)

Why is that?

Since I am cloning to a dev instance where notifications cannot be sent by default, I can theoretically leave it out, right?

Thanks in advance, and if you have any experience or tips regarding cloning and what to look out for, or what is often forgotten with preserver/excluded records, please feel free to write.

Greetings

Simon

[Ankur Bawiskar]

@simonvolkwe 

In production email sending and receiving is enabled.

When you clone PROD -> DEV the email properties will be marked as True and emails might be sent out from DEV instance which is not recommended.

-> there could be active emails in email logs in PROD and if they get cloned to DEV then those emails might be sent out.

-> notifications from DEV might confuse users.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Hanna_G]

Hi @simonvolkwe 

As part of cloning it disables email sending.

A dev/test instance can send email notifications - by enabling the sending policies - best practice would be to create a shared mailbox to send the notifications to for any testing scenarios. This is why the clone process disables this. 

If you don't use emails in Dev/test environments then you don't need to re-enable post clone. 

Hope this helps!

[Dr Atul G- LNG]

Hi @simonvolkwe 

Sending emails from the Dev environment is not recommended, as it can confuse users. Also, after a clone, make sure to check that email properties in Dev are disabled, since they get copied from Prod.

[simonvolkwe]

Hello, 

Thank you for your fast replys.

So I should create a postclone script to disable this property in the source (LIVE) instance and a preclone script to enable it again after successfull cloning.

Or is this already configured by default?

Greetings

Simon