GoodData Datacenters

GoodData operates datacenters in the following locations (one datacenter per location):

• United States (US), Chicago
• United States (US), Dallas
• European Union (EU), Frankfurt (Germany)
• Canada (CA), Montreal
• United Kingdom (UK), London To assure naming convention continuity, the UK-based datacenter retains its ‘EU’ moniker in the domain URL and may be referred to as EU-1 in related documents.
• Australia (AU), Sydney

Finding Out Your Data Colocation

You can easily find out where your data is physically stored. That information is useful when, for example, a planned maintenance window is announced and you want to find out whether your operations could be affected.

Example:  Find out colocation of your data using the host command on a Mac.

host acmecorp.gooddata.com

where acmecorp.gooddata.com is the domain URL that is used to log in to the GoodData platform.

• If the result contains secure-na3.na.gooddata.com, your data is collocated in the US Dallas datacenter.
• If the result contains secure.fra1.gooddata.com, your data is collocated in the EU Frankfurt datacenter.

For colocation identifiers, see Datacenter Properties.

Migration between Datacenters

Migration is not self-service and is offered as a service from GoodData Support. Migration is subject to a charge. Self-service migration is not available.

• Migration is supported only for workspaces (also known as projects). If your workspaces are housed in the US datacenters, you can request for them to be migrated to the UK London datacenter or the CA Montreal datacenter. You can also request to create your new workspaces in a different datacenter than your current workspaces. The migration transfers the workspace alongside all associated workspace users. Users are added to the same domain as on the source datacenter (the domain needs to first be created on the target datacenter).
• ADS migration is not provided. ADS instances need to be explicitly recreated and populated by each customer.
• Deployed ETL processes (both CloudConnect and BI Automation) are not migrated and must be re-deployed and re-scheduled manually.

Access to Data across Datacenters

Consider the following:

• Each datacenter shares no data or metadata with any other datacenter and can therefore contain overlapping entities such as domains, ADS instances, workspaces, users, and so on. Two entities with the same name (or ID/hash) can coexist in each datacenter at the same time and can have different credentials and definitions (for example, different passwords, domains, users, and workspaces can have different data and metadata, and so on).

• Existing users of the US datacenters do not have access to the UK London datacenter and CA Montreal datacenter.

• Credentials, domains, workspaces, dashboards, and metadata must be created separately in each datacenter.

• White-labeling customizations must be applied separately on each datacenter with a separate domain name for each region.

• CloudConnect Designer must be configured to work with the US datacenters, UK London datacenter, or CA Montreal datacenter.

The following objects and entities are datacenter-specific:

• Dashboard and report embedding URLs
• SSO and authentication tokens
• Reports and ETL process schedules

Knowing which GoodData datacenter stores your data is important if you want to secure data loading by IP whitelisting. See GoodData IP Addresses and IP Whitelisting to find out which IP addresses are whitelisted for individual datacenters.

Datacenter Properties

Expand the following section to explore technical details of individual GoodData datacenters.