Endpoint Backup v2 1.15.0 release notes

New features

Backup health visibility

You can now see what happened during each backup instead of only whether or not it succeeded.
Each recovery point lists the files that were protected, the files that reported errors, and the reason for each error.
Export the file and error lists to review coverage, confirm that critical data is protected, and act on the files that need attention.
For more detail, read: Asset details: Recovery points

Enhancements

Image resize

Backups no longer stop when a protected Windows NTFS volume grows beyond its original size.
The agent detects the new disk capacity and reports it, and the backup target expands to match without manual intervention.
A periodic capacity check catches growth before it causes an out-of-space failure, and out of space conditions are now recognized consistently across file systems.
For more detail, read: Disk space requirements

Cancel restore

You can now cancel a restore that is already running.
Cancellation reaches both the agent and the storage service, stops the transfer, and reports the final state back to the portal so the task no longer shows as active.
This lets you free up the asset and start a corrected restore right away.
For more detail, read: Recovery operations: Cancel

macOS agent now excludes remote files

The macOS agent now excludes cloud storage folders by default, including Dropbox, Google Drive, and OneDrive.
Backups no longer stall while trying to read files that live in another provider's cloud, and protected data stays limited to what is actually stored on the device.
For more detail, read: Default exclusions on macOS

Fixes

• The macOS agent no longer hangs when it reaches log directories created by MalwareBytes.
  Backups on affected machines run to completion and report an accurate status instead of stalling.
  For more detail, read: Troubleshooting the macOS agent
• macOS assets now register under their configured computer name.
  Assets no longer appear in the portal with a generic name, so you can match each backup to the right machine.
  For more detail, read: Asset details: Asset information
• The macOS agent now ignores read only file systems, including those on dual boot machines.
  Backups skip volumes that cannot be protected instead of failing.
  For more detail, read: macOS agent: Limitations
• Retention now removes assets that have retention settings but no stored backups.
  These records no longer linger in the system or count toward reported storage.
  For more detail, read: Understanding retention
• Organizations whose email domain produced an invalid subdomain now provision correctly.
  Account creation no longer fails for these tenants, and their assets appear in the portal as expected.
  For more detail, read: Setting up your organization
• Stalled restores are now detected instead of holding their resources for days.
  Real progress, rather than a fixed timer, keeps a restore alive, so a stalled task expires and you can start a new one.
  For more detail, read: Recovery operations: Columns
• Retention no longer deletes a recovery point that an active restore is reading.
  In progress restores keep access to their source data until they finish.
  For more detail, read: Retention and active restores
• Small files that do not carry the system attribute now back up and restore as regular files.
  They are no longer converted into sockets, so restored data matches the source.
  For more detail, read: Informational messages
• The portal no longer accepts include and exclude selections that conflict with each other.
  Invalid combinations are rejected while you edit the policy, which prevents saving a backup policy that cannot run.
  For more detail, read: Selective backup: Exclusion takes precedence
• Backups recover from a corrupted volume tree stamp.
  Affected assets resume protection without a manual reset.
  For more detail, read: Working with backup errors
• A backup no longer hangs when the server still holds a lock from the previous backup of the same asset.
  Finalizing a backup now blocks new backup requests until the image closes, which clears the gateway timeout and lease errors that left backups stuck in progress.
  For more detail, read: Working with backup errors
• Every restore now resumes from the point where it stopped after the agent restarts.
  The resume point is stored on the device now, so the rare cases where the resume restarted from the beginning no longer happen.
  For more detail, read: Recovery operations: Columns
• Backups no longer fail on files that carry an unsupported access control list revision.
  The agent drops the unsupported entry and continues, so the backup completes rather than stopping with an extended attribute error.
  For more detail, read: Informational messages
• Backups recover when volume metadata is missing on the server.
  The service recreates the metadata file instead of failing on every attempt, which clears backups that were stuck reporting errors.
  For more detail, read: Working with backup errors