You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cyclecloud/cycleserver-configuration-reference.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
title: CycleServer Configuration Reference
3
3
description: Configuration reference for cycle_server.properties file
4
4
author: atomic-penguin
5
-
ms.date: 07/15/2024
5
+
ms.date: 03/28/2025
6
6
ms.author: erwolfe
7
7
---
8
8
9
9
# CycleServer Configuration
10
10
11
-
CycleCloud uses the _cycle_server.properties_ fileto pass configuration parameters to the CycleServer application and application server (Tomcat). The most common reason for updating this file is to configure SSL for the application server. For more information, see the [SSL Configuration How-to Guide](./how-to/ssl-configuration.md).
11
+
CycleCloud uses the _cycle_server.properties_ file, located under the `/opt/cycle_server/config/` directory on Linux systems, to pass the configuration parameters to the CycleServer application and Tomcat application server. The most common reason for updating this file is to configure SSL for the application server. For more information, see the [SSL Configuration How-to Guide](./how-to/ssl-configuration.md).
12
12
13
13
> [!IMPORTANT]
14
14
> When editing the _cycle_server.properties_ file, first look for preexisting key-value definitions. If the file contains more than one definition, the **last** one is in effect.
Copy file name to clipboardExpand all lines: articles/storage/files/files-disaster-recovery.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,20 @@ Microsoft strives to ensure that Azure services are always available. However, u
15
15
> [!IMPORTANT]
16
16
> Azure File Sync only supports storage account failover if the Storage Sync Service is also failed over. This is because Azure File Sync requires the storage account and Storage Sync Service to be in the same Azure region. If only the storage account is failed over, sync and cloud tiering operations will fail until the Storage Sync Service is failed over to the secondary region. If you want to fail over a storage account containing Azure file shares that are being used as cloud endpoints in Azure File Sync, see [Azure File Sync disaster recovery best practices](../file-sync/file-sync-disaster-recovery-best-practices.md) and [Azure File Sync server recovery](../file-sync/file-sync-server-recovery.md).
17
17
18
+
## Applies to
19
+
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
Customer-managed planned failover can also be utilized in multiple scenarios, including planned disaster recovery testing, a proactive approach to large scale disasters, or to recover from non-storage related outages.
@@ -42,12 +56,12 @@ The cost of DR generally increases with lower or zero RPO/RTO. Companies that ne
42
56
43
57
Azure Files offers different redundancy options to protect your data from planned and unplanned events ranging from transient hardware failures, network and power outages, to natural disasters. All Azure file shares can use locally redundant (LRS) or zone-redundant storage (ZRS). For more information, see [Azure Files redundancy](files-redundancy.md).
44
58
45
-
Azure Files supports account failover for standard storage accounts configured with geo-redundant storage (GRS) and geo-zone redundant storage (GZRS) for protection against regional outages. With account failover, you can initiate the failover process for your storage account if the primary endpoint becomes unavailable. The failover updates the secondary endpoint to become the primary endpoint for your storage account. Once the failover is complete, clients can begin writing to the new primary endpoint.
59
+
Azure Files supports account failover for HDD file shares configured with geo-redundant storage (GRS) and geo-zone redundant storage (GZRS) for protection against regional outages. With account failover, you can initiate the failover process for your storage account if the primary endpoint becomes unavailable. The failover updates the secondary endpoint to become the primary endpoint for your storage account. Once the failover is complete, clients can begin writing to the new primary endpoint.
46
60
47
61
GRS and GZRS still carry a [risk of data loss](#anticipate-data-loss) because data is copied to the secondary region asynchronously, meaning there's a delay before a write to the primary region is copied to the secondary region. In the event of an outage, write operations to the primary endpoint that haven't yet been copied to the secondary endpoint will be lost. This means a failure that affects the primary region might result in data loss if the primary region can't be recovered. The interval between the most recent writes to the primary region and the last write to the secondary region is the RPO. Azure Files typically has an RPO of 15 minutes or less, although there's currently no SLA on how long it takes to replicate data to the secondary region.
48
62
49
63
> [!IMPORTANT]
50
-
> GRS/GZRS aren't supported for premium Azure file shares. However, you can [sync between two Azure file shares](https://github.com/Azure-Samples/azure-files-samples/tree/master/SyncBetweenTwoAzureFileSharesForDR) to achieve geographic redundancy.
64
+
> GRS/GZRS aren't supported for SSD file shares. However, you can [sync between two Azure file shares](https://github.com/Azure-Samples/azure-files-samples/tree/master/SyncBetweenTwoAzureFileSharesForDR) to achieve geographic redundancy.
Copy file name to clipboardExpand all lines: articles/synapse-analytics/sql/tutorial-external-tables-using-managed-identity.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ To enable your managed identity to access data on ADLS Gen2 accounts, you need t
40
40
Your workspace identity is now a member of the Storage Blob Data Contributor role and has access to the source folder.
41
41
42
42
> [!NOTE]
43
-
> These steps also apply to secure ADLS Gen2 accounts that are configured to restrict public access. If your storage account is associated with a secured ADLS Gen2 account or associated with a VNet, you must authenticate using a managed identity. To learn more about securing your ADLS Gen2 account, see [Configure Azure Storage firewalls and virtual networks](/azure/storage/common/storage-network-security).
43
+
> These steps also apply to secure ADLS Gen2 accounts that are configured to restrict public access. If your storage account is associated with a secured ADLS Gen2 account or associated with a VNet, the external table or COPY INTO command must use a managed identity. To learn more about securing your ADLS Gen2 account, see [Configure Azure Storage firewalls and virtual networks](/azure/storage/common/storage-network-security).
0 commit comments