Backup Server and Testing Instances
Contents
Overview
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 SmartSimple instance from the previous day.
The backup instance of your SmartSimple is updated 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 your new password when it is performed that night.
Using the Backup Instance
Locating Your Backup Instance
Depending on the location of your production instance, you can determine the location of your backup instance using the following table:
| Production Instance | Backup Instance |
| 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 all cases, the backup instance is therefore accessed by appending "bk" to your production instance's URL. 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 instance with the same username and password as the production instance.
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.
Note: Any changes to the data or the structure of the backup instance will be overwritten when the nightly backup executes.
The backup is also a great resource 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 overviews, importing users, creating buttons, and more on the backup instance. 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
When system upgrades are scheduled the backup servers are updated two weeks prior to the production servers for testing purposes.
See here for further information, including the schedule of the system updates.
