| Title: | NetWorker |
| Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
| Moderator: | DECWET::RANDALL .com::lenox |
| Created: | Thu Oct 10 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 750 |
| Total number of notes: | 3361 |
dunix 3.2c nsr 4.2b 2100 with tz877
Customer runs a script to shutdown Oracle database and start 4 savegrp
commands. Script is initiated from Platinum AutoSys scheduler.
Worked OK with NSR 3.2. Customer just upgraded to NSR 4.2b and now the
savegrp command hangs. ps shows savegrp commands but no nsrd daemons
are started.
Any ideas on how to troubleshoot this one? I will ask for the output
from ps ax when the savegrp command in hanging.
The script runs OK manually or from crontab.
Thanks in advance for any ideas.
Gene
NSR Support
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 434.1 | DECWET::ONO | Software doesn't break-it comes broken | Fri Feb 21 1997 11:42 | 15 | |
Why does the customer use four savegrp commands? Starting a bunch of savegrps at the same time is asking for trouble. If they're doing it to backup four filesystems simultaneously, then they should: - Define four client resources with one filesystem in the saveset field of each resource - Assign all four clients to the same group - launch one savegrp command I'd like to see their nsr.res and daemon.log files. If they're big, mail them to me. Wes | |||||
| 434.2 | Works OK without verbose | ALFSS2::ZURIK_E | Tue Mar 04 1997 10:53 | 26 | |
I have some additional infomation from the customer.
He is only starting one savegroup.
dunix 3.2c nsr 4.2b 2100 with tz877
Customer runs a script to shutdown Oracle database and starts a
savegrp command. Script is initiated from Platinum AutoSys scheduler.
Worked OK with NSR 3.2. Customer just upgraded to NSR 4.2b and now
the savegrp command hangs.
Customer discovered that the problem only occurs when doing
savegrp -v groupname. Without the -v the command works OK.
The script runs OK manually or from crontab with the -v.
Customer claims verbose gave more infomation in v3.2.
I closed the call with the customer since he doesn't really need the
verbose output. I'm posting this note in case someone else has a
similar problem.
Gene
Nsr Support
| |||||