[Veritas-bu] Novell (5.1) Alternate Path Restore Problem for 4.5_FP3

2003-07-25 10:42:13
Subject: [Veritas-bu] Novell (5.1) Alternate Path Restore Problem for 4.5_FP3
From: Ronald.Nicely AT ncmail DOT net (Ronald Nicely)
Date: Fri, 25 Jul 2003 10:42:13 -0400
To whom it may concern:

Novell Client Problem:

NWTWAN411 is a Novell client (v 5.1) that was being backed up and 
restored.  We noticed the following problem:

I am trying to do an alternate path restore to a Novell box without any
luck.  I am using the Java interface.  When doing a normal restore I
have no problems, but when I try to do an alternate path restore I have
Novell Client: NWTWAN411  target: SYS
source path in gui: \sys\sys\veritas\nbuclnt\netback\bp.ini
AltPath1: \sys\sys\veritas\nbuclnt\netback\restored\bp.ini
AltPath2: \sys\veritas\nbuclnt\netback\restored\bp.ini
AltPath3: \sys\sys\veritas\nbuclnt\netback\bp.ini.restored
Master : scc086
Media Server: NDITSMEDIA01
I get the following with all alternate path restores:
07/14/2003 17:33:32 - begin restore operation
07/14/2003 17:48:38 - media needed: 000078
07/14/2003 17:48:39 - restore from image NWTWAN411_1057948522
07/14/2003 17:50:01 - Error bpbrm (pid=2280) timed out connecting to scc086
07/14/2003 17:49:41 - restored from image NWTWAN411_1057948522; restore 
time: 0:01:02
07/14/2003 17:50:02 - Error bpbrm (pid=2280) cannot put rename file on 
07/14/2003 17:49:42 - Warning bprd (pid=3069) Restore must be resumed 
prior to first image expiration on Mon 11 Aug 2003 02:35:22 PM EDT
07/14/2003 17:49:43 - end restore operation; operation time 0:16:11
07/14/2003 17:50:08 - Error bpbrm (pid=2280) client restore EXIT STATUS 
54: timed out connecting to client the restore failed to recover the 
requested files (5)
The knowledge base gives two results from "cannot put rename file":
242848 and 245324
The altpath directory is there from 245324 and bpclntcmd from media 
server suceeds for both bpclntcmd -hn and bpclntcmd -ip.
Do I have to do the restores from the client in order for this to work?
If so, why - it is not optimal here for security reasons.

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