Q

Channel extending a tape environment

Storage expert Christopher Poelker offers advice on channel extending a tape environment.

We are looking to consolidate Mainframe CPUs from site A into site B. We are also looking to leave the existing tape environment (VTS/ATL, STK silos, floor drives) at site A and channel extend them from site B (approx. 250 miles). This would be for full time 24x7 tape operation, not just peer-to-peer replication or for offsite backups.

Do you have any recommendations, dos and don'ts, pitfalls, risks? Is there anyway to obtain information on others' experiences with channel extension used in this manner?

There are a number of companies that provide channel extension hardware and appliances. I will assume from your question that the current tape subsystems are SAN fabric attached, and you are currently using FICON connections from the mainframes to a switched fabric.

Please be advised that moving tape backup streams over extended channels would require substantial bandwidth between sites A and B. I'm not sure if you currently have dedicated dark fiber between sites, but that may be the minimum that would be required for multiple concurrent backup streams. 250 miles is also very far for extended channels. 100KM to 200KM is usually the top-end distance for either Fibre Channel (FC) or FICON extension before latency or "droop" occurs (ESCON extension is MUCH less tolerant to distance).

200KM is about 124 miles as the crow flies, so even using dark fiber connections and great extension gear will only get you halfway there for channel extension. Using an IP bridge to your fabric with a leased IP connection would be a better solution for that type of distance. Buffering, packet shaping, compression and spoofing of the connection can reduce a lot of the latency issues. Common Mainframe PPRC, XRC and GDPS configurations can utilize connections such as this. An even better approach may be to use SONET as the connection medium, since some of the FICON to SONET vendors support high-bandwidth trunking, and distances up to 40,000KM.

Your bandwidth requirements will depend on how much data you need to move across the links. I use a simple formula of 10 Mbit of IP bandwidth required for every 1 megabyte (MB) of data per second transmitted. As for do's, don'ts, pitfalls, and risks, there are too many to discuss using this as a venue. You should sit down with your storage, tape and switch vendors and have an in-depth planning session to go over all the details.

The tape vendors you mentioned in your question have a lot of experience in this area, and may be a very useful resource for you, as would your FICON switch vendor. You did not mention the storage vendor you are using, but I would also include them on the planning session.

This was first published in July 2005

Dig deeper on Tape backup and tape libraries

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSolidStateStorage

SearchVirtualStorage

SearchCloudStorage

SearchDisasterRecovery

SearchStorage

SearchITChannel

Close