Skip to content

Commit 558e021

Browse files
Merge pull request #265917 from ChaseCrum/CEOL-3
EOL message insert
2 parents 73a1a0e + 8d42ba9 commit 558e021

10 files changed

+32
-2
lines changed

articles/site-recovery/azure-stack-site-recovery.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ ms.service: site-recovery
99
---
1010
# Replicate Azure Stack VMs to Azure
1111

12+
> [!CAUTION]
13+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
14+
1215
This article shows you how to set up disaster recovery Azure Stack VMs to Azure, using the [Azure Site Recovery service](site-recovery-overview.md).
1316

1417
Site Recovery contributes to your business continuity and disaster recovery (BCDR) strategy. The service ensures that your VM workloads remain available when expected and unexpected outages occur.
@@ -320,4 +323,4 @@ In this article we replicated Azure Stack VMs to Azure. With replication in plac
320323

321324
## Next steps
322325

323-
After failing back, you can reprotect the VM and start replicating it to Azure again To do this, repeat the steps in this article.
326+
After failing back, you can reprotect the VM and start replicating it to Azure again To do this, repeat the steps in this article.

articles/site-recovery/azure-to-azure-support-matrix.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ ms.custom: engagement-fy23, references_regions
1111

1212
# Support matrix for Azure VM disaster recovery between Azure regions
1313

14+
> [!CAUTION]
15+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
16+
1417
This article summarizes support and prerequisites for disaster recovery of Azure VMs from one Azure region to another, using the [Azure Site Recovery](site-recovery-overview.md) service.
1518

1619
## Deployment method support

articles/site-recovery/azure-to-azure-troubleshoot-errors.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.custom: engagement-fy23
1212

1313
# Troubleshoot Azure-to-Azure VM replication errors
1414

15+
> [!CAUTION]
16+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
17+
1518
This article describes how to troubleshoot common errors in Azure Site Recovery during replication and recovery of [Azure virtual machines](azure-to-azure-tutorial-enable-replication.md) (VM) from one region to another. For more information about supported configurations, see the [support matrix for replicating Azure VMs](azure-to-azure-support-matrix.md).
1619

1720
## Azure resource quota issues (error code 150097)

articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.custom: engagement-fy23
1313
---
1414
# Accelerated Networking with Azure virtual machine disaster recovery
1515

16+
> [!CAUTION]
17+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
18+
1619
Accelerated Networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the datapath, reducing latency, jitter, and CPU utilization, for use with the most demanding network workloads on supported VM types. The following picture shows communication between two VMs with and without accelerated networking:
1720

1821
:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png" alt-text="Screenshot of difference between accelerated and non-accelerated networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png":::

articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.date: 08/01/2023
1212

1313
# Replicate virtual machines running in a proximity placement group to another region
1414

15+
> [!CAUTION]
16+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
17+
1518
This article describes how to replicate, fail over, and fail back Azure virtual machines (VMs) running in a proximity placement group to a secondary region.
1619

1720
[Proximity placement groups](../virtual-machines/windows/proximity-placement-groups-portal.md) are a logical grouping capability in Azure Virtual Machines. You can use them to decrease the inter-VM network latency associated with your applications.

articles/site-recovery/site-recovery-failover-to-azure-troubleshoot.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ ms.author: ankitadutta
1111
---
1212
# Troubleshoot errors when failing over VMware VM or physical machine to Azure
1313

14+
> [!CAUTION]
15+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
16+
1417
You may receive one of the following errors while doing failover of a virtual machine to Azure. To troubleshoot, use the described steps for each error condition.
1518

1619
## Failover failed with Error ID 28031

articles/site-recovery/site-recovery-whats-new-archive.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ ms.date: 12/27/2023
1010

1111
# Archive for What's new in Site Recovery
1212

13+
> [!CAUTION]
14+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
15+
1316
This article contains information on older features and updates in the Azure Site Recovery service. The primary [What's new in Azure Site Recovery](./site-recovery-whats-new.md) article contains the latest updates.
1417

1518
## Updates (November 2021)

articles/storage/blobs/storage-how-to-mount-container-linux.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.custom: engagement-fy23, linux-related-content
1313

1414
# How to mount Azure Blob Storage as a file system with BlobFuse v1
1515

16+
> [!CAUTION]
17+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
18+
1619
> [!IMPORTANT]
1720
> [BlobFuse2](blobfuse2-what-is.md) is the latest version of BlobFuse and has many significant improvements over the version discussed in this article, BlobFuse v1. To learn about the improvements made in BlobFuse2, see [the list of BlobFuse2 enhancements](blobfuse2-what-is.md#blobfuse2-enhancements-from-blobfuse-v1).
1821

articles/storage/files/files-remove-smb1-linux.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ ms.author: kendownie
99
---
1010

1111
# Remove SMB 1 on Linux
12+
13+
> [!CAUTION]
14+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
1215
Many organizations and internet service providers (ISPs) block the port that SMB uses to communicate, port 445. This practice originates from security guidance about legacy and deprecated versions of the SMB protocol. Although SMB 3.x is an internet-safe protocol, older versions of SMB, especially SMB 1, aren't. SMB 1, also known as CIFS (Common Internet File System), is included with many Linux distributions.
1316

1417
SMB 1 is an outdated, inefficient, and insecure protocol. The good news is that Azure Files doesn't support SMB 1. Also, starting with Linux kernel version 4.18, Linux makes it possible to disable SMB 1. We always [strongly recommend](https://aka.ms/stopusingsmb1) disabling the SMB 1 on your Linux clients before using SMB file shares in production.
@@ -97,4 +100,4 @@ See these links for more information about Azure Files:
97100
- [Planning for an Azure Files deployment](storage-files-planning.md)
98101
- [Use Azure Files with Linux](storage-how-to-use-files-linux.md)
99102
- [Troubleshoot SMB issues on Linux](/troubleshoot/azure/azure-storage/files-troubleshoot-linux-smb?toc=/azure/storage/files/toc.json)
100-
- [Troubleshoot NFS issues on Linux](/troubleshoot/azure/azure-storage/files-troubleshoot-linux-nfs?toc=/azure/storage/files/toc.json)
103+
- [Troubleshoot NFS issues on Linux](/troubleshoot/azure/azure-storage/files-troubleshoot-linux-nfs?toc=/azure/storage/files/toc.json)

articles/storage/files/storage-how-to-use-files-linux.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ ms.author: kendownie
1010
---
1111

1212
# Mount SMB Azure file share on Linux
13+
14+
> [!CAUTION]
15+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
1316
[Azure Files](storage-files-introduction.md) is Microsoft's easy to use cloud file system. Azure file shares can be mounted in Linux distributions using the [SMB kernel client](https://wiki.samba.org/index.php/LinuxCIFS).
1417

1518
The recommended way to mount an Azure file share on Linux is using SMB 3.1.1. By default, Azure Files requires encryption in transit, which is supported by SMB 3.0+. Azure Files also supports SMB 2.1, which doesn't support encryption in transit, but you can't mount Azure file shares with SMB 2.1 from another Azure region or on-premises for security reasons. Unless your application specifically requires SMB 2.1, use SMB 3.1.1.

0 commit comments

Comments
 (0)