Status 134 errors with NetBackup 3.4?

This Wiki is brought to you by Backup Central, where you can find the Mr. Backup Blog, Forums, and a mailing list for each forum!
Backup FAQs	Service Providers	Backup Software	Backup Hardware	Backup Book Wiki	Free Stuff	Miscellaneous

In patch 645 for NetBackup 3.4, the workaround for the Status 134 error messages indicates that the file /usr/openv/volmgr/DISABLE_RESOURCE_BUSY needs to be touched(an empty file created). There is supposedly now a TechNote from Veritas to correct this but the correct workaround is to touch the file

/usr/openv/volmgr/DISABLE_RESOURCES_BUSY

The difference is between RESOURCE and RESOURCES.

This needs to be touched/created on all the master/media servers.