Did anyone have a performance result for an export/import process of a node
using:
1- sequential media
2- server to server comm.
Any recommendations ¿?
TSM 5.2.2.0 running on solaris 8 to TSM 5.2.6.3 running on solaris 9
Regards,
Ibán Bernaldo de Quirós Márquez
Technical Specialist
cell
To: [EMAIL PROTECTED]
Subject: Re: Export/Import process
It's OS/390 V2R9. The LPAR has GIGABIT Ethernet, so throughput should be
good. I'll check with our network folks.
Thank you VERY much.
-Original Message-
From: Cook, Dwight E (SAIC) [mailto:[EMAIL PROTECTED]]
Sent: Thursday
-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
-- 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
: Export/Import process
Is that an OS/390 running MVS/ESA ?
probably your network interface... or TCP/IP configuration on MVS
lots of tuning is required under MVS to get TSM to run well...
and it still won't run as good as on a healthy IBM S70 AIX machine...
we got rid of our two MVS tsm servers
We have exported a node from an MVS platform to an RS6000. As the node was
imported all filespaces were renamed. User is having problems attempting to
retrieve data. All data is archive. Does anyone have experience with the
export/import process.
Thanks,
[EMAIL PROTECTED]
We have exported a node from an MVS platform to an RS6000. As the node was
imported all filespaces were renamed. User is having problems attempting to
retrieve data. All data is archive. Does anyone have experience with the
export/import process.
If Import finds a filespace of the same name
