Date: March 13, 2003 Time: 9:40 AM
From: Jerry Lawson
The Hartford Insurance Group
860 547-2960 [EMAIL PROTECTED]
----------------------------------------------------------------------------
-
It is interesting how in Data Processing, once you are associated with a
product, people keep asking you questions about it, even though you no
longer have a direct relationship. At least it's that way in my shop - I am
(and always will be) the ADSM/TSM guy. Not that it's a bad thing, but
sometimes the questions get a bit deep.
We are thinking about migrating our primary tape storage pool from cartridge
devices to an STK Virtual Tape device (This is a Big Iron based system). It
seems to me to be a doable thing - I'm a little concerned about reclamation
of the virtual volumes, but other than that, it's a positive move for us.
I have two questions, though...
1. Has anyone else done this, and what have your experiences
been?
2. The migration from the physical tape to the virtual tape
pool has caused us to think. We could just change the devclass unit type,
but then all of the current tapes would be incompatible - we would have the
OS trying to mount the tape on a disk device. Not good. A better approach
seems to be to create a new devclass, The question becomes where do we show
the relationship to the new devclass. Can we change the storage pool
definition to point to the new devclass, or do we have to create a new
Storage Pool as well, and then change the copy group definitions to point to
the new pool?
I've been away from this too long!
----------------------------------------------------------------------------
-
Jerry W. Lawson
Specialist, Infrastructure Support Center
Enterprise Technology Services Company
690 Asylum Ave., NP2-5
Hartford, CT 06115
(860) 547-2960
[EMAIL PROTECTED]
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all copies.
