====== Ahsay Upgrade Advisory (#29634) – Critical Issue with AhsayCBS v8 web console update of retention policy settings ======
We have recently confirmed a critical bug related to changing the backup set retention policy settings using the AhsayCBS web console affecting all backup set types, which can cause data to be removed from the Retention Area after **one day or one job**, instead of retention period specified by the customer.
If a customer enters a value for the retention policy on the AhsayCBS web console which is not listed in the drop-down menu **(1,2,3,4,5,6,7,8,9,10, 14,21,28,100, and 365)** and saves the change, AhsayCBS will set the value of retention policy to **1** instead of the value entered by the customer.
{{:public:announcement:29634.png?direct&800|}}
For example, if a value 15 days is entered for the Simple retention policy, instead of deleted/updated files remaining in the Retention Area for 15 days, where they can be still restored if required and only permanently deleted after 15 days. **They will be in fact permanently deleted after 1 day**.
===== Does this issue affect my customers? =====
This issue only affects customers who have changed their retention policy settings using the AhsayCBS web console and used a value not listed in the drop-down menu **(1,2,3,4,5,6,7,8,9,10, 14,21,28,100, and 365)**.
===== What are the affected Backup Sets? =====
* All backup set types
===== What are the affected Retention Policy Types? =====
* Simple (days or Jobs)
* Advanced (days)
===== What are the affected CBS versions? =====
* AhsayCBS v8.3.6.0 to 8.5.0.98
===== What action do I need to take to fix this problem? =====
In all AhsayCBS releases from v8.5.0.127 (or later), a special one-time batch job is included to identify and change any retention policy value from 1 to a preset higher value.
- CBS Administrators are strongly advised to immediately upgrade all affected AhsayCBS to v8.5.0.127 or above.
- When the AhsayCBS service is restarted after the upgrade, the special one-time batch job will automatically identify all backup sets with retention policy set 1 and update their values higher to stymie premature retention cleanup.
The value varies if the retention policy is set as 'jobs', 'day', 'month', etc.
Example,
* a retention policy of "1 day", will be reset to "90 days"
* a retention policy of "1 week", will be reset to "7 weeks"
* a retention policy of "1 month", will be reset to "10 months"
* a retention policy of "1 year", will be reset to "10 years"
* a retention policy of "1 job", will be reset to "90 jobs"
Once this special task has completed, a log file is created containing the users and the backup sets that have been affected.
The log is saved in the following location %CBS_INSTALL_PATH%/logs/retention-policy-reset.log ; you should review this file after upgrade.
2021-11-18-11-25-18 Start reset the retention policy affected by #29634
1. User = Hardy
Affected backup set = default-backup-set-name-1 (RP=adv)(1637205271903)
...Reset the ADVANCED-MONTHLY retention policy from 1 to 10 month(s). User = Hardy, backup set = default-backup-set-name-1 (RP=adv)(1637205271903)
...Reset the ADVANCED-YEARLY retention policy from 1 to 10 year(s). User = Hardy, backup set = default-backup-set-name-1 (RP=adv)(1637205271903)
...Reset the ADVANCED-WEEKLY retention policy from 1 to 7 week(s). User = Hardy, backup set = default-backup-set-name-1 (RP=adv)(1637205271903)
Retention Policy Settings: Type = ADVANCED, Unit = DAYS, Period = 7, Overlap Sensitive = false, Advanced Retention Policy List = [Advanced Retention Policy: ID = 1637205310940, Name = 1 mo, repeat 1mo, Type = MONTHLY, Numbers To Keep = 1, Date Type = EXACT, Sun = false, Mon = false, Tue = false, Wed = false, Thu = false, Fri = false, Sat = false, Day = 1, Week = 1, Month = 0, Year = 0, Advanced Retention Policy: ID = 1637205365152, Name = 1 yr, repeat 1 yr, Type = YEARLY, Numbers To Keep = 1, Date Type = EXACT, Sun = false, Mon = false, Tue = false, Wed = false, Thu = false, Fri = false, Sat = false, Day = 1, Week = 1, Month = 1, Year = 0, Advanced Retention Policy: ID = 1637205388324, Name = 1 wk, wed, keep 1wk, Type = WEEKLY, Numbers To Keep = 1, Date Type = , Sun = false, Mon = false, Tue = false, Wed = true, Thu = false, Fri = false, Sat = false, Day = 0, Week = 0, Month = 0, Year = 0] => Retention Policy Settings: Type = ADVANCED, Unit = DAYS, Period = 7, Overlap Sensitive = false, Advanced Retention Policy List = [Advanced Retention Policy: ID = 1637205310940, Name = 1 mo, repeat 1mo, Type = MONTHLY, Numbers To Keep = 10, Date Type = EXACT, Sun = false, Mon = false, Tue = false, Wed = false, Thu = false, Fri = false, Sat = false, Day = 1, Week = 1, Month = 0, Year = 0, Advanced Retention Policy: ID = 1637205365152, Name = 1 yr, repeat 1 yr, Type = YEARLY, Numbers To Keep = 10, Date Type = EXACT, Sun = false, Mon = false, Tue = false, Wed = false, Thu = false, Fri = false, Sat = false, Day = 1, Week = 1, Month = 1, Year = 0, Advanced Retention Policy: ID = 1637205388324, Name = 1 wk, wed, keep 1wk, Type = WEEKLY, Numbers To Keep = 7, Date Type = , Sun = false, Mon = false, Tue = false, Wed = true, Thu = false, Fri = false, Sat = false, Day = 0, Week = 0, Month = 0, Year = 0]
2. User = Laurel
Affected backup set = default-backup-set-name-1 (RP=1job_acpsimple)(1637205419957)
...Reset the SIMPLE retention policy from 1 to 90 day/job. User = Laurel, backup set = default-backup-set-name-1 (RP=1job_acpsimple)(1637205419957)
Retention Policy Settings: Type = SIMPLE, Unit = JOBS, Period = 1, Overlap Sensitive = false, Advanced Retention Policy List = [] => Retention Policy Settings: Type = SIMPLE, Unit = JOBS, Period = 90, Overlap Sensitive = false, Advanced Retention Policy List = []
2021-11-18-11-25-18 Completed recovering the retention policy.
2021-11-18-11-25-18 Number of affected user = 2
==== Will this fix apply if my user intended their backup set's retention policy to be "1"? ====
Yes. The fix's implementation will scan and reset any retention policy found to be "1", and increase the value accordingly. If any user's backup set were affected by this correction, you should consult with your user to notify them of this reset; the user can then determine what the true retention policy value should be set to, and manually update their backup set setting.
==== Will this fix apply if I run an older CBS version prior to upgrade to any CBS v8.5.0.127+ ? ====
Yes. The fix does not take into consideration the CBS version you are upgrading from.
The fix will apply to any and all backup sets existing on your CBS after your first upgrade to v8.5.0.127 (or newer release version), even though the user's device is outside of the affected CBS version.
Example, you currently run AhsayCBS v8.3.6.30, and upgrade to v8.5.0.127, since your v8.3.6.30 is within the affected version, the special one-time batch job will scan and reset any backup sets with a retention policy of "1", to a higher value.
Example, you currently run AhsayCBS v8.1.1.50, and upgrade to v8.5.0.127, even though your v8.1.1.50 is outside of the affected version, the special one-time batch job will still process your user's backup sets.
Example, you currently run AhsayCBS v7.17.2.2, and upgrade to v8.5.4.86 (Released 2021-Oct-11), the special one-time batch job will still process your user's backup sets upon the first CBS v8.5.4.86 service startup.
==== Will this fix apply if I upgrade from v8.5.0.127, to a newer release (example, v8.5.2.33 or v8.5.4.86)? ====
No. The first time you upgrade to any v8.5.0.127 (or later), the fix is performed at most once. If you upgrade again from v8.5.0.127 to a higher version, the fix is not performed again.
==== If I upgrade to v8.5.0.127 (or above), and the fix is applied, but then I rollback CBS, what happens? ====
The reset values are retained after the rollback if //users.xml// is not reverted.
The reset values are not retained if //users.xml// is also reverted.
Later, when you re-upgrade to v8.5.0.127+ , the one-time job will run again. At that time, if it detects any retention policy = "1", it will increase its value.
If you at any time you revert to an older "//users.xml//", the one-time job may reapply once you restart CBS service.
==== Can this fix be bypassed? ====
No.
===== What if my maintenance has already expired? How do I upgrade? =====
**Stop! Do not upgrade** until you contact a member our Sales team [[mailto:sales-kb@ahsay.com|sales-kb@ahsay.com]] for assistance with your maintenance renewal.
===== What if I require assistance with my AhsayCBS server upgrade? =====
Our professional service team is ready to provide immediate assistance to partners with AhsayCBS v8 upgrades.
Please contact a member our Sales team [[mailto:sales-kb@ahsay.com|sales-kb@ahsay.com]] to obtain a quotation for the AhsayCBS Upgrade Service.