My design goal is VTL for on-prem backup and LTO tape for off-prem.

Out of interest when I asked IBM about VTL they recommended DSI as IBM no
longer do VTL for Power. One other vendor is proposed DELL. Is there much
between them?

On Sat, Dec 14, 2019 at 1:21 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Jack,
VTL replication was discussed. However once someone has it in their head
that they must have physical tapes I find that it's banging your head
against the wall to try to convince them otherwise. Remember the old
saying "Not my monkey, not my circus".

I do though resent the implication that our data is "not critical" and is
therefore expendable. The powers that be here who wrote the checks for
separate Power systems in separate data centers with their own networking
equipment, VTL's, Replication software, etc might take umbrage to that
belief.

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
Jack Kingsley
Sent: Friday, December 13, 2019 6:31 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Thoughts on this design for two Power servers across two data
centers

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.


Could you add VTL replication if it was supported.

On Fri, Dec 13, 2019 at 4:35 AM Laurence Chiu <lchiu7@xxxxxxxxx> wrote:

I must I am confused why mirroring the SANs at the SAN level would be an
issue? The plan was to have the DR Power server off. Then the SANs would
replicate the data in real time and that data would always be application
data. If there was a failure in the primary DC, then why would the DR
Power
9 fail IPL when the boot volumes content hasn't changed? That's how we
do
it on the mainframe but then Z mainframes connected to DS8K's are not
quite
the same as Power servers connected to V5020 SANs.

As for maintenance etc. could we do that one LPAR designated for test/dev
and not replicate the volumes they are on. Then when we were happy with
the
changes, copy them to the production LPAR (during a planned outage) and
then test. SInce we were in a planned outage, we could temporarily
shutdown replication since no new data is being created,

The VTL is for local tape backup. The LTO is for offsite backup in
another
city. This is critical financial data so backups on two VTL's is not
enough
for archiving.

On Fri, Dec 13, 2019 at 3:01 AM DrFranken <midrange@xxxxxxxxxxxx> wrote:

I would add IBM PowerHA to manage the mirroring parts of the SANs. If
you use the mirroring 'bare' then you're replicating the entire
partition and as such if you need to flip to the backup you guarantee
an
abnormal IPL. You also lose the ability to do maintenance activities on
one system (Upgrades, full saves, PTFs) while you're running on the
other system.

One other comment. With VTL do you still need LTO? Each DSI unit can
replicate to the other so you get offsite backups that way.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/11/2019 4:33 PM, Laurence Chiu wrote:
Looking to deploy new Power servers across two data centers to
support
application that is low volume but mission critical and high
financial
value.

I am using the following design guidelines.

1. Both servers use SAN no disks. Total 5TB max
2. Data is encrypted at rest
3. Data is replicated in real time across the two sites
4. Backup to VTL
5. Off-site backups to LTO tape

So the kit would be

1. Two Power 9 servers 16GB FC
2. HMC
3. IBM Storwize V5000 using its encryption and mirroring software
5. DSI IDSI520-D04 VTL
6. LTO7

This is for an Enterprise that already has mainframes and DS8K SANs
with
SKLM supporting encryption so it's not over cooking it

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