Redirect duplicates-Set 2

Author: ManikaDhiman

.openpublishing.redirection.json

@@ -10446,9 +10446,14 @@
       "redirect_document_id": false
     },
     {
-      "source_path": "WindowsServerDocs/storage/understand-the-cache.md",
+      "source_path": "WindowsServerDocs/storage/storage-spaces/understand-the-cache.md",
       "redirect_url": "/azure-stack/hci/concepts/cache",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "WindowsServerDocs/storage/storage-spaces/storage-spaces-fault-tolerance.md",
+      "redirect_url": "/azure-stack/hci/concepts/fault-tolerance",
+      "redirect_document_id": false
     }
   ]
 }

WindowsServerDocs/storage/TOC.md

@@ -131,7 +131,7 @@
 ## [Storage Spaces Direct](storage-spaces/storage-spaces-direct-overview.md)
 ### Understand
 #### [Understand the cache](/azure-stack/hci/concepts/cache)
-#### [Fault tolerance and storage efficiency](storage-spaces/Storage-Spaces-Fault-Tolerance.md)
+#### [Fault tolerance and storage efficiency](/azure-stack/hci/concepts/fault-tolerance)
 #### [Drive symmetry considerations](storage-spaces/drive-symmetry-considerations.md)
 #### [Understand and monitor storage resync](storage-spaces/understand-storage-resync.md)
 #### [Cluster and pool quorum](storage-spaces/understand-quorum.md)

WindowsServerDocs/storage/refs/mirror-accelerated-parity.md

@@ -20,7 +20,7 @@ Storage Spaces can provide fault tolerance for data using two fundamental techni
 
 Mirror and parity resiliency schemes have fundamentally different storage and performance characteristics:
 - Mirror resiliency allows users to attain fast write performance, but replicating the data for each copy isn't space efficient.
-- Parity, on the other hand, must re-compute parity for every write, causing random write performance to suffer. Parity does, however, allow users to store their data with greater space efficiency. For more info, see [Storage Spaces fault tolerance](../storage-spaces/Storage-Spaces-Fault-Tolerance.md).
+- Parity, on the other hand, must re-compute parity for every write, causing random write performance to suffer. Parity does, however, allow users to store their data with greater space efficiency. For more info, see [Storage Spaces fault tolerance](/azure-stack/hci/concepts/fault-tolerance).
 
 Thus, mirror is predisposed to deliver performance-sensitive storage while parity offers improved storage capacity utilization. In mirror-accelerated parity, ReFS leverages the benefits of each resiliency type to deliver both capacity-efficient and performance-sensitive storage by combining both resiliency schemes within a single volume.
 

WindowsServerDocs/storage/storage-spaces/add-nodes.md

@@ -84,7 +84,7 @@ New-Volume -FriendlyName <Name> -FileSystem CSVFS_ReFS -StoragePoolFriendlyName
 
 ![adding a fourth server to a three-node cluster](media/add-nodes/Scaling-3-to-4.png)
 
-With four servers, you can use dual parity, also commonly called erasure coding (compare to distributed RAID-6). This provides the same fault tolerance as three-way mirroring, but with better storage efficiency. To learn more, see [Fault tolerance and storage efficiency](storage-spaces-fault-tolerance.md).
+With four servers, you can use dual parity, also commonly called erasure coding (compare to distributed RAID-6). This provides the same fault tolerance as three-way mirroring, but with better storage efficiency. To learn more, see [Fault tolerance and storage efficiency](/azure-stack/hci/concepts/fault-tolerance).
 
 If you're coming from a smaller deployment, you have several good options to begin creating dual parity volumes. You can use whichever you prefer.
 
@@ -135,7 +135,7 @@ As you scale beyond four servers, new volumes can benefit from ever-greater pari
 
 However, any pre-existing volumes will *not* be "converted" to the new, wider encoding. One good reason is that to do so would require a massive calculation affecting literally *every single bit* in the entire deployment. If you would like pre-existing data to become encoded at the higher efficiency, you can migrate it to new volume(s).
 
-For more details, see [Fault tolerance and storage efficiency](storage-spaces-fault-tolerance.md).
+For more details, see [Fault tolerance and storage efficiency](/azure-stack/hci/concepts/fault-tolerance).
 
 ### Adding servers when using chassis or rack fault tolerance
 

WindowsServerDocs/storage/storage-spaces/choosing-drives.md

@@ -95,4 +95,4 @@ We recommend limiting the total storage capacity per server to approximately 400
 - [Understand the cache in Storage Spaces Direct](/azure-stack/hci/concepts/cache)
 - [Storage Spaces Direct hardware requirements](storage-spaces-direct-hardware-requirements.md)
 - [Planning volumes in Storage Spaces Direct](plan-volumes.md)
-- [Fault tolerance and storage efficiency](storage-spaces-fault-tolerance.md)
+- [Fault tolerance and storage efficiency](/azure-stack/hci/concepts/fault-tolerance)

WindowsServerDocs/storage/storage-spaces/delimit-volume-allocation.md

@@ -21,12 +21,12 @@ Windows Server 2019 introduces an option to manually delimit the allocation of v
 ### ![Green checkmark icon.](media/delimit-volume-allocation/supported.png) Consider using this option if:
 
 - Your cluster has six or more servers; and
-- Your cluster uses only [three-way mirror](storage-spaces-fault-tolerance.md#mirroring) resiliency
+- Your cluster uses only [three-way mirror](/azure-stack/hci/concepts/fault-tolerance.md#mirroring) resiliency
 
 ### ![Red X icon.](media/delimit-volume-allocation/unsupported.png) Do not use this option if:
 
 - Your cluster has fewer than six servers; or
-- Your cluster uses [parity](storage-spaces-fault-tolerance.md#parity) or [mirror-accelerated parity](storage-spaces-fault-tolerance.md#mirror-accelerated-parity) resiliency
+- Your cluster uses [parity](/azure-stack/hci/concepts/fault-tolerance.md#parity) or [mirror-accelerated parity](/azure-stack/hci/concepts/fault-tolerance.md#mirror-accelerated-parity) resiliency
 
 ## Understand
 
@@ -36,7 +36,7 @@ With regular three-way mirroring, the volume is divided into many small "slabs"
 
 ![Diagram showing the volume being divided into three stacks of slabs and distributed evenly across every server.](media/delimit-volume-allocation/regular-allocation.png)
 
-This default allocation maximizes parallel reads and writes, leading to better performance, and is appealing in its simplicity: every server is equally busy, every drive is equally full, and all volumes stay online or go offline together. Every volume is guaranteed to survive up to two concurrent failures, as [these examples](storage-spaces-fault-tolerance.md#examples) illustrate.
+This default allocation maximizes parallel reads and writes, leading to better performance, and is appealing in its simplicity: every server is equally busy, every drive is equally full, and all volumes stay online or go offline together. Every volume is guaranteed to survive up to two concurrent failures, as [these examples](/azure-stack/hci/concepts/fault-tolerance.md#examples) illustrate.
 
 However, with this allocation, volumes can't survive three concurrent failures. If three servers fail at once, or if drives in three servers fail at once, volumes become inaccessible because at least some slabs were (with very high probability) allocated to the exact three drives or servers that failed.
 
@@ -202,7 +202,7 @@ No, it's the same as with regular allocation.
 ## Additional References
 
 - [Storage Spaces Direct overview](storage-spaces-direct-overview.md)
-- [Fault tolerance in Storage Spaces Direct](storage-spaces-fault-tolerance.md)
+- [Fault tolerance in Storage Spaces Direct](/azure-stack/hci/concepts/fault-tolerance)
 
 ## Appendix
 

WindowsServerDocs/storage/storage-spaces/deploy-storage-spaces-direct.md

@@ -377,6 +377,6 @@ CD $ScriptFolder
 -   [Storage Spaces Direct overview](storage-spaces-direct-overview.md)
 -   [Understand the cache in Storage Spaces Direct](/azure-stack/hci/concepts/cache)
 -   [Planning volumes in Storage Spaces Direct](plan-volumes.md)
--   [Storage Spaces Fault Tolerance](storage-spaces-fault-tolerance.md)
+-   [Storage Spaces Fault Tolerance](/azure-stack/hci/concepts/fault-tolerance)
 -   [Storage Spaces Direct Hardware Requirements](Storage-Spaces-Direct-Hardware-Requirements.md)
 -   [To RDMA, or not to RDMA – that is the question](https://techcommunity.microsoft.com/t5/storage-at-microsoft/bg-p/FileCAB) (TechNet blog)

WindowsServerDocs/storage/storage-spaces/nested-resiliency.md

@@ -28,7 +28,7 @@ Nested resiliency is a new capability of [Storage Spaces Direct](storage-spaces-
 
 ## Why nested resiliency
 
-Volumes that use nested resiliency can **stay online and accessible even if multiple hardware failures happen at the same time**, unlike classic [two-way mirroring](storage-spaces-fault-tolerance.md) resiliency. For example, if two drives fail at the same time, or if a server goes down and a drive fails, volumes that use nested resiliency stay online and accessible. For hyper-converged infrastructure, this increases uptime for apps and virtual machines; for file server workloads, this means users enjoy uninterrupted access to their files.
+Volumes that use nested resiliency can **stay online and accessible even if multiple hardware failures happen at the same time**, unlike classic [two-way mirroring](/azure-stack/hci/concepts/fault-tolerance) resiliency. For example, if two drives fail at the same time, or if a server goes down and a drive fails, volumes that use nested resiliency stay online and accessible. For hyper-converged infrastructure, this increases uptime for apps and virtual machines; for file server workloads, this means users enjoy uninterrupted access to their files.
 
 ![Storage availability](media/nested-resiliency/storage-availability.png)
 
@@ -50,7 +50,7 @@ Storage Spaces Direct in Windows Server 2019 offers two new resiliency options i
 
   ![Nested two-way mirror](media/nested-resiliency/nested-two-way-mirror.png)
 
-- **Nested mirror-accelerated parity.** Combine nested two-way mirroring, from above, with nested parity. Within each server, local resiliency for most data is provided by single [bitwise parity arithmetic](storage-spaces-fault-tolerance.md#parity), except new recent writes which use two-way mirroring. Then, further resiliency for all data is provided by two-way mirroring between the servers. For more information about how mirror-accelerated parity works, see [Mirror-accelerated parity](../refs/mirror-accelerated-parity.md).
+- **Nested mirror-accelerated parity.** Combine nested two-way mirroring, from above, with nested parity. Within each server, local resiliency for most data is provided by single [bitwise parity arithmetic](/azure-stack/hci/concepts/fault-tolerance.md#parity), except new recent writes which use two-way mirroring. Then, further resiliency for all data is provided by two-way mirroring between the servers. For more information about how mirror-accelerated parity works, see [Mirror-accelerated parity](../refs/mirror-accelerated-parity.md).
 
   ![Nested mirror-accelerated parity](media/nested-resiliency/nested-mirror-accelerated-parity.png)
 
@@ -190,6 +190,6 @@ For details see the [Remove servers](remove-servers.md) topic.
 ## Additional References
 
 - [Storage Spaces Direct overview](storage-spaces-direct-overview.md)
-- [Understand fault tolerance in Storage Spaces Direct](storage-spaces-fault-tolerance.md)
+- [Understand fault tolerance in Storage Spaces Direct](/azure-stack/hci/concepts/fault-tolerance)
 - [Plan volumes in Storage Spaces Direct](plan-volumes.md)
 - [Create volumes in Storage Spaces Direct](create-volumes.md)

WindowsServerDocs/storage/storage-spaces/plan-volumes.md

@@ -67,7 +67,7 @@ Nested resiliency (available only on Windows Server 2019) provides data resilien
 
 ### With three servers
 
-With three servers, you should use three-way mirroring for better fault tolerance and performance. Three-way mirroring keeps three copies of all data, one copy on the drives in each server. Its storage efficiency is 33.3% – to write 1 TB of data, you need at least 3 TB of physical storage capacity in the storage pool. Three-way mirroring can safely tolerate [at least two hardware problems (drive or server) at a time](storage-spaces-fault-tolerance.md#examples). If 2 nodes become unavailable the storage pool will lose quorum, since 2/3 of the disks are not available, and the virtual disks will be unaccessible. However, a node can be down and one or more disks on another node can fail and the virtual disks will remain online. For example, if you're rebooting one server when suddenly another drive or server fails, all data remains safe and continuously accessible.
+With three servers, you should use three-way mirroring for better fault tolerance and performance. Three-way mirroring keeps three copies of all data, one copy on the drives in each server. Its storage efficiency is 33.3% – to write 1 TB of data, you need at least 3 TB of physical storage capacity in the storage pool. Three-way mirroring can safely tolerate [at least two hardware problems (drive or server) at a time](/azure-stack/hci/concepts/fault-tolerance.md#examples). If 2 nodes become unavailable the storage pool will lose quorum, since 2/3 of the disks are not available, and the virtual disks will be unaccessible. However, a node can be down and one or more disks on another node can fail and the virtual disks will remain online. For example, if you're rebooting one server when suddenly another drive or server fails, all data remains safe and continuously accessible.
 
 ![Diagram depicting the concept of three-way mirror data storage.](media/plan-volumes/three-way-mirror.png)
 
@@ -195,4 +195,4 @@ See [Creating volumes in Storage Spaces Direct](create-volumes.md).
 
 - [Storage Spaces Direct overview](storage-spaces-direct-overview.md)
 - [Choosing drives for Storage Spaces Direct](choosing-drives.md)
-- [Fault tolerance and storage efficiency](storage-spaces-fault-tolerance.md)
+- [Fault tolerance and storage efficiency](/azure-stack/hci/concepts/fault-tolerance)

WindowsServerDocs/storage/storage-spaces/storage-spaces-direct-overview.md

@@ -20,7 +20,7 @@ For other applications of Storage Spaces, such as shared SAS clusters and stand-
 
 | Description | Documentation |
 |--|--|
-| **Understand**<br><ul><li>Overview (you are here)</li><li>[Understand the cache](/azure-stack/hci/concepts/cache)</li><li>[Fault tolerance and storage efficiency](storage-spaces-fault-tolerance.md)<li>[Drive symmetry considerations](drive-symmetry-considerations.md)</li><li>[Understand and monitor storage resync](understand-storage-resync.md)</li><li>[Understanding cluster and pool quorum](understand-quorum.md)</li><li>[Cluster sets](/azure-stack/hci/deploy/cluster-set)</li> | **Plan**<br><ul><li>[Hardware requirements](storage-spaces-direct-hardware-requirements.md)</li><li>[Using the CSV in-memory read cache](csv-cache.md)</li><li>[Choose drives](choosing-drives.md)</li><li>[Plan volumes](plan-volumes.md)</li><li>[Using guest VM clusters](storage-spaces-direct-in-vm.md)</li><li>[Disaster recovery](storage-spaces-direct-disaster-recovery.md)</li> |
+| **Understand**<br><ul><li>Overview (you are here)</li><li>[Understand the cache](/azure-stack/hci/concepts/cache)</li><li>[Fault tolerance and storage efficiency](/azure-stack/hci/concepts/fault-tolerance)<li>[Drive symmetry considerations](drive-symmetry-considerations.md)</li><li>[Understand and monitor storage resync](understand-storage-resync.md)</li><li>[Understanding cluster and pool quorum](understand-quorum.md)</li><li>[Cluster sets](/azure-stack/hci/deploy/cluster-set)</li> | **Plan**<br><ul><li>[Hardware requirements](storage-spaces-direct-hardware-requirements.md)</li><li>[Using the CSV in-memory read cache](csv-cache.md)</li><li>[Choose drives](choosing-drives.md)</li><li>[Plan volumes](plan-volumes.md)</li><li>[Using guest VM clusters](storage-spaces-direct-in-vm.md)</li><li>[Disaster recovery](storage-spaces-direct-disaster-recovery.md)</li> |
 | **Deploy**<br><ul><li>[Deploy Storage Spaces Direct](deploy-storage-spaces-direct.md)</li><li>[Create volumes](create-volumes.md)</li><li>[Nested resiliency](nested-resiliency.md)</li><li>[Configure quorum](../../failover-clustering/manage-cluster-quorum.md)</li><li>[Upgrade a Storage Spaces Direct cluster to Windows Server 2019](upgrade-storage-spaces-direct-to-windows-server-2019.md)</li><li>[Understand and deploy persistent memory](/azure-stack/hci/concepts/deploy-persistent-memory)</li> | **Manage**<br><ul><li>[Manage with Windows Admin Center](../../manage/windows-admin-center/use/manage-hyper-converged.md)</li><li>[Add servers or drives](add-nodes.md)</li><li>[Taking a server offline for maintenance](maintain-servers.md)</li><li>[Remove servers](remove-servers.md)</li><li>[Extend volumes](resize-volumes.md)</li><li>[Delete volumes](delete-volumes.md)</li><li>[Update drive firmware](../update-firmware.md)</li><li>[Performance history](performance-history.md)</li><li>[Delimit the allocation of volumes](delimit-volume-allocation.md)</li><li>[Use Azure Monitor on a hyper-converged cluster](configure-azure-monitor.md)</li> |
 | **Troubleshooting**<br><ul><li>[Troubleshooting scenarios](troubleshooting-storage-spaces.md)</li><li>[Troubleshoot health and operational states](storage-spaces-states.md)</li><li>[Collect diagnostic data with Storage Spaces Direct](data-collection.md)</li><li>[Storage-class memory health management](Storage-class-memory-health.md)</li> | **Recent blog posts**<br><ul><li>[13.7 million IOPS with Storage Spaces Direct: the new industry record for hyper-converged infrastructure](https://techcommunity.microsoft.com/t5/storage-at-microsoft/the-new-hci-industry-record-13-7-million-iops-with-windows/ba-p/428314)</li><li>[Hyper-converged infrastructure in Windows Server 2019 - the countdown clock starts now!](https://techcommunity.microsoft.com/t5/storage-at-microsoft/bg-p/FileCAB)</li><li>[Five big announcements from the Windows Server Summit](https://techcommunity.microsoft.com/t5/storage-at-microsoft/bg-p/FileCAB)</li><li>[10,000 Storage Spaces Direct clusters and counting...](https://techcommunity.microsoft.com/t5/storage-at-microsoft/storage-spaces-direct-10-000-clusters-and-counting/ba-p/428185)</li></ul> |
 
@@ -92,7 +92,7 @@ Here's an overview of the Storage Spaces Direct stack:
 
 **Storage Pool.** The collection of drives that form the basis of Storage Spaces is called the storage pool. It is automatically created, and all eligible drives are automatically discovered and added to it. We strongly recommend you use one pool per cluster, with the default settings. Read our [Deep Dive into the Storage Pool](https://techcommunity.microsoft.com/t5/storage-at-microsoft/deep-dive-the-storage-pool-in-storage-spaces-direct/ba-p/425959) to learn more.
 
-**Storage Spaces.** Storage Spaces provides fault tolerance to virtual "disks" using [mirroring, erasure coding, or both](storage-spaces-fault-tolerance.md). You can think of it as distributed, software-defined RAID using the drives in the pool. In Storage Spaces Direct, these virtual disks typically have resiliency to two simultaneous drive or server failures (e.g. 3-way mirroring, with each data copy in a different server) though chassis and rack fault tolerance is also available.
+**Storage Spaces.** Storage Spaces provides fault tolerance to virtual "disks" using [mirroring, erasure coding, or both](/azure-stack/hci/concepts/fault-tolerance). You can think of it as distributed, software-defined RAID using the drives in the pool. In Storage Spaces Direct, these virtual disks typically have resiliency to two simultaneous drive or server failures (e.g. 3-way mirroring, with each data copy in a different server) though chassis and rack fault tolerance is also available.
 
 **Resilient File System (ReFS).** ReFS is the premier filesystem purpose-built for virtualization. It includes dramatic accelerations for .vhdx file operations such as creation, expansion, and checkpoint merging, and built-in checksums to detect and correct bit errors. It also introduces real-time tiers that rotate data between so-called "hot" and "cold" storage tiers in real-time based on usage.
 
@@ -125,7 +125,7 @@ Try Storage Spaces Direct [in Microsoft Azure](https://techcommunity.microsoft.c
 
 ## Additional References
 
-- [Fault tolerance and storage efficiency](storage-spaces-fault-tolerance.md)
+- [Fault tolerance and storage efficiency](/azure-stack/hci/concepts/fault-tolerance)
 - [Storage Replica](../storage-replica/storage-replica-overview.md)
 - [Storage at Microsoft blog](https://techcommunity.microsoft.com/t5/storage-at-microsoft/bg-p/FileCAB)
 - [Storage Spaces Direct throughput with iWARP](https://techcommunity.microsoft.com/t5/storage-at-microsoft/bg-p/FileCAB) (TechNet blog)