Offload to Azure Blob Storage does not work

[rjv1971]

I have a question on this also. I have setup my performance tier / capacity tier (Azure). in my performance tier I see this for the backup copy job:

06/06/2019 01:34 PM 2,325,756,928 SERVER2.vm-987654D2019-06-06T000040_2FDC.vbk
06/06/2019 01:33 PM 45,712,384 SERVER2.vm-987654D2019-06-06T133308_89FD.vib
06/07/2019 06:00 AM 54,690,816 SERVER2.vm-987654D2019-06-07T060000_6293.vib
06/08/2019 06:00 AM 56,403,456 SERVER2.vm-987654D2019-06-08T060000_0BE0.vib
06/09/2019 06:00 AM 54,406,656 SERVER2.vm-987654D2019-06-09T060000_0ECE.vib
06/10/2019 06:00 AM 55,037,440 SERVER2.vm-987654D2019-06-10T060000_38DB.vib
06/10/2019 01:54 PM 44,352,512 SERVER2.vm-987654D2019-06-10T135414_BC95.vib
06/10/2019 01:56 PM 2,276,101,120 SERVER2.vm-987654D2019-06-10T135628_01BB.vbk
06/10/2019 03:40 PM 2,276,069,376 SERVER2.vm-987654D2019-06-10T154012_CFEE.vbk
06/10/2019 06:02 PM 37,412,352 SERVER2.vm-987654D2019-06-10T174047_CAE4.vib
06/10/2019 09:02 PM 37,311,488 SERVER2.vm-987654D2019-06-10T204201_E9DB.vib
06/11/2019 12:06 AM 37,399,552 SERVER2.vm-987654D2019-06-10T234324_8CCC.vib
06/11/2019 03:02 AM 37,528,576 SERVER2.vm-987654D2019-06-11T024447_7CB2.vib
06/11/2019 06:02 AM 41,753,600 SERVER2.vm-987654D2019-06-11T054553_7817.vib
06/11/2019 07:18 AM 2,276,048,384 SERVER2.vm-987654D2019-06-11T071756_42D8.vbk


If I read this correctly... it has several sealed backup chains. yet nothing gets uploaded to Azure? Why is that?

[HannesK]

Hello,
and welcome to the forums.

I split your question away from the other topic to avoid confusion.

Your backup copy chain does not look like a GFS backup copy chain. What kind of GFS and normal retention did you configure?

Best regards,
Hannes

[rjv1971]

normal retention: keep 10 copies (in performance tier), job runs ever 3 hrs. then capacity tier: (backup copy job) keep 30, 4 weekly, 12 monthly, 5 yearly. run once an hour.

We are in a testing/poc phase with Veeam, capacity tier/Azure for long term archive. I am just trying to speed up the process of getting something uploaded to Azure to test with. From reading manuals, it seems all I need is a sealed backup chain, but there's more that I need?
All the backupcopy job is doing is putting it in the repository onsite, then the SOBR tiering job runs (once every 4 hrs)...and... nothing

[HannesK]

I believe I reproduced your issue. I did the following

1) run initial backup copy job
2) run incremental backup job
3) sync bcj again -> new increment on BCJ destination
4) run a manual "active full" on the backup copy job -> result is Full - increment - Full (sealed chain)
5) I manually tried to offload but the UI does not allow it for normal retention points of the primary BCJ chain

Is that what you did?

You have no "W" (weekly) backups right now, correct?

[rjv1971]

correct, I have no 'W' retention

[HannesK]

It works as documented, you can only use GFS points

When offloading backup chains created by backup copy jobs, only full backup files that have a GFS flag on them will be offloaded.

to continue your test installation I suggest the following:

option 1: if you just want to test how capacity tier "feels": use reverse incremental on a primary backup job and just offload old data
option 2: wait until you have GFS weekly restore points

[rjv1971]

Thanks: so option 1: I do reverse incremental on the primary job... then how does it get to the capacity tier? How do I offload old data to Azure?

[Gostev]

You just point your primary job to the same scale-out backup repository, the rest is automated.

[HannesK]

or if you don't want to wait: "CTRL+right click" on the scale-out repository and click "run tiering job now"

also keep in mind that you need at least three reverse incrementals as the latest two reverse increments will not be offloaded.

[rjv1971]

Thanks HannesK and Gostev. As I mentioned before, I am trying to test Veeam and Azure and am trying to speed up the process got get something uploaded to Azure so I can test how it 'looks and feels' in Veeam and also get a handle on Azure storage. I know I should be patient and just let it run for a few weeks.... but trying to speed the process up a little. I will give this a try and will let you know results.
Thanks again!