Troubleshooting Cloning – Part 2 – Clone Wars

The clone wars continue. As you may recall from the Part 1, my NetWorker optimized clones have been hanging with this misleading error:

Waiting for 1 Writable volume on backup pool ‘Device’ disk(s) on nsr_server

To further complicate things, control over the clone from the console can be limited. I had been using the jobkill utility. Preston has a great write up on it here. The issue is that after killing the clone, the NMC console shows it as running still? Attempts to restart the clone via NMC resulted in the following error:

1 1429638078 event task manager Task aborted: task ‘clone.name Clone’ is already running

So is the job kill, really murdering all the required processes? Lets take a look.

My new env is Windows. So lets visit our old friend the task manager, here we want to look for nsrtask and nsrclone processes. First nsrclone. I’ve had to obfuscate the output, but what I found were the appropriate running clones. The specific job I needed to restart was not listed.

 

nsrclone

The same cannot be said for the clone jobs associated nsrtask process. There was indeed a process still hanging around.

nsrtask

After killing it, the state in NMC changed from Running to Interrupted. I could then restart the job.

interuppted

 

 

All this just to get my clone going again. This is some progress as I had previously been restarting NetWorker, interrupting the service and other running clones.

Category: backup recovery, Cloning, NetWorker |

no comments

Comments are closed.