Hi Christian,
Thank You! I ran the command and it showed where the data was.
Ok, I didn't know TSM would automatically create the node. that
explains the message ' Node SNJ265 is already registered" I saw in the
Server Log.
Thanks for the explanation!
Best Regards,
Tim
Hi,
As Shawn say. If you run "q occ" it will show where the data is.
If you don't pre-define the nodes, then will TSM automatic create the node in
your Standard Domain and copy the data to your Destination Storage Pool in your
Default Management class.
And when the migration is done do you need
On 8 nov 2009, at 16:46, Huebschman, George J. wrote:
"Server" is not a column name, use "group_name" :
I know that server is not the name of any column in the group_member
table. What I'm surprised about is that TSM parses this as a literal
string rather than as a column name in my select.
"Server" is not a column name, use "group_name" :
GROUP_MEMBERGROUP_NAME 1 1 A VARCHAR 64
0 FALSE Server Group
GROUP_MEMBERMEMBER_NAME 2 2 A VARCHAR 64
0 FALSE Members
GROUP_MEMBERCHG_TIME3 TIMES
AIX 5.3 TSM 5.5.2.0:
tsm: TSMSERVER2.DEMO>select server from group_member
Unnamed[1]
--
SERVER
huuh? :)
definitely not what I expected
--
Met vriendelijke groeten/Kind regards,
Remco Post
r.p...@plcs.nl
That assumes that the compression occurs file by file. Is that true or is on
the transaction. I suppose it is on the files themselves and all clients would
compress the file into the same set of bits. If it doesn't do that though,
then your high dedup rates won't be realized.
Kelly Lipp
Chie
A TSM server and some TSM clients are connected to SAN by conventional HBAs.
What happens if some clients come to SAN via FCoE? Imagine an IBM blade
equipped with converged network adapter (CNA) accesses above SAN via an
intermediate FCoE switch, what are the considerations for a fully-functional
T
