How to cancel a large number of Queued Jobs (179794)

You notice a large number of queued jobs on your core, possibly due to replication having to catch up after a base image on a protected server. You realize that this may have serious consequences. For instance, even if you are using the rollup method described in KB#137049 (https://support.quest.com/appassure/kb/137049), the rollups still do not run, as the queued jobs block them. You are able to cancel queued jobs manually but they are too many and new jobs are added constantly to the queue. Moreover, you note that although you may attempt to cancel jobs pertaining to a protected server using the stop-activejobs AppAssure PowerShell commandlet, some machines have both active and queued jobs and canceling the active jobs together with the queued jobs would set you back even more. You are looking for a method to cancel the queued jobs for the duration of the increased core activity.

This script is provided "as is" for the purpose of illustrating how AppAssure tasks may be performed in conjunction with Powershell. AppAssure shall not be liable for any direct, indirect, incidental, consequential, or other damage alleged in connection with the furnishing or use of this script or of the principles it demonstrates.

A powershell script designed to cancel only queued jobs has been prepared. The script may be run in an infinite loop and stopped by hitting ctrl-c or one an one time basis. By default, the script runs just once. However, using the -donotstop parameter runs the cancelling job in an infinite loop. Each loop is repeated after a pause of 3 minutes. This is necessary for new jobs to become active if available slots are present. This option is especially necessary when the core is overwhelmed by the number of queued jobs.

The script code is shown below between horizontal lines and attached to this KB.

_____________________________________________

 <# 

.Synopsis 

 Cancel queued jobs

.Description

 Queued jobs may be canceled using this script. The script runs either on a one time basis or in an infinite loop. If this is the case it may be stopped by hitting ctrl-c

.Parameter donotstop

 enables the infinite loop

.Example 

.\cancelqueuedjobs

.Example

.\cancelqueuedjobs -donotstop

#>

 param([switch]$donotstop)

 cls

 $starttime = get-date

 $duration=$null

 $i=$null

 for(;;){

 $ajobs = get-activejobs -all | where {$_.status -eq "Queued"}

 $x=$ajobs.count

 if($x -le 0){$x = $null}

 if($i){$duration = "(running for $((New-TimeSpan -start $starttime -end (get-date)).ToString().substring(0,11)))"}

 Write-Host "`nCancelling $x Queued Jobs Loop $i $duration" -ForegroundColor Green

 $i++

 foreach ($ajob in $ajobs){

 $protectedserver = $ajob.summary

 $jobid = $ajob.Id

 Write-Host "Cancelling queued job: $protectedserver" -f Yellow

 Invoke-RestMethod -Uri "https://$($env:computername):8006/apprecovery/api/core/jobmgr/jobs/$jobId" -Method DELETE -UseDefaultCredentials

 }

 if(!($donotstop)){

 break

 }

 start-sleep 180

 }

_____________________________________________