ADSM-L

Re: [ADSM-L] SV: Windows 2003 32bit whole system restore

2011-03-09 05:07:29
Subject: Re: [ADSM-L] SV: Windows 2003 32bit whole system restore
From: Steven Langdale <steven.langdale AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 9 Mar 2011 10:06:29 +0000
Thanks for the quick reply, looks like my assumption was incorrect.

Looks like some clopt updates are in order!

Steven

On 9 March 2011 09:06, Christian Svensson <Christian.Svensson AT cristie DOT 
se>wrote:

> Hi,
> Normally NICs do have a couple of files that don't belong to System State
> that are binary and others.
>
> The Mouse situation can't I explain but I'm guessing you have the same
> issue as the NIC problem.
>
> Best Regards
> Christian Svensson
>
> Cell: +46-70-325 1577
> E-mail: Christian.Svensson AT cristie DOT se
> Supported Platform for CPU2TSM::
> http://www.cristie.se/cpu2tsm-supported-platforms
>
> ________________________________________
> Från: Steven Langdale [steven.langdale AT GMAIL DOT COM]
> Skickat: den 9 mars 2011 09:34
> Till: ADSM-L AT VM.MARIST DOT EDU
> Ämne: Windows 2003 32bit whole system restore
>
> Hello All, a quick systemstate restore question....
>
> Our current backup process for Win2003 is to include the systemstate but
> EXCLUDE C:\windows  from the standard filesystem backup - this is under the
> assumption that the systemstate covers all that is needed in there (for a
> base system recovery at least)
>
> In testing a system recovery (VMware environ) the systemstate and C:
> restore
> work fine but after a reboot there is no network and no mouse - but the
> keyboard works :)
>
> If we do another backup of the donor with the C:\windows INCLUDED, then do
> a
> systemstate & C: restore (in that order), all works perfectly after a
> reboot.
>
> So, was my understanding of the systemstate backup not correct i.e. is this
> working as designed, or do I have an issue?
>
> Client is  5.5.3.0.
>
> Thanks
>
> Steven
>

<Prev in Thread] Current Thread [Next in Thread>