Changes

If you are testing a new idea or process, using Configuration Mode or otherwise, it is best practice to make all changes in the backup environment first, run the process if necessary, and then copy the desired changes into the live instance. Because the backup instance has no impact on live users, it is best used for any changes or updates to the production instance that should be tested. Changes that are successfully tested on the backup can then be repeated on the production instance in order for them to actually reflect onto the live system.

You can be logged into the backup and live instances simultaneously, however, it is recommended to dedicate one browser to live, and one to backup. That way there is less chance of making an unintended change in the live instance by selecting the wrong tab, and you can test your changes in multiple browsers. 

The backup instance does not send any emails triggered by workflows, but you can review the output results in the In Queue tab of the [[Message Queue]], so it is an excellent environment to safely test [[Workflow|workflows]]. 

The backup is also a great resource to allow new internal users who are unfamiliar with the SmartSimple system to build confidence and manage or investigate processes. For a new System Administrator, for example, it can be helpful to provide this user with System Administrator/Global Administrator permissions on backup only, so as not to impact your live environment.

When system [[Upgrade|upgrades]] are scheduled the backup servers are updated '''two weeks prior''' to the production servers for testing purposes. This schedule does not include users who are working on a dedicated server.