You could start by getting a list of nodes that are set to either COMPRESSION=CLIENT or YES and those with DEDUPLICATION=CLIENTORSERVER. The default is SERVERONLY. Those would be good candidates to start with. You can't do client-side dedup without setting the node attribute.
Bill "When the pin is pulled, Mr. Grenade is NOT your friend!" - USMC -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ehresman,David E. Sent: Wednesday, November 28, 2012 9:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Who is performing Client Based Encryption and Compression I think "q actlog begindate=today-ndays msgno=4968" is more efficient. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Tuesday, November 27, 2012 5:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Who is performing Client Based Encryption and Compression For compression: q actlog begindate=today-ndays search=ane4968 Non-zero values mean the client is compressing. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Harris, Chad Sent: Tuesday, November 27, 2012 5:04 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Who is performing Client Based Encryption and Compression Fellow TSM Admins, We are in the process of bringing VTLs into our TSM Environment. In order to take full advantage of deduplication features on the VTL we need to go after the clients that are performing client based encryption and compression. With that in mind, does anyone know an easy way to tell which clients are using these features? Thanks, Chad Harris
