Bill, <snip> > The > intended > nature of CFW is that the data is volatile and can be easily recreated. <snip>
For HDS all of cache is battery backed, and for HDS USP and EMC the changed data is destaged to disk if power is dropped. This means CFW is always written to non-volatile storage. In HDS and pre DMX3 it simply means there is only one copy of CFW data in cache. For architectures that use a separate NVS it makes sense that a synchronous commit would have to be forced to disk to become non-volatile, but that is just one technology left over from the 3990. Not every vendor used this method. Ron ---------------------------------------------------------------------- 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
