Check this tech note.
http://seer.support.veritas.com/docs/251163.htm
I had to recover a production server after crash few weeks back. What I did
was to restore system_state and C: drive at one go. Make sure you have
enough space in the C: drive. Otherwise it will not restore all the required
files and will cause the system reboot continuously. I have seen this happen
before.
-Shyam
On 8/2/06, Spearman, David <spe08 at co.henrico.va.us> wrote:
>
> Sorry one and All, made a mistake, it was 5.1mp3 that had the
> problem. My support call is below
>
>
>
> I tried restoring a w2k3 server as a test and got an lssas error on
>
> reboot, with the machine constantly rebooting. After going to your support
>
>
> page I ran in to the following document
>
> Document ID: 274353
>
> *http://support.veritas.com/docs/274353*<http://support.veritas.com/docs/274353>
>
> It essentially says contact veritas. So what now?
>
> RESPONSE
> David,
>
> As we had discussed, this is a known issue, so there wasn't any
> configuration mistakes on your end. There is a technote with troubleshooting
> steps to try and remedy the issue. This isn't a 100% guaranteed fix, as we
> had discussed regarding the use of the Win2Koption.
>
> http://support.veritas.com/docs/262411
>
> To reiterate what's occurring:
>
> What is happening is that Windows 2003 Shadow Copy Components have changed
> so that there is a slip in recovering some registry hives. (see the
> Microsoft link at the bottom of the technote) For us to keep up with these
> changes, we need to modify our software with new patch releases. The new
> release for this issue is due out soon, but no concrete date that I can
> release. In the meantime, I will create an escalations task and will inform
> you on what I can get from backline, and what they may request from you for
> additional information.
>
> At any rate it was definately fixed with mp4, for your sake Simon I would
> test your MP2 or upgrade your master/media servers to mp4.
>
> dds
>
>
> -----Original Message-----
> *From:* WEAVER, Simon [mailto:simon.weaver at astrium.eads.net]
> *Sent:* Wednesday, August 02, 2006 6:56 AM
> *To:* Spearman, David; Wilkinson, Tim; veritas-bu at mailman.eng.auburn.edu
> *Subject:* RE: [Veritas-bu] Restoring entire servers (Windows)
>
> *David*
> *What is the bug, as we use MP2 NBU 5.1*
> **
> *can you provide details on this?*
> **
> *Thanks*
>
> *Regards*
>
> *Simon Weaver
> 3rd Line Technical Support
> Windows Domain Administrator*
>
> *EADS Astrium Limited, B23AA IM (DCS)*
> *Anchorage Road, Portsmouth, PO3 5PU*
>
> *Email: **Simon.Weaver at Astrium-eads.net* <Simon.Weaver at Astrium-eads.net>
>
> -----Original Message-----
> *From:* Spearman, David [mailto:spe08 at co.henrico.va.us]
> *Sent:* 02 August 2006 11:33
> *To:* Wilkinson, Tim; veritas-bu at mailman.eng.auburn.edu
> *Subject:* Re: [Veritas-bu] Restoring entire servers (Windows)
>
> Tim,
>
> Windows is the easiest restore in the entire venue. From scratch, load the
> OS (patched to whatever level your version of NBU requires) and leave it in
> the workgroup mode with a workgroup having the same name as the domain it
> was in. Load the nbu agent, partition the drive, then do a FULL resore,
> reboot, done. I have actually done this across disimiliar platforms, albeit
> you have to be a bit tricky. In short we will never waste money on windows
> bmr, it's just to easy to do it the old fashioned way. The only caveats are
> 1. Domain Comtrollers require a reboot into domain controller restore mode
> 2. NB5.1 mp2 had a major bug with w2k3. Just make sure you are higher (or
> lower) than that.
>
> -----Original Message-----
> *From:* veritas-bu-bounces at mailman.eng.auburn.edu [mailto:
> veritas-bu-bounces at mailman.eng.auburn.edu] *On Behalf Of *Wilkinson, Tim
> *Sent:* Wednesday, August 02, 2006 12:27 AM
> *To:* veritas-bu at mailman.eng.auburn.edu
> *Subject:* [Veritas-bu] Restoring entire servers (Windows)
>
> I'm just reviewing disaster recovery at the moment and have found a
> paragraph or 2 recommending that all system files and application files are
> backed up. We generally run A_L_D in our policies 'just in case' but I've
> been thinking about restoring system and application files and wonder how
> most people approach this sort of thing.
> We don't use BMR so I figure the best way to restore an entire server is
> to rebuild the OS, install any applications then restore actual 'data'; I've
> always considered if you try to restore 'everything' it could get a bit
> messy and confused if some of it doesn't get restored exactly as it was
> before.
> Without using BMR, can you restore the contents of an entire server in
> Windows (I'm talking the whole show including system files, system_state
> data, applications and everything)?
>
> Cheers,
>
>
>
>
> ---------------------------------------------------------------------
> Tim Wilkinson
> I.T. Support Officer
> Science Corporate Information Systems
> Defence Science & Technology Organisation
> Department of Defence
>
> Tel: (02) 96921484
> Fax: (02) 96921562
> Email:***** tim.wilkinson at dsto.defence.gov.au*
>
>
>
>
> This email is for the intended addressee only.
> If you have received it in error then you must not use, retain,
> disseminate or otherwise deal with it.
> Please notify the sender by return email.
> The views of the author may not necessarily constitute the views of
> Astrium Limited.
> Nothing in this email shall bind Astrium Limited in any contract or
> obligation.
>
> Astrium Limited, Registered in England and Wales No. 2449259
> Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
> England
>
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060802/59d1bf4a/attachment-0001.html
|
