Network/Unplugged 5.0 uses Lazy Real Time Backup solution to keep source and destination always in sync, where Lazy technique reduces bandwidth consumption. Bandwidth throttling limits synchronization process to use only a portion of available bandwidth for better coexistence. These features couple with existing file level differencing and compression techniques to keep bandwidth usage to minimum level.

The 5.0 version can compress backup destination to make optimal use of storage space. Compression while transmitting data was available in earlier versions too. Additionally, project wise exclusion of files, folders and extensions, grace period for aging files and control of user space helps in better storage control.

The base product (client only version) of Network/Unplugged comes for $80. Adaptive file level differencing, compression, encryption and synchronization in disconnected state come with client server model, which is priced at $252. The trial version of product can be downloaded from http://www.mobiliti.com/netUP.html. Mobiliti, Inc., based in Edison, New Jersey, is a leading developer of synchronization and backup products. Founded in 1997, Mobiliti has developed Network/Unplugged and Continuity@Work series of products using patented technologies. For more information, please visit http://www.mobiliti.com.

In part, this problem is also rooted in malleable nature of computer software. No self-respecting civil engineer would design a bridge by slapping girders together until he has something that works; after all, if bridge collapses, it could take months to rebuild it. Similarly, no sensible architect would want to build a house without blueprints and floor plans. Yet it is commonplace for programmers to develop software using poorly chosen functions and only sketchiest of designs. After all, if software doesn’t work, they can always find bug and fix it—at least, in theory. In practice, these bugs are often difficult to detect, and fixing them can require extensive surgery. The consequences of an ill-designed software program can be disastrous indeed.

For this reason, I believe that high-tech companies need to give software engineering respect that it deserves. They need to develop a true culture of systematic software design, instead of merely settling for “whatever works.” A company that’s looking toward future must pay proper devotion to principles of software maintainability, proper documentation and elegant, robust design. It must also inculcate a culture of true software engineering among its employees. The failure to do so may work in short-term, but it is a recipe for long-term disaster.