Hi, I have head a similar requirement and asked the Support about it. They advised to create another pool and use tiring to move the date.
" Hi Jonas, thanks for your reply and patience on this case. I have checked your inquiry regarding moving/migrating data from an existing S3 provider to another, via Spectrum Protect server operations (so the DB can reflect the changes), however it's not applicable at the moment. The workaround will be setting up a new storage pool on the system, then tier the data from the old pool to the new one. This way you can bypass the limitation and migrate the data successfully So the way to do it (SP server 8.1.9 is required) is to enable an option (setopt is fine no restart needed) called AllowTierTargetDir (just set it to YES or ON). With that option enabled, they can define a tiering STGRULE with both a target and and source pool as a container pool. Using that tiering STGRULE you can move data from one container pool to the other (tiering is basically migration for container pools). Without the option enabled, the target isn't allowed to be a container pool. Please find the link below for a tiering scenario with A step-by-step example https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.9/srv.admin/r_cloud_tier_example.html Please let us know if <ou have any additional questions regarding this case or provide feedback to close this case." Best regards, --- Jonas Jansen IT Center Gruppe: Server & Storage Abteilung: Systeme & Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-28784 Fax: +49 241 80-22134 jan...@itc.rwth-aachen.de www.itc.rwth-aachen.de -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Rackoll, Björn Sent: Monday, April 6, 2020 12:57 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Moving data in cloud storage pool Hi, I have to move data from a bucket in a cloud container storage pool that unfortunately was created with the wrong owner. I understand that I can't change the owner of the bucket directly (on the S3 level), neither can I copy the data to a new bucket in S3 and change the bucket name of the cloud container storage pool to the new one in TSM. Is really the last option that I have to lock the node, copy the contents of the bucket into a temporary new bucket on the S3 level, delete the old bucket, recreate it with the right owner and copy the whole data back? Or does somebody have another idea? Cloud system is on-premise Cloudian S3, if that matters. We have two regions, but CRR is far too slow to be considered for this problem (the data amount is fairly large). Regards, -- Björn Rackoll Universität Hamburg Regionales Rechenzentrum Basis-Infrastruktur Storage, Dateidienste, Backup und E-Mail Schlüterstr. 70 20146 Hamburg E-Mail: bjoern.rack...@uni-hamburg.de
