Re: Windows 2008 SBS - bare metal restore/disaster recovery

Perfect. And exactly the sort of test that gives you real confidence that you'll actually be able to recover. Now, take it one step further. Write the whole experience up in some detail. What you did, what you ran in to, how you fixed it, etc. What you wish you'd done first. Do it now, while it's fresh in your mind. You'll likely find other things you want to tweak in the process.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"blair003" <stepped@xxxxxxxxx> wrote in message news:342b741e-8b3c-4cd7-b07d-005a0a87ab6c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I shrunk the volumes by 20MB each using disk management which worked
fine. Thanks!

However I tried the restore again and received a similar error. Turns
out, the RAID arrays on the spare server I was restoring to were
created in the incorrect order such that what was presented to the OS
as Disk 0 on the live server was now Disk 1 on the spare server, and
vice versa (and disk0 and disk1 were different sizes).

Once I fixed that, the restore went fine. I restored to the DL385
(AMD) from the DL380 (Intel) backup. It booted but initially showed
only the SBS console – no start menu or desktop – after 5 minutes it
came right and started installing device drivers automatically. After
it finished installing it requested a reboot and after the reboot it
worked fine.

Blair

On Jun 9, 12:51 am, "Charlie Russel - MVP"
<char...@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
The builtin volume resize in Windows Server 2008 (and thus SBS 2008) should
work fine to shrink the volume. You don't need to shrink it very much, just
enough to get it squeezed on to the recovery server.

Diskmgmt.msc, select the volume, right click, shrink volume, if I remember
correctly off the top of my head. I'd definitely use the native solution -
it isn't as aggressive at finding space as some third party solutions, but
it's fully supported and works just fine.

--
Charlie.http://msmvps.com/blogs/xperts64http://mvp.support.microsoft.com/profile/charlie.russel

"blair003" <step...@xxxxxxxxx> wrote in message

news:88d9673f-c46e-40c8-9802-20503c926ca9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

I have created a bit of a problem for myself and hope to benefit from
the experience here.

I have an HP DL380 G4 running Windows 2008 SBS. The system has two
RAID arrays on the built in Smart Array 6i. The OS is a RAID1 array
comprised of two 146GB drives and the data array is RAID1+0 made from
4x 72.8GB drives. Each array contains a single partition using 100% of
the available space.

Everything on this server is operating perfectly and it’s been solid
for about five months.

I am creating/testing a new disaster recovery plan. In the past the
plan has been old school - reinstall server from scratch, configure,
patch, restore data. But given that I have backups from Windows Server
Backup (via the SBS Console), I thought I would try a bare metal
restore as it could save a lot of time. I booted into Windows Complete
PC Restore to try a bare metal restore to an HP DL385 G1 (AMD Opteron
equivalent of the DL380 G4). This system has 4x72.8GB drives
configured in a RAID1+0 array.

When attempting to restore, I get an error about the destination drive
being too small. If I understand correctly, the destination partition
has to be larger than the source partition in order for this to work.

Given where I am now, what options do I have in terms of a disaster
recovery plan?

Ideally I think I would like to use the Complete PC Restore route,
although given the hardware is a bit different, I am not sure it will
work properly anyway… and even if it did, is this the best option for
disaster recovery in WIndows 2008 SBS?

I don’t like to mess with a perfectly working server (if its not
broke..), but the server is only using 57GB of the 146GB RAID1 OS
partition, so presumably one option is to resize the array to say 70GB
and create a new partition with the remaining space. How reliable is
partition resizing with NTFS on Windows 2008? Can you recommend any
software to do it?

Another option is obviously to purchase some 300GB drives, but they
are pretty expensive so I would really rather not.

Any other ideas or recommendations?

Thanks
Blair

.

Relevant Pages

  • Re: Two Disaster Recovery Questions
    ... I support the Professional Association for SQL Server ... > recovery site ... > second restore at the recovery site. ...
    (microsoft.public.sqlserver.server)
  • RE: Disaster Recovery AD + Exchange 2003
    ... I am actually looking at restoring the whole server to a different site into ... Directory recovery options available to you. ... let's take Exchange (take a look at the Exchange 2003 DR ... recovery to retrieve the item or restore the entire public store. ...
    (microsoft.public.windows.server.active_directory)
  • Restore Exchange Server2003 aufsetzen
    ... Nachdem ich nun etliche Abende damit verbracht haben, eine Exchange Restore ... um einen Recovery Server aufzusetzen: ... Dieses Hilfsmittel verwendet die neu im Windows 2003 Server verbaute ... Postfachspeicher mit der rechten Maustaste Offline stellen (Bereitstellung ...
    (microsoft.public.de.german.exchange2000.general)
  • Re: OT but on topic. Acronis restore to new hardware woes
    ... I downloaded the software, installed it, and created the recovery disc ... option - it was this recovery CD which I used for my test restore, ... Production server is running an Intel Motherboard with an Intel Raid ... Check your SBS with the SBS Best Practices Analyzer ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2008 SBS - bare metal restore/disaster recovery
    ... the spare server just sitting there ready to go, ... However I tried the restore again and received a similar error. ... RAID arrays on the built in Smart Array 6i. ... If I understand correctly, the destination partition ...
    (microsoft.public.windows.server.sbs)
Loading