<FONT face=3D"Default Sans Serif, Verdana, Arial, Helvetica, sans-serif" si=
ze=3D2><DIV><FONT face=3D"Courier New">hi Ian !</FONT></DIV><DIV><FONT face=
=3D"Courier New"></FONT> </DIV><DIV><FONT face=3D"Courier New">last we=
ek i have the same problem, no schedule running after upgrade, and no statu=
s at all, the same problem if i am doing manual backup.</FONT></DIV><=
DIV><FONT face=3D"Courier New"></FONT> </DIV><DIV><FONT face=3D"Courie=
r New">i trying to run manual backup from client, and found the error statu=
s is </FONT><FONT face=3DVerdana>status 25 not from activity monitor b=
ut from backup progress at jbpSA</FONT></DIV><DIV> </DIV><DIV>after ch=
eck the log daemon i am found "nbpem process terminating" but, finally the =
error came from the </DIV><DIV> </DIV><DIV>/etc/hosts </DIV><DIV> =
;</DIV><DIV>the configuration at /etc/hosts must be:</DIV><DIV> </DIV>=
<DIV>10.2.200.321 testupgrade.domain.com =
testupgrade</DIV><DIV> </DIV><DIV>and can not=
be like:</DIV><DIV> </DIV><DIV>10.2.200.321 testupg=
rade</DIV><DIV>127.0.0.1 localho=
st<BR>10.2.200.321 testupgrade &nb=
sp; testupgrade. loghost<BR></DIV=
><DIV> </DIV><DIV>and after change /etc/hosts..the schedule backup and=
manual backup..runing smoothly..</DIV><DIV> </DIV><DIV>after have thi=
s error experienced..the /etc/hosts totally important..if you dont use dns =
server and check for /etc/nsswitch.conf the configuration must be:</DIV><DI=
V> </DIV><DIV>hosts: files dns</DIV><DIV> </DIV><DIV>the format o=
f /etc/hosts must be: </DIV><DIV>10.2.200.321 testupgrade.=
domain.com testupgrade</DIV><DIV>=
</DIV><DIV>i hope this will help!</DIV><DIV> </DIV><DIV>any body=
knows why the /etc/hosts configuration must be :</DIV><DIV> </DIV><DI=
V>10.2.200.321 testupgrade.domain.com &nb=
sp; testupgrade ???</DIV><DIV> </DIV><DIV> </DI=
V><DIV> </DIV><DIV> </DIV><DIV>Best Regards </DIV><DIV> </DI=
V><DIV> </DIV><DIV> </DIV><DIV>Harun Jonatan</DIV><DIV> </DI=
V><DIV>Veritas System Engineer</DIV><DIV> </DIV><DIV> </DIV><DIV>=
</DIV><DIV> </DIV><DIV> </DIV><DIV> </DIV><DIV><FONT f=
ace=3D"Courier New"></FONT> </DIV><DIV><FONT face=3D"Courier New"></FO=
NT> </DIV><DIV><FONT face=3D"Courier New"></FONT> </DIV><DIV><FON=
T face=3D"Courier New"></FONT> </DIV><DIV><FONT face=3D"Courier New"><=
/FONT> </DIV><DIV><FONT face=3D"Courier New">Message: 5<BR>To: <ver=
itas-bu AT mailman.eng.auburn DOT edu><BR>From: Ian.Fehring AT nab.com DOT
au<BR>Date:=
Sat, 13 May 2006 17:36:47 +1000<BR>Subject: [Veritas-bu] nbpem process ter=
minating<BR><BR><BR><BR>Hi,<BR><BR>We have just recently upgraded our Solar=
is master server from NBU 5.1 to<BR>NBU6.0 MP2. Only our Master server has =
been upgraded at this stage. Since<BR>the upgrade, the nbpem process seems =
to die about once a day, causing jobs<BR>to stop getting scheduled.<BR><BR>=
Support have told me that there is a know issue with nbpem when checkpoint<=
BR>restarts are enabled, so I have disabled them all, but the nbpem process=
<BR>still dies for no apparent reason.<BR><BR>The nbpem log does not show a=
ny errors. It appears as though the process<BR>simply dies. Has anyone seen=
this?<BR> &n=
bsp; =
 =
; <BR>Ian Fehring &n=
bsp; =
 =
; <BR>Lead Te=
chnical Specialist, Storage Management &=
nbsp; <BR>Nat=
ional Australia Bank  =
; &nb=
sp; <BR>  =
; &nb=
sp; &=
nbsp; =
<BR>Level 1, 122 Lewis Rd =
 =
; &nb=
sp; <BR>Tel: +61 (0) 3 9886 2367 | Fax: +61 (0) 3 9886 27=
00 | Mob: +61 (0)417 <BR>520 953 &nb=
sp; &=
nbsp; =
<BR>Email: I=
an.Fehring AT nab.com DOT au </FONT></DIV></FONT>=
|