delayed write failure with DLO Agent

[Kent_Belcher]

We're experiencing the following error with some of our DLO Agents.

{Delayed Write Failed} Windows was unable to save all the data for the file \Device\LanmanRedirector. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file \\NWD2FAC1\NWD2DATA1\ANALOG-kbelche\.dlo\kbelche-l03\c_\documents and settings\kbelche\my documents\mail\mailbox.pst. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

This occurs on Backup Exec 10.5484 SP1 and is intermittent. You can see by the content why it would be alarming to our clients. We have been able, in some cases, to mitigate this by mathing the PC NIC speed to the port speed on the switch, but this does not work in all cases. We are running W2K Server for BE10 and a W2K server with a Dell/EMC AX100 Fibre Channel Drive Array for the data store.

Has anyone else seen this error and does anyone have a more permanent fix?

Thanks,

Kent

[Renuka_-]

Hello,


1. The Open Transaction Manager (OTM). Using OTM makes a clean sector-by-sector copy of the working server disk onto the secondary drive while the server is live.


Resolution has traditionally been to uninstall/disable Otman, or update it.


2. The error may be occurring on both SCSI attached and fibre attached systems (if you have fibre channel).


Resolution is to update to the latest firmware for the controllers attached to the system in question.


3. Check and verify the length of external SCSI cable. If it exceeds the recommended length this error could happen. The length of the cable is determined by contacting the manufacturer of both the SCSI adapter and the cable manufacturer.


4. Verify proper SCSI termination. Check whether software only termination is implemented or active hardware termination. Contact the SCSI adapter manufacturer for best recommendations.


5. Observe if heavy local file I/O to the disk(s) has lead to this problem being triggered. If this is the case check the SCSI controller's cache settings. Try adjusting the cache for 100% write, or disable the cache altogether.


6. Analyse whether there is heavy network I/O to the disk(s).
This document provides an explanation and solution "How to Disable Network Redirector File Caching MS Q Article Q163401" to disable NT file system cache for the redirector.
Link is
<>


7. Another reason for this problem relates if a Non NTFS partition resides on the shared cluster disk.
Microsoft Q Article 275704 provide a workaround. Link is Q275704 - Cluster Disks May Be Incorrectly Accessible from All Nodes <>

Other Related Articles


The following are all related articles on the Delay Write Failed issue :-


Error Message: System Process - Lost Delayed-Write Data (Q252974)

<<>>;EN-US;q252974


Error Message: System Process Lost Delayed-Write Data (Q247065)

<<>>;EN-US;q247065


System Process Loses Delayed-Write Data with Windows Clustering (Q272569)

<<>>;EN-US;q272569

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[Kent_Belcher]

Thanks for the articles, unfortunately, they are irrelevant to my situation. This setup is not a cluster server, SCSI, or is it backing up a server system. This error is occuring on DLO Client PCs when writing to the previously mentioned fibre channel drive array.

[Deepali_Badave]

Hello,

Are you getting thsi error during the backup on the DLO client?

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Kent_Belcher]

Yes, the error occurs on the client PC. It occurs when backing up the Outlook pst file, which in our case can be rather large. The unusual thing about this is that we are using incremental, message level backup. This should "not" be occuring with that volume of data.

[Renuka_-]

Hello,
1. Does this happen to users who have realtime backups or scheduled backups?
2. Please apply the following hotfix :

http://support.veritas.com/docs/274927
3. Re-deploy the DLO agents.
4. Are these .pst located in the default profile location or elsewhere?

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[Kent_Belcher]

Yes, this happens during realtime backups. The pst files are located in the default profile and we are already running hotfix 8. We are evaluating build 5520 right now to see if this issue is resolved.

[Amruta_Purandar]

Hello,

Please update us on the status of this issue after upgrading to the latest revision.

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.