Merge pull request #91634 from yegu-ms/master

Updated Import and Export screenshots

Author: American-Dipper

articles/azure-cache-for-redis/TOC.yml

@@ -28,19 +28,17 @@
     - name: Azure Cache for Redis samples
       href: cache-redis-samples.md
     - name: Azure PowerShell
-      href: cache-howto-manage-redis-cache-powershell.md
+      href: cache-how-to-manage-redis-cache-powershell.md
     - name: Azure CLI
       href: cli-samples.md
 - name: Concepts
   items:
-    - name: Best Practices
-      items:
-        - name: Best Practices for Azure Cache for Redis
-          href: cache-best-practices.md
-        - name: Azure Architecture Best Practices for Caching
-          href: https://docs.microsoft.com/azure/architecture/best-practices/caching?toc=%2Fazure%2Fredis-cache%2Ftoc.json
-    - name: Failover and patching explained
+    - name: Best practices
+      href: cache-best-practices.md
+    - name: Failover and patching
       href: cache-failover.md
+    - name: Architecture best practices for caching
+      href: https://docs.microsoft.com/azure/architecture/best-practices/caching?toc=%2Fazure%2Fredis-cache%2Ftoc.json
 - name: How-to guides
   items:
   - name: Plan
@@ -58,19 +56,25 @@
   - name: Automate
     items:
     - name: Deploy and manage using Azure Powershell
-      href: cache-howto-manage-redis-cache-powershell.md
+      href: cache-how-to-manage-redis-cache-powershell.md
     - name: Deploy and Manage using Azure CLI
       href: cli-samples.md
     - name: Provision an Azure Cache for Redis
       href: cache-redis-cache-arm-provision.md
     - name: Provision a Web App with Azure Cache for Redis
       href: cache-web-app-arm-with-redis-cache-provision.md
-  - name: Integrate with ASP.NET
+  - name: Integrate with application
     items:
-    - name: Session state provider
-      href: cache-aspnet-session-state-provider.md
-    - name: Output cache provider
-      href: cache-aspnet-output-cache-provider.md
+    - name: ASP.NET
+      items:
+      - name: Use session state provider
+        href: cache-aspnet-session-state-provider.md
+      - name: Use output cache provider
+        href: cache-aspnet-output-cache-provider.md
+    - name: Java Spring
+      items:
+      - name: Use Spring Boot Initializer
+        href: cache-java-spring-boot-initializer-with-redis-cache.md
   - name: Manage
     items:
     - name: Configure in Azure portal
@@ -85,24 +89,28 @@
       href: cache-administration.md#schedule-updates
     - name: Configure redis-cli.exe access
       href: cache-how-to-redis-cli-tool.md
-  - name: Monitor and troubleshoot
+  - name: Monitor
     items:
     - name: Monitor in Azure portal
       href: cache-how-to-monitor.md
-    - name: Troubleshoot cache issues
-      href: cache-how-to-troubleshoot.md
     - name: Set alerts for exceptions
       href: cache-how-to-monitor.md#operations-and-alerts
+  - name: Diagnose and troubleshoot
+    items:
+    - name: Troubleshoot Redis server
+      href: cache-how-to-troubleshoot-server.md
+    - name: Troubleshoot Redis client
+      href: cache-how-to-troubleshoot-client.md
+    - name: Troubleshoot timeouts
+      href: cache-how-to-troubleshoot-timeouts.md
+    - name: Troubleshoot data loss
+      href: cache-how-to-troubleshoot-data-loss.md
   - name: Scale
     items:
     - name: Update to a different size and tier
       href: cache-how-to-scale.md
     - name: Use Redis cluster to scale in/out
       href: cache-how-to-premium-clustering.md
-  - name: Integrate with Spring Boot
-    items:
-    - name: Use a Spring Boot Initializer app with Azure Cache for Redis
-      href: cache-java-spring-boot-initializer-with-redis-cache.md
 - name: Reference
   items:
   - name: Code samples

articles/azure-cache-for-redis/cache-administration.md

@@ -67,7 +67,7 @@ If you reboot both the **Master** and **Slave** nodes, all data in the cache (or
 If you reboot just one of the nodes, data is not typically lost, but it still may be. For example if the master node is rebooted and a cache write is in progress, the data from the cache write is lost. Another scenario for data loss would be if you reboot one node and the other node happens to go down due to a failure at the same time. For more information about possible causes for data loss, see [What happened to my data in Redis?](https://gist.github.com/JonCole/b6354d92a2d51c141490f10142884ea4#file-whathappenedtomydatainredis-md)
 
 ### Can I reboot my cache using PowerShell, CLI, or other management tools?
-Yes, for PowerShell instructions see [To reboot an Azure Cache for Redis](cache-howto-manage-redis-cache-powershell.md#to-reboot-an-azure-cache-for-redis).
+Yes, for PowerShell instructions see [To reboot an Azure Cache for Redis](cache-how-to-manage-redis-cache-powershell.md#to-reboot-an-azure-cache-for-redis).
 
 ## Schedule updates
 The **Schedule updates** blade allows you to designate a maintenance window for your cache instance. When the maintenance window is specified, any Redis server updates are made during this window. 

articles/azure-cache-for-redis/cache-best-practices.md

@@ -27,9 +27,9 @@ By following these best practices, you can help maximize the performance and cos
 
  * **Develop your system such that it can handle connection blips** [because of patching and failover](https://gist.github.com/JonCole/317fe03805d5802e31cfa37e646e419d#file-azureredis-patchingexplained-md).
 
- * **Configure your [maxmemory-reserved setting](cache-configure.md#maxmemory-policy-and-maxmemory-reserved) to improve system responsiveness** under memory pressure conditions.  This setting is especially important for write-heavy workloads or if you're storing larger values (100 KB or more) in Redis.  I would recommend starting with 10% of the size of your cache, then increase if you have write-heavy loads. See [some considerations](cache-how-to-troubleshoot.md#considerations-for-memory-reservations) when selecting a value.
+ * **Configure your [maxmemory-reserved setting](cache-configure.md#maxmemory-policy-and-maxmemory-reserved) to improve system responsiveness** under memory pressure conditions.  This setting is especially important for write-heavy workloads or if you're storing larger values (100 KB or more) in Redis. It's recommended that you start with 10% of the size of your cache and then increase the percentage if you have write-heavy loads.
 
- * **Redis works best with smaller values**, so consider chopping up bigger data into multiple keys.  In [this Redis discussion](https://stackoverflow.com/questions/55517224/what-is-the-ideal-value-size-range-for-redis-is-100kb-too-large/), some considerations are listed that you should consider carefully.  Read [this article](cache-how-to-troubleshoot.md#large-requestresponse-size) for an example problem that can be caused by large values.
+ * **Redis works best with smaller values**, so consider chopping up bigger data into multiple keys.  In [this Redis discussion](https://stackoverflow.com/questions/55517224/what-is-the-ideal-value-size-range-for-redis-is-100kb-too-large/), some considerations are listed that you should consider carefully.  Read [this article](cache-how-to-troubleshoot-client.md#large-request-or-response-size) for an example problem that can be caused by large values.
 
  * **Locate your cache instance and your application in the same region.**  Connecting to a cache in a different region can significantly increase latency and reduce reliability.  While you can connect from outside of Azure, it  not recommended *especially when using Redis as a cache*.  If you're using Redis as just a key/value store, latency may not be the primary concern. 
 
@@ -39,7 +39,7 @@ By following these best practices, you can help maximize the performance and cos
      > [!NOTE]
      > This guidance is specific to the *connection attempt* and not related to the time you're willing to wait for an *operation* like GET or SET to complete.
  
- * **Avoid expensive commands** - Some redis operations, like the [KEYS command](https://redis.io/commands/keys), are *very* expensive and should be avoided.  For more information, see [some considerations around expensive commands](cache-how-to-troubleshoot.md#expensive-commands)
+ * **Avoid expensive operations** - Some Redis operations, like the [KEYS](https://redis.io/commands/keys) command, are *very* expensive and should be avoided.  For more information, see some considerations around [long-running commands](cache-how-to-troubleshoot-server.md#long-running-commands)
 
  * **Use TLS encryption** - Azure Cache for Redis requires TLS encrypted communications by default.  TLS versions 1.0, 1.1 and 1.2 are currently supported.  However, TLS 1.0 and 1.1 are on a path to deprecation industry-wide, so use TLS 1.2 if at all possible.  If your client library or tool doesn't support TLS, then enabling unencrypted connections can be done [through the Azure portal](cache-configure.md#access-ports) or [management APIs](https://docs.microsoft.com/rest/api/redis/redis/update).  In such cases where encrypted connections aren't possible, placing your cache and client application into a virtual network would be recommended.  For details on which ports are used for 
 

articles/azure-cache-for-redis/cache-configure.md

@@ -426,7 +426,7 @@ New Azure Cache for Redis instances are configured with the following default Re
 For more information about databases, see [What are Redis databases?](cache-faq.md#what-are-redis-databases)
 
 > [!NOTE]
-> The `databases` setting can be configured only during cache creation and only using PowerShell, CLI, or other management clients. For an example of configuring `databases` during cache creation using PowerShell, see [New-AzRedisCache](cache-howto-manage-redis-cache-powershell.md#databases).
+> The `databases` setting can be configured only during cache creation and only using PowerShell, CLI, or other management clients. For an example of configuring `databases` during cache creation using PowerShell, see [New-AzRedisCache](cache-how-to-manage-redis-cache-powershell.md#databases).
 > 
 > 
 

articles/azure-cache-for-redis/cache-dotnet-core-quickstart.md

@@ -20,7 +20,7 @@ ms.custom: mvc
 ---
 # Quickstart: Use Azure Cache for Redis with a .NET Core app
 
-In this quickstart, you incorporate Azure Cache for Redis into a .NET Core app to have access to a secure, dedicated cache that is accessible from any application within Azure. You specifically use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) client with C# code in a .NET Core console app. 
+In this quickstart, you incorporate Azure Cache for Redis into a .NET Core app to have access to a secure, dedicated cache that is accessible from any application within Azure. You specifically use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) client with C# code in a .NET Core console app.
 
 ## Prerequisites
 

articles/azure-cache-for-redis/cache-faq.md

@@ -69,7 +69,7 @@ The following FAQs cover basic concepts and questions about Azure Cache for Redi
 * [Performance considerations around connections](#performance-considerations-around-connections)
 
 ## Monitoring and troubleshooting FAQs
-The FAQs in this section cover common monitoring and troubleshooting questions. For more information about monitoring and troubleshooting your Azure Cache for Redis instances, see [How to monitor Azure Cache for Redis](cache-how-to-monitor.md) and [How to troubleshoot Azure Cache for Redis](cache-how-to-troubleshoot.md).
+The FAQs in this section cover common monitoring and troubleshooting questions. For more information about monitoring and troubleshooting your Azure Cache for Redis instances, see [How to monitor Azure Cache for Redis](cache-how-to-monitor.md) and the various troubleshoot guides.
 
 * [How do I monitor the health and performance of my cache?](#how-do-i-monitor-the-health-and-performance-of-my-cache)
 * [Why am I seeing timeouts?](#why-am-i-seeing-timeouts)
@@ -174,7 +174,7 @@ For more information on considerations when using Azure Cache for Redis with oth
 - [Azure China 21Vianet Cloud - Azure Cache for Redis](https://www.azure.cn/home/features/redis-cache/)
 - [Microsoft Azure Germany](https://azure.microsoft.com/overview/clouds/germany/)
 
-For information on using Azure Cache for Redis with PowerShell in Azure Government Cloud, Azure China 21Vianet Cloud, and Microsoft Azure Germany, see [How to connect to other clouds - Azure Cache for Redis PowerShell](cache-howto-manage-redis-cache-powershell.md#how-to-connect-to-other-clouds).
+For information on using Azure Cache for Redis with PowerShell in Azure Government Cloud, Azure China 21Vianet Cloud, and Microsoft Azure Germany, see [How to connect to other clouds - Azure Cache for Redis PowerShell](cache-how-to-manage-redis-cache-powershell.md#how-to-connect-to-other-clouds).
 
 <a name="cache-configuration"></a>
 
@@ -193,6 +193,7 @@ Usually the default values of the client are sufficient. You can fine-tune the o
   * For ConnectRetry and ConnectTimeout, the general guidance is to fail fast and retry again. This guidance is based on your workload and how much time on average it takes for your client to issue a Redis command and receive a response.
   * Let StackExchange.Redis automatically reconnect instead of checking connection status and reconnecting yourself. **Avoid using the ConnectionMultiplexer.IsConnected property**.
   * Snowballing - sometimes you may run into an issue where you are retrying and the retries snowball and never recovers. If snowballing occurs, you should consider using an exponential backoff retry algorithm as described in [Retry general guidance](../best-practices-retry-general.md) published by the Microsoft Patterns & Practices group.
+  
 * **Timeout values**
   * Consider your workload and set the values accordingly. If you are storing large values, set the timeout to a higher value.
   * Set `AbortOnConnectFail` to false and let StackExchange.Redis reconnect for you.
@@ -439,7 +440,7 @@ These tools enable you to monitor the health of your Azure Cache for Redis insta
 <a name="cache-timeouts"></a>
 
 ### Why am I seeing timeouts?
-Timeouts happen in the client that you use to talk to Redis. When a command is sent to the Redis server, the command is queued up and Redis server eventually picks up the command and executes it. However the client can time out during this process and if it does an exception is raised on the calling side. For more information on troubleshooting timeout issues, see [Client-side troubleshooting](cache-how-to-troubleshoot.md#client-side-troubleshooting) and [StackExchange.Redis timeout exceptions](cache-how-to-troubleshoot.md#stackexchangeredis-timeout-exceptions).
+Timeouts happen in the client that you use to talk to Redis. When a command is sent to the Redis server, the command is queued up and Redis server eventually picks up the command and executes it. However the client can time out during this process and if it does an exception is raised on the calling side. For more information on troubleshooting timeout issues, see [client-side troubleshooting](cache-how-to-troubleshoot-client.md) and [StackExchange.Redis timeout exceptions](cache-how-to-troubleshoot-timeouts.md#stackexchangeredis-timeout-exceptions).
 
 <a name="cache-disconnect"></a>