General discussion

  • Creator
    Topic
  • #2080050

    Preparing for disaster

    Locked

    by ebott ·

    With less than three months until Windows 2000 hits the streets, I’m counting on your input to assemble the Mother of All Windows 2000 Upgrade Guides–just in time for the official launch party in February.
    This week’s Challenge is to build the definitive Windows 2000 Emergency Kit. Unfortunately, the Blue Screen of Death is alive and well in Windows 2000, as thousands of beta testers can testify. With my existing NT4 systems, I keep the original CD, service packs, boot disks, and an up-to-date Emergency Repair Disk nearby at all times. Is that strategy sufficient for Windows 2000, or do I need to do more? What would you put in your emergency kit besides boot disks? A copy of your r?sum?? Bill Gates’ unlisted e-mail address? Add your suggestions to the list. I’ll award valuable TechPoints–and maybe even a cool TechRepublic T-shirt–to the best contributions and post the results in two weeks. But don’t delay–this challenge closes at the end of the day on Friday, December 3.

All Comments

  • Author
    Replies
    • #3901952

      Preparing for disaster

      by rstencel ·

      In reply to Preparing for disaster

      One thing I would do is use Norton?s Ghost to make a Base Image of Each Different type of system you are going to install it on. It reduces down time if you have to start over and setup times of similar machines (when they update ghost walker to support 2000). ERD is a definite as long as you keep it up to date. Service Packs, hotfixes, boot disk and original software are a given. A Disaster recover guide for your particular environment should also be kept, incase you are not around and so you don?t miss any steps. If properly written and tested it saves you allot of time when a real emergency hits. It also helps with testing new software as you can use it to setup test environment that more closely duplicates your original environment. Of course this would have to be updated and retested for Win 2000 but the old one could help you if you need to revert back. The last thing I would recommend would be copies of all the 3rd party drivers for any hardware that requires them (latest versions, not orig

      • #3792888

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901927

      Preparing for disaster

      by mktz ·

      In reply to Preparing for disaster

      1)All necessary “Latest” drivers for hardware.
      2)Win2000 server emergency repair disk.
      3)Boot disk to boot to FAT partition.(If installed on one).
      4)Latest info from technet on CD
      5)A copy of windows 2000 handy.
      6)A complete backup of your system files,registry.
      7)Win 2000 ntfs boot disk to boot to edit boot.ini if necessary.

      • #3792889

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901926

      Preparing for disaster

      by gary ·

      In reply to Preparing for disaster

      All of the above would be essential for individual machines. You should plan this very carefully and for a time when you are able to recover if need be. So start on friday evening, take a crate of red bull, advise your spouse that you may only see them in a few days (this is a very real problem:-)). As a contingency you may want to book a one way flight for sunday evening?
      Seriously, it depends on the machines and their purpose. Critical servers should be backed up completely, ghost or similaris quicker to use. Ensure you know each component of your machine, get the latest drivers (emulation) for all. A nice resource is http://www.betaos.com, they have some useful stuff. ERD’s, installation media, boot disks, are essential, fat partition might be helpful but is this realistic, what self respecting domain admin would implement this anyway? Been using win2k for over two years now, beta 3 was temperamental but rc2 is very nice. Existing CDR and remote admin software is mostly not compatible with win2k. I think MS

      • #3792890

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901925

      Preparing for disaster

      by txitguy ·

      In reply to Preparing for disaster

      I haven’t ever used Windows 2000, but if it’s ANYTHING like Windows 98, expect it to crash and burn every 3 to 6 months. In addition to the above, I keep a tape backup of all my non-replaceable files. For Example, internet downloads, Pictures, Address Books, Email, Newsgroups, Buddy Lists, My Documents Folder. I’m on my second reinstallation now, and (judging by experience) will be reinstalling again in the next month.
      I don’t back up the entire system for two reasons:
      1. The size (I havea small tape drive).
      2. (and more important) I don’t want to copy the system errors that caused the crash to begin with, that way I have more time before I have to do it again.
      Ben Nelson

      • #3792225

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901922

      Preparing for disaster

      by top.phrog ·

      In reply to Preparing for disaster

      A copy of Corel WordPerfect Office 2000

      • #3792891

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901917

      Preparing for disaster

      by andrew basak ·

      In reply to Preparing for disaster

      A sledgehammer and various other power tools

      • #3792892

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901913

      Preparing for disaster

      by jeff_gebhart ·

      In reply to Preparing for disaster

      I agree with the sledgehammer suggestion!

      One that I would definitely add is a copy of ERD Commander Disksfrom http://www.winternals.com. This one will let you boot from 3 floppies and be able to manipulate your NTFS partitions in the event of a crash! Almost an essential tool!

      • #3792893

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901909

      Preparing for disaster

      by edwilke ·

      In reply to Preparing for disaster

      If at all possible use a standalone machine
      that has a zip drive included and keep all
      known good configurations until a blue screen
      of death is met.

      • #3792894

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901907

      Preparing for disaster

      by gicu artistu’ ·

      In reply to Preparing for disaster

      My experience with 2000 is relatively new. But what I can tell for sure is that no information technology is failure safe or “disaster aware “ or whatever your term for reliability is. And I’m very sure about this.
      So my way of doing things in this domain is simple.
      1. System data and user data has to be on different storage (at least different partitions)
      2. Keep the version of the system that you had installed (install CD) and on another CD the patches that you applied till the point that the machine worked good for the purpose it was designed for. DO NOT apply patches if the machine works. You might as well wreck it because of that.
      3. Make daily backup of the user data. There are tape systems that could backup asmuch as you need.
      4. Update your emergency disks tapes and whatever… There are useless anyway because when a disaster comes (nature says that) you have to start over again. There are made only to relief part of your stress.
      5. Keep a copy ofthe BIBLE handy with

      • #3792895

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901906

      Preparing for disaster

      by gicu artistu’ ·

      In reply to Preparing for disaster

      My experience with 2000 is relatively new. But what I can tell for sure is that no information technology is failure safe or “disaster aware “ or whatever your term for reliability is. And I’m very sure about this.
      So my way of doing things in this domain is simple.
      1. System data and user data has to be on different storage (at least different partitions)
      2. Keep the version of the system that you had installed (install CD) and on another CD the patches that you applied till the point that the machine worked good for the purpose it was designed for. DO NOT apply patches if the machine works. You might as well wreck it because of that.
      3. Make daily backup of the user data. There are tape systems that could backup asmuch as you need.
      4. Update your emergency disks tapes and whatever… There are useless anyway because when a disaster comes (nature says that) you have to start over again. There are made only to relief part of your stress.
      5. Keep a copy ofthe BIBLE handy with

      • #3792896

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901900

      Preparing for disaster

      by jeremy ·

      In reply to Preparing for disaster

      1- Prepare a document that details all network settings such as IP addresses etc.
      2 – A folder which contains all the relevant drivers etc stored on a different machine.
      3 – Updated ERD and Full system backup including registry to a tape drive
      4 – Copy of Partion Magic and Boot Magic.
      5 – Boot disk (ntldr, ntdetect.com, boot.ini)
      6 – Enable Boot logging (press F8 and select during operating system selection phase) and export the ntbtlog.txt to a different machine.
      7 – Last but not least DO A TRAIL RECOVERY AND DOCUMENT PROBLEMS AND SOLUTIONS!!!

      • #3792897

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901890

      Preparing for disaster

      by michael.simmons ·

      In reply to Preparing for disaster

      I would use a product like UltraBac to make an image backup of the system disk and backup other partitions using NTBackup. On every machine I upgraded to Win2K, I’d load the recovery command console by running \i386\winnt32 /cmdcons from the setup CD.

      • #3792898

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901885

      Preparing for disaster

      by djharker ·

      In reply to Preparing for disaster

      The idea of a server pack is just SO important. It’s the kind of information that can ONLY be done when a server is built and it should be on everyone’s server build procedure.

      I keep a copy of the operating system CD, plus the service pack, plusa cd with any other patches. I keep the EULA and/or CLA documents, plus a full backup taken as soon as the build is complete. With regard to the Emergency Repair Diskette – I ignore the create ERD prompt within Server setup, and manually run RDISK once I am satisfied all the patches etc are installed. We always buy COMPAQ servers, and so I have a diskette with the INSPECT report on it, alomg with the System Config Backup SCI files. The same kind of information could be put together using msinfoor sysinfo. The important thing is this gives the bios revisions etc for the components.

      Having dealt with the hardware, I list the users and groups, with security information – what permissions etc.

      The whole idea of a server pack is that it helps you recreate th

      • #3792899

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901883

      Preparing for disaster

      by dennis@l ·

      In reply to Preparing for disaster

      How long does it take to change out a hard drive? Throw in a hard drive, with an identical OS configuration already on it.

      • #3792900

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901861

      Preparing for disaster

      by cyancey ·

      In reply to Preparing for disaster

      Disaster Recovery:
      1. You should have made a log during installation of the order in which software was installed, configuration settings that you entered, Service Pack levels of all software, version number etc.
      2. Contained within that log should have been contact information for each vendor (name and phone number).
      3. Make the Boot Disk…..doesn’t matter that you think that you will never need them, you will. While you’re at, get a copy of a Win98 R2 Boot disk…it will help when all else fails.
      4. Get a copy NTFS DOS. A helpful utility for getting around the NTFS security.
      5. Make sure that your rdisk is updated, and use the /s option to backup the SAM.
      6. If space is available, GHOST the drive. Norton is only one of many utilities with the ability to copy HDD’s. I specified GHOST here, because of its ability to work cleanly with NTFS partitions.
      7. Have a contact list of who does what in case of an emergency….a.k.a. The ContingencyPlan.
      8. Update dri

      • #3792901

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901849

      Preparing for disaster

      by top.phrog ·

      In reply to Preparing for disaster

      Sorry about my previous answer. Must be getting hard of seeing in my old age. I thought you were talking about MS-Office2000. Since you are talking about windows 2000, my toolkit would include Linux and Corels’ Word Perfect Suite for same.

      • #3792902

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901841

      Preparing for disaster

      by lhubert ·

      In reply to Preparing for disaster

      1)throw it into a test environment and get all your current apps, printers, devices, etc working.
      2)get backup software that is specifically Win2K-compatable. Do a backup, then format all disks.
      3)start the restore process from scratch – this time document everything – including what you used (CDs, device driver disks, etc) and how you did it.
      4)repeat 3) until it actually works!
      5)now take your documented procedure, combine with all software and throw it in a safe!

      • #3792903

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901839

      Preparing for disaster

      by rkward ·

      In reply to Preparing for disaster

      I would also keep any necessary third party drivers in the kit, and a written detailed procedure documentation. I would also test the process of a full restore if at all possible. This test would tell you exactly what you need, and any other gotcha’s that may come up. In testing restore procedures in the past, I have had to manipulate the hives of the registry. Microsoft gave me instructions and suggestions, but they wouldn’t support it if there were problems. This is why the process should be thoroughly, before a failure happens.

      Regards
      Rich Ward

      • #3792904

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3901826

      Preparing for disaster

      by aramos ·

      In reply to Preparing for disaster

      Most of the suggestions here will satisfy even the most paranoid Administrator (the sledgehammer is a little extreme, I would recommend a copy of Red Hat Secure Server ;-). One addition that I would make is to have a backup server that can take overif the first one fails. I’m surprised no one suggested this. Ghost is a wonderful tool that everyone should look into. If you’re not looking at Ghost, a good tape backup methodology should be in place.

      • #3792226

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903547

      Preparing for disaster

      by eric.farrell ·

      In reply to Preparing for disaster

      Buy a second drive and configure it as a mirror for your NT4 server. Mirror the NT4 System Partition to the new drive. Remove the new drive from the server and turn off the mirroring. Then upgrade to Windows 2000. Worst case scenario, you can beback up and running in minutes by simply swapping the new mirrored drive back into the server and reformating the Windows 2000 drive.

      • #3792905

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903538

      Preparing for disaster

      by jlanka ·

      In reply to Preparing for disaster

      An Online UPS and an Electrical Generator. You wont be able to boot from that floppy if there is no power.

      • #3792906

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903535

      Preparing for disaster

      by jesselou ·

      In reply to Preparing for disaster

      windows 2000 emergency kit will include;
      =setup disks for windows 2000
      =bootable diskette without config.sys & autoexec.bat
      =startup disks windows 2000, win98/95 winnt(erd)
      =antivirus emergency dos diskettes
      =details of local isp
      =windows 2000cd; include win98/95 if you decided later to dual boot.
      since windows 2000 supports fat, fat32 and ntfs i would implement dual booting with windows 98 because in this environment i will
      install the diagnostics programs whereas in win 2000 i will install the big applications
      program. besides, if you will encounter the blue screen syndrome you can go to win 98 platform and there you can modify, restore the files that went wrong not in the dos prompt.

      • #3792907

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903531

      Preparing for disaster

      by wfox ·

      In reply to Preparing for disaster

      I wouldn’t upgrade to Windows 2000 for at least three months after it hits the streets. That should give Mother Gates enough time to squash all the really bad bugs before they infect your network.

      • #3792908

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903474

      Preparing for disaster

      by likertj ·

      In reply to Preparing for disaster

      Before I upgrade to Win2000, I would make a full backup of my NT 4 Server. I would hold onto my latest SP and CD. I would also keep all of the latest proprietary drivers for my SCSI cards and other peripherals on one CD to save space. I would also keep the prior list on all servers I am not going to upgrade immediately, especially my DC’s. For my Win2000 server I would keep an updated ERD and backup, including a CD of specific drivers I’d have to install.

      • #3792909

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903368

      Preparing for disaster

      by dan ·

      In reply to Preparing for disaster

      Assuming that Win2000 is not too diferent from W98, the most basic
      precaution would be to back up the registery EVERY time anything in the way of an app or utility is added to/subtracted from your system.

      dante@hereami.co.uk

      • #3792910

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903363

      Preparing for disaster

      by amjad ·

      In reply to Preparing for disaster

      Assuming Windows 200o not to be different from other WIndows versions,it will be a good idea to keep a backup of the registry eveytime an application is added or removed.
      Update the emergency repair disk whenever some hardware is changed & any addition or deletion to the applications is made.Take backups frequently.

      Rest the strategy you follow is enough.

      • #3792911

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903348

      Preparing for disaster

      by dstorbakken ·

      In reply to Preparing for disaster

      Ghosted image of the working installation, latest backup, ERD, APD Boot disk with cdrom and possible scsi drivers. Zip or Jazz drivers, Video drivers, Bios, NIC drivers, Novell Client32, DOS 6.22, Blank formated disks. Sound card and Modem drivers. List of hardware configuration with S/N’s and manufacturer web url’s and phone numbers.

      • #3792912

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903228

      Preparing for disaster

      by tk421 ·

      In reply to Preparing for disaster

      Like any OS, you should never implement it into the workplace until you are reasonably comfortable (I am talking aout the MIS people). You can support an OS your aren’t familiar with. With that said, moving to 2000 will vary from workplace to workplace. There doesn’t seem to be any real reason that ALL computers have to have W2000 right away. In an NT environment, W2000 machines can be added in on a need-be basis. Normally I don’t recommend upgrading from one OS to another; I’d rather perform aclean install. As long as a company is going to start off with a new and improved(?) OS, they might as well implement good computing habits and save any and all important data on the server. That way, a tech can safely wipe all the client’s harddrives clean and install W2000 the right way. I don’t see any reason W2000 will be fundamentally different from any other OS. You need the OS software, drivers, maybe some reference guides, but most importantly a gameplan and a level head.

      • #3792913

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3900296

      Preparing for disaster

      by joemcse ·

      In reply to Preparing for disaster

      I would also add all the updated ROM Packs for the server, updated device drivers, and Virus scanning software.

      • #3792914

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3900291

      Preparing for disaster

      by mooker ·

      In reply to Preparing for disaster

      For those of you who are too young to have gone through the various MS upgrades in the past, let me pass on this one tidbit of hard learned experience: “NEVER upgrade a Microsoft product”.

      Install it new – one time for each class of PC’s in your organization (If you have more than a half dozen different kinds, tell your Manager it’s best to stay with NT for a while). Load the rest with “Ghosted” images.

      Apply the 7500 or so patches that will be released in the next year to fresh Ghost loads until you find the right mix of SP’s for your organization. Repair explosions as necessary with properly patched Ghost images. Happy Motoring…..

      • #3792227

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3900163

      Preparing for disaster

      by myerssd ·

      In reply to Preparing for disaster

      Let me start by saying that my exposure to Windows2K at this point is somewhat limited, but most of the information in numerous responses presented here should be standard practices for any NT infrastructure.
      Documentation, Documentation, Documentation.
      As well as a reliable backup system affording disaster recovery specific to the NT operating system.
      The recovery console is also another feature that I wouldn’t overlook, but I would not rely on it as my only source of recovery.

      Also I don’t want to minimize the importance of one other concept…it is imperative that the operating system reside on a different logical volume than that of the data or in some cases even the applications (my preference is that they be on different physical devices as well).

      Again, many excellent suggestions have been made, just use good common sense and select the suggestions that seem to fit your environment and all should be well. 🙂

      • #3792915

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3900154

      Preparing for disaster

      by defaultuser ·

      In reply to Preparing for disaster

      We all agree on most of the same things:

      1. Backups
      2. ERD
      3. Drivers
      4. Maybe a spare hard drive with the OS on it already.
      5. NT Boot disks
      6. A partition manager
      7. Always a copy of DOS 6.22(and CD-ROM drivers to go with it)
      8. TechNet binder
      9. Laptop with Internet access from anywhere(just in case)

      But, I didn’t see anyone mention hardware issues? Don’t know what hardware you’re working with, but I always have the following in addition to the NT stuff:
      1. Compaq SSD for Compaq servers
      2. Dell PowerEdge Support CDs
      3. Gateway Support CDs
      4. HP NetServer Navigator Support disks for their servers

      A lot of times you’ll be kicking yourself for not bringing them if you need them. And good luck getting everything off the Internet if you need hardware drivers. You’ll spend half a day trying to get them.

      With all of those CDs and disks, there won’t be a problem you can’t fix.

      Good luck.

      • #3792916

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903196

      Preparing for disaster

      by ames ·

      In reply to Preparing for disaster

      Your best bet is to do a total system backup every night. With NT4 we were able to restore one of our servers from a backup. Put the tapes away in a safe place and when you do the upgrade to win2000 and everything fails you can rely on your backups to go back to nt4. If every thing goes well you can start backing up win 2000. Documentation of your dhcp server is a must and check win2000 hardware compatability list first before making the upgrade.

      • #3792917

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903182

      Preparing for disaster

      by rgravelle ·

      In reply to Preparing for disaster

      If you have a CD-RW, copy the whole system
      to a cd. Cds are cheap and you can upgrade
      to new ones every few days.
      One program you can use is WINDOWS COMMANDER
      to tranfer your system.You then can use a
      floppy to transfer the system files.

      • #3792918

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903111

      Preparing for disaster

      by i.reddish ·

      In reply to Preparing for disaster

      when i installed win2000 beta i installed it with nothing inside my system got it up and running then put my sound card in installed the drivers so on so on till it was running as a full system and it ran perfectly for months till i found out so software will not work without updates. when people download the update i don`t think there will be any problems at all

      • #3792919

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903108

      Preparing for disaster

      by symmetrynet ·

      In reply to Preparing for disaster

      best win2k preperation kit?

      easy!

      one simple thing:

      an instruction page for how to reformat the hard-drive and run FDisk

      also listing the FTP server for downloading Debian Linux

      😉

      • #3792920

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903081

      Preparing for disaster

      by abrennan ·

      In reply to Preparing for disaster

      Hi ebott.

      In the emergency kit I would keep a list of links to sites such as Tech Republic.

      Most organisations cannot, or do not, afford much in the way of training in this rapidly changing industry.

      I find that access to cyber places likethis help in a big way to supplement my knowledge and abilities.

      • #3792921

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903063

      Preparing for disaster

      by lvngfree ·

      In reply to Preparing for disaster

      I keep the boot disks, Win NT CD, all service packs, and an up-to-date Emergency Repair Disk close at all times. I also have backup tapes of my system to save time in reloading everything incase my system crashes. I also have a standby harddrive that has NT loaded with all my programs so if I don’t have the time to reload everything and need to do something asap all I have to do is put the other hard drive into tne Computer and I am up and running again. Sounds like alot of stuff but the futureis always unknown. For me, doing this is beneficial since I seem to crash my system at least once a year. I just try to insure I keep my backup records as up to date as possible.

      • #3792922

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903027

      Preparing for disaster

      by seamus ·

      In reply to Preparing for disaster

      This is an option for some one that cannot afford for their server to be down, has money and is on a tight schedule. Rent a server and set it up as a duplicate of the Server want to replace with Windows 2000. Perform the test on the second machine.
      Before you start however I would make a reservation in a nice hotel with rubber walls, because I’m sure the project will have you bouncing the walls.

      • #3792923

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3903025

      Preparing for disaster

      by mike.h ·

      In reply to Preparing for disaster

      If you have spare disk space then copy all the cd files onto a spare partition – 1Gb should be enough. Create a directory structure with all your drivers in and dated folders for backups. I’ve installed W2k a few times without problems (scary eh!) and the machines I use can dual boot to DOS for network access if I missed something out (like network drivers). With a non NT bootable partition you will also be able to start again easily. You can even dual boot to win98 and use a fat32 partition for all your source files.
      Also have you tried scripting the installation? This speeds things up and ensures that you can repeat the install again and again.

      • #3792924

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3902880

      Preparing for disaster

      by mesterhazy ·

      In reply to Preparing for disaster

      You might consider a Disaster Recovery Document for your site, along with a good virus scanner. In your DR Doc you will want a contact list & wk phone #’s, Hm phone #’s, pager #’s, password list for Administrator priv’s. a hard copy of all disk partations and FS types, locations where back tapes/cd’s are located and how to access them (instructions on how to restore). a set of current backup tapes. a cleaning tape, a list of all applications running on your system, a list of back up systems . and Doc’s on how to fail over to them. A DR Assesistment guide -it’s a check list to predict the total recovery time. Depending on your business needs – some sites can stay down for a couple of days, while others are business critical.So the first question most upper managers will ask is how long??. At least with the check list you have a good time frame for them.

      Since this is important information, you will want to keep it in a secure place,
      so lock it up , have the key in a box with a combo lock on it. If any

      • #3792925

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897153

      Preparing for disaster

      by *artemis* ·

      In reply to Preparing for disaster

      I know the answere’s too late…but you can’t beat having a ghosted copy of the hard disks burned in segments on cdroms 🙂

      • #3792926

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897143

      Preparing for disaster

      by istal ·

      In reply to Preparing for disaster

      Be tuff, be you.

      Nothing else counts!!!

      • #3792927

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897050

      Preparing for disaster

      by leo.valmores ·

      In reply to Preparing for disaster

      The additional “kits” or strategies I would add are:
      1. Thorough review of your existing servers whether or not all meets the bare minimum requirements of WIN2K.
      2. List of your users logon ID’s/PWs, their respective shares, access permission lists and printers access, IP addresses, etc.
      3. List of your existing and additional shared printers and their respective driver CD’s/disks for WIN2K
      4. WIN2K upgrade CDs/disks for your existing backup system.
      5. Lot of guts! And prepare and rehearsehow you will tell your CEO in case of a roll-back!!

      • #3792928

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3896912

      Preparing for disaster

      by vemilewski ·

      In reply to Preparing for disaster

      Don’t forget original CD’s for third-party software (ArcServe, database clients, applications, etc.), and the names and phone numbers of people who can test the applications themselves to make sure they are fully functional.

      Also, make sure the drivers you keep (for possible backout) are ones that you know work, which may or may not be the latest…

      • #3792228

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897521

      Preparing for disaster

      by ahbws ·

      In reply to Preparing for disaster

      Do the backup and try to keep all the drivers for you hardware.

      • #3792929

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897389

      Preparing for disaster

      by mrmikey59 ·

      In reply to Preparing for disaster

      When preparing for disaster, I keep the originals offsite in a flame proof box. I make copies of the originals for active use… Don’t forget to label them with CD-Keys and other required input data. I also have a recovery binder with the readme notes and installation guides for all application and operating system software. My recovery binder also contains lessons learned for each installation of software I encounter. (Creates shortcuts for data entry)

      • #3792930

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897284

      Preparing for disaster

      by wefearonlygod ·

      In reply to Preparing for disaster

      Nothing happens during the Y2k and Windows 2000 had Beta distributed earlier in Sept or Nov I might be wrong…Had my winnt4 upgraded and win98 upgraded and office97 to office 2000 nothing happen…Be cool computer are human made and mistakes are common problem…Enjoy the upgrading…Cheers..Why spent so much and worry too much…Be happy and everything will be fine..

      • #3792931

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897271

      Preparing for disaster

      by cnickerson ·

      In reply to Preparing for disaster

      1) use ghost to make a master image that is CLEAN
      2) a copy of WIN2k
      3)A cd with ALL of the latest drivers you need for any component in the boxes.
      4)a copy of the first option pac for 2k when it comes out.
      5) a booklet with all of your Active directory permissions/accounts/trees/forrests.
      6) lucky rabbit’s foot
      7) anything you need to boot up… including a fresh boot disk

      • #3792229

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897683

      Preparing for disaster

      by straz ·

      In reply to Preparing for disaster

      Frist back-up all your files and keep them up to date. Besides the original cd, boot disks and a good emergency repair disk. Add to this a trouble shooter program and a good set of pubications on 2000.

      • #3792932

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3897642

      Preparing for disaster

      by hasse mcse/brainbench ·

      In reply to Preparing for disaster

      Hi!

      When it comes to upgrading existing NT Servers, I would first make a backup of the whole system at it is right now.

      I would prefer to make an Image of the present systems boot drive.

      I would keep bootdisks,sps and a NT4 cd handy, I would also get bootdisks, Win2k server cds and win2k diagnostics cd.

      Then I would just put the win2k cd in and hit update.

      If all goes well a few hours later I’m running Win2k.

      /Hasse

      • #3792933

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3900672

      Preparing for disaster

      by asecret ·

      In reply to Preparing for disaster

      Have the obvious things handy such as original installation Media (eg. boot disks & CD’s), Manuals, and serial numbers. I ghost image of the drive may be extremely useful in the event of the unforgiving blue screen of death, as will a copy of all the required drivers for your system.
      One of the most important things you can do however is document everything. In the event that you find yourself faced with a lifeless server, desperately in need of a fresh start to life, no matter how good you may be, if you have the step by step instructions in front of you from your last install (including notes of any updates done since) the job will progress faster. Think like a Boy Scout and be prepared.

      • #3792934

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3900426

      Preparing for disaster

      by ciberdann ·

      In reply to Preparing for disaster

      I have been using Windows 2000 for the past 6 months and seen the blue screen of death, and had to reload my hole system. But now I found this new program that I have been using for the past 4 months and I have recovered from two major crashes. The software is call Fix-It 2000, It’s made for Windows 2000 and they play good togeither. It has alot of fetures on it like Life line, It works before your into windows and can keep you from losing data on a crash it updates easy. and it’s antivirus picked up two viruses that Nortons and McAfee did not even see. If you want more info let me know

      • #3792935

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3898582

      Preparing for disaster

      by defaultuser ·

      In reply to Preparing for disaster

      DISASTER RECOVERY…SOLVED

      Most of the earlier suggestions are very good, but I didn’t see this one…

      Hopefully, the drives on your server are setup so that you are mirroring your primary boot drive. If this is the case, I would suggest breaking the mirror first, pulling out the 2nd drive, putting it on a shelf, then upgrading to 2000. If you have any problems at all, you can simply put the other drive back in and you just saved yourself a few hours of tension while the boss looks overyour shoulder to fix the problem. It is what we’ve implemented here and have had to go to it a couple times. For the cost of 1 hard drive, it’s your best choice. In fact, if there are problems and you are able to get it all back in 20 minutes, then you’ll look like a genius.

      Do it for all of your servers on a monthly or quarterly basis…you’ll sleep better.

      • #3792936

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3898580

      Preparing for disaster

      by defaultuser ·

      In reply to Preparing for disaster

      Oops, a couple people already mentioned the same solution…they’re right though…mirrored hard drive is still your best choice.

      • #3792937

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3898481

      Preparing for disaster

      by donald.young ·

      In reply to Preparing for disaster

      One more thing that is always a good idea, just in case…

      If you are planning on using NTFS, I like to do an Emergency load of NT in a folder named WINNT.EMR. Then you make an additional entry in the Boot.ini file named Emergency load. This will allow you to get to the NTFS partition to replace a corrupt driver if the ERD disk doesn’t help.

      Donyoun, MCSE

      • #3792938

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3898352

      Preparing for disaster

      by techrepublic ·

      In reply to Preparing for disaster

      Although this is late, I would add one additional suggestion. A cloned drive, mirrored drive, backup, Ghost, original disks and docs are all perfect plans, it is important to make sure you (the current MIS person) is not the ONLY one that knows where everything (backups, drives, docs, etc.) is located. All of the preparation is of no value to a company if it cannot be found or used properly. If a predecessor to you leaves the company (or customer) for ANY reason and you are brought in to support the network, you would hope to have what you need to do the job. Keep documentation on the work you do, and see that a partner or an owner understands where it is and what it is, and the importance of what you are doing.
      From experience I have followed other MIS people that left nothing but a mess. It is my hope I have never done that to another of my peers.

      • #3792939

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3898344

      Preparing for disaster

      by ashapoo_jain ·

      In reply to Preparing for disaster

      Keep picture of Bill Gates in front of you and also a phone to call ur lawyer to sue Bill Gates if the damn thing crashes down

      • #3792940

        Preparing for disaster

        by ebott ·

        In reply to Preparing for disaster

        The question was auto-closed by TechRepublic

    • #3792887

      Preparing for disaster

      by ebott ·

      In reply to Preparing for disaster

      This question was auto closed due to inactivity

Viewing 58 reply threads