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.
