I am having an odd issue currently with a single client savegroup in a large enviroment. this client is already in a group performing a daily backup and works fine.
it has now been setup as the "VMware VCB Proxy Client", the first test backup went fine but since then the group runs to 100% complete but never goes to "successful" stays at "running", the only way to stop it is to restart the services which is unacceptable in this production environment.
I've set VCB up a few times and not had this issue, also, looking through the daemon logs the savesets are all complete and the postcommand has been run the job just won't complete...
Where do you see it still running - in NMC? Does the session end or is the session also seen (however it would appear still and hold device in "writing, idle status")? What about server - do you see savegrp process? Also check client (proxy) for save process.
the NMC shows the group as 100% complete, all savesets complete but the status is "running", the savegrp and save processes appear to have finished although the user says they have "crashed" but there is no error to back this up. logs for the savegrp show it succeeded and the tape has completed savesets on it.
What NW version is that? Also, does your example also apply to VCB backups? I assume you're with 7.3.x and this is potential jobsdb issue, but I'd like to confirm version first....
I'm a colleague of Viktor. In Nsradmin status is running and all saves (processlists) are done.But until we restart the NetWorker services, group status is running. After restart group status is green (successful).
Version of NetWorker is 7.3.2. Jumbo 1. VCB Module 1.0.0, VCB NetWorker Integration Module 3.0.0. We also tried with VCB 3.0.1 and VCB Integration Module 1.0.2. Problem applies only to VCB Backups, while ordinary backups (Groups) are working properly.
I would suggest to open this with support as it seems to be a bug. I've been just asked same thing by my colleague so it seems to behavior which is "typical" for VCB based backups. Perhaps it is already fixed in latest build or updated VCB script is required - not sure.
Interesting. Perhaps this issue is resolved in EXS 3.0.2 / VCB 1.0.3 which has just been released. Support for NetWorker 7.3.2 Update1 is anounced in these releases from VMware. However, the EMC Software Compatibility guide still has no mention of VCB...
So, my suggestion, run your tests with the VMWare updates unless you wish to await for EMC certification to anounce something.
ble1
6 Operator
•
14354 Posts
•
56186 Points
336
0
Posted March 11th, 2007 15:00