Merge pull request #34692 from MashaMSFT/fixes

FCI screenshot & mi link network note

Author: JillGrant615

azure-sql/managed-instance/managed-instance-link-troubleshoot-how-to.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot issues with the link
 titleSuffix: Azure SQL Managed Instance
-description: Learn how troubleshoot common issues with a link between SQL Server and Azure SQL Managed Instance.
+description: Learn how to troubleshoot common issues with a link between SQL Server and Azure SQL Managed Instance.
 author: djordje-jeremic
 ms.author: djjeremi
 ms.reviewer: mathoma, danil
@@ -27,6 +27,8 @@ When establishing a link between SQL Server and Azure SQL Managed Instance, ther
 
 If the speed of the link between the two instances is slower than what is necessary, the time to seed is likely to be noticeably affected. You can use the stated seeding speed, total size of data, and the link speed to estimate how long the initial seeding phase will take before data replication starts. For example, for a single 100-GB database, the initial seed phase would take about 1.2 hours if the link is capable of pushing 84 GB per hour, and if there are no other databases being seeded to a different link. If the link can only transfer 10 GB per hour, then seeding a 100-GB database can take about 10 hours. If there are multiple databases to replicate via multiple links, seeding will be executed in parallel, and, when combined with a slow link speed, the initial seeding phase might take considerably longer, especially if the parallel seeding of data from all databases exceeds the available link bandwidth.
 
+The initial seeding phase isn't resilient to network interruptions and instance maintenance or failover operations. If bi-directional connectivity between SQL Server and SQL Managed Instance is temporarily lost, or if either SQL Server or SQL Managed instance is restarted or failed over during the initial seeding phase, seeding is restarted. 
+
 > [!IMPORTANT]
 > The initial seeding phase can take days with extremely low-speed or busy links. In this case, creating the link can time out. Creating the link is automatically canceled after 6 days. 
 

docs/sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server.md

@@ -135,6 +135,10 @@ Contrary to the availability group, an FCI must use shared storage between all n
 
 The VNN for the FCI provides a unified connection point for the FCI. This allows applications to connect to the VNN without the need to know the currently active node. When a failover occurs, the VNN is registered to the new active node after it starts. This process is transparent to the client or application connecting to [!INCLUDE [ssNoVersion](../../../includes/ssnoversion-md.md)] and this minimizes the downtime the application or clients experience during a failure.
 
+The following screenshot highlights the network name for the failover cluster instance in Failover Cluster Manager: 
+
+:::image type="content" source="media/always-on-failover-cluster-instances-sql-server/fci-network-name.png" alt-text="Screenshot of the fci network name in Failover Cluster Manager.":::
+
 ### Virtual IPs
 
 In the case of a multi-subnet FCI, a virtual IP address is assigned to each subnet in the FCI. During a failover, the VNN on the DNS server is updated to point to the virtual IP address for the respective subnet. Applications and clients can then connect to the FCI using the same VNN after a multi-subnet failover.