No one buys "Open File Backup" as a distinct licensed feature anymore - there is no specific license anymore. Instead, OFB comes with NetBackup Enterprise Server.
.
This next statement is probably true for all general purpose OS and all general purpose file-systems:
If an application opens a file and places a restrictive lock on a file (aka a blocking lock, or a dis-allow read lock) then there's nothing anyone, even an OS, let alone a backup product, can do about it.
.
The term OFB is old and no longer relevant. It comes from the very early days when Windows was young and didn't have the feature of allowing a file to be "locked for write, allowed for read" - i.e. in the old days, if a file was locked then it was locked, end of story, and no backups could be taken - and so third party backup product developers started looking at how to backup these locked files, and spent much time and effort developing neat tricks to get around the problem of locked files and read them - and so, because the backup software vendors spent so much time and money developing these tricks, they needed to recoup their investment and so made it a chargeable licensed feature, hence the "NeatBackup feature" name of "OFB". All this is no longer relevant.
.
What is relevant these days, is to get your application users to close their files before backups. If NetBackup cannot read a locked file, then some other aplication has placed a very hard lock on a file and there's nothing that you or I or VSS can do about it - and so, one has to change one's working practices (i.e. your users), or go back to the vendor/developers of the application which is placing the hard lock (effectively a dis-allow read) on files - and get them to modify their code.
