Minimal cost offsite backup

Question

Raw beginner on Azure. I have managed to create and access a storage account, (and tested the ability to backup from my server to Azure) but I need advice on optimal configuration to minimize cost (anything created to date can be deleted)

I have several TB of data on a home server, and I need off-site backup just to provide a recovery path in the event of (for example) catastrophic failure of my server. So, I want to be able to one-way sync on a regular basis to capture new/changed data. In a perfect world, I will never access the azure files and, if I do, there is no requirement for immediacy -- if necessary, I could wait some days. I would prefer to be able to be selective on which folders/files are restored in a given session.

As noted above, I am looking for the most economical solution, and I am lost in all the blob/file choices, etc.

I am sure this is all well documented, but I am struggling to find the basics andf create an optimal solution. Thanks in anticipation

peter

Answer 1

Hello Peter Symes

Thank you for posting your query on Microsoft Q&A platform.

Based on your requirements (multi‑TB off‑site backup, one‑way sync, very rare access, no immediacy required, lowest possible cost), It is recommended to user Azure Blob Storage with the Archive access tier for this scenario.

Azure Blob Storage is designed for storing large amounts of unstructured data at the lowest storage cost, especially when data is rarely accessed.

The archive tier is an offline tier for storing data that is rarely accessed and has the lowest storage cost.

Azure Files is intended for live file shares (SMB/NFS) and is not cost‑optimized for cold off‑site backups. Azure Backup adds per‑instance and management costs and is meant for managed recovery scenarios, not simple cold storage backups.

Follow below supported approach:

1. Create a General‑purpose v2 storage account
2. Upload backup data to the Cool tier
3. Use a Lifecycle Management policy to move data to the Archive tier

You can’t write data directly to the archive tier. Data must be uploaded to hot or cool and then moved to archive.”

Lifecycle Management is the recommended and supported method for automating this tier transition.

Restore Behaviour:

• Archive tier data is offline
• Restore (rehydration) takes hours
• Retrieval costs are higher, but expected for disaster recovery scenarios

So, the Data in the archive tier must be rehydrated before access, which can take several hours.

The most economical and recommended solution for your scenario is:

• Azure Blob Storage (General‑purpose v2)
• LRS redundancy
• Cool tier for ingestion
• Lifecycle policy to Archive tier
• Restore only when required

This is the lowest‑cost storage option Microsoft provides for rarely accessed, large‑scale backup data.

Refer the below documents for additional details:

1. Archive tier overview and cost behavior https://learn.microsoft.com/azure/storage/blobs/archive-cost-estimation
2. Azure Backup pricing (shows additional cost components) https://azure.microsoft.com/pricing/details/backup/

This approach follows storage design guidance for cold, rarely accessed backup data and avoids unnecessary services or costs that are not required for the stated recovery objectives.

Please let us know if the suggested resolution helped/ addressed your concern. If it did, we’d appreciate your feedback on the proposed resolution as it helps others with similar issues.

If the resolution did not help, feel free to share more details about the challenge you’re still facing.

We’re happy to continue assisting and work with you toward the right solution.

Thanks,

Suchitra.

Answer 2

To minimize costs for offsite backup to Azure while ensuring you have a recovery path, consider the following strategies:

1. Use the Archive Storage Tier: Since you mentioned that you will not frequently access the files and can wait for days if needed, the Archive storage tier is the most economical option. It has the lowest storage costs, although it incurs higher access and transaction costs when you need to retrieve data.
2. Incremental Backups: Instead of performing full backups every time, implement incremental backups. This method captures only the changes made since the last backup, reducing the amount of data transferred and stored, which can significantly lower costs.
3. Backup Compression: Enable compression during the backup process to reduce the size of backup files. This will save on storage costs as well.
4. Selective Backup and Restore: Ensure that your backup solution allows for selective backup and restoration of files and folders. This way, you can choose to backup only the most critical data, further optimizing your costs.
5. Review Retention Policies: Adjust your backup retention policies based on your business needs. Keeping backups for shorter durations can help reduce storage costs.
6. Evaluate Network Bandwidth: Consider using Azure Data Box for initial data transfer if your internet bandwidth is limited. This can help you avoid high costs associated with data transfer over the internet.

By following these strategies, you can create a cost-effective backup solution that meets your needs for offsite storage and recovery.

---

References:

• Optimize backups
• Backup to Azure with DobiProtect