RE: VTL sizing / FC distance issue -- MIDRANGE-L

Not all VTL do the DUP, with some it would still be done with the Power9.
Not all VTL offer the DEDUP.
With some VTL, the DEDUP is done afterwards, 2nd process, not to slow the save.

We don't have a 2nd/HA/DR machine.

You don't have the fiber channel distance issue that I'm running into.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, May 09, 2019 11:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: VTL sizing / FC distance issue

The Power 9 does not duplicate the media. The VTL does. Offloading all those cycles, etc.
I happen to have a power 9 at the co-lo.
There are two ways to get the 'tape' from the co-lo if the local VTL dies.
1-Buy a new VTL and get them in sync.
2-Restore to the remote P9.
Since the co-lo has a P9 we have both VTL's dup each other. The co-lo holds our HA machine. Why not put your second VTL where your Mimix machine is and have them back up each other?

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Thursday, May 9, 2019 11:39 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: VTL sizing / FC distance issue

Rob,

How is the 2nd VTL, which is used for the DUPS, connected to your Power9?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, May 09, 2019 11:36 AM
To: Midrange Systems Technical Discussion
Subject: RE: VTL sizing / FC distance issue

No need to append volumes with a VTL. They do not take up the full allocated size. IOW, if you create 10 LTO7 tapes they do not take up the physical space of 10 mylar LTO7 tapes. They only take up the size written. LTO7 is basically a maximum size.

Dedup is a HUGE thing. Very HUGE thing. If you did three full system saves back to back to back you would not be taking up the space of three saves. Probably barely more than one save.

We have two VTL's which replicate "tapes" between each other. One is in Grand Rapids MI at one of those secure co-location facilities. The other is in the next room from me. Distance is no problem.

We have no physical mylar media at all.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Thursday, May 9, 2019 11:27 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: VTL sizing / FC distance issue

1) I'm trying to size a VTL based from my current LTO7 volumes/usage.
An LTO7 volume is 6TB native, 15TB compressed.
I'm using BRMS, and we append to our volumes to get maximum usage.
We also use BRMS control group auto dup feature for 2nd copy which is taken offsite daily.
Base on save statistics, I am seeing the 15TB compressed per volume.

55 full LTO7 at 15TB each - 825TB
15 scratch volumes at 15TB each - 225TB
32 full LTO7 offsite duplicated volumes at 15TB each - 480TB.

I'm looking at two options.
1) Deploy a VTL, which could be used for either the original saves or offsite duplication, keeping the current 3573 LTO7, one of which will be at a new offsite location.

2) Deploy two VTL, one for current backups, second for offsite duplication.

If VTL is used for BRMS saves, 1PB.
If VTL is used for BRMS off site duplication, 500TB.

Are these numbers in the ball park, acceptable?
Suggestions?

2) When talking with our network folks, the distance issue came up when discussing how to deploy either the new VTL or the LTO7 library at an offsite location.

From a network side, the numbers started adding up when trying to deploy a either a remote VTL or a LTO7.

How are others solving the distance issue for a remote offsite, library?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.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