Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cannot determine the status of the backup process 1

Status
Not open for further replies.

olympe69

Technical User
Dec 14, 2005
11
FR
hi

we have this messages sometimes on servers client
and the save is bad.

the next save are ok without doing something specially.

This error is referenced by networker but when we look
the solution for this pb, nothing is wrong.

An idea ?? thanks

we have 10 servers networker on 7.2 windows 2003 with this
error.

We have 6 servers networker on 6.4 windows nt4 without
this pb .
 
- I do not understand what you mean by "pb".
- NW 6.4 does not exist. I assume it is NW 6.1.4
- What is the exact problem? - Can you provide an example?
 
excuse me but in french pb =problem

exactly not 6.4 but 6.1.4


this message occurs sometimes when save are finished.
Is referenced in the legato guide error, but the solution
is no good for us.

already servers clients impacted are lotus,ged,unix.
the next day save are good .......????????????????

 
Well, move the problematic clients to a separate group and start their group manually from the command line... adding more "-v"s for addinitial information.
 
when we do the command manually after problem,is already ok.

THis problem comes monday but thursday ....thurday.....already saves are ok !!!!

we have 10 sites with this problem since 10 month and no one
can help us .....
 
What do you expect? - The behavior ist strange. However, how can somebody help with the only statement "my saves are bad" ?
 
what are you expecting ?

people just say to us that the problem is a network problem.
we are sure that is not the case.

this is the solution of legato :


Cannot determine status of the backup process. Use
mminfo to determine job status.
Type
Fatal Error
Source
savegrp, save
Description
The backup of the specified save set might be complete. There has not been any
status reported from the client-side program. This problem might occur when:
• The network connection between the client and server was lost during
the backup session.
• The disk on which the client status is logged is full. By default, the client
status is maintained in the following directory:
UNIX: /nsr/logs
Windows: %SystemDrive%\Program Files\Legato\nsr\logs
NetWare: SYS:\NSR\logs
• The NetWorker Module binaries are not installed on the database server.
Resolution
Complete one or more of the following tasks to resolve this error:
• Use mminfo -v -c client_name -t time to determine whether the save set was
backed up successfully. The mminfo report shows completion status in
the Flags column. An “a” flag means the backup was aborted.
• Use ping to verify that the network protocols are functioning properly.
• Determine whether the drive containing the log file is full. To do this:
UNIX: Run df /nsr/tmp.
Windows: Right-click the drive where the NetWorker software is installed
and select Properties.
• Verify that all relevant NetWorker Module binaries are installed on the
 
The proposal from the knowledgebase is just one thing. But the minimum information from the server and/or client is what you will see in the logs.
 
How can you be sure that you don't have any network problem?
How often do you check the connection between client and server?
This message can be caused by external reasons, for example ftp transfer, 100% CPU, memory swap, etc...
I suggest you to monitor the clients, check system logs when the problem occurs.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top