We have a 4.5 year old Dell PowerEdge 2500. Six hard drives in a RAID5. Small Business Server 2000. Backup Exec 8.5. We've been hoping to replace this server within the next month, upgrading everything.
Two hard drives failed, we lost all data. I replaced the hard drives, got the RAID functioning, with Dell's help. I installed SBS2K, from the discs. I updated and patched it. [This was time-consuming; neither Windows Update nor Microsoft's MSBE (or whatever their answer to HFNETCHK is) worked at first. I had to manually updated BITS and some other files, bring it up to Windows 2000 SP 4, then I could install SBS2K SP1, then apply the 30-ish security patches.]
Then I installed Backup Exec 8.5. I looked for patches for it on Veritas' website - they didn't seem to have anything crucial for it.
Then I followed Veritas' instructions on disaster recovery (their Intelligent Disaster Recover had not been an install option). I set the Exchange databases so that they could be overwritten by a restore. Their instructions on restoring the System State were to reboot in Directory Services Recovery Mode (similar to safe mode), and restore the system state (I also included Information Store and a chunk of our file system data in this restore). Then it was supposed to prompt me for a reboot.
I restored. I rebooted when prompted. It stopped at the Windows screen with this:
If you're seeing this message for the first time, reboot. If it comes up again:
Check for viruses. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for Hard Drive corruption, and then restart.
I rebooted, same Stop happened. I booted to the disk for Symantec AntiVirus Corporate Edition (a few years old). I ran a scan, it found no infected files on the C:.
I called Dell back. We quickly determined that it's not a RAID issue. We tried to boot to the Last Known Good hardware configuration: no dice. He suggested I try to repair the OS with the installation disk. I did the repair where it replaced all the files on the C: with those on the disk. Rebooted to the same Stop message. He suggested I could do a parallel OS install. I'm not sure what that would accomplish.
I called Veritas. Unsurprisingly, they refused to help me because my version of Backup Exec is too old.
Here are the options I'm seeing, please let me know what you think:
1) Reinstall SBS from scratch again, patch it up again (taking 4-5 hours?). Reinstall BackupExec 8.5 again. Verify that I can at least recover my data and my exchange databases from tape. This time, instead of restoring the System State, manually add each user (there's maybe 25 or 30). Then, call Microsoft and pay an incident for them to walk me through connecting each user to his/her right mailbox. Is this even possible? What is involved?
2) Reinstall SBS. Purchase current version of Backup Exec, hope that it will be able to restore files and system state from our tape that was made with 8.5. Would the current version of Backup Exec even work on SBS 2000?
Is there any way SBS2000's native backup program would be able to restore with the tape that was made from BE?
At this point, we've been offline for two days, and management, although kind and understanding, wants to be back online ASAP.
Does anyone know of a service that will accept and hold incoming mail for our domain, then forward it to us when we're back online?
Any recommendations would be hugely appreciated. We're a nonprofit human rights organization in NYC with a very tight budget, but if we could pay someone more capable than me to have this fixed quickly, we would.
> We have a 4.5 year old Dell PowerEdge 2500. Six hard drives in a RAID5. > Small Business Server 2000. Backup Exec 8.5. We've been hoping to > replace > this server within the next month, upgrading everything.
Call Microsoft immediately (open 24/7) and they'll work with you until the problem is resolved for a flat fee. If you are on a tight budget, this will be your best bet. Reconnecting mailboxes is a piece of cake, but everything else is a little more involved. :-)
Inaccessible boot device sounds like incorrect drivers or some other issue with that RAID controller. Have you checked firmware on that RAID controller? Given that two drives have failed, I am not sure that I would trust that card again, at least until its batteries were replaced, firmware was updated, and it was burned it for 24 hours. You do know that you have to replace its batteries on the battery-backed cache every 3-4 years, right?
Do you basically just want to recover data? There are services that will hold your mail until your Exchange is back. I don't remember the name off top of my head, but search for "mail holding" in Exchange newsgroups.
Download a trial of BackupExec 10 from Veritas and restore with that. Veritas will certainly support Version 10? :-) You want to do an offline restore (the EDB and STM files).
New configuration - just say "No" to RAID5:
RAID 1 - System Partition/Transaction Logs RAID 1 - Exchange data RAID 1 - Data files
I would build a BartPE disk with Dell RAID drivers on it and access your data that way. It does sound like the data got restored correctly, but something is amiss in the RAID config, which prevented the system from coming back online. I would take this time to optimize your disk subsystem layout.
Hands down, I think working with Microsoft would be your best option. :-)
There is a reason why I sell HP servers. -- Leonid S. Knyshov, CEO Crashproof Solutions, LLC - http://www.crashproofsolutions.com MCP Exchange 2003/Small Business Server 2003, CCNA, SCSA 8, NCIE Microsoft Small Business Specialist Partner
I had rebooted many times before this happened, which is why I've been associating the crash with something that happened as a result of restoring the System State. But maybe I'm discounting the hints that it's hardware/firmware related. I did not know that I had to replace the RAID controller's batteries.
What is a a BartPE disk?
Again, thank you, this seems logical and sets my mind a bit at ease.
I'm getting a few hours sleep, and will resume this in the morning, and will reconsider HP for our next server.
> > We have a 4.5 year old Dell PowerEdge 2500. Six hard drives in a RAID5. > > Small Business Server 2000. Backup Exec 8.5. We've been hoping to > > replace > > this server within the next month, upgrading everything.
> Call Microsoft immediately (open 24/7) and they'll work with you until the > problem is resolved for a flat fee. If you are on a tight budget, this will > be your best bet. Reconnecting mailboxes is a piece of cake, but everything > else is a little more involved. :-)
> Inaccessible boot device sounds like incorrect drivers or some other issue > with that RAID controller. Have you checked firmware on that RAID > controller? Given that two drives have failed, I am not sure that I would > trust that card again, at least until its batteries were replaced, firmware > was updated, and it was burned it for 24 hours. You do know that you have to > replace its batteries on the battery-backed cache every 3-4 years, right?
> Do you basically just want to recover data? There are services that will > hold your mail until your Exchange is back. I don't remember the name off > top of my head, but search for "mail holding" in Exchange newsgroups.
> Download a trial of BackupExec 10 from Veritas and restore with that. > Veritas will certainly support Version 10? :-) You want to do an offline > restore (the EDB and STM files).
> New configuration - just say "No" to RAID5:
> RAID 1 - System Partition/Transaction Logs > RAID 1 - Exchange data > RAID 1 - Data files
> I would build a BartPE disk with Dell RAID drivers on it and access your > data that way. It does sound like the data got restored correctly, but > something is amiss in the RAID config, which prevented the system from > coming back online. I would take this time to optimize your disk subsystem > layout.
> Hands down, I think working with Microsoft would be your best option. :-)
> There is a reason why I sell HP servers. > -- > Leonid S. Knyshov, CEO > Crashproof Solutions, LLC - http://www.crashproofsolutions.com > MCP Exchange 2003/Small Business Server 2003, CCNA, SCSA 8, NCIE > Microsoft Small Business Specialist Partner
> I had rebooted many times before this happened, which is why I've been > associating the crash with something that happened as a result of > restoring > the System State. But maybe I'm discounting the hints that it's > hardware/firmware related. I did not know that I had to replace the RAID > controller's batteries.
> What is a a BartPE disk?
> Again, thank you, this seems logical and sets my mind a bit at ease. > Matthew
Sure.
BartPE is a troubleshooting environment - in essence you can boot into Windows from CD. Look it up on Google.
Most people never replace the batteries, so don't worry. :-)
I would concentrate on making sure the RAID drivers are properly setup and I am not so sure I'd patch everything and rather I'd make sure the system reboots after a restore. Seriously though, you should have Microsoft online with you. They will bring in progressively more senior people to help you, which really helps. -- Leonid S. Knyshov, CEO Crashproof Solutions, LLC - http://www.crashproofsolutions.com MCP Exchange 2003/Small Business Server 2003, CCNA, SCSA 8, NCIE Microsoft Small Business Specialist Partner
> We have a 4.5 year old Dell PowerEdge 2500. Six hard drives in a RAID5. > Small Business Server 2000. Backup Exec 8.5. We've been hoping to replace > this server within the next month, upgrading everything.
> Two hard drives failed, we lost all data. I replaced the hard drives, got > the RAID functioning, with Dell's help. I installed SBS2K, from the discs. > I updated and patched it. [This was time-consuming; neither Windows Update > nor Microsoft's MSBE (or whatever their answer to HFNETCHK is) worked at > first. I had to manually updated BITS and some other files, bring it up to > Windows 2000 SP 4, then I could install SBS2K SP1, then apply the 30-ish > security patches.]
> Then I installed Backup Exec 8.5. I looked for patches for it on Veritas' > website - they didn't seem to have anything crucial for it.
> Then I followed Veritas' instructions on disaster recovery (their > Intelligent Disaster Recover had not been an install option). I set the > Exchange databases so that they could be overwritten by a restore. Their > instructions on restoring the System State were to reboot in Directory > Services Recovery Mode (similar to safe mode), and restore the system state > (I also included Information Store and a chunk of our file system data in > this restore). Then it was supposed to prompt me for a reboot.
> I restored. I rebooted when prompted. It stopped at the Windows screen > with this:
> If you're seeing this message for the first time, reboot. If it comes up > again:
> Check for viruses. Remove any newly installed hard drives or hard drive > controllers. Check your hard drive to make sure it is properly configured > and terminated. Run CHKDSK /F to check for Hard Drive corruption, and then > restart.
> I rebooted, same Stop happened. I booted to the disk for Symantec AntiVirus > Corporate Edition (a few years old). I ran a scan, it found no infected > files on the C:.
> I called Dell back. We quickly determined that it's not a RAID issue. We > tried to boot to the Last Known Good hardware configuration: no dice. He > suggested I try to repair the OS with the installation disk. I did the > repair where it replaced all the files on the C: with those on the disk. > Rebooted to the same Stop message. He suggested I could do a parallel OS > install. I'm not sure what that would accomplish.
> I called Veritas. Unsurprisingly, they refused to help me because my > version of Backup Exec is too old.
> Here are the options I'm seeing, please let me know what you think:
> 1) Reinstall SBS from scratch again, patch it up again (taking 4-5 hours?). > Reinstall BackupExec 8.5 again. Verify that I can at least recover my data > and my exchange databases from tape. This time, instead of restoring the > System State, manually add each user (there's maybe 25 or 30). Then, call > Microsoft and pay an incident for them to walk me through connecting each > user to his/her right mailbox. Is this even possible? What is involved?
> 2) Reinstall SBS. Purchase current version of Backup Exec, hope that it > will be able to restore files and system state from our tape that was made > with 8.5. Would the current version of Backup Exec even work on SBS 2000?
> Is there any way SBS2000's native backup program would be able to restore > with the tape that was made from BE?
> At this point, we've been offline for two days, and management, although > kind and understanding, wants to be back online ASAP.
> Does anyone know of a service that will accept and hold incoming mail for > our domain, then forward it to us when we're back online?
> Any recommendations would be hugely appreciated. We're a nonprofit human > rights organization in NYC with a very tight budget, but if we could pay > someone more capable than me to have this fixed quickly, we would.
Welcome - I've just been through what you're going through. Stressful huh.
The SP1a *includes* SP4 BTW, and shoulda installed that as it noted it was not (installed). Worked for me like that. Then I added the other SP's not contained in SP1a (Exchange and ISA FP1 and SP's)
Then I got Veritas 8.6 on - tried a DSRM recovery - twice - with little joy. Ended up doing what you've done, scratch rebuild, and use the tape data to restore just the data.
Exhange wasn't too bad, from memory... * I used a 'lab' PC and installed *another* copy of SBS (I made a *weeee* mistake, named the FQDN wrongly (put an extra character in by mistake!!!) - no going back (unless I reinstalled again) - hence I built up a lab PC (named it right this time).
Put the users back on (yep, manually), then I mounted the old store (from tape data). Mbconn to connect up the email boxes w' Exchange. Exmerge to pst the data out. And then exmerge on the rebuilt Server to get the User data back in. Worked fine.
Then there was all the tweaking and 3rd party apps and data.
Five days later, they were back up and running (two days over the weekend thankfully).
I can't help it, the only part of Leonid's advice I agree with is 'CALL MS'.
Break your problem down to it's most simplistic piece, you are unable to boot due to a 0x7B error.
A 'parallel install' is no problem. All it means is to install windows to another partition on the same system. This will allow you to inspect the SBS' registry, perform RAID/HDD management/testing, isolate your problem.
"Applebaum" <mappleNOS...@inch.com> wrote in message
> 1) Reinstall SBS from scratch again, patch it up again (taking 4-5 > hours?). > Reinstall BackupExec 8.5 again. Verify that I can at least recover my > data > and my exchange databases from tape. This time, instead of restoring the > System State, manually add each user (there's maybe 25 or 30). Then, call > Microsoft and pay an incident for them to walk me through connecting each > user to his/her right mailbox. Is this even possible? What is involved?
If you want to try this again you can forget most of the patching stuff. Install _just_ the OS portion of SBS2000, apply SP4, then start your restore process.
> 2) Reinstall SBS. Purchase current version of Backup Exec, hope that it > will be able to restore files and system state from our tape that was made > with 8.5. Would the current version of Backup Exec even work on SBS 2000?
You've discovered, in the worst possible way, why I use NTBackup. I wouldn't waste my money buying something which has already proven it's uselessness.
> Is there any way SBS2000's native backup program would be able to restore > with the tape that was made from BE?
I'm pretty sure no. I'm not up on current status but if (my really bad) memory serves, though 2000+ NTBackup is, basically, a cut down version of BE (MS bought it from Veritas) 2000 NTBackup will not read BE8 tapes.
> At this point, we've been offline for two days, and management, although > kind and understanding, wants to be back online ASAP.
> Does anyone know of a service that will accept and hold incoming mail for > our domain, then forward it to us when we're back online?
Your ISP may be able to implement 'secondary' or 'backup' MX while you are down. Anyone who uses their own mail server (SBS Exchange, or ANY other mail system) should look at having secondary services. ZoneEdit will supply such for a 'token' payment per year.
> Any recommendations would be hugely appreciated. We're a nonprofit human > rights organization in NYC with a very tight budget, but if we could pay > someone more capable than me to have this fixed quickly, we would.
I'm a long way from NYC (I'm in AU) hopefully someone closer will notice your predicament.
I'll skip most of today's story for now, because I haven't slept much lately.
The first two Microsoft technicians I spoke with today concluded that our STOP error message was caused by a corrupt registry, probably the registry I had restored from our backup tape. (They spent many hours trying to repair that registry)
So I've now done a fresh install of Windows 2000 Server and it's fully patched. I'm letting it go overnight, to make sure lingering LsaSrv error msgs don't come up anymore now that it's been patched. (The third MS tech suggested leaving it for a few hours for this purpose.)
Tomorrow morning, assuming that we're still clean, I plan to continue with the SBS install. I'll be manually recreating our user directory, security settings, etc.
My question is about Backup Exec, and recovering the rest of our files. Half of our data is still on a backup tape. If you recall, we have BE 8.5, which Veritas no longer supports. Leonid recommended downloading BE 10. Here are my concerns:
Will BE 10 be able to read our tapes that were created using BE 8.5? I suppose that if they can't, I can always uninstall it, and going with our 8.5 install disk.
But if I need to use 8.5 in order to access tapes made under 8.5, here's my worry: Our STOP crash, and registry corruption occured after installing BE 8.5 and doing a restore. Admittedly, the restore included System State. But I recall, about 4 years ago when I first installed SBS and BE 8.5, there were issues then, too. Is this software too buggy, and now without support? Moot point if BE10 can read tapes from BE8.5.
Well, that's the crux of my question for now, assuming that our server stays alive until tomorrow.
Many Thanks in advance!
Matthew
"Applebaum" <mappleNOS...@inch.com> wrote in message
> We have a 4.5 year old Dell PowerEdge 2500. Six hard drives in a RAID5. > Small Business Server 2000. Backup Exec 8.5. We've been hoping to replace > this server within the next month, upgrading everything.
> Two hard drives failed, we lost all data. I replaced the hard drives, got > the RAID functioning, with Dell's help. I installed SBS2K, from the discs. > I updated and patched it. [This was time-consuming; neither Windows Update > nor Microsoft's MSBE (or whatever their answer to HFNETCHK is) worked at > first. I had to manually updated BITS and some other files, bring it up to > Windows 2000 SP 4, then I could install SBS2K SP1, then apply the 30-ish > security patches.]
> Then I installed Backup Exec 8.5. I looked for patches for it on Veritas' > website - they didn't seem to have anything crucial for it.
> Then I followed Veritas' instructions on disaster recovery (their > Intelligent Disaster Recover had not been an install option). I set the > Exchange databases so that they could be overwritten by a restore. Their > instructions on restoring the System State were to reboot in Directory > Services Recovery Mode (similar to safe mode), and restore the system state > (I also included Information Store and a chunk of our file system data in > this restore). Then it was supposed to prompt me for a reboot.
> I restored. I rebooted when prompted. It stopped at the Windows screen > with this:
> If you're seeing this message for the first time, reboot. If it comes up > again:
> Check for viruses. Remove any newly installed hard drives or hard drive > controllers. Check your hard drive to make sure it is properly configured > and terminated. Run CHKDSK /F to check for Hard Drive corruption, and then > restart.
> I rebooted, same Stop happened. I booted to the disk for Symantec AntiVirus > Corporate Edition (a few years old). I ran a scan, it found no infected > files on the C:.
> I called Dell back. We quickly determined that it's not a RAID issue. We > tried to boot to the Last Known Good hardware configuration: no dice. He > suggested I try to repair the OS with the installation disk. I did the > repair where it replaced all the files on the C: with those on the disk. > Rebooted to the same Stop message. He suggested I could do a parallel OS > install. I'm not sure what that would accomplish.
> I called Veritas. Unsurprisingly, they refused to help me because my > version of Backup Exec is too old.
> Here are the options I'm seeing, please let me know what you think:
> 1) Reinstall SBS from scratch again, patch it up again (taking 4-5 hours?). > Reinstall BackupExec 8.5 again. Verify that I can at least recover my data > and my exchange databases from tape. This time, instead of restoring the > System State, manually add each user (there's maybe 25 or 30). Then, call > Microsoft and pay an incident for them to walk me through connecting each > user to his/her right mailbox. Is this even possible? What is involved?
> 2) Reinstall SBS. Purchase current version of Backup Exec, hope that it > will be able to restore files and system state from our tape that was made > with 8.5. Would the current version of Backup Exec even work on SBS 2000?
> Is there any way SBS2000's native backup program would be able to restore > with the tape that was made from BE?
> At this point, we've been offline for two days, and management, although > kind and understanding, wants to be back online ASAP.
> Does anyone know of a service that will accept and hold incoming mail for > our domain, then forward it to us when we're back online?
> Any recommendations would be hugely appreciated. We're a nonprofit human > rights organization in NYC with a very tight budget, but if we could pay > someone more capable than me to have this fixed quickly, we would.
BackupExec 8.0 and older can be migrated into version 10. In your case, you should be able to do an install, then recreate media catalogs manually by scanning the tapes. You can then restore to alternate disk locations. (Never accept the default restore settings. You'll overwrite data in a most inconvenient way.)
>From Veritas (now Symantec) manual for 10.0d:
Cataloging Media in a Drive Use Catalog to log the contents of a media created by a product other than this installation of Backup Exec (imported media), or to create a new catalog on the local hard drive if the catalog for the media no longer exists. Media must have a catalog before data can be restored from it or verified. You can also catalog backup-to-disk files. If the media is being used by this system for the first time, you may need to inventory the media first[snip]
I think that means that I can install version 10 without installing 8.x before it, and my tapes will be read.
Thank you very much! I hope to attempt this on Friday!
Meanwhile, am having difficulties installing Symantec AntiVirus, so I am going without antivirus until I can get Exchange up and running (Exchange databases were recovered from tape, using BE 8.5 on a prior installation. Restored to a data partition that survived when the prior installation's registry got corrupted by BackupExec's restoring the System State.)
I've added users, security & dist groups manually, and will have Microsoft's help in getting the Exchange databases online, and in connecting users to their proper mailboxes. After that, I think I'll try to get an antivirus solution installed. Maybe the free trial version of Symantec A.V. We're nonprofit, and usually buy software like Symantec's at about 10% of their retail price, but that disqualifies us from getting tech suppt from them. I'm hoping that Symantec will provide tech support if their free trial version doesn't install. And hopefully Symantec Mail Security will install as well.
After all of this (and a week on a beach couldn't hurt), I need to have a serious talk with this client about disaster preparation. Before that, I'll be mining these newsgroups for research. One big lesson from this week is, when you keep using old versions of software, neglecting to upgrade, it makes it potentially difficult and time-consuming to recover from disaster.
> BackupExec 8.0 and older can be migrated into version 10. In your > case, you should be able to do an install, then recreate media catalogs > manually by scanning the tapes. You can then restore to alternate disk > locations. (Never accept the default restore settings. You'll > overwrite data in a most inconvenient way.)
> >From Veritas (now Symantec) manual for 10.0d:
> Cataloging Media in a Drive > Use Catalog to log the contents of a media created by a product other > than this installation > of Backup Exec (imported media), or to create a new catalog on the > local hard drive if the > catalog for the media no longer exists. Media must have a catalog > before data can be > restored from it or verified. You can also catalog backup-to-disk > files. If the media is being > used by this system for the first time, you may need to inventory the > media first[snip]
In article <#Wk5PsOOGHA.1...@TK2MSFTNGP11.phx.gbl>, mappleNOS...@inch.com says...
> I think that means that I can install version 10 without installing 8.x > before it, and my tapes will be read.
> Thank you very much! I hope to attempt this on Friday!
> Meanwhile, am having difficulties installing Symantec AntiVirus, so I am > going without antivirus until I can get Exchange up and running (Exchange > databases were recovered from tape, using BE 8.5 on a prior installation. > Restored to a data partition that survived when the prior installation's > registry got corrupted by BackupExec's restoring the System State.)
> I've added users, security & dist groups manually, and will have Microsoft's > help in getting the Exchange databases online, and in connecting users to > their proper mailboxes. After that, I think I'll try to get an antivirus
Dunno if you've already paid MS for this support or not - but it's a pretty simple procedure (given your DN/FQDN is the same as before).
Stop the Store service.
Go into Program Files\Exchsrvr\MDBDATA - copy the edb and stm files somewhere (nothin' in 'em anyway).
Delete all the other files in MDBDATA.
Copy your old exchange data in (stm's and edb's).
Use eseutil.exe to check/repair the databases.
Start the Store Service.
Go into Exchange Server and mount the store.
Use Mbconn.exe to connect up the mailboxes.
Check in Exchange Server that they are connected (you *might* need to right click each user and connect 'em again in Exchange Server).
That's all of the top of my head - I can no longer find the MS articles I used - but if you get any error messages just Google 'em (<error message> site:.microsoft.com) - and hopefully you'll find what I found.
I do have an open ticket with MS that will include this. We decided it was worth the expense, the disaster recovery wasn't going as planned.
I hadn't realized how simple this looks, the database restore and user connections. That would be a relief, if it goes nicely. I haven't used MBconn.exe before. New knowledge...good!
> In article <#Wk5PsOOGHA.1...@TK2MSFTNGP11.phx.gbl>, > mappleNOS...@inch.com says... > > I think that means that I can install version 10 without installing 8.x > > before it, and my tapes will be read.
> > Thank you very much! I hope to attempt this on Friday!
> > Meanwhile, am having difficulties installing Symantec AntiVirus, so I am > > going without antivirus until I can get Exchange up and running (Exchange > > databases were recovered from tape, using BE 8.5 on a prior installation. > > Restored to a data partition that survived when the prior installation's > > registry got corrupted by BackupExec's restoring the System State.)
> > I've added users, security & dist groups manually, and will have Microsoft's > > help in getting the Exchange databases online, and in connecting users to > > their proper mailboxes. After that, I think I'll try to get an antivirus
> Dunno if you've already paid MS for this support or not - but it's a > pretty simple procedure (given your DN/FQDN is the same as before).
> Stop the Store service.
> Go into Program Files\Exchsrvr\MDBDATA - copy the edb and stm files > somewhere (nothin' in 'em anyway).
> Delete all the other files in MDBDATA.
> Copy your old exchange data in (stm's and edb's).
> Use eseutil.exe to check/repair the databases.
> Start the Store Service.
> Go into Exchange Server and mount the store.
> Use Mbconn.exe to connect up the mailboxes.
> Check in Exchange Server that they are connected (you *might* need to > right click each user and connect 'em again in Exchange Server).
> That's all of the top of my head - I can no longer find the MS articles > I used - but if you get any error messages just Google 'em (<error > message> site:.microsoft.com) - and hopefully you'll find what I found.
In article <OfQJNN6NGHA.3...@TK2MSFTNGP09.phx.gbl>, n...@your.nellie says...
> You've discovered, in the worst possible way, why I use NTBackup. I wouldn't > waste my money buying something which has already proven it's uselessness.
Well maybe NTBackup worked for you during disaster recovery, but my recent experience with an MS Security Patch gone awry was awful.
The POP3 patch somehow affected the system so that none of my Sceduled Tasks would run. (I recognized this because SBS Backup was not backing up).
After getting no help from the newsgroup,I decided I would restore the system state using NTBackup. As you know, to restore you need to boot into "Safe Mode" (Active Directoy deactivated) and run NTBackup from there. Well after 5 attempts with reboots NTBackup would just hang...that is reliable recovery software isn't it!!
I finally restored the system in 15 minutes with Acronis True Image Server running from a CD, and a "Notebook" size USB hard drive which contained an image of the Active Partition.
The moral of the story. Don't use tape, and don't use any software developed by Veritas.
|
