Open isd503 opened 8 months ago
It has been a couple years since I looked at this, so bear with me. By "not protected" you mean that the same values are synced to all devices in the Sync Group?
While perhaps imperfect, it is functioning as designed. You can mitigate pruning issues by:
What I would like to do is to use one application with different settings on each F5 appliance so that I can back up each appliance in the cluster individually. Currently the application installs on both F5s in a pair but the settings in the pruning area are over written every time a sink occurs. Sent from my iPhoneOn Nov 2, 2023, at 21:27, Daniel Tavernier @.***> wrote: It has been a couple years since I looked at this, so bear with me. By "not protected" you mean that the same values are synced to all devices in the Sync Group? While perhaps imperfect, it is functioning as designed. You can mitigate pruning issues by:
Enabling "Only Prune iApp-Generated Archives" Increasing the number of archives to keep (at least n*3, where n = number of BIG-IPs in the cluster). Ensuring each F5 cluster has a different pruning suffix and or is saving archives to a different folder. Setting up multiple iApps to handle daily/weekly/monthly archiving with different suffixes (e.g. _daily, _weekly, _monthly).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
I believe that is fundamentally impossible because iApps are synced between all cluster members. There is no way to have different versions of the iApp on each device.
OK to bypass it we went ahead and simply disabled the pruning feature within the application. We’ll have to manually prune.Sent from my iPhoneOn Nov 2, 2023, at 21:55, Daniel Tavernier @.***> wrote: I believe that is fundamentally impossible because iApps are synced between all cluster members. There is no way to have different versions of the iApp on each device.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Most F5 appliances are deployed in a pair and both of them need to be backed up.
The 'backup schedule time' and 'unique filename suffix' fields are not protected during a sync between devices. This results in both devices being backed up at the same time with the same suffix. Further, one appliances config can then delete the other appliances backup from the archive location.