Smartstaff, administrator
687
edits
Changes
updating to dynamically reference the upgrade schedule instead of hard-coding dates
In addition to the [[instance]] that your organization uses for day to day work, [[SmartSimple]] clients have access to a second backup instance.
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 it is performed that nightafter its nightly updated.
{| class="wikitable"
|-
!|Backup
||The backup environment is a hot warm backup. This means that it is 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 at around 3:00 am Eastern Standard Timeover night. This means that not modifications to the production environment of your SmartSimple instance will not be immediately reflected onto the backup - the delay will could be around one day depending on when you have made the modification(s)up to 24 hours.
|-
!|Archive
||The archive environment storage retains incremental the daily backups of the database for up to 90 days. This environment is not an accessible web server; it is only retrieves and stores used to store each daily database backup.
|}
==Using the Backup Instance==
===Locating Your Backup Instance===
||alias.smartsimplebk.ie
|}
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).
<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 in logged into the backup instance. This can be observed 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===
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.
===System Upgrades===
====System Upgrade Schedule====
{| class="wikitable"|-||'''{Upgrade'''||'''Planned Production Date'''|-||May 2019||Thursday, May 9, 2019|-||August 2019||Thursday, August 8, 2019|-Schedule}}||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}}'''.
====System Upgrade Process====