Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: rudedog who wrote (32911)	6/19/2000 8:38:00 AM
From: DownSouth	Read Replies (2) \| Respond to of 64865

If you come across with an explanation of SUNW's "snapshot", please pass it on. I hope you will indulge in studying NTAP's SNAPSHOT mechanism, which is based on the characteristics of NTAP's Write Anywhere File Layout: netapp.com I am sure you will agree that because no journaling other than the root inode is required and multiple snapshots can be available to users very easily, SNAPSHOT is far superior to any system based on journaling, provides all of the restore capabilities of journaling, requires far fewer resources, and results in very efficient methods to create remote SNAPSHOTS and incrementals. I do want to learn more about what SUNW is doing, though. I'd be its more elegant and innovative than a journaling technique. There was one disturbing phrase used in the webcast however. They discussed "integrating snapshot into the application". That would indicate that the snapshot mechanism is not transparent to the app and is app specific. I don't really think it is, but I don't know what the mechanism is, either. Anybody?