Hi Steve! I would hope not, because in that case TSM would have a data integrity issue... 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 Schaub, Steve Sent: maandag 10 april 2017 17:30 To: ADSM-L@VM.MARIST.EDU Subject: Re: Deduplication Perhaps the client side dedupe is keeping a dedupe hash-bitmap that is not getting fully refreshed when you purge the backup data from the server? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, Eric van (ITOPT3) - KLM Sent: Monday, April 10, 2017 10:57 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Deduplication Hi guys! We are trying to make a fair comparison between server- and client-side deduplication. I'm running into an 'issue' where I notice that once you created a backup of a certain set of data, it is always deduplicated 100% afterwards when you start a new client-side deduped backup. Even when you delete all previous backup on the server first! So I backed up a directory, retrieved all objectids through a select * from backups and deleted all objects, but still a new backup is deduplicated 100%. I don't understand why. I though it maybe had something to do with data still being in the container pool, but even with reusdelay=0, everything is deduplicated... Thanks for any help (Andy? :)) in advance. Kind regards, Eric van Loon Air France/KLM Storage Engineering ******************************************************** 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 ******************************************************** ------------------------------------------------------------------------------ Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm ******************************************************** 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 ********************************************************