doesn't start the job.
The job is enabled and idle.
The odd thing is that if the job is disabled, then it starts but quickly stops with a warning saying the job is disabled.
The command above works fine on a regular backup job.
Is there a setting or something in my copy jobs that prevents powershell from starting them?
The backup copy job is continuous job, which means it's always running. If you want to execute Sync now option, then, use Sync-VBRBackupCopyJob. Thanks!
The description for Start-VBRJob is a little misleading then:
Start-VBRJob
Short Description
Starts backup, replication or copy job.
Even the first example includes a copy job:
Example 1
This command starts the jobs named "WebApplications Server Backup" and "Fileserver Copy Job". The job is obtained with Get-VBRJob and piped down.
Get-VBRJob -Name "WebApplications Server Backup", "Fileserver Copy Job" | Start-VBRJob
Start-VBRJob can be used to with backup copy job, but only to start active full backup via -FullBackup switch. Otherwise, you will need to utilize Sync-VBRBackupCopyJob cmdlet.
As to the examples given, Fileserver Copy Job refers to File Copy Job, not Backup Copy one.