Such possibility exists. I guess you could easily add LGTO binaries to exclude list for AV check and see if that makes any difference.

Why do you think space is your issue? The error itself is "The I/O operation has been aborted because of either a thread exit or an application request." so I would check Dr. Watson log first. Second, your module version is not latest build so I would make sure I have latest one before moving any further.

Temp files are created in ..\nsr\tmp unless you specify some other location.

My original thought was that it was trying to create a temporary file and did not have the space and was aborting due to that. I have checked the event logs and there are no additional messages related to NW. I did see messages that Symantec was having problems scanning the email attachments. I am wondering if this has something to do with it. It looks like this is happening throughout the backup.

It appears that the Symantec exchange module is scanning the email messages and attachments as they are being read to be backed up. The are a lot of messages like this one in the log
The attachment "" located in message with subject "FW: CPOE Radiology Status Update Initial "Go Live" Nov. 2004 (received)", located in XXXXX/Journal has violated the following policy settings:
Scan: Auto-Protect
Rule: Unscannable File Rule
The following actions were taken on it:
The attachment "" was Logged Only for the following reason(s):
Scan Engine error. Error code: 0xC009008F

We are reviewing this with Symantec.

Symantec requires us to move to the latest version of the antivirus exchange module. The message being displayed is resolved in that release. It may fix the backup problem. We are reviewing the release notes and will schedule the upgrade. I will be installing that latest release of the NW Exchange Module next week.