Hi Martijn
I assume you are using an on-prem performance and Azure Blob capacity tier?
With our Backup to Tape job, you cannot select "2 year old backups" to be written to tape. And we don't pull backups from Capacity Tier with such job, only from the performance tier. Backup To Tape jobs always write the most recent restore points to Tape.
A File To Tape job would be able to write these backups to tape, by selecting the 2 year old backup files. The backups have to be first stored as backup files on performance tier or any other non-object storage repository. You can
export or download them to a local disk. Then use a File To Tape job to write it to the tape.
Please note, downloading backups from Azure Blob to the performance tier may be very expensive. Microsoft will bill you for all the API calls and egress traffic of your backup files. It's better to write Tapes directly from your primary backup on performance tier or standalone on-premise backup repositories.
If you have backups on Azure Blob, then I recommend to send them to immutable Azure Archive Storage for long term retention requirements. This allows you to keep GFS backups for a long time on cheaper storage.
Can you please share the main use case why are you writing backups to tapes? Compliance reasons? Or to remove backups from Azure Blob to save money?
Best,
Fabian
I assume you are using an on-prem performance and Azure Blob capacity tier?
With our Backup to Tape job, you cannot select "2 year old backups" to be written to tape. And we don't pull backups from Capacity Tier with such job, only from the performance tier. Backup To Tape jobs always write the most recent restore points to Tape.
A File To Tape job would be able to write these backups to tape, by selecting the 2 year old backup files. The backups have to be first stored as backup files on performance tier or any other non-object storage repository. You can
export or download them to a local disk. Then use a File To Tape job to write it to the tape.
Please note, downloading backups from Azure Blob to the performance tier may be very expensive. Microsoft will bill you for all the API calls and egress traffic of your backup files. It's better to write Tapes directly from your primary backup on performance tier or standalone on-premise backup repositories.
If you have backups on Azure Blob, then I recommend to send them to immutable Azure Archive Storage for long term retention requirements. This allows you to keep GFS backups for a long time on cheaper storage.
How are you "deleting manually from Azure Blob? Manual interaction outside of VBR console on Azure Blob is not supported.so that we don't have to manually add backs to our tape machine and deleted them manual from the Azure blob storage.
Can you please share the main use case why are you writing backups to tapes? Compliance reasons? Or to remove backups from Azure Blob to save money?
Best,
Fabian
Statistics: Posted by Mildur — Jan 09, 2025 8:59 am
