NetWorker backup failed,other client can success,why?the log like this

Wow!! This is a first. Please provide some information on the backup and around the failure. You cant simply throw in a piece of un-formatted log and expect us to resolve your issue.

hint: You might be able to get some information for the failure here C:\Program Files\EMC NetWorker\nsr\logs\policy\jhdzx-db07\Workflow1\backup_192474_logs\192500.log

thank you very much

192500.log:

181407:save: Step (1 of 7) for PID-41412: Save has been started on the client 'tjhdzx-db07'.
174412:save: Step (2 of 7) for PID-41412: Running the backup on the client 'tjhdzx-db07' for the save set '/data/public'.
180569:save: Identified a save for the backup with PID-41412 on the client 'tjhdzx-db07'. Updating the total number of steps from 7 to 6.
174920:save: Step (3 of 6) for PID-41412: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '/data/public'.
174908:save:Saving the backup data in the pool 'datadomainlocaldomain'.
175019:save:Received the media management binding information on the host 'win-gk5eesvvbji'.
174910:save:Connected to the nsrmmd process on the host 'win-gk5eesvvbji'.
175295:save: Successfully connected to the Data Domain device.
174922:save: Step (4 of 6) for PID-41412: Successfully connected to the target media device through the nsrmmd process on the host 'win-gk5eesvvbji' for the save set '/data/public'.
174422:save: Step (5 of 6) for PID-41412: Reading the save sets and writing to the target device.
174416:save: Step (6 of 6) for PID-41412: Backup has succeeded. Save is exiting. See the savegrp log to track the closure steps of the backup.
tjhdzx-db07: /data/public level=incr, 1483 MB 00:11:23 12 files
completed savetime=1619529281
94694:save: The backup of save set '/data/public' succeeded.

174416:save: Step (6 of 6) for PID-41412: Backup has succeeded. Save is exiting. See the savegrp log to track the closure steps of the backup.
tjhdzx-db07: /data/public level=incr, 1483 MB 00:11:23 12 files
completed savetime=1619529281
94694:save: The backup of save set '/data/public' succeeded.

So - where is the problem?.

I give up.

Once again, you are hiding valuable information because you obviously do not know NW fundamental issues. This log is useless because you have not used the proper log file 'converter' nsr_render_log which would replace all you tiny variables with true values. Then you should see a more meaningful text which might contain the problem (and indirectly the solution already).

May I suggest that you participate in a basic NW course which will explain NW fundamentals before you look at the problem again.

I'm so sorry. I really a newcomer to networker. I'll learn some NW foundation.

as you indeed haven't rendered the output in human readable format, it is difficult to assess the reason.

however I see mentioned "WARNING indication(s) at completion". You might have set the job to be reported as failed in case a warning occurs? That might for example be when you run into a "file changed during save" situation. So look if that is the case here, which the logs should state (possibly logfile C:\Program Files\EMC NetWorker\nsr\logs\policy\jhdzx-db07\Workflow1\backup_192542_logs\192564.log but that might have already been deleted by now due to default retention for log files being 3 days (72 hours)).

If you don't mind that a file might change during save, then you could alter the job success state, by allowing it to be reported as successful in case of warnings. open files like DB files, should be skipped through a skip directive, either from nw end or on client end (which we do as application teams often create new application filesystem directories automatically while creating the required client end directives right away instead of having to involve us for that. So the filesystem backups would not backup Oracle nor SAP on Oracle directories containing the DB files)

It is the nature of some files that they will change (grow) during the backup - the time at the very beginning when NW builds up the internal worklist until it will actually backup the file. I am surprised that NW will actually set the status to failed - usually it just internally sets an appropriate warning.

How to solve the issue:

  - One method would be to stop the application before and to restart it after the backup.

  - If this is a NW supported database, use the appropriate module that will also ensure that the you have a consistent backup. In this case you have to create 2 client resources for the same host - one to backup the filesystem without the database and the other to only backup the db with the appropriate backup command (the NW server does the same for its internal databases).

  - You can apply the Unix standard directive (see below) for that client to overcome this issue. Do not forget to add the marked statement to the resource for your specific environment.

However, applying 'logasm' does not necessarily mean that the backup (of the database) will be consistent. So be careful.

You will find more details about the NW directives and 'ASMs' in the uasm manpage (command line reference).

As bingo also refers to, to me it seems you are making a backup of the log file of mongodb. I assume you also have something in place to backup the db? For example in its simplest form a dump to disk (preferably triggered by a post command by nw)? Or using the nmda module feature from nw18.1 onwards called application orvhestration protection leveraging nw, nmda and boostfs. There is KB article 000158074 detailing how to do this for postgresql.

For the filesystem backup changed during save failure, look into the backup action options, if memory serves me well. There is an option to set for based on warning or success.