> > That's why I don't subscribe to the notion that "development" > data is less important than production data. Especially in a D/R > environment. When stuff breaks and you have to go to D/R, which > production systems will need to be fixed?
We have procedures in place to allow logon to Prod LPARs. Yes it's been tested, yes it works. Anything that is in production has been migrated to the prod level of Endeavor - everything needed will be in place *at DR*. > For those of you who do segregate DASD because of D/R, I have a question. > Do you regularly validate your D/R plan by going to your D/R site and > running real work for a period of time? If so, what does management > think about the programmers that are idled for the duration? Doesn't take long to restore an environment - all the backups are in the silo out there. Easy to do in a test, probably of little consequence in a real DR scenario. We generally get both devl environments up within a few hours. Most of them (me included) are contractors. The cost of a few programmers time would be inconsequential compared to a business outage in a real disaster. Shane ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
