Incremental schedule runs base (full) backup task

Details

When the following conditions are met, the first incremental backup schedule does not run after changing the settings. 
Reconcile task does not run either.
After running the base (full) backup, incremental backup schedule will run.

Common with agent-based/agentless backup
- When no backup image file exist in the backup destination, the first incremental schedule runs to create full backup. The subsequent backups run according to the schedules.

Agent-based
- Deduplication Compression level or Compression level is changed or or vice versa (This applies only when the setting can be changed in a previous version. The setting cannot be edited in the current version.）
- Upgrading from ActiveImage Protector 2.x to ActiveImage Protector 3.x.
- Upgrading from ActiveImage Protector 3.0/3.1 to ActiveImage Protector 3.5.
- Upgrading from the earlier version of ActiveImage Protector 3.5 to the new version of ActiveImage Protector 3.5.
- Upgrading from the versions of ActiveImage Protector 2018 to ActiveImage Protector 2022 or later.
- Upgrading ActiveImage Protector updates the image format (please refer to the Related Articles below).
- Backup source is changed.
- Resizing (enlarge or reduce the size) the backup source disk or volume.
- Restarting Linux OS (specifications of Linux Edition)
 

Agentless (HyperBack)
- Upgrading from ActiveImage Protector 2018 to ActiveImage Protector 2022 or later.
- Changing backup source (Ex: In case that a guest has multiple selected disks and some of the disks are not connected properly for any reason. (In that case, the first backup after recovery will also be a full backup.)
- If the backup source is a dynamically expanding VHD/VHDX or a thin-provisioned VMDK, and the disk size is increased or decreased (regardless of any changes to the volume size within the disk).
- Upgrading ActiveImage Protector updates the image format (please refer to the Related Articles below).
- When RCT is enabled for a Hyper-V guest, files named .mrt and .rct exist in the same folder as the virtual disk. When the guest is powered off, these files can be manually deleted. However, the subsequent incremental backup cannot be created and the incremental chain fails in Error -603 until the next full backup is created. If you encounter this issue, please manually run a full backup or wait until the next full backup schedule.

* Reconcile feature was first implemented in ActiveImage Protector 3.1 Windows Edition. However, the tracking method for incremental changes was changed from Tracking Driver mode to CBC mode from ActiveImage Protector 2018 Update 7 or later, and the Reconcile feature was discontinued.
* From ActiveImage Protector Windows Edition version 7.0.0.8643, Tracking Driver mode or CBC mode is selectable for the change tracking method. Reconcile is available when Tracking Driver mode is enabled.
* Deduplication Compression feature was first implemented with ActiveImage Protector 3.5.

Related Articles
Backup image file format compatibility
https://actiphyhelp.zendesk.com/hc/en-us/articles/13451355905433
Agentless backup using Resilient Change Tracking (RCT)
https://actiphyhelp.zendesk.com/hc/en-us/articles/31274272565017
Creating multiple schedules and editing a schedule
https://actiphyhelp.zendesk.com/hc/en-us/articles/35762969730201

13451074847001