Print this page

Site Switching Overview

Knowledge Article Number 000228631
Description

 

Each instance has a secondary instance located in a geographically separate location. The primary and secondary instances are identical and are referred to as an instance pair and share the same name: EU4, for example.


As necessary, site switching allows us to move a production instance between its primary and secondary locations. In the future, we plan on moving your org within its instance pair for the added benefit of allowing us to reduce the impact of scheduled maintenance windows and performance degradations.

Frequently Asked Questions

 
  1. What is a site switch and how will it benefit me?

    1. Each instance has a secondary instance located in a geographically separate location. The primary and secondary instances are identical and are referred to as an instance pair and share the same name: EU4, for example.

    2. As necessary, site switching allows us to move a production instance between its primary and secondary locations.

    3. Site switching also allows us to improve the availability of our service. In the future, we plan on moving your org within its instance pair for the added benefit of allowing us to reduce the impact of scheduled maintenance windows and performance degradations.

      1. For example, in the future state, when a maintenance is scheduled for the primary instance, we will perform a site switch to place your org on the secondary instance, within your instance pair, so that your users may continue their business as usual without experiencing a scheduled maintenance window.

 
  1. What action do I need to take to prepare for a site switch?

    1. If you already follow our best practices for network settings, and are not restricting access to Salesforce IP ranges, the maintenance should be seamless to your users. However, if you control your DNS timeout values set, then you will need to refresh your DNS cache and restart any integrations following the maintenance.

    2. If you are restricting access to certain IP ranges or data centers, please update your network settings to include the complete list of Salesforce IP ranges from the What are the Salesforce IP Addresses to whitelist? article in order to avoid any unintended service disruptions.

 
  1. What are Salesforce’s recommended best practices for customer orgs?

    1. As necessary, Salesforce will schedule system maintenances during the preferred system maintenance windows listed in the Salesforce Maintenance Schedule article. We ask that you plan your activities accordingly, and avoid scheduling activities during the Salesforce maintenance windows.

    2. In order to avoid unintended service disruptions, we recommend that you:

      1. follow our network and email settings best practices outlined in the What are the Salesforce IP Addresses to whitelist? article.

      2. use relative URLs or enable MyDomains to ensure you do not have any hard-coded references as our systems cannot redirect hard-coded references in integrations and Knowledge articles when you move to a new instance. For more information on relative URLs, please check out the Best Practices When Referencing Server Endpoints article.

    3. If you control your DNS timeout values set, then you will need to refresh your DNS cache and restart any integrations following maintenance windows.

 
  1. Would Salesforce ever leave the instance in its secondary instance location if that location was in another region?

    1. In the event that we need to implement the disaster recovery plan or to maintain service availability and performance, we will leave the instance in its secondary instance location until service can be maintained in the primary instance location. This is the purpose of our disaster recovery plans.

 
  1. Where can I find more information?

    1. If you have additional questions, please reach out to Customer Support by opening a case via the Help & Training portal.





promote demote