Sorry for lack of details..lemme see if I can fill in the blanks.
1. Not sure what difference is between Disk Storage Unit (DSU?) and DSSU...
2. I get all sorts of error codes...mostly 84s on failed jubs. Sometimes 58, sometimes 53. I did some further troubleshooting looking at buffer sizes and whatnot and it looks like the server is waiting on empty buffers, waiting on full buffers, etc.
3. Netbackup 6.5.2A...clients running the same thing...all clients including exchange ones are on 6.5.2A with a new binary on each exchange client to allow public folder jobs to run. This was probably fixed in 6.5.3, but I haven't yet upgraded.
4. Exchange 2003 Enterprise SP2, all updates.
5. Correct, not a third party. We use SAMFS and have a 1TB CIF share presented for backups. Once it gets finished with files, after so many hours, it'll move it off to tape automatically...but the file system shows the files are still there, but in th background the files may be moved to tape or they may be still sitting on disk. But no files that are active will be moved off of active disk.
Interesting note on the water mark...each of our storage units (Quarterly, Weekly, Daily) are set for high/low of 98/80. And while I looked, all of my exchange backups completed fine last night...go figure. YOU FIXED IT! :)
I know the issue pertains to the CIF share by SAMFS. One of our engineers had to hack a version of Samba to get it running in Solaris...as their is no native CIFS support. I carved out a share on one of our netapps and loaded that as a test storage unit in Netbackup, and every backup worked perfectly. I know the samba is the culprit...i'm just trying to minimize the failures in the existing environment for my backups. IE...i want to tweak the client and server settings, buffer sizes, etc.
One of my Exchange clients I set for a 256k buffer rather than 16k. Not sure if that was good or bad, but I don't think it had any positve or negative impact.