Some thimes your Disk Storage unit is busy in placing the another backup and not able to faciliate your backup then Netbackup gives you below error which is high lighted in RED

If working with heterogeneous operating systems do not forget to make host file entries in client as well as media master servers.
This will be for name resolution

Some people don't like to use host file entires.
But perfer DNS to do the work.
this prevents you from having to edit your host files all the time.
If DNS is setup and working properly you don't need host files.

But with DNS you do have to make sure the the forward nslookup and reverse come back referencing the same server name.

So if using DNS
nslookup <servername>
do this twice to see that you get the same responce
nslookup <ipaddress>
do this twice to see you get the same response.

Does the same name come back for both.  If the server has a alias have it set up as a ture alias and not a second DNS entry.

How HOSTS file playing a role in Netbackup !

https://www-secure.symantec.com/connect/articles/h...

Good  initiative zahid

Hi Zahid

really gud for those peoples who are new in this field  like me .

plz be continue.

:)

This utility is a great source for looking over your environment, from a number of commands output.

The nbsu utility is an internally developed Symantec utility for troubleshooting NetBackup (tm) problems.

I have used it several times to see if servers configured correctly.
Particularly handy, if you are taking ownership of NetBackup servers that someone else installed/configured.

DOCUMENTATION: What is the nbsupport utility and where can it be found? (Note: With more current versions of NetBackup the nbsupport utility is replaced by NBSU.)
http://seer.entsupport.symantec.com/docs/264785.htm

DOCUMENTATION AND DOWNLOAD: NetBackup Support Utility (NBSU) Usage and Examples for 6.x. NBSU was released with 6.5, 6.0 MP6, and 5.1 MP7, and replaces what is known as "nbsupport" in previous versions.
http://seer.entsupport.symantec.com/docs/323434.htm

Thanks all of you guys to motivate me on this.......:)...but we need to do more on this:)....tc

https://www-secure.symantec.com/connect/blogs/active-directory-backup-not-start-backing

restore failed to recover the requested files(5)

Restore failed

6/8/2009 5:29:28 PM - begin Restore
6/8/2009 5:29:34 PM - restoring image dbcluster_1244419813
6/8/2009 5:29:35 PM - requesting resource Fibre Transport
6/8/2009 5:29:35 PM - Warning nbjm(pid=2524) NBU status: 800, EMM status: Fibre Transport resources are not available
6/8/2009 5:29:35 PM - Warning nbjm(pid=2524) NBU status: 800, EMM status: Fibre Transport resources are not available
6/8/2009 5:35:39 PM - Error bpbrm(pid=4916) listen for client protocol error - couldn't accept from data socket, The operation completed successfully. (0)
6/8/2009 5:35:44 PM - Error bpbrm(pid=4916) client restore EXIT STATUS 25: cannot connect on socket
6/8/2009 5:37:38 PM - restored image dbcluster_1244419813 - (cannot connect on socket(25)); restore time 00:08:04
6/8/2009 5:37:43 PM - end Restore; elapsed time: 00:08:15
the restore failed to recover the requested files(5)

kindly look the below link where how i resolved it
https://www-secure.symantec.com/connect/forums/restore-failed-recover-requested-files5#comment-2549061

OR see my Blog

https://www-secure.symantec.com/connect/blogs/ms-sql-failed-restore-backup-status-code-5

http://www.unixforum.info/forum/unix-storage/netbackup%27s-status-codes/

Let help to World :)
Zahid Haseeb

Raghuraam

In windows you can face issues with ghost devices - old devices which does not exist but their entries are still there in device manager causing muliple paths to the same device.

Below mentioned link will brief you regarding the same.

http://seer.entsupport.symantec.com/docs/259595.htm

If a NetBackup Client on Windows Server you are most likely to see Error entries on server startup Event Viewer logs relating to the PBX service.

So heres another good tip, for Clients only

PBX only needs to run if the Windows client is also a SAN client, or if the client is also a NOM server or VBR server. Otherwise, the Service can be disabled.

DOCUMENTATION: Does Private Branch Exchange (PBX) need to be enabled on all NetBackup 6.5.x Windows clients
http://seer.entsupport.symantec.com/docs/306419.htm
Notes for Private Branch Exchange (PBX)
http://seer.entsupport.symantec.com/docs/306215.htm

This is another good one to note when implementing a new media server to disable the Removable Storage service.

This service will interfere with VERITAS NetBackup (tm) and cause various issues with tape drives and tape libraries. Tape drives can go down and there maybe issues when incorrect tapes are loaded into the tape drives.

In particular SAN media servers:

3rd PARTY: Removable Storage Service set to Manual or Automatic and running.
http://seer.entsupport.symantec.com/docs/274991.htm

I experienced this recently, and took a couple of hours to track down.

I don't see the value in having all this dissassociated information in one post.
A person needs to scroll through a lot of information that may have nothing to do with their problem.
If you provide a user with a link to this thread it may just confuse them more.
Pwerhaps it would be better to do this in a blog and with several different posts.
A blog for network connectivity issues
A blog for database problems.
A blog for resolving slow backups and restores
A blog for catalog issues
etc.......

This forum post seems more like a catch-all and will quickly be too large to be of much use.