This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C448DA.783C09CC
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C448DA.783C09CC"
------_=_NextPart_001_01C448DA.783C09CC
Content-Type: text/plain;
charset="iso-8859-1"
Karl (and anyone else that hit this problem),
I have created a BMR External Procedure that allows BMR to get around this
issue. I have attached it here. It should work for the restore of a Domain
Controller provided that SYSVOL is kept in the System Drive. If it is not,
just edit this file and change the variable %SystemDrive% to the Drive
letter where SYSVOL is kept (e.g. if SYSVOL is kept in "D:", change the
"%SystemDrive%" to "D:").
Put this file in /var/bmr/epdir on the BMR Main Server, and rename it
appropriately for an External Procedure at the prerestore execution point.
For example, if the BMR client name is "nbuclient,nbuserver", then rename
this file to "nbuclient,nbuserver_prerestore". (See the BMR System Admin
Guide for the details of External Procedures including the naming
convention). Then when you do a prepare to restore of nbuclient,nbuserver
check the "Run External Procedures" checkbox. You will get a message after
the "prepare to restore" operation is complete that this external procedure
will be run.
That's it.
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of
Karl.Rossing AT Federated DOT CA
Sent: Friday, May 28, 2004 3:05 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] BMR 4.7 and NB 5.0MP1 and Win2k DC equals ....
Just a heads up.
I've been fighting with a BMR 4.7 NB 5.0MP1(and GA) issue this week.
It seems that NB 5.0MP1(and GA) are unable to restore the sysvol because it
can't write sub-directories with a . (dot) in them.
Netbackup is scheduled to have this patched in 5.0MP3.
The good news is that's i'm still testing our DR procedure. What's not good
for me is i need to have my project wrapped up.
So people that have a win2k dc, with BMR 4.7 and NB 5.0(and ga) might want
to test their win2kDC restores.
Karl
------_=_NextPart_001_01C448DA.783C09CC
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4937.800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff size=2>Karl
(and anyone else that hit this problem),</FONT></SPAN></DIV>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff size=2>I
have
created a BMR External Procedure that allows BMR to get around this
issue. I have attached it here. It should work for the restore
of a Domain Controller provided that SYSVOL is kept in the System
Drive. If it is not, just edit this file and change the variable
%SystemDrive% to the Drive letter where SYSVOL is kept (e.g. if SYSVOL is kept
in "D:", change the "%SystemDrive%" to "D:").</FONT></SPAN></DIV>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff size=2>Put
this file in /var/bmr/epdir on the BMR Main Server, and rename it appropriately
for an External Procedure at the prerestore execution point. For example, if
the
BMR client name is "nbuclient,nbuserver", then rename this file to
"nbuclient,nbuserver_prerestore". (See the BMR System Admin Guide for the
details of External Procedures including the naming convention).
Then
when you do a prepare to restore of nbuclient,nbuserver check the "Run External
Procedures" checkbox. You will get a message after the "prepare to
restore" operation is complete that this external procedure will be
run.</FONT></SPAN></DIV>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff
size=2>That's
it. </FONT></SPAN></DIV>
<DIV><SPAN class=328051317-02062004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]<B>On Behalf Of
</B>Karl.Rossing AT Federated DOT CA<BR><B>Sent:</B> Friday, May 28, 2004
3:05
PM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B>
[Veritas-bu] BMR 4.7 and NB 5.0MP1 and Win2k DC equals
....<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>Just a heads
up.</FONT> <BR><BR><FONT face=sans-serif size=2>I've been fighting with a BMR
4.7 NB 5.0MP1(and GA) issue this week.</FONT> <BR><BR><FONT face=sans-serif
size=2>It seems that NB 5.0MP1(and GA) are unable to restore the sysvol
because it can't write sub-directories with a . (dot) in them.</FONT>
<BR><BR><FONT face=sans-serif size=2>Netbackup is scheduled to have this
patched in 5.0MP3.</FONT> <BR><BR><FONT face=sans-serif size=2>The good news
is that's i'm still testing our DR procedure. What's not good for me is i
need
to have my project wrapped up.</FONT> <BR><BR><FONT face=sans-serif size=2>So
people that have a win2k dc, with BMR 4.7 and NB 5.0(and ga) might want to
test their win2kDC restores.</FONT> <BR><BR><FONT face=sans-serif
size=2>Karl</FONT></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C448DA.783C09CC--
------_=_NextPart_000_01C448DA.783C09CC
Content-Type: application/octet-stream;
name="my_ADServer_prerestore"
Content-Disposition: attachment;
filename="my_ADServer_prerestore"
cd %SystemDrive%\BMR
echo Change /System_State/SYSVOL/%SystemDrive% to /%SystemDrive% > EPRename.txt
%SystemDrive%\BMR\NBU\bin\bprestore -R %SystemDrive%\BMR\EPRename.txt
System_State:\SYSVOL\*
------_=_NextPart_000_01C448DA.783C09CC--
|
