RE: recover from crash
Do you mean your computer goes down and won't start back up again? In that case, a hardware failure is strangly indicated, and you need to find out what the bad part is. Tools like Compaq Insight Manager can help identify problem components before the fail completely. Jim Helfer -Original Message- From: Ron Grant [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 03, 2002 10:46 AM To: Exchange Discussions Subject: recover from crash Scenario: You come in one morning, reboot the exchange server, and it never comes back up, blue screens or whatever. It crashes. Question: What do you do FIRST to try to bring it back up? What do you do Second if that doesn't work? At what point do you go for the recovery server, and your backup tape? I was looking through the disaster recovery paper and its great...but I didn't see what to do before the backup server plan. It has tons of switches and command line tools, but im looking for elementary type notes When it crashes, try ERD first and run repair, if that doesn't work try... Stuff like that. IF the server boots, I found lots of info on error messages and the likes to try to get the IS started etc..but nothing if its basically dead. I know, this is something I should have learned long ago, but point me to the site, or papers where I can get this and I can move past this embarrassment! Thanks! Ron Oh and I found this in the archives: When your Exchange server crashed, most likely you need restore it from the tape. It is time consuming. But, If you have a clean and working dir.edb stored somewhere else, you don't need to restore it from the tape, just copy it back! So when your Exchange server is in a good condition, copy the dir.edb file to a save location such as another server, or your SAN. Is it the dir.edb that causes the crash? And does this copy tip work most of the time? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: recover from crash
-Original Message- From: Ron Grant [mailto:[EMAIL PROTECTED]] Sent: 03 January 2002 15:46 To: Exchange Discussions Subject: recover from crash Scenario: You come in one morning, reboot the exchange server, and it never comes back up, blue screens or whatever. It crashes. Question: What do you do FIRST to try to bring it back up? What do you do Second if that doesn't work? At what point do you go for the recovery server, and your backup tape? I was looking through the disaster recovery paper and its great...but I didn't see what to do before the backup server plan. It has tons of switches and command line tools, but im looking for elementary type notes When it crashes, try ERD first and run repair, if that doesn't work try... Stuff like that. IF the server boots, I found lots of info on error messages and the likes to try to get the IS started etc..but nothing if its basically dead. I know, this is something I should have learned long ago, but point me to the site, or papers where I can get this and I can move past this embarrassment! There is no magic one shot always do this answer to this I'm afraid. If it's a software error, I'd start with the microsoft technet CDs and website for example, and follow their troubleshooting guide for whatever the error is that you are getting. If you crashed after recently installing a new application, contact the vendor for that as well. If it's a hardware fault, do likewise with whatever troubleshooting stuff your hardware vendor has supplied. The time to start thinking about disaster recovery and restores and so on, imho, is when you are clear that you are not going to get a fix or when it is clear that the fix is going to take longer to appear and work than your users are willing to wait, which again is something specific to your user using the affected server and their needs. -- Robert Moir, MSMVP IT Systems Engineer, Luton Sixth Form College Rome did not create a mighty empire by having management meetings -- This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons or unauthorized employees of the intended organisations is strictly prohibited. The contents of this email do not necessarily represent the views or policies of Luton Sixth Form College, its employees or students. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: recover from crash
Ran into something simular. The user had run out of space on the C drive. When this happens you are not able to bring the system up or login at all. We ended up making a bootable NTFS disk if the main partion is NTFS or you can regular DOS disk to then access the drive and kill files after we verified that was the problem. Scenario: You come in one morning, reboot the exchange server, and it never comes back up, blue screens or whatever. It crashes. Question: What do you do FIRST to try to bring it back up? What do you do Second if that doesn't work? At what point do you go for the recovery server, and your backup tape? I was looking through the disaster recovery paper and its great...but I didn't see what to do before the backup server plan. It has tons of switches and command line tools, but im looking for elementary type notes When it crashes, try ERD first and run repair, if that doesn't work try... Stuff like that. IF the server boots, I found lots of info on error messages and the likes to try to get the IS started etc..but nothing if its basically dead. I know, this is something I should have learned long ago, but point me to the site, or papers where I can get this and I can move past this embarrassment! There is no magic one shot always do this answer to this I'm afraid. If it's a software error, I'd start with the microsoft technet CDs and website for example, and follow their troubleshooting guide for whatever the error is that you are getting. If you crashed after recently installing a new application, contact the vendor for that as well. If it's a hardware fault, do likewise with whatever troubleshooting stuff your hardware vendor has supplied. The time to start thinking about disaster recovery and restores and so on, imho, is when you are clear that you are not going to get a fix or when it is clear that the fix is going to take longer to appear and work than your users are willing to wait, which again is something specific to your user using the affected server and their needs. -- Robert Moir, MSMVP IT Systems Engineer, Luton Sixth Form College Rome did not create a mighty empire by having management meetings -- This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons or unauthorized employees of the intended organisations is strictly prohibited. The contents of this email do not necessarily represent the views or policies of Luton Sixth Form College, its employees or students. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: recover from crash
Not reboot it in the first place?!?! Since you've ruled out good administrative practice, my first step depends entirely on why it won't boot - bluescreen or whatever is a wide range of problems. First thing is that I ALWAYS shut the box down again, and try restarting it again. After that, its all gut feel. Bluescreen - check Technet for the STOP message and see where that leads. Hardware failure - reseat the component(s) and try again. -- Roger D. Seielstad - MCSE Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Ron Grant [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 03, 2002 10:46 AM To: Exchange Discussions Subject: recover from crash Scenario: You come in one morning, reboot the exchange server, and it never comes back up, blue screens or whatever. It crashes. Question: What do you do FIRST to try to bring it back up? What do you do Second if that doesn't work? At what point do you go for the recovery server, and your backup tape? I was looking through the disaster recovery paper and its great...but I didn't see what to do before the backup server plan. It has tons of switches and command line tools, but im looking for elementary type notes When it crashes, try ERD first and run repair, if that doesn't work try... Stuff like that. IF the server boots, I found lots of info on error messages and the likes to try to get the IS started etc..but nothing if its basically dead. I know, this is something I should have learned long ago, but point me to the site, or papers where I can get this and I can move past this embarrassment! Thanks! Ron Oh and I found this in the archives: When your Exchange server crashed, most likely you need restore it from the tape. It is time consuming. But, If you have a clean and working dir.edb stored somewhere else, you don't need to restore it from the tape, just copy it back! So when your Exchange server is in a good condition, copy the dir.edb file to a save location such as another server, or your SAN. Is it the dir.edb that causes the crash? And does this copy tip work most of the time? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: recover from crash
This is my wild-ass guess to a what if question. I would try to boot into safe mode. If that failed, I would pray that I was smart enough to have installed the recovery console. In either case I would systematically elimiate devices I suspect to have failed. Ed Crowley MCSE+I MVP Tech Consultant Compaq Computer There are seldom good technological solutions to behavioral problems. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ron Grant Sent: Thursday, January 03, 2002 7:46 AM To: Exchange Discussions Subject: recover from crash Scenario: You come in one morning, reboot the exchange server, and it never comes back up, blue screens or whatever. It crashes. Question: What do you do FIRST to try to bring it back up? What do you do Second if that doesn't work? At what point do you go for the recovery server, and your backup tape? I was looking through the disaster recovery paper and its great...but I didn't see what to do before the backup server plan. It has tons of switches and command line tools, but im looking for elementary type notes When it crashes, try ERD first and run repair, if that doesn't work try... Stuff like that. IF the server boots, I found lots of info on error messages and the likes to try to get the IS started etc..but nothing if its basically dead. I know, this is something I should have learned long ago, but point me to the site, or papers where I can get this and I can move past this embarrassment! Thanks! Ron Oh and I found this in the archives: When your Exchange server crashed, most likely you need restore it from the tape. It is time consuming. But, If you have a clean and working dir.edb stored somewhere else, you don't need to restore it from the tape, just copy it back! So when your Exchange server is in a good condition, copy the dir.edb file to a save location such as another server, or your SAN. Is it the dir.edb that causes the crash? And does this copy tip work most of the time? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
