Hi,
According to the documentation, the Force Delete feature should be configured with a value that is at least one backup generation period longer than the retention period.
I would like to confirm my understanding and the detailed calculation logic.
Example:
- Retention period: 93 days
- Maximum backup generation interval: 31 days
Based on the documentation, is it correct to assume that a Force Delete value of at least 124 days satisfies the requirement?
In addition, I would like to understand how the age calculation is performed.
For example, if Force Delete is configured to 124 days and a backup was created on January 1st at 06:00:
1. Is the age calculated using the exact timestamp, or only the calendar date?
2. Is a backup deleted when its age is:
- greater than the configured number of days
- greater than or equal to the configured number of days
3. Which timestamp is used for the calculation?
- backup start time
- backup completion time
- another timestamp
Could you please clarify the product behavior?
Best Regards,
Rin
-
rin
- Enthusiast
- Posts: 37
- Liked: 5 times
- Joined: Jun 24, 2025 6:40 am
- Full Name: Rintaro Tamura
- Contact:
-
rin
- Enthusiast
- Posts: 37
- Liked: 5 times
- Joined: Jun 24, 2025 6:40 am
- Full Name: Rintaro Tamura
- Contact:
Additional Questions Regarding Oracle RMAN Force Delete Retention Calculation
Additional clarification:
For context, the Oracle RMAN retention period is configured as 93 days, and the maximum backup generation period is 31 days.
My understanding of the requirement:
"A value for the number of days setting must be at least 1 backup generation period longer than the retention period"
is that the minimum Force Delete value can be calculated as:
Retention Period + 1 Backup Generation Period
For example:
Retention Period = 93 days
Maximum Backup Generation Period = 31 days
=> Minimum Force Delete Value = 124 days
Is this understanding correct?
I would also appreciate any clarification regarding whether there are additional considerations beyond the retention period and backup generation period when determining the Force Delete value.
I understand some details may be implementation-specific or internal product logic.
If the exact calculation method cannot be publicly disclosed, any guidance that can be shared regarding the intended behavior or interpretation of the feature would be greatly appreciated.
For the age calculation behavior, I would also like to confirm whether the calculation is based on the exact timestamp or only the calendar date.
For context, the Oracle RMAN retention period is configured as 93 days, and the maximum backup generation period is 31 days.
My understanding of the requirement:
"A value for the number of days setting must be at least 1 backup generation period longer than the retention period"
is that the minimum Force Delete value can be calculated as:
Retention Period + 1 Backup Generation Period
For example:
Retention Period = 93 days
Maximum Backup Generation Period = 31 days
=> Minimum Force Delete Value = 124 days
Is this understanding correct?
I would also appreciate any clarification regarding whether there are additional considerations beyond the retention period and backup generation period when determining the Force Delete value.
I understand some details may be implementation-specific or internal product logic.
If the exact calculation method cannot be publicly disclosed, any guidance that can be shared regarding the intended behavior or interpretation of the feature would be greatly appreciated.
For the age calculation behavior, I would also like to confirm whether the calculation is based on the exact timestamp or only the calendar date.
-
PetrM
- Veeam Software
- Posts: 4224
- Liked: 754 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Question about Force Delete retention calculation
Hello,
Do you run a full backup once per month? If so, your assumption seems to be valid, but let me clarify the details with my colleagues and update the topic as soon as I know more — I'm not ready to confirm it yet.
My second question is how you perform regular retention. Are you using RMAN scripts, or the plug-in in managed mode?
The main idea is that the option simply deletes files from the file system without any validation, so we need to set a value that exceeds your absolute maximum storage period. For example, if you know for sure that you will never need a backup older than 124 days — and that a restore from such an old backup would not cover any of your business cases, including testing scenarios - then set the value above that.
Thanks!
Do you run a full backup once per month? If so, your assumption seems to be valid, but let me clarify the details with my colleagues and update the topic as soon as I know more — I'm not ready to confirm it yet.
My second question is how you perform regular retention. Are you using RMAN scripts, or the plug-in in managed mode?
The main idea is that the option simply deletes files from the file system without any validation, so we need to set a value that exceeds your absolute maximum storage period. For example, if you know for sure that you will never need a backup older than 124 days — and that a restore from such an old backup would not cover any of your business cases, including testing scenarios - then set the value above that.
Thanks!
Who is online
Users browsing this forum: No registered users and 13 guests