Skip to content

Commit 364f96b

Browse files
Merge pull request #290233 from v-thepet/poli-databox
Policheck: databox-overview and databox-heavy-overview
2 parents 5dd2269 + 949c0b1 commit 364f96b

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/databox/data-box-heavy-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,13 +56,13 @@ Data Box Heavy is designed to move massive amounts of data to Azure with little
5656
5757
Previous releases of Data Box, Data Box Disk, and Data Box Heavy didn’t support cross-region data transfer. With the exception of transfers both originating and terminating between the United Kingdom (UK) and the European Union (EU), data couldn’t cross commerce boundaries.
5858

59-
Data Box cross-region data transfer capabilities, now in preview, support offline seamless cross-region data transfers between many regions. This capability allows you to copy your data from a local source and transfer it to a destination within a different country, region, or boundary. It's important to note that the Data Box device isn't shipped across commerce boundaries. Instead, it's transported to an Azure data center within the originating country or region. Data transfer between the source country and the destination region takes place using the Azure network and incurs no additional cost.
59+
Data Box cross-region data transfer capabilities, now in preview, support offline seamless cross-region data transfers between many regions. This capability allows you to copy your data from a local source and transfer it to a destination within a different country, region, or boundary. It's important to note that the Data Box device isn't shipped across commerce boundaries. Instead, it's transported to an Azure data center within the originating country or region. Data transfer between the source country/region and the destination region takes place using the Azure network and incurs no additional cost.
6060

6161
Although cross-region data transfer doesn't incur additional costs, the functionality is currently in preview and subject to change. Note, too, that some data transfer scenarios take place over large geographic areas. Higher than normal latencies might be encountered during such transfers.
6262

6363
Cross-region transfers are currently supported between the following countries and regions:
6464

65-
| Source Country | Destination Region |
65+
| Source Country/Region | Destination Region |
6666
|----------------|---------------------|
6767
| US<sup>1</sup> | EU<sup>2</sup> |
6868
| EU<sup>2</sup> | US<sup>1</sup> |

articles/databox/data-box-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -171,11 +171,11 @@ Data Box can transfer data based on the region in which service is deployed, the
171171

172172
## Data resiliency
173173

174-
The Data Box service is geographical in nature and has a single active deployment in one region within each country or commerce boundary. For data resiliency, a passive instance of the service is maintained in a different region, usually within the same country or commerce boundary. In a few cases, the paired region is outside the country or commerce boundary.
174+
The Data Box service is geographical in nature and has a single active deployment in one region within each country/region or commerce boundary. For data resiliency, a passive instance of the service is maintained in a different region, usually within the same country/region or commerce boundary. In a few cases, the paired region is outside the country/region or commerce boundary.
175175

176176
In the extreme event of any Azure region being affected by a disaster, the Data Box service will be made available through the corresponding paired region. Both ongoing and new orders will be tracked and fulfilled through the service via the paired region. Failover is automatic, and is handled by Microsoft.
177177

178-
For regions paired with a region within the same country or commerce boundary, no action is required. Microsoft is responsible for recovery, which could take up to 72 hours.
178+
For regions paired with a region within the same country/region or commerce boundary, no action is required. Microsoft is responsible for recovery, which could take up to 72 hours.
179179

180180
For regions that don’t have a paired region within the same geographic or commerce boundary, the customer will be notified to create a new Data Box order from a different, available region and copy their data to Azure in the new region. New orders would be required for the Brazil South, Southeast Asia, and East Asia regions.
181181

0 commit comments

Comments
 (0)