Virtual tape does just what you'd think: a backup thinks it's writing to tape, but in reality the data is going elsewhere. It may still end up on tape eventually, but in the meantime it's heading for disk, local or otherwise. This stuff isn't cheap, but then neither are the systems where people would be interested in it.
It does raise some interesting questions, though. In the Unix and Linux world, we don't usually have to resort to anything like this: tar, cpio or whatever can already happily write to anything, so we don't need virtual tape. Most Unix utilities don't assume a lot about their output. Microsoft backup programs are, of course, much different, and will usually be hardwired to expect certain hardware.
As we move up from tar and cpio, things change. Higher level backup programs are more apt to be concerned with hardware details, and will want to both query and control a tape at a very low level. These programs aren't going to send a backup to anything that doesn't look like a tape drive, and more specifically a type of tape drive that the software comprehends. Virtual tape would be the only way to cajole these critters to write to some other storage.
But isn't there still something wrong here? Why would the backup app folks let IBM or whoever come in and sell thousands of dollars worth of software when it would seem that they could rather easily tweak their programs to write to anything? You would think that their design is a generic writer that calls stubs for various hardware specific features, and that it would be somewhat trivial to write stubs for disk backup or whatever. Apparently not. I can only guess, but if they can't do that, their software must be horribly complicated and extremely difficult to modify.
References: IBM ports virtual tape to Unix and Intel
Virtual tape offers first step toward disk-based backup
More Articles by Tony Lawrence - Find me on Google+

Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar