fixing broken links, adding redirection

MashaMSFT · MashaMSFT · commit 176f0d24fb6e · 2019-01-16T11:14:17.000-08:00
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -260,6 +260,11 @@
             "redirect_url": "/sql/linux/sql-server-linux-manage-ssms",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/sql-server/failover-clusters/high-availability-solutions-sql-server.md",
+            "redirect_url": "/sql/database-engine/sql-server-business-continuity-dr",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/2014/relational-database/replication/what-s-new-replication.md",
             "redirect_url": "/sql/relational-database/replication/sql-server-replication?view=sql-server-2014",
diff --git a/docs/2014/database-engine/database-engine-features-and-tasks.md b/docs/2014/database-engine/database-engine-features-and-tasks.md
@@ -25,7 +25,7 @@ manager: craigg
   
  [Database Engine Cross-Instance Features](../../2014/database-engine/database-engine-cross-instance-features.md)  
   
- [High Availability Solutions &#40;SQL Server&#41;](../sql-server/failover-clusters/high-availability-solutions-sql-server.md)  
+ [High Availability Solutions &#40;SQL Server&#41;](../database-engine/sql-server-business-continuity-dr.md)  
   
  [Security Center for SQL Server Database Engine and Azure SQL Database](../relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md)  
   
diff --git a/docs/2014/database-engine/database-mirroring/database-mirroring-operating-modes.md b/docs/2014/database-engine/database-mirroring/database-mirroring-operating-modes.md
@@ -60,7 +60,7 @@ manager: craigg
  High-performance mode can be useful in a disaster-recovery scenario in which the principal and mirror servers are separated by a significant distance and where you do not want small errors to impact the principal server.  
   
 > [!NOTE]  
->  Log shipping can be a supplement to database mirroring and is a favorable alternative to asynchronous database mirroring. For information about the advantages of log shipping, see [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md). For information on using log shipping with database mirroring, see [Database Mirroring and Log Shipping &#40;SQL Server&#41;](database-mirroring-and-log-shipping-sql-server.md).  
+>  Log shipping can be a supplement to database mirroring and is a favorable alternative to asynchronous database mirroring. For information about the advantages of log shipping, see [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md). For information on using log shipping with database mirroring, see [Database Mirroring and Log Shipping &#40;SQL Server&#41;](database-mirroring-and-log-shipping-sql-server.md).  
   
 ###  <a name="WitnessImpactOnHighPerf"></a> The Impact of a Witness on High-Performance Mode  
  If you use Transact-SQL to configure high-performance mode, whenever the SAFETY property is set to OFF, we strongly recommend that the WITNESS property also be set to OFF. A witness can coexist with high-performance mode, but the witness provides no benefit and introduces risk.  
diff --git a/docs/2014/database-engine/install-windows/install-sql-server-database-engine.md b/docs/2014/database-engine/install-windows/install-sql-server-database-engine.md
@@ -56,7 +56,7 @@ manager: craigg
  [Features Supported by the Editions of SQL Server 2014](../../getting-started/features-supported-by-the-editions-of-sql-server-2014.md)   
  [Editions and Components of SQL Server 2014](../../sql-server/editions-and-components-of-sql-server-2016.md)   
  [Planning a SQL Server Installation](../../sql-server/install/planning-a-sql-server-installation.md)   
- [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md)   
+ [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md)   
  [Upgrade to SQL Server 2014 Using the Installation Wizard &#40;Setup&#41;](upgrade-sql-server-using-the-installation-wizard-setup.md)  
   
   
diff --git a/docs/2014/database-engine/install-windows/install-sql-server.md b/docs/2014/database-engine/install-windows/install-sql-server.md
@@ -64,6 +64,6 @@ manager: craigg
  [Planning a SQL Server Installation](../../sql-server/install/planning-a-sql-server-installation.md)   
  [Upgrade to SQL Server 2014](upgrade-sql-server.md)   
  [Uninstall SQL Server 2014](../../sql-server/install/uninstall-sql-server.md)   
- [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md)  
+ [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md)  
   
   
diff --git a/docs/2014/relational-databases/in-memory-oltp/unsupported-sql-server-features-for-in-memory-oltp.md b/docs/2014/relational-databases/in-memory-oltp/unsupported-sql-server-features-for-in-memory-oltp.md
@@ -55,7 +55,7 @@ manager: craigg
   
 -   Failover Clustering: As part of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] AlwaysOn offering, AlwaysOn Failover Cluster Instances leverages Windows Server Failover Clustering (WSFC) functionality to provide local high availability through redundancy at the server-instance level-a failover cluster instance (FCI). For more information, see [AlwaysOn Failover Cluster Instances (SQL Server)](../../sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server.md).  
   
--   Integration with AlwaysOn: [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] provides several options for creating high availability for a server or database, including AlwaysOn. For more information, see [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md).  
+-   Integration with AlwaysOn: [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] provides several options for creating high availability for a server or database, including AlwaysOn. For more information, see [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md).  
   
 -   Log shipping: [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Log shipping allows you to automatically send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. For more information, see [About Log Shipping &#40;SQL Server&#41;](../../database-engine/log-shipping/about-log-shipping-sql-server.md).  
   
diff --git a/docs/2014/reporting-services/high-availability-reporting-services.md b/docs/2014/reporting-services/high-availability-reporting-services.md
@@ -32,7 +32,7 @@ manager: craigg
  The Report Server Web service and Windows service are tightly integrated and run together as a single report server instance. You cannot configure availability for one service separately from the other.  
   
 ## See Also  
- [High Availability Solutions &#40;SQL Server&#41;](../sql-server/failover-clusters/high-availability-solutions-sql-server.md)   
+ [High Availability Solutions &#40;SQL Server&#41;](../database-engine/sql-server-business-continuity-dr.md)   
  [Configure a Native Mode Report Server Scale-Out Deployment &#40;SSRS Configuration Manager&#41;](install-windows/configure-a-native-mode-report-server-scale-out-deployment.md)  
   
   
diff --git a/docs/breadcrumb/toc.yml b/docs/breadcrumb/toc.yml
@@ -204,7 +204,7 @@
       items:
       - name: Failover clusters
         href: /sql/sql-server/failover-clusters/
-        homepage: /sql/sql-server/failover-clusters/high-availability-solutions-sql-server
+        homepage: /sql/database-engine/sql-server-business-continuity-dr
         items:
         - name: Install
           href: /sql/sql-server/failover-clusters/install/
diff --git a/docs/database-engine/database-mirroring/database-mirroring-operating-modes.md b/docs/database-engine/database-mirroring/database-mirroring-operating-modes.md
@@ -67,7 +67,7 @@ manager: craigg
  High-performance mode can be useful in a disaster-recovery scenario in which the principal and mirror servers are separated by a significant distance and where you do not want small errors to impact the principal server.  
   
 > [!NOTE]  
->  Log shipping can be a supplement to database mirroring and is a favorable alternative to asynchronous database mirroring. For information about the advantages of log shipping, see [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md). For information on using log shipping with database mirroring, see [Database Mirroring and Log Shipping &#40;SQL Server&#41;](../../database-engine/database-mirroring/database-mirroring-and-log-shipping-sql-server.md).  
+>  Log shipping can be a supplement to database mirroring and is a favorable alternative to asynchronous database mirroring. For information about the advantages of log shipping, see [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md). For information on using log shipping with database mirroring, see [Database Mirroring and Log Shipping &#40;SQL Server&#41;](../../database-engine/database-mirroring/database-mirroring-and-log-shipping-sql-server.md).  
   
 ###  <a name="WitnessImpactOnHighPerf"></a> The Impact of a Witness on High-Performance Mode  
  If you use Transact-SQL to configure high-performance mode, whenever the SAFETY property is set to OFF, we strongly recommend that the WITNESS property also be set to OFF. A witness can coexist with high-performance mode, but the witness provides no benefit and introduces risk.  
diff --git a/docs/database-engine/install-windows/install-sql-server-database-engine.md b/docs/database-engine/install-windows/install-sql-server-database-engine.md
@@ -64,7 +64,7 @@ The following features are installed when you select **[!INCLUDE[ssNoVersion](..
 ## See also  
  [Editions and supported features of SQL Server 2017](~/sql-server/editions-and-components-of-sql-server-2017.md)   
  [Planning a SQL Server Installation](../../sql-server/install/planning-a-sql-server-installation.md)   
- [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md)   
+ [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md)   
  [Upgrade SQL Server Using the Installation Wizard &#40;Setup&#41;](../../database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup.md)  
   
   
diff --git a/docs/database-engine/install-windows/install-sql-server.md b/docs/database-engine/install-windows/install-sql-server.md
@@ -87,6 +87,6 @@ manager: craigg
 [Planning a SQL Server Installation](../../sql-server/install/planning-a-sql-server-installation.md)   
  [Upgrade to [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)]](../../database-engine/install-windows/upgrade-sql-server.md)   
  [Uninstall [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)]](../../sql-server/install/uninstall-sql-server.md)   
- [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md)  
+ [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md)  
   
   
diff --git a/docs/sql-server/failover-clusters/index.md b/docs/sql-server/failover-clusters/index.md
@@ -1,3 +1,3 @@
 --- 
-redirect_url: /sql/sql-server/failover-clusters/high-availability-solutions-sql-server
+redirect_url: /sql/database-engine/sql-server-business-continuity-dr
 --- 
diff --git a/docs/sql-server/failover-clusters/toc.yml b/docs/sql-server/failover-clusters/toc.yml
@@ -14,7 +14,7 @@
         - name: Create a cluster
           href: install/create-a-new-sql-server-failover-cluster-setup.md
         - name: Install client tools on a failover cluster
-          href: install-client-tools-on-a-sql-server-failover-cluster.md
+          href: install/install-client-tools-on-a-sql-server-failover-cluster.md
         - name: Add or remove nodes
           href: install/add-or-remove-nodes-in-a-sql-server-failover-cluster-setup.md
         - name: Remove a failover cluster (setup)
diff --git a/docs/sql-server/install/planning-a-sql-server-installation.md b/docs/sql-server/install/planning-a-sql-server-installation.md
@@ -71,6 +71,6 @@ manager: craigg
   
 ## See Also  
  [Install SQL Server from the Command Prompt](../../database-engine/install-windows/install-sql-server-2016-from-the-command-prompt.md)   
- [High Availability Solutions &#40;SQL Server&#41;](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md)   
+ [High Availability Solutions &#40;SQL Server&#41;](../../database-engine/sql-server-business-continuity-dr.md)   
  [Before Installing Failover Clustering](../../sql-server/failover-clusters/install/before-installing-failover-clustering.md)   
  [Upgrade SQL Server Using the Installation Wizard &#40;Setup&#41;](../../database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup.md)  
diff --git a/docs/sql-server/stretch-database/backup-stretch-enabled-databases-stretch-database.md b/docs/sql-server/stretch-database/backup-stretch-enabled-databases-stretch-database.md
@@ -25,7 +25,7 @@ manager: craigg
  -   Microsoft Azure automatically backs up the remote data that Stretch Database has migrated from SQL Server to Azure.  
 
 > [!TIP]
-> Backup is only one part of a complete high availability and business continuity solution. For more info about high availability, see [High Availability Solutions](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md).
+> Backup is only one part of a complete high availability and business continuity solution. For more info about high availability, see [High Availability Solutions](../../database-engine/sql-server-business-continuity-dr.md).
    
 ## Back up your SQL Server data  
   
diff --git a/docs/sql-server/stretch-database/restore-stretch-enabled-databases-stretch-database.md b/docs/sql-server/stretch-database/restore-stretch-enabled-databases-stretch-database.md
@@ -19,7 +19,7 @@ manager: craigg
   For more info about backup, see [Backup Stretch-enabled databases](../../sql-server/stretch-database/backup-stretch-enabled-databases-stretch-database.md).
 
 > [!TIP]
-> Backup is only one part of a complete high availability and business continuity solution. For more info about high availability, see [High Availability Solutions](../../sql-server/failover-clusters/high-availability-solutions-sql-server.md).
+> Backup is only one part of a complete high availability and business continuity solution. For more info about high availability, see [High Availability Solutions](../../database-engine/sql-server-business-continuity-dr.md).
 
 ## Restore your SQL Server data
 To recover from hardware failure or corruption, restore the Stretch-enabled SQL Server database from a backup. You can continue to use the SQL Server restore methods that you currently use. For more info, see [Restore and Recovery Overview](../../relational-databases/backup-restore/restore-and-recovery-overview-sql-server.md).
