Xopero ONE v1.8.0

🆕 NEW FEATURES

New onboarding experience

Welcome view

We have completely transformed the method of onboarding new users. When logging in for the first time, a user is immediately directed to a new screen presenting all possible resources to secure with Xopero. By default, a new user can connect a service with GitProtect within the literal 3-step process, however, e.g. if the SaaS organization requires authorization using login, token, or GitHub App there is still available a previous advanced mode aside.

Context menu

The upper blue bar, which contains the context menu for the currently visible subpage, has also undergone important changes. Allowing an easy setup of a new backup plan or adding new services to protect. We have also moved the language setting to the User's action and provided an easy way to upgrade or purchase licenses.

Default backup plan

To increase the security of user data, encryption is enabled by default for each new backup plan. For this purpose, a default encryption key is generated, which can be viewed only once at the time of its creation.

Backup plan configuration

For each of the supported ecosystems and services, Xopero ONE Backup and Recovery provides a separate type of backup plan - hence from v.1.8.0 user can choose between physical devices, VMware or Hyper-V backup plan and SaaS e.g. Microsoft 365, or event GitHub, Bitbucket, GitLab, and Jira backup plans - and then configure them according to the security rules of its organization.

🔨 IMPROVEMENTS

Performance improvements and SaaS service autoscaling

With this release, we provide a solution for a not enough allocation of RAMs issues. When there is not enough RAM to perform a operation, the service will automatically receive an increased amount of resources. In the first phase, the mechanism will operate in manual mode, i.e. the service will automatically send the request, but the resource assignment will take place after user approval. Additionally, we have introduced optimizations that will improve the release of used RAM, and thus reduce its consumption, which will positively affect not only SaaS but also on-premise and Xopero Unified Protection users.

Time zone support in backup plans

Xopero ONE users can now set the time zone within the backup plan schedule according to all future tasks will be launched. This improvement eliminates the need for manual time zone change during the winter/summer time switch.

Deduplicated data restore

In this release, we have improved the process of restoring deduplicated data from cloud storage. The data restore process will be significantly faster for the file-level and Microsoft 365 backup copies.

Symbolic links improvements

We have improved the way symbolic links are handled by adding a setting where the user can specify whether:

• the agent should follow symbolic links, which means that the file and directories the symlink points to will also be backed up,

• the agent should not follow symbolic links, which means that only the symbolic link will be backed up, not the content it points to.

Preserving agent configuration during upgrades

In the config.json file in the agent installation directory, the user can store an additional configuration. However, during each update, this file was overwritten, forcing users to re-enter configuration changes. From this release changes in the config.json file will be preserved during updates.

SLA reports available through Slack notifications

Xopero ONE provides a new type of Slack notification - the SLA report is ready to download.

System password excluded (hidden) from Password Manager

From v1.8.0 we hide all system passwords and they will not be visible on the App UI. This is a proactive measure so that the user cannot delete or change the system password.

🐛 BUGFIXES

Improved data storage management

For data storages created by the user, the correct default worker for browsing the storage will be selected. The default worker is the one which was used to create the storage, but you can change it in settings. Changing the worker in settings also works properly now.

Another improvement is an error notification if a user was to look through the storage using a worker to which they have no access to. A lack of such a notification could mislead the user into thinking that the storage is empty.

Hyper-V fixes

Instant Restore from cloud storages

We improved the performance of virtual machines running in the Instant Restore mode from cloud storages by implementing a new cache.

Hyper-V host included in the SLA section (main dashboard)

The Hyper-V license also allows for making copies directly from the host on which virtual machines are running. From such a server the user can secure files, as well as disk images. Tasks completed by this kind of host were not considered in the SLA section in the dashboard.

Machine restore with a "#" character in a disk name

Until now, if a virtual machine disk name had a # character, then the backup plan ended with an error, and data could not be restored. The bug has been fixed in this release.

Default backup plan with several data stores

In the case where a user had added multiple storages to the service and then was adding Hyper-V, it was impossible to run the default Hyper-V backup plan. In this scenario, a user should choose the storage on which the backup copies should be saved, and that is how the aforementioned issue has been resolved. Before the default plan is initiated, the plan editing is displayed during the stage of storage selection.

UX/UI improvements

We revised the way backup plan details are presented within the VM dashboard and also improved the process of adding a Hyper-V cluster.

Copy of a machine v5.0

If the virtual machine had a 5.0 configuration, its copy ended with an error. From version 1.8.0 we provide support for this configuration hence the machines can be secured properly.

Restoring Microsoft 365 backup data to PST

Due to a change in the data format returned by the Microsoft 365 service, restoring a copy of a mailbox to the PST format stopped working. The bug has been fixed and restoring the mailbox to the user's computer is possible again.

VM list sync issue with VMware Datastore Clusters

We have fixed a VM list sync issue, which occurred after combining VMware datastores into a cluster.