ArcServe 11.5 E3719/E3712 with File System Devices

[mikehiland]

Periodically, we experience a job Failure with E3719 and e3712 errors. The destination for the backup job is a file system on a server across the network. This most recent episode shows "E3719 Unable to write to media" followed immediately by "E3712 Unable to close session". There are a few other E3712 errors in the job after that.

In the NT Event Log, we see an Application Popup Information message indicating a "Windows - Delay Write Failed" telling me that Windows was unable to save the data, the data was lost, could be a hardware or network failure.

I see no other Errors in the Event Logs of the Media Server or the target server of the backup job (where the backup files are stored) that would indicate a disk or network issue.

Finally, I also see numerous instances of this NT Event Log entry on other days - BUT - the ArcServe job did not fail on those days!

Can anyone provide some thoughts on E3719 and E3712 with respect to File System destinations as opposed to Tape? I have reviewed the documents suggested in other posts, but they are geared towards SCSI and tape drives.

Thanks!

 

[davidmichel]

the 3xxx level of errors are from Task so putting the Job Engine into debug might help. Thats done via the ARCserve Server Admin.

Network Monitor can be left running on both systems to tell if there is a network problem.

 

[mikehiland]

I just stumbled onto CA Tech Document TEC268739 which closes with the recommendation that you do not backup File System Devices as part of a regular tape backup job.

We do this every night.

Is anyone aware of whether this practice can corrupt the File System Devices? Maybe that is why the are OK for a while and then start to throw errors?

Thanks for any comments!

 

[davidmichel]

I have not heard of it corrupting the FSD but it you want to migrate the data to tape use tapecopy.