If you are using the NAS Proxy-based protection approach to protect your Azure Files SMB shares, you must migrate your existing backupsets and policies to the new Azure Files Cloud-Native protection.
Prerequisites
One or more NAS backupsets protecting Azure Files SMB shares.
A target storage account configured for Public access, and ‘accessible from all networks’.
Migration Process
There is no automated migration process for existing NAS Proxy-based backupsets. Migration requires setting up the cloud-native protection in parallel:
Follow the [Azure Files - Onboarding] instructions to onboard your Azure Files SMB shares for the new cloud-native protection.
Deduplication Benefit: Your new Azure Files cloud-native backups will automatically deduplicate against your prior NAS Proxy-based backups if you select the same cloud and storage region.
Post-Migration Cleanup
After successfully onboarding your Azure Files shares, you must disable the old NAS Proxy-based backups to eliminate redundancy.
Procedure to Disable Old Backups
Log in to the Management Console.
Select your Organization.
Navigate to the NAS section.
Search for the backup set in All Backupsets.
Click Disable backup.
Historical Recovery & Cost Considerations
Historical Recovery: To recover your historical Azure Files backups taken using the NAS Proxy, you must keep the NAS Proxy available in your Azure subscription.
TCO Benefit: We strongly recommend shutting down the NAS Proxy VM after migration to reduce any ongoing Microsoft runtime costs.
Note:
You can also scale down the CPU, RAM for your NAS Proxy, as it will only be performing restore actions. Contact Support, and we can help you re-configure your NAS Proxy for its reduced workload and ensure its costs are optimized.