Changes

* ==Overview==In addition to the [[instance ]] that your organisation organization uses for day to day work, [[SmartSimple customers ]] clients have access to a second backup instance.

* These The backup instances instance is a copy of your '''live''' SmartSimple are updated nightly with all the current information instance from the main instance as it exists at about 3:00 a.mprevious day. 

* You can log into the The backup instance of your SmartSimple is synced nightly with all the same username and current information from your main instance as it existed when the backup is performed each night. For example, if you change your password as on the production live instanceof SmartSimple, the backup will reflect your new password after its nightly updated. 

{| class="wikitable"|-!|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''Please note a real-time continuous sync. Rather, the backup only synchronizes from the production servers once a day over night. This means that any changes modifications 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 data or 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 Instance=====Locating Your Backup Instance===Depending on the structure location of your production instance, you can determine the location of your backup instance will be overwritten when using the live data transfer takes place at 3following table:00   {| class="wikitable"|-||'''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 most cases, the backup instance is therefore accessed by inserting a"'''bk'''" into the [[URL]] of your production instance.mThe '''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 logged into the backup instance. Note the following morningbk 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. 

When system [[Upgrade|upgrades]] are The next upgrade is scheduled the backup servers are updated 2 days earlier than the production servers for testing purposesfor '''{{CurrentUpgradeDate}}'''.

See [[Upgrades#====System Upgrade Process|here]] ====The objective of our system upgrade process is to ensure that customers have a chance to review how their applications and information will work following a system upgrade, without compromising the integrity of their current production system. In order to take advantage of this, the backup instance must be used. The backup update allows for further informationinstance-specific testing, as you can log into your respective backup instance and test the changes against your most current data and configuration.

Depending on ==See Also==* [[:Category:Glossary|Glossary]]* [[How the location of your production instance, you can determine the location of your backup instance using the following tableSmartSimple 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]]