MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

RE: DUPTAP learned something new



fixed

Jim,

When I do a multiple device save, BRMS keeps all objects for a library on the same volume.
Only libraries are spread across volumes.
IFS can spread, but not recommended, the recovery could be ugly.

Parallel device resources:
Minimum resources . . . . . . . . . . 2 1-32, *NONE, *AVAIL
Maximum resources . . . . . . . . . . 2 1-32, *AVAIL, *MIN

Specifies the minimum and maximum number of device resources to be used
for parallel save operations during backup control group processing.
Not all backup items can be saved using parallel resources. If a backup
item does not support parallel save operations, the save will be
performed as a serial save. Backup items capable of parallel saves can
be mixed with backup items limited to serial saves. See the specific
Backup item help to determine whether the item supports the use of
parallel resources.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Wednesday, June 18, 2014 9:22 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: DUPTAP learned something new

I would check to be sure the combined tape can be used for recovery. The way IBM save with multiple devices works is different for large objects vs.
small objects. For large objects it "may" split the object up between tapes, so just because those files wind up on one tape, the recovery may not work as you expect. I've not tried combining tapes like you suggest so I don't have direct experience. I suspect that some information on the tapes used etcetera is saved on the tapes so the restore commands understand how to request tapes.

In this case BRMS is an interface to the IBM save and restore commands, so BRMS is not driving the requirements here.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Wednesday, June 18, 2014 7:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: DUPTAP learned something new

HA, That's good! However I suspect only a small subset of readers will have four tape drives available.....

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 6/17/2014 10:33 PM, Steinmetz, Paul wrote:

Larry,

Currently doing that.
Here's another tip.
Use 4 drives on a system save to minimize the down window.
Once complete, 4 AUTODUPs dup and append the 4 volumes to one volume.
Now you have the entire system save on 1 single volume.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Tuesday, June 17, 2014 10:22 PM
To: Midrange Systems Technical Discussion
Subject: Re: DUPTAP learned something new

'ish'. WHat I mean by that is for the thing to be bootable all the
correct files need to be at the beginning, this is likely where you ere going. What you CAN do, however, is dup the data portion by using the 'Start Sequence Number (FROMSEQNBR)' parameter and thus consolidate them that way.

If you think about it, old tapes to new tapes you can often get 10 or
more
to 1 and that's if the old ones are mostly full!!

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 6/17/2014 4:47 PM, Bryan Dietz wrote:

Be aware that you cannot "consolidate" SAVSYS tapes. they must start
at seq #1.

Bryan

Jeff Crosby said the following on Tue, 6/17/2014 4:02 PM:
After all these years I learned something new about the DUPTAP command.

There's a TOSEQNBR parm where you can say TOSEQNBR(*END) and it will
add to the end of the destination tape. I have a number of archive
tapes I decided to consolidate and that will make my life easier.

Since I learned something new, I can go home now. :)


--
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