Hi expert!
We have a TSM server (source) ver. 6.3.4 (AIX) which arcives files for the application ICC4SAP.
Three nodes are involved and these store their data (very small files) in three huge diskpools:
DISKPOOL1_400GB
DISKPOOL2_500GB
DISKPOOL3_200GB
We plan to export these nodes to a new TSM server (target) giving these a new node_name
on target.
As we see it, it will take a LONG time to export the data since it's many small files.
We will perform the flw. activities:
1. set up server-to-server communication (both tsm servers are running ver. 6.3.4)
2. export policy information
3. export the nodes in question with their archived data
But since there are so large diskpools, could we 'transfer' / copy the data in another way and connect them to the target TSM server? The diskpools for the source TSM server are residing on Storwize disks.
I guess that the data are remaining on the source server even though they are exported?
Are there any performance options to take into account during a pot. export?
If we had to perform an export node, I think we had to put in a timestamp since the application cannot be down during the time the export take.
Thank you for your comments!
We have a TSM server (source) ver. 6.3.4 (AIX) which arcives files for the application ICC4SAP.
Three nodes are involved and these store their data (very small files) in three huge diskpools:
DISKPOOL1_400GB
DISKPOOL2_500GB
DISKPOOL3_200GB
We plan to export these nodes to a new TSM server (target) giving these a new node_name
on target.
As we see it, it will take a LONG time to export the data since it's many small files.
We will perform the flw. activities:
1. set up server-to-server communication (both tsm servers are running ver. 6.3.4)
2. export policy information
3. export the nodes in question with their archived data
But since there are so large diskpools, could we 'transfer' / copy the data in another way and connect them to the target TSM server? The diskpools for the source TSM server are residing on Storwize disks.
I guess that the data are remaining on the source server even though they are exported?
Are there any performance options to take into account during a pot. export?
If we had to perform an export node, I think we had to put in a timestamp since the application cannot be down during the time the export take.
Thank you for your comments!