For more information on this topic, review the following article: http://www.veritas.com/docs/000040937
NOTE: This is not a recommended way to back up such files as it bypasses the VSS APIs and therefore can compromise data consistency in backups - this is a method of last resort to back up the data.
Configure a Policy to backup the windows client in question. Edit the Backup Selection to resemble the following:
NOTE: 'hostname' is the hostname of the client, which should match the client name entry in the backup policy
NOTE: It may also be necessary to adjust the NetBackup Client Service on the client in question, and adjust the Log On As account from LocalSystem, to an Administrator level account which has full permissions on the host and local filesystems.
Use of a UNC path within the Backup Selection, to access the data will bypass the VSS logic used to determine if the files encountered during the backup job, are indexed and owned by System State or Shadow Copy Components thereby allowing them to be backed up (as opposed to filtered out).
Adjust the path to target the volume and or files desired.
This technique also bypasses the OS's ability to take a snapshot of the volume specified in the Backup Selection. No snapshot will be attempted.
This technique attempts to back up all files in the specified location, even locked and open files (no snapshot) . This is important to understand. Many, if not most of the files owned by System State are actively in use and therefore can not be backed up without a snapshot. The consequence of using this technique will likely be a job ending in Status 1.
NOTE: Attempting to protect an entire system volume (usually C:\) with this technique will not produce a backup image which is capable of being used to perform a full system recovery.