SmartSimple clients have access to a second backup environment in addition to their primary working environment. The backup environment is a copy of the previous day's live environment, synced nightly to reflect all current data as it existed at the time of the backup. For example, if a password is changed on the live environment, the backup will reflect that change after the nightly sync.
Who: Global Administrators
Backup and Archive
Backup - The backup environment is a 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 over night. This means that modifications to the production environment of your SmartSimple system will not be immediately reflected onto the backup and 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.
Using the Backup Environment
Locating Your Backup Environment
Depending on the location of your production environment , you can determine the location of your backup environment using the following table:
| Production Environment | Backup Environment |
|---|---|
| alias.smartsimple.com | alias.smartsimplebk.com |
| alias.smartsimple.biz | alias.smartsimplebk.biz |
| alias.smartsimple2.biz | alias.smartsimple2bk.biz |
| alias.smartsimple.ca | alias.smartsimplebk.ca |
| alias.smartsimple.us | alias.smartsimplebk.us |
| alias.smartsimple.ie | alias.smartsimplebk.ie |
In most cases, the backup environment is accessed by inserting a "bk" into the URL of your production environment . The bk is added after the smartsimple part of the URL, but before the domain ending (.com, .biz, .ca, etc).
You can log into the backup environment with the same username and password as the production environment .
In the image below, the user is logged into the backup environment. Note the bk in the URL, as well as the header that states Environment: Backup.
Configuration Mode - Testing Changes
If you are testing a new idea or process using Configuration Mode, 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 environment . Because the backup environment has no impact on live users, it is best used for any changes or updates to the production environment that should be tested. Changes that are successfully tested on the backup environment can then be repeated on the production environment in order for them to actually reflect onto the live system.
You can be logged into the backup and live environment 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 environment by selecting the wrong tab, and you can test your changes in multiple browsers.
Learning Environment
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.
It is possible to restrict login access to the backup environment by role, which can be found under System Feature Permissions in the Global Settings.
Global Releases
When global releases 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.
Global Release Process
The objective of our global release process is to ensure that customers have a chance to review how their applications and information will work following a global release, without compromising the integrity of their current production system. In order to take advantage of this, the backup environment must be used. The backup update allows for environment -specific testing, as you can log into your respective backup environment and test the changes against your most current data and configuration.
If you have any questions about accessing your backup environment, contact Support.