ZFSDataMgmtinSolaris.pptVIP

* The other big ZFS feature found only in Solaris 11 is ZFS encryption. As noted we can now add the adjective Secured to this simple mission statement for ZFS. You set the encryption property at create time. That really isnt much of a limitation….. if you had an existing file system you wanted to encrypt, just use cpio or rsync to copy the data into a newly created encrypted file system. And of course encryption is on a data set basis not on a pool basis. One caveat here, you cant encrypt the boot disk. There are no plans to ever offer this on Solaris 10. * * * Remember the idea of boot environments is that you create a copy of the current boot environment, in other words a copy of everything that allows Solaris to run, kernel, config files, Solaris utilities, libraries and so forth... So we make a copy of that. Then you make changes to that copy like applying package updates. No impact on our availability because we arent making changes to the boot environment we are working in. When done we reboot to the new environment, test it, and if we dont like it, we simply reboot to the previous unchanged boot environment. A great safety net! This is a very involved diagram to illustrate a simple point. Step one of using boot environments is to create the copy and creating a copy in ZFS is pretty much an atomic operation. For Solaris 10, creating a boot environment can take 15-30 minutes. (last data point I saw was actually over an hour for a system 3. For Solaris 11, maybe 10 seconds or so. If it takes you a half hour to create a boot environment 1) you probably arent going to use them as a safety net every time you make system changes 2) it is likely the system will have changed during that 30 minutes copying so really havent got a copy. So at best LU has a pretty good copy not an exact one. On S11 with ZFS it only takes a few seconds to make a Boot Environment. ZFS is a copy-on-write architecture, so you dont have to do much because nothing has changed.