MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

Re: DUPTAP outside BRMS



fixed

Why is it so important for you to have the same volume ID's ?
What's wrong with having different volumes with the same data on them ?


On Sat, Mar 22, 2014 at 11:54 AM, Bakutis, Becky <
BBakutis@xxxxxxxxxxxxxxxxxxxx> wrote:

Thanks Paul, I think the resolution is to expire the volumes in BRMS as
they are only in there to keep organized and run the duptap command. I
believe I was making this way too difficult.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, March 21, 2014 3:52 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: DUPTAP outside BRMS

Becky,

If one your requirements is that the dup volume has the same volume as the
original, then you can't use DUPMEBRM, (can't have 2 tapes with same volume
in BRMS.
But you might be able to use DUPTAP.

Duplicate Tape (DUPTAP)

Type choices, press Enter.

From device . . . . . . . . . . > TAPMLB01 Name
To device . . . . . . . . . . . > TAPMLB01 Name
From sequence number:
Starting file sequence number *FIRST 1-16777215, *FIRST
Ending file sequence number . *LAST 1-16777215, *ONLY, *LAST
To sequence number . . . . . . . *FROMSEQ 1-16777215, *END, *FROMSEQ

Additional Parameters

From volume identifier . . . . . *MOUNTED Character value, *MOUNTED
+ for more values
To volume identifier . . . . . . *MOUNTED Character value,
*MOUNTED...
+ for more values
Tape density . . . . . . . . . . *DEVTYPE *DEVTYPE, *CTGTYPE,
*QIC120...
Data compaction . . . . . . . . *FROMFILE *FROMFILE, *YES, *NO
Files to duplicate . . . . . . . *ALL *ALL, *ACTIVE

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bakutis, Becky
Sent: Friday, March 21, 2014 6:36 PM
To: Midrange Systems Technical Discussion
Subject: RE: DUPTAP outside BRMS

Someone suggested ordering cartridges with the same labels, expiring the
cartridges from the media class and then running the duptap command. This
should remove any hooks to BRMS...hopefully. If anyone sees any obvious
errors in my thinking, please let me know.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, March 21, 2014 2:40 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: DUPTAP outside BRMS

Becky,

We dup all are volumes, you shouldn't have an issue, assuming you have a
tape library with at least 2 devices, or 2 stand alone devices.
DUPMEDBRM is slow, a full LTO 5 volume takes 10 hours.
LTO 2 should be considerably less.

sbmjob, DUPMEDBRM, F4, fill in the fields as such.
Do this for each volume, simply change the from volume identifier.
Fill in the to media policy with one that matches your volumes.

Label . . . . . . . . . . . . .
From volume identifier . . . . . > 001008
From device . . . . . . . . . . > TAPMLB01 OPT05, TAPMLB01,
TAPMLB17.
To device . . . . . . . . . . . > TAPMLB01 OPT05, TAPMLB01, TAPMLB17.
From sequence number:
Starting file sequence number > 1 1-16777215, *FIRST
Ending file sequence number . > *LAST 1-16777215, *LAST, *ONLY
To sequence number . . . . . . . > *END 1, *END
To media policy . . . . . . . . > PERMTN *SYSPCY, *NONE, APPEND10D,
Input volume list . . . . . . . > *VOL
+ for more values
From device end option . . . . . > *UNLOAD *REWIND, *LEAVE, *UNLOAD
To device end option . . . . . . > *LEAVE *UNLOAD, *LEAVE, *REWIND
From system . . . . . . . . . . *LCL

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bakutis, Becky
Sent: Friday, March 21, 2014 5:22 PM
To: midrange-l@xxxxxxxxxxxx
Subject: DUPTAP outside BRMS

I have ten LTO 2 cartridges used for long term storage/retrieval of
Robot/REPORTS items. We do not have Robot/Save, but the native commands
savobj and rstobj work fine. Robot/REPORTS has a database that keeps track
of each report along with its volid. We have BRMS installed and the
cartridges are in a media class just for organizational reasons. Now my
dilemma is we will be going live with HA in a few weeks. I need to figure
out a way to duplicate the ten cartridges using the same volid's so these
can be sent to the city that houses our HA machine.

I spoke with Help Systems and they offered a rather cumbersome process
which is plan B. They also told me that Robot/Save has an exit that can be
removed when duplicating outside of their product using the same volid's.
They thought BRMS may have such an exit. They were helpful in giving me
ideas. When I tried to inztap a cartridge with an existing volid that was
used for Robot/REPORTS I received a message that the volid has not been
expired. This tells me BRMS has it's hooks somewhere. Is there a way to
duplicate cartridges using the same volid?

Becky Bakutis

Republic Services
W: 480.627.2760


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact