- 1. TSM and Diskxtender - Windows (score: 1)
- Author: Tom Melton <Tom.Melton AT EMORYHEALTHCARE DOT ORG>
- Date: Thu, 18 May 2006 16:24:16 -0400
- TSM Window Client 5.2.3.4 TSM Server 5.2.2.5 Diskxtender 5.6 We have a large Windows box with millions of files on it. We utilize the HSM components of Legato/EMC Diskxtender to migrate the unused fi
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-05/msg00367.html (11,451 bytes)
- 2. Re: TSM and Diskxtender - Windows (score: 1)
- Author: Tab Trepagnier <Tab.Trepagnier AT LAITRAM DOT COM>
- Date: Sat, 27 May 2006 05:16:45 -0500
- Tom, We've seen the same phenomenon. We have TSM 5.1.7 running in a Windows 2003 Sp1 file server with almost 2 million files. The file server is itself running on VMWare and connected to LUNs on our
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-05/msg00465.html (13,272 bytes)
- 3. Re: TSM and Diskxtender - Windows (score: 1)
- Author: "Schaub, Steve" <steve_schaub AT BCBST DOT COM>
- Date: Mon, 29 May 2006 20:12:08 -0400
- Tom/Tab, For what it's worth, my experience is that troubleshooting TSM clients that are VM guests is nothing like dealing with physicals. Assume absolutely nothing. For example, don't assume that th
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-05/msg00473.html (14,756 bytes)
- 4. Re: TSM and Diskxtender - Windows (score: 1)
- Author: steve freeman <sfreeman AT ACR-ITS DOT COM>
- Date: Tue, 30 May 2006 10:38:05 +0100
- We had a problem last year with TSM and diskextender and ended up taking off diskextender. The problem was related to Alternative file:streams. Apparently, what happened was the file would be migrate
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-05/msg00474.html (15,850 bytes)
This search system is powered by
Namazu