Can you clarify, you are killing the savegrp process on the server, but doing nothing on the client, but you are finding the hung processes on the client are still running? Or that you are killing the savegrp process but it still appears to be running in the Networker GUI?
Im taking backup of raw .vmdk file when server is powerd off but as its running long i am killing the savegrp for this .vmdk file but its savesession on NETWORKER SERVER is still running becuase of which this file is locked and im unable to poweron this machine from Vsphere (Networker is on WINDOWS machine and do not show particular savesession hence cannot kill that session also whcih is making this file locked)
Now my wues. is is there any way to kill this savesession in networker (in windows machine )
It sounds as if savegrp stop didn't manage to stop save on ESX. In such case you can kill save process on ESX. But it might be that save is also stuck or something which would explain why savegrp has problems stopping it in first place and why does it take long for you to complete this operation. Why don't you simply do VCB based backup?
DavidHampson-rY
294 Posts
0
August 13th, 2010 06:00
Can you clarify, you are killing the savegrp process on the server, but doing nothing on the client, but you are finding the hung processes on the client are still running? Or that you are killing the savegrp process but it still appears to be running in the Networker GUI?
PS22
5 Posts
0
August 16th, 2010 22:00
David,
Im taking backup of raw .vmdk file when server is powerd off but as its running long i am killing the savegrp for this .vmdk file but its savesession on NETWORKER SERVER is still running becuase of which this file is locked and im unable to poweron this machine from Vsphere (Networker is on WINDOWS machine and do not show particular savesession hence cannot kill that session also whcih is making this file locked)
Now my wues. is is there any way to kill this savesession in networker (in windows machine )
ble1
4 Operator
•
14.4K Posts
0
August 25th, 2010 04:00
It sounds as if savegrp stop didn't manage to stop save on ESX. In such case you can kill save process on ESX. But it might be that save is also stuck or something which would explain why savegrp has problems stopping it in first place and why does it take long for you to complete this operation. Why don't you simply do VCB based backup?