Excellent! It is one thing to *know* this stuff, and quite another to document! As you said, doing this for an existing server is tougher than building from scratch!
As far as *why* it went down, one time IIS had stopped working...one time the password to the box had changed, but none of the internal passwords had - and the other time, the whole RAID array fried - uggghhh. Lisa Lisa Cruz Systems Administrator "There's no place like 127.0.0.1" Office of Clinical Operations Great Plains Regional Medical Command 2410 Stanley Rd., Suite B-17 Ft Sam Houston, Texas 78234-6230 210-295-2705 DSN: 421-2705 Fax: 210-295-2345 DSN: 421-2345 -----Original Message----- From: Justin [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 1:54 PM To: [EMAIL PROTECTED] Subject: RE: [ cf-dev ] Disaster recovery Plan for CF 5 and SQL 2000/IIS 5.0 In that case its a education thing, right? There is no one shoe fits all when it comes to a Disaster plan. Who ever (or what job role) is going to have some degree of skills in windows / networking etc. Well the first thing on my list of "WHAT TO DO" would be figure out what went wrong. No point in restoring the server if a network card if your SQL server network card is fried. So some sort of reporting tools seem to be what you need for a start. Something that pings, probes ports etc... You don't mention if its a remote server BTW What about something like: IF there is a problem with server XZY Work your way down this list, this investigating where required. 1) Verify network connection (as outlined in whatever.doc). If not run procedure NET_001.doc. Contact ABC person. 2) Verify SQL server responding. If not run procedure SQL_001.doc 3) Verify cf server is running. Try Restarting the CF SERVICE. Contact EFG person. 4) Verify IIS is responding.If not run procedure IIS_001.doc etc. Do you know why it went down 3 times? Justin -----Original Message----- From: Cruz, Lisa L Ms GPRMC [mailto:[EMAIL PROTECTED] Sent: 12 January 2004 19:24 To: '[EMAIL PROTECTED]' Subject: RE: [ cf-dev ] Disaster recovery Plan for CF 5 and SQL 2000/IIS 5.0 Thanks Justin - this is really the kind of thing I am looking for - I have restored the server three times when it went down, and know what to do - BUT I am not sure of how to formulate it so any Joe Blow can do it if I am not here - make sense? Lisa Cruz Systems Administrator "There's no place like 127.0.0.1" Office of Clinical Operations Great Plains Regional Medical Command 2410 Stanley Rd., Suite B-17 Ft Sam Houston, Texas 78234-6230 210-295-2705 DSN: 421-2705 Fax: 210-295-2345 DSN: 421-2345 -----Original Message----- From: Justin [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 1:17 PM To: [EMAIL PROTECTED] Subject: RE: [ cf-dev ] Disaster recovery Plan for CF 5 and SQL 2000/IIS 5.0 I would suggest the following, if anyone has other suggestions I'd love to hear about them. If anyone finds it useful let me know I might even start a blog :-) Any decent sys. admin. will know all this. However lots of people do lots of jobs and don't have a dedicated system guy. This is really only a brief overview of the areas to look at, when thinking about disaster recovery for CF/IIS/WINDOWS box. For your OS --------------------------------------------- Put System backups in place (more on this later) Back up your reg. Backup your user accounts. Etc. For CF5 ---------------------------------------------- backup 1) the registry entries 2) the CF home folder 3) any system users it uses 4) CFX and any 3rd party COM For your code ---------------------------------------------- Backup you code directories. For IIS5 look here ---------------------------------------------- http://www.iisfaq.com/?View=A329 For SQL server ---------------------------------------------- To many too list. Google for backup SQL server 2000 Here is a nice starting point. http://www.zdnet.com.au/builder/architect/database/story/0,2000034918,202740 68,00.htm For your entire box. ---------------------------------------------- Create a golden image of your server. Create a Backup policy. Make sure it runs. Make sure if you run out of disk space when backing up you hear about it. If you don't know what I mean by a Golden Image For you (and anyone who will ) ----------------------------------------------- Buy this book http://www.oreilly.com/catalog/securwinserv/ .Read it. Back yourself up... Make sure someone can do everything when; you are on holidays / your have been knocked over by a bus. For your organisation --------------------------------------------- First understand your requirements. How much time can your box be down? Using an image is faster than reinstalling an OS, etc. Create a policy. Know what directories, software, user accounts etc. that change on your server. Put in systems. Test them. Write your document. Test your document. Ensure you have included all the steps. Distribute your document. Ensure its understood. If you need tools to establish what directories, reg entries etc. are used. Look at the win2000 resource kit, and/or at http://www.sysinternals.com/ntw2k/utilities.shtml. Wonderful software. A staged backup process is more flexible and possibly quicker, but may incur risks. For your sanity ---------------------------------------------- Limit the risk. Harden your box (if you don't know how, consult or learn. A decent consultant can give you a build plan for now and the future, that only needs to change when you start to do something different with your box). Use hardware, clusters, RAID etc. where you can (cost/benefit) Use a firewall, (and turn it on, don't laugh its happened.) Store your backups offsite. Wet backup tapes are not fun. This stuff is all much harder when you have to work on and existing server and software. HTH Justin -----Original Message----- From: Cruz, Lisa L Ms GPRMC [mailto:[EMAIL PROTECTED] Sent: 12 January 2004 16:11 To: '[EMAIL PROTECTED]' Subject: RE: [ cf-dev ] Disaster recovery Plan for CF 5 and SQL 2000/IIS 5.0 Thanks Paul! I'll check it out. Lisa Lisa Cruz Systems Administrator "There's no place like 127.0.0.1" Office of Clinical Operations Great Plains Regional Medical Command 2410 Stanley Rd., Suite B-17 Ft Sam Houston, Texas 78234-6230 210-295-2705 DSN: 421-2705 Fax: 210-295-2345 DSN: 421-2345 -----Original Message----- From: Paul Johnston [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: RE: [ cf-dev ] Disaster recovery Plan for CF 5 and SQL 2000/IIS 5.0 There are some resources on this on the web... Look up Business Recovery Plans on google and go from there. Tbh it's one of those "consultancy" tools to make more money imho. A good plan is simple to understand and effective in implementation. That doesn't mean it's easy to come up with or easy to do. http://www.google.co.uk/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=Bu siness+Recovery+Plans (watch the wrapping!) Paul > -----Original Message----- > From: Cruz, Lisa L Ms GPRMC [mailto:[EMAIL PROTECTED] > Sent: 12 January 2004 16:02 > To: '[EMAIL PROTECTED]' > Subject: [ cf-dev ] Disaster recovery Plan for CF 5 and SQL > 2000/IIS 5.0 > > > Hi All, > > Does anyone have a good recovery plan I could look at? I > started one, but my boss doesn't like it - and won't give me > ideas---can any of you help? > > Thanks, > > Lisa > > Lisa Cruz > Systems Administrator > "There's no place like 127.0.0.1" > Office of Clinical Operations > Great Plains Regional Medical Command > 2410 Stanley Rd., Suite B-17 > Ft Sam Houston, Texas 78234-6230 > 210-295-2705 DSN: 421-2705 > Fax: 210-295-2345 DSN: 421-2345 > > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
