Re: TSM level for deduplication
I submitted this request to IBM TSM development, and am posting it on their behalf: TSM Data deduplication has been in the product since 6.1 (server side data deduplication) and 6.2 (client side data deduplication) and is therefore considered mature at the 7.1 version. The data deduplication mechanism itself has remained largely unchanged since initial release but improvements have been focused on performance and increasing the size of files that could be deduplicated. We recommend that customers be at either TSM 6.3.5 (or above) or TSM 7.1.1.100 (or above). The TSM 6.3.5 version contains the important performance improvements though this version did not add improvements in deduplicating large files. TSM 7.1.1.100 contains not only the performance improvements but also ability to deduplicate larger files as well as replication performance improvements. All 7.1 deduplication customers should be at 7.1.1.100 due to this problem: http://www-01.ibm.com/support/docview.wss?uid=swg21688321 Dave CananIBM SRT (TSM Solutions Response Team)ddca...@us.ibm.com916-723-2409Office Hours 9:00 - 5:00 PT Date: Mon, 8 Dec 2014 13:00:53 -0500 From: yodaw...@gmail.com Subject: Re: [ADSM-L] TSM level for deduplication To: ADSM-L@VM.MARIST.EDU Would anyone from IBM care to comment on this thread? is dedup a stable mature feature in 7.1.1? On Mon, Dec 8, 2014 at 12:50 PM, J. Pohlmann jpohlm...@shaw.ca wrote: FYI - 7.1.1.000 is still on the FTP site. 7.1.1.100 is also on the FTP site. Ref http://www-01.ibm.com/support/docview.wss?uid=swg24035122 Best regards, Joerg Pohlmann -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: December 8, 2014 08:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM level for deduplication Bent, TSM 7.1.1.000 had a bug that sometimes caused restores of large files to fail. IBM considered the bug serious enough to warrant removing 7.1.1.000 from its software distribution servers. Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bent Christensen Sent: Saturday, December 06, 2014 6:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: TSM level for deduplication Hi Thomas, when you are calling 7.1.1- an utter distaster when it comes to dedup then what issues are you referring to? I have been using 7.1.1 in a production environment dedupping some 500 TB, approx 400 nodes, without any bigger issues for more than a year now. Surely, there are still lots of not-very-well-documented features in TSM 7, and I am not at all impressed by IBM support, and especially not DB2 support and their lack of willingness to recognize TSM DB2 as being a production environment, but when it comes to dedupping it has been smooth sailing for us up until now. - Bent Fra: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] P#229; vegne af Thomas Denier [thomas.den...@jefferson.edu] Sendt: 5. december 2014 20:56 Til: ADSM-L@VM.MARIST.EDU Emne: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
Re: TSM level for deduplication
Awesome... thank you Dave! On Tue, Dec 9, 2014 at 9:52 AM, Dave Canan ddca...@outlook.com wrote: I submitted this request to IBM TSM development, and am posting it on their behalf: TSM Data deduplication has been in the product since 6.1 (server side data deduplication) and 6.2 (client side data deduplication) and is therefore considered mature at the 7.1 version. The data deduplication mechanism itself has remained largely unchanged since initial release but improvements have been focused on performance and increasing the size of files that could be deduplicated. We recommend that customers be at either TSM 6.3.5 (or above) or TSM 7.1.1.100 (or above). The TSM 6.3.5 version contains the important performance improvements though this version did not add improvements in deduplicating large files. TSM 7.1.1.100 contains not only the performance improvements but also ability to deduplicate larger files as well as replication performance improvements. All 7.1 deduplication customers should be at 7.1.1.100 due to this problem: http://www-01.ibm.com/support/docview.wss?uid=swg21688321 Dave CananIBM SRT (TSM Solutions Response Team)ddca...@us.ibm.com916-723-2409Office Hours 9:00 - 5:00 PT Date: Mon, 8 Dec 2014 13:00:53 -0500 From: yodaw...@gmail.com Subject: Re: [ADSM-L] TSM level for deduplication To: ADSM-L@VM.MARIST.EDU Would anyone from IBM care to comment on this thread? is dedup a stable mature feature in 7.1.1? On Mon, Dec 8, 2014 at 12:50 PM, J. Pohlmann jpohlm...@shaw.ca wrote: FYI - 7.1.1.000 is still on the FTP site. 7.1.1.100 is also on the FTP site. Ref http://www-01.ibm.com/support/docview.wss?uid=swg24035122 Best regards, Joerg Pohlmann -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: December 8, 2014 08:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM level for deduplication Bent, TSM 7.1.1.000 had a bug that sometimes caused restores of large files to fail. IBM considered the bug serious enough to warrant removing 7.1.1.000 from its software distribution servers. Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bent Christensen Sent: Saturday, December 06, 2014 6:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: TSM level for deduplication Hi Thomas, when you are calling 7.1.1- an utter distaster when it comes to dedup then what issues are you referring to? I have been using 7.1.1 in a production environment dedupping some 500 TB, approx 400 nodes, without any bigger issues for more than a year now. Surely, there are still lots of not-very-well-documented features in TSM 7, and I am not at all impressed by IBM support, and especially not DB2 support and their lack of willingness to recognize TSM DB2 as being a production environment, but when it comes to dedupping it has been smooth sailing for us up until now. - Bent Fra: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] P#229; vegne af Thomas Denier [thomas.den...@jefferson.edu] Sendt: 5. december 2014 20:56 Til: ADSM-L@VM.MARIST.EDU Emne: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication
Re: TSM level for deduplication
Bent, TSM 7.1.1.000 had a bug that sometimes caused restores of large files to fail. IBM considered the bug serious enough to warrant removing 7.1.1.000 from its software distribution servers. Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bent Christensen Sent: Saturday, December 06, 2014 6:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: TSM level for deduplication Hi Thomas, when you are calling 7.1.1- an utter distaster when it comes to dedup then what issues are you referring to? I have been using 7.1.1 in a production environment dedupping some 500 TB, approx 400 nodes, without any bigger issues for more than a year now. Surely, there are still lots of not-very-well-documented features in TSM 7, and I am not at all impressed by IBM support, and especially not DB2 support and their lack of willingness to recognize TSM DB2 as being a production environment, but when it comes to dedupping it has been smooth sailing for us up until now. - Bent Fra: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] P#229; vegne af Thomas Denier [thomas.den...@jefferson.edu] Sendt: 5. december 2014 20:56 Til: ADSM-L@VM.MARIST.EDU Emne: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
Re: TSM level for deduplication
FYI - 7.1.1.000 is still on the FTP site. 7.1.1.100 is also on the FTP site. Ref http://www-01.ibm.com/support/docview.wss?uid=swg24035122 Best regards, Joerg Pohlmann -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: December 8, 2014 08:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM level for deduplication Bent, TSM 7.1.1.000 had a bug that sometimes caused restores of large files to fail. IBM considered the bug serious enough to warrant removing 7.1.1.000 from its software distribution servers. Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bent Christensen Sent: Saturday, December 06, 2014 6:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: TSM level for deduplication Hi Thomas, when you are calling 7.1.1- an utter distaster when it comes to dedup then what issues are you referring to? I have been using 7.1.1 in a production environment dedupping some 500 TB, approx 400 nodes, without any bigger issues for more than a year now. Surely, there are still lots of not-very-well-documented features in TSM 7, and I am not at all impressed by IBM support, and especially not DB2 support and their lack of willingness to recognize TSM DB2 as being a production environment, but when it comes to dedupping it has been smooth sailing for us up until now. - Bent Fra: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] P#229; vegne af Thomas Denier [thomas.den...@jefferson.edu] Sendt: 5. december 2014 20:56 Til: ADSM-L@VM.MARIST.EDU Emne: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
Re: TSM level for deduplication
Would anyone from IBM care to comment on this thread? is dedup a stable mature feature in 7.1.1? On Mon, Dec 8, 2014 at 12:50 PM, J. Pohlmann jpohlm...@shaw.ca wrote: FYI - 7.1.1.000 is still on the FTP site. 7.1.1.100 is also on the FTP site. Ref http://www-01.ibm.com/support/docview.wss?uid=swg24035122 Best regards, Joerg Pohlmann -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: December 8, 2014 08:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM level for deduplication Bent, TSM 7.1.1.000 had a bug that sometimes caused restores of large files to fail. IBM considered the bug serious enough to warrant removing 7.1.1.000 from its software distribution servers. Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bent Christensen Sent: Saturday, December 06, 2014 6:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: TSM level for deduplication Hi Thomas, when you are calling 7.1.1- an utter distaster when it comes to dedup then what issues are you referring to? I have been using 7.1.1 in a production environment dedupping some 500 TB, approx 400 nodes, without any bigger issues for more than a year now. Surely, there are still lots of not-very-well-documented features in TSM 7, and I am not at all impressed by IBM support, and especially not DB2 support and their lack of willingness to recognize TSM DB2 as being a production environment, but when it comes to dedupping it has been smooth sailing for us up until now. - Bent Fra: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] P#229; vegne af Thomas Denier [thomas.den...@jefferson.edu] Sendt: 5. december 2014 20:56 Til: ADSM-L@VM.MARIST.EDU Emne: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
Re: TSM level for deduplication
The web page at https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs has the note Removed from FTP site 12/1 due to IT05283. Replaced by 7.1.1.100. in reference to 7.1.1.000. I just looked at the FTP site and 7.1.1.000 is indeed still there. I overestimated IBM's ability to keep track of the contents of its own Web sites and FTP servers. Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of J. Pohlmann Sent: Monday, December 08, 2014 12:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM level for deduplication FYI - 7.1.1.000 is still on the FTP site. 7.1.1.100 is also on the FTP site. Ref http://www-01.ibm.com/support/docview.wss?uid=swg24035122 Best regards, Joerg Pohlmann -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: December 8, 2014 08:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM level for deduplication Bent, TSM 7.1.1.000 had a bug that sometimes caused restores of large files to fail. IBM considered the bug serious enough to warrant removing 7.1.1.000 from its software distribution servers. Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bent Christensen Sent: Saturday, December 06, 2014 6:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: TSM level for deduplication Hi Thomas, when you are calling 7.1.1- an utter distaster when it comes to dedup then what issues are you referring to? I have been using 7.1.1 in a production environment dedupping some 500 TB, approx 400 nodes, without any bigger issues for more than a year now. Surely, there are still lots of not-very-well-documented features in TSM 7, and I am not at all impressed by IBM support, and especially not DB2 support and their lack of willingness to recognize TSM DB2 as being a production environment, but when it comes to dedupping it has been smooth sailing for us up until now. - Bent Fra: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] P#229; vegne af Thomas Denier [thomas.den...@jefferson.edu] Sendt: 5. december 2014 20:56 Til: ADSM-L@VM.MARIST.EDU Emne: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
Re: TSM level for deduplication
Hi Thomas, I agree, don't even think about using dedup at 6.2.5. Too many performance and data handling bugs. We're deduping 4.5-5 TB a day (Windows TSM server) and even had issues at 6.3.4. Have seen no issues at all so far at 6.3.5 (and it should be easy for you to get there from 6.2.5). W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: Friday, December 05, 2014 2:56 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
SV: TSM level for deduplication
Hi Thomas, when you are calling 7.1.1- an utter distaster when it comes to dedup then what issues are you referring to? I have been using 7.1.1 in a production environment dedupping some 500 TB, approx 400 nodes, without any bigger issues for more than a year now. Surely, there are still lots of not-very-well-documented features in TSM 7, and I am not at all impressed by IBM support, and especially not DB2 support and their lack of willingness to recognize TSM DB2 as being a production environment, but when it comes to dedupping it has been smooth sailing for us up until now. - Bent Fra: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] P#229; vegne af Thomas Denier [thomas.den...@jefferson.edu] Sendt: 5. december 2014 20:56 Til: ADSM-L@VM.MARIST.EDU Emne: [ADSM-L] TSM level for deduplication My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
TSM level for deduplication
My management is very eager to deploy TSM deduplication in our production environment. We have been testing deduplication on a TSM 6.2.5.0 test server, but the list of known bugs makes me very uncomfortable about using that level for production deployment of deduplication. The same is true of later Version 6 levels and TSM 7.1.0. TSM 7.1.1.000 was an utter disaster. Is there any currently available level in which the deduplication code is really fit for production use? IBM has historically described patch levels as being less thoroughly tested than maintenance levels. Because of that I have avoided patch levels unless they were the only option for fixing crippling bugs in code we were already using. Is that attitude still warranted? In particular, is that attitude warranted for TSM 7.1.1.100? Has IBM dropped any hints about the likely availability date for TSM 7.1.2.000? Thomas Denier Thomas Jefferson University Hospital The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
