|
Tough to know where to begin with that last question...--
In a BRMS managed shop I would need to see some explanation as to why
anything would be saved to a save file and then saved to tape (virtual
or otherwise).
Ignoring that, when you use a VTL (Virtual Tape Library, not to be
confused with a tape device or a virtual tape image catalog) the IBM i
thinks it's saving to an IBM tape library. To the IBM i this tape
library could have one or more drives. And the IBM i thinks the
library could have a vast number of tape cartridges loaded into the
tape library. So the IBM i sends the data to the VTL like it was a
mylar tape library. Now, how the VTL stores the data on it's disk
drives is it's own business and is very proprietary between brands.
And how they replicate the data between two VTL's of the same
manufacturer is again proprietary and is NOT done by DUPMED or
DUPMEDBRM. Therefore you cannot just plop a VTL from a different manufacturer in there and have them duplicate the tapes between each other.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Laurence Chiu
Sent: Tuesday, February 11, 2020 2:45 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Compatibility between different vendors VTL solutions
CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender
and know the content is safe.
This is somewhat vague but why I asked about VTL solutions I was told this.
Backups are managed using BRMS.
The application saves the DB to a Save file and then saves the Save
File to tape. So perhaps the storage appliance is only being used as a
virtual tape device replicating what you would do with a physical tape or autoloader?
So the formats are not proprietary?
On Tue, Feb 11, 2020, 1:47 PM DrFranken <midrange@xxxxxxxxxxxx> wrote:
It would be 'very unlikely' that two different VTLs could exchangeall
data unless they were both connected to an IBM i partition where you
could utilize DUPTAP from one to another.
From the three vendors that I've worked with significantly the
format of the data on disk as well as the connection between systems
are very different between them. I expect that difference would
extend to virtually all vendors.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 2/10/2020 4:36 PM, Laurence Chiu wrote:
I am in a situation where in one data center there is a VTL
solution. I want to implement in another data center a VTL
solution and then copy
eachthe tape backups from the first to the second data center.
Assuming the backup is using BRMS do I need to keep the same
hardware solution at
atDC? So for example if one DC is using say a Dell VTL could I use
DSI
onthe second and still be able to migrate and use all the backups
taken
thethe Dell?
I'm actually trying to find out what specific VTL solution is used
in
options.first DC but thought I would ask the generic question to know my
list--
Thanks
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
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@xxxxxxxxxxxx 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@xxxxxxxxxxxx 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@xxxxxxxxxxxx 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 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.
midrange.com
