Oh, and don't forget that your server requires a significant amount of CPU's when switching to container pools since all deduplication and compression is done inline during your backup window. So when you want to switch in place from file to container, make sure your server has enough cores available. Check the Spectrum Protect Blueprints for details. Kind regards, Eric van Loon Air France/KLM Storage Engineering
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: dinsdag 18 september 2018 15:37 To: ADSM-L@VM.MARIST.EDU Subject: CONTAINER pool experiences We are investigating using CONTAINER pools for our offsite replica server vs the current FILE method which is killing us with the constant dedup, reclaims, etc. So, what are the "gotchas' ? We are still at V7.1.7.400 so I figure we will have to do without any new features added in the V8 branch. But is it problematic enough at V7 to avoid it? Your thoughts? Experiences? -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/ ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************
