Backup Job Management

Overview

Backup Job Management lets users view the list of backup jobs, create new jobs, update configurations, enable or pause jobs, run jobs manually, delete jobs, and empty the restore points of VMs attached to a job. It also lets you protect data offsite with Backup Copy (Offsite) and track the protection status of your VMs from the Monitoring tab.

Prerequisites

• The tenant has Backup Instance by Veeam service activated.
• The user is logged in to the Unify Portal.
• The user has permissions to operate on backup jobs in the current VPC.
• The VM to back up belongs to the current VPC and is not already attached to another backup job.
• The tenant has sufficient backup quota.

View the backup job list

Purpose

View all backup jobs in the current VPC, check the most recent run status, the last run time, the next scheduled run, the Backup Copy (Offsite) status, and perform quick actions.

Steps

1. Open the Backup Jobs screen on the Unify Portal.
2. Review the displayed list of backup jobs.
3. Use search or filter to find a job by name, Latest Run Status, Schedule Type, or creation time.
4. Move between pages if the list is long.
5. Track job status via the columns in the list.

Main displayed fields

Field	Meaning
Name	Backup job name
Latest Run Status	Current or most recent status of the job
Latest Run	Time of the most recent run (shows Never if the job has not run)
Next Run	Scheduled time of the next run (shows N/A when there is no upcoming run)
Backup Copy (Offsite)	Whether the offsite backup copy is Active or Inactive
Description	Short description of the job
Date Created	Time the job was created
Actions	Actions available based on the job status

Notes

• The list auto-refreshes every few seconds to reflect new status, without losing your current filter, search, or page.
• You can filter by Schedule Type (Daily, Monthly, or Hourly).
• Successfully deleted jobs are not shown in the default list.
• The screen does not display a separate Job Status column.
• Status filtering supports only Latest Run Status.
• The Start action is available only when Latest Run Status is Never started, Success, Fail, or Warning.

Create a backup job

Purpose

Create a backup job to protect one or more VMs in the same VPC, following a user-defined schedule and retention policy.

Steps

1. On the Backup Jobs screen, click Create Backup Job. You can also start from the Backup tab inside a VM's detail page; in that case the VM is pre-selected in Instances.
2. Enter the Job Name.
3. Select VMs in Instances.
4. Choose Notification Recipients from the available recipient list.
5. Enter a Description if needed.
6. Set Keep Backups For and choose the Retention Unit (Days or Restore Points).
7. Set the Backup Schedule to Daily, Monthly, or Hourly, then configure the schedule fields shown for your choice.
8. Enable Backup Copy (Offsite) if you want an offsite copy. This can only be set now — it cannot be changed after the job is created.
9. Review the information and click Create.

Fields

Field	Required	Notes
Job Name	Yes	Up to 50 characters, unique within the VPC. Helper text: Name limits up to 50 characters. They may contain dashes.
Instances	Yes	At least one VM not already in another job. Helper text: An instance can belong to only one backup schedule.
Notification Recipients	Yes	Choose from existing recipients only; free-form emails are not allowed. Use the Create Recipient link to add one in CloudGuard Recipient Management, then return.
Description	No	Up to 100 characters. Helper text: Description limits up to 100 characters. Description can contain alphanumeric characters, dashes, symbols and periods.
Keep Backups For	Yes	Integer 1–1000 (default 7). Interpreted per the Retention Unit.
Retention Unit	Yes	Days or Restore Points.
Backup Schedule	Yes	Daily, Monthly, or Hourly.
Backup Copy (Offsite)	No	Off by default. Can only be set at creation and cannot be changed afterward. See Backup Copy (Offsite) — the 3-2-1 standard.

Daily schedule fields

Field	Required	Notes
Run On	Yes	Every Day, Working Days, or Selected Days (default Every Day).
Selected Days	Conditional	Shown only when Run On is Selected Days; choose at least one weekday.
Start Time	Yes	Time of day in HH:mm.

Monthly schedule fields

Field	Required	Notes
Start Time	Yes	Time of day in HH:mm.
Monthly Schedule Type	Yes	first, second, third, fourth, last, or a specific day (default first).
Day or Date	Yes	A weekday (Monday–Sunday) when a week-of-month type is chosen; a date 1–31 or Last when a specific day is chosen.

Hourly schedule fields

Field	Required	Notes
Run Every	Yes	Interval in hours; allowed values 1, 2, 3, 4, 6, 8, 12, or 24 (default 12).
Allowed Start Window - Start	Yes	First hour the job may start, 0–23 (default 0).
Allowed Start Window - End	Yes	End of the window, 1–24 and greater than Start (default 24; 24 means end of day).

Helper text for the Hourly schedule: The job starts when the allowed window begins, then repeats every X hours within the window.

Result after creation

• The job is created and appears in the Backup Jobs list.
• The job is Active when creation succeeds.
• The job does not run a backup immediately after creation.
• The job runs according to schedule or when the user runs it manually.
• The first backup is a full backup; subsequent backups follow the backup system's incremental mechanism.

Update a backup job

Purpose

Update the configuration of an existing backup job, including job name, description, VM list, retention, schedule, and notification recipients.

Steps

1. Open the Backup Jobs list.
2. Select the job to update.
3. Click Edit.
4. Adjust the fields to change. You can switch the Backup Schedule between Daily, Monthly, and Hourly.
5. Check form validation.
6. Click Save.
7. Wait for the portal to show the result and reload the job data.

Updatable fields

• Job Name
• Description
• Instances
• Retention Unit
• Keep Backups For
• Backup Schedule and its schedule fields
• Notification Recipients

Backup Copy (Offsite) is shown read-only on the Edit form and cannot be changed after the job is created.

Cannot update when

• Latest Run Status is one of Updating, Deleting, Creating, Working, Starting, Disabling schedule, Enabling schedule, or Error.
• The user does not have permission to update the job.
• The update would leave the job with no VMs.

Result after update

• The new configuration takes effect from the next run.
• The job does not run automatically right after an update.
• Previously created restore points are preserved.

Enable or pause a backup job

Purpose

Re-enable a paused job or pause an active job without changing the job configuration.

Disable Backup Job

1. Open the Backup Jobs list.
2. Select an Active job.
3. Click Disable.
4. Confirm in the popup.
5. Wait for the portal to refresh and show the job as Disabled.

Enable Backup Job

1. Open the Backup Jobs list.
2. Select a Disabled job.
3. Click Enable.
4. Wait for the portal to refresh and show the job as Active.

Notes

• Disabling a job stops it from running on schedule until it is re-enabled.
• Disabling a job does not delete restore points, run history, activity log, or job configuration.
• Enabling a job allows it to resume on the current schedule.
• Only Active jobs can be disabled and only Disabled jobs can be enabled.

Run a backup job manually

Purpose

Run a backup job immediately instead of waiting for the next scheduled run.

Steps

1. Open the Backup Jobs list.
2. Find the job to run.
3. Click Start manual in the Actions column.
4. Wait for the portal to refresh the job status.
5. Track the result in the Latest Run Status column or in Job History.

Conditions for a manual run

• Latest Run Status is Never started, Success, Fail, or Warning.
• The user has permission to run a manual backup job.

Result after running

• The job is dispatched to run immediately.
• Latest Run Status may move to Working or Starting, then update to the actual result.
• If a run fails, the system retries automatically up to 2 more times (3 attempts in total) and stops as soon as one attempt succeeds.

Notes

• A manual run does not change the job configuration.
• If the job is already running or in a transitional state, the Start action is disabled or the action is rejected.
• The final result may require auto-refresh or opening Job History to view.

Delete a backup job

Purpose

Delete a backup job when it is no longer needed.

Steps

1. Open the Backup Jobs list.
2. Select the job to delete.
3. Click Delete.
4. Read the confirmation popup carefully.
5. Confirm deletion.
6. The job moves to Deleting status.
7. Wait for the portal to refresh until the job is hidden from the default list, or moves to an error state if deletion fails.

Cannot delete when

• The job is Running.
• The job is Creating.
• The job is Deleting.
• The job is already Deleted.
• The user does not have permission to delete the job.

Result after deletion

• The job is processed for deletion asynchronously.
• During processing, the job shows Deleting status and actions are disabled.
• When deletion succeeds, the job moves to Deleted and is hidden from the default list.
• VMs that belonged to the job are released from the deleted job.
• Related restore points and activity logs are preserved.

Notes

• Deleting a backup job does not delete restore points.
• If the job moves to Delete Failed, check the status or contact support following operational guidance.

Empty Restore Point

Purpose

Delete all restore points of the VMs currently attached to a backup job when the user no longer needs the existing recovery points of that job.

Steps

1. Open the Backup Jobs list.
2. Select the job to operate on.
3. Open the Actions menu.
4. Click Empty Restore Point.
5. Read the confirmation popup carefully.
6. Confirm the action.
7. Wait for the system to process and check the result in Job History or Activity Log.

Deletion scope

• The system deletes only the restore points of VMs currently attached to the job at the time of the action.
• Restore points of VMs previously detached from the job are not deleted.
• Deleting restore points of VMs detached from a job is not supported.

Cannot operate when

• The user does not have permission to empty restore points.
• The job does not exist or does not belong to the current VPC.
• The job has been Deleted.

Result after the action

• Restore points in scope are deleted based on the response from the backup system.
• The backup job still exists.
• Job configuration, schedule, retention, and notification are unchanged.
• The system records entries in Job History and Activity Log.

Scheduled backup jobs

Purpose

Let backup jobs run automatically on the configured schedule without manual action.

How it works

• A job runs automatically only when it is Active.
• The schedule is taken from the job configuration.
• Daily, Monthly, and Hourly schedules are supported.
• When the scheduled time arrives, the system triggers the job automatically.
• If a scheduled run fails, the system retries automatically up to 2 more times (3 attempts in total) and stops as soon as one attempt succeeds.
• Scheduled runs are incremental.

Daily schedule

• Runs every day at the chosen time.
• Can be set to Every Day, Working Days, or specific Selected Days.

Monthly schedule

• Runs based on a monthly rule, for example a specific week of the month or a specific day of the month.
• Start time must always be configured.

Hourly schedule

• Runs several times a day within the Allowed Start Window.
• The job starts at the beginning of the window, then repeats every Run Every hours until the end of the window.
• Hours outside the window do not run.

Notes

• Disabled jobs do not run on schedule.
• Scheduled runs do not change the job configuration.
• Scheduled run results are reflected on the Backup Jobs list, Job History, and related reports.

warning

Backup quota is shared across the entire tenant. When the tenant's backup storage usage reaches or exceeds its quota, the system automatically disables scheduled backup jobs across all VPCs in the tenant until quota is freed or raised. When a VPC's service is pending reclamation, scheduled jobs of that VPC are also disabled until reclamation completes. The portal shows a banner in these cases.

Backup Monitoring

Purpose

Track the backup-protection status of the VMs in the current VPC from a single Monitoring tab, so you can spot VMs that are unprotected or at risk.

Open the Monitoring tab

1. Open Backup Management.
2. Select the Monitoring tab.

The tab requires the backup monitoring permission. Without it, the tab is hidden or a No Permission page is shown. Data is always limited to the current VPC.

Summary cards

Card	Meaning
Total Instances	Number of VMs in the current VPC
Protected Instances	VMs with at least one valid restore point and a healthy job
Unprotected Instances	VMs not attached to any backup job
Pending Protection	VMs in a healthy job but with no valid restore point yet
At-risk Instances	VMs whose protection is not assured

Protection statuses

Status	Meaning
Protected	The VM has at least one valid restore point and its current job is healthy (not disabled, latest run did not fail).
Unprotected	The VM is not assigned to any backup job.
Pending Protection	The VM is in a backup job but currently has no valid restore point (never had one, or it expired past retention).
At Risk	The VM has backup configured but protection is not assured.

At-risk VMs show a risk reason: Latest Backup Failed (the latest run failed) or Backup Job Disabled (the related job is disabled).

Lists

• Unprotected and Pending Protection — columns: Instance Name, Project/Tenant, Power Status, Created At, Protection Status, Reason.
• At-risk Instances — columns: Instance Name, Project/Tenant, Backup Job, Latest Backup, Latest Restore Point, Risk Reason.

Notes

• VMs in Instant Recovery state are excluded until they are successfully migrated.
• If backup data has not synced yet, the tab shows the last synced data and may display Unknown for missing fields.

Monitoring quick actions

From the Monitoring tab you can act on an Unprotected VM directly. Quick actions appear only for VMs whose status is Unprotected.

Create a backup job for the VM

1. On an Unprotected VM, choose the action to create a backup job.
2. The Create Backup Job form opens with the VM pre-selected in Instances.
3. Configure the job as described in Create a backup job and click Create.

This action requires the create-job permission.

Add the VM to an existing backup job

1. On an Unprotected VM, choose the action to add it to an existing backup job.
2. The portal shows the eligible backup jobs in the current VPC, each with its name, Latest Run Status, and current VM count.
3. Select a job and confirm.
4. The VM is added to the job and the Monitoring tab refreshes.

This action requires the edit-job permission. A job is eligible only if it is in the same VPC, not deleted, not in a transitional or error state, and does not already contain the VM.

Notes

• After a quick action succeeds, the VM moves to Pending Protection until its first successful restore point is created.
• Adding a VM to a job does not trigger an immediate backup run.

Backup Copy (Offsite) — the 3-2-1 standard

What it does

Backup Copy (Offsite) helps a job meet the 3-2-1 backup standard: three copies of the data, on two different locations, with one copy offsite. When it is enabled, each restore point is stored as two copies in two different regions — a primary copy in the job's region plus a replica in the paired region.

How to enable it

Turn on the Backup Copy (Offsite) toggle when you create the backup job. It is off by default.

warning

Backup Copy (Offsite) can only be set when you create the job. It cannot be changed afterward, so decide before creating the job. Enabling it uses additional storage.

Cross-region behavior

• A job in Hà Nội (HN) stores its offsite replica in Hồ Chí Minh (HCM).
• A job in Hồ Chí Minh (HCM) stores its offsite replica in Hà Nội (HN).

Replica creation and synchronization are handled by the infrastructure; no extra action is needed. On restore, the system automatically selects a valid source and falls back to the cross-site replica if the primary copy is unavailable.

note

Deleting a restore point deletes both the primary copy and the offsite replica. Backup Copy (Offsite) protects against infrastructure or disaster risk in one region — it does not protect against accidental deletion.

Common statuses

Status	Meaning for the user
Success	The most recent run succeeded
Fail	The most recent run failed
Warning	The most recent run completed with warnings
Never started	The job has never run
Updating	The job is being updated
Deleting	The job is being deleted
Creating	The job is being created
Working	The job is running or processing
Starting	The job is starting
Disabling schedule	The job is being disabled
Enabling schedule	The job is being enabled
Error	The job is in an error state

Common errors

Situation	Resolution
Cannot see Create, Edit, Delete, or Start buttons	Check action permissions or the current job status
Cannot select a VM	The VM may not belong to the current VPC or may already be in another backup job
Cannot create a job because of missing recipient	Create a recipient in CloudGuard Recipient Management, then return to select it
Cannot start manually	Check whether Latest Run Status is Never started, Success, Fail, or Warning
Cannot delete the job	Check whether the job is running or in a transitional state
Job does not run on schedule	Check whether the job is Disabled, the tenant quota is exceeded, or the schedule is correct