PC backup with Veeam Agent to Azure

[jcofin13]

I have a pc that has been getting backed up locally via the stand alone agent. ITs now a requirement that the machine be also backed up offsite.
Object storage from Azure blob storage will be used.

I am unclear when you would set for the azure blob storage settings on the azure side. When do you select Hot or Cool? Is once per day considered hot and once per week considered cool......or once per month etc. Once the main seed gets uploaded (~700gb) i would expect any change data to be quite small.

Also i am curious about names or the folder structure in azure.
Is it such were you create a container called "WorkstationBackups" and inside that create a folder with the PCs name. Will Veeam create the "veeam" folder and all subfolders under that when the first backup runs or as you setup the agent job to connect to that container and folder?

[david.domask]

Hi jcofin13,

I've moved your topic to our Object Storage as Backup Target forum as seems the questions are more about the structure of our backups on Object Storage / using Object Storage repositories.

>When do you select Hot or Cool?

The access tier is set when adding the Object Storage Repository

> Also i am curious about names or the folder structure in azure.

Object Storage repositories use a unique structure to optimize storage usage and reduce API calls to the Object Storage target. Creating the repository will create the necessary base structure, and additional folders (actually prefixes) will be added underneath those to store the metadata and the actual backup data.

You do not need to engage directly with the data on the object storage repository and must not. It is not simply storing VBKs / VIBs like you're maybe expecting, it uses a different structure.