Skip to Main Content
IBM System Storage Ideas Portal


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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Status Under review
Created by Guest
Created on Aug 20, 2024

Tiering rules need more flexibility for Filesystem and/or type of data (Backup/Archive)

I would like to see the tiering rules to be able to be a bit more flexible.

I have a node that has Backup and Archive data.
Backup data is more often needed quickly so a backup location in ContainerPools is valid.
The Archive data is kept 10 years and not really needed on expensive disks.

I know an early setup with a separate Policy or a separate node for the archive data would have allowed for using ContainerPool and hierarchical structure for the appropriate backup types.

With Tiering to allow for either backup type or Filesystem to be tiered would allow us to get cold data out of the ContainerPool to tape media, where it belongs.
I do not want to tier all data from that node, just the Archive data, which resides in one filesystem.

Example:

Type    Filespace    FSID
Bkup    /            5
Arch    /backup      1
Bkup    /data        3
Bkup    /home        4
Bkup    /opt         8
Bkup    /usr/local   11
Bkup    /var         13

I only would like to tier /backup (FSID 1) to tape.

The syntax of subrules already has some element for filesystems in it but it seems it is only valid for VM-Backups(?).
The selection of Backup or Archive data would be new to the subrule set.
Currently the only selections available is for 'ALL DATA', 'INACTIVE' or 'NO DATA'

Idea priority Medium