This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
By setting the "Allow Expiration" for snapshot rules under the GUI, it sets the snapshot only until the next execution, not for the whole retention, neither allows to client to sets its own retention.
Based on the IBM Documentation "https://www.ibm.com/docs/en/storage-scale/5.1.8?topic=systems-managing-snapshots-using-storage-scale-gui" :
- In the Retention fields, specify the number of snapshots that must be retained in a time period.
- Select the Allow Expiration checkbox to delete the snapshot when the defined retention period is completed.
The client has a snapshot policy which executes the snap multiple times a day (every 3 hours) and retain the last 6 versions of it.
[root@xsscalensd01a ~]# /usr/lpp/mmfs/gui/cli/lssnaprule
Cluster Name Snapshot Prefix Frequency Hours DaysW DaysM Weeks Months Min after Exclude start Exclude end Max Hrs/Min Max days Max weeks Max months Last implemented Off-hour deletions
GPFSLAB.CVALE policy @GMT non periodic 04,10,13,16,19,22 N/A ALL N/A ALL 05 N/A N/A 6 0 0 0 11/30/23 10:00 AM no
When the snapshot of Nov 30 10:05 was taken, the expiration was set only to 3 hours later, meaning the next execution - Nov 30 13:05
[root@xsscalensd01a ~]# mmlssnapshot DadosLab
Snapshots in file system DadosLab:
Directory SnapId Status Created ExpirationTime Fileset
@GMT-2023.11.30-13.05.22 13 Valid Thu Nov 30 10:05:24 2023 Thu Nov 30 13:05:00 2023
However the snapshot retention was set to keep the last 6 executions of a 3-hour schedule, so the expiration should be set on the next 18 hours.
Also client wanted to be able to have more flexibility to choose for how long to keep it, in within the policy. Once the "Allow Expiration" box was set, it could bring another field to the client determine - [ ] hours [ ] days... and client could add the number of hours to retain, if it is under the retention period of the snapshot policy.
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.