technical background question about copy Backup jobs

[TheBrain82]

Hello Dear Veeam community,

the Veeam support told me to open a new topic inside of this Forum based on case Case-Nr.05347042.

My question is quite simple. We would like to setup many new backup copy jobs, based to the new features what came with v6 version. In our scenario the vbo and the proxies are running in the public cloud on azure. They are using Azure cool Object storage.

Now we would like to set up copy backup jobs to copy all backed up data older than 30 days to Az-ure archive Object storage for a long time.

Now, before we start to copy hundreds of TB from "Azure cool Object storage" to "Azure archive Object storage" we would like to know, what kind of get-operations on "Azure cool Object storage" and what kind of put-operations on "Azure archive Object storage" will be generated, when for exam-ple 1TB of Backup-Data gets copied between both types of Object Storage?

Especially when a "get" on the "Azure cool Object storage" does differ between "Read operations (per 10,000)" $ or "Iterative Read Operations (per 10,000)" in $ or "Data Retrieval (per GB)" in $?
Also for a "put" on "Azure archive Object storage" does differ between "Write operations (per 10,000)" in $ or "Iterative write operations (100s)" in $ or "Data Write (per GB)" in $?
(see https://azure.microsoft.com/en-gb/prici ... age/blobs/ at "Operations and data trans-fer")

The same questions also comes up in case of an item restore from data what resides on "Azure ar-chive Object storage".

At the end all information’s are required to plan a migration scenario from technical point of few and to calculate the costs against the savings by using "Azure archive Object storage".

It would be great and perfect if these missing information’s would be added here at the end.
https://bp.veeam.com/vbo/guide/design/s ... orage.html .

Cheers and best regards,

[Mildur]

Hi Oleg

I'm very sorry for the late answer.
I see on the case internal notes that the discussion between support and RnD for both of your questions is happening.

Now we would like to set up copy backup jobs to copy all backed up data older than 30 days to Azure archive Object storage for a long time.

The backup copy Job will copy all items and doesn't have a time based filter.
You can use a retention of 30 days on your primary object storage repository and a longer retention on your archive object storage repository. That should achieve your goal.

[Polina]

Small addition to the above.
Backup copy always transfers the latest restore point according to the schedule that you set in its configuration.
And the BP guide will soon be updated with the average number of operations required for copying and data retrievals. Unfortunately, I cannot provide them right now, tests are in progress at the moment.