Is it possible to backup to Microsoft Azure Blob-storage ? I want to store 5TB per year for 5 years. Resulting in 25TB at year 5 and after that rollover, delete the oldest 5tb in with new 5tb on year 6 and so on. It seems VERY cheap actually.
The exact storage name is "Block Blob Storage, General Purpose V2, Flat Namespace, LRS Redundancy, Cold Access Tier, 25 TB Capacity - Pay as you go, 10 x 10,000 Write operations, 10 x 10,000 List and Create Container Operations, 10 x 10,000 Read operations, 1 x 10,000 Other operations. 1,000 GB Data Retrieval, 1,000 GB Data Write"
The full spec of my proposed storage as on the link below.
https://azure.com/e/088c2af6e5a14acd80718e5bcb5ea907
-
- Novice
- Posts: 8
- Liked: 1 time
- Joined: Apr 04, 2014 6:53 am
- Contact:
-
- Chief Product Officer
- Posts: 32217
- Liked: 7583 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Backup to Azure blob storage
Before V12, you could only copy backups to object storage. This is the right way and the best practice from backup and DR perspective so we highly recommend you do that.
Starting V12, you can also backup direct to object storage. However, there are many reasons why you don't want to backup directly to cloud object storage. And while it might tempting to just go directly to cheap cloud object storage, we don't really do backups to save money - but to be able to restore our data from any type of disaster and do it quickly.
Starting V12, you can also backup direct to object storage. However, there are many reasons why you don't want to backup directly to cloud object storage. And while it might tempting to just go directly to cheap cloud object storage, we don't really do backups to save money - but to be able to restore our data from any type of disaster and do it quickly.
-
- Novice
- Posts: 8
- Liked: 1 time
- Joined: Apr 04, 2014 6:53 am
- Contact:
Re: Backup to Azure blob storage
Hello,
We have a local repo with 150TB NVME drives for fast backup an recovery then we do have SOBR to Wasabi. This Azure blob is only to be used for VERY cold storage. It's yearly backups if and when we need to go back in economic transactions if and when the government/accounting firm needs proof of transactions. IN the last 20 years it has never actually been used because we also keep all these transactions in our systems. But we are still obligated by law to keep these transactions for at least 8 years.
We have a local repo with 150TB NVME drives for fast backup an recovery then we do have SOBR to Wasabi. This Azure blob is only to be used for VERY cold storage. It's yearly backups if and when we need to go back in economic transactions if and when the government/accounting firm needs proof of transactions. IN the last 20 years it has never actually been used because we also keep all these transactions in our systems. But we are still obligated by law to keep these transactions for at least 8 years.
-
- Chief Product Officer
- Posts: 32217
- Liked: 7583 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Backup to Azure blob storage
Got it. Then it seems like new V12 capabilities are a good fit for your use case.
You could also consider SOBR with both Capacity Tier and Archive Tier on Azure though. While Capacity Tier will be more expensive with Azure than with Wasabi, Archive Tier will be so much cheaper as it is able to leverage Archive class storage. This one is perfect for "Write Once Read Never" type of use cases, and across 8 years it might present significant cost savings. Perhaps you should do the math of total costs across 8 years and decide. Keep in mind the added technical benefit too: with this approach, you won't have to push TBs of data to cloud twice (first to Wasabi, then to Azure). In case available bandwidth and/or time it takes is a concern with 5TB worth of backups to upload.
You could also consider SOBR with both Capacity Tier and Archive Tier on Azure though. While Capacity Tier will be more expensive with Azure than with Wasabi, Archive Tier will be so much cheaper as it is able to leverage Archive class storage. This one is perfect for "Write Once Read Never" type of use cases, and across 8 years it might present significant cost savings. Perhaps you should do the math of total costs across 8 years and decide. Keep in mind the added technical benefit too: with this approach, you won't have to push TBs of data to cloud twice (first to Wasabi, then to Azure). In case available bandwidth and/or time it takes is a concern with 5TB worth of backups to upload.
Who is online
Users browsing this forum: No registered users and 8 guests