Steps To Troubleshoot VMware Backup Error Timeout

Need to fix Windows errors? ASR Pro can help

  • 1. Download and install the ASR Pro software
  • 2. Open the software and click "Scan for Issues"
  • 3. Click "Repair All" to start the repair process
  • Protect your computer from harmful viruses and malware with this software download.

    If you see timeout for VMware reservation error, the following blog post will help you.

    loading × Sorry to really interrupt youUpdateloading × Sorry to interruptUpdate

    This is the second in-depth analysis of our company diary by Nathan Small (Twitter ID: vSphereStorage). If people missed the first one, it will be here.

    Problem History

    Need to fix Windows errors? ASR Pro can help

    Is your computer running slow and sluggish? Are you getting the dreaded Blue Screen of Death? Then it's time to download ASR Pro! This revolutionary software will repair all your common Windows errors, protect your files from loss or corruption, and keep your hardware functioning optimally. So what are you waiting for? Download ASR Pro now!

  • 1. Download and install the ASR Pro software
  • 2. Open the software and click "Scan for Issues"
  • 3. Click "Repair All" to start the repair process

  • General storage capacity issue with timeouts and SCSI reservation issues (timeout / conflict) in ESX 4 slots (VMware 1 View) and ESX 5.0. We need to understand why these games are perceived the way they are, and how we can improve performance right now.

    The first step in solving this type of problem is probably to create a common frame of reference for all visible sentences. Here is a problem with one of the ESX 4.1 hosts:

    ESXi 4.1:

    Mar 28 17:12:58 vmkernel: 34: 11: 37: 08.013 cpu13: 4262) NMP: nmp_PathDetermineFailure: SCSI cmd failed backup found on path vmhba1: C0: T2: L1, backup status on naa app .60060480000190100554533010043032303243232432 unknown.mar 17 12: 58 VMKERNEL: 34: 11: 37: 08.013 CPU13: 4262) SCSEWICEIO: 1688: Command to device 0x16 “Naa.60060480000190100554533032324644” D: 0x0: 0x032324644 “Failed. P: 0x0. Possible detection data: 0x0.0x0.0x0.Mar 17:12:58 vmkernel: 34: 11: 37: 08.Cpu13: 4262) WARNING: 013 NMP: nmp_DeviceRequestFastDeviceProbe: NMP device “naa.60060480000190100554533032324644” in case of doubt; requested fast express update path … 28. 17:12:58 March vmkernel: 34: 11: 37: 08.013 FS3: cpu14: 4134) WARNING: 7120: Backup error: Timeout

    When checking all the logs of the ESX 5.0 provider, the problem is observed at the same time:
    A
    ESXi 5.0:
    A
    vmware reservation error timeout

    2012-03-28T17: 12: 56.481Z cpu11: 4107) NMP: nmp_PathDetermineFailure: 2084: SCSI RESERVE command failed on route vmhba2: C0: T3: L23, redundancy status on naa device. 60060480000190100554533033364445 is simply unknown. 2012 03 -28T17: 12: 56.481Z CPU11: 4107) NRW: CMD NMP_TRTROTTLELELOGFORDEVICE: 2318: 0x16 (0x4124003D4740, 0) on dev “Naa.60060480000190100554533033364445” Go to “VMHBA2: 0: P: 0x3 0x0 0x0 0x0. Act: EVAL2012-03-28T17: 12: 56.Cpu11: 4107) WARNING: 481z NMP: nmp_DeviceRequestFastDeviceProbe: 237: NMP Instrument “naa.60060480000190100554533033364445” requested in case of doubt 2012 very fast path; -03-28T17: 12: 56.481Z cpu11: 4107) ScsiDeviceIO: 2322: 0x16, cmd (0x4124003d4740) CmdSN 0x23102 from world 0 to real developer “naa.60060480000190130053453” 410035356×4: 0x0: 0x-03 0x-03 -28T17: 12: 56.481Z cpu1: 4132) WARNING: FS3: 1835: Backup error: Timeout

    These logs show the ESX machine’s storage stack is unaware of the itemsSCSI backups of the entire device state. This occurs despite the fact that a SCSI RESERVE command was supplied that has timed out inappropriately, and an interrupt sent to advertise a SCSI will also fail due to a timeout. This usually happens for 1 of 2 reasons:
    A
    1. Fabric problems due to dropped bedding.
    2. The cubicle or controlled cubicle is overloaded
    A
    There are other messages in the logs that also indicate array performance issues:
    A

    2012-03-26T23: 00: 30.950Z cpu8: 4131) FS3Misc: 1440: VMFS3 long rsv on “VMW02” (held 1457ms). # R: 1, # W: 1 byte Xfer: 4 sectors 2012-03-27T23: 01: 15.491Z 1440: cpu4: 4133) FS3Misc: Long VMFS3-RSV time on “VMW04” (held against 2640ms). R: # 1, # W: 1 BytesXfer: 2 sectors 2012-03-28T17: 12: 59.456Z cpu15: 4131) FS3Misc: 1440: VMFS3-RSV long time from “VMW07” for (hold 2967ms). # R: 1, # 1 w: bytesXfer: 3 sectors 2012-03-28T20: 05: 19.372Z cpu0: 4131) FS3Misc: 1440: VMFS3-RSV time long on “VMW07” (holds like 19196ms). # R: 1, # W: 1 byteXfer: 2 sectors

    Simple orchestration is a performance scenario that needs to be investigated in more detail by the storage team or mix vendor, may be acceptable to allex, but let’s try to figure it out and provide more information if this is the case. partner and I decided to leave. First, let’s take a closer look at the LUNs that report the issue in some environments:
    A
    ESX 4.1:
    A
    Error message:
    A
    vmware reservation error timeout

    Tue 17:12:58 36 vmkernel: 34: 11: 37: 08.013 cpu13: 4262) NMP: nmp_PathDetermineFailure: SCSI cmd failed path reservation vmhba1: C0: T2: L1, backup situation on device naa. 60060480000190100554533032324644 unknown.

    LUN question: no data. 60060480000190100554533037394644
    A

    naa.60060480000190100554533032324644: EMC Channel Fiber Disk (naa.60060480000190100554533032324644) vmhba0: C0: T2: L1 LUN: 1 state: active fc Adapter: 1: 5: 002: 00: 00 24 WWPN: 20: 00: 00: 25: b5: 01: 0a: 24 Destination: WWNN: 50: 06: 04: 82: d5: 2d: 12: 8d WWPN: 50: 06: 04: 82: D5: 2d: 12: 8d vmhba1: C0: T2 : L1 LUN: 1 state: active fc Adapter: WWNN: 20: 00: 00: 25: b5: 01: 00: 24 WWPN: Target: 20: 00: 00: 25: b5: 01: 0b: 24 WWNN: 50 : 06: 04: 82: d5: 2d: 12: 82 WWPN: 50: 06: 04: 82: D5: 2d: 12: 82B

    From this output we can see my WWPN (world port name) in relation to the connected array ports which can be found 50: 06: 04: 82: d5: 2d: 12: 8d and 50: 06: 04: 82: d5: 2d : 12: 82.
    A
    ESX 5.0:
    A
    Error message:
    A

    2012-03-28T17: 12: 56.481Z cpu11: 4107) NMP: nmp_PathDetermineFailure: 2084: SCSI RESERVE command error on path vmhba2: C0: T3: L23, reservation state for naa device. 60060480000190100 / page unknownbut>
    Applicable LUN: naa.60060480000190100554533033364445
    A

    naa.60060480000190100554533033364445 >> EMC Fiber Channel (naa disk.60060480000190100554533033364445) vmhba2: C0: T3: L23 LUN: 23 state: active fc Adapter: WWNN: 2: 0: 0: 00: 0d: WWPN: 20:00 00: 25: b5: 01: 0a: 0d Destination: WWNN: 50: 06: 04: 82: d5: 2d: 12: 8d WWPN: 50: 06: 04: 82: d5: 2d: 12: 8d vmhba3: C0 : T3: L23 LUN: 23 state: active fc Adapter: WWNN: 20: 00: 00: 25: b5: 01: 00: 0d WWPN: 20: 00: 00: 25: b5: 01: 0b: 0d Target: WWNN : 50: 06: 04: 82: d5: 2d: 12: 82 WWPN: 50: 06: 04: 82: d5: 2d: 12: 82

    From the output of esxcfg-mpath we can tell that the new LUN with the same problem is usually connected to the same WWPN within this cluster: 50: 06: 04: 82: d5: 2d: 12: 8d and 50:06:04: 82 : d5: 2d: 12: 82
    A
    Since there are two different situations involving the same set of controllers (FA port in your case), it is very likely that your current array controller is overloaded. The next step is to completely collect all information from the array side from now on so that the NFL storage group or storage array provider can only check the state of the array at that time – there, if another event occurs, to make sure that it, that is, it will definitely follow the generated input-output.
    A
    In this particular case, the EMC storage group showed interest and confirmed that the FA transport was overloaded. To fill this gap and provide the best View behavior, the VMware View area has been relocated to a different dedicated FA in the array.

    Protect your computer from harmful viruses and malware with this software download.

    Timeout Fur Vmware Reservierungsfehler
    Vmware 예약 오류 시간 초과
    Vmware Reservationsfel Timeout
    Tiempo De Espera De Error De Reserva De Vmware
    Tajm Aut Oshibki Rezervirovaniya Vmware
    Tempo Limite De Erro De Reserva Vmware
    Delai D Expiration De L Erreur De Reservation Vmware
    Timeout Dell Errore Di Prenotazione Del Vmware
    Time Out Voor Vmware Reserveringsfout
    Przekroczono Limit Czasu Bledu Rezerwacji Vmware