03-17-2011 01:04 PM
Hi,
On firing the restore of client cdclnq94, I am getting the following log:
Mar 17, 2011 8:52:41 AM - begin Restore
Mar 17, 2011 8:52:44 AM - number of images required: 1
Mar 17, 2011 8:52:44 AM - media needed: FP1162
Mar 17, 2011 8:57:49 AM - restoring from image cdclnq94_1299790868
Mar 17, 2011 8:57:53 AM - connecting
Mar 17, 2011 8:57:55 AM - Error bpbrm (pid=25866) Couldn't open /usr/openv/netbackup/.rename.25866 on client cdclnq94, status: 13
Mar 17, 2011 8:57:56 AM - Error bpbrm (pid=25866) cannot put rename file on cdclnq94
Mar 17, 2011 8:57:55 AM - requesting resource FP1162
Mar 17, 2011 8:57:56 AM - granted resource FP1162
Mar 17, 2011 8:57:56 AM - granted resource Dup-IBM-1-2-5
Mar 17, 2011 9:59:49 AM - Warning bprd (pid=8686) Restore must be resumed prior to first image expiration on Thu Mar 24 17:01:08 2011
Mar 17, 2011 9:59:50 AM - end Restore; elapsed time 1:07:09
cannot connect on socket (25)
Though I'm able to ping telnet the client from the master server...Backups running fine.Only thing is I'm facing problem in this critical restore.
Would appreciate help on this.
Solved! Go to Solution.
03-18-2011 12:17 AM
Yeah....I have found out the solution to the problem. All the logs were there and also the permissions.
The problem was McAfee was scanning the Netbackup directories which prevented logs from getting created and also the /.rename file required for the restore.
I unblocked the NBU files from getting scanned and then the restore ran fine and ultimately got completed.
Thanks all for your invaluable responses.
03-17-2011 01:14 PM
The fact that it seems to break after 1 hour between your log entries makes me suspect some network timeout or firewall involvement. What's between these machines, networkwise? What timeouts might be set to 3600 seconds?
03-17-2011 01:17 PM
CAUSE:
Communication issue with host during restore only. Backups were running fine
SOLUTION:
Within the Admin Console > Host Properties > Master > Client Attributes > Client > Browse and Restore Ability > Allow Both
03-17-2011 01:18 PM
Please share the following:
NBU version on master, media server and client
OS on master and client cdclnq94.
If Client OS is Windows, please ensure that the following directory exists on the client: <install_path>\VERITAS\NetBackup\logs\AltPath.
Also create tar log directory on client under logs for further troubleshooting.
03-17-2011 01:46 PM
NBU Master, Media and Client - All have 6.5.6
Master is solaris 9 and Client is Windows. The path \logs\AltPath is already there....though i'm not able to generate logs at client.
03-17-2011 01:55 PM
Well there are no firewalls between master and the client, nor in the path of media server.
The timeouts setting for client is the default one:
Client Read timeout: 300 secs
File Browse timeout: 300 secs
03-17-2011 10:13 PM
"i'm not able to generate logs at client."
Please verify permissions on the logs folder. User account starting NetBackup Client Service must be able to write logs.
I just had another look at your opening post - we see a 'connecting', never 'connected'
Mar 17, 2011 8:57:53 AM - connecting
Mar 17, 2011 8:57:55 AM - Error bpbrm (pid=25866) Couldn't open /usr/openv/netbackup/.rename.25866 on client cdclnq94, status: 13
Please ensure bpcd log dir exists on the client, then run the following test on the master and media server:
bptestbpcd -verbose -client cdclnq94
Please post output as well as client's bpcd log.
03-18-2011 12:17 AM
Yeah....I have found out the solution to the problem. All the logs were there and also the permissions.
The problem was McAfee was scanning the Netbackup directories which prevented logs from getting created and also the /.rename file required for the restore.
I unblocked the NBU files from getting scanned and then the restore ran fine and ultimately got completed.
Thanks all for your invaluable responses.
03-18-2011 01:04 AM
Thanks for the feedback - this will help someone else down the line having the same problem.
I have marked your post as Solution.
03-18-2011 06:19 AM
We have seen some quirks with antivirus but this is the first I've heard of trouble creating log files.