Domain Controller server stops responding during backup of all drives (disk partitions) with Backup Exec System Recovery (BESR) or Backup Exec for Windows Servers (BEWS)

Article:TECH59663  |  Created: 2009-01-16  |  Updated: 2009-01-16  |  Article URL http://www.symantec.com/docs/TECH59663
Article Type
Technical Solution

Product(s)

Environment

Problem



Domain Controller server stops responding during backup of all drives (disk partitions) with Backup Exec System Recovery (BESR) or Backup Exec for Windows Servers (BEWS)

Solution



When running a backup of all drives on a Domain Controller server, the server stops responding and the following situations are noted:
  • Users cannot log into the Domain
  • Users cannot access shares on the server
  • Backup Exec Services cannot be stopped
  • Changing the Performance slider bar position has no impact
  • Messages in the event log indicate a timeout condition being reported by the RAID controller on the server

The issue can be resolved by modifying the IRPStackSize parameter in the registry per the following steps:

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

1. Launch Regedit or Regedt32
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE | SYSTEM | CurrentControlSet | Services | LanmanServer | Parameters
3. If the IRPStackSize does not already exist, click on Edit, point to New, and then select DWORD Value.
4. Type IRPStackSize and press ENTER. Note: IRPStackSize is case sensitive
5. Click Edit, and then Modify
6. Set the Value Data to 30 then click OK.

Note: The default value of the IRPStackSize parameter is 15. The range is from 11 (0xb hexadecimal) through 50 (0x32 hexadecimal).

If the problem persists after completing this procedure, test increasing the value of IRPStackSize in increments of 5 or more.  It is not recommended to exceed 50.

7. Quit Regedit or Regedt32 and then restart the server.

For additional information about the <IRP> Stacksize, please review the following Microsoft Knowledgebase Article:
Description of the IRPStackSize parameter in Windows 2000, in Windows XP, and in Windows Server 2003
http://support.microsoft.com/default.aspx?kbid=285089



Legacy ID



302935


Article URL http://www.symantec.com/docs/TECH59663


Terms of use for this information are found in Legal Notices