• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TSM virtual volumes for export/import nodes data

sra006

ADSM.ORG Member
#1
Hi ,
I am evaluating using virtual volumes to store exported data from tsm clients.
I have time to export nodes from source to virtual volumes, and at some point I would need to import them to
the target to be nodes on the target.
My question is :
will it improve import time if I use virtual volumes that already on the target server to create source nodes on the target? vs directly using server to server communications for exports ?
Virtual volumes are controlled by the source server, does it mean that all I/o will be looping back to the source,
even if it resides on the target?
Thank you,
Al
 

marclant

ADSM.ORG Moderator
#2
will it improve import time if I use virtual volumes that already on the target server to create source nodes on the target? vs directly using server to server communications for exports ?
No because you would be moving the data twice.
Virtual volumes are controlled by the source server, does it mean that all I/o will be looping back to the source,
even if it resides on the target?
The I/O is handled by both the source and target. Source is doing I/O over the network to the target, the target is doing the physical I/O to the media (tape or disk).
 

sra006

ADSM.ORG Member
#4
Thank you for the replies.
One of the reasons I could not run exports or replication is because my final target server does not exist ,
it will be build in 2 months. Meanwhile I was considering other options, that will avoid creating multiple tsm nodes on the "in-between target server"
As I see in one of the replies the target server will control the virtual volume pools for staging data .
My process for migrating a node :
source_srv ---> export to virtual v on "temp target" pool
import from "temp target" to the final target

In the scenario of exporting a node to a virtual volume on the "temp" target and importing it to the final target
will the data flow directly to the final target from the "virtual volumes" and just metadata gets referenced by the source?
This is what I am trying to clarify.

Best ,
Al
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 9 22.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 19 47.5%
  • Let's be formal and just say Spectrum Protect

    Votes: 8 20.0%
  • Other (please comement)

    Votes: 4 10.0%

Forum statistics

Threads
31,001
Messages
131,978
Members
21,255
Latest member
pzzl321
Top