Re: URGENT - System State Restore - SBS

A restore to different hardware is going to be somewhat messy, and generally
would only be used for disaster recovery where there isn't another option.

What you could try is, after the restore - and after the blue screen - boot
to your Windows CD (disk 1) and perform a repair installation. This often
succeeds, but you'll have to do some work in devman afterwards to clean up
non-present devices from the previous installation. This includes NICs - and
the non-present nics and now invalid network configuration will likely cause
a *very* long boot time, but eventually the server should come up.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Andy Wolsten" <AndyWolsten@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5D5440F0-66FC-4FC1-AE93-E73D7F44CF5A@xxxxxxxxxxxxxxxx
i cant remember exactly. im just rebuilding the server now to reattempt the
restore.

Reading the article on SBS restore there are various things which are
disimilar between the current live server and the new test server. It is a
completely different hardware set for a start, disk sizes, cpu etc, but
would
this affect the restore of the system state only?



"cjobes" wrote:

What is the next line under the stop error? 0x0000007b is normally
inaccessible_boot_device

Claus

"Andy Wolsten" <AndyWolsten@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EC0A6A9E-72D5-483C-8365-B110CAD19BC7@xxxxxxxxxxxxxxxx
ok, i built an offline copy of my SBS server, booted in to Directory
Services
Mode and performed a system state restore via NT backup from a
successful
System State backup we took yesterday

On reboot, when the win2k3 progress screen comes up the OS blue screens

message:

STOP 0x0000007b (0xf789A63C,0xC0000034, 0x00000000, 0x00000000)
-(not that i expect anyone to understand this exactly of course)

any ideas??






.

Relevant Pages

  • RE: Reboot Loop after Restore
    ... Thank you for posting in SBS newsgroup. ... As the document stated, the hardware must ... be similar for a restore. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 Connection logon problems
    ... I think you'll see something to ease a restore to different hardware, ... Les Connor [SBS Community Member] ... When i went from the old server to the new ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2000 - New AD (users manually re-created) - Can I restore
    ... restore the first time I couldn't get back into the system at all. ... > SP1a includes SP4, to eliminate any other potential problems, it may be best ... > the time of your system state backup). ... The other fixes and features of SBS ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: How to use Windows Backup?!!
    ... AD is only backed up as part of the system state, and as such, the system must be in the *same* state. ... With that said, if you are backing up system state *and* the "program files" directory and doing a bulk restore, you will usually be fine. ... Yes I restored without incident from a good SBS backup. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exporting Active Directory Data
    ... If I bought a new server, the hardware will be different from the old ... same hardware, same scsi controleur, or no restore ... So the backup solution is to be put aside. ... as long as you backup the whole C: drive, and a System State backup (I do ...
    (microsoft.public.windows.server.active_directory)
Loading