Ike,
Have a search in www.adsm.org for the answer to your query on idle wait.
In particular see Andy Raibeck's note dated 01/02/2002 and subject
Re: WHy Idle wait keeps incrementing?(reply)
You can get very satisfactory results with an os390 TSM server.
Make sure you are running multi threaded for cpu
If you do a "query option" check that you have
MPThreading Yes
Have a look at the information provided by query active ie.
q ac begind=today-1 begint=08:00 endd=today endt=08:00 originator=client > 'your
filename'
Below is the output from the backup of a typical one of my novell data servers
How would this compare with your stats for particularly Network data transfer
rate & Aggregate data transfer rate.
02/15/2002 00:51:04
ANE4952I (Session: 9533, Node: D1) Total number of objects
inspected: 1,372,588
02/15/2002 00:51:04
ANE4954I (Session: 9533, Node: D1) Total number of objects
backed up: 9,676
02/15/2002 00:51:04
ANE4958I (Session: 9533, Node: D1) Total number of objects
updated: 0
02/15/2002 00:51:04
ANE4960I (Session: 9533, Node: D1) Total number of objects
rebound: 0
02/15/2002 00:51:04
ANE4957I (Session: 9533, Node: D1) Total number of objects
deleted: 0
02/15/2002 00:51:04
ANE4970I (Session: 9533, Node: D1) Total number of objects
expired: 1,256
02/15/2002 00:51:04
ANE4959I (Session: 9533, Node: D1) Total number of objects
failed: 8
02/15/2002 00:51:04
ANE4961I (Session: 9533, Node: D1) Total number of bytes
transferred: 3.42 GB
02/15/2002 00:51:04
ANE4963I (Session: 9533, Node: D1) Data transfer time:
1,500.81 sec
02/15/2002 00:51:04
ANE4966I (Session: 9533, Node: D1) Network data transfer rate:
2,390.71 KB/sec
02/15/2002 00:51:04
ANE4967I (Session: 9533, Node: D1) Aggregate data transfer
rate: 539.48 KB/sec
02/15/2002 00:51:04
ANE4968I (Session: 9533, Node: D1) Objects compressed by:
0%
02/15/2002 00:51:04
ANE4964I (Session: 9533, Node: D1) Elapsed processing time:
01:50:50
"Hunley, Ike" <[EMAIL PROTECTED]> on 02/14/2002 04:57:23 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: John Naylor/HAV/SSE)
Subject: Re: Export/Import process
Great,
Thanks a lot. I'm reading TSM doc as I respond to TSM issues.
We've moved a client server from a UNIX based TSM to a TSM(4.2.1.9) started
task running on OS/390 v2r9. Now backups take a LOT more time. Where do I
begin to look for the why?
I see extended IDLE waits.
1,162 BPX-- IdleW 2.0 H 76.2 M 4.4 K Node WinNT
What causes idle wait?
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 11:32 AM
To: [EMAIL PROTECTED]
Subject: Re: Export/Import process
Neither.
Look at the help for IMPORT NODE.
If the filespaces you are importing have identical names to the ones backed
up on the new server (and they probably will, since the clients haven't
changed), IMPORT will create new filespace names for the imported ones. TSM
will NOT merge filespace data on import.
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
-----Original Message-----
From: Hunley, Ike [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 11:00 AM
To: [EMAIL PROTECTED]
Subject: Export/Import process
We had a TSM region setup for testing and we are moving servers from one TSM
started task to another one.
So far we've just pointed the servers to the new TSM. We'd like to export
all data for each node to import into the new TSM. If we do this, would we
overwrite data in the new environment, or would it simply store it?
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this e-mail
message. Any personal comments made in this e-mail do not reflect the views of
Blue Cross Blue Shield of Florida, Inc.
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************
