× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2020

Re: Compatibility between different vendors VTL solutions

I'd imagine if there's a ProtecTier VTL there should be fiber channel. I'll
have to ask.

The old server does have a LTO6 drive and we intend to put one LTO6 drive
in the new data center connected to one Power server. So I was thinking as
a slow manual process we could dump out a number of backups to one tape fly
that to the other data center and restore it. Each backup would be a about
a terabyte so you could write quite a few to one tape.

The plan in the new data center is to use VTL but a tape is just there for
contingency.

On Thu, Feb 27, 2020, 1:24 AM Rob Berendt <rob@xxxxxxxxx> wrote:

<snip>
What sort of connection would the second VTL require to the Power server?
</snip>
<replySnip>
In the old DC you would need a FC connection from your Power system to
your switch then to your new VTL in that same old DC.
</replySnip>

<snip>
Alternatively could we dump a number of backups to a lto6 tape cartridge,
ship that over and restore that to the new VTL?
</snip>
You mean you could do DUPMEDBRM to LTO6 at the old DC. Ship them over to
the new DC. Do a DUPMEDBRM from LTO6 to the new VTL.
Right?
Why would the new DC even have a physical tape library?
We have no physical tape drives or libraries. None. Haven't for years.
Never been an issue. Done bare metal restores. Don't even send physical
media to IBM anymore for in depth problem solving. All MSD's, etc go via
internet.
With the money you'd spend on physical media, libraries, shipping and
manual labor are you sure you wouldn't be better off with another VTL?



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 25, 2020 8:46 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.


No budget for a third but could possibly stretch to putting one in the
primary DC, connecting it to the ProtecTier VTL and dumping to the new VTL
using DUPMEDBRM.

Then ship the VTL to the remote site.

What sort of connection would the second VTL require to the Power server?

Alternatively could we dump a number of backups to a lto6 tape cartridge,
ship that over and restore that to the new VTL?

On Wed, Feb 26, 2020, 8:28 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Do you have enough pad in your budget to put a third new VTL at the old
DC? Then the Power system there could run a DUPMEDBRM from the old VTL
to
the new VTL. All your meta data would be saved. The new VTL at the old
DC
could then replicate to the other new VTL's. In the old DC you would
need
a FC connection from your Power system to your switch then to your new
VTL
in that same old DC.

From an lpar on my Power system in Indiana I can run a
WRKMEDBRM TYPE(*ACT) SYSNAME(lpar in Michigan)
Then with a little mumbo jumbo done on the VTL I can restore a save done
in Michigan on to a system in Indiana. This is how we do our saves on
our
H/A production backup lpar in Michigan to our primary development lpar in
Indiana. This is how we refresh our test data.

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 25, 2020 1:01 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.


The existing DCs have ProtecTier VTLs. The other remote DCs have no Power
servers nor VTLs but we are planning to put one in each location each
with
its own VTL.

On Wed, Feb 26, 2020, 1:31 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Is one of these DC's the one with the older VTL?

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: Monday, February 24, 2020 7:27 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.


I'll have to prefix all my comments that I'm not a IBMi person. My
background is z/OS but got involved because of my technical background.

As for backing up VTLs the plan is to have 2, one in each DC with
replication between them both. That is how we do mainframe backups.






On Sat, Feb 22, 2020, 1:21 AM Rob Berendt <rob@xxxxxxxxx> wrote:

How do you plan on backing up your new VTL at your local DC? Or
aren't
you?

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