Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.
QuickBase Secondary Data Center: Action Required
As you know, Intuit QuickBase has taken number of steps to enhance the stability and resiliency of QuickBase. We’ve begun implementing high availability capability across two sites—our primary data center in Quincy, Washington and our secondary site in San Diego,California. Our goal is to be able to bring QuickBase into operation in our secondary data center within two hours of a service interruption (previously it took more than a day). The changes we’re making to enable faster recovery to a secondary site are a significant improvement in our ability to provide the level of service our customers expect.
As part of our implementation, we will begin testing our “failover” process to the secondary site. When we conduct these tests, you’ll be reaching QuickBase through a different IP address.
What do you need to do?
Because testing will begin in November, we need you to check your ability to access both IPs by November 12, 2010. Once completed, QuickBase will have two IP addresses: one for the primary site and one for the secondary site.
As a best practice, you should always access QuickBase via its domain name rather than its IP address: <yourdomain>.quickbase.com. Doing so ensures that you'll always be able to access QuickBase, even if the IP address changes.
However, some organizations allow traffic from only very specific IP addresses through their firewall. If the IP address of the secondary site is blacklisted and we need to fail over to the secondary site, you will not be able to access QuickBase.
If you access QuickBase via a domain name: You don’t need to do anything; you’ll be able to access QuickBase throughout our testing and in the event of a failover.
If your organization DOES “white list” specific IP addresses: You do need to take action. Your network administrator needs to make sure that you can access the IP addresses of BOTH our primary and secondary sites after the switch. These are:
Primary site: 126.96.36.199
About scripts that point to QuickBase
If your organization uses scripts that point to QuickBase’s IP address, these need to be updated as well. The person responsible for updating your scripts should make sure all scripts point to your QuickBase domain name.
What about email servers?
Some organizations have strict email filtering rules in place that allow only approved email into their domain. QuickBase keeps an up to date Sender Policy Framework (SPF) record for all email servers used to send email for the quickbase.com domain.
SPF is our recommended and supported method for spam filtering. If your email administrator uses an active SPF policy to validate the source of emails coming into your domain, you should experience no issues during a fail over.
Since the IP addresses of email servers can change without notice, customers should no longer “white list” IP addresses to allow QuickBase emails to be received via IP address. If your organization has implemented this practice, you should plan to implement SPF as soon as possible. You can temporarily access the current list of IPs and networks that can be white listed in this Knowledge Base article; however, relying on this published list will not guarantee interruption-free service.
You may also want to reference Why are my users not receiving QuickBase email as expected? to learn how to troubleshoot email problems you may be experiencing.