Jobs
Use jobs to define what an agent backs up, where it writes, and when it runs.
Creating a job
The create dialog has two steps. Select an agent, enter a job name, and provide the source path and destination restic repository URL. An SFTP destination reveals an optional SSH port; an empty port uses 22. Select an interval or a custom cron schedule.
After saving, the second step shows the setup command. Run it once on the agent machine:
sudo vecta-agent setup <JOB_ID>
Replace <JOB_ID> with the ID supplied by the dashboard. The command stores destination credentials locally and initializes the repository when needed. No destination credentials are entered in the dashboard.
Schedules
| Choice | Meaning |
|---|---|
| Every 6 hours | The default interval. |
| Every 12 hours | Runs twice per day. |
| Every day at 03:00 UTC | Runs daily at 03:00 UTC. |
| Weekly on Sunday at 02:00 UTC | Runs weekly at 02:00 UTC. |
| Custom cron | A validated five-field UTC cron expression. |
Warning
All cron times are UTC. Convert your local time before saving a schedule. The control plane decides when a job is due, and the agent starts it at a check-in within about two minutes of that time.
An interval and a cron schedule are mutually exclusive. If a cron expression is present, it takes precedence. A schedule edit applies on the next check-in.
Statuses and badges
| Status or badge | Meaning |
|---|---|
pending |
Never run, or flagged but not yet picked up. |
running |
Backup in progress; the row shows reported progress. |
success |
Last run completed and created a snapshot. |
failed |
Last run errored, was stopped, or timed out. |
warning |
A snapshot was created after zero files were processed. Check the source path. |
stalled |
A running job has reported no progress for many hours. |
force-run |
The job is flagged for the next check-in, even when disabled. |
Controlling runs
Run now flags the job; it does not execute immediately. It works for disabled jobs, which receive the force-run badge. Stop requests termination from a running agent, and the run becomes failed with a cancellation message. Mark as failed immediately closes a run in the dashboard and also requests a stop; use it when the agent cannot be reached or Stop is not enough.
Editing a job
You can edit the name, source, destination, SSH port, schedule, and enabled state. Disabling prevents scheduled runs, but does not prevent a force-run.
Warning
Changing the destination changes the credential key. Credentials for the old destination do not apply to the new one. Run sudo vecta-agent setup <JOB_ID> again on the agent before the next backup.
Deleting a job
Warning
Deleting a job permanently removes its run history and snapshot-ID records. Backed-up data remains in the repository, but Vecta can no longer locate those snapshots for you. Use Restoring Data for the from-scratch path.
Failure emails
Note
A failed job sends one email to the account owner from noreply@notifications.vectaapp.com. It includes the job name, server name, and the agent's error-message tail. Safelist that sender if needed. Vecta does not send success or warning emails.
What's next
See Destinations for repository URLs and credentials, or Job lifecycle & statuses for state transitions.