Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+6\.x\s+and\s+dedupe\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+6\.x\s+and\s+dedupe\s*$/: 9 ]

Total 9 documents matching your query.

1. [ADSM-L] TSM 6.x and dedupe (score: 1): Author: "Tyree, David" <david.tyree AT SGMC DOT ORG>; Date: Fri, 20 Feb 2009 08:51:28 -0500; Can users of TSM 6.x comment on it's data dedupe functionality? I'm curious as to how it functions and would like some info about it. David Tyree Interface Analyst South Georgia Medical Center 229.33; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00346.html (11,663 bytes)
2. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Mark Stapleton <Mark.Stapleton AT CDW DOT COM>; Date: Fri, 20 Feb 2009 08:07:25 -0600; Being that TSM 6.1 is still in beta, I wouldn't put much weight on any kind of metrics or performance available with the current load. Everyone also needs to keep in mind that dedupe will only be ini; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00348.html (12,664 bytes)
3. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Fri, 20 Feb 2009 09:25:07 -0500; "What's New" Data deduplication Data deduplication is a method of eliminating redundant data in sequential-access disk (FILE) primary, copy, and active-data storage pools. One unique instance of the; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00350.html (13,885 bytes)
4. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>; Date: Fri, 20 Feb 2009 10:25:55 -0500; Is the TSM 6.x guide due out next month or april? I assume there will be a New Concepts guide at some point also. Regards Tim From the as yet unpublished (e.g. subject to change) "Upgrade Guide" unde; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00354.html (14,393 bytes)
5. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Delroy Blake <hcddbz AT MAC DOT COM>; Date: Sat, 21 Feb 2009 19:49:48 +0000; Until it comes out, one could use diligent Protectier as reference point --Original Message-- From: Tyree, David Sender: ADSM: Dist Stor Manager To: ADSM-L AT VM.MARIST DOT EDU ReplyTo: ADSM: Dist St; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00366.html (11,984 bytes)
6. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Sat, 21 Feb 2009 21:20:36 +0100; Until it comes out, one could use diligent Protectier as reference point do you have any indications about any part of the diligent system having made it's way into TSM 6.1? IMNSHO your statement is; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00367.html (12,676 bytes)
7. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Delroy Blake <hcddbz AT MAC DOT COM>; Date: Sat, 21 Feb 2009 20:29:08 +0000; My statement was a point of reference to a similar technology, which has real world use cases. Until 6.x comes out and is used or IBM puts out Red Books, Red papers look at like tech is all anyone ha; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00368.html (13,096 bytes)
8. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Sat, 21 Feb 2009 21:42:25 +0100; My statement was a point of reference to a similar technology, which has real world use cases. Until 6.x comes out and is used or IBM puts out Red Books, Red papers look at like tech is all anyone h; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00369.html (14,038 bytes)
9. Re: [ADSM-L] TSM 6.x and dedupe (score: 1): Author: Joerg Pohlmann <jpohlman AT CA.IBM DOT COM>; Date: Sat, 21 Feb 2009 17:41:15 -0800; In case anyone forgot the URL to the Oxford presentations: http://tsm-symposium.oucs.ox.ac.uk/2007contributions.html: in particular: http://tsm-symposium.oucs.ox.ac.uk/2007/papers/Dave%20Cannon%20-%2; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-02/msg00370.html (11,584 bytes)

Current List: 1 - 9
Page: [1]