Changes

Jump to: navigation, search

Backup Server and Testing Instances

1,661 bytes added, 20:17, 28 October 2021
no edit summary
<pre> You can log into the backup instance with the same username and password as the production instance. </pre>
In the image below, the user is logged into the backup instance. Note the bk in the URL, as well as the header that states '''Environment: Backup'''.
 
:: [[File:Backup example.png|700px|border]]
===When to Use the Backup Instance===
======Configuration Mode - Testing 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]].
===When to Use the Backup Instance===Learning Environment======Because the The backup instance has no impact on live users, it is best used for any changes or updates also a great resource to allow new internal users who are unfamiliar with the production instance that should be testedSmartSimple system to build confidence and manage or investigate processes. Changes that are successfully tested on the backup For a new System Administrator, for example, it can then be repeated helpful to provide this user with System Administrator/Global Administrator permissions on the production instance in order for them backup only, so as not to actually reflect onto the impact your live systemenvironment.
The backup It is also a great resource possible to allow new internal users who are unfamiliar with restrict login access to the backup environment by role, which can be found under [[System Feature Permissions]] in the SmartSimple system to learn how to navigate[[:Category:Global Settings|Global Settings]]. 
'''Note:''' Any changes to the data or the structure of the backup instance will be overwritten when the nightly backup executes.
===System Upgrades===
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.
====System Upgrade Schedule====
==See Also==
* [[:Category:Glossary|Glossary]]
* [[How the SmartSimple Support Desk Works]]
* [[Instance]]
* [[Entity and Instance]]
* [[:Category:Universal Tracking Application|Universal Tracking Application/UTA]]
* [[Entity|Entity/Module/UTA Level]]
* [[Creating a Universal Tracking Application|Creating a UTA/Universal Tracking Application]]
* [[Configuration Mode]]
 
[[Category:System Management]][[Category:Upgrades|Upgrades]]
Smartstaff
56
edits

Navigation menu