That is not really possible since the source VTL is IBM ProtecTier and it's
EOL.

The target VTL is in another country(!) with two different Power servers.
But they are running the same application and backing up the same libraries
each night.

We have access to both the source VTL and BRMS and of course the target VTL
and BRMS. As a starter our target system vendor suggested we try this out
before we do a bulk migration.

Source System.
1. Create a virtual tape library, see
https://www.ibm.com/docs/en/i/7.3?topic=tape-setting-up-virtual-storage
2. Duplicate historical data of 3 or 4 tapes to the VTL created above.
3. Provide the BRMS meta data, library QUSRBRM to *SAVF.
4. FTP the virtual tape to remote location
5. FTP the BRMS meta data, *SAVF.

Target System
1. Create a virtual tape library, see
https://www.ibm.com/docs/en/i/7.3?topic=tape-setting-up-virtual-storage
2. Add the tape received from the source system into the new virtual
library.
3. Duplicate the tape (virtual) to a VTL tape and update BRMS.
4. Perform a restore of the data and verify it is valid and matches the
original source tape.
5. Perform user testing and acceptance of the data and process to restore.

But that is all theory and I am waiting for the VTL SME's who manage the
source system to review and comment.

On Fri, Dec 17, 2021 at 12:33 AM Jack Kingsley <iseriesflorida@xxxxxxxxx>
wrote:

If you would have stuck with the same vtl vendor, would this have made this
overall easier?? Next question that I thought of was, you have the VTL
side for configuration as well, will you need to take that into
consideration for this, sounds like no, but overall was not sure.

On Wed, Dec 15, 2021 at 5:38 PM Laurence Chiu <lchiu7@xxxxxxxxx> wrote:

Well I'm still waiting for my support vendor to see if they can do that
when it's going to a different VTL. Doesn't seem like something they do
very often.

On Wed, Dec 15, 2021, 12:36 PM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

Yes, brms kept the info.



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