Re: Slow restore of entire server volume
Hi, > We lost a server volume over the weekend - Netware 5.1 server > - 20 GB or so > to restore from tape. The process is going extremely slowly; > it seems that > most of the time is being spent retrieving tapes, and we have > only 3.5 GB > restored so far (started late yesterday afternoon). Do you have a separate management class for directories (see the option DIRMC)? During a restore, TSM first recovers the directory structure and then the files. If you don't have a directory mangement class, TSM has to search through your tapes twice. Regards, Dirk KastensTel.: +49 541 969-2347 Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany
Re: Slow restore of entire server volume
Is your storage pool you are restoring from collocated? Do you have an automated tape library or manual tape drives? -Original Message- From: Nancy Ames [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 3:25 PM To: [EMAIL PROTECTED] Subject: Slow restore of entire server volume We lost a server volume over the weekend - Netware 5.1 server - 20 GB or so to restore from tape. The process is going extremely slowly; it seems that most of the time is being spent retrieving tapes, and we have only 3.5 GB restored so far (started late yesterday afternoon). Is this normal??
Slow restore of entire server volume
We lost a server volume over the weekend - Netware 5.1 server - 20 GB or so to restore from tape. The process is going extremely slowly; it seems that most of the time is being spent retrieving tapes, and we have only 3.5 GB restored so far (started late yesterday afternoon). Is this normal??
Re: Slow restore of entire server volume
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Nancy Ames > We lost a server volume over the weekend - Netware 5.1 server - > 20 GB or so > to restore from tape. The process is going extremely slowly; it seems that > most of the time is being spent retrieving tapes, and we have only 3.5 GB > restored so far (started late yesterday afternoon). Welcome to the world of non-collocation. If you're using a tape medium that is not very fast to mount and spin up (DLT, for example), and your client has non-collocated data, your TSM server is having to bounce around from location to location on each tape, and from tape to tape, to find each and every one of its files. Restoration of collocated data is faster, because it avoids having to mount and dismount multiple tapes during a restore. Of course, collocation puts a strain on tape resources, because a given tape volume (or volumes) will have to be access every time the client is backed up. Another solution is to use a faster tape medium for NetWare backups--LTO, or IBM 3570 and 3590 media come to mind. NetWare appears to be a particularly slow client when it comes to mass restores, so, yes, I'd say you're not experiencing anything out of the ordinary, particularly if you're restoring a TSM client that has been a long-term client (1 year +). The longer the client has been backed up, the more scattered the client's files will become. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
