Could be number of things. Does this happen every time? Does it fail at savefs or save level? If save level I would suggest to run save in debug mode and inspect where it fails. Does this happen during full as well or just incremental backups? While "hung" appears, can you run RPC queries from the backup server against the client (rpcinfo -t client_name 390113)? Do you use 7.2.1 on clients as well? Do you see anything in logs on client side? Does the client side initiated backup work? (so, many questions and things to try out to get better picture of what is even an issue there).
the backup works fine only just after the client reboot, but after a while backup hungs again. And a new reboot is required.
Sound like some kind of "release" is required. If you setup the perfmon to monitor memory, CPU, disk and network (where first is what I would suspect the most) check something doesn't get released.
during the backup the output of the command rpcinfo -t client_name 390113 "program 390113 version 1 ready and waiting"
Is this during the hung backup? Because it means we can communicate without any problem with nsrexecd on the client. This indicates that probably an issue is isolated to the client itself.
No logs on client side.
Even in event log?
When this hungs, if you stop the group and you go to client do you see save still running? Now, if you try to kill the save via task manager is that possible? If not, can you just retart services? (so we are not doing a reboot now).
Hi, I have a simmilar problem. Is yours using somekind of script? My process hungs when trying to backup a dump from SQL. Has anyone encountered something like that? I'm using 7.3 on the client side.
ble1
4 Operator
•
14.4K Posts
0
February 22nd, 2006 03:00
DavidHampson
2 Intern
•
1.1K Posts
0
February 22nd, 2006 07:00
ble1
4 Operator
•
14.4K Posts
0
February 22nd, 2006 08:00
reboot, but after a while backup hungs again. And a
new reboot is required.
Sound like some kind of "release" is required. If you setup the perfmon to monitor memory, CPU, disk and network (where first is what I would suspect the most) check something doesn't get released.
rpcinfo -t client_name 390113
"program 390113 version 1 ready and waiting"
Is this during the hung backup? Because it means we can communicate without any problem with nsrexecd on the client. This indicates that probably an issue is isolated to the client itself.
Even in event log?
When this hungs, if you stop the group and you go to client do you see save still running? Now, if you try to kill the save via task manager is that possible? If not, can you just retart services? (so we are not doing a reboot now).
mmiglioranzi
19 Posts
0
February 22nd, 2006 08:00
This condition happens both for the full and incremental backup, and even for manual backup from client.
during the backup the output of the command
rpcinfo -t client_name 390113
is
"program 390113 version 1 ready and waiting"
On the client is installed the NetWokrer 7.2.1
No logs on client side.
dbagley1
8 Posts
0
May 4th, 2006 09:00
http://forums.emc.com/forums/thread.jspa?threadID=35519&tstart=0
JAUG1
1 Message
0
January 28th, 2008 12:00
I have a simmilar problem. Is yours using somekind of script?
My process hungs when trying to backup a dump from SQL.
Has anyone encountered something like that? I'm using 7.3 on the client side.
ble1
4 Operator
•
14.4K Posts
0
January 28th, 2008 13:00