New non-prod environment setup

[Mark C_]

We've recently acquired another non-prod instance to use and I was looking for some best practices to set this up.

Could I confirm If I can simply:
1. Request a clone from our prod instance to the new one ?
2. Set-up the remaining items e.g. email settings, ldap, sso, etc. ?

Would appreciate your guidance.

Thanks,
Mark

[Saurabh Gupta]

For point 1. yes you can easily do this.
Point 2. You need to put a test email id to send outbound email. (on test email id)
SSO : you need to configure with the help of team responsible for sso (F5 or Azure)
ldap: I don't think is required in non prod.

If my answer replied your question please mark appropriate response as correct so that the question will appear as resolved for other users who may have a similar question in the future.

Regards,
Saurabh

[Michael Jones -]

Typically speaking, yes, you would request a clone from PROD (or another DEV instance), with the caveat that if you can only access PROD via SSO then you would need to preserve a local account with admin to ensure you can still access the instance. You would also most likely want to setup table exclusions for things like the task table as you probably would not want those records copied to your new instance.

That will generally cover about 80% of what you need. The rest (such as what you mention) would need to be done manually on the instance itself. SSO, LDAP, Mid-Servers, instance specific system properties, etc. 

Keep in mind that if you do perform a clone and find you either missed something you wanted or needed to exclude / preserve, you always have the option to roll back the clone and schedule it again for later! 

There will be some trial and error, but in general you have the right idea. 

I hope this helps!

If this was helpful, or correct, please be kind and mark the answer appropriately.

Michael Jones - Proud member of the GlideFast Consulting Team!