> For the complete documentation index, see [llms.txt](https://helpcenter.xopero.com/xopero-one-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.xopero.com/xopero-one-en/changelog/2024/xopero-one-1.8.0.md).

# Xopero ONE 1.8.0

### 🆕 NEW FEATURES

#### <mark style="background-color:blue;">Welcome view</mark>

We have completely redesigned the onboarding process for new users. When logging in for the first time, the user is directed to a new screen that presents all available resources that can be secured with **Xopero**. By default, a new user can connect a service with **Xopero ONE** using a simple three-step process. However, if a **SaaS** organization requires authorization via login, token, or **GitHub App**, the previous advanced mode is still available.

#### <mark style="background-color:blue;">Context menu</mark>

The upper blue bar (which contains the context menu for the currently visible subpage) has also been updated. It now allows **quick configuration of a new backup plan** and **adding new services to protect**. The language setting has been moved to the **User actions**, and an easy option to upgrade or purchase licenses is now available.

#### <mark style="background-color:blue;">Default backup plan</mark>

To enhance the security of user data, **encryption is now enabled by default for every new backup plan**. A default encryption key is generated for this purpose, which can be viewed only once at the time of creation.

#### <mark style="background-color:blue;">Backup plan configuration</mark>

For each supported ecosystem and service, **Xopero ONE** offers a dedicated type of backup plan. Starting from version 1.8.0, users can choose between backup plans for physical devices, **VMware**, or **Hyper-V**, as well as **SaaS** services such as **Microsoft 365**, **GitHub**, **Bitbucket**, **GitLab**, and **Jira**. Each plan can then be configured according to the security policies of the organization.

***

### 🔨 IMPROVEMENTS

#### <mark style="background-color:blue;">Performance improvements and SaaS service autoscaling</mark>

With this release, we address issues related to insufficient **RAM** allocation. When there is not enough **RAM** to perform an operation, the service will automatically request additional resources. In the initial phase, this mechanism operates in manual mode: the service sends the request automatically, but the resources are assigned **only after user approval**. Additionally, we have introduced optimizations that improve the release of used **RAM**, reducing overall consumption. This enhancement benefits not only **SaaS** users but also on-premise and **Xopero Unified Protection** users.

#### <mark style="background-color:blue;">Time zone support in backup plans</mark>

**Xopero ONE** users can now set the time zone within the backup plan schedule, ensuring that all future tasks are launched according to the selected time zone. This improvement eliminates the need to manually adjust the time zone during winter or summer time changes.

#### <mark style="background-color:blue;">Deduplicated data restore</mark>

In this release, we have improved the process of restoring deduplicated data from cloud storages. Restoring **file-level** and **Microsoft 365** backup copies will now be significantly faster.

#### <mark style="background-color:blue;">Symbolic links improvements</mark>

We have improved handling of symbolic links by adding a setting that allows users to choose whether:

1. The agent should follow symbolic links, backing up the files and directories they point to.
2. The agent should not follow symbolic links, backing up only the link itself without its content.

#### <mark style="background-color:blue;">Preserving agent configuration during updates</mark>

The **config.json** file in the **agent** installation directory allows users to store additional configuration settings. Previously, this file was overwritten during each update, requiring users to re-enter their configuration changes. Starting with this release, changes in the **config.json** file **will be preserved during updates**.

#### <mark style="background-color:blue;">SLA reports available through Slack notifications</mark>&#x20;

**Xopero ONE** now offers a new type of **Slack** notification: **the SLA report is ready for download**.

#### <mark style="background-color:blue;">System password excluded (hidden) from Password Manager</mark>

Starting from version 1.8.0, all system passwords are hidden and no longer visible in the app UI. This proactive measure prevents users from deleting or modifying system passwords.

***

### 🐛 BUGFIXES

#### <mark style="background-color:blue;">Improved data storage management</mark>

For user-created data storages, the correct **default worker** for browsing the storage is now **automatically selected**, but can be manually changed in the settings (changing the **worker** in settings now works correctly).

Additionally, an error notification is displayed if a user attempts to browse a storage using a **worker** they do not have access to. Previously, the absence of such a notification could mislead users into thinking the storage was empty.

#### <mark style="background-color:blue;">Instant restore from cloud storages</mark>

We have improved the performance of **Hyper-V** virtual machines running in **instant restore mode** from **cloud storages** by implementing a new cache.

#### <mark style="background-color:blue;">Hyper-V host included in the SLA section (main dashboard)</mark>

The **Hyper-V** license also allows creating copies **directly from the host where virtual machines are running** (users can back up files as well as disk images). Previously, tasks completed by this type of host were not reflected in the **SLA** section of the dashboard.

#### <mark style="background-color:blue;">Machine restore with a # character in a disk name</mark>

Previously, if a **Hyper-V** virtual machine disk name contained a **#** character, the backup plan would fail, and the data could not be restored. This bug has been fixed in this release.

#### <mark style="background-color:blue;">Default backup plan with several data stores</mark>

Previously, if a user had added multiple storages to the service and then added **Hyper-V**, it was impossible to run the default **Hyper-V** backup plan. This issue has been resolved: the user now selects the storage where the backup copies should be saved. Before the default plan starts, the plan editing screen is displayed at the storage selection stage.

#### <mark style="background-color:blue;">UX/UI improvements</mark>

We have revised how backup plan details are displayed in the **VM** dashboard and improved the process of adding a **Hyper-V** cluster.

#### <mark style="background-color:blue;">Copy of a 5.0 machine</mark>

Previously, **Hyper-V** virtual machines with a 5.0 configuration would fail during backup. Starting from version 1.8.0, 5.0 configuration is supported, allowing these machines to be backed up correctly.

#### <mark style="background-color:blue;">Restoring Microsoft 365 backup data to PST</mark>

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

#### <mark style="background-color:blue;">VM list sync issue with VMware datastore clusters</mark>

We have fixed an issue with **VM** list synchronization that occurred after combining **VMware** datastores into a cluster.

***

<p align="center"><a href="https://xopero.com/product-changelogs">ALL XOPERO ONE SOFTWARE RELEASES</a></p>