Changes

The backup instance is a shadow copy of your '''live live'''SmartSimple instance from the previous day. 

The backup instance of your SmartSimple is updated synced nightly (around 3:00 am Eastern Standard Time) with all the current information from your main instance as it existed when the backup is performed each night. For example, if you change your password on the live instance of SmartSimple, the backup will save reflect your new password when after its nightly updated.  {| class="wikitable"|-!|Backup||The backup environment is a warm backup. This means that it is performed always running and available, just like the production (live) environment. However, the backup is ''not'' a real-time continuous sync. Rather, the backup only synchronizes from the production servers once a day over night. This means that nightmodifications to the production environment of your SmartSimple instance will not be immediately reflected onto the backup - the delay could be up to 24 hours.|-!|Archive||The archive storage retains the daily backups of the database for up to 90 days. This environment is not an accessible web server; it is only used to store each daily database backup. |}

 In all most cases, the backup instance is therefore accessed by appending inserting a "'''bk'''" to your production instance's into the [[URL]]of your production instance. The '''bk '''is added after the '''smartsimple '''part of the URL, but before the domain ending ('''.com, .biz, .ca, '''etc). 

In the following imagebelow, you can note that the user is in logged into the backup instance by the '''bk '''appendage on . 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 [[File:Backup example.pngMessage Queue]], so it is an excellent environment to safely test [[Workflow|500px|borderworkflows]].

===When to Use the Backup Instance===Learning Environment======Because the The backup instance has no impact on live is also a great resource to allow new internal userswho are unfamiliar with the SmartSimple system to build confidence and manage or investigate processes. For a new System Administrator, for example, it is best used for any changes or updates can be helpful to provide this user with System Administrator/Global Administrator permissions on backup only, so as not to the production instance that should be testedimpact your live environment. 

'''Note: '''Any changes It is possible to restrict login access to the data or the structure of the backup instance will environment by role, which can be overwritten when found under [[System Feature Permissions]] in the nightly backup executes[[:Category:Global Settings|Global Settings]]. 

The backup is also a great resource '''Note:''' Any changes to allow new internal users who are unfamiliar with the SmartSimple system to learn how to navigate. For example, they can fiddle with configuring [[List View Overview|list view overviews]], importing users, creating buttons, and more on data or the structure of the backup instance. Changes that are successfully tested on will be overwritten when the nightly backup can then be repeated on the production instance in order for them to actually reflect onto the live systemexecutes.

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.

See [[Upgrades#====System Upgrade Process|here]] for further information.Schedule===={{Upgrade Schedule}}

====System Upgrade Schedule===={| class="wikitable"|-||'''Upgrade'''||'''Planned Production Date'''|-||May 2019||Thursday, May 9, 2019|-||August 2019||Thursday, August 8, 2019|-||November 2019||Thursday, November 14, 2019|-||February 2020||Thursday, February 13, 2020|-||May 2020||Thursday, May 14, 2020|-||August 2020||Thursday, August 13, 2020|-||November 2020||Thursday, November 12, 2020|-||February 2021||Thursday, February 11, 2021|-||May 2021||Thursday, May 13, 2021|-||August 2021||Thursday, August 12, 2021|-||November 2021||Thursday, November 11, 2021|}The next closest upgrade is scheduled for '''Thursday, August 8, 2019.{{CurrentUpgradeDate}}'''.

For more information about the our specific upgrade process, see the see [[Upgrades#System Upgrade Process|here]].