- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Windows 2000 Disaster Recovery procedure
ProLiant Servers (ML,DL,SL)
1821587
Members
3414
Online
109633
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2002 04:00 PM
06-16-2002 04:00 PM
Windows 2000 Disaster Recovery procedure
I have set up a test lab to conduct a Windows 2000 Server disaster recovery exercise migrating from an ML530 to a DL380 using the same Smart Array 5304 boot controller, single processor & NC family network adapter. I am using the Msoft technet artcle Q249694 as a procedure.
When I reach point 8 of the procedure which recommends initiating an in-place upgrade after a complete system restore to refresh the setup.log and registry files the system hangs at the following point:-
1. I run winnt32.exe from my win2k cdrom and select the \winnt boot path for repair/upgrade.
2. Setup runs through ok, I specify F6 to force the loading of the cpqcissm.sys 5304 device driver which is read successfully.
3. Finally setup completes and reboots, nothing appears on the display and the hard disk is being thrashed, the system is hung!
4. On subsequent boots the sytem either hangs at this point again or blue screens with a KMODE exeption fault specifying the cpqcissm device driver, ie it looks like the system cannot boot off it.
Any ideas? Is there an official Compaq procedure for moving a Windows 2000 installation for DR or replacing a boot controller?
When I reach point 8 of the procedure which recommends initiating an in-place upgrade after a complete system restore to refresh the setup.log and registry files the system hangs at the following point:-
1. I run winnt32.exe from my win2k cdrom and select the \winnt boot path for repair/upgrade.
2. Setup runs through ok, I specify F6 to force the loading of the cpqcissm.sys 5304 device driver which is read successfully.
3. Finally setup completes and reboots, nothing appears on the display and the hard disk is being thrashed, the system is hung!
4. On subsequent boots the sytem either hangs at this point again or blue screens with a KMODE exeption fault specifying the cpqcissm device driver, ie it looks like the system cannot boot off it.
Any ideas? Is there an official Compaq procedure for moving a Windows 2000 installation for DR or replacing a boot controller?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2002 04:00 PM
08-14-2002 04:00 PM
Re: Windows 2000 Disaster Recovery procedure
Hello,
Please make sure that the firmware version of the controller is uptodate before it's moved. Also the System bios of the destination server should be uptodate. If there is any KVM involved please remove it and connect the Key Board and Mouse directly to the server. If not then try clearing NVRAM and run System Configuration utility by going into the System Partition once the Video display is available. If you need further assistance Hardware wise please contact our Technical Support Team at 1-800-652-6672.
Regards,
Please make sure that the firmware version of the controller is uptodate before it's moved. Also the System bios of the destination server should be uptodate. If there is any KVM involved please remove it and connect the Key Board and Mouse directly to the server. If not then try clearing NVRAM and run System Configuration utility by going into the System Partition once the Video display is available. If you need further assistance Hardware wise please contact our Technical Support Team at 1-800-652-6672.
Regards,
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP