Video Screencast Help

NetBackup and Oracle RMAN issues

Created: 12 Sep 2011 • Updated: 12 Sep 2011 | 5 comments


We're using NetBackup 6.5 to backup an Oracle 9i database running on Solaris 10 SPARC using the agent and the script.

We've started getting the below errors during the backups:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 09/10/2011 19:28:03
ORA-19502: write error on file "duke_iemm7fmc_1_1_761511628", blockno 61080065 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
   VxBSASendData: Failed with error:
   Server Status:  Communication with the server has not been iniatated or the server status has not been retrieved from the serve

Any ideas on how to troubleshoot this error?


Comments 5 CommentsJump to latest comment

Marianne's picture

" Communication with the server has not been iniatated "

Verify comms between client and master.

Client needs to connect to bprd (via vnetd) on master. Check port connectivity (vnetd: 13724) between client and master and double-check hostname lookup. You need to ensure that master can resolve client's incoming IP address to hostname that matches client name in policy. Add hosts entries on master if DNS is problematic.

For further troubleshooting, ensure that you have the following log folders:

On master: bprd.  Restart NBU after creating the folder.
On client: bpcd and dbclient. Remember to chmod 777 dbclient.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Dipendra Singh's picture

Has the linking of RMAN with netbackup done(oracle_link ).......... this might cause the communication issue.

aab159's picture

It ended up being an issue with bad tapes.    Thanks for everyone's help.

Will Restore's picture

but I don't see that error being caused by bad tapes.  Something else was corrected too?

Will Restore -- where there is a Will there is a way