Hi There,
I have a nas job that runs every 15 minutes, the copy is allowed to run at all times.
Once a day the customers writes a little more than the copy job can copy before the backup has to start again.
So it stops the copy job, and it gets failed status.
It seems like it is "working as designed" since the copy job is stopped with this message:
Failed to process NAS backup copy task Error: Stopped by job 'Backup job name' (NasBackup)
But did anyone find a method to prevent this ?
-
Henrik.Grevelund
- Service Provider
- Posts: 195
- Liked: 34 times
- Joined: Feb 13, 2017 2:56 pm
- Full Name: Henrik Grevelund
- Contact:
Copy jobs gets stopped by backup job
Have nice day,
Henrik
Henrik
-
RubinCompServ
- Service Provider
- Posts: 439
- Liked: 154 times
- Joined: Mar 16, 2015 4:00 pm
- Full Name: David Rubin
- Contact:
Re: Copy jobs gets stopped by backup job
It seems like you might be able to write a Job script that will check to see if the Copy job is running, and then stop the backup job. Something like this:
Code: Select all
$CopyJob = Get-VBRJob -Name <COPY_JOB>
if ($CopyJob.IsRunning) {
$ScriptPID = Get-WMIObject win32_process | Where-Object {$_.ProcessID -eq $PID}
$ParentProc = Get-WMIObject win32_process | Where-Object {$_.ProcessID -eq $ScriptPID.ParentProcessId}
$JobID = $ParentProc.CommandLine.Split()[7].Trim('"')
$BackupJob = Get-VBRJob | Where-Object {$_.id -eq $JobID}
Stop-VBRJob -Job $BackupJob
}
Who is online
Users browsing this forum: No registered users and 4 guests