This isn't a Netappliance NAS -- this is two IBM netfinity boxes running Win2K server with TSM 4.2 client installed, running as an MS cluster, with fiber-attached FastT disk. So I don't have the double load issue. I'm pushing the NT staff for the multiple drive letter option, but current planning is that IF we *have* to do multple drives then this 800K files will be one of the drives. The NT group would rather set the entore 1.2 TB up as one drive . . .
One of my thoughts was to assign several management classes with the inlude-exclude list, then define the copygroups as co-located but use the same storage pools. Has anyone out there tried this stunt? I mean, the example for multiple restores for NT shows c:\users, c:\data1, and c:\data2 and then later states that 'if data2 is on a different tape' -- so I'm trying to force the issue. Tom Kauffman NIBCO, Inc > -----Original Message----- > From: Seay, Paul [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 01, 2002 3:33 AM > To: [EMAIL PROTECTED] > Subject: Re: question on configuring large NT client for > optimum restore > p roce ssing > > > First thing is NAS puts double load on the network. If you > have the NAS box > on a different interface with Gigabit connectivity that would > help. Also > Gigabit to your TSM server. > > Divide the data up into as many drive letters (filesystems) > as you can so > that you can run simultaneous backups/restores as multiple threads. > > Setup the Resourceutlization has high as you can tolerate. > > You really needed to go for SAN on this. The IP stack > overhead for CIFS is > very high which is how the NAS box communicates with the NT server. > > There may be some other options to use the NDMP capabilities > of TSM check > into that. It may do what you want and improve performance > dramatically. > Especially, if the NAS box has SAN connectivity capabilities > for backup and > recovery. > > Paul D. Seay, Jr. > Technical Specialist > Naptheon Inc. > 757-688-8180 > > > -----Original Message----- > From: Kauffman, Tom [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 31, 2002 4:05 PM > To: [EMAIL PROTECTED] > Subject: question on configuring large NT client for optimum > restore proce > ssing > > > What's the preferred method of configuring a large NT > fileserver for optimum > data recovery speed? > > Can I do something with co-location at the filesystem (what > IS a filesystem > in NT/2000?) level? > > We're bringing in an IBM NAS to replace four existing NT > servers and our > recovery time for the existing environment stinks. The main > server currently > has something over 800,000 files using 167 GB (current box > actually uses NT > file compression, so it's showing as 80 GB on NT). We had to > do a recovery > last year (raid array died) and it ran to 40+ hours; I'm getting the > feedback that over 20 hours will be un-acceptable. > > The TSM server and the client code are relatively recent 4.2 > versions and > will be staying at 4.2 for the rest of this year (so any neat > features of > TSM 5 would be nice to know but otherwise unuseable :-) > > To add to the fun and games, this will be an MS cluster > environment. With > 1.2 TB of disk on it. We do have a couple of weeks to play > around and try > things out before getting serious. One advantage to the MSCS > is that disk > compression is not allowed, so that should speed things up a > bit on the > restore. > > Tom Kauffman > NIBCO, Inc >
