In general .. Mirroring is a recovery technology for infrastructure - should you lose hardware / geographic incident, etc. - If you have any data corruption (intentional or otherwise) - Mirroring just makes it worse.. If you’re serious about having a development environment (Most shops are - Prodduction fixes, round the clock development, etc) you have to treat it as good as you would production.
Backups are for putting the pieces back in the event of inadvertant (or intentional) corruption / deletion / modification of something. You need both - if your environment is important to you. Sell it like this - Suppose you have a major development outage - what’s that costing you in lost productivity by the dev staff? What if you had a production issue during that outage - is your source code availble? Could you apply / test a fix? lastly - how long would it take to rebuild / buy a new development environment if you had a major issue. Could you be down that long? I suspect not, if you are like most places. At a minimum you should back up and offsite your source code repos - any IP you cannot easily replace. My .02 Chad > On May 19, 2016, at 9:02 AM, White, Andy <[email protected]> wrote: > > Hi people - For companies that mirror their mainframe DASD via XRC, SRDF, how > many of them back up the development DASD? > > Currently, we mirror all production but don't mirror the development DASD we > back most via VTS but I am pushing or trying that we back up all DASD. My > thoughts about this are the development cycles and releases have a lot of > time and money invested if it lost this work, how much is this worth? > > Anyway, if you are mirroring your development how did you "sell" it to your > management? If you're not why not? > > Thanks > Andy > > > > The information contained in this message may be CONFIDENTIAL and is for the > intended addressee only. Any unauthorized use, dissemination of the > information, or copying of this message is prohibited. If you are not the > intended addressee, please notify the sender immediately and delete this > message. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
