We have an onpremise Veeam server that runs the following jobs:
1. Backup to local storage (weekly full, daily incrementals)
2. Copy job to Linux hardened repository (immutable)
3. Copy job to Azure Blob cool storage (immutable)
Now i would like to have the Azure monthly backups moved to archive tier. I'm assuming i have to use SOBR for this. The following question arise:
- i create a second immutable repository with longer immutability, say 1 year. After moving the full backup, will it calculate ‘initial backup date + 1 year’, or ‘SOBR copy date + 1 year’?
- do i need a new container for this or can i just create a folder within a container?
- if a backup is still immutable can it be moved to the archive tier?
- copying backups obviously generates a large amount of traffic. Download backup from one repository, upload to another. Is there something i can do to limit the amount of traffic and costs?
- what's the risk here? To move data the local Veeam server needs to have modify permissions in both the cool and archive repository. Theoretically a hacker with access to the backup server could stop it copying to archive repository, but still delete from cool repository?
Best answer by MicoolPaul
View original