Jee and Ronbenton mention 2 issues that are imporant to me:
- "We manage to get rid of the error using cron. When the RMAN script is
executed by cron on the linux client the error doesn't occur. "
- "The debug log files they have me collecting indicate that it is timing out
connecting to the NSR server for the client file index."
Both statements are connected. A cron job does never run an index backup in the
end. It is logical that if the problem is due to the index backup (or in the
transition phase), you may prevent it just by running client-initiated backups.
We have a similar phenomenon in our NW 7.6.1.6 (with older clients) environment
- i call it a 'sleeping group'. But it is obviously a 'sleeping client'. The
effect shows as follows:
- A group will run until it is almost finished (99%).
- Then no more save sets will become active.
- To proceed, simply restart nsrexeced on (all) the remaining clients.
If you are lucky, the group ends successfully.
Sometimes you can even see an index backup rush through,
- If the group fails, you can still restart it and to almost 100%, it will
end successfully.
Unfortunately, the problem occurs randomly on our 400+ client environment.
The only help EMC provided so far was:
- Activate the NSR_KEEP_ALIVE functionality at the client
- Delete the "nsr peer information" on the server and the client
+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
