Hello Luc. I'm not sure that Glacier is a good fit for most TSM data.
TSM has a lot of churn. Data expires and then you are left with a choice of reclamation or storing excess data. Glacier retrieval is slow, so you would have to mark volumes as offsite to allow reclamation from the primary copy. (that’s something that we need BTW if anyone from development is reading this, the ability to mark a copypool as offsite so that the offsite reclamation strategy is always used). Glacier storage is cheap but there are access and retrieval costs, and there is a charge for keeping less than 90 days. What it would be good for is storing exports or backupsets of data that needs to be kept for long periods for regulatory purposes, as once written that never changes. If it were me I'd go with standard S3 until I understood my data access pattern and move to Glacier once I was convinced that was a good deal. I did once set up a system that lived entirely on AWS. Two TSM Servers in different zones, that replicated to one another. We used S3 there, but I was not further involved after set up. The TSM Servers were, of course, the biggest and most expensive resource consumers in the whole fleet. It would be great if you could report here what you eventually decide Cheers Steve Steven Harris TSM Admin/Consultant Canberra Australia -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michaud, Luc [Analyste principal - environnement AIX] Sent: Friday, 2 February 2018 1:27 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Need guidance on how to protect stgpool to cloud Greetings to you all, We've setup a blueprint replicated environment with directory container pools on both sides. We protect the primary node stgpools to tape as well, with offsite movements. Now we want to get rid of the tapes, most likely by leveraging AWS Glacier. We have been exposed to a limitation of containers only being able to have 1 container protection and 1 tape protection. How have you guys done it ? Any trick or caveat that we should be aware of ? Regards, Luc Michaud Société de Transport de Montréal This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. You should immediately delete the message if you are not the intended recipient. If you have received this email by mistake please delete it from your system; you should not copy the message or disclose its content to anyone. This electronic communication may contain general financial product advice but should not be relied upon or construed as a recommendation of any financial product. The information has been prepared without taking into account your objectives, financial situation or needs. You should consider the Product Disclosure Statement relating to the financial product and consult your financial adviser before making a decision about whether to acquire, hold or dispose of a financial product. For further details on the financial product please go to http://www.bt.com.au Past performance is not a reliable indicator of future performance.
