Open-E Knowledgebase

Why when failing over there is a Delayed Write Failed error with Windows that will lose some portion of data as well?

Article ID: 582
Last updated: 03 Mar, 2014

Problem:

When failing over there is a Delayed Write Failed error with Windows or possibly other OS’s that will lose some portion of data as well.
 
Windows can produce an Event ID error 50.
 
Event Type:      Warning
Event Source:   Ntfs
Event Category:            None
Event ID:          50
Date:                7/20/2009
Time:                9:26:30 AM
User:                N/A
Computer:         ARTEMIS
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file . 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.
 
Solution:

This can be resolved by checking that the Write Back feature for the LUN’s is disabled and that the SCSI ID for the LUNs are the same for both the Primary and Secondary servers when using the iSCSI Auto Failover feature.

This article was:   Helpful | Not helpful Report an issue


Article ID: 582
Last updated: 03 Mar, 2014
Revision: 1
Views: 4181
Posted: 28 Jul, 2009 by --
Updated: 03 Mar, 2014 by Berger A.
print  Print email  Subscribe email  Email to friend share  Share pool  Add to pool
Prev     Next
Losing iSCSI connection during failover       Why my failback is not working although failover do??

The Knowledge base is managed by Open-E data storage software company.