Messages

1

MP Server / CMOD data retention and external storage managers - Azure

« on: August 17, 2021, 09:34:07 AM »

We currently are using TSM as the external storage manager with CMOD on AIX. We are moving to Azure cloud and will use Azure object storage as the external storage manager. With TSM, the migration of the data would reset the 'start' date for expiration of the object files, since TSM manages and ages the data based on the store/load date. We want to avoid this reset of course, so we need to understand how data migrated/loaded to the Azure object storage is managed in terms of expiration. If we keep expiration by segment, for example, will CMOD manage expiration of the object files based on the segment date, i.e., expire a segment table's worth of data from Azure storage when a whole segment AG table is expired and dropped? And if it is not managed that way, how is it?  Or would we need to migrate our expire by segment AGs to expire by load to make expiration work properly?
Thanks and I welcome any ideas and ESPECIALLY anyone with experience with using Azure.