Merge pull request #309607 from akarshprabhu/main

Archive tier support for CRR unsupported doc changes

Author: prmerger-automator[bot]

articles/backup/archive-tier-support.md

@@ -24,7 +24,7 @@ Archive tier supports the following workloads:
 
 | Workloads | Operations |
 | --- | --- |
-| Azure Virtual Machines | Only monthly and yearly recovery points. Daily and weekly recovery points aren't supported.  <br><br> Age >= 3 months in Vault-standard tier <br><br> Retention left >= 6 months. <br><br> No active on-demand, daily, and weekly dependencies. There are no un-expired daily or weekly recovery points between the recovery point considered for archival and the next monthly or yearly recovery point. |
+| Azure Virtual Machines | Only monthly and yearly recovery points. Daily and weekly recovery points aren't supported.  <br><br> Age >= 3 months in Vault-standard tier <br><br> Retention left >= 6 months. <br><br> No active on-demand, daily, and weekly dependencies. There are no unexpired daily or weekly recovery points between the recovery point considered for archival and the next monthly or yearly recovery point. |
 | SQL Server in Azure Virtual Machines <br><br> SAP HANA in Azure Virtual Machines | Only full recovery points. Logs and differentials aren't supported. <br><br> Age >= 45 days in Vault-standard tier. <br><br> Retention left >= 6 months. <br><br>  No dependencies. |
 
 A recovery point becomes archivable only if all the above conditions are met.
@@ -33,7 +33,7 @@ A recovery point becomes archivable only if all the above conditions are met.
 > Archive tier support for Azure Virtual Machines, SQL Servers in Azure VMs and SAP HANA in Azure VM is now generally available in multiple regions. For the detailed list of supported regions, see the [supported regions](#supported-regions).
 
 > [!CAUTION]
-> Archive tier is not supported on vaults configured with ZRS storage.
+> Archive tier isn't supported on vaults configured with ZRS storage.
 
 ### Supported clients
 
@@ -55,12 +55,12 @@ Archive tier supports the following clients:
 
 ## Archive recommendations (only for Azure Virtual Machines)
 
-The recovery points for Azure Virtual Machines are incremental. When you move recovery points to archive tier, they're converted to full recovery points (to ensure that all recovery points in Archive tier are independent and isolated from each other). Thus, overall backup storage (Vault-standard + Vault-archive) may increase.
+The recovery points for Azure Virtual Machines are incremental. When you move recovery points to archive tier, they're converted to full recovery points (to ensure that all recovery points in Archive tier are independent and isolated from each other). Thus, overall backup storage (Vault-standard + Vault-archive) might increase.
 
 The amount of storage increase depends on the churn pattern of the Virtual Machines.
 
 - The higher the churn in the Virtual Machines, lesser is the overall backup storage when a recovery point is moved to archive tier.
-- If the churn in the Virtual Machine is low, moving to Archive tier may lead to increase in Backup storage. This may offset the price difference between the Vault-standard tier and Vault-archive tier. Therefore, that might increase the overall cost.
+- If the churn in the Virtual Machine is low, moving to Archive tier might lead to increase in Backup storage. This might offset the price difference between the Vault-standard tier and Vault-archive tier. Therefore, that might increase the overall cost.
 
 To resolve this, Azure Backup provides recommendation set. The recommendation set returns a list of recovery points, which if moved together to Archive tier ensures cost savings.
 
@@ -96,19 +96,19 @@ You can view the Archive tier pricing from our [pricing page](https://azure.micr
 
 ## Frequently asked questions
 
-### What will happen to archive recovery points if I stop protection and retain data?
+### What happens to archive recovery points if I stop protection and retain data?
 
-The recovery point will remain in archive forever. For more information, see [Impact of stop protection on recovery points](manage-recovery-points.md#impact-of-stop-protection-on-recovery-points).
+The recovery point remains in archive forever. For more information, see [Impact of stop protection on recovery points](manage-recovery-points.md#impact-of-stop-protection-on-recovery-points).
 
 ### Is Cross Region restore supported from archive tier?
 
-When you move your data in GRS vaults from standard tier to archive tier, the data moves into GRS archive. This is true even when Cross region restore is enabled. Once the backup data moves into archive tier, you can’t restore the data into the paired region. However, during region failures, the backup data in secondary region will become available for restore. 
-
-When you restore from recovery point in Archive tier in primary region, the recovery point is copied to the Standard tier and is retained according to the rehydration duration, both in primary and secondary region. You can perform Cross region restore from these rehydrated recovery points.
+No. Cross‑Region Restore (CRR) from Archive‑tier recovery points - including recovery points that are rehydrated into Standard tier during restore. When a recovery point is restored from Archive tier, it's temporarily rehydrated into Standard tier for use *only within the source region*.  
+Rehydration doesn't make the recovery point eligible for Cross‑Region Restore. CRR validation requires metadata markers that aren't preserved after rehydration, and attempting CRR from rehydrated Archive RPs might fail.  
+To perform Cross‑Region Restore, use a Recovery Point that resides in Standard tier.
 
 ### I can see eligible recovery points for my Virtual Machine, but I can't seeing any recommendation. What can be the reason?
 
-The recovery points for Virtual Machines meet the eligibility criteria. So, there are archivable recovery points. However, the churn in the Virtual Machine may be low, thus there are no recommendations. In this scenario, though you can move the archivable recovery points to archive tier, but it may increase the overall backup storage costs.
+The recovery points for Virtual Machines meet the eligibility criteria. So, there are archivable recovery points. However, the churn in the Virtual Machine might be low, thus there are no recommendations. In this scenario, though you can move the archivable recovery points to archive tier, but it might increase the overall backup storage costs.
 
 ### How do I ensure that all recovery points are moved to Archive tier, if moved via Azure portal?
 
@@ -123,7 +123,7 @@ If the list of recovery points is blank, then all the eligible/recommended recov
 
 No. Currently, the **File Recovery** option doesn't support restoring specific files from an archived recovery point of an Azure VM backup.
 
-### What are the possible reasons if my VM recovery point was not moved to archive?
+### What are the possible reasons if my VM recovery point wasn't moved to archive?
 
 Before you move VM recovery points to archive tier, ensure that the following criteria are met:
 
@@ -147,7 +147,6 @@ No, after moving the recovery point to the archive tier, it can't return to the
 >[!Note]
 >You can do the rehydration process during the restore from a recovery point only.
 
-
 ## Next steps
 
 - [Use Archive tier](use-archive-tier-support.md).