{"id":2956,"date":"2011-03-17T06:25:59","date_gmt":"2011-03-16T20:25:59","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=2956"},"modified":"2018-12-11T18:16:39","modified_gmt":"2018-12-11T08:16:39","slug":"killing-scheduled-cloning-operations","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2011\/03\/17\/killing-scheduled-cloning-operations\/","title":{"rendered":"Killing scheduled cloning operations"},"content":{"rendered":"

In a previous blog post, I discussed how much I liked the scheduled cloning operations introduced in NetWorker 7.6 SP1. Since then, I’ve had several people comment on it saying that while they’re able to manually start scheduled cloning operations, they’re not able to stop<\/em> scheduled cloning operations in NMC \u2013 regardless of whether they were manually or automatically started.<\/p>\n

Now I thought I’d been able to manually stop a scheduled cloning operation via NMC during beta testing, but I may have confused myself with something else, and when I noticed the same issue, it led me to think \u2013 can I stop this some other way, maybe from the command line? (For what it’s worth, the inability to stop a scheduled clone from NMC is a known issue, and there’s an EMC request running for it.)<\/p>\n

It turns out without NMC, the command line is how you stop a scheduled cloning operation. It actually turned out to be fairly simple in the end. To do so, you use jobquery<\/em> and jobkill<\/em>.<\/p>\n

First, use jobquery to identify the scheduled clone job you want:<\/p>\n

# jobquery<\/strong>\njobquery> show name:; job id:; job state:\n<\/strong>jobquery> print type: clone job; job state: SESSION ACTIVE:\n<\/strong>                      job id: 64002;\n                   job state: SESSION ACTIVE;\n                        name: clone.linux clones;<\/pre>\n
Once you’ve got that job ID, all you have to do is quit jobquery, and run:<\/p>\n
# jobkill -j jobID<\/em><\/strong><\/pre>\n
In this case – it would be:<\/p>\n
# jobkill -j 64002\n<\/strong>Terminating job 64002<\/pre>\n
That’s it \u2013 that’s how you stop a scheduled clone job.<\/p>\n","protected":false},"excerpt":{"rendered":"
In a previous blog post, I discussed how much I liked the scheduled cloning operations introduced in NetWorker 7.6 SP1.…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[6,16],"tags":[226,510,511,865,866],"class_list":["post-2956","post","type-post","status-publish","format-standard","hentry","category-basics","category-networker","tag-clone","tag-jobkill","tag-jobquery","tag-scheduled-clone","tag-scheduled-cloning"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t