Ok, so assuming the primary storage takes care of DR backups, active/active, 
sync/async replication, physical risks [earth(quake), fire, wind, water, 
power], assures ease of standing up the DR environment after a whoopsie, isn't 
from a rent-seeking company that does planned obsolescence (i.e., there's a way 
to upgrade h/w without having to take it down).

Thank you, I don't mean to say everything is already accounted for, just trying 
to surface the kind of issues/things to consider.


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, July 5, 2020 11:07 PM, retired mainframer <retired-mainfra...@q.com> 
wrote:

> You might want to consider whether transportability is an issue. How do you 
> get your backups to your disaster recovery site? The systems I worked on were 
> prohibited from connecting to public networks.
>
> You might also want to consider operational security. If your new storage 
> device is physically on line, it is subject to things like accidental data 
> deletion and damage from a power surge, fire, or EMP. A tape drive in a 
> secure vault could probably survive the next mass extinction.
>
> And after you resolve all the technical issues, somebody should still bring 
> up cost. It's not just acquisition cost per megabyte but things like 
> equipment footprint, power, air conditioning, maintenance. And don't forget 
> planned obsolescence. Mine was one of the last sites in the company 
> (country?) to use 9345s.
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On
> > Behalf Of kekronbekron
> > Sent: Sunday, July 05, 2020 5:13 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Storage & tape question
> > Hello List,
> > Just wondering ... assuming there's a primary storage product out there 
> > that can store
> > how-many-ever hoo-haa-bytes, and is a good product in general, it should 
> > make sense
> > to begin eliminating all tape (3490/3590) use right?
> > First, ML1 & ML2 in HSM, then HSM itself, then rebuild jobs to write to 
> > disk, or do
> > SMS/ACS updates to make it all disk reads/writes.
> > Looking at the current storage solutions out there, this is possible, right?
> > What would be the drawbacks (assume that primary storage is super 
> > cost-efficient, so
> > there's no need to archive anything).
> >
> > -   KB
> >
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
>
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to