config Scale-out backup Performance / capacity / archive

[pacorus]

Hello good afternoon, I need help I'm crazy,

I have a Scale-out backup repository with Performance / capacity / archive
Retention policy job 31 days and weekly GFS for 1 year
Capacity tier (copy / move with 15 days)
archive tier 31 days

On the 10th the data is in performance and capacity?
On the 20th the data is still in performance and capacity or only capacity?
On day 30, is the data still in performance and capacity or only capacity?
On day 40 the data only in (first 10 points in archive) and points from 11 to 40 in performance and capacity?
On the 50th the data only in (first 20 points in archive) and points from 21 to 50 in performance and capacity?

I hope you can help me.
Are there examples to clarify this?

Thanks for the help

[HannesK]

Hello,
I'm not sure what you mean with "the data" when you ask for the specific days. Except for the first two, "the data" will be split. The easiest way is two draw it on paper.

The first thing to understand is that only the inactive chain gets moved to capacity tier. If one increment does not meet the 15 days, then the whole chain stays where it is (so you might want to decrease your days).

For Archive tier, it depends what you configured for "Archive GFS backups older than xx days"

Best regards,
Hannes

[pacorus]

Hi, Thanks for answering Hannes.

Capacity only moves the inactive chains but does the copy move the active chains?

The question is, I have a retention of 31 days of the month in Performance
And I have active Capacity with copy and Move of 14 or 15 days and the Archive with 31 days. What is the evolution, for example for day 10, 20, 30, 40 and 50 where are the backups located?

Thanks
All the best

[HannesK]

Hello,

but does the copy move the active chains?

the "copy" duplicates all data including the active chain. "copy" never "moves". it always "copies"

If you enable copy and move, then data in performance tier will be deleted according to what you configured.

The question is what your goal is. If you want to move as soon as possible to cheap archive tier, then you can reduce the days. If you just want to know "what happens when", I recommend taking a calendar and align it with your schedules (e.g. which day of the week is your GFS weekly, what is the exact job configuration). As 10 / 20 / 30 / 40 / 50 don't align with anything weekly, I cannot do that in my mind and would also have to draw it on paper.

Best regards,
Hannes

[pacorus]

Thank you very much for the help.
I want to have all the backups in capacity in case there is a problem in onpremise and the most current 15 days in performance after the 15th only in capacity, I want to archive from the 31st until the end of the year.
That's why I put this string that I think can happen:
day 10 all backups will be in performance and capacity
day 20 be all backups in performnace and capacity
day 30 the oldest chain only in capacity and the other weeks in performance and capacity
day 40 the 2 oldest chains in capacity and the 2 most current in performance and capacity
day 50 will start archiving strings in archive.
it would be correct?

[HannesK]

most parts sound good to me

the 40 might be a weekly GFS restore point plus the oldest chain depending on the day of the month you start to count
40 & 50 depends when you start moving (the "Archive GFS backups older than xx days" setting I mentioned earlier)