Re: Disk with NTDS failing

I have one account backing up over a 100 gigs every night twice. Once
using NTBackup to usb drive starts at 5:00 pm. A second backup using
Backup Exec to DLT tape starts at 11:00 pm.

I have backed up the system state and Exchange separately from other
stuff when I was having issues.

On Mon, 12 May 2008 19:56:00 -0700, Pallium
<Pallium@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Thanks Cliff and Jim,

So, any clue about my experience? Is a 79 GB backup file unusual? There sure
seemed to be enough hits on the 'net about this "unrecognized media" error I
got.

Would it be advisable to do two separate backups, one of system state, and
one of my Exchange mail data?

-Bryan

"Jim Behning SBS MVP" wrote:

I have restored from scratch a server using NTBackup. I am not alone
on total server restores using NTBackup. Disaster recovery 101 is
doing test restores frequently. Part 2 is having multiple go back
restore files.

On Mon, 12 May 2008 12:38:01 -0700, Pallium
<Pallium@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I never did get the backup to restore. Howeer, I *did* finally get things
working. The drive that was dying, that had Active Directory on it...right
before it died, I copied SysVol and NTDS to another drive. Good thing. That's
what saved me.

I put those onto the replacement drive, with the same drive letter, and SBS
started up ok. I'm back online and getting mail.

This experience, however, has left my faith in ntbackup deeply shaken. I
need a *reliable* backup mechanism, and my experience this weekend is *not*
giving me that feeling.

Is there something better than ntbackup? Are there best practices written
down somewhere? I really need to avoid this kind of headache in the future.

-Bryan

"Pallium" wrote:

Hi everyone,

I've got an SBS 2003 SP2 server. The disk on which NTDS resides (not the
boot disk), is failing, and keeping lsass.exe from starting. I can boot into
Directory Services Restore Mode, logged in as machine Admin.

My AD event log has events indicating that AD can't access its database,
such as this (event ID 508)

NTDS (412) NTDSA: A request to write to the file "C:\NTDS\temp.edb" at
offset 172032 (0x000000000002a000) for 122880 (0x0001e000) bytes succeeded,
but took an abnormally long time (122 seconds) to be serviced by the OS. This
problem is likely due to faulty hardware. Please contact your hardware vendor
for further assistance diagnosing the problem.

SO:
How do I move directory services (x:\NTDS) to a different disk? Or if that
is impossible, recreate it on another disk?

Thanks,
Bryan

See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx

See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx
.

Relevant Pages

  • Re: NTBackup requires 18-23 hours to complete.
    ... going to spend the money to buy huge usb drives. ... that I am using SBS and I know it works, but that something is wrong in the ... else, I never implied that the SBS backup didn't work, only that the wizard ... NTBackup due to the wizards insistance on including ...
    (microsoft.public.windows.server.sbs)
  • Re: NtBackup hangs during scheduled backups
    ... In your logs, ntbackup isn't starting. ... You may try deleting them all if they exist, and then try sbsbackup wizard, which will create a scheduled backup. ... Les Connor [SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup requires 18-23 hours to complete.
    ... troubleshooting involved replacing my existing hardware with USB drives, ... Les Connor [SBS MVP] ... else, I never implied that the SBS backup didn't work, only that the ... NTBackup due to the wizards insistance on ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup requires 18-23 hours to complete.
    ... I'm not sure if you use SBSbackup, or only the native NTbackup to configure your backups. ... Considering you want something different than SBSBackup offers, I'd suggest you run the backup configuration wizard and elect *not* to use SBS backup, and do your configuration via NTbackup, or a third party backup application. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Backup/Restore- Best Practice
    ... I have always loved tape and never had an issue restoring. ... us are going to use hard disks (As SBS 2008 was designed for this). ... As long as the client gets a reliable backup, ... Do practice restores periodically. ...
    (microsoft.public.windows.server.sbs)