Unable to change retention period

If you change the retention period, it doesn’t lock in until data aging runs. I would suggest first running the data aging forecast report to verify the changes being made.

To add to what @Aplynx said, the freeing of space can easily be delayed due to the deduplication aging process.

I responded to a similar post yesterday here:

Hi @Aplynx, @Mike Struening, I am afraid even in the Data Retention Forecast and Compliance report there were no changes visible. Newly performed backups are still with the same retention period. Do you have any idea what to do next?

I would add, we are unable to confirm changes in the bar (for Days and Cycles). After clicking OK, old records are returning back

What are you changing and what is the expected result? 

Current status: Retain for 60 Days 8 Cycles

Desired status: Retain for 32 Days 4 Cycles

@drPhil , are you saying that when you change the 60 and 8 to 32 and 4, then click ok, the settings aren’t actually sticking?

That’s indeed odd.  I would run a GUI Audit Trail report and see if it even acknowledges your change attempt.

For the main issue itself, I reread your original post and I believe you are saying that you simply can’t change the setting and get it to stick.

I’m discussing with a colleague to see if there are any times this is automatically overridden.

Spoke to my colleague here and if you are indeed getting no response from clicking ok, that sounds broken.  Check the GUI Audit trail and share back the result, though this sounds like an incident.

Hi @Aplynx and @Mike Struening!

Heurekaaaaaa! Finally, we have the solution! As per your advice I have changed the retention period on the master server - Commserve Server itself instead of using console on the jump host server. Then, the retention period has been sucessfully changed.

Thank you so much for your support!!!