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/
midrange.com
