Failing save set 'NetWorker Module for Databases and Applications'

You have to give us the details written in the client properties field of "Savesets" and "Application information".

"It fails" ... is not really a useful description - i am sure you would not have opened this thread if the backup would have run successfully. So any more details about the error itself could be helpful as well, like

  - the exact error message

  - a potential message code

  - the client configuration

just to name some of them.

Don't you think this is worth to start with rather than generating tons of info using debug mode (most customers use level 9) and search for the needle in the haystack?

We use DPA to report on our backups, within the DPA report for failed save sets, it has multiple entries for the Save Set name 'NetWorker Module for Databases and Applications' if I look through the daemon log on the backup server, it does not show me any failures.  When I look at the mminfo for the client, the savesets for that backup are all successful, our DBAs have confirmed that the database backups are all good as well, they are not seeing any failures or errors.  After continuing to dig through everything yesterday, it appears that this saveset 'failure' may be related to a connection timeout on our backup server - we are looking at all of our TCP/IP settings on the server to see if we have something set up incorrectly.  We did turn NSR debug on last night on a couple of the RMAN backups that we have consistently seen this with last night, and no error messages were created - thus leading me to believe that it is not any type of an actual failure within the backup.

There is no actual error message, the error code is 0, our clients are running Solaris 8 with Oracle 10G.  Our Networker server is also Solaris 8

Sorry for this being so vague, I am having trouble actually finding out any information on what this 'save set' is or what specifically is happening to be able to provide any good information.  This is the main reason that I asked if anyone had seen this before, just trying to get a direction to look to help determine what it is.

Thanks for your assistance.

I have tested DPA (4.8.1? with NW 7.6.4) as well last year and i also got failed save sets reported which actually did not exist. So i am not surprised. Finally we refused to implement DPA and this was one of the major reasons. For the statistics mminfo, along with some scripting, is capable to do the job as well.

Glad to hear someone else ran into this with DPA - we are running 5.8.3 so it obviously still has the same thing going on.  Appreciate your input.  Thanks again!

lynn.specht@gwl.com wrote: We are running Networker 7.6.5.3 and NMDA 1.2.  I noticed last week, that after our people added a new Oracle server in for RMAN backups, there is a save set named "Networker Module for Databases and Applications' that is failing every time an RMAN backup runs from that server.  I am thinking there is a parameter or something that is not set correctly, but so far have had no luck determining what I need to change or correct to solve this issue. Has anyone else seen this before and can you provide any direction?  I had our DBA's turn on debugging on a couple of their RMAN backups for tonight to see if it will provide any additional information. Thank you!

Adding new Oracle backup and then having one failing sounds like - lack of license.

However, to really check what is going, you need to check logs.  You can't check logs with DPA as DPA will tell you if something has failed or not, but not why.  As to why, you as backup admin, need to check logs on server and client along with configuration parameters to make sure that all is in place (obviously, something is not).

Hello,

Did You able to find a solution to the problem? I have the same message in DPA 5.8.4 & NetWorker 8.0.1.3 (NMDA 1.5.0.0):

Save set: NetWorker Module for Databases and Applications

Status: failed

Error Code: 0

Regards,

Aigar

NMDA 1.5 is not GA yet and I believe it plays more friendly with NW8.1.