Steve--That wasn't the answer I wanted to hear but is the type I
expected. We don't use VM:Tape, just VM:Backup. A work-around I've
thought of is to do the backups, which happen in the middle of the
night, in 2 separate runs. First a backup specifying the 3590 tape pool
and then another backup specifying the virtual tape pool. They wouldn't
be exact but at least the taking the default on a restore of the most
recent backup would pull the virtual tapes rather than the 3590
cartridges.
On the other hand, I'll have to talk with the group to see if it really
makes any difference as to which gets pulled for a restore. The result
is going to be the same. One purpose of the virtual tape was to allow
us to get an old 3494 out of use and off maintenance. Mission
accomplished, even tho not esthetically pleasing.
Jim
Imler, Steven J wrote:
You VM:Backup System Programmer is correct ... the "higher" density
media will always be preferenced in the volser list sent to VM:Tape. =20
The simplest thing I can think to do is use a VM:Tape COMMAND EXIT that
swaps the 2 volsers in the list. =20
Alternatively, I suppose you could "outcode" (CHECKOUT) the 3590 tapes,
I think that would prevent them from being selected (but you'd need to
remember to check them back in before they can be scratched for reuse).=20
JR (Steven) Imler
CA=20
Senior Sustaining Engineer
Tel: +1-703-708-3479
steven.im...@ca.com
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Jim Bohnsack
Sent: Tuesday, June 16, 2009 10:34 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: VMBackup question
We have installed a Luminex virtual tape system. My question isn't how=20
to make it work. It seems to be doing fine. The only problem and the=20
reason for my question is that I have the virtual tapes defined as 3490C
tapes. My quandary is the fact that I have the virtual tapes defined as
the VMBackup Primary Resource Pool and and a 3494 robot with 3590=20
drives, located in a different location, as the VMBackup Copy Resource=20
Pool. It works just fine for backups.=20
Restores, however, result in VMBackup picking a 3590 tape rather than=20
one of the 3490 tapes. I know, or think I know, that I can get around=20
that using VMBackup Job Template files and specifying the input tape=20
volser and/or density. That's a little awkward. I want the restores to
be able to be done from the VMBackup screens so our admin. people can do
them. The VMBackup System Prog. Ref says that the tapes for a restore=20
are chosen from a density preference list with the higher density tapes,
naturally, being chosen first. That's logical, but not what I want.=20
Does anyone have any idea as to how to force VMBackup to use a different
list? I have a question open the CA but I was hoping that someone has=20
faced the same question .
Jim
--=20
Jim Bohnsack
Cornell University
(972) 596-6377 home/office
(972) 342-5823 cell
jab...@cornell.edu
--
Jim Bohnsack
Cornell University
(972) 596-6377 home/office
(972) 342-5823 cell
jab...@cornell.edu
