John,
To answer your questions.:
Yes, MPThreading is turned on.
Yes, it is getting plenty of processor.  Region is set at 512M.  I have
sent to IBM dumps that were taken during the "hung" periods.  What I have
been told, is that there is a large number of locks being generated during
that period, and that everything is working as designed.   I can see why
there are a large number of locks.  The backupset that causes this has 1.6+
million objects (and growing daily).  I have also been told that soon there
will be another client node the same size (200+gb).

The biggest hurdle for me to overcome is the reliance on these backupsets
for DR purposes.  As far as I can tell, they were not originally designed
for DR purposes.  If they were, I believe they would be managed under DRM.

Michael Moore
VF Services Inc.
121 Smith Street
Greensboro,  NC  27420-1488

Voice: 336-332-4423
Fax: 336-332-4544




                    "Seay, Paul"
                    <seay_pd@NAPTH       To:     ADSM-L AT VM.MARIST DOT EDU
                    EON.COM>             cc:
                    Sent by:             Subject:     Re: Using Backupsets for 
Disaster Recovery
                    "ADSM: Dist
                    Stor Manager"
                    <ADSM-L AT VM DOT MAR
                    IST.EDU>


                    05/01/02 11:59
                    AM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






My situation is very different from many TSM sites.  I have no tape drives
in my servers so I have no way to create backupsets that can be read by the
client because 3590 is not supported based on what I know.  And, anyway, it
would not be feasible.  Sorry, I did not fully explain why they are too
cumbersome for my environment.  When you have as many servers as I do and
they all have hundreds of gigabytes it is just not feasible.

Different strokes for different folks.  That is the beauty of TSM.

Paul D. Seay, Jr.
Technical Specialist
Naptheon, INC
757-688-8180