Can't do that because the two VTLs are in two different countries. From
what I understand using the DUPMEDBRM command will work even if the target
device is a physical tape unit. I'm guessing because you're running it off
the same LPAR when you did DUPMEDBRM command the updated BRMS information
stayed in the catalog?

On Wed, Dec 15, 2021, 1:49 AM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

We connected one lpar to both VTL solutions and did DUPMEDBRM for any
volumes needed.
Its a very manual and not potentially fast way, but doing this way
preserved the BRMS inventory.

Hope that is an option… Changing VTL vendors is no fun.

Bryan

On Dec 13, 2021, at 5:24 PM, Laurence Chiu <lchiu7@xxxxxxxxx> wrote:

I have a large amount of data on an existing VTL (IBM ProtecTier) what I
want to dump off and move to a different IBMi system and import into
that
system's VTL and integrate with the BRMS catalogue information.

The existing backup all have the same names (same nightly database and
libraries being backed up) and easily identified in BRMS by time/date of
the backup.

Because of many network constraints we plan to dump the information to
tape
using (at the moment) the DUPMEDBRM command and just stream the backups
to
many tapes.

Once we get the tapes in the new location we would import them into the
new
VTL and ideally integrate them into the new BRMS. But what is not clear
to
us is how we can export the existing BRMS information and import that
into
the new one to retain all the metadata.

So for example if we wanted a backup for a file XXXXXX taken on 1/1/2016
then we only need to look for that backup taken on that date and BRMS
would
be able to locate the right backup in the VTL and restore it. Note to
make
clear, file XXXXXX would exist thousands of time in the backup database
since it is a nightly backup of the primary database taken over several
years worth of operations.

I have asked the vendor doing the work to provide some advice but so far
they have not been particularly helpful. Any ideas from experts in this
group would be appreciated.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.