acronis.

com

Cyber Protection
24.03

User Guide REVISION: 4/2/2024

Table of contents
Getting started with Cyber Protection 19
Activating the account 19
Password requirements 19
Two-factor authentication 19
Privacy settings 21
Accessing the Cyber Protection service 22
Software requirements 23
Supported web browsers 23
Supported operating systems and environments 23
Supported Microsoft SQL Server versions 29
Supported Microsoft Exchange Server versions 29
Supported Microsoft SharePoint versions 30
Supported Oracle Database versions 30
Supported SAP HANA versions 30
Supported MySQL versions 30
Supported MariaDB versions 31
Supported virtualization platforms 31
Compatibility with encryption software 40
Compatibility with Dell EMC Data Domain storages 42
Supported protection features by operating system 43
Supported operating systems and versions 43
Supported file systems 51
Supported operations with logical volumes 54
Backup 54
Recovery 55
Installing and deploying Cyber Protection agents 56
Preparation 56
Step 1 56
Step 2 56
Step 3 56
Step 4 56
Step 5 57
Step 6 58
Which agent do I need? 58
Agent-based and agentless backup 62

2 © Acronis International GmbH, 2003-2024

 Which backup type do I need? 62
System requirements for agents 63
Linux packages 65
Are the required packages already installed? 66
Installing the packages from the repository 67
Installing the packages manually 68
Configuring proxy server settings 69
Installing protection agents 73
Downloading protection agents 73
Installing protection agents in Windows 73
Installing protection agents in Linux 75
Installing protection agents in macOS 78
Granting the required system permissions to the Connect Agent 79
Changing the logon account on Windows machines 80
Dynamic installation and uninstallation of components 82
Unattended installation or uninstallation 82
Unattended installation or uninstallation in Windows 82
Examples 83
Example 85
Examples 85
Examples 93
Example 94
Examples 94
Unattended installation or uninstallation in Linux 100
Unattended installation and uninstallation in macOS 106
Registering and unregistering workloads manually 115
Passwords with special characters or blank spaces 119
Changing the registration of a workload 120
Autodiscovery of machines 120
Prerequisites 121
How autodiscovery works 121
How remote installation of agents works 123
Performing autodiscovery and manual discovery 123
Managing discovered machines 129
Troubleshooting 129
Deploying Agent for VMware (Virtual Appliance) 131
Before you start 131

3 © Acronis International GmbH, 2003-2024

 Deploying the OVF template 131
Configuring the virtual appliance 132
Deploying Agent for Scale Computing HC3 (Virtual Appliance) 135
Before you start 135
Deploying the QCOW2 template 136
Configuring the virtual appliance 136
Agent for Scale Computing HC3 – required roles 139
Deploying Agent for Virtuozzo Hybrid Infrastructure (Virtual Appliance) 140
Before you start 140
Configuring networks in Virtuozzo Hybrid Infrastructure 141
Configuring user accounts in Virtuozzo Hybrid Infrastructure 141
Deploying the QCOW2 template 144
Configuring the virtual appliance 144
Deploying Agent for oVirt (Virtual Appliance) 148
Before you start 148
Deploying the OVA template 149
Configuring the virtual appliance 150
Agent for oVirt – required roles and ports 153
Deploying Agent for Synology 153
Before you start 153
Downloading the setup program 155
Installing Agent for Synology 155
Updating Agent for Synology 159
Deploying agents through Group Policy 162
Prerequisites 162
Generating a registration token 162
Creating the transform file and extracting the installation packages 165
Setting up the Group Policy object 166
SSH connections to a virtual appliance 167
Starting the Secure Shell daemon 167
Setting the root password on a virtual appliance 167
Accessing a virtual appliance via an SSH client 168
Updating agents 168
Updating agents manually 169
Updating agents automatically 171
Updating agents on BitLocker-protected workloads 173
Preventing unauthorized uninstallation or modification of agents 173

4 © Acronis International GmbH, 2003-2024

 Uninstalling agents 174
Protection settings 176
Automatic updates for components 176
Updating the Cyber Protection definitions by schedule 177
Updating the Cyber Protection definitions on-demand 177
Cache storage 177
Changing the service quota of machines 178
Cyber Protection services installed in your environment 179
Services installed in Windows 179
Services installed in macOS 180
Saving an agent log file 180
Site-to-site Open VPN - Additional information 180
License management for on-premises management servers 187
Defining how and what to protect 188
The Management tab 188
Plan statuses 188
Protection plans 189
Backup plans for cloud applications 189
Backup scanning plans 189
Off-host data processing 190
VM heartbeat 198
Screenshot validation 198
Intermediate snapshots 205
Protection plans and modules 205
Creating a protection plan 206
Actions with protection plans 207
Resolving plan conflicts 211
Default protection plans 212
Individual protection plans for hosting control panel integrations 218
#CyberFit Score for machines 218
How it works 219
Running a #CyberFit Score scan 223
Cyber Scripting 225
Prerequisites 225
Limitations 225
Supported platforms 225
User roles and Cyber Scripting rights 226

5 © Acronis International GmbH, 2003-2024

 Scripts 228
Script repository 237
Scripting plans 237
Script quick run 246
Protection of collaboration and communication applications 247
Understanding your current level of protection 248
Monitoring 248
The Overview dashboard 248
The Activities dashboard 249
The Alerts dashboard 250
Alert types 251
Alert widgets 269
Cyber Protection 270
Protection status 270
Endpoint Detection and Response (EDR) widgets 271
#CyberFit Score by machine 275
Disk health monitoring 276
Data protection map 280
Vulnerability assessment widgets 281
Patch installation widgets 282
Backup scanning details 284
Recently affected 284
Cloud applications 285
Software inventory widgets 286
Hardware inventory widgets 287
Remote sessions widget 288
Smart protection 288
The Activities tab 295
Cyber Protect Monitor 296
Configuring proxy server settings in Cyber Protect Monitor 297
Reports 298
Actions with reports 299
Reported data according to widget type 301
Managing workloads in the Cyber Protect console 304
The Cyber Protect console 304
What's new in the Cyber Protect console 305
Using the Cyber Protect console as a partner administrator 306

6 © Acronis International GmbH, 2003-2024

 Prerequisites 309
Workloads 314
Adding workloads to the Cyber Protect console 315
Removing workloads from the Cyber Protect console 320
Device groups 324
Built-in groups and custom groups 324
Static groups and dynamic groups 325
Cloud-to-cloud groups and non-cloud-to-cloud groups 325
Creating a static group 326
Adding workloads to a static group 327
Creating a dynamic group 328
Editing a dynamic group 344
Deleting a group 345
Applying a plan to a group 345
Revoking a plan from a group 346
Working with the Device control module 347
Using device control 349
Access settings 356
Device types allowlist 361
USB devices allowlist 362
Excluding processes from access control 366
Device control alerts 368
Wiping data from a managed workload 371
Viewing workloads managed by RMM integrations 372
CyberApp workloads 373
Aggregated workloads 373
Working with CyberApp workloads 374
Working with aggregated workloads 374
Linking workloads to specific users 375
Find the last logged in user 376
Managing the backup and recovery of workloads and files 378
Backup 378
Protection plan cheat sheet 380
Selecting data to back up 382
Selecting entire machine 382
Selecting disks or volumes 383
Selecting files or folders 386

7 © Acronis International GmbH, 2003-2024

 Selecting system state 388
Selecting ESXi configuration 388
Continuous data protection (CDP) 389
How it works 390
Supported data sources 391
Supported destinations 392
Configuring a CDP backup 392
Selecting a destination 393
Advanced storage option 394
About Secure Zone 395
Backup schedule 398
Backup schemes 398
Backup types 400
Running a backup on a schedule 400
Running a backup manually 413
Retention rules 414
Important tips 415
Retention rules according to the backup scheme 415
Configuring retention rules 418
Replication 419
Usage examples 419
Supported locations 419
Encryption 420
Configuring encryption in the protection plan 421
Configuring encryption as a machine property 421
Notarization 423
How to use notarization 424
How it works 424
Default backup options 424
Backup options 425
Availability of the backup options 425
Alerts 427
Backup consolidation 428
Backup file name 428
Backup format 433
Backup validation 434
Changed block tracking (CBT) 435

8 © Acronis International GmbH, 2003-2024

 Cluster backup mode 435
Compression level 436
Error handling 437
Fast incremental/differential backup 438
File filters (Inclusions/Exclusions) 438
File-level backup snapshot 440
Forensic data 441
Log truncation 449
LVM snapshotting 450
Mount points 450
Multi-volume snapshot 451
One-click recovery 451
Performance and backup window 456
Physical Data Shipping 460
Pre/Post commands 461
Pre/Post data capture commands 463
Scheduling 466
Sector-by-sector backup 466
Splitting 467
Task failure handling 467
Task start conditions 468
Volume Shadow Copy Service (VSS) 468
Volume Shadow Copy Service (VSS) for virtual machines 470
Weekly backup 471
Windows event log 472
Recovery 472
Recovery cheat sheet 472
Safe recovery 474
Recovering a machine 475
Prepare drivers 484
Check access to the drivers in bootable environment 485
Automatic driver search 485
Mass storage drivers to install anyway 485
Recovering files 487
Recovering system state 493
Recovering ESXi configuration 493
Recovery options 494

9 © Acronis International GmbH, 2003-2024

 Operations with backups 502
The Backup storage tab 502
Mounting volumes from a backup 504
Validating backups 506
Exporting backups 506
Deleting backups 507
Understanding the detection of bottlenecks 509
Backing up workloads to public clouds 513
Defining a backup location in Microsoft Azure 513
Defining a backup location in Amazon S3 515
Defining a backup location in Wasabi 518
Viewing and updating public cloud backup locations 519
Managing public cloud account access 520
Protecting Microsoft applications 536
Protecting Microsoft SQL Server and Microsoft Exchange Server 536
Protecting Microsoft SharePoint 536
Protecting a domain controller 536
Recovering applications 537
Prerequisites 537
Database backup 539
Application-aware backup 545
Mailbox backup 547
Recovering SQL databases 549
Recovering Exchange databases 557
Recovering Exchange mailboxes and mailbox items 559
Changing the SQL Server or Exchange Server access credentials 565
Protecting mobile devices 566
Supported mobile devices 566
What you can back up 566
What you need to know 566
Where to get the Cyber Protect app 567
How to start backing up your data 567
How to recover data to a mobile device 568
How to review data via the Cyber Protect console 568
Protecting Hosted Exchange data 569
What items can be backed up? 569
What items can be recovered? 570

10 © Acronis International GmbH, 2003-2024

 Selecting Exchange Online mailboxes 570
Recovering mailboxes and mailbox items 571
Protecting Microsoft 365 data 573
Why back up Microsoft 365 data? 573
Cloud agent and local agent 573
Required user rights 576
Limitations 577
Microsoft 365 seats licensing report 577
Logging 577
Using the locally installed Agent for Office 365 578
Using the cloud Agent for Microsoft 365 582
Protecting Google Workspace data 613
What does Google Workspace protection mean? 613
Required user rights 613
About the backup schedule 614
Limitations 614
Logging 614
Adding a Google Workspace organization 614
Creating a personal Google Cloud project 615
Discovering Google Workspace resources 619
Setting the frequency of Google Workspace backups 619
Protecting Gmail data 620
Protecting Google Drive files 624
Protecting Shared drive files 628
Notarization 631
Search in cloud-to-cloud backups 632
Full-text search 633
Search indexes 634
Checking the size of a search index 634
Updating, rebuilding, or deleting indexes 634
Enabling enhanced search in encrypted backups 635
Enabling or disabling enhanced search in existing plans 636
Disabling full-text search for Gmail backups 636
Protecting Oracle Database 637
Protecting SAP HANA 637
Protecting MySQL and MariaDB data 637
Configuring an application-aware backup 638

11 © Acronis International GmbH, 2003-2024

 Recovering data from an application-aware backup 639
Protecting websites and hosting servers 643
Protecting websites 643
Protecting web hosting servers 646
Special operations with virtual machines 647
Running a virtual machine from a backup (Instant Restore) 647
Working in VMware vSphere 651
Backing up clustered Hyper-V machines 669
Limiting the total number of simultaneously backed-up virtual machines 670
Machine migration 671
Microsoft Azure and Amazon EC2 virtual machines 675
Creating bootable media to recover operating systems 675
Custom or ready-made bootable media? 676
Linux-based or WinPE/WinRE-based bootable media? 676
Creating physical bootable media 677
Bootable Media Builder 678
Recovery from the cloud storage 681
Recovery from a network share 682
Files of a script 682
Structure of autostart.json 683
Top-level object 683
Variable object 683
Control type 684
Connecting to a machine booted from bootable media 691
Local operations with bootable media 692
Remote operations with bootable media 693
Startup Recovery Manager 696
Implementing disaster recovery 698
About Cyber Disaster Recovery Cloud 698
The key functionality 698
Software requirements 699
Supported operating systems 699
Supported virtualization platforms 699
Limitations 700
Cyber Disaster Recovery Cloud trial version 701
Limitations when using Geo-redundant Cloud Storage 701
Disaster Recovery compatibility with encryption software 702

12 © Acronis International GmbH, 2003-2024

 Compute points 702
Setting up the disaster recovery functionality 703
Create a disaster recovery protection plan 704
Editing the Recovery server default parameters 705
Cloud network infrastructure 706
Setting up connectivity 707
Networking concepts 707
Initial connectivity configuration 718
Prerequisites 720
Network management 726
Prerequisites 741
Setting up recovery servers 742
Creating a recovery server 742
How failover works 745
How failback works 753
Prerequisites 755
Prerequisites 760
Working with encrypted backups 763
Operations with Microsoft Azure virtual machines 764
Setting up primary servers 764
Creating a primary server 764
Operations with a primary server 767
Managing the cloud servers 767
Firewall rules for cloud servers 768
Setting firewall rules for cloud servers 769
Checking the cloud firewall activities 771
Backing up the cloud servers 772
Orchestration (runbooks) 772
Why use runbooks? 773
Creating a runbook 773
Operations with runbooks 776
Configuring your antivirus and antimalware protection 778
Supported platforms 778
Supported features per platform 779
Antivirus and antimalware protection 781
Antimalware features 782
Scanning types 782

13 © Acronis International GmbH, 2003-2024

 Antivirus and antimalware protection settings 783
Active Protection in the Cyber Backup Standard edition 798
Active Protection settings in Cyber Backup Standard 799
URL filtering 805
How it works 806
URL filtering configuration workflow 808
URL filtering settings 808
Description 814
Microsoft Defender Antivirus and Microsoft Security Essentials 814
Schedule scan 815
Default actions 815
Real-time protection 816
Advanced 816
Exclusions 817
Firewall management 817
Quarantine 818
How do files get into the quarantine folder? 818
Managing quarantined files 819
Quarantine location on machines 819
Self-service custom folder on-demand 819
Corporate whitelist 820
Automatic adding to the whitelist 820
Manual adding to the whitelist 820
Adding quarantined files to the whitelist 821
Whitelist settings 821
Viewing details about items in the whitelist 821
Antimalware scan of backups 821
Limitations 822
Working with Advanced protection features 824
Advanced Data Loss Prevention 826
Creating the data flow policy and policy rules 826
Enabling Advanced Data Loss Prevention in protection plans 835
Automated detection of destination 838
Sensitive data definitions 838
Data Loss Prevention events 844
Advanced Data Loss Prevention widgets on the Overview dashboard 845
Custom sensitivity categories 846

14 © Acronis International GmbH, 2003-2024

 Organization map 848
Known issues and limitations 851
Endpoint Detection and Response (EDR) 851
Why you need Endpoint Detection and Response (EDR) 851
Enabling Endpoint Detection and Response (EDR) functionality 854
How to use Endpoint Detection and Response (EDR) 856
Viewing which incidents are currently not mitigated 859
Understanding the scope and impact of incidents 860
How to navigate attack stages 869
Enabling monitoring mode for Endpoint Detection and Response (EDR) 902
How to test if Endpoint Detection and Response (EDR) is working correctly 903
Assessing vulnerabilities and managing patches 905
Vulnerability assessment 905
Supported Microsoft and third-party products 905
Supported Apple and third-party products 907
Supported Linux products 908
Vulnerability assessment settings 908
Vulnerability assessment for Windows machines 910
Vulnerability assessment for Linux machines 911
Vulnerability assessment for macOS devices 911
Managing found vulnerabilities 912
Patch management 913
The patch management workflow 914
Patch management settings in the protection plan 914
Viewing the list of available patches 919
Automatic patch approval 921
Approving patches manually 926
Installing patches on demand 926
Managing your software and hardware inventory 928
Software inventory 928
Enabling the software inventory scanning 928
Running a software inventory scan manually 929
Browsing the software inventory 929
Viewing the software inventory of a single device 931
Hardware inventory 932
Enabling the hardware inventory scanning 932
Running a hardware inventory scan manually 933

15 © Acronis International GmbH, 2003-2024

 Browsing the hardware inventory 933
Viewing the hardware of a single device 936
Connecting to workloads for remote desktop or remote assistance 938
Supported remote desktop and assistance features 939
Supported platforms 942
Remote connection protocols 943
NEAR 943
RDP 944
Apple Screen Sharing 944
Remote sound redirection 944
Connections to remote workloads for remote desktop or remote assistance 945
Remote management plans 946
Creating a remote management plan 946
Adding a workload to a remote management plan 954
Removing workloads from a remote management plan 954
Additional operations with existing remote management plans 955
Compatibility issues with remote management plans 957
Resolving compatibility issues with remote management plans 958
Workload credentials 959
Adding credentials 959
Assigning credentials to a workload 960
Deleting credentials 960
Unassigning credentials from a workload 960
Working with managed workloads 961
Configuring RDP settings 961
Connecting to managed workloads for remote desktop or remote assistance 962
Connecting to a managed workload via a web client 964
Transferring files 965
Performing control actions on managed workloads 966
Monitoring workloads via screenshot transmission 967
Observing multiple managed workloads simultaneously 968
Working with unmanaged workloads 969
Connecting to unmanaged workloads via Acronis Quick Assist 970
Connecting to unmanaged workloads via IP address 970
Transferring files via Acronis Quick Assist 971
Using the toolbar in the Viewer window 972
Recording and playing remote sessions 974

16 © Acronis International GmbH, 2003-2024

 Configuring the Connect Client settings 975
The remote desktop notifiers 976
Monitoring the health and performance of workloads 978
Monitoring plans 978
Monitoring types 978
Anomaly-based monitoring 978
Supported platforms for monitoring 979
Configurable monitors 979
Settings of the Disk space monitor 983
Settings of the CPU temperature monitor 986
Settings of the GPU temperature monitor 987
Settings of the Hardware changes monitor 989
Settings of the CPU usage monitor 989
Settings of the Memory usage monitor 991
Settings of the Disk transfer rate monitor 993
Settings of the Network usage monitor 995
Settings of the CPU usage by process monitor 998
Settings of the Memory usage by process monitor 998
Settings of the Disk transfer rate by process monitor 999
Settings of the Network usage by process monitor 1000
Settings of the Windows service status monitor 1002
Settings of the Process status monitor 1002
Settings of the Installed software monitor 1003
Settings of the Last system restart monitor 1003
Settings of the Windows event log monitor 1004
Settings of the Files and folders size monitor 1005
Settings of the Windows Update status monitor 1006
Settings of the Firewall status monitor 1006
Settings of the Failed logins monitor 1006
Settings of the Antimalware software status monitor 1007
Settings of the AutoRun feature status monitor 1008
Settings of the Custom monitor 1009
Monitoring plans 1010
Creating a monitoring plan 1010
Adding workloads to monitoring plans 1012
Revoking monitoring plans 1013
Configuring automatic response actions 1013

17 © Acronis International GmbH, 2003-2024

 Additional operations with monitoring plans 1015
Compatibility issues with monitoring plans 1018
Resolving compatibility issues with monitoring plans 1018
Resetting the machine learning models 1019
Monitoring alerts 1020
Configuring monitoring alerts 1020
Monitoring alert variables 1021
Manual response actions 1023
Viewing the monitoring alerts for a workload 1026
Viewing the alert log of monitoring alerts 1026
Configuring email notification policies 1027
Viewing monitor data 1028
Monitor widgets 1029
Additional Cyber Protection tools 1031
Compliance mode 1031
Limitations 1031
Unsupported features 1031
Setting the encryption password 1031
Changing the encryption password 1032
Recovering backups for tenants in the Compliance mode 1032
Immutable storage 1033
Immutable storage modes 1033
Supported storages and agents 1033
Enabling immutable storage 1034
Disabling immutable storage 1035
Accessing deleted backups in immutable storage 1035
Geo-redundant storage 1035
Enabling and disabling geo-redundant storage 1036
Geo-replication status 1036
Limitations 1037
Glossary 1038
Index 1042

18 © Acronis International GmbH, 2003-2024

Getting started with Cyber Protection

Activating the account

When an administrator creates an account for you, an email message is sent to your email address.
The message contains the following information:

l Your login. This is the user name that you use to log in. Your login is also shown on the account
activation page.
l Activate account button. Click the button and set the password for your account. Ensure that
your password is at least nine characters long. For more information about the password, refer to
"Password requirements" (p. 19).

If your administrator has enabled two-factor authentication, you will be prompted to set it up for
your account. For more information about it, refer to "Two-factor authentication" (p. 19).

Password requirements
The password for a user account must be at least 9 characters long. Passwords are also checked for
complexity, and fall into one of the following categories:

l Weak
l Medium
l Strong

You cannot save a weak password, even though it might contain 9 characters or more. Passwords
that repeat the user name, the login, the user email, or the name of the tenant to which a user
account belongs are always considered weak. Most common passwords are also considered weak.

To strengthen a password, add more characters to it. Using different types of characters, such as
digits, uppercase and lowercase letters, and special characters, is not mandatory but it results in
stronger passwords that are also shorter.

Two-factor authentication
Two-factor authentication (2FA) provides extra protection from unauthorized access to your
account. When 2FA is set up, you are required to enter your password (the first factor) and a one-
time code (the second factor) to log in to the Cyber Protect console. The one-time code is generated
by a special application that must be installed on your mobile phone or another device that belongs
to you. Even if someone discovers your login and password, they will not be able to log in to your
account without having access to your second-factor device.

To set up two-factor authentication for your account

You must set up 2FA for your account if the administrator has enabled it for your organization. If the
administrator enables 2FA while you are logged in to the Cyber Protect console, you will have to set
it up when your current session expires.

19 © Acronis International GmbH, 2003-2024

Prerequisites

l Two-factor authentication is enabled for your organization by an administrator.

To set up two-factor authentication for your account

1. Install an authenticator app on your mobile device.

Examples of authenticator apps:
l Twilio Authy
l Microsoft Authenticator
l Google Authenticator
2. Scan the QR code using your authenticator app, and then enter the 6-digit code displayed on the
authenticator app in the Set up two-factor authentication window.
3. Click Next.
The instructions on how to restore your access to your account if you lose your 2FA device or
uninstall the authenticator app are displayed.
4. Save or print the PDF file.

Note
Ensure that you save the PDF file in a safe place or print it for further reference. This is the best
way to restore your access.

5. Return to the Cyber Protect console login page and enter the generated code.
A one-time code is valid for 30 seconds. If you wait longer than 30 seconds, use the next
generated code.

Next time you log in, you can select the Trust this browser... check box. In this case, the code will
not be required for subsequent logins by using this browser on this machine.

Note
We recommend that you leave this check box clear. Otherwise, you will lose the access to 2FA for
your account.

To restore two-factor authentication on a new device (2FA)

If you have access to the previously set-up mobile authentication app

1. Install an authenticator app on your new device.

2. Use the PDF file that you saved when you configured 2FA on your device. This file contains the
32-digit code that you must enter in the authenticator app to link the authenticator app to your
Acronis account again.

Important
If the code is not working, ensure that the time in the authenticator mobile app is synced with
your device.

If you did not save the PDF file during the setup:

20 © Acronis International GmbH, 2003-2024

a. Click Reset 2FA, and then enter the one-time password shown in the mobile authenticator app.
b. Follow the on-screen instructions.

If you do not have access to the previously set-up mobile authenticator app

1. Take a new mobile device.

2. Use the stored PDF file to link a new device (default name of the file is cyberprotect-2fa-
backupcode.pdf).
3. Restore access to your account from backup. Ensure that backups are supported by your mobile
app.
4. Open the app under the same account from another mobile device if it is supported by the app.

Privacy settings
Privacy settings help you indicate whether or not you give consent for the collection, use and
disclosure of your personal information.

Depending on the country in which you are using Cyber Protect Cloud and the Cyber Protect Cloud
data center that provides services to you, on the initial launch of Cyber Protect Cloud you may be
asked to confirm whether you agree to use Google Analytics in Cyber Protect Cloud.

Google Analytics helps us better understand user behavior and improve user experience in Cyber
Protect Cloud by collecting pseudonymized data.

If you enabled or refused to enable Google Analytics on the initial launch of Cyber Protect Cloud,
you can change your decision at any time later.

To enable or disable Google Analytics

1. In the Cyber Protect console, click Manage account.

2. Click the account icon in the upper-right corner.
3. Select My privacy settings. The My privacy settings window is displayed.
4. In the Google Analytics data collection section, click one of the following buttons:
l On to enable Google Analytics
l Off to disable Google Analytics

In the How to delete cookies section, you can control and manage cookies directly in your
browser.

Note
If you do not see Google Analytics section, it means that Google Analytics is not used in your
country.

In the In-product onboarding and interactive help section, shown initially during trial period, you
can stop or keep receiving the information about the improvements and new features in the
program in the future. This feature is enabled by default, but you can disable it by switching the
toggle to Off.

21 © Acronis International GmbH, 2003-2024

Accessing the Cyber Protection service
After you activate your account, you can access the Cyber Protection service by logging in to the
Cyber Protect console or via the management portal.

To log in to the Cyber Protect console

1. Go to the Cyber Protection service login page.

2. Type your login, and then click Next.
3. Type your password, and then click Next.
4. [If you use more than one Cyber Protect Cloud service] Click Cyber Protection.
Users who only have access the Cyber Protection service, log in directly to the Cyber Protect
console.
If Cyber Protection is not the only service you have access to, you can switch between the

services by using the icon in the upper-right corner. Administrators can also use this icon
for switching to the management portal.

The timeout period for the Cyber Protect console is 24 hours for active sessions and 1 hour for idle
sessions.

You can change the language of the web interface by clicking the account icon in the upper-right
corner.

To access the Cyber Protect console via the management portal

1. In the management portal, go to Monitoring > Usage.

2. Under Cyber Protect, select Protection, and then click Manage service.
Alternatively, under Clients, select a customer, and then click Manage service.

As a result, you are redirected to the Cyber Protect console.

Important
If the customer is in Self-service management mode, you cannot manage services for him. Only the
customer administrators can change the customer mode to Managed by service provider, and
then manage the services.

To reset your password

1. Go to the Cyber Protection service login page.

2. Type your login, and then click Next.
3. Click Forgot password?
4. Confirm that you want further instructions by clicking Send.
5. Follow the instructions in the email that you have received.
6. Set up your new password.

22 © Acronis International GmbH, 2003-2024

Software requirements

Supported web browsers

The Cyber Protect console uses the TLS 1.2 protocol and supports the following web browsers:

l Google Chrome 29 or later

l Mozilla Firefox 23 or later
l Opera 16 or later
l Microsoft Edge 25 or later
l Safari 8 or later running in the macOS and iOS operating systems

In other web browsers (including Safari browsers running in other operating systems), the user
interface might be displayed incorrectly or some functions may be unavailable.

Supported operating systems and environments

Agent for Windows

This agent includes a component for Antivirus & Antimalware protection and URL Filtering. See
"Supported protection features by operating system" (p. 43) for details about supported
functionality by operating system.

l Windows XP Professional SP1 (x64), SP2 (x64), SP3 (x86)

l Windows Server 2003 SP1/2003 R2 and later – Standard and Enterprise editions (x86, x64)
l Windows Small Business Server 2003/2003 R2
l Windows Server 2008, Windows Server 2008 SP2* – Standard, Enterprise, Datacenter,
Foundation, and Web editions (x86, x64)
l Windows Small Business Server 2008, Windows Small Business Server 2008 SP2*
l Windows 7 – all editions

Note
To use Cyber Protection with Windows 7, you must install the following updates from Microsoft
before installing the protection agent:
o Windows 7 Extended Security Updates (ESU)
o KB4474419
o KB4490628
For more information on the required updates, refer to this knowledge base article.

l Windows Server 2008 R2* – Standard, Enterprise, Datacenter, Foundation, and Web editions
l Windows Home Server 2011*
l Windows MultiPoint Server 2010*/2011*/2012
l Windows Small Business Server 2011* – all editions

23 © Acronis International GmbH, 2003-2024

l Windows 8/8.1 – all editions (x86, x64), except for the Windows RT editions
l Windows Server 2012/2012 R2 – all editions
l Windows Storage Server 2003/2008/2008 R2/2012/2012 R2/2016
l Windows 10 – Home, Pro, Education, Enterprise, IoT Enterprise and LTSC (formerly LTSB) editions
l Windows Server 2016 – all installation options, except for Nano Server
l Windows Server 2019 – all installation options, except for Nano Server
l Windows 11 – all editions
l Windows Server 2022 – all installation options, except for Nano Server

Note
* To use Cyber Protection with this version of Windows, you must install the SHA2 code signing
support update from Microsoft (KB4474419) before installing the protection agent.

For information on issues related to the SHA2 code signing support update, refer to this knowledge
base article.

Agent for SQL, Agent for Active Directory, Agent for Exchange (for database
backup and application-aware backup)
Each of these agents can be installed on a machine running any operating system listed above and a
supported version of the respective application.

Agent for Data Loss Prevention

Device control

l Microsoft Windows 7 Service Pack 1 and later

l Microsoft Windows Server 2008 R2 and later
l macOS 10.15 (Catalina)
l macOS 11.2.3 (Big Sur)
l macOS 12 (Monterey)
l macOS 13 (Ventura)

Note
Agent for Data Loss Prevention for macOS supports only x64 processors. Apple silicon ARM-based
processors are not supported.

Data loss prevention

l Microsoft Windows 7 Service Pack 1 and later

l Microsoft Windows Server 2008 R2 and later

24 © Acronis International GmbH, 2003-2024

Note
Agent for Data Loss Prevention might be installed on unsupported macOS systems because it is an
integral part of Agent for Mac. In this case, the Cyber Protect console will indicate that Agent for
Data Loss Prevention is installed on the computer, but the device control and data loss prevention
functionality will not work. Device control functionality will only work on macOS systems that are
supported by Agent for Data Loss Prevention.

Agent for Advanced Data Loss Prevention

l Microsoft Windows 7 Service Pack 1 and later
l Microsoft Windows Server 2008 R2 and later

Agent for File Sync & Share

For the list of supported operating systems, refer to the Cyber Files Cloud user guide.

Agent for Exchange (for mailbox backup)

l Windows Server 2008 – Standard, Enterprise, Datacenter, Foundation, and Web editions (x86,
x64)
l Windows Small Business Server 2008
l Windows 7 – all editions
l Windows Server 2008 R2 – Standard, Enterprise, Datacenter, Foundation, and Web editions
l Windows MultiPoint Server 2010/2011/2012
l Windows Small Business Server 2011 – all editions
l Windows 8/8.1 – all editions (x86, x64), except for the Windows RT editions
l Windows Server 2012/2012 R2 – all editions
l Windows Storage Server 2008/2008 R2/2012/2012 R2
l Windows 10 – Home, Pro, Education, and Enterprise editions
l Windows Server 2016 – all installation options, except for Nano Server
l Windows Server 2019 – all installation options, except for Nano Server
l Windows 11 – all editions
l Windows Server 2022 – all installation options, except for Nano Server

Agent for Microsoft 365

l Windows Server 2008 – Standard, Enterprise, Datacenter, Foundation, and Web editions (x64
only)
l Windows Small Business Server 2008
l Windows Server 2008 R2 – Standard, Enterprise, Datacenter, Foundation, and Web editions
l Windows Home Server 2011
l Windows Small Business Server 2011 – all editions

25 © Acronis International GmbH, 2003-2024

l Windows 8/8.1 – all editions (x64 only), except for the Windows RT editions
l Windows Server 2012/2012 R2 – all editions
l Windows Storage Server 2008/2008 R2/2012/2012 R2/2016 (x64 only)
l Windows 10 – Home, Pro, Education, and Enterprise editions (x64 only)
l Windows Server 2016 – all installation options (x64 only), except for Nano Server
l Windows Server 2019 – all installation options (x64 only), except for Nano Server
l Windows 11 – all editions
l Windows Server 2022 – all installation options, except for Nano Server

Agent for Oracle

l Windows Server 2008R2 – Standard, Enterprise, Datacenter, and Web editions (x86, x64)
l Windows Server 2012R2 – Standard, Enterprise, Datacenter, and Web editions (x86, x64)
l Linux – any kernel and distribution supported by Agent for Linux (listed below)

Agent for MySQL/MariaDB

l Linux – any kernel and distribution supported by Agent for Linux (listed below)

Agent for Linux

This agent includes a component for Antivirus & Antimalware protection and URL Filtering. See
"Supported protection features by operating system" (p. 43) for details about supported
functionality by operating system.

The following Linux distributions and kernel versions have been specifically tested. However, even if
your Linux distribution or kernel version is not listed below, it may still work correctly in all required
scenarios, due to the specifics of the Linux operating systems.

If you encounter issues while using Cyber Protection with your combination of Linux distribution
and kernel version, contact the Support team for further investigation.

Linux with kernel from 2.6.9 to 5.19 and glibc 2.3.4 or later, including the following x86 and
x86_64 distributions:

l Red Hat Enterprise Linux 4.x, 5.x, 6.x, 7.x, 8.x*, 9.0*, 9.1*, 9.2*, 9.3*
l Ubuntu 9.10, 10.04, 10.10, 11.04, 11.10, 12.04, 12.10, 13.04, 13.10, 14.04, 14.10, 15.04, 15.10,
16.04, 16.10, 17.04, 17.10, 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10, 22.04, 22.10, 23.04
l Fedora 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 37, 38
l SUSE Linux Enterprise Server 10, 11, 12, 15

Important
Configurations with Btrfs are not supported for SUSE Linux Enterprise Server 12 and SUSE Linux
Enterprise Server 15.

26 © Acronis International GmbH, 2003-2024

l Debian 4.x, 5.x, 6.x, 7.0, 7.2, 7.4, 7.5, 7.6, 7.7, 8.0, 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.8, 8.11, 9.0, 9.1,
9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 9.8, 10, 11
l CentOS 5.x, 6.x, 7.x, 8.x*
l CentOS Stream 8*, 9*
l Oracle Linux 5.x, 6.x, 7.x, 8.x*, 9.0*, 9.1*, 9.2* – both Unbreakable Enterprise Kernel and Red Hat
Compatible Kernel

Note
Installing the protection agent on Oracle Linux 8.6 and later, on which Secure Boot is enabled,
requires manual signing of kernel modules. For more information on how to sign a kernel
module, refer to this knowledge base article.

l CloudLinux 5.x, 6.x, 7.x, 8.x*

l ClearOS 5.x, 6.x, 7.x
l AlmaLinux 8.x*,9.0*, 9.1*, 9.2*
l Rocky Linux 8.x*, 9.0*, 9.1*, 9.2*, 9.3*
l ALT Linux 7.0

* Starting from version 8.4, supported only with kernels from 4.18 to 5.19

Agent for Mac

This agent includes a component for Antivirus & Antimalware protection and URL Filtering. See
"Supported protection features by operating system" (p. 43) for details about supported
functionality by operating system.

Both x64 and ARM architecture (used in Apple silicon processors such as Apple M1 and M2) are
supported.

Note
You cannot recover disk-level backups of Intel-based Macs to Macs that use Apple silicon
processors, and vice-versa. You can recover files and folders.

l macOS High Sierra 10.13

l macOS Mojave 10.14
l macOS Catalina 10.15
l macOS Big Sur 11
l macOS Monterey 12
l macOS Ventura 13
l macOS Sonoma 14

27 © Acronis International GmbH, 2003-2024

Important
Starting from version C23.07, Cyber Protect Cloud does not support the following operating
systems: OS X Yosemite 10.10, OS X El Capitan 10.11, and macOS Sierra 10.12.

We strongly recommend that you upgrade your operating system to a supported version in order to
ensure compatibility and be able to use the full functionality of Cyber Protect Cloud.

Agent for VMware (Virtual Appliance)

This agent is delivered as a virtual appliance for running on an ESXi host.

VMware ESXi 4.1, 5.0, 5.1, 5.5, 6.0, 6.5, 6.7, 7.0, 8.0

Agent for VMware (Windows)

This agent is delivered as a Windows application for running in any operating system listed above
for Agent for Windows with the following exceptions:

l 32-bit operating systems are not supported.

l Windows XP, Windows Server 2003/2003 R2, and Windows Small Business Server 2003/2003 R2
are not supported.

Agent for Hyper-V

l Windows Server 2008 (x64 only) with Hyper-V role, including Server Core installation mode
l Windows Server 2008 R2 with Hyper-V role, including Server Core installation mode
l Microsoft Hyper-V Server 2008/2008 R2
l Windows Server 2012/2012 R2 with Hyper-V role, including Server Core installation mode
l Microsoft Hyper-V Server 2012/2012 R2
l Windows 8, 8.1 (x64 only) with Hyper-V
l Windows 10 – Pro, Education, and Enterprise editions with Hyper-V
l Windows Server 2016 with Hyper-V role – all installation options, except for Nano Server
l Microsoft Hyper-V Server 2016
l Windows Server 2019 with Hyper-V role – all installation options, except for Nano Server
l Microsoft Hyper-V Server 2019
l Windows Server 2022 – all installation options, except for Nano Server

Agent for Virtuozzo

l Virtuozzo 6.0.10, 6.0.11, 6.0.12, 7.0.13, 7.0.14
l Virtuozzo Hybrid Server 7.5

Agent for Virtuozzo Hybrid Infrastructure

Virtuozzo Hybrid Infrastructure 3.5, 4.0, 4.5, 4.6, 4.7, 5.0, 5.1, 5.2, 5.3, 5.4, 6.0

28 © Acronis International GmbH, 2003-2024

Agent for Scale Computing HC3
Scale Computing Hypercore 8.8, 8.9, 9.0, 9.1, 9.2, 9.3

Agent for oVirt

Red Hat Virtualization 4.2, 4.3, 4.4, 4.5

Agent for Synology

DiskStation Manager 6.2.x, 7.x

Agent for Synology supports only NAS devices with x86_64 processors. ARM processors are not
supported.

Cyber Protect Monitor

l Windows 7 and later
l Windows Server 2008 R2 and later
l All macOS versions that are supported by Agent for Mac

Supported Microsoft SQL Server versions

l Microsoft SQL Server 2022
l Microsoft SQL Server 2019
l Microsoft SQL Server 2017
l Microsoft SQL Server 2016
l Microsoft SQL Server 2014
l Microsoft SQL Server 2012
l Microsoft SQL Server 2008 R2
l Microsoft SQL Server 2008
l Microsoft SQL Server 2005

The SQL Server Express editions of the above SQL server versions are supported as well.

Note
Microsoft SQL backup is supported only for databases running on NFTS, REFS, and FAT32 file
systems. ExFat is not supported.

Supported Microsoft Exchange Server versions

l Microsoft Exchange Server 2019 – all editions.
l Microsoft Exchange Server 2016 – all editions.
l Microsoft Exchange Server 2013 – all editions, Cumulative Update 1 (CU1) and later.

29 © Acronis International GmbH, 2003-2024

l Microsoft Exchange Server 2010 – all editions, all service packs. Mailbox backup and granular
recovery from database backups are supported starting with Service Pack 1 (SP1).
l Microsoft Exchange Server 2007 – all editions, all service packs. Mailbox backup and granular
recovery from database backups are not supported.

Supported Microsoft SharePoint versions

Cyber Protection supports the following Microsoft SharePoint versions:

l Microsoft SharePoint 2013

l Microsoft SharePoint Server 2010 SP1
l Microsoft SharePoint Foundation 2010 SP1
l Microsoft Office SharePoint Server 2007 SP2*
l Microsoft Windows SharePoint Services 3.0 SP2*

*In order to use SharePoint Explorer with these versions, you need a SharePoint recovery farm to
attach the databases to.

The backups or databases from which you extract data must originate from the same SharePoint
version as the one where SharePoint Explorer is installed.

Supported Oracle Database versions

l Oracle Database version 11g, all editions
l Oracle Database version 12c, all editions
l Oracle Database version 19c, all editions
l Oracle Database version 21c, all editions

Only single-instance configurations are supported.

Supported SAP HANA versions

HANA 2.0 SPS 03 installed in RHEL 7.6 running on a physical machine or VMware ESXi virtual
machine.

Because SAP HANA does not support recovery of multitenant database containers by using storage
snapshots, this solution supports SAP HANA containers with only one tenant database.

Supported MySQL versions

l 5.5.x − Community Server, Enterprise, Standard, and Classic editions
l 5.6.x − Community Server, Enterprise, Standard, and Classic editions
l 5.7.x − Community Server, Enterprise, Standard, and Classic editions
l 8.0.x − Community Server, Enterprise, Standard, and Classic editions

30 © Acronis International GmbH, 2003-2024

Supported MariaDB versions
l 10.0.x
l 10.1.x
l 10.2.x
l 10.3.x
l 10.4.x
l 10.5.x
l 10.6.x
l 10.7.x

Supported virtualization platforms

The following table summarizes how various virtualization platforms are supported.

For more information about the differences between the agent-based and agentless backup, see
"Agent-based and agentless backup" (p. 62).

Note
If you use a virtualization platform or version that is not listed below, the Agent-based backup
(Backup from inside a guest OS) method may still work correctly in all required scenarios. If you
encounter issues with the agent-based backup, contact the Support team for further investigation.

VMware
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

VMware vSphere versions: 4.1, Supported Supported

5.0, 5.1, 5.5, 6.0, 6.5, 6.7, 7.0, 8.0
Devices > Add > Devices > Add > Workstations
VMware vSphere editions: Virtualization hosts > or Servers > Windows or
VMware ESXi > Agent for Linux
VMware vSphere Essentials*
installation in Windows
VMware vSphere Essentials Plus*
or
VMware vSphere Standard*
Devices > Add >
VMware vSphere Advanced Virtualization hosts >

VMware vSphere Enterprise VMware ESXi > Virtual

appliance (OVF)
VMware vSphere Enterprise Plus

VMware vSphere Hypervisor (Free Not supported Supported

ESXi)**
Devices > Add > Workstations

31 © Acronis International GmbH, 2003-2024

 Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

or Servers > Windows or

Linux

VMware Server (VMware Virtual Not supported Supported

server)
Devices > Add > Workstations
VMware Workstation or Servers > Windows or
Linux
VMware ACE

VMware Player

* In these editions, the HotAdd transport for virtual disks is supported on vSphere 5.0 and later. On
version 4.1, backups may run slower.

** Backup at a hypervisor level is not supported for vSphere Hypervisor because this product
restricts access to Remote Command Line Interface (RCLI) to read-only mode. The agent works
during the vSphere Hypervisor evaluation period while no serial key is entered. Once you enter a
serial key, the agent stops functioning.

Note
Cyber Protect Cloud officially supports any update within the supported major vSphere version.

For example, vSphere 8.0 support includes support for any update within this version, unless stated
otherwise. That is, vSphere 8.0 Update 1 is also supported along with originally released vSphere
8.0.

Support for specific VMware vSphere version means that vSAN of the corresponding version is also
supported. For example, support for vSphere 8.0 means that vSAN 8.0 is also supported.

Limitations
l Fault tolerant machines
Agent for VMware backs up a fault tolerant machine only if fault tolerance was enabled in
VMware vSphere 6.0 and later. If you upgraded from an earlier vSphere version, it is enough to
disable and enable fault tolerance for each machine. If you are using an earlier vSphere version,
install an agent in the guest operating system.
l Independent disks and RDM
Agent for VMware does not back up Raw Device Mapping (RDM) disks in physical compatibility
mode or independent disks. The agent skips these disks and adds warnings to the log. You can
avoid the warnings by excluding independent disks and RDMs in physical compatibility mode
from the protection plan. If you want to back up these disks or data on these disks, install an
agent in the guest operating system.

32 © Acronis International GmbH, 2003-2024

l In-guest iSCSI connection
Agent for VMware does not back up LUN volumes connected by an iSCSI initiator that works
within the guest operating system. Because the ESXi hypervisor is not aware of such volumes, the
volumes are not included in hypervisor-level snapshots and are omitted from a backup without a
warning. If you want to back up these volumes or data on these volumes, install an agent in the
guest operating system.
l Encrypted virtual machines (introduced in VMware vSphere 6.5)
o Encrypted virtual machines are backed up in an unencrypted state. If encryption is critical to
you, enable encryption of backups when creating a protection plan.
o Recovered virtual machines are always unencrypted. You can manually enable encryption after
the recovery is complete.
o If you back up encrypted virtual machines, we recommend that you also encrypt the virtual
machine where Agent for VMware is running. Otherwise, operations with encrypted machines
may be slower than expected. Apply the VM Encryption Policy to the agent's machine by
using vSphere Web Client.
o Encrypted virtual machines will be backed up via LAN, even if you configure the SAN transport
mode for the agent. The agent will fall back on the NBD transport because VMware does not
support SAN transport for backing up encrypted virtual disks.
l Secure Boot
o VMware virtual machines: (introduced in VMware vSphere 6.5) Secure Boot is disabled after a
virtual machine is recovered as a new virtual machine. You can manually enable this option
after the recovery is complete. This limitation applies to VMware.
o Hyper-V virtual machines: For all GEN2 VMs, Secure Boot is disabled after the virtual machine is
recovered to both new virtual machine or an existing virtual machine.
l ESXi configuration backup is not supported for VMware vSphere 7.0.
l Supported operations for machines with logical volumes
Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with some limitations. For more information about the
limitations, see "Supported operations with logical volumes" (p. 54).

Microsoft
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Windows Server 2008 (x64) with Supported Supported

Hyper-V
Devices > Add > Devices > Add > Workstations
Windows Server 2008 R2 with Virtualization hosts > Hyper- or Servers > Windows or
Hyper-V V Linux

Microsoft Hyper-V Server

2008/2008 R2

33 © Acronis International GmbH, 2003-2024

 Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Windows Server 2012/2012 R2

with Hyper-V

Microsoft Hyper-V Server

2012/2012 R2

Windows 8, 8.1 (x64) with Hyper-V

Windows 10 with Hyper-V

Windows Server 2016 with Hyper-

V – all installation options, except
for Nano Server

Microsoft Hyper-V Server 2016

Windows Server 2019 with Hyper-

V – all installation options, except
for Nano Server

Microsoft Hyper-V Server 2019

Windows Server 2022 with Hyper-

V – all installation options, except
for Nano Server

Microsoft Virtual PC 2004, 2007 Not supported Supported

Windows Virtual PC Devices > Add > Workstations

or Servers > Windows or
Linux

Microsoft Virtual Server 2005 Not supported Supported

Devices > Add > Workstations

or Servers > Windows or
Linux

Note
Hyper-V virtual machines running on a hyper-converged cluster with Storage Spaces Direct (S2D)
are supported. Storage Spaces Direct is also supported as a backup storage.

Limitations
l Pass-through disks
Agent for Hyper-V does not back up pass-through disks. During backup, the agent skips these
disks and adds warnings to the log. You can avoid the warnings by excluding pass-through disks

34 © Acronis International GmbH, 2003-2024

 from the protection plan. If you want to back up these disks or data on these disks, install an
agent in the guest operating system.
l Hyper-V guest clustering
Agent for Hyper-V does not support backup of Hyper-V virtual machines that are nodes of a
Windows Server Failover Cluster. A VSS snapshot at the host level can even temporarily
disconnect the external quorum disk from the cluster. If you want to back up these machines,
install agents in the guest operating systems.
l In-guest iSCSI connection
Agent for Hyper-V does not back up LUN volumes connected by an iSCSI initiator that works
within the guest operating system. Because the Hyper-V hypervisor is not aware of such volumes,
the volumes are not included in hypervisor-level snapshots and are omitted from a backup
without a warning. If you want to back up these volumes or data on these volumes, install an
agent in the guest operating system.
l Secure Boot
For all GEN2 VMs, Secure Boot is disabled after the virtual machine is recovered to both new
virtual machine or an existing virtual machine.
l Supported operations for machines with logical volumes
Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with some limitations. For more information about the
limitations, see "Supported operations with logical volumes" (p. 54).
l VHD/VHDX file names with ampersand symbols
On Hyper-V hosts running Windows Server 2016 or later, you cannot back up legacy virtual
machines (version 5.0) originally created with Hyper-V 2012 R2 or older, if the names of their
VHD/VHDX files contain the ampersand symbol (&).
To be able to back up such machines, in Hyper-V Manager, detach the corresponding virtual disk
from the virtual machine, edit the VHD/VHDX file name by removing the ampersand symbol, and
then attach the disk back to the virtual machine.
l Dependency on the Microsoft WMI subsystem
Agentless backups of Hyper-V virtual machines depend on the Microsoft WMI subsystem, and in
particular on the Msvm_VirtualSystemManagementService class. If the WMI queries fail, the backups
will also fail. For more information about the Msvm_VirtualSystemManagementService class, see the
Microsoft documentation.

Scale Computing
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Scale Computing Hypercore 8.8, Supported Supported

8.9, 9.0, 9.1, 9.2, 9.3
Devices > Add > Devices > Add > Workstations
Virtualization hosts > Scale or Servers > Windows or
Computing HC3 Linux

35 © Acronis International GmbH, 2003-2024

Limitations
Supported operations for machines with logical volumes

Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with some limitations. For more information about the limitations,
see "Supported operations with logical volumes" (p. 54).

Citrix
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Citrix XenServer/Citrix Hypervisor Not supported Supported only for fully

4.1.5, 5.5, 5.6, 6.0, 6.1, 6.2, 6.5, 7.0, virtualized (aka HVM) guests.
7.1, 7.2, 7.3, 7.4, 7.5, 8.0, 8.1, 8.2 Paravirtualized (aka PV) guests
are not supported.

Devices > Add > Virtualization

hosts > Citrix XenServer >
Windows or Linux

Red Hat and Linux

Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Red Hat Enterprise Virtualization Not supported Supported

(RHEV) 2.2, 3.0, 3.1, 3.2, 3.3, 3.4,
Devices > Add > Workstations
3.5, 3.6
or Servers > Windows or
Red Hat Virtualization (RHV) 4.0, Linux
4.1

Red Hat Virtualization (managed Supported Supported

by oVirt) 4.2, 4.3, 4.4, 4.5
Devices > Add > Devices > Add > Workstations
Virtualization hosts > Red or Servers > Windows or
Hat Virtualization (oVirt) Linux

Kernel-based Virtual Machines Not supported Supported

(KVM)
Devices > Add > KVM >
Windows or Linux

Kernel-based Virtual Machines Supported Supported

(KVM) managed by oVirt 4.3
Devices > Add > Devices > Add > Workstations
running on Red Hat Enterprise

36 © Acronis International GmbH, 2003-2024

 Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Linux 7.6, 7.7 or CentOS 7.6, 7.7 Virtualization hosts > Red or Servers > Windows or
Hat Virtualization (oVirt) Linux

Kernel-based Virtual Machines Supported Supported

(KVM) managed by oVirt 4.4
Devices > Add > Devices > Add > Workstations
running on Red Hat Enterprise
Virtualization hosts> Red Hat or Servers > Windows or
Linux 8.x or CentOS Stream 8.x
Virtualization (oVirt) Linux

Kernel-based Virtual Machines Supported Supported

(KVM) managed by oVirt 4.5
Devices > Add > Devices > Add > Workstations
running on Red Hat Enterprise
Virtualization hosts > Red or Servers > Windows or
Linux 8.x or CentOS Stream 8.x
Hat Virtualization (oVirt) Linux

Limitations
Supported operations for machines with logical volumes

Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with some limitations. For more information about the limitations,
see "Supported operations with logical volumes" (p. 54).

Parallels
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Parallels Workstation Not supported Supported

Devices > Add > Workstations

or Servers > Windows or
Linux

Parallels Server 4 Bare Metal Not supported Supported

Devices > Add > Workstations

or Servers > Windows or
Linux

37 © Acronis International GmbH, 2003-2024

Oracle
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Oracle Virtualization Manager Supported Supported

(based on oVirt)* 4.3
Devices > Add > Devices > Add > Workstations
Virtualization hosts > Red or Servers > Windows or
Hat Virtualization (oVirt) Linux

Oracle VM Server 3.0, 3.3, 3.4 Not supported Supported only for fully
virtualized (aka HVM) guests.
Paravirtualized (aka PV) guests
are not supported.

Devices > Add > Virtualization

hosts > Oracle > Windows or
Linux

Oracle VM VirtualBox 4.x Not supported Supported

Devices > Add > Virtualization

hosts > Oracle > Windows or
Linux

*Oracle Virtualization Manager is supported by Agent for oVirt.

Limitations
Supported operations for machines with logical volumes

Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with some limitations. For more information about the limitations,
see "Supported operations with logical volumes" (p. 54).

Nutanix
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Nutanix Acropolis Hypervisor Not supported Supported

(AHV) 20160925.x through
Devices > Add > Virtualization
20180425.x
hosts > Nutanix AHV >
Windows or Linux

38 © Acronis International GmbH, 2003-2024

Virtuozzo
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Virtuozzo 6.0.10, 6.0.11, 6.0.12 Supported Supported for virtual machines

only. Containers are not
Devices > Add >
supported.
Virtualization hosts >
Virtuozzo Devices > Add > Workstations
or Servers > Windows or
Linux

Virtuozzo 7.0.13, 7.0.14 Supported for ploop containers Supported for virtual machines
only. Virtual machines are not only. Containers are not
supported. supported.

Devices > Add > Devices > Add > Workstations

Virtualization hosts > or Servers > Windows or
Virtuozzo Linux

Virtuozzo Hybrid Server 7.5 Supported Supported for virtual machines

only. Containers are not
Devices > Add >
supported.
Virtualization hosts >
Virtuozzo Devices > Add > Workstations
or Servers > Windows or
Linux

Limitations
Supported operations for machines with logical volumes

Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with some limitations. For more information about the limitations,
see "Supported operations with logical volumes" (p. 54).

Vituozzo Hybrid Infrastructure

Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Virtuozzo Hybrid Infrastructure Supported Supported

3.5, 4.5, 4.6, 4.7, 5.0, 5.1, 5.2, 5.3,
Devices > Add > Devices > Add > Workstations
5.4, 6.0
Virtualization hosts > or Servers > Windows or
Virtuozzo Hybrid Linux
infrastructure

39 © Acronis International GmbH, 2003-2024

Limitations
l Agentless backup of VMs with disks on an external iSCSI storage
You cannot back up VMs from Virtuozzo Hybrid Infrastructure, if VM disks are placed on external
iSCSI volumes (attached to the VHI cluster).
l Supported operations for machines with logical volumes
Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with some limitations. For more information about the
limitations, see "Supported operations with logical volumes" (p. 54).

Amazon
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Amazon EC2 instances Not supported Supported

Devices > Add > Workstations

or Servers > Windows or
Linux

Microsoft Azure
Platform Agentless backup Agent-based backup
(Backup at the hypervisor (Backup from inside a guest
level) OS)

Azure virtual machines Not supported Supported

Devices > Add > Workstations

or Servers > Windows or
Linux

Compatibility with encryption software

There are no limitations on backing up and recovering data that is encrypted by file-level encryption
software.

Disk-level encryption software encrypts data on the fly. This is why data contained in the backup is
not encrypted. Disk-level encryption software often modifies system areas: boot records, or
partition tables, or file system tables. These factors affect disk-level backup and recovery, the ability
of the recovered system to boot and access to Secure Zone.

You can back up the data encrypted by the following disk-level encryption software:

40 © Acronis International GmbH, 2003-2024

l Microsoft BitLocker Drive Encryption
l McAfee Endpoint Encryption
l PGP Whole Disk Encryption

To ensure reliable disk-level recovery, follow the common rules and software-specific
recommendations.

Common installation rule

We strongly recommend that you install the encryption software before you install the protection
agents.

The way of using Secure Zone

Secure Zone must not be encrypted with disk-level encryption. This is the only way to use Secure
Zone:

1. Install the encryption software; then, install the agent.

2. Create Secure Zone.
3. Exclude Secure Zone when encrypting the disk or its volumes.

Common backup rule

You can do a disk-level backup in the operating system.

Software-specific recovery procedures

Microsoft BitLocker Drive Encryption

To recover a system that was encrypted by BitLocker:

1. Boot from the bootable media.

2. Recover the system. The recovered data will be unencrypted.
3. Reboot the recovered system.
4. Turn on BitLocker.

If you only need to recover one partition of a multi-partitioned disk, do so under the operating
system. Recovery under bootable media may make the recovered partition undetectable for
Windows.

McAfee Endpoint Encryption and PGP Whole Disk Encryption

You can recover an encrypted system partition by using bootable media only.

If the recovered system fails to boot, rebuild Master Boot Record as described in the following
Microsoft knowledge base article: https://support.microsoft.com/kb/2622803

41 © Acronis International GmbH, 2003-2024

Compatibility with Dell EMC Data Domain storages
You can use Dell EMC Data Domain devices as backup storage.

With this storage, we recommend that you use a backup scheme that regularly creates full backups,
for example Always full. To learn more about the available backup schemes, see "Backup schemes"
(p. 398).

Retention lock (Governance mode) is supported. If retention lock is enabled, you need to add the
AR_RETENTION_LOCK_SUPPORT environment variable to the machine with the protection agent that uses
this storage as a backup destination.

Note
Dell EMC Data Domain storages with enabled retention lock are not supported by Agent for Mac.

To add the AR_RETENTION_LOCK_SUPPORT environment variable

In Windows

1. Log in as administrator to the machine with the protection agent.

2. In Control Panel, go to System and Security > System > Advanced system settings.
3. On the Advanced tab, click Environment Variables.
4. In the System variables panel, click New.
5. In the New System Variable window, add the new variable as follows:
l Variable name: AR_RETENTION_LOCK_SUPPORT
l Variable value: 1
6. Click OK.
7. In the Environment Variables window, click OK.
8. Restart the machine.

In Linux

1. Log in as administrator to the machine with the protection agent.

2. Go to the /sbin directory, and then open the acronis_mms file for editing.
3. Above the line export LD_LIBRARY_PATH, add the following line:

export AR_RETENTION_LOCK_SUPPORT=1

4. Save the acronis_mms file.

5. Restart the machine.

In a virtual appliance

1. Log in as administrator to the virtual appliance.

2. Go to the /bin directory, and then open the autostart file for editing.
3. Under the line export LD_LIBRARY_PATH, add the following line:

42 © Acronis International GmbH, 2003-2024

 export AR_RETENTION_LOCK_SUPPORT=1

4. Save the autostart file.

5. Restart the virtual appliance machine.

Supported protection features by operating system

This topic contains information about the protection features of Cyber Protect Cloud. It does not list
the backup and recovery features.

The protection features are only supported on machines on which a protection agent is installed.
They are not available for virtual machines that are backed up in the agentless mode, for example,
by Agent for Hyper-V, Agent for VMware, Agent for Virtuozzo Hybrid Infrastructure, Agent for Scale
Computing, or Agent for oVirt.

Some features might require additional licensing, depending on the applied licensing model.

Supported operating systems and versions

Windows

Unless stated otherwise for a specific feature set, the following Windows versions are supported:

l Windows 7 Service Pack 1 and later

l Windows Server 2008 R2 Service Pack 1 and later

Note
For Windows 7, you must install the following updates from Microsoft before installing the
protection agent.

l Windows 7 Extended Security Updates (ESU)

l KB4474419
l KB4490628

For more information on the required updates, refer to this knowledge base article.

Linux

Supported Linux distributions and their versions depend on the feature sets, and are shown at the
bottom of each table.

macOS

Supported macOS versions depend on the feature sets, and are shown at the bottom of each table.

43 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Default protection plans

Remote Workers Yes No No

Office Workers (third-party antivirus) Yes No No

Office Workers (Cyber Protect antivirus) Yes No No

Cyber Protect Essentials (only for Cyber Protect

Yes No No
Essentials edition)

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Forensic backup

Collecting memory dump Yes No No

Snapshot of running processes Yes No No

Notarization of local image forensic backup Yes No No

Notarization of cloud image forensic backup Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Features Windows Linux macOS

Continuous data protection (CDP)

CDP for files and folders Yes No No

CDP for changed files via application tracking Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Autodiscovery and remote installation

Network-based discovery Yes No No

Active Directory-based discovery Yes No No

Template-based discovery (importing machines from a

Yes No No
file)

Manual adding of devices Yes No No

44 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Autodiscovery and remote installation

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Active Protection

Process Injects detection Yes No No

Automatic recovery of affected files from the local

Yes Yes Yes
cache

Self-defense for Acronis backup files Yes No No

Self-defense for Acronis software Yes

(Only Active
Yes No Protection and
antimalware
components)

Trusted/blocked process management Yes No Yes

Processes/folders exclusions Yes Yes Yes

Ransomware detection based on a process behavior

Yes Yes Yes
(AI-based)

Cryptomining process detection based on process

Yes No No
behavior

External drives protection (HDD, flash drives, SD

Yes No Yes
cards)

Network folder protection Yes Yes Yes

Server-side protection Yes No No

Zoom, Cisco Webex, Citrix Workspace, and Microsoft

Yes No No
Teams protection

For more information about the supported operating systems and their versions, see "Supported
platforms" (p. 778).

45 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Antivirus and Antimalware protection

Fully-integrated Active Protection functionality Yes No No

Real-time antimalware protection Yes, with the Yes, with the

Advanced Advanced
Yes
Antimalware Antimalware
pack pack

Advanced real-time antimalware protection with

Yes Yes Yes
local signature-based detection

Static analysis for portable executable files Yes No Yes*

On-demand antimalware scanning Yes Yes** Yes

Network folder protection Yes Yes No

Server-side protection Yes No No

Scan of archive files Yes No Yes

Scan of removable drives Yes No Yes

Scan of new and changed files only Yes No Yes

File/folder exclusions Yes Yes Yes***

Processes exclusions Yes No Yes

Behavioral analysis engine Yes No Yes

Exploit prevention Yes No No

Quarantine Yes Yes Yes

Quarantine auto clean-up Yes Yes Yes

URL filtering (http/https) Yes No No

Corporate-wide whitelist Yes No Yes

Firewall management**** Yes No No

Microsoft Defender Antivirus

Yes No No
management*****

Microsoft Security Essentials management Yes No No

46 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Antivirus and Antimalware protection

Registering and managing Antivirus and

Antimalware protection via Windows Security Yes No No
Center

For more information about the supported operating systems and their versions, see "Supported
platforms" (p. 778).

* Static analysis for portable executable files is supported only for scheduled scans on macOS.

** Start conditions are not supported for on-demand scanning on Linux.

*** File/folder exclusions are only supported for the case when you specify files and folders that will
not be scanned by real-time protection or scheduled scans on macOS.

**** Firewall management is supported on Windows 8 and later. Windows Server is not supported.

***** Microsoft Defender Antivirus management is supported on Windows 8.1 and later.

Feature set Windows Linux macOS

Vulnerability assessment

Vulnerability assessment of operating system and its

Yes Yes****** Yes
native applications

Vulnerability assessment for 3rd-party applications Yes No Yes

For more information about the supported operating systems and their versions, refer to "Supported
Microsoft and third-party products" (p. 905), "Supported Linux products" (p. 908), and "Supported Apple
and third-party products" (p. 907).

****** The vulnerability assessment depends on the availability of official security advisories for
specific distribution, for example https://lists.centos.org/pipermail/centos-announce,
https://lists.centos.org/pipermail/centos-cr-announce, and others.

Feature set Windows Linux macOS

Patch management

Patch auto-approval Yes No No

Patch auto-installation Yes No No

Patch testing Yes No No

Manual patch installation Yes No No

Patch scheduling Yes No No

47 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Patch management

Fail-safe patching: backup of machine before installing

Yes No No
patches as part of protection plan

Cancelation of a machine reboot if a backup is running Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Features Windows Linux macOS

Data protection map

Adjustable definition of important files Yes No No

Scanning machines to find unprotected files Yes No No

Unprotected locations overview Yes No No

Ability to start the protection action from the Data

Yes No No
protection map widget (Protect all files action)

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Disk health

AI-based HDD and SSD health control Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Features Windows Linux macOS

Smart protection plans based on Acronis Cyber Protection Operations Center (CPOC) alerts

Threat feed Yes No No

Remediation wizard Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Backup scanning

Antimalware scan of image backups as part of backup

Yes No No
plan

48 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Backup scanning

Scanning of image backups for malware in cloud Yes No No

Malware scan of encrypted backups Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Safe recovery

Antimalware scanning with Antivirus and Antimalware

Yes No No
protection during the recovery process

Safe recovery for encrypted backups Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Remote desktop connection

Connection via NEAR Yes Yes Yes

Connection via RDP Yes No No

Connection via Apple Screen Sharing No No Yes

Connection via web client Yes No No

Connection via Quick Assist Yes Yes Yes

Remote assistance Yes Yes Yes

File transfer Yes Yes Yes

Screenshot transmission Yes Yes Yes

For more information about the supported operating systems and their versions, see "Supported
platforms" (p. 942).

Feature set Windows Linux macOS

#CyberFit Score

#CyberFit Score status Yes No No

#CyberFit Score standalone tool Yes No No

49 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

#CyberFit Score

#CyberFit Score recommendations Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Data loss prevention

Supported on
Macs with Intel
processors
running macOS
10.15 and later
or macOS
Device control Yes No 11.2.3 or later.

Not supported
on ARM-based
Apple silicon
processors,
such as Apple
M1 / M2.

Advanced Data Loss Prevention Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

Feature set Windows Linux macOS

Management options

Upsell scenarios to promote Cyber Protect editions Yes Yes Yes

Web-based centralized and remote management console Yes Yes Yes

Supported operating systems and versions: Platform independent.

Feature set Windows Linux macOS

Protection options

Remote wipe Yes No No

Supported for Windows 10 and later.

50 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Cyber Protect Monitor

Cyber Protect app Yes No Yes

Protection status for Zoom Yes No No

Protection status for Cisco Webex Yes No No

Protection status for Citrix Workspace Yes No No

Protection status for Microsoft Teams Yes No No

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

On macOS, Cyber Protect Monitor is supported for all versions on which you can install Agent for Mac. For
more information, see "Agent for Mac" (p. 27).

Feature set Windows Linux macOS

Software inventory

Software inventory scanning Yes No Yes

Software inventory monitoring Yes No Yes

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

On macOS, Software inventory is supported for versions 10.13.x − 13.x.

Feature set Windows Linux macOS

Hardware inventory

Hardware inventory scanning Yes No Yes

Hardware inventory monitoring Yes No Yes

See the supported Windows versions in "Supported operating systems and versions" (p. 43).

On macOS, Hardware inventory is supported for versions 10.13.x − 13.x.

Supported file systems

A protection agent can back up any file system that is accessible from the operating system where
the agent is installed. For example, Agent for Windows can back up and recover an ext4 file system if
the corresponding driver is installed in Windows.

The following table summarizes the file systems that can be backed up and recovered (bootable
media supports only recovery). The limitations apply to both the agents and bootable media.

51 © Acronis International GmbH, 2003-2024

 Supported by

Bootable
File system Bootable Limitations
media for
Agents media for
Windows
Mac
and Linux

FAT16/32 All agents + +

NTFS All agents + +

No limitations
ext2/ext3/ext4 All agents + -

Agent for
HFS+ - +
Mac

l Supported starting with

macOS High Sierra 10.13
l Disk configuration should
Agent for
APFS - + be re-created manually
Mac
when recovering to a non-
original machine or bare
metal.

Agent for
l File filters
JFS + - (Inclusions/Exclusions) are
Linux
not supported
l Fast incremental/
Agent for differential backup cannot
ReiserFS3 + -
Linux be enabled

l File filters
(Inclusions/Exclusions) are
not supported
Agent for l Fast incremental/
ReiserFS4 + -
Linux differential backup cannot
be enabled
l Volumes cannot be resized
during a recovery

l File filters
(Inclusions/Exclusions) are
not supported
l Fast incremental/
ReFS All agents + +
differential backup cannot
be enabled
l Volumes cannot be resized
during a recovery

52 © Acronis International GmbH, 2003-2024

 Supported by

Bootable
File system Bootable Limitations
media for
Agents media for
Windows
Mac
and Linux

l During a file recovery from

a ReFS backup, only the
content is recovered.
Access-control lists (ACL)
and alternate streams are
not recovered. Sparse files
are recovered as regular
files.

l File filters
(Inclusions/Exclusions) are
not supported
l Fast incremental/
differential backup cannot
be enabled
l Volumes cannot be
resized during a recovery
l The fast-incremental
XFS All agents + +
backup mode is not
supported for the XFS file
system. Incremental and
differential backups of XFS
volumes to the cloud may
be significantly slower
than comparable ext4
backups that use the fast-
incremental mode.

Agent for
Linux swap + - No limitations
Linux

+
l Only disk/volume backup
Bootable is supported
media cannot l File filters
exFAT All agents be used for + (Inclusions/Exclusions) are
recovery if not supported
the backup is l Individual files cannot be
stored on
recovered from a backup
exFAT

53 © Acronis International GmbH, 2003-2024

The software automatically switches to the sector-by-sector mode when backing up drives with
unrecognized or unsupported file systems (for example, Btrfs). A sector-by-sector backup is possible
for any file system that:

l is block-based
l spans a single disk
l has a standard MBR/GPT partitioning scheme

If the file system does not meet these requirements, the backup fails.

Data Deduplication
In Windows Server 2012 and later, you can enable the Data Deduplication feature for an NTFS
volume. Data Deduplication reduces the used space on the volume by storing duplicate fragments
of the volume's files only once.

You can back up and recover a data deduplication–enabled volume at a disk level, without
limitations. File-level backup is supported, except when using Acronis VSS Provider. To recover files
from a disk backup, either run a virtual machine from your backup, or mount the backup on a
machine running Windows Server 2012 or later, and then copy the files from the mounted volume.

The Data Deduplication feature of Windows Server is unrelated to the Acronis Backup Deduplication
feature.

Supported operations with logical volumes

Backup and recovery of workloads with logical volumes, such as LDM in Windows (dynamic disks)
and LVM in Linux, are supported with the following limitations.

Backup
Agent-based backup is a backup created by a protection agent that is installed on the workload or
by a bootable media.

Agentless backup is available only for virtual machines. The agentless backup is performed on the
hypervisor level by agent that can back up and recover all virtual machines in the environment. No
individual agents are installed on the protected virtual machines.

For more information about the differences between agent-based and agentless backup, see
"Agent-based and agentless backup" (p. 62).

Agent-based backup Agentless backup

l Logical volumes are backed on per volume basis. l When a logical volume is detected on a disk, the
l File filters (Inclusions/Exclusions) are supported. disk is backed up in the sector-by-sector (RAW)
mode. The partition structure of the disk is not
analyzed and no volume images are stored
separately.

54 © Acronis International GmbH, 2003-2024

 Agent-based backup Agentless backup

l Individual LDM or LVM volumes cannot be

selected as backup source – neither by direct
selection nor by using policy rules. Only Entire
machine is available in the What to back up
section of a protection plan.
l File filters (Inclusions/Exclusions) are not
supported. Any configured inclusions or
exclusions will be ignored.

Recovery
Agent-based recovery is a recovery performed by an agent that is installed on the workload or by a
bootable media.

Agentless recovery supports only virtual machines as targets. The agentless recovery is a performed
on the hypervisor level by agent that can back up and recover all virtual machines in the
environment. You do not have to create manually a target machine to which the backup is
recovered.

From agent-based backup From agentless backup

l Per-volume recovery is available. l Per-volume recovery is not available.

Agent-based l File and folder recovery is available. l File and folder recovery is available.
recovery

l Machine migration (P2V, V2P, and V2V) l Per-volume recovery is not available.
is not supported. To recover data from l Entire machine recovery is available.
an agent-based backup, use bootable l File and folder recovery is available.
media. l The Run as VM operation is supported.
l The Run as VM operation is not To make the virtual machine bootable,
supported. you might need to change the boot
Agentless l File and folder recovery is available. order. For more information, see this
recovery
knowledge base article.
l Conversion to the following types of
virtual machine is supported:
o VMware ESXi
o Microsoft Hyper-V
o Scale Computing HC3

55 © Acronis International GmbH, 2003-2024

Installing and deploying Cyber Protection
agents

Preparation

Step 1
Choose an agent, depending on what you are going to back up. For more information on the
possible choices, refer to Which agent do I need?

Step 2
Ensure that there is enough free space on your hard drive to install an agent. For detailed
information about the required space, refer to "System requirements for agents" (p. 63).

Step 3
Download the setup program. To find the download links, click All devices > Add.

The Add devices page provides web installers for each agent that is installed in Windows. A web
installer is a small executable file that downloads the main setup program from the Internet and
saves it as a temporary file. This file is deleted immediately after the installation.

If you want to store the setup programs locally, download a package containing all agents for
installation in Windows by using the link at the bottom of the Add devices page. Both 32-bit and 64-
bit packages are available. These packages enable you to customize the list of components to install.
These packages also enable unattended installation, for example, via Group Policy. This advanced
scenario is described in "Deploying agents through Group Policy" (p. 162).

To download the setup program for Agent for Microsoft 365, click the account icon in the top-right
corner, and then click Downloads > Agent for Microsoft 365.

Installation in Linux and macOS is performed from ordinary setup programs.

All setup programs require an Internet connection to register the machine in the Cyber Protection
service. If there is no Internet connection, the installation will fail.

Step 4
Cyber Protect features require Microsoft Visual C++ 2017 Redistributable. Please ensure that it is
already installed on your machine or install it before installing the agent. After the installation of
Microsoft Visual C++, a restart may be required. You can find the Microsoft Visual C++
Redistributable package here https://support.microsoft.com/help/2999226/update-for-universal-c-
runtime-in-windows.

56 © Acronis International GmbH, 2003-2024

Step 5
Verify that your firewalls and other components of your network security system (such as a proxy
server) allow outbound connections through the following TCP ports.

l Ports 443 and 8443

These ports are used for accessing the Cyber Protect console, registering the agents,
downloading the certificates, user authorization, and downloading files from the cloud storage.
l Ports in the range 7770 – 7800
The agents use these ports to communicate with the management server.
l Ports 44445 and 55556
The agents use these ports for data transfer during backup and recovery.

If a proxy server is enabled in your network, refer to "Configuring proxy server settings" (p. 69) to
understand whether you need to configure these settings on each machine that runs a protection
agent.

The minimum Internet connection speed required for managing an agent from the cloud is 1 Mbit/s
(not to be confused with the data transfer rate acceptable for backing up to the cloud). Consider this
if you use a low-bandwidth connection technology such as ADSL.

TCP ports required for backup and replication of VMware virtual machines
l Port 443
Agent for VMware (both Windows and Virtual Appliance) connects to this port on the ESXi
host/vCenter server to perform VM management operations, such as create, update, and delete
VMs on vSphere during backup, recovery, and VM replication operations.
l Port 902
Agent for VMware (both Windows and Virtual Appliance) connects to this port on the ESXi host to
establish NFC connections to read/write data on VM disks during backup, recovery, and VM
replication operations.
l Port 3333
If the Agent for VMware (Virtual Appliance) is running on the ESXi host/cluster that is the target
for VM replication, VM replication traffic does not go directly to the ESXi host on port 902. Instead,
the traffic goes from the source Agent for VMware to TCP port 3333 on the Agent for VMware
(Virtual Appliance) located on the target ESXi host/cluster.
The source Agent for VMware that reads data from the original VM disks can be anywhere else
and can be of any type: Virtual Appliance or Windows.
The service that is responsible for accepting VM replication data on the target Agent for VMware
(Virtual Appliance) is called “Replica disk server.” This service is responsible for the WAN
optimization techniques, such as traffic compression and deduplication during VM replication,
including replica seeding (see Seeding an initial replica). When no Agent for VMware (Virtual
Appliance) is running on the target ESXi host, this service is not available, and therefore the
replica seeding scenario is not supported.

57 © Acronis International GmbH, 2003-2024

Ports required by the Downloader component
The Downloader component is responsible for delivering updates to a computer and distributing
them to other Downloader instances. It can run in agent mode which turns its computer into
Downloader agent. The Downloader agent downloads updates from the internet and serves as the
source of updates distribution to other computers. The Downloader requires the following ports to
operate.

l TCP and UDP (incoming) port 6888

Used by the BitTorrent protocol for torrent peer-to-peer updates.
l UDP port 6771
Used as the local peer discovery port. Also takes part in peer-to-peer updates.
l TCP port 18018
Used for communication between updaters working in different modes: Updater and
UpdaterAgent.
l TCP port 18019
Local port, used for communication between the Updater and the protection agent.

Step 6
On the machine where you plan to install the protection agent, verify that the following local ports
are not in use by other processes.

l 127.0.0.1:9999
l 127.0.0.1:43234
l 127.0.0.1:9850

Note
You do not have to open them in the firewall.

Changing the ports used by the protection agent

Some of the ports required by the protection agent might be in use by other applications in your
environment. To avoid conflicts, you can change the default ports used by the protection agent by
modifying the following files.

l In Linux: /opt/Acronis/etc/aakore.yaml
l In Windows: \ProgramData\Acronis\Agent\etc\aakore.yaml

Which agent do I need?

Selecting an agent depends on what you are going to back up. The table below summarizes the
information, to help you decide.

58 © Acronis International GmbH, 2003-2024

In Windows, Agent for Exchange, Agent for SQL, Agent for Active Directory, and Agent for Oracle
require that Agent for Windows is also installed. Thus, if you install, for example, Agent for SQL, you
also will be able to back up the entire machine where the agent is installed.

We recommend that you also install Agent for Windows when you install Agent for VMware
(Windows) and Agent for Hyper-V.

In Linux, Agent for Oracle, Agent for MySQL/MariaDB, and Agent for Virtuozzo require that Agent for
Linux (64-bit) is also installed. These agents are bundled into the Agent for Linux (64-bit) setup file.

What are you going to back up? Which agent to Where to install
install? it?

Physical machines

Physical machines running Windows Agent for Windows On the machine

that will be backed
Physical machines running Linux Agent for Linux
up.

Physical machines running macOS Agent for Mac

Databases

SQL databases Agent for SQL On the machine

running Microsoft
SQL Server.

MySQL databases Agent for On the machine

MySQL/MariaDB running MySQL
Server.
(Bundled into the
Agent for Linux (64-
bit) setup file)

MariaDB databases Agent for On the machine

MySQL/MariaDB running MariaDB
Server.
(Bundled into the
Agent for Linux (64-
bit) setup file)

Exchange databases Agent for Exchange On the machine

running the
Mailbox role of
Microsoft Exchange
Server.*

Oracle databases Agent for Oracle On the machine

running Oracle
(In Linux, bundled
Database.
into the Agent for
Linux (64-bit) setup

59 © Acronis International GmbH, 2003-2024

 file)

Cloud-to-cloud workloads

Microsoft 365 mailboxes Cloud agent This functionality is

available with a
(Cloud agent or local agent) (No installation
cloud agent that is
required)
deployed in the
data center. For
more information,
see "Using the
cloud Agent for
Microsoft 365" (p.
582).

Agent for Office On a Windows

365 machine that is
connected to the
Internet. For more
information, see
"Using the locally
installed Agent for
Office 365" (p. 578).

Microsoft 365 OneDrive files and SharePoint Online sites Cloud agent This functionality is
available with a
(No installation
cloud agent that is
required)
deployed in the
data center. For
more information,
see "Using the
cloud Agent for
Microsoft 365" (p.
582).

Google Workspace Gmail mailboxes, Google Drive files, and Cloud agent This functionality is
Shared drive files available with a
(No installation
cloud agent that is
required)
deployed in the
data center. For
more information,
see "Protecting
Google Workspace
data" (p. 613).

Active Directory

Machines running Active Directory Domain Services Agent for Active On the domain
Directory controller.

60 © Acronis International GmbH, 2003-2024

 Virtual machines

VMware ESXi virtual machines Agent for VMware On a Windows

(Windows) machine that has
network access to
vCenter Server and
to the virtual
machine storage.**

Agent for VMware On the ESXi host.

(Virtual Appliance)

Hyper-V virtual machines Agent for Hyper-V On the Hyper-V

host.

Scale Computing HC3 virtual machines Agent for Scale On the Scale
Computing HC3 Computing HC3
(Virtual Appliance) host.

Red Hat Virtualization virtual machines (managed by oVirt) Agent for oVirt On the Red Hat
(Virtual Appliance) Virtualization host.

Virtuozzo virtual machines and containers*** Agent for Virtuozzo On the Virtuozzo
host.
(Bundled into the
Agent for Linux (64-
bit) setup file)

Virtuozzo Hybrid Infrastructure virtual machines Agent for Virtuozzo On the Virtuozzo
Hybrid Hybrid
Infrastructure Infrastructure host.
(Virtual Appliance)

Virtual machines hosted on Amazon EC2 The same as for On the machine
physical that will be backed
Virtual machines hosted on Windows Azure
machines**** up.
Citrix XenServer virtual machines

Red Hat Virtualization (RHV/RHEV), not managed by oVirt

Kernel-based Virtual Machines (KVM), not managed by oVirt

Oracle virtual machines, not managed by oVirt

Nutanix AHV virtual machines

Red Hat Virtualization (RHV/RHEV), managed by oVirt Agent for oVirt On the
(Virtual Appliance) virtualization host.
Kernel-based Virtual Machines (KVM), managed by oVirt

Oracle virtual machines, managed by oVirt

61 © Acronis International GmbH, 2003-2024

 Mobile devices

Mobile devices running Android Mobile app for On the mobile

Android device that will be
backed up.
Mobile devices running iOS Mobile app for iOS

*During the installation, Agent for Exchange checks for enough free space on the machine where it
will run. Free space equal to 15 percent of the biggest Exchange database is temporarily needed
during a granular recovery.

**If your ESXi uses a SAN attached storage, install the agent on a machine connected to the same
SAN. The agent will back up the virtual machines directly from the storage rather than via the ESXi
host and LAN. For detailed instructions, see "Agent for VMware - LAN-free backup" (p. 657).

***For Virtuozzo 7, only ploop containers are supported. Virtual machines are not supported.

****A virtual machine is considered virtual if it is backed up by an external agent. If an agent is

installed in the guest system, the backup and recovery operations are the same as with a physical
machine. Nevertheless, if Cyber Protection can identify a virtual machine by using the CPUID
instruction, a virtual machine service quota is assigned to it. If you use direct passthrough or
another option that masks the CPU manufacturer ID, only service quotas for physical machines can
be assigned.

Agent-based and agentless backup

Agent-based backup requires that a protection agent is installed on each protected machine. Agent-
based backup is supported on all physical and virtual machines. For more information about which
agent you need and where to install it, see "Which agent do I need?" (p. 58)

Agentless backup is supported by some virtualization platforms and it is not available for physical
machines. Agentless backup requires only one protection agent, which is installed on a dedicated
machine in the virtual environment. This agent backs up all other virtual machines in this
environment. For more information about the supported backup types per virtualization platform,
see "Supported virtualization platforms" (p. 31).

For some virtualization platforms, virtual appliances are available. A virtual appliance (VA) is a ready-
made virtual machine that contains a protection agent. The virtual appliances are available in
hypervisor-specific formats, such as .ovf, .ova, or .qcow.

Which backup type do I need?

We recommend the agent-based backup if you need the following:

l Additional protection functionality, such as antivirus and antimalware, patch management, or

remote desktop connection. For more information about these features, see "Supported
protection features by operating system" (p. 43).

62 © Acronis International GmbH, 2003-2024

l Separate virtual machines on the tenant level. For example, because you want to provide the
users in the tenant with access only to their own backups.
l File-level backups that you can recover to the guest operating systems.

We recommend the agentless backup if you need the following:

l Only backup, without any additional protection features.

l Simplified management—you can back up multiple virtual machines by installing and configuring
only one agent.
l Minimal resource usage—one dedicated agent uses less CPU and RAM than multiple agents
installed on each virtual machine in your environment.
l Specific backup setups, such as LAN-free backup. For more information about this feature, see
"Agent for VMware - LAN-free backup" (p. 657).
l Less configuration overhead. The dedicated agent backs up the virtual machines on the
hypervisor level, regardless of guest operating systems.

System requirements for agents

Agent Disk space required for installation

Agent for Windows 1.2 GB

Agent for Linux 2 GB

Agent for Mac 1 GB

Agent for SQL and Agent for Windows 1.2 GB

Agent for Exchange and Agent for Windows 1.3 GB

Agent for Data Loss Prevention 500 MB

Agent for Microsoft 365 500 MB

Agent for Active Directory and Agent for Windows 2 GB

Agent for VMware and Agent for Windows 1.5 GB

Agent for Hyper-V and Agent for Windows 1.5 GB

Agent for Virtuozzo and Agent for Linux 1 GB

Agent for Virtuozzo Hybrid Infrastructure 700 MB

Agent for Oracle and Agent for Windows 2.2 GB

Agent for Oracle and Agent for Linux 2 GB

Agent for MySQL/MariaDB and Agent for Linux 2 GB

63 © Acronis International GmbH, 2003-2024

Backup operations, including deleting backups, require about 1 GB of RAM per 1 TB of backup size.
The memory consumption may vary, depending on the amount and type of data being processed by
the agents.

Note
The RAM usage might increase when backing up to extra large backup sets (4 TB and more).

On x64 systems, operations with bootable media and disk recovery with restart require at least 2 GB
of memory.

On workloads with modern processors, such as 11th Gen Intel Core or AMD Ryzen 7, that support
CET technology, some features of the Agent for Data Loss Prevention are disabled to avoid conflicts.
The following table lists the availability of Device Control and Advanced DLP features on systems
with such CPUs.

Features Device Control Advanced DLP

Local channels

Removable storage n/a Yes

Encrypted removable storage Yes n/a

Printers n/a No

Redirected mapped drives n/a Yes

Redirected clipboard n/a No

Network communications

SMTP emails n/a Yes

Microsoft Outlook (MAPI) n/a Yes

IBM Notes n/a No

Webmails n/a Yes

Instant messaging (ICQ) n/a No

Instant messaging (Viber) n/a No

Instant messaging (IRC, Jabber, Skype, Viber) n/a Yes

File sharing services n/a Yes

Social networks n/a Yes

Local network file sharing (SMB) n/a Yes

Web access (HTTP/HTTPS) n/a Yes

64 © Acronis International GmbH, 2003-2024

 File transfers (FTP/FTPS) n/a Yes

Data transfer allowlisting

Allowlist for device types n/a Yes

Allowlist for network communications n/a Yes

Allowlist for remote hosts n/a Yes

Allowlist for applications n/a Yes

Peripheral devices

Removable storage Yes Yes

Encrypted removable storage Yes Yes

Printers No No

MTP-connected mobile devices No No

Bluetooth adapters Yes Yes

Optical drives Yes Yes

Floppy drives Yes Yes

Windows clipboard No No

Screenshot capture No No

Redirected mapped drives Yes Yes

Redirected clipboard No No

Cyber Protect Agent self-protection

Protection from regular end users Yes Yes

Protection from local system administrators Yes Yes

Linux packages
To add the necessary modules to the Linux kernel, the setup program needs the following Linux
packages:

l The package with kernel headers or sources. The package version must match the kernel version.
l The GNU Compiler Collection (GCC) compiler system. The GCC version must be the one with
which the kernel was compiled.
l The Make tool.
l The Perl interpreter.

65 © Acronis International GmbH, 2003-2024

l The libelf-dev, libelf-devel, or elfutils-libelf-devel libraries for building kernels starting with
4.15 and configured with CONFIG_UNWINDER_ORC=y. For some distributions, such as Fedora 28,
they need to be installed separately from kernel headers.

The names of these packages vary depending on your Linux distribution.

In Red Hat Enterprise Linux, CentOS, and Fedora, the packages normally will be installed by the
setup program. In other distributions, you need to install the packages if they are not installed or do
not have the required versions.

Are the required packages already installed?

To check whether the packages are already installed, perform these steps:

1. Run the following command to find out the kernel version and the required GCC version:

cat /proc/version

This command returns lines similar to the following: Linux version 2.6.35.6 and gcc version
4.5.1
2. Run the following command to check whether the Make tool and the GCC compiler are installed:

make -v
gcc -v

For gcc, ensure that the version returned by the command is the same as in the gcc version in
step 1. For make, just ensure that the command runs.
3. Check whether the appropriate version of the packages for building kernel modules is installed:
l In Red Hat Enterprise Linux, CentOS, and Fedora, run the following command:

yum list installed | grep kernel-devel

l In Ubuntu, run the following commands:

dpkg --get-selections | grep linux-headers

dpkg --get-selections | grep linux-image

In either case, ensure that the package versions are the same as in Linux version in step 1.
4. Run the following command to check whether the Perl interpreter is installed:

perl --version

If you see the information about the Perl version, the interpreter is installed.
5. In Red Hat Enterprise Linux, CentOS, and Fedora, run the following command to check whether
elfutils-libelf-devel is installed:

yum list installed | grep elfutils-libelf-devel

If you see the information about the library version, the library is installed.

66 © Acronis International GmbH, 2003-2024

Installing the packages from the repository
The following table lists how to install the required packages in various Linux distributions.

Linux Package How to install

distribution names

Red Hat kernel- The setup program will download and install the packages automatically
Enterprise devel by using your Red Hat subscription.
Linux gcc
make
elfutils-
libelf-devel

perl Run the following command:

yum install perl

CentOS kernel- The setup program will download and install the packages
devel automatically.
Fedora
gcc
make
elfutils-
libelf-devel

perl Run the following command:

yum install perl

Ubuntu linux- Run the following commands:

headers
Debian
linux-image sudo apt-get update
gcc sudo apt-get install linux-headers-$(uname -r)
sudo apt-get install linux-image-$(uname -r)
make sudo apt-get install gcc-<package version>
perl sudo apt-get install make
sudo apt-get install perl

SUSE Linux kernel-

sudo zypper install kernel-source
source sudo zypper install gcc
OpenSUSE
gcc sudo zypper install make
make sudo zypper install perl
perl

The packages will be downloaded from the distribution's repository and installed.

For other Linux distributions, please refer to the distribution's documentation regarding the exact
names of the required packages and the ways to install them.

67 © Acronis International GmbH, 2003-2024

Installing the packages manually
You may need to install the packages manually if:

l The machine does not have an active Red Hat subscription or Internet connection.
l The setup program cannot find the kernel-devel or gcc version corresponding to the kernel
version. If the available kernel-devel is more recent than your kernel, you need to either update
the kernel or install the matching kernel-devel version manually.
l You have the required packages on the local network and do not want to spend time for
automatic search and downloading.

Obtain the packages from your local network or a trusted third-party website, and install them as
follows:

l In Red Hat Enterprise Linux, CentOS, or Fedora, run the following command as the root user:

rpm -ivh PACKAGE_FILE1 PACKAGE_FILE2 PACKAGE_FILE3

l In Ubuntu, run the following command:

sudo dpkg -i PACKAGE_FILE1 PACKAGE_FILE2 PACKAGE_FILE3

Example: Installing the packages manually in Fedora 14

Follow these steps to install the required packages in Fedora 14 on a 32-bit machine:

1. Run the following command to determine the kernel version and the required GCC version:

cat /proc/version

The output of this command includes the following:

Linux version 2.6.35.6-45.fc14.i686

gcc version 4.5.1

2. Obtain the kernel-devel and gcc packages that correspond to this kernel version:

kernel-devel-2.6.35.6-45.fc14.i686.rpm
gcc-4.5.1-4.fc14.i686.rpm

3. Obtain the make package for Fedora 14:

make-3.82-3.fc14.i686

4. Install the packages by running the following commands as the root user:

rpm -ivh kernel-devel-2.6.35.6-45.fc14.i686.rpm

rpm -ivh gcc-4.5.1.fc14.i686.rpm
rpm -ivh make-3.82-3.fc14.i686

68 © Acronis International GmbH, 2003-2024

 You can specify all these packages in a single rpm command. Installing any of these packages may
require installing additional packages to resolve dependencies.

Configuring proxy server settings

The protection agents can transfer data through an HTTP/HTTPS proxy server. The server must work
through an HTTP tunnel without scanning or interfering with the HTTP traffic. Man-in-the-middle
proxies are not supported.

Because the agent registers itself in the cloud during the installation, you must configure the proxy
server settings during the installation of the agent or in advance.

For Windows

If a proxy server is configured in Control panel > Internet Options > Connections, the setup
program reads the proxy server settings from the registry and uses them automatically.

Use this procedure if you want to perform the following tasks.

l Configure the proxy settings before the installation of the agent.

l Update the proxy settings after the installation of the agent.

To configure the proxy settings during the installation of the agent, see "Installing protection agents
in Windows" (p. 73).

Note
This procedure is valid only when the http-proxy.yaml file does not exist on the machine. If the
http-proxy.yaml file exists on the machine, you must update the proxy settings in the file, as it
overrides the settings in the aakore.yaml file.

The %programdata%\Acronis\Agent\var\aakore\http-proxy.yaml file is created when you configure

the proxy server settings by using Cyber Protection Monitor. For more information, see "Configuring
proxy server settings in Cyber Protect Monitor" (p. 297).

To open the http-proxy.yaml file, you must be member of the Administrators group in Windows.

To configure the proxy settings

1. Create a new text document and open it in a text editor, such as Notepad.
2. Copy and paste the following lines into the file.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Acronis\Global\HttpProxy]
"Enabled"=dword:00000001
"Host"="proxy.company.com"
"Port"=dword:000001bb
"Login"="proxy_login"
"Password"="proxy_password"

69 © Acronis International GmbH, 2003-2024

 3. Replace proxy.company.com with your proxy server host name/IP address, and 000001bb with the
hexadecimal value of the port number. For example, 000001bb is port 443.
4. If your proxy server requires authentication, replace proxy_login and proxy_password with the
proxy server credentials. Otherwise, delete these lines from the file.
5. Save the document as proxy.reg.
6. Run the file as an administrator.
7. Confirm that you want to edit the Windows registry.
8. If the agent is not installed on this workload yet, install it now. If the agent is already installed on
the workload, continue to the next step.
9. Open the %programdata%\Acronis\Agent\etc\aakore.yaml file in a text editor.
To open this file, you must be member of the Administrators group in Windows.
10. Locate the env section or create it, and then add the following lines.

env:
http-proxy: proxy_login:proxy_password@proxy_address:port
https-proxy: proxy_login:proxy_password@proxy_address:port

11. Replace proxy_login and proxy_password with the proxy server credentials, and proxy_
address:port with the address and port number of the proxy server.
12. In the Start menu, click Run, type: cmd, and then click OK.
13. Restart the aakore service by running the following commands.

net stop aakore

net start aakore

14. Restart the agent by running the following commands.

net stop mms

net start mms

For macOS

Use this procedure if you want to perform the following tasks.

l Configure the proxy settings before the installation of the agent.

l Update the proxy settings after the installation of the agent.

To configure the proxy settings during the installation of the agent, see "Installing protection agents
in macOS" (p. 78).

To configure the proxy settings

1. Create the /Library/Application Support/Acronis/Registry/Global.config file and open it in a

text editor, such as Text Edit.
2. Copy and paste the following lines into the file.

<?xml version="1.0" ?>

<registry name="Global">

70 © Acronis International GmbH, 2003-2024

 <key name="HttpProxy">
<value name="Enabled" type="Tdword">"1"</value>
<value name="Host" type="TString">"proxy.company.com"</value>
<value name="Port" type="Tdword">"443"</value>
<value name="Login" type="TString">"proxy_login"</value>
<value name="Password" type="TString">"proxy_password"</value>
</key>
</registry>

3. Replace proxy.company.com with your proxy server host name/IP address, and 443 with the
decimal value of the port number.
4. If your proxy server requires authentication, replace proxy_login and proxy_password with the
proxy server credentials. Otherwise, delete these lines from the file.
5. Save the file.
6. If the agent is not installed on this workload yet, install it now. If the agent is already installed on
the workload, continue to the next step.
7. Open the /Library/Application Support/Acronis/Agent/etc/aakore.yaml file in a text editor.
8. Locate the env section or create it and then add the following lines.

env:
http-proxy: proxy_login:proxy_password@proxy_address:port
https-proxy: proxy_login:proxy_password@proxy_address:port

9. Replace proxy_login and proxy_password with the proxy server credentials, and proxy_
address:port with the address and port number of the proxy server.
10. Go to Applications > Utilities > Terminal.
11. Restart the aakore service by running the following commands.

sudo launchctl stop aakore

sudo launchctl start aakore

12. Restart the agent by running the following commands.

sudo launchctl stop acronis_mms

sudo launchctl start acronis_mms

For Linux

Run the installation file with the --http-proxy-host=ADDRESS --http-proxy-port=PORT --http-proxy-

login=LOGIN --http-proxy-password=PASSWORD parameters. Use the following procedure to update
the proxy settings after the installation of the protection agent.

To configure the proxy settings

1. Open the /etc/Acronis/Global.config file in a text editor.

2. Do one of the following:

71 © Acronis International GmbH, 2003-2024

 l If the proxy settings were specified during the agent installation, locate the following section.

<key name="HttpProxy">
<value name="Enabled" type="Tdword">"1"</value>
<value name="Host" type="TString">"ADDRESS"</value>
<value name="Port" type="Tdword">"PORT"</value>
<value name="Login" type="TString">"LOGIN"</value>
<value name="Password" type="TString">"PASSWORD"</value>
</key>

l If the proxy settings were not specified during the agent installation, copy the following lines
and paste them into the file between the <registry name="Global">...</registry> tags.

<key name="HttpProxy">
<value name="Enabled" type="Tdword">"1"</value>
<value name="Host" type="TString">"ADDRESS"</value>
<value name="Port" type="Tdword">"PORT"</value>
<value name="Login" type="TString">"LOGIN"</value>
<value name="Password" type="TString">"PASSWORD"</value>
</key>

3. Replace ADDRESS with the new proxy server host name/IP address, and PORT with the decimal
value of the port number.
4. If your proxy server requires authentication, replace LOGIN and PASSWORD with the proxy server
credentials. Otherwise, delete these lines from the file.
5. Save the file.
6. Open file /opt/acronis/etc/aakore.yaml in a text editor.
7. Locate the env section or create it and add the following lines:

env:
http-proxy: proxy_login:proxy_password@proxy_address:port
https-proxy: proxy_login:proxy_password@proxy_address:port

8. Replace proxy_login and proxy_password with the proxy server credentials, and proxy_
address:port with the address and port number of the proxy server.
9. Restart the aakore service by running the following command.

sudo service aakore restart

10. Restart the agent by executing the running command in any directory.

sudo service acronis_mms restart

For bootable media

When working under bootable media, you might need to access the cloud storage via a proxy
server. To configure the proxy server settings, click Tools > Proxy server, and then configure the
proxy server host name/IP address, port, and credentials.

72 © Acronis International GmbH, 2003-2024

Installing protection agents
You can install agents on machines running any of the operating systems listed in "Supported
operating systems and environments". The operating systems that support the Cyber Protect
features are listed in "Supported Cyber Protect features by operating system".

Downloading protection agents

Before you install an agent, you must download its installation file from the Cyber Protect console.

To download an agent while adding a workload to protect

1. In the Cyber Protect console, navigate to Devices > All devices.

2. In the upper right, click Add device.
3. In the Add devices panel, from the Release channel drop-down menu, select an agent version.
l Previous release - download the agent version from the previous release.
l Current - download the latest available agent version.
4. Select the agent that corresponds to the operating system of the workload that you are adding.
The Save As dialog opens.
5. [Only for Macs with Apple silicon (such as Apple M1) processors] Click Cancel. In the Add Mac
panel that opens, click the Download ARM installer link.
6. Select a location to save the agent installation file and click Save.

To download an agent for later use

1. In the upper right corner of the Cyber Protect console, click the User icon.
2. Click Downloads.
3. In the Downloads dialog, from the Release channel drop-down menu, select an agent version.
l Previous release - download the agent version from the previous release.
l Current - download the latest available agent version.
4. Scroll the list of available installers to locate the agent installer that you need and click the
download icon at the end of its row.
The Save As dialog opens.
5. Select a location to save the agent installation file and click Save.

Installing protection agents in Windows

Prerequisites

Download the agent that you need on the workload that you plan to protect. See "Downloading
protection agents" (p. 73).

To install Agent for Windows

1. Ensure that the machine is connected to the Internet.

2. Log on as an administrator and start the installer.

73 © Acronis International GmbH, 2003-2024

3. [Optional] Click Customize installation settings and make the appropriate changes if you want:
l To change the components to install (for example, to disable the installation of Cyber
Protection Monitor or the Command-Line Tool, or to install the Agent for Antimalware
protection or the Agent for URL filtering).

Note
On Windows machines, the antimalware protection feature requires the installation of Agent
for Antimalware protection, and the URL filtering feature requires the installation of Agent for
URL filtering. These agents are installed automatically for protected workloads if the
Antivirus & Antimalware protection and/or the URL filtering modules are enabled in their
protection plans.

l To change the method of registering the workload in the Cyber Protection service. You can
switch from Use service console (default) to Use credentials or Use registration token.
l To change the installation path.
l To change the user account under which the agent service will run. For details, refer to
"Changing the logon account on Windows machines" (p. 80).
l To verify or change the proxy server host name/IP address, port, and credentials. If a proxy
server is enabled in Windows, it is detected and used automatically.
4. Click Install.
5. [Only when installing Agent for VMware] Specify the address and access credentials for the
vCenter Server or the stand-alone ESXi host on which you want to back up and recover virtual
machines, and then click Done.
We recommend that you use a dedicated account for accessing vCenter Server or the ESXi host,
instead of using an existing account with the Administrator role. To learn more about the
required privileges for the dedicated account, refer to "Agent for VMware – necessary privileges"
(p. 666).
6. [Only when installing on a domain controller] Specify the user account under which the agent
service will run, and then click Done. For security reasons, the setup program does not
automatically create new accounts on a domain controller.

Note
The user account that you specify must be granted the Log on as a service right. This account
must have already been used on the domain controller, in order for its profile folder to be
created on that machine.

For more information about installing the agent on a read-only domain controller, see this
knowledge base article.
7. If you kept the default registration method Use service console in step 3, wait until the
registration screen appears, and then proceed to the next step. Otherwise, no more actions are
required.
8. Do one of the following:

74 © Acronis International GmbH, 2003-2024

 l If you log in under a company administrator account, register workloads for your company:
a. Click Register workload.
b. In the opened browser window, sign in to the Cyber Protect console and review the
registration details.
c. In the Register for account list, select the user account under which you want to register
the workload.
d. Click Check code, and then click Confirm registration.
l If you log in under a partner administrator account, register workloads for your customers:
a. Click Register workload.
b. In the opened browser window, sign in to the Cyber Protect console and review the
registration details.
c. In the Register for account list, select the user account of your customer under which you
want to register the workload.
d. Click Check code, and then click Confirm registration.
l Click Show registration info. The setup program shows the registration link and the
registration code. If you cannot complete the workload registration on the current machine,
copy the registration link and code, and then follow the registration steps on a different
machine. In this case, you will need to enter the registration code in the registration form. The
registration code is valid for one hour.
Alternatively, you can access the registration form by clicking All devices > Add, scrolling
down to Registration via code, and then clicking Register.

Note
Do not quit the setup program until you confirm the registration. To initiate the registration
again, you will have to restart the setup program and repeat the installation procedure.

As a result, the workload will be assigned to the account that was used to log in to the Cyber
Protect console.
l Register the workload manually by using the command line. For more information on how to
do this, refer to "Registering and unregistering workloads manually" (p. 115).
9. [If the agent is registered under an account whose tenant is in the Compliance mode] Set the
encryption password.

Installing protection agents in Linux

Preparation
l Download the agent that you need on the machine that you plan to protect. See "Downloading
protection agents" (p. 73).
l Ensure that the necessary Linux packages are installed on the machine.
l When installing the agent in SUSE Linux, ensure that you use su - instead of sudo. Otherwise, the
following error occurs when you try to register the agent via the Cyber Protect console: Failed to
launch the web browser. No display available.

75 © Acronis International GmbH, 2003-2024

 Some Linux distributions, such as SUSE, do not pass the DISPLAY variable when using sudo, and
the installer cannot open the browser in the graphical user interface (GUI).

Installation
To install Agent for Linux, you need at least 2 GB of free disk space.

To install Agent for Linux

1. Ensure that the machine is connected to the Internet.

2. As the root user, navigate to directory with the installation file, make the file executable, and
then run it.

chmod +x <installation file name>

./<installation file name>

If a proxy server is enabled in your network, when running the installation file, specify the server
host name/IP address and port in the following format: --http-proxy-host=ADDRESS --http-
proxy-port=PORT --http-proxy-login=LOGIN --http-proxy-password=PASSWORD.
If you want to change the default method of registering the machine in the Cyber Protection
service, run the installation file with one of the following parameters:
l --register-with-credentials – to ask for a user name and password during the installation
l --token=STRING – to use a registration token
l --skip-registration – to skip the registration
3. Select the check boxes for the agents that you want to install. The following agents are available:
l Agent for Linux
l Agent for Virtuozzo
l Agent for Oracle
l Agent for MySQL/MariaDB
Agent for Virtuozzo, Agent for Oracle, and Agent for MySQL/MariaDB require that Agent for Linux
(64-bit) is also installed.
4. If you kept the default registration method in step 2, proceed to the next step. Otherwise, enter
the user name and password for the Cyber Protection service, or wait until the machine will be
registered by using the token.
5. Do one of the following:
l If you log in under a company administrator account, register workloads for your company:
a. Click Register workload.
b. In the opened browser window, sign in to the Cyber Protect console and review the
registration details.
c. In the Register for account list, select the user account under which you want to register
the workload.
d. Click Check code, and then click Confirm registration.

76 © Acronis International GmbH, 2003-2024

 l If you log in under a partner administrator account, register workloads for your customers:
a. Click Register workload.
b. In the opened browser window, sign in to the Cyber Protect console and review the
registration details.
c. In the Register for account list, select the user account of your customer under which you
want to register the workload.
d. Click Check code, and then click Confirm registration.
l Click Show registration info. The setup program shows the registration link and the
registration code. If you cannot complete the workload registration on the current machine,
copy the registration link and code, and then follow the registration steps on a different
machine. In this case, you will need to enter the registration code in the registration form. The
registration code is valid for one hour.
Alternatively, you can access the registration form by clicking All devices > Add, scrolling
down to Registration via code, and then clicking Register.

Note
Do not quit the setup program until you confirm the registration. To initiate the registration
again, you will have to restart the setup program and repeat the installation procedure.

As a result, the workload will be assigned to the account that was used to log in to the Cyber
Protect console.
l Register the workload manually by using the command line. For more information on how to
do this, refer to "Registering and unregistering workloads manually" (p. 115).

6. [If the agent is registered under an account whose tenant is in the Compliance mode] Set the
encryption password.
7. If the UEFI Secure Boot is enabled on the machine, you are informed that you need to restart the
system after the installation. Be sure to remember what password (the one of the root user or
"acronis") should be used.

Note
The installation generates a new key that is used for signing the kernel modules. You must enroll
this new key to the Machine Owner Key (MOK) list by restarting the machine. Without enrolling
the new key, your agent will not be operational. If you enable the UEFI Secure Boot after the
agent is installed, you need to reinstall the agent.

8. After the installation completes, do one of the following:

l Click Restart, if you were prompted to restart the system in the previous step.
During the system restart, opt for MOK (Machine Owner Key) management, choose Enroll
MOK, and then enroll the key by using the password recommended in the previous step.
l Otherwise, click Exit.

Troubleshooting information is provided in the file:

/usr/lib/Acronis/BackupAndRecovery/HOWTO.INSTALL

77 © Acronis International GmbH, 2003-2024

Installing protection agents in macOS
Prerequisites

Download the agent that you need on the workload that you plan to protect. See "Downloading
protection agents" (p. 73).

To install Agent for Mac (x64 or ARM64)

1. Ensure that the machine is connected to the Internet.

2. Double-click the installation file (.dmg).
3. Wait while the operating system mounts the installation disk image.
4. Double-click Install.
5. If a proxy server is enabled in your network, click Protection Agent in the menu bar, click Proxy
server settings, and then specify the proxy server host name/IP address, port, and credentials.
6. If prompted, provide administrator credentials.
7. Click Continue.
8. Wait until the registration screen appears.
9. Do one of the following:
l If you log in under a company administrator account, register workloads for your company:
a. Click Register workload.
b. In the opened browser window, sign in to the Cyber Protect console and review the
registration details.
c. In the Register for account list, select the user account under which you want to register
the workload.
d. Click Check code, and then click Confirm registration.
l If you log in under a partner administrator account, register workloads for your customers:
a. Click Register workload.
b. In the opened browser window, sign in to the Cyber Protect console and review the
registration details.
c. In the Register for account list, select the user account of your customer under which you
want to register the workload.
d. Click Check code, and then click Confirm registration.
l Click Show registration info. The setup program shows the registration link and the
registration code. If you cannot complete the workload registration on the current machine,
copy the registration link and code, and then follow the registration steps on a different
machine. In this case, you will need to enter the registration code in the registration form. The
registration code is valid for one hour.
Alternatively, you can access the registration form by clicking All devices > Add, scrolling
down to Registration via code, and then clicking Register.

78 © Acronis International GmbH, 2003-2024

 Note
Do not quit the setup program until you confirm the registration. To initiate the registration
again, you will have to restart the setup program and repeat the installation procedure.

As a result, the workload will be assigned to the account that was used to log in to the Cyber
Protect console.
l Register the workload manually by using the command line. For more information on how to
do this, refer to "Registering and unregistering workloads manually" (p. 115).

10. [If the agent is registered under an account whose tenant is in the Compliance mode] Set the
encryption password.
11. If your macOS version is Mojave 10.14.x or later, grant full disk access to the protection agent to
enable backup operations.
For instructions, see Grant the 'Full Disk Access' permission to the Cyber Protection agent
(64657).
12. To use the remote desktop functionality, grant the required system permissions to the Connect
Agent. For more information, see "Granting the required system permissions to the Connect
Agent" (p. 79).

Granting the required system permissions to the Connect Agent

To enable all features from the remote desktop functionality on macOS workloads, in addition to
the full disk access permission, you must grant the following permissions to the Connect Agent:

l Screen Recording - enables screen recording of the macOS workload via NEAR. Until this
permission is granted, all remote control connections will be denied.
l Accessibility - enables remote connections in control mode via NEAR
l Microphone - enables sound redirection from the remote macOS workload to the local workload
via NEAR. To enable the sound redirection feature, a sound capture driver must be installed on
the workload. For more information, see "Remote sound redirection" (p. 944).
l Automation - enables the empty Recycle bin action

After you start the agent on the macOS workload, it will check if the agent has these rights and will
ask you to grant the permissions, if needed.

To grant the Screen Recording permission

1. In the Grant required system permissions for Cyber Protect Agent dialog, click Set up system
permissions.
2. In the System permissions dialog, click Request Screen Recording permission.
3. Click Open System Preferences.
4. Select Connect Agent.

If the agent does not have the permission when you try to access the workload remotely, it will show
the Screen Recording permission request dialog. Only the local user may answer the dialog.

79 © Acronis International GmbH, 2003-2024

To grant the Accessibility permission

1. In the Grant required system permissions for Cyber Protect Agent dialog, click Set up system
permissions.
2. In the System permissions dialog, click Request Accessibility permission.
3. Click Open System Preferences.
4. Click the lock icon in the bottom-left corner of the window so that it changes to an unlocked one.
The system will ask you for an administrator password to make changes.
5. Select Connect Agent.

To grant the Microphone permission

1. In the Grant required system permissions for the Connect Agent dialog, click Set up system
permissions.
2. In the System permissions dialog, click Request Microphone permission.
3. Click OK.

Note
You must also install a sound capture driver on the macOS workload to let the agent utilize the
given permission and redirect the sound of the workload. For more information, see "Remote
sound redirection" (p. 944).

To grant the Automation permission

1. In the Grant required system permissions for the Connect Agent dialog, click Set up system
permissions.
2. In the System permissions dialog, click Request Automation permission.

Changing the logon account on Windows machines

On the Select components screen, define the account under which the services will run by
specifying Logon account for the agent service. You can select one of the following:

l Use Service User Accounts (default for the agent service)

Service User Accounts are Windows system accounts that are used to run services. The
advantage of this setting is that the domain security policies do not affect these accounts' user
rights. By default, the agent runs under the Local System account.
l Create a new account
The account name will be Agent User for the agent.
l Use the following account
If you install the agent on a domain controller, the system prompts you to specify existing
accounts (or the same account) for the agent. For security reasons, the system does not
automatically create new accounts on a domain controller.
The user account that you specify when the setup program runs on a domain controller must be
granted the Log on as a service right. This account must have already been used on the domain
controller, in order for its profile folder to be created on that machine.

80 © Acronis International GmbH, 2003-2024

 For more information about installing the agent on a read-only domain controller, see this
knowledge base article.

If you chose the Create a new account or Use the following account option, ensure that the
domain security policies do not affect the related accounts' rights. If an account is deprived of the
user rights assigned during the installation, the component may work incorrectly or not work.

Privileges required for the logon account

A protection agent is run as a Managed Machine Service (MMS) on a Windows machine. The account
under which the agent will run must have specific rights for the agent to work correctly. Thus, the
MMS user should be assigned the following privileges:

1. Included in the Backup Operators and Administrators groups. On a Domain Controller, the
user must be included in the group Domain Admins.
2. Granted the Full Control permission on the folder %PROGRAMDATA%\Acronis (in Windows XP and
Server 2003, %ALLUSERSPROFILE%\Application Data\Acronis) and on its subfolders.
3. Granted the Full Control permission on certain registry keys in the following key: HKEY_LOCAL_
MACHINE\SOFTWARE\Acronis.
4. Assigned the following user rights:
l Log on as a service
l Adjust memory quotas for a process
l Replace a process level token
l Modify firmware environment values

How to assign the user rights

Follow the instructions below to assign the user rights (this example uses the Log on as service
user right, the steps are the same for other user rights):

1. Log on to the computer by using an account with administrative privileges.

2. Open Administrative Tools from Control Panel (or click Win+R, type control admintools, and
press Enter) and open Local Security Policy.
3. Expand Local Policies and click on User Rights Assignment.
4. In the right pane, right-click Log on as a service and select Properties.
5. Click on the Add User or Group… button to add a new user.
6. In the Select Users, Computers, Service Accounts, or Groups window, find the user you wish
to enter and click OK.
7. Click OK in the Log on as a service Properties to save the changes.

Important
Ensure that the user which you have added to the Log on as service user right is not listed in the
Deny log on as a service policy in Local Security Policy.

81 © Acronis International GmbH, 2003-2024

Note that we recommend that you do not change logon accounts manually after the installation is
completed.

Dynamic installation and uninstallation of components

For Windows workloads protected by agent version 15.0.26986 (released in May 2021) or later, the
following components are installed dynamically—that is, only when required by a protection plan:

l Agent for URL filtering—required for the operation of the URL filtering features.
l Agent for Antimalware protection—required for the operation of the antimalware protection
features.
l Agent for Data Loss Prevention—required for the operation of the device control features.

By default, these components are not installed. The respective component is automatically installed
if a workload becomes protected by a plan in which any of the following modules is enabled:

l Antivirus & Antimalware protection

l URL filtering
l Device control

Similarly, if no protection plan requires antimalware protection, URL filtering, or device control
features anymore, the respective component is automatically uninstalled.

Dynamic installation or uninstallation of components takes up to 10 minutes after you change the
protection plan. However, if any of the following operations are running, dynamic installation or
uninstallation will start after this operation finishes:

l Backup
l Recovery
l Backup replication
l Virtual machine replication
l Testing a replica
l Running a virtual machine from backup (including finalization)
l Disaster recovery failover
l Disaster recovery failback
l Running a script (for Cyber Scripting functionality)
l Patch installation
l ESXi configuration backup

Unattended installation or uninstallation

Unattended installation or uninstallation in Windows

In Windows, you can perform unattended installation or uninstallation in the following ways:

82 © Acronis International GmbH, 2003-2024

l By using the EXE file of the setup program and specifying the installation parameters on the
command line.
l By using an MSI file that you extract from the setup program, and specifying the installation
parameters in one of the following ways:
o In an MST file
o Directly on the command line

Unattended installation and uninstallation with an EXE file

For this type of unattended installation, download the setup program, and then start it from the
command line with the required installation parameters. To see the parameters that you can use,
see "Parameters for unattended installation (EXE)" (p. 85).

You do not need to extract installation packages, MSI, and MST files in advance.

Installing and uninstalling agents and components (EXE)

To perform unattended installation with an EXE file, run the setup program and specify the
installation parameters on the command line.

To download the setup program, in the Cyber Protect console, click the account icon in the top-right
corner, and then click Downloads. The download link is also available in the Add devices pane.

To install agents and components

1. Start the command-line interface as administrator, and then navigate to the EXE file of the setup
program.
2. To start the setup program and specify the installation parameters, run the following command:

<file path>/<EXE file><PARAMETER 1>=<value 1> ... <PARAMETER N>=<value n>

Use spaces to separate the parameters, and commas without spaces to separate the values for a
parameter. For example:

C:\Users\Administrator\Downloads\AgentForWindows_web.exe --add-
components=agentForWindows,agentForSql,commandLine --install-dir="C:\Program
Files\BackupClient" --reg-address=https://eu2-cloud.company.com --reg-token=34F6-
8C39-4A5C --quiet

To check the available parameters and their values, see "Parameters for unattended installation
(EXE)" (p. 85).

Examples
l Installing Agent for Windows, Agent for Antimalware, Agent for URL filtering, Command-Line Tool,
and Cyber Protect Monitor. Registering the workload in the Cyber Protection service by using a
user name and password.

83 © Acronis International GmbH, 2003-2024

 C:\Users\Administrator\Downloads\AgentForWindows_web.exe --add-
components=agentForWindows,agentForAmp,commandLine,trayMonitor --install-
dir="C:\Program Files\BackupClient" --agent-account=system --reg-
address=https://cloud.company.com --reg-login=johndoe --reg-password=johnspassword

l Installing Agent for Windows, Command-Line Tool, and Cyber Protect Monitor. Creating a new
logon account for the agent service in Windows. Registering the workload in the Cyber Protection
service by using a token.

C:\Users\Administrator\Downloads\AgentForWindows_web.exe --add-
components=agentForWindows,commandLine,trayMonitor --install-dir="C:\Program
Files\BackupClient" --agent-account=new --reg-address=https://eu2-cloud.company.com -
-reg-token=34F6-8C39-4A5C

l Installing Agent for Windows, Command-Line Tool, Agent for Oracle and Cyber Protect Monitor.
Registering the machine in the Cyber Protection service by using a user name and password.

C:\Users\Administrator\Downloads\AgentForWindows_web.exe --add-
components=agentForWindows,commandLine,agentForOracle,trayMonitor --install-
dir="C:\Program Files\BackupClient" --language=en --agent-account=system --reg-
address=https://cloud.company.com --reg-login=johndoe --reg-password=johnspassword

l Installing Agent for Windows, Command-Line Tool, and Cyber Protect Monitor. Setting the user
interface language to German. Registering the machine in the Cyber Protection service by using a
token. Setting an HTTP proxy.

C:\Users\Administrator\Downloads\AgentForWindows_web.exe --add-
components=agentForWindows,commandLine,agentForOracle,trayMonitor --install-
dir="C:\Program Files\BackupClient"--language=de --agent-account=system --reg-
address=https://eu2-cloud.company.com --reg-token=34F6-8C39-4A5C --http-proxy-
address=https://my-proxy.company.com:80 --http-proxy-login=tomsmith --http-proxy-
password=tomspassword

To remove an installed component

1. Start the command-line interface as administrator, and then navigate to

%ProgramFiles%\BackupClient\RemoteInstall.
2. Run the following command:

web_installer.exe --remove-components=<value 1>,<value 2> --quiet

To check the available parameters and their values, see "Parameters for unattended installation
(EXE)" (p. 85).

84 © Acronis International GmbH, 2003-2024

Example
l Uninstalling the Cyber Protect Monitor.

C:\Program Files\BackupClient\RemoteInstall\web_installer.exe --remove-

components=trayMonitor --quiet

To uninstall an agent

1. Start the command-line interface as administrator, and then navigate to %Program Files%\Common
Files\Acronis\BackupAndRecovery.
2. Run the following command:

Uninstaller.exe --quiet --delete-all-settings

To check the available parameters and their values, see "Parameters for unattended installation
(EXE)" (p. 85).

Examples
l Uninstalling Agent for Windows and all its components. Deleting all logs, tasks, and configuration
settings.

C:\Program Files\Common Files\Acronis\BackupAndRecovery\Uninstaller.exe --quiet --

delete-all-settings

l Uninstalling a password-protected Agent for Windows and all its components. Deleting all logs,
tasks, and configuration settings.

C:\Program Files\Common Files\Acronis\BackupAndRecovery\Uninstaller.exe --anti-

tamper-password=<password> --quiet --delete-all-settings

Parameters for unattended installation (EXE)

The following table summarizes the parameters for unattended installation with an EXE file.

Parameters Description

General parameters

--add- The components to be installed. See the full list of

components= available components in "Components for unattended
<component1,component2,...,componentN> installation (EXE)" (p. 90).

When you specify multiple components, separate them

with commas. Do not add spaces before or after the
comma.

If you specify components that are already installed,

85 © Acronis International GmbH, 2003-2024

 Parameters Description

these components will be repaired or updated,

depending on version of the setup program and the
version of the installed components.

If you do not specify this parameter, a default set of

components will be installed, depending on the machine
on which you perform the installation. For example,
Agent for SQL is only installed on machines that run MS
SQL Server.

--install-dir=<path> The folder in which the selected components will be

installed. If the specified folder does not exist, it will be
created.

If you do not specify this parameter, a default folder is

used: C:\Program Files\BackupClient.

--log-dir=<path> The folder in which the installation logs will be saved.

If you do not specify this parameter, a default folder is

used: %ProgramData%\Acronis\InstallationLogs.

--language=<code> The product language.

The following values are available: en, bn, bg, cs, da, de,
es, fr, ko, id, it, hi, hu, ms, nl, ja, nb, pl, pt, pt_BR, ru, fi, sr,
sv, th, tr, vi, zh, zh_TW.

If you do not specify this parameter, and the system

language of the machine on which you perform the
installation is listed above, the system language is used.
In all other cases, the value is set to en.

--quiet Use this parameter to run the setup program without

showing the graphical user interface.

Do not use it together with the --register-only

parameter.

--help Use this parameter to see a list of all available

parameters that you can use on the command line and
their descriptions.

--fss-onboarding-auto-start Use this parameter together with the --quiet parameter

to show the File Sync & Share on-boarding wizard after
an unattended installation.

Registration parameters

--registration={skip | by-credentials | by- Use this parameter to choose how to register the agent
token | device-flow} after the installation.

86 © Acronis International GmbH, 2003-2024

 Parameters Description

To skip the registration, specify skip. You can register the

agent later, by using the --register-only parameter.

To register the agent by using credentials, specify by-

credentials, and then use the --reg-login and --reg-
password parameters. Also, you can use only --reg-login
and --reg-password parameters, which makes specifying
--registration=by-credentials optional.

To register the agent with a registration token, specify

by-token, and then use the --reg-token parameter. Also,
you can use only the --reg-token parameter, which
makes specifying --registration=by-token optional.

To register the agent by using the OAuth 2.0 protocol,

specify device-flow. After the installation completes, the
registration page opens automatically.

When you use --registration=device-flow, specify the

exact datacenter address as a value for the --reg-
address parameter. This is the URL that you see after
you log in to the Cyber Protection service. For example,
https://eu2-cloud.company.com.

Do not use --registration=device-flow with the --quiet

parameter.

--reg-address=<url> The URL of the Cyber Protection service. You can use this
parameter either with the --reg-login and --reg-
password parameters, or with the --reg-token parameter.

l When you use it with --reg-login and --reg-password

parameters, specify the address that you use to log
in to the Cyber Protection service. For example,
https://cloud.company.com:

l When you use it with the --reg-token parameter,

specify the exact datacenter address. This is the URL
that you see after you log in to the Cyber Protection
service. For example, https://eu2-cloud.company.com.

Do not use https://cloud.company.com with the --reg-

87 © Acronis International GmbH, 2003-2024

 Parameters Description

token parameter.

--reg-login=<login> The credentials for the account under which the agent
will be registered in the Cyber Protection service. This
--reg-password=<password>
cannot be a partner administrator account.

When you use these parameters, specifying the --

registration parameter is optional.

Do not use these parameters with the --reg-token

parameter.

--reg-token=<token> The registration token.

The registration token is a series of 12 characters,

separated into three segments by hyphens. For more
information about how to generate one, see "Generating
a registration token" (p. 162).

When you use this parameter, specifying the --

registration parameter is optional.

Do not use this parameter with the --reg-login and --

reg-password parameters.

--register-only Use this parameter to skip the installation and register

the agent by using the OAuth 2.0 protocol (device-flow).

After the installation completes, the registration page

opens automatically.

Do not use --register-only with the --quiet parameter.

Logon account for the agent service

--agent-account={system | new | custom} Use this parameter to specify the logon account under
which agent service will run. For more information about
or
the logon accounts, see "Changing the logon account on
--agent-account-login=<login> Windows machines" (p. 80).

--agent-account-password=<password> To use the Local System account, specify --agent-

account=system or do not use the --agent-account
parameter in your command.

To make the agent service run under a new logon

account, Acronis Agent User, which is created
automatically, specify new.

To make the agent service run under an existing

account, specify the account credentials by using the --
agent-account-login and --agent-account-password
parameters. In this case, specifying the --agent-

88 © Acronis International GmbH, 2003-2024

 Parameters Description

account=custom parameter is optional.

vCenter/ESXi parameters

--esxi-address=<host> The host name or IP address of vCenter Server or the

ESXi host.

Use this parameter when you install Agent for VMware.

--esxi-login=<login> The access credentials to vCenter Server or the ESXi host.

--esxi-password=<password> Use these parameters when you install Agent for

VMware.

Proxy parameters

--http-proxy={none | system | custom} Use this parameter to specify the HTTP proxy server that
you want to use for backup to and recovery from the
cloud storage.

If disable the proxy server connections, specify --http-

proxy=none.

To use a system-wide proxy server, specify --http-

proxy=system or do not use the --http-proxy parameter
in your command.

To use another proxy server, specify the proxy server

address and credentials by using the --http-proxy-
address, --http-proxy-login, and --http-proxy-password
parameters. In this case, specifying --http-proxy=custom
parameter is optional.

--http-proxy-address=<host>:<port> The hostname or IP address, and the port of the custom

HTTP proxy server.

--http-proxy-login=<login> Login for the custom HTTP proxy server.

--http-proxy-password=<password> Password for the custom HTTP proxy server.

Uninstallation parameters

--remove- The components to be uninstalled. See the full list of

components= available components in "Components for unattended
<component1,component2,...,componentN> installation (EXE)" (p. 90).

When you specify multiple components, separate them

with commas. Do not add spaces before or after the
comma.

89 © Acronis International GmbH, 2003-2024

 Parameters Description

Important
By using this parameter, you can uninstall only
components. To uninstall the product completely, go to
Windows Control Panel > Programs and Features, select
the product, and then click Uninstall.

--delete-all-settings Use this optional parameter when you use the --remove-
components parameter to delete all product logs, tasks,
and configuration settings.

--anti-tamper-password=<password> The password required for uninstalling a password-

protected Agent for Windows or modifying its
components.

Components for unattended installation (EXE)

The table below summarizes the components that you can use for unattended installation via an
EXE file. Use the value names to specify values for the --add-components parameter.

For more information, see "Parameters for unattended installation (EXE)" (p. 85)"Parameters for
unattended installation (MSI)" (p. 95)

Value name Component description

agentForWindows Agent for Windows

agentForSas Agent for Files Sync & Share

agentForAd Agent for Active Directory

agentForAmp Agent for Antimalware protection and Agent for

URL filtering

agentForDlp Agent for Data Loss Prevention

agentForEsx Agent for VMware (Windows)

agentForExchange Agent for Exchange

agentForHyperV Agent for Hyper-V

agentForOffice365 Agent for Office 365

agentForOracle Agent for Oracle

agentForSql Agent for SQL

commandLine Command-Line Tool

mediaBuilder Bootable Media Builder

90 © Acronis International GmbH, 2003-2024

 Value name Component description

trayMonitor Cyber Protect Monitor

all This value combines all components.

allAgents This value combines all agents.

Unattended installation and uninstallation with an MSI file

For this type of unattended installation, use the Windows Installer (the Msiexec program). Extract the
installation packages and the MSI file in advance, by using the graphical user interface of the setup
program.

When you install components with an MSI file, you can use an MST transform file to customize the
installation parameters. For more information on how to use the combination of MSI and MST files,
see "Installing agents and components (MSI and MST combination)" (p. 92). You can use this
installation method in an Active Directory domain to install protection agents by using Windows
Group Policy. For more information, see "Deploying agents through Group Policy" (p. 162).

Alternatively, you can specify the installation parameters manually on the command line. In this
case, you do not need an MST file. For more information, see "Examples" (p. 93).

Extracting the MSI, MST, and CAB files

Extract the MSI, MST, and CAB files with the installation packages by running the graphical user
interface of the setup program.

To extract the MSI, MST, and CAB files

1. Run the graphical user interface of the setup program, and then click Create .mst and .msi files
for unattended installation.
2. In What to install, select the components that you want to install, and then click Done.
The installation packages for these components will be extracted from the setup program as CAB
files.
3. In Registration settings, select Use credentials or Use registration token. Depending on your
choice, specify the credentials or the registration token, and then click Done.
For more information on how to generate a registration token, see "Generating a registration
token" (p. 162).
4. [Only when installing on a domain controller] In Logon account for the agent service, select
Use the following account. Specify the user account under which the agent service will run,
and then click Done. For security reasons, the setup program does not automatically create new
accounts on a domain controller.

91 © Acronis International GmbH, 2003-2024

 Note
The user account that you specify must be granted the Log on as a service right. This account
must have already been used on the domain controller, in order for its profile folder to be
created on that machine.

For more information about installing the agent on a read-only domain controller, see this
knowledge base article.
5. Review or modify other installation settings that will be added to the MST file, and then click
Proceed.
6. Select the folder in which the MSI, MST, and CAB files will be extracted, and then click Generate.

Installing agents and components (MSI and MST combination)

Use the MST file to customize the installation setting for the MSI file. Use the MSI and MST
combination when you install agents on multiple machines through a Windows Group Policy. For
more information, see "Deploying agents through Group Policy" (p. 162).

To install components with MSI and MST files

1. Extract the MSI and MST files as described in "Extracting the MSI, MST, and CAB files" (p. 91).
2. On the command-line interface of the machine on which you want to install components, run the
following command:

msiexec /i <MSI file> TRANSFORMS=<MST file>

For example:

msiexec /i BackupClient64.msi TRANSFORMS=BackupClient64.msi.mst

Installing and uninstalling agents and components (MSI and direct selection)
Run the MSI file, manually select the components to install, and specify their installation parameters
on the command line. In this case, you do not need the MST file.

To install agents and components

1. Extract the MSI file and the installation packages (CAB files) as described in "Extracting the MSI,
MST, and CAB files" (p. 91).
For this installation method, you only need the MSI and CAB files. You do not need the MST file.
2. In the command-line interface of the machine, run the following command:

msiexec /i <MSI file><PARAMETER 1>=<value 1> ... <PARAMETER N>=<value n>

Use spaces to separate the parameters, and commas without spaces to separate the values for a
parameter. For example:

92 © Acronis International GmbH, 2003-2024

 msiexec.exe /i BackupClient64.msi
ADDLOCAL=MmsMspComponents,BackupAndRecoveryAgent,CommandLineTool,TrayMonitor
TARGETDIR="C:\Program Files\BackupClient" REGISTRATION_ADDRESS=https://eu2-
cloud.company.com REGISTRATION_TOKEN=34F6-8C39-4A5C

To check the available parameters and their values, see "Parameters for unattended installation
(MSI)" (p. 95).

Examples
l Installing Agent for Windows, Agent for Antimalware, Agent for URL filtering, Command-Line Tool,
and Cyber Protect Monitor. Registering the workload in the Cyber Protection service by using a
user name and password.

msiexec.exe /i BackupClient64.msi /l*v my_log.txt /qn

ADDLOCAL=MmsMspComponents,BackupAndRecoveryAgent,AmpAgentFeature,CommandLineTool,Tray
Monitor TARGETDIR="C:\Program Files\BackupClient" REBOOT=ReallySuppress MMS_USE_
SYSTEM_ACCOUNT=1 REGISTRATION_ADDRESS=https://cloud.company.com REGISTRATION_
LOGIN=johndoe REGISTRATION_PASSWORD=johnspassword

l Installing Agent for Windows, Command-Line Tool, and Cyber Protect Monitor. Creating a new
logon account for the agent service in Windows. Registering the workload in the Cyber Protection
service by using a token.

msiexec.exe /i BackupClient64.msi /l*v my_log.txt /qn

ADDLOCAL=MmsMspComponents,BackupAndRecoveryAgent,CommandLineTool,TrayMonitor
TARGETDIR="C:\Program Files\BackupClient" REBOOT=ReallySuppress MMS_CREATE_NEW_
ACCOUNT=1 REGISTRATION_ADDRESS=https://eu2-cloud.company.com REGISTRATION_TOKEN=34F6-
8C39-4A5C

l Installing Agent for Windows, Command-Line Tool, Agent for Oracle and Cyber Protect Monitor.
Registering the machine in the Cyber Protection service by using a user name and encoded in
base64 password. You might need to encode your password if it contains special characters or
blank spaces. For more information about how to encode a password, see "Passwords with
special characters or blank spaces" (p. 119).

msiexec.exe /i BackupClient64.msi /l*v my_log.txt /qn

ADDLOCAL=MmsMspComponents,BackupAndRecoveryAgent,CommandLineTool,OracleAgentFeature,T
rayMonitor TARGETDIR="C:\Program Files\BackupClient" REBOOT=ReallySuppress CURRENT_
LANGUAGE=en MMS_USE_SYSTEM_ACCOUNT=1 REGISTRATION_ADDRESS=https://cloud.company.com
REGISTRATION_LOGIN=johndoe REGISTRATION_PASSWORD_ENCODED=am9obnNwYXNzd29yZA==

l Installing Agent for Windows, Command-Line Tool, and Cyber Protect Monitor. Registering the
machine in the Cyber Protection service by using a token. Setting an HTTP proxy.

msiexec.exe /i BackupClient64.msi /l*v my_log.txt /qn

ADDLOCAL=MmsMspComponents,BackupAndRecoveryAgent,CommandLineTool,TrayMonitor
TARGETDIR="C:\Program Files\BackupClient" REBOOT=ReallySuppress CURRENT_LANGUAGE=en
MMS_USE_SYSTEM_ACCOUNT=1 REGISTRATION_ADDRESS=https://eu2-cloud.company.com

93 © Acronis International GmbH, 2003-2024

 REGISTRATION_TOKEN=34F6-8C39-4A5C HTTP_PROXY_ADDRESS=https://my-proxy.company.com
HTTP_PROXY_PORT=80 HTTP_PROXY_LOGIN=tomsmith HTTP_PROXY_PASSWORD=tomspassword

To remove an installed component

1. Extract the MSI file and the installation packages (CAB files) as described in "Extracting the MSI,
MST, and CAB files" (p. 91).
For this installation method, you only need the MSI and CAB files. You do not need the MST file.
2. In the command-line interface of the machine, run the following command:

msiexec /i <MSI file><REMOVE>=<value 1>,<value 2> REBOOT=ReallySuppress /qn

To check the available parameters and their values, see "Parameters for unattended installation
(MSI)" (p. 95).

Example
l Removing Cyber Protect monitor.

msiexec.exe /i BackupClient64.msi /l*v uninstall_log.txt REMOVE=TrayMonitor

REBOOT=ReallySuppress /qn

To uninstall an agent

1. Extract the MSI file and the installation packages (CAB files) as described in "Extracting the MSI,
MST, and CAB files" (p. 91).
For this installation method, you only need the MSI and CAB files. You do not need the MST file.
2. In the command-line interface of the machine, run the following command:

msiexec /x <MSI file> /l*v uninstall_log.txt DELETE_ALL_SETTINGS=1

REBOOT=ReallySuppress /qn

To check the available parameters and their values, see "Parameters for unattended installation
(MSI)" (p. 95).

Examples
l Uninstalling Agent for Windows and all its components. Deleting all logs, tasks, and configuration
settings.

msiexec.exe /x BackupClient64.msi /l*v uninstall_log.txt DELETE_ALL_SETTINGS=1

REBOOT=ReallySuppress /qn

l Uninstalling a password-protected Agent for Windows and all its components. Deleting all logs,
tasks, and configuration settings.

msiexec.exe /x BackupClient64.msi /l*v uninstall_log.txt ANTI_TAMPER_

PASSWORD=<password> DELETE_ALL_SETTINGS=1 REBOOT=ReallySuppress /qn

94 © Acronis International GmbH, 2003-2024

Parameters for unattended installation (MSI)
The following table summarizes the parameters for unattended installation when you use an MSI
file.

You can also use additional msiexec parameters. For example, use /qn to prevent any GUI elements
from showing. To learn more about the msiexec parameters, see the Microsoft documentation.

Parameters Description

General parameters

ADDLOCAL= The components to be installed. See the full list of

<component1,component2,...,componentN> available components in "Components for unattended
installation (MSI)" (p. 98).

When you specify multiple components, separate them

with commas. Do not add spaces before or after the
comma.

Note
You must extract the installation files for all components
that you want to install. For more information about
how to extract them, see "Extracting the MSI, MST, and
CAB files" (p. 91).

TARGETDIR=<path> The folder in which the selected components will be

installed. If the specified folder does not exist, it will be
created.

If you do not specify this parameter, a default folder is

used: C:\Program Files\BackupClient.

REBOOT=ReallySuppress Specify this parameter if you want to install components

without restarting the machine.

/l*v <log file> Specify this parameter to save a verbose log. This log is
needed if you have to investigate installation issues.

CURRENT_LANGUAGE=<language ID> The product language.

The following values are available: en, bn, bg, cs, da, de,
es, fr, ko, id, it, hi, hu, ms, nl, ja, nb, pl, pt, pt_BR, ru, fi, sr,
sv, th, tr, vi, zh, zh_TW.

If you do not specify this parameter, and the system

language of the machine on which you perform the
installation is listed above, the system language is used.
In all other cases, the value is set to en.

SKIP_SHA2_KB_CHECK={0,1} Use this parameter to choose whether to check if the

95 © Acronis International GmbH, 2003-2024

 Parameters Description

SHA2 code signing support update from Microsoft

(KB4474419) is installed on the machine. The check only
runs on operating systems that require this update. To
see if it is required for your operating system, see
"Supported operating systems and environments" (p.
23).

Use this parameter with value set to 1 to skip the check.

If you do nоt specify the parameter or set its value to 0,

and the SHA2 code signing support update is not found
on the machine, the installation fails.

FSS_ONBOARDING_AUTO_START={0,1} Use this parameter with value set to 1 to show the File
Sync & Share on-boarding wizard after an unattended
installation.

If you do not specify this parameter or set its value to 0,

the on-boarding wizard will not be shown.

Registration parameters

REGISTRATION_ADDRESS The URL of the Cyber Protection service. You can use this
parameter either with the REGISTRATION_LOGIN and
REGISTRATION_PASSWORD parameters, or with
REGISTRATION_TOKEN.

l When you use it with REGISTRATION_LOGIN and

REGISTRATION_PASSWORD parameters, specify the
address that you use to log in to the Cyber Protection
service. For example, https://cloud.company.com:

l When you use it with the REGISTRATION_TOKEN

parameter, specify the exact datacenter address. This
is the URL that you see after you log in to the Cyber
Protection service. For example, https://eu2-
cloud.company.com.

Do not use https://cloud.company.com with the

REGISTRATION_TOKEN parameter.

REGISTRATION_LOGIN The credentials for the account under which the agent
will be registered in the Cyber Protection service. This
REGISTRATION_PASSWORD
cannot be a partner administrator account.

96 © Acronis International GmbH, 2003-2024

 Parameters Description

Do not use these parameters with the REGISTRATION_

TOKEN parameter.

REGISTRATION_PASSWORD_ENCODED The password for the account under which the agent will
be registered in the Cyber Protection service, encoded in
base64. For more information on how to encode your
password, see "Passwords with special characters or
blank spaces" (p. 119).

REGISTRATION_TOKEN The registration token.

The registration token is a series of 12 characters,

separated into three segments by hyphens. For more
information about how to generate one, see "Generating
a registration token" (p. 162).

Do not use this parameter with the REGISTRATION_LOGIN

and REGISTRATION_PASSWORD parameters.

REGISTRATION_REQUIRED={0,1} Use this parameter to choose what happens if the

registration fails.

If you set the value to 1, the installation also fails. If you

set the value to 0 or do not specify the parameter, the
installation completes successfully even though the
registration fails.

Logon account for the agent service

MMS_USE_SYSTEM_ACCOUNT={0,1} Use this parameter with value 1, to make the service run
under the Local System logon account.

For more information about the logon accounts, see

"Changing the logon account on Windows machines" (p.
80).

MMS_CREATE_NEW_ACCOUNT={0,1} Use this parameter with value 1, to make the agent

service run under a new logon account, Acronis Agent
User, which is created automatically.

MMS_SERVICE_USERNAME=<user name> Use these parameters to specify an existing logon

account under which the agent service will run.
MMS_SERVICE_PASSWORD=<password>

vCenter/ESXi parameters

SET_ESX_SERVER={0,1} Use this parameter when you install Agent for VMware.

If you set the value to 0, Agent for VMware will not be

connected to vCenter Server or an ESXi host.

If you set the value to 1, specify the following

97 © Acronis International GmbH, 2003-2024

 Parameters Description

parameters: ESX_HOST, EXI_USER, ESX_PASSWORD.

ESX_HOST=<host name> The host name or IP address of vCenter Server or the

ESXi host.

ESX_USER=<user name> The access credentials to vCenter Server or the ESXi host.

ESX_PASSWORD=<password>

Proxy parameters

HTTP_PROXY_ADDRESS=<IP address> Use these parameters to specify the HTTP proxy server
that the agent will use.
HTTP_PROXY_PORT=<port>
If you do not use a proxy server, do not specify these
parameters.

HTTP_PROXY_LOGIN=<login> The credentials for the HTTP proxy server.

HTTP_PROXY_PASSWORD=<password> Use these parameters if the proxy server requires

authentication.

Uninstallation parameters

REMOVE={<list of components>|ALL} The components to be uninstalled.

When you specify multiple components, separate them

with commas. Do not add spaces before or after the
comma.

To remove all product components, set the value to ALL.

DELETE_ALL_SETTINGS={0, 1} To delete all product logs, tasks, and configuration

settings, set the value to 1.

Use this optional parameter when you use the REMOVE

parameter.

ANTI_TAMPER_PASSWORD=<password> The password required for uninstalling a password-

protected Agent for Windows or modifying its
components.

Components for unattended installation (MSI)

The table below summarizes the components that you can use for unattended installation via an
MSI file. Use the value names to specify values for the ADDLOCAL parameter. For more information,
see "Parameters for unattended installation (MSI)" (p. 95).

Value name Component Must be installed Bitness

description together with

98 © Acronis International GmbH, 2003-2024

AgentFeature Core 32-bit/64-
components bit
for agents

MmsMspComponents Core AgentFeature 32-bit/64-

components bit
for backup

BackupAndRecoveryAgent Agent for MmsMspComponents 32-bit/64-

Windows bit

AmpAgentFeature Agent for BackupAndRecoveryAgent 32-bit/64-

Antimalware bit
protection

UrlFilteringAgentFeature Agent for URL BackupAndRecoveryAgent 32-bit/64-

Filtering bit

DlpAgentFeature Agent for Data BackupAndRecoveryAgent 32-bit/64-

Loss bit
Prevention

SasAgentFeature Agent for File TrayMonitor 32-bit/64-

Sync & Share bit

ArxAgentFeature Agent for MmsMspComponents 32-bit/64-

Exchange bit

ArsAgentFeature Agent for SQL BackupAndRecoveryAgent 32-bit/64-

bit

ARADAgentFeature Agent for BackupAndRecoveryAgent 32-bit/64-

Active bit
Directory

ArxOnlineAgentFeature Agent for MmsMspComponents 32-bit/64-

Microsoft 365 bit

OracleAgentFeature Agent for BackupAndRecoveryAgent 32-bit/64-

Oracle bit

AcronisESXSupport Agent for BackupAndRecoveryAgent 64-bit

VMware ESX(i)
(Windows)

HyperVAgent Agent for BackupAndRecoveryAgent 32-bit/64-

Hyper-V bit

CommandLineTool Command-Line 32-bit/64-

Tool bit

TrayMonitor Cyber Protect AgentFeature 32-bit/64-

99 © Acronis International GmbH, 2003-2024

 Monitor bit

BackupAndRecoveryBootableComponents Bootable 32-bit/64-

Media Builder bit

Unattended installation or uninstallation in Linux

This section describes how to install or uninstall protection agents in the unattended mode on a
machine running Linux, by using the command line.

To install an agent

1. Open Terminal.

2. Do one of the following:

l To start the installation by specifying the parameters on the command line, run the following
command:

<package name> -a <parameter 1> ... <parameter N>

Here, <package name> is the name of the installation package (an .i686 or an .x86_64 file). All
available parameters and their values are described in "Unattended installation or uninstallation
parameters" (p. 101).
l To start the installation with parameters that are specified in a separate text file, run the following
command:

<package name> -a --options-file=<path to the file>

This approach might be useful if you do not want to enter sensitive information on the command
line. In this case, you can specify the configuration settings in a separate text file and ensure that
only you can access it. Put each parameter on a new line, followed by the value for that
parameter, for example:

--rain=https://cloud.company.com
--login=johndoe
--password=johnspassword
--auto

or

-C
https://cloud.company.com
-g
johndoe
-w
johnspassword
-a
--language
en

100 © Acronis International GmbH, 2003-2024

 If the same parameter is specified both on the command line and in the text file, the command
line value precedes.

3. If UEFI Secure Boot is enabled on the machine, you are informed that you need to restart the
system after the installation. Ensure that you remember what password (that of the root user or
"acronis") should be used. During the system restart, opt for MOK (Machine Owner Key)
management, choose Enroll MOK, and then enroll the key by using the recommended password.

If you enable UEFI Secure Boot after the agent installation, repeat the installation, including step 3.
Otherwise, backups will fail.

To uninstall an agent

1. Open Terminal.
2. Do one of the following:
l To uninstall the agent and remove all logs, tasks, and configuration settings, run the following
command:

/usr/lib/Acronis/BackupAndRecovery/uninstall/uninstall -a

l To uninstall the agent but keep its ID (for example, if you plan to install the agent later), run
the following command:

/usr/lib/Acronis/BackupAndRecovery/uninstall/uninstall -a --no-purge

l To uninstall the agent by using the installation file, run the following command:

<package name> -a -u

Here, <package name> is the name of the installation package (an .i686 or an .x86_64 file). All
available parameters and their values are described in "Unattended installation or
uninstallation parameters" (p. 101).

Note
Use this command only when the installation package is the same version as the installed
agent and if /usr/lib/Acronis/BackupAndRecovery/uninstall/uninstall is corrupted or
inaccessible.

Unattended installation or uninstallation parameters

This section describes parameters that are used during unattended installation or uninstallation in
Linux.

The minimal configuration for unattended installation includes -a and registration parameters (for
example, --login and --password parameters; --rain and --token parameters). You can use more
parameters to customize you installation.

101 © Acronis International GmbH, 2003-2024

Installation parameters

Basic parameters
{-i |--id=}<list of components>

The components to be installed, separated by commas and without space characters. The
following components are available in the .x86_64 installation package:

Component Component description

BackupAndRecoveryAgent Agent for Linux

AgentForPCS Agent for Virtuozzo

OracleAgentFeature Agent for Oracle

MySQLAgentFeature Agent for MySQL/MariaDB

Without this parameter, all of the above components will be installed.

Agent for Virtuozzo, Agent for Oracle, and Agent for MySQL/MariaDB require that Agent for
Linux is also installed.

The .i686 installation package contains only BackupAndRecoveryAgent.

{-a|--auto}

The installation and registration process will complete without any further user interaction.
When using this parameter, you must specify the account under which the agent will be registered
in the Cyber Protection service, either by using the --token parameter, or by using the --login and -
-password parameters.

{-t|--strict}

If the parameter is specified, any warning that occurs during the installation results in
installation failure. Without this parameter, the installation completes successfully even in the case
of warnings.

{-n|--nodeps}

The absence of required Linux packages will be ignored during the installation.

{-d|--debug}

Writes the installation log in the verbose mode.

--options-file=<location>

The installation parameters will be read from a text file instead of the command line.

--language=<language ID>

102 © Acronis International GmbH, 2003-2024

 The product language. Available values are as follows: en, bg, cs, da, de, es, fr, hu, id,
it, ja, ko, ms, nb, nl, pl, pt, pt_BR, ru, fi, sr, sv, tr, zh, zh_TW.
If this parameter is not specified, the product language will be defined by your system language on
the condition that it is in the list above. Otherwise, the product language will set to English (en).

Registration parameters
Specify one of the following parameters:

l {-g|--login=}<user name> and {-w|--password=}<password>

Credentials for the account under which the agent will be registered in the Cyber Protection
service. This cannot be a partner administrator account.

l --token=<token>
The registration token is a series of 12 characters, separated by hyphens in three segments. You
can generate one in the Cyber Protect console, as described in "Deploying agents through Group
Policy".
You cannot use the --token parameter along with --login, --password, and --register-with-
credentials parameters.
o {-C|--rain=}<service address>
The URL of the Cyber Protection service.
You don't need to include this parameter explicitly when you use --login and --password
parameters for registration, because the installer uses the correct address by default – this
would be the address that you use to log in to the Cyber Protection service. For example:

However, when you use {-C|--rain=} with the --token parameter, you must specify the exact
datacenter address. This is the URL that you see once you are logged in to the Cyber
Protection service. For example:

l --register-with-credentials

If this parameter is specified, the installer's graphical interface will start. To finish the
registration, enter the user name and password for the account under which the agent will be
registered in the Cyber Protection service. This cannot be a partner administrator account.

l --skip-registration

Use this parameter if you need to install the agent but you plan to register it in the Cyber
Protection service later. For more information on how to do this, refer to "Registering machines
manually".

103 © Acronis International GmbH, 2003-2024

Additional parameters
--http-proxy-host=<IP address> and --http-proxy-port=<port>

The HTTP proxy server that the agent will use for backup and recovery from the cloud, and
for connection to the management server. Without these parameters, no proxy server will be used.

--http-proxy-login=<login> and --http-proxy-password=<password>

The credentials for the HTTP proxy server. Use these parameters if the server requires
authentication.

--tmp-dir=<location>

Specifies the folder where the temporary files are stored during the installation. The default
folder is /var/tmp.

{-s|--disable-native-shared}

Redistributable libraries will be used during the installation, even though they might have
already been present on your system.

--skip-prereq-check

There will be no check of whether the packages required for compiling the snapapi module
are already installed.

--force-weak-snapapi

The installer will not compile a snapapi module. Instead, it will use a ready-made module
that might not match the Linux kernel exactly. We do not recommend that you use this option.

--skip-svc-start

The services will not start automatically after the installation. Most often, this parameter is
used with the --skip-registration one.

Information parameters
{-?|--help}

Shows the description of parameters.

--usage

Shows a brief description of the command usage.

{-v|--version}

Shows the installation package version.

--product-info

Shows the product name and the installation package version.

--snapapi-list

104 © Acronis International GmbH, 2003-2024

 Shows the available ready-made snapapi modules.

--components-list

Shows the installer components.

Parameters for legacy features

These parameters relate to a legacy component, agent.exe.

{-e|--ssl=}<path>

Specifies the path to a custom certificate file for SSL communication.

{-p|--port=}<port>

Specifies the port on which agent.exe listens for connections. The default port is 9876.

Uninstallation parameters
{-u|--uninstall}

Uninstalls the product.

--purge

Uninstalls the product and removes its logs, tasks, and configuration settings. You don't
need to specify the --uninstall parameter explicitly when you use the --purge one.

Examples
l Installing Agent for Linux without registering it.

./Cyber_Protection_Agent_for_Linux_x86_64.bin -i BackupAndRecoveryAgent -a --skip-

registration

l Installing Agent for Linux, Agent for Virtuozzo, and Agent for Oracle, and registering them by
using credentials.

./Cyber_Protection_Agent_for_Linux_x86_64.bin -a --login=johndoe --
password=johnspassword

l Installing Agent for Oracle and Agent for Linux, and registering them by using a registration
token.

./Cyber_Protection_Agent_for_Linux_x86_64.bin -i
BackupAndRecoveryAgent,OracleAgentFeature -a --rain=https://eu2-cloud.company.com --
token=34F6-8C39-4A5C

l Installing Agent for Linux, Agent for Virtuozzo, and Agent for Oracle with configuration settings in
a separate text file.

105 © Acronis International GmbH, 2003-2024

 ./Cyber_Protection_Agent_for_Linux_x86_64.bin -a --options-
file=/home/mydirectory/configuration_file

l Uninstalling Agent for Linux, Agent for Virtuozzo, and Agent for Oracle, and removing all their
logs, tasks, and configuration settings.

./Cyber_Protection_Agent_for_Linux_x86_64.bin -a --purge

Unattended installation and uninstallation in macOS

This section describes how to install, register, and uninstall the protection agent in the unattended
mode on a machine running macOS, by using the command line.

Required permissions

Before you initiate an unattended installation on a Mac workload, you must modify the Privacy
Preferences Policy Control to allow App access and kernel and system extensions in the macOS of
the workload to enable the installation of the Cyber Protection agent. See "Required permissions for
unattended installation in macOS" (p. 107).

After you deploy the PPPC payload, you can proceed with the procedures below.

To download the installation file (.dmg)

1. In the Cyber Protect console, go to Devices > All devices.

2. Click Add, and then click Mac.

To install an agent

1. Open Terminal.
2. Create a temporary directory where you will mount the installation file (.dmg).

mkdir <dmg_root>

Here, <dmg_root> is a name of your choice.

3. Mount the .dmg file.

hdiutil attach <dmg_file> -mountpoint <dmg_root>

Here, <dmg_file> is the name of the installation file. For example, Cyber_Protection_Agent_for_
MAC_x64.dmg.
4. Run the installer.
l If you use a full installer for Mac, like CyberProtect_AgentForMac_x64.dmg or CyberProtect_
AgentForMac_arm64.dmg, run the following command.

sudo installer -pkg <dmg_root>/Install.pkg -target LocalSystem

106 © Acronis International GmbH, 2003-2024

 Note
If you need to enable auto-onboarding for File Sync & Share, run the following command
instead. This option will request the administrator password.

open <dmg_root>/Install.app --args --unattended --fss-onboarding-auto-start

l If you use an universal installer for Mac, like CyberProtect_AgentForMac_web.dmg, run the
following command.

sudo <dmg_root>/Install.app/Contents/MacOS/cyber_installer -a

5. Detach the installation file (.dmg).

hdiutil detach <dmg_root>

Example

mkdir mydirectory

hdiutil attach /Users/JohnDoe/Cyber_Protection_Agent_for_MAC_x64.dmg -mountpoint

mydirectory

sudo installer -pkg mydirectory/Install.pkg -target LocalSystem

hdiutil detach mydirectory

To uninstall an agent

1. Open Terminal.
2. Do one of the following:
l To uninstall the agent, run the following command:

sudo /Library/Application\ Support/BackupClient/Acronis/Cyber\ Protect\ Agent\

Uninstall.app/Contents/MacOS/AgentUninstall /confirm

l To uninstall the agent and remove all logs, tasks and configuration settings, run the following
command:

sudo /Library/Application\ Support/BackupClient/Acronis/Cyber\ Protect\ Agent\

Uninstall.app/Contents/MacOS/AgentUninstall /confirm /purge

Required permissions for unattended installation in macOS

Before you initiate an unattended installation on a Mac workload, you must modify the Privacy
Preferences Policy Control to allow App access and kernel and system extensions in the macOS of

107 © Acronis International GmbH, 2003-2024

the workload to enable the installation of the Cyber Protection agent. You can do this by deploying a
custom PPPC payload or by configuring the preferences in the graphical user interface of the
workload. The following permissions are required.

Requirements for macOS 11 (Big Sur) or later

Tab Section Field Value

108 © Acronis International GmbH, 2003-2024

Privacy App Access Identifier com.acronis.backup
Preferences
Policy Control

109 © Acronis International GmbH, 2003-2024

 Identifier Type Bundle ID

110 © Acronis International GmbH, 2003-2024

 Code identifier "com.acronis.backup" and anchor apple
Requirement generic and certificate 1[field.1.2.840.113635.100.6.2.6]
/* exists */ and certificate leaf
[field.1.2.840.113635.100.6.1.13] /* exists */ and
certificate leaf[subject.OU] = ZU2TV78AA6

APP OR SystemPolicyAllFiles
SERVICE

ACCESS Allow

App Access Identifier com.acronis.backup.aakore

Identifier Type Bundle ID

Code identifier "com.acronis.backup.aakore" and anchor

Requirement apple generic and certificate 1
[field.1.2.840.113635.100.6.2.6] /* exists */ and
certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists
*/ and certificate leaf[subject.OU] = ZU2TV78AA6

APP OR SystemPolicyAllFiles
SERVICE

ACCESS Allow

App Access Identified com.acronis.backup.activeprotection

Identifier Type Bundle ID

Code identifier "com.acronis.backup.activeprotection" and

Requirement anchor apple generic and certificate 1
[field.1.2.840.113635.100.6.2.6] /* exists */ and
certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists
*/ and certificate leaf[subject.OU] = ZU2TV78AA6

APP OR SystemPolicyAllFiles
SERVICE

ACCESS Allow

111 © Acronis International GmbH, 2003-2024

 App Access Identifier cyber-protect-service

Identifier Type Bundle ID

Code identifier "cyber-protect-service" and anchor apple

Requirement generic and certificate 1
[field.1.2.840.113635.100.6.2.6] /* exists */ and
certificate leaf[field.1.2.840.113635.100.6.1.13] /*
exists */ and certificate leaf[subject.OU] =
ZU2TV78AA6

APP OR SystemPolicyAllFiles
SERVICE

ACCESS Allow

System Allow users to Enabled

Extensions approve
system
extensions

Allowed Display Name Acronis Cyber Protection Agent System Extensions

Team IDs
and System
Extensions

System Allowed Team Identifiers

Extension
Types

Team Identifier ZU2TV78AA6

Requirements for macOS versions prior to version 11

Tab Section Field Value

112 © Acronis International GmbH, 2003-2024

Privacy App Access Identifier com.acronis.backup
Preferences
Policy Control

113 © Acronis International GmbH, 2003-2024

 Identifier Type Bundle ID

Code identifier "com.acronis.backup" and anchor apple

Requirement generic and certificate 1[field.1.2.840.113635.100.6.2.6]
/* exists */ and certificate leaf
[field.1.2.840.113635.100.6.1.13] /* exists */ and
certificate leaf[subject.OU] = ZU2TV78AA6

APP OR SERVICE SystemPolicyAllFiles

ACCESS Allow

App Access Identifier com.acronis.backup.aakore

Identifier Type Bundle ID

Code identifier "com.acronis.backup.aakore" and anchor

Requirement apple generic and certificate 1
[field.1.2.840.113635.100.6.2.6] /* exists */ and
certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists
*/ and certificate leaf[subject.OU] = ZU2TV78AA6

APP OR SERVICE SystemPolicyAllFiles

ACCESS Allow

App Access Identified com.acronis.backup.activeprotection

Identifier Type Bundle ID

Code identifier "com.acronis.backup.activeprotection" and

Requirement anchor apple generic and certificate 1
[field.1.2.840.113635.100.6.2.6] /* exists */ and
certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists
*/ and certificate leaf[subject.OU] = ZU2TV78AA6

APP OR SERVICE SystemPolicyAllFiles

ACCESS Allow

App Access Identifier cyber-protect-service

Identifier Type Bundle ID

Code identifier "cyber-protect-service" and anchor apple

Requirement generic and certificate 1[field.1.2.840.113635.100.6.2.6]
/* exists */ and certificate leaf
[field.1.2.840.113635.100.6.1.13] /* exists */ and
certificate leaf[subject.OU] = ZU2TV78AA6

APP OR SERVICE SystemPolicyAllFiles

ACCESS Allow

114 © Acronis International GmbH, 2003-2024

 Approved Allow users to Enabled
Kernel approve kernel
Extensions extensions

Allow standard Enabled

users to
approve legacy
kernel
extensions
(macOS 11 or
later)

Approved Approved Team Acronis Cyber Protection Agent Kernel Extensions

Team IDs ID - Display
and Kernel Name
Extensions
Team ID ZU2TV78AA6

Kernel l com.acronis.systeminterceptors
Extension l com.acronis.ngscan
Bundle IDs l com.acronis.notifyframework

System Allow users to Enabled

Extensions approve system
extensions

Allowed Display Name Acronis Cyber Protection Agent System Extensions

Team IDs
System Allowed Team Identifiers
and System
Extension Types
Extensions

Team Identifier ZU2TV78AA6

Registering and unregistering workloads manually

Workloads are automatically registered in the Cyber Protection service when you install the
protection agent on them. When you uninstall the protection agent, the workloads are automatically
unregistered and disappear from the Cyber Protect console.

You can also register a workload manually, by using the command line interface. You might need to
use the manual registration, for example, if the automatic registration fails or if you want to move a
workload to a new tenant or under a new user account.

To register a workload by using a user name and password

In Windows

At the command line, run the following command:

115 © Acronis International GmbH, 2003-2024

 "%ProgramFiles%\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t cloud
-a <service address> -u <user name> -p <password>

For example:

"C:\ProgramFiles\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t cloud

-a https://cloud.company.com -u johndoe -p johnspassword

In Linux

At the command line, run the following command:

sudo "/usr/lib/Acronis/RegisterAgentTool/RegisterAgent" -o register -t cloud -a <service

address> -u <user name> -p <password>

For example:

sudo "/usr/lib/Acronis/RegisterAgentTool/RegisterAgent" -o register -t cloud -a

https://cloud.company.com -u johndoe -p johnspassword

In macOS

At the command line, run the following command:

sudo "/Library/Application Support/BackupClient/Acronis/RegisterAgentTool/RegisterAgent"

-o register -t cloud -a <service address> -u <user name> -p <password>

For example:

sudo "/Library/Application Support/BackupClient/Acronis/RegisterAgentTool/RegisterAgent"

-o register -t cloud -a https://cloud.company.com -u johndoe -p johnspassword

Note
Use the user name and password for the account under which you want to register the workload.
This cannot be a partner administrator account.

The service address is the URL that you use to log in to the Cyber Protection service. For example,
https://cloud.company.com.

Important
If your password contains special characters or blank spaces, refer to "Passwords with special
characters or blank spaces" (p. 119).

116 © Acronis International GmbH, 2003-2024

Important
If you use macOS 10.14 or later, grant full disk access to the protection agent. To do so, go to
Applications >Utilities, and then run Cyber Protect Agent Assistant. Then, follow the
instructions in the application window.

To register a workload by using a registration token

In Windows

At the command line, run the following command:

"%ProgramFiles%\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t cloud

-a <service address> --token <registration token>

For example:

"C:\ProgramFiles\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t cloud

-a https://au1-cloud.company.com --token 3B4C-E967-4FBD

In Linux

At the command line, run the following command:

sudo "/usr/lib/Acronis/RegisterAgentTool/RegisterAgent" -o register -t cloud -a <service

address> --token <registration token>

For example:

sudo "/usr/lib/Acronis/RegisterAgentTool/RegisterAgent" -o register -t cloud -a

https://eu2-cloud.company.com --token 34F6-8C39-4A5C

In macOS

At the command line, run the following command:

sudo "/Library/Application Support/BackupClient/Acronis/RegisterAgentTool/RegisterAgent"

-o register -t cloud -a <service address> --token <registration token>

For example:

sudo "/Library/Application Support/BackupClient/Acronis/RegisterAgentTool/RegisterAgent"

-o register -t cloud -a https://us5-cloud.company.com --token 9DBF-3DA9-4DAB

Important
If you use macOS 10.14 or later, grant full disk access to the protection agent. To do so, go to
Applications >Utilities, and then run Cyber Protect Agent Assistant. Then, follow the
instructions in the application window.

117 © Acronis International GmbH, 2003-2024

Virtual appliance

1. In the console of the virtual appliance, press CTRL+SHIFT+F2 to open the command-line
interface.
2. At the command prompt, run the following command:

register_agent -o register -t cloud -a <service address> --token <registration token>

For example:

register_agent -o register -t cloud -a https://eu2-cloud.company.com --token 34F6-

8C39-4A5C

3. To return to the graphical interface of the appliance, press ALT+F1.

Note
When you use a registration token, you must specify the exact data center address. This is the URL
that you see after you log in to the Cyber Protection service. For example, https://eu2-
cloud.company.com.

Do not use https://cloud.company.com here.

The registration token is a series of 12 characters, separated by hyphens in three segments. For
more information on how to generate one, refer to "Generating a registration token" (p. 162).

To unregister a workload

In Windows

At the command line, run the following command:

"%ProgramFiles%\BackupClient\RegisterAgentTool\register_agent.exe" -o unregister

For example:

"C:\ProgramFiles\BackupClient\RegisterAgentTool\register_agent.exe" -o unregister

In Linux

At the command line, run the following command:

sudo "/usr/lib/Acronis/RegisterAgentTool/RegisterAgent" -o unregister

In macOS

At the command line, run the following command:

118 © Acronis International GmbH, 2003-2024

 sudo "/Library/Application Support/BackupClient/Acronis/RegisterAgentTool/RegisterAgent"
-o unregister

Virtual appliance

1. In the console of the virtual appliance, press CTRL+SHIFT+F2 to open the command-line
interface.
2. At the command prompt, run the following command:

register_agent -o unregister

3. To return to the graphical interface of the appliance, press ALT+F1.

Moving a workload to another tenant

Moving a workload to another tenant is not natively supported. As a workaround, you can
unregister the workload, and then register it in another tenant. All applied protection plans will be
revoked from that workload, and it will lose access to its backups in the cloud storage of the original
tenant.

For more information about how to register a workload in a new tenant or under a new user
account, see "Changing the registration of a workload" (p. 120).

Passwords with special characters or blank spaces

If your password contains special characters or blank spaces, enclose it in quotation marks when
you type it on the command line.

For example, in Windows, run this command:

Command template:

"%ProgramFiles%\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t cloud

-a <service address> -u <user name> -p <"password">

Command example:

"C:\ProgramFiles\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t cloud

-a https://cloud.company.com -u johndoe -p "johns password"

If this command fails, encode your password into base64 format at https://www.base64encode.org/.
Then, at the command line, specify the encoded password by using the -b or --base64 parameter.

For example, in Windows, run this command:

Command template:

"%ProgramFiles%\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t cloud

-a <service address> -u <user name> -b -p <encoded password>

119 © Acronis International GmbH, 2003-2024

Command example:

"C:\ProgramFiles%\BackupClient\RegisterAgentTool\register_agent.exe" -o register -t
cloud -a https://cloud.company.com -u johndoe -b -p am9obnNwYXNzd29yZA==

Changing the registration of a workload

You can change the current registration of a workload by registering it in a new tenant or under a
new user account.

Important
When you change the registration of a workload, all protection plans that are applied to it will be
revoked. To continue protecting the workload, apply a new protection plan to it.

If you register the workload in a new tenant, the workload will lose access to the backups in the
cloud storage of the original tenant. The backups in non-cloud storages will remain accessible.

You can change the registration of a workload by using the command line or by using the GUI
installer. When you use the command line, you do not need to uninstall the agent.

To change the registration of a workload

By using the command line

1. Unregister the protection agent, as described in "To unregister a workload" (p. 118).
2. Register the protection agent in the new tenant or under the new user account, as described in
"To register a workload by using a user name and password" (p. 115) or in "To register a
workload by using a registration token" (p. 117).

By using the GUI installer

1. Uninstall the protection agent.

2. Install the protection agent, and then register it in the new tenant or under the new user
account.

For more information about how to install and register an agent, refer to "Installing protection
agents" (p. 73).

Autodiscovery of machines
Using autodiscovery, you can:

l Automate the installation of protection agents and the registration of machines by detecting the
machines in your Active Directory domain or local network.
l Install and update protection agents on multiple machines.
l Use synchronization with Active Directory, in order to reduce the efforts for provisioning
resources and managing machines in a large Active Directory domain.

120 © Acronis International GmbH, 2003-2024

Prerequisites
To perform autodiscovery, you need at least one machine with an installed protection agent in your
local network or Active directory domain. This agent is used as a discovery agent.

Important
Only agents that are installed on Windows machines can be discovery agents. If there are no
discovery agents in your environment, you will not be able to use the Multiple devices option in
the Add devices panel.

Remote installation of agents is supported only for machines running Windows (Windows XP is not
supported). For remote installation on a machine running Windows Server 2012 R2, you must have
Windows update KB2999226 installed on this machine.

How autodiscovery works

During a local network discovery, the discovery agent collects the following information for each
machine in the network, by using NetBIOS discovery, Web Service Discovery (WSD), and the Address
Resolution Protocol (ARP) table:

l Name (short/NetBIOS hostname)

l Fully qualified domain name (FQDN)
l Domain/workgroup
l IPv4/IPv6 addresses
l MAC addresses
l Operating system (name/version/family)
l Machine category (workstation/server/domain controller)

During an Active Directory discovery, the discovery agent, in addition to the list above, collects
information about the Organizational Unit (OU) of the machines and detailed information about
their names and operating systems. However, the IP and MAC addresses are not collected.

The following diagram summarizes the autodiscovery process.

121 © Acronis International GmbH, 2003-2024

1. Select the discovery method:
l Active Directory discovery
l Local network discovery
l Manual discovery – By using a machine IP address or host name, or by importing a list of
machines from a file
The results of an Active directory discovery or a local network discovery exclude machines with
installed protection agents.
During a manual discovery, the existing protection agents are updated and re-registered. If you
perform autodiscovery by using the same account under which an agent is registered, the agent
will only be updated to the latest version. If you perform autodiscovery by using another
account, the agent will be updated to the latest version and re-registered under the tenant to
which the account belongs.
2. Select the machines that you want to add to your tenant.
3. Select how to add these machines:
l Install a protection agent and additional components on the machines, and register them in
the Cyber Protect console.

122 © Acronis International GmbH, 2003-2024

 l Register the machines in the Cyber Protect console (if a protection agent was already
installed).
l Add the machines to the Cyber Protect console as Unmanaged machines, without installing a
protection agent.
You can also apply an existing protection plan to the machines on which you install a protection
agent or which you register in the Cyber Protect console.
4. Provide administrator credentials for the selected machines.
5. Verify that you can connect to the machines by using the provided credentials.

The machines that are shown in the Cyber Protect console, fall into the following categories:

l Discovered – Machines that are discovered, but a protection agent is not installed on them.
l Managed – Machines on which a protection agent is installed.
l Unprotected – Machines to which a protection plan is not applied. Unprotected machines
include both discovered machines and managed machines with no protection plan applied.
l Protected – Machines to which a protection plan is applied.

How remote installation of agents works

1. The discovery agent connects to the target machines by using the host name, IP address, and
administrator credentials specified in the discovery wizard, and then uploads the web_
installer.exe file to these machines.
2. The web_installer.exe file runs on the target machines in the unattended mode.
3. The web installer retrieves additional installation packages from the cloud, and then installs
them to the target machines via the msiexec command.
4. After the installation completes, the components are registered in the cloud.

Note
Remote installation of agents is not supported for Domain Controllers due to the additional
permissions required for the agent service to run.

Performing autodiscovery and manual discovery

Before starting the discovery, ensure that the prerequisites are met.

Note
Autodiscovery is not supported for adding Domain Controllers due to additional permissions
required for the agent service to run.

To discover machines

1. In the Cyber Protect console, go to Devices> All devices.

2. Click Add.
3. In Multiple devices, click Windows-only. The discovery wizard opens.

123 © Acronis International GmbH, 2003-2024

4. [If there are units in your organization] Select a unit. Then, in Discovery agent you will be able to
select the agents associated with the selected unit and its child units.
5. Select the discovery agent that will perform the scan to detect machines.
6. Select the discovery method:
l Search Active Directory. Ensure that the machine with the discovery agent is the Active
Directory domain member.
l Scan local network. If the selected discovery agent could not find any machines, select
another discovery agent.
l Specify manually or import from file. Manually define the machines to be added or import
them from a text file.
7. [If the Active Directory discovery method is selected] Select how to search for machines:
l In organizational unit list. Select the group of machines to be added.
l By LDAP dialect query. Use the LDAP dialect query to select the machines. Search base
defines where to search, while Filter allows you to specify the criteria for machine selection.
8. Depending on the discovery method that you selected, perform one of the following actions:

Discovery Action
method

Search Active In the list of discovered machines, select the machines that you want to add.
Directory

Scan local In the list of discovered machines, select the machines that you want to add.
network

Specify Specify the machine IP addresses or hostnames, or import the machine list from a
manually or text file. The file must contain IP addresses/hostnames, one per line. Here is an
import from a example of a file:
file
156.85.34.10
156.85.53.32
156.85.53.12
EN-L00000100
EN-L00000101

After adding machine addresses manually or importing from a file, the agent tries
to ping the added machines and define their availability.

9. Select the actions that must be performed after the discovery:

Option Description

Install agents You can select which components to install on the machines by clicking Select
and register components. For more details, see "Selecting components for installation" (p. 128).
machines

Logon This setting is available on the Select components screen.

account for The setting defines the account under which the services will run.

124 © Acronis International GmbH, 2003-2024

 Option Description

the agent You can select one of the following options:

service l Use Service User Accounts (default for the agent service)
Service User Accounts are Windows system accounts that are used to run
services. The advantage of this setting is that the domain security policies do not
affect these accounts' user rights. By default, the agent runs under the Local
System account.
l Create a new account
The account name will be Agent User for the agent.
l Use the following account
If you install the agent on a domain controller, the system prompts you to specify
existing accounts (or the same account) for the agent. For security reasons, the
system does not automatically create new accounts on a domain controller.
If you chose the Create a new account or Use the following account option,
ensure that the domain security policies do not affect the related accounts' rights. If
an account is deprived of the user rights assigned during the installation, the
component might work incorrectly or not work at all.

Register Use this option if the agent is already installed on the machines, and you only need
machines to register them in Cyber Protection. If no agent is found on the machines, they will
with installed be added as Unmanaged machines.
agents

Add as If you select this option, the agent will not be installed on the machines. You will be
unmanaged able to view them in the console and install or register the agent later.
machines

Restart the This option appears when Install agents and register machines is selected.
machine, if If you select this option, the machine will be restarted as many times as required to
required complete the installation.
Restart of the machine may be required in one of the following cases:
l Installation of prerequisites is completed, and restart is required to continue the
installation.
l Installation is completed but restart is required, as some files are locked during
installation.
l Installation is completed, but restart is required for other previously installed
software.

Do not This option appears when Restart the machine if required is selected.
restart if the If you select this option, the machine will not be automatically restarted if the user is
user logged logged in to the system. For example, if a user is working while installation requires
in restart, the system will not be restarted.
If the prerequisites were installed but the machine was not restarted because a user
was logged in, to complete the installation you must restart the machine, and then
start the installation again.

125 © Acronis International GmbH, 2003-2024

 Option Description

If the agent was installed but then the machine was not restarted, you must restart
the machine.

User where [If there are units in your organization] Select the user account of unit or subordinate
to register units under which you want to register the machines.
the machines [When performing autodiscovery on the partner tenant level] In the list of customer
tenants that you manage, expand the tree structure, and then select the user
account under which you want to register the machines.
[When performing autodiscovery as a customer administrator] If you selected Install
agents and register machines or Register machines with installed agents, there
is also an option to apply the protection plan to the machines. If you have several
protection plans, you can select which one to use.

10. Specify the credentials of the user with administrator rights for all of the machines.

Important
Note that remote installation of agent works without any preparations only if you specify the
credentials of the built-in administrator account (the first account created when the operating
system is installed). If you want to define some custom administrator credentials, then you
should do additional manual preparations as described in "Preparing a machine for remote
installation" (p. 126).

11. The system checks connectivity to all of the machines. If the connection to some of the machines
fails, you can change the credentials for these machines.

When the discovery of machines is initiated, you will find the corresponding task in Monitoring>
Activities > Discovering machines activity.

Preparing a machine for remote installation

l For successful installation on a remote machine running Windows 7 or later, the option Control
panel > Folder options > View > Use Sharing Wizard must be disabled on that machine.
l For successful installation on a remote machine that is not a member of an Active Directory
domain, User Account Control (UAC) must be disabled on that machine. For more information on
how to disable it, refer to "Requirements on User Account Control (UAC)" > To disable UAC.
l By default, the credentials of the built-in administrator account are required for remote
installation on any Windows machine. To perform remote installation by using the credentials of
another administrator account, User Account Control (UAC) remote restrictions must be disabled.
For more information on how to disable them, refer to "Requirements on User Account Control
(UAC)" > To disable UAC remote restrictions.
l File and Printer Sharing must be enabled on the remote machine. To access this option:
o On a machine running Windows 2003 Server: go to Control panel > Windows Firewall >
Exceptions > File and Printer Sharing.

126 © Acronis International GmbH, 2003-2024

 o On a machine running Windows Server 2008, Windows 7, or later: go to Control panel >
Windows Firewall > Network and Sharing Center > Change advanced sharing settings.
l Cyber Protection uses TCP ports 445, 25001, and 43234 for remote installation.
Port 445 is automatically opened when you enable File and Printer Sharing. Ports 43234 and
25001 are automatically opened through Windows Firewall. If you use a different firewall, make
sure that these three ports are open (added to exceptions) for both incoming and outgoing
requests.
After the remote installation is complete, port 25001 is automatically closed through Windows
Firewall. Ports 445 and 43234 need to remain open if you want to update the agent remotely in
the future. Port 25001 is automatically opened and closed through Windows Firewall during each
update. If you use a different firewall, keep all the three ports open.

Requirements on User Account Control (UAC)

On a machine that is running Windows 7 or later and is not a member of an Active Directory
domain, centralized management operations (including remote installation) require that UAC and
UAC remote restrictions be disabled.

To disable UAC

Do one of the following depending on the operating system:

l In a Windows operating system prior to Windows 8:

Go to Control panel > View by: Small icons > User Accounts > Change User Account
Control Settings, and then move the slider to Never notify. Then, restart the machine.
l In any Windows operating system:
1. Open Registry Editor.
2. Locate the following registry key: HKEY_LOCAL_
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System
3. For the EnableLUA value, change the setting to 0.
4. Restart the machine.

To disable UAC remote restrictions

1. Open Registry Editor.

2. Locate the following registry key: HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. For LocalAccountTokenFilterPolicy value, change the setting to 1.
If the LocalAccountTokenFilterPolicy value does not exist, create it as DWORD (32-bit). For
more information about this value, refer to the Microsoft documentation:
https://support.microsoft.com/en-us/help/951016/description-of-user-account-control-and-
remote-restrictions-in-windows.

127 © Acronis International GmbH, 2003-2024

Note
For security reasons, we recommend that after finishing the management operation (for example,
remote installation), you revert both settings to their original state: EnableLUA=1 and
LocalAccountTokenFilterPolicy = 0

Selecting components for installation

You can find the description of mandatory and additional components in the following table:

Component Description

Mandatory component

Agent for This agent backs up disks, volumes, files and will be installed on Windows machines. It
Windows will be always installed, not selectable.

Additional components

Agent for Data This agent enables you to limit the user access to local and redirected peripheral devices,
Loss ports, and clipboard on machines under protection plans. It will be installed if selected.
Prevention

Antimalware This component enables the Antivirus & Antimalware protection module and URL
and URL filtering module in protection plans. Even if you select not to install it, it will be
filtering automatically installed later, if any of these modules is enabled in a protection plan for
the machine.

Agent for This agent backs up Hyper-V virtual machines and will be installed on Hyper-V hosts. It
Hyper-V will be installed if selected and detected Hyper-V role on a machine.

Agent for SQL This agent backs up SQL Server databases and will be installed on machines running
Microsoft SQL Server. It will be installed if selected and application detected on a
machine.

Agent for This agent backs up Exchange databases and mailboxes and will be installed on
Exchange machines running the Mailbox role of Microsoft Exchange Server. I will be installed if
selected and application detected on a machine.

Agent for This agent backs up the data of Active Directory Domain Services and will be installed on
Active domain controllers. It will be installed if selected and application detected on a machine.
Directory

Agent for This agent backs up VMware virtual machines and will be installed on Windows machines
VMware that have network access to vCenter Server. It will be installed if selected.
(Windows)

Agent for This agent backs up Microsoft 365 mailboxes to a local destination and will be installed
Microsoft 365 on Windows machines. It will be installed if selected.

Agent for This agent backs up Oracle databases and will be installed on machines running Oracle
Oracle Database. It will be installed if selected.

128 © Acronis International GmbH, 2003-2024

 Cyber This component enables a user to monitor execution of running tasks in the notification
Protection area and will be installed on Windows machines. It will be installed if selected.
Monitor
Supported on Windows 7 Service Pack 1 and later, and Windows Server 2008 R2 Service
Pack 1 and later.

Managing discovered machines

After the discovery process is performed, you can find all of the discovered machines in Devices>
Unmanaged machines.

This section is divided into subsections by the discovery method used. The full list of machine
parameters is shown below (it may vary depending on the discovery method):

Name Description

Name The name of the machine. The IP address will be shown if the name of the machine
could not be discovered.

IP address The IP address of the machine.

Discovery type The discovery method that was used to detect the machine.

Organizational The organizational unit in Active Directory that the machine belongs to. This column
unit is shown if you view the list of machines in Unmanaged machines > Active
Directory.

Operating The operating system installed in the machine.

system

There is an Exceptions section, where you can add the machines that must be skipped during the
discovery process. For example, if you do not need the exact machines to be discovered, you can
add them to this list.

To add a machine to Exceptions, select it in the list and click Add to exceptions. To remove a
machine from Exceptions, go to Unmanaged machines > Exceptions, select the machine, and
click Remove from exceptions.

You can install the protection agent and register a batch of discovered machines in Cyber Protection
by selecting them in the list and clicking Install and register. The opened wizard also allows you to
assign the protection plan to a batch of machines.

After the protection agent is installed on machines, those machines will be shown in the Devices>
Machines with agents section.

To check your protection status, go to Monitoring> Overview and add the Protection status
widget or the Discovered machine widget.

Troubleshooting
If you have any issues with the autodiscovery functionality, try to check the following:

129 © Acronis International GmbH, 2003-2024

l Check that NetBIOS over TCP/IP is enabled or set to default.

l In the “Control Panel\Network and Sharing Center\Advanced sharing settings” turn on network
discovery.

l Check that the Function Discovery Provider Host service is running on the machine that does
discovery and on the machines to be discovered.
l Check that the Function Discovery Resource Publication service is running on the machines to be
discovered.

130 © Acronis International GmbH, 2003-2024

Deploying Agent for VMware (Virtual Appliance)

Before you start

System requirements for the agent

By default, the virtual appliance is assigned 4 GB of RAM and 2 vCPUs, which is optimal and
sufficient for most operations.

To improve the backup performance and avoid failures related to insufficient RAM memory, we
recommend that you increase these resources to 16 GB of RAM and 4 vCPUs in more demanding
cases. For example, increase the assigned resources when you expect the backup traffic to exceed
100 MB per second (for example, in 10-Gigabit networks) or if you simultaneously back up multiple
virtual machines with large hard drives (500 GB or more).

The appliance's own virtual disks occupy no more than 6 GB. Thick or thin disk format does not
matter, it does not affect the appliance performance.

How many agents do I need?

Even though one virtual appliance is able to protect an entire vSphere environment, the best
practice is deploying one virtual appliance per vSphere cluster (or per host, if there are no clusters).
This makes for faster backups because the appliance can attach the backed-up disks by using the
HotAdd transport, and therefore the backup traffic is directed from one local disk to another.

It is normal to use both the virtual appliance and Agent for VMware (Windows) at the same time, as
long as they are connected to the same vCenter Server or they are connected to different ESXi hosts.
Avoid cases when one agent is connected to an ESXi directly and another agent is connected to the
vCenter Server which manages this ESXi.

We do not recommend that you use locally attached storage (i.e. storing backups on virtual disks
added to the virtual appliance) if you have more than one agent. For more considerations, see
"Using a locally attached storage" (p. 660).

Disable automatic DRS for the agent

If the virtual appliance is deployed to a vSphere cluster, be sure to disable automatic vMotion for it.
In the cluster DRS settings, enable individual virtual machine automation levels, and then set
Automation level for the virtual appliance to Disabled.

Deploying the OVF template

1. Click All devices > Add > VMware ESXi > Virtual Appliance (OVF).
The .zip archive is downloaded to your machine.
2. Unpack the .zip archive. The folder contains one .ovf file and two .vmdk files.

131 © Acronis International GmbH, 2003-2024

3. Ensure that these files can be accessed from the machine running vSphere Client.
4. Start vSphere Client and log on to the vCenter Server.
5. Deploy the OVF template.
l When configuring storage, select the shared datastore, if it exists. Thick or thin disk format
does not matter, as it does not affect the appliance performance.
l When configuring network connections, be sure to select a network that allows an Internet
connection, so that the agent can properly register itself in the cloud.

Configuring the virtual appliance

After deploying the virtual appliance, you must configure it so that it can access vCenter Server or
the ESXi host and the Cyber Protection service.

To configure the virtual appliance

1. In the vSphere Client, open the console of the virtual appliance.

2. Ensure that the network connection is configured.
The connection is configured automatically via Dynamic Host Configuration Protocol (DHCP).
To change the default configuration, under Agent options, in the eth0 field, click Change, and
then specify the network settings.
3. Connect the virtual appliance to vCenter Server or the ESXi host.
a. Under Agent options, in the vCenter/ESX(i) field, click Change, and then specify the
following.
l [If you use vCenter Server] The vCenter Server name or IP address.
l [If you do not use vCenter Server] The name or IP address of the ESXi host on which you
want to back up and recover virtual machines. For faster backups, deploy the virtual
appliance on the same host.
l The credentials required for the appliance to connect to vCenter Server or the ESXi host.
We recommend that you use a dedicated account for accessing vCenter Server or the ESXi
host, instead of using an existing account with the Administrator role. To learn more about
the required privileges for the dedicated account, refer to "Agent for VMware – necessary
privileges" (p. 666).
b. Click Check connection to verify that the settings are correct.
c. Click OK.
4. Register the appliance in the Cyber Protection service by using one of the following methods.
l [Only for tenants without two-factor authentication] Register the appliance in its graphical
interface.
a. Under Agent options, in the Management Server field, click Change.
b. In the Server name/IP field, select Cloud.
The Cyber Protection service address appears. Do not change this address unless
instructed otherwise.

132 © Acronis International GmbH, 2003-2024

 c. In the User name and Password fields, specify the credentials for your account in the
Cyber Protection service. The virtual appliance and the virtual machines that the appliance
manages are registered under this account.
d. Click OK.
l Register the appliance in the command-line interface.

Note
With this method, you need a registration token. For more information about how to
generate one, refer to "Generating a registration token" (p. 162).

a. Press CTRL+SHIFT+F2 to open the command-line interface.

b. Run the following command:

register_agent -o register -t cloud -a <service address> --token <registration

token>

Note
When you use a registration token, you must specify the exact data center address. This is
the URL that you see after you log in to the Cyber Protect console. For example,
https://eu2-cloud.company.com.

Do not use https://cloud.company.com here.

c. To return to the graphical interface of the appliance, press ALT+F1.

5. [Optional] Add local storage.
a. In the vSphere Client, attach a virtual disk to the virtual appliance. The virtual disk must have
at least 10 GB of free space.
b. In the graphical user interface of the appliance, click Refresh.

The Create storage button becomes active.

c. Click Create storage.

133 © Acronis International GmbH, 2003-2024

 d. Specify a label for the storage, and then click OK.
e. Confirm your choice by clicking Yes.
6. [If a proxy server is enabled in your network] Configure the proxy server.
a. Press CTRL+SHIFT+F2 to open the command-line interface.
b. Open the file /etc/Acronis/Global.config in a text editor.
c. Do one of the following:
l If the proxy settings were specified during the agent installation, find the following section:

<key name="HttpProxy">
<value name="Enabled" type="Tdword">"1"</value>
<value name="Host" type="TString">"ADDRESS"</value>
<value name="Port" type="Tdword">"PORT"</value>
<value name="Login" type="TString">"LOGIN"</value>
<value name="Password" type="TString">"PASSWORD"</value>
</key>

l Otherwise, copy the above lines and paste them into the file between the <registry
name="Global">...</registry> tags.
d. Replace ADDRESS with the new proxy server host name/IP address, and PORT with the decimal
value of the port number.
e. If your proxy server requires authentication, replace LOGIN and PASSWORD with the proxy server
credentials. Otherwise, delete these lines from the file.
f. Save the file.
g. Open the file /opt/acronis/etc/aakore.yaml in a text editor.
h. Locate the env section or create it and add the following lines:

env:
http-proxy: proxy_login:proxy_password@proxy_address:port
https-proxy: proxy_login:proxy_password@proxy_address:port

i. Replace proxy_login and proxy_password with the proxy server credentials, and proxy_
address:port with the address and port number of the proxy server.
j. Run the reboot command.

Note
To be able to update a virtual appliance deployed behind a proxy, edit the appliance config.yaml
file ( /opt/acronis/etc/va-updater/config.yaml), by adding the following line to the bottom of
that file, and then entering values specific to your environment:

httpProxy: http://<proxy_login>:<proxy_password>@<proxy_address>:<port>

For example:

httpProxy: http://mylogin:[email protected]:8080

134 © Acronis International GmbH, 2003-2024

Deploying Agent for Scale Computing HC3 (Virtual
Appliance)

Before you start

This appliance is a pre-configured virtual machine that you deploy in a Scale Computing HC3 cluster.
It contains a protection agent that enables you to administer cyber protection for all virtual
machines in the cluster.

System requirements for the agent

By default, the virtual machine with the agent uses 2 vCPUs and 4 GiB of RAM. These settings are
sufficient for most operations but you can change them by editing the virtual machine in the Scale
Computing HC3 web interface.

To improve the backup performance and avoid failures related to insufficient RAM memory, we
recommend that you increase these resources to 4 vCPUs and 8 GiB of RAM in more demanding
cases. For example, increase the assigned resources when you expect the backup traffic to exceed
100 MB per second (for example, in 10-Gigabit networks) or if you back up simultaneously multiple
virtual machines with large hard drives (500 GB or more).

The size of the appliance virtual disk is about 9 GB.

How many agents do I need?

One agent can protect the entire cluster. However, you can have more than one agent in the cluster
if you need to distribute the backup traffic bandwidth load.

If you have more than one agent in a cluster, the virtual machines are automatically evenly
distributed between the agents, so that each agent manages a similar number of machines.

Automatic redistribution occurs when the load imbalance among the agents reaches 20 percent.
This may happen after you add or remove a machine or an agent. For example, you realize that you
need more agents to help with throughput and you deploy an additional virtual appliance to the
cluster. The management server will assign the most appropriate machines to the new agent. The
old agents' load will reduce. When you remove an agent from the management server, the
machines assigned to the agent are redistributed among the remaining agents. However, this will
not happen if an agent gets corrupted or is deleted manually from the Scale Computing HC3 cluster.
Redistribution will start only after you remove such an agent from the Cyber Protect console.

To check which agent manages a specific machine

1. In the Cyber Protect console, click Devices, and then select Scale Computing.
2. Click the gear icon in the upper right corner of the table, and under System, select the Agent

135 © Acronis International GmbH, 2003-2024

 check box.
3. Check the name of the agent in the column that appears.

Deploying the QCOW2 template

1. Log in to your Cyber Protection account.
2. Click Devices > All devices > Add > Scale Computing HC3.
The .zip archive is downloaded to your machine.
3. Unpack the .zip archive, and then save the .qcow2 file and the .xml file to a folder named
ScaleAppliance.
4. Upload the ScaleAppliance folder to a network share and ensure that the Scale Computing HC3
cluster can access it.
5. Log in to the Scale Computing HC3 cluster as an administrator who has the VM Create/Edit role
assigned. For more information about the roles required for operations with Scale Computing
HC3 virtual machines, refer to "Agent for Scale Computing HC3 – required roles" (p. 139).
6. In the Scale Computing HC3 web interface, import the virtual machine template from the
ScaleAppliance folder.
a. Click the Import HC3 VM icon.
b. In the Import HC3 VM window, specify the following:
l A name for the new virtual machine.
l The network share on which the ScaleAppliance folder is located.
l The user name and password required for accessing this network share.
l [Optional] A domain tag for the new virtual machine.
l The path to the ScaleAppliance folder on the network share.
c. Click Import.

After the deployment completes, you must configure the virtual appliance. For more information on
how to configure it, refer to "Configuring the virtual appliance" (p. 136).

Note
If you need more than one virtual appliance in your cluster, repeat the steps above and deploy
additional virtual appliances. Do not clone an existing virtual appliance by using the Clone
VM option in the Scale Computing HC3 web interface.

Configuring the virtual appliance

After deploying the virtual appliance, you need to configure it so that it can reach both the Scale
Computing HC3 cluster that it will protect and the Cyber Protection service.

To configure the virtual appliance

1. Log in to your Scale Computing HC3 account.

2. Select the virtual appliance that you want to configure, and then click the Console icon.
3. In the eth0 field, configure the network interfaces of the appliance.

136 © Acronis International GmbH, 2003-2024

 Ensure that automatically assigned DHCP addresses (if any) are valid within the networks that
your virtual machine uses or assign them manually. Depending on the number of networks that
the appliance uses, there may be one or more interfaces to configure.
4. In the Scale Computing field, click Change to specify the Scale Computing HC3 cluster address
and credentials for accessing it.
a. In the Server name/IP field, enter the DNS name or IP address of the cluster.
b. In the User name and Password fields, enter the credentials for the Scale Computing HC3
administrator account.
Ensure that this account has the roles required for operations with Scale Computing HC3
virtual machines. For more information about these roles, refer to "Agent for Scale
Computing HC3 – required roles" (p. 139).
c. Click Check connection to verify that the settings are correct.
d. Click OK.
5. Register the appliance in the Cyber Protection service by using one of the following methods.
l [Only for tenants without two-factor authentication] Register the appliance in its graphical
interface.
a. Under Agent options, in the Management Server field, click Change.
b. In the Server name/IP field, select Cloud.
The Cyber Protection service address appears. Do not change this address unless
instructed otherwise.
c. In the User name and Password fields, specify the credentials for your account in the
Cyber Protection service. The virtual appliance and the virtual machines that the appliance
manages are registered under this account.
d. Click OK.
l Register the appliance in the command-line interface.

Note
With this method, you need a registration token. For more information about how to
generate one, refer to "Generating a registration token" (p. 162).

a. Press CTRL+SHIFT+F2 to open the command-line interface.

b. Run the following command:

register_agent -o register -t cloud -a <service address> --token <registration

token>

137 © Acronis International GmbH, 2003-2024

 Note
When you use a registration token, you must specify the exact data center address. This is
the URL that you see after you log in to the Cyber Protect console. For example,
https://eu2-cloud.company.com.

Do not use https://cloud.company.com here.

c. To return to the graphical interface of the appliance, press ALT+F1.

6. [Optional] In the Name field, click Change to edit the default name for the virtual appliance,
which is localhost. This name is shown in the Cyber Protect console.
7. [Optional] In the Time field, click Change, and then select the time zone of your location to
ensure that the scheduled operations run at the appropriate time.
8. [If a proxy server is enabled in your network] Configure the proxy server.
a. Press CTRL+SHIFT+F2 to open the command-line interface.
b. Open the file /etc/Acronis/Global.config in a text editor.
c. Do one of the following:
l If the proxy settings were specified during the agent installation, find the following section:

<key name="HttpProxy">
<value name="Enabled" type="Tdword">"1"</value>
<value name="Host" type="TString">"ADDRESS"</value>
<value name="Port" type="Tdword">"PORT"</value>
<value name="Login" type="TString">"LOGIN"</value>
<value name="Password" type="TString">"PASSWORD"</value>
</key>

l Otherwise, copy the above lines and paste them into the file between the <registry
name="Global">...</registry> tags.
d. Replace ADDRESS with the new proxy server host name/IP address, and PORT with the decimal
value of the port number.
e. If your proxy server requires authentication, replace LOGIN and PASSWORD with the proxy server
credentials. Otherwise, delete these lines from the file.
f. Save the file.
g. Open the file /opt/acronis/etc/aakore.yaml in a text editor.
h. Locate the env section or create it and add the following lines:

env:
http-proxy: proxy_login:proxy_password@proxy_address:port
https-proxy: proxy_login:proxy_password@proxy_address:port

i. Replace proxy_login and proxy_password with the proxy server credentials, and proxy_

138 © Acronis International GmbH, 2003-2024

 address:port with the address and port number of the proxy server.
j. Run the reboot command.

Note
To be able to update a virtual appliance deployed behind a proxy, edit the appliance config.yaml
file ( /opt/acronis/etc/va-updater/config.yaml), by adding the following line to the bottom of
that file, and then entering values specific to your environment:

httpProxy: http://<proxy_login>:<proxy_password>@<proxy_address>:<port>

For example:

httpProxy: http://mylogin:[email protected]:8080

To protect virtual machines in the Scale Computing HC3 cluster

1. Log in to your Cyber Protection account.

2. Navigate to Devices > Scale Computing HC3> <your cluster> or find your machines in Devices >
All devices.
3. Select machines and apply a protection plan to them.

Agent for Scale Computing HC3 – required roles

This section describes the roles required for operations with Scale Computing HC3 virtual machines.

Operation Role

Back up a virtual machine Backup

VM Create/Edit

VM Delete

Recover to an existing virtual machine Backup

VM Create/Edit

VM Power Control

VM Delete

Cluster Settings

Recover to a new virtual machine Backup

VM Create/Edit

VM Power Control

VM Delete

Cluster Settings

139 © Acronis International GmbH, 2003-2024

Deploying Agent for Virtuozzo Hybrid Infrastructure
(Virtual Appliance)

Before you start

This appliance is a pre-configured virtual machine that you deploy in Virtuozzo Hybrid
Infrastructure. It contains a protection agent that enables you to administer cyber protection for all
virtual machines in a Virtuozzo Hybrid Infrastructure cluster.

Note
To ensure that backups with enabled Volume Shadow Copy Service (VSS) for virtual machines
backup option run properly and capture data in application-consistent state, verify that Virtuozzo
Guest Tools are installed and up-to-date on the protected virtual machines.

System requirements for the agent

When deploying the virtual appliance, you can choose between different predefined combinations
of vCPUs and RAM (flavors). You can also create your own flavors.

2 vCPUs and 4 GB of RAM (medium flavor) are optimal and sufficient for most operations. To
improve the backup performance and avoid failures related to insufficient RAM memory, we
recommend that you increase these resources to 4 vCPUs and 8 GB of RAM in more demanding
cases. For example, increase the assigned resources when you expect the backup traffic to exceed
100 MB per second (for example, in 10-Gigabit networks) or if you back up simultaneously multiple
virtual machines with large hard drives (500 GB or more).

How many agents do I need?

One agent can protect the entire cluster. However, you can have more than one agent in the cluster
if you need to distribute the backup traffic bandwidth load.

If you have more than one agent in a cluster, the virtual machines are automatically evenly
distributed between the agents, so that each agent manages a similar number of machines.

Automatic redistribution occurs when the load imbalance among the agents reaches 20 percent.
This may happen after you add or remove a machine or an agent. For example, you realize that you
need more agents to help with throughput and you deploy an additional virtual appliance to the
cluster. The management server will assign the most appropriate machines to the new agent. The
old agents' load will reduce. When you remove an agent from the management server, the
machines assigned to the agent are redistributed among the remaining agents. However, this will
not happen if an agent gets corrupted or is deleted manually from the Virtuozzo Hybrid
Infrastructure node. Redistribution will start only after you remove such an agent from the Cyber
Protection web interface.

To check which agent manages a specific machine

140 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, click Devices, and then select Virtuozzo Hybrid Infrastructure.
2. Click the gear icon in the upper right corner of the table, and under System, select the Agent
check box.
3. Check the name of the agent in the column that appears.

Limitations
l Virtuozzo Hybrid Infrastructure appliance cannot be deployed remotely.
l Application-aware backup of virtual machines is not supported.

Configuring networks in Virtuozzo Hybrid Infrastructure

Before deploying and configuring the virtual appliance, you need to have your networks in Virtuozzo
Hybrid Infrastructure configured.

Network requirements for the Agent for Virtuozzo Hybrid Infrastructure (Virtual
Appliance)
l The virtual appliance requires 2 network adapters.
l The virtual appliance must be connected to Virtuozzo networks with the following network traffic
types:
o Compute API
o VM Backup
o ABGW Public
o VM Public

For more information about configuring the networks, see Compute cluster requirements in the
Virtuozzo documentation.

Configuring user accounts in Virtuozzo Hybrid Infrastructure

To configure the virtual appliance, you need a Virtuozzo Hybrid Infrastructure user account. This
account must have the Administrator role in the Default domain. For more information about
users, refer to Managing admin panel users in the Virtuozzo Hybrid Infrastructure documentation.
Ensure that you granted this account access to all projects in the Default domain.

To grant access to all projects in the Default domain

1. Create an environment file for the system administrator. To do this, run the following script in
the Virtuozzo Hybrid Infrastructure cluster via the OpenStack Command-Line Interface. For more
information on how to connect to this interface, refer to Connecting to OpenStack command-line
interface in the Virtuozzo Hybrid Infrastructure documentation.

su - vstoradmin
kolla-ansible post-deploy
exit

141 © Acronis International GmbH, 2003-2024

2. Use the environment file to authorize further OpenStack commands:

. /etc/kolla/admin-openrc.sh

3. Run the following commands:

openstack --insecure user set --project admin --project-domain Default --domain

Default <username>
openstack --insecure role add --domain Default --user <username> --user-domain
Default compute --inherited

Here, <username> is the Virtuozzo Hybrid Infrastructure account with the Administrator role in
the Default domain. The virtual appliance will use this account in order to back up and restore
the virtual machines in any child project under the Default domain.

Example

su - vstoradmin
kolla-ansible post-deploy
exit
. /etc/kolla/admin-openrc.sh
openstack --insecure user set --project admin --project-domain Default --domain Default
johndoe
openstack --insecure role add --domain Default --user johndoe --user-domain Default
compute --inherited

To manage backups for virtual machines in a domain that is different from the Default domain, run
the following command as well.

To grant access to all projects in a different domain

openstack --insecure role add --domain <domain name> --inherited --user <username> --
user-domain Default admin

Here, <domain name> is the domain to the projects in which the <username> account will have
access.

Example

openstack --insecure role add --domain MyNewDomain --inherited --user johndoe --user-
domain Default admin

After granting access to projects, check what roles are assigned to the account.

To check assigned roles

openstack --insecure role assignment list --user <username> --names

Here, <username> is the Virtuozzo Hybrid Infrastructure account.

142 © Acronis International GmbH, 2003-2024

Example

openstack --insecure role assignment list --user johndoe --names -c Role -c User -c
Project -c Domain
+--------------+-----------------+---------+-------------+
| Role | User | Project | Domain |
+--------------+-----------------+---------+-------------+
| admin | johndoe@Default | | MyNewDomain |
| compute | johndoe@Default | | Default |
| domain_admin | johndoe@Default | | Default |
| domain_admin | johndoe@Default | | Default |
+--------------+-----------------+---------+-------------+

In this example, the options -c Role, -c User, -c Project, and -c Domain are used to abridge the
command output to fit the page.

To check what effective roles are assigned to the account in all projects, run the following command
as well.

To check effective roles in all projects

openstack --insecure role assignment list --user <username> --names --effective

Here, <username> is the Virtuozzo Hybrid Infrastructure account.

Example

openstack --insecure role assignment list --user johndoe --names --effective -c Role -c
User -c Project -c Domain
+--------------+-----------------+-----------------+---------+
| Role | User | Project | Domain |
+--------------+-----------------+-----------------+---------+
| domain_admin | johndoe@Default | | Default |
| compute | johndoe@Default | admin@Default | |
| compute | johndoe@Default | service@Default | |
| domain_admin | johndoe@Default | admin@Default | |
| domain_admin | johndoe@Default | service@Default | |
| project_user | johndoe@Default | service@Default | |
| member | johndoe@Default | service@Default | |
| reader | johndoe@Default | service@Default | |
| project_user | johndoe@Default | admin@Default | |
| member | johndoe@Default | admin@Default | |
| reader | johndoe@Default | admin@Default | |
| project_user | johndoe@Default | | Default |
| member | johndoe@Default | | Default |
| reader | johndoe@Default | | Default |
+--------------+-----------------+-----------------+---------+

143 © Acronis International GmbH, 2003-2024

In this example, the options -c Role, -c User, -c Project, and -c Domain are used to abridge the
command output to fit the page.

Deploying the QCOW2 template

1. Log in to your Cyber Protection account.
2. Click Devices > All devices > Add > Virtuozzo Hybrid Infrastructure.
The .zip archive is downloaded to your machine.
3. Unpack the .zip archive. It contains a .qcow2 image file.
4. Log in to your Virtuozzo Hybrid Infrastructure account.
5. Add the .qcow2 image file to the Virtuozzo Hybrid Infrastructure compute cluster as follows:
l On the Compute > Virtual machines > Images tab, click Add image.
l In the Add image window, click Browse, and then select the .qcow2 file.
l Specify the image name, select the Generic Linux OS type, and then click Add.
6. In the Compute > Virtual machines > Virtual machines tab, click Create virtual machine. A
window will open where you need to specify the following parameters:
l A name for the new virtual machine.
l In Deploy from, choose Image.
l In the Images window, select the .qcow2 image file of the appliance, and then click Done.
l In the Volumes window, you don’t need to add any volumes. The volume that is added
automatically for the system disk is sufficient.
l In the Flavor window, choose your desired combination of vCPUs and RAM, and then click
Done. Usually, 2 vCPUs and 4 GiB of RAM are enough.
l In the Network interfaces window, click Add, select the virtual network of type public, and
then click Add. It will appear in the Network interfaces list.
If you use a setup with more than one physical network (and thus, with more than one virtual
network of type public), repeat this step and select the virtual networks that you need.
7. Click Done.
8. Back in the Create virtual machine window, click Deploy to create and boot the virtual
machine.

Configuring the virtual appliance

After deploying the Agent for Virtuozzo Hybrid Infrastructure (Virtual Appliance), you need to
configure the virtual appliance so that it can reach both the Virtuozzo Hybrid Infrastructure cluster
that it will protect and the Cyber Protection cloud service.

To configure the virtual appliance

1. Log in to your Virtuozzo Hybrid Infrastructure account.

2. On the Compute > Virtual machines > Virtual Machines tab, select the virtual machine that
you created. Then, click Console.

144 © Acronis International GmbH, 2003-2024

3. Configure the network interfaces of the appliance. There may be one or more interfaces to
configure – it depends on the number of virtual networks that the appliance uses. Ensure that
automatically assigned DHCP addresses (if any) are valid within the networks that your virtual
machine uses or assign them manually.

4. Specify the Virtuozzo cluster address and credentials:

l DNS name or IP address of the Virtuozzo Hybrid Infrastructure cluster – this is the address of
the management node of the cluster. The default port 5000 will be automatically set. If you
use a different port, you need to specify it manually.
l In the User domain name field, specify your domain in Virtuozzo Hybrid Infrastructure. For
example, Default.
The domain name is case-sensitive.
l In the User name and Password fields, enter the credentials for Virtuozzo Hybrid
Infrastructure user account with Administrator role in the specified domain. For more
information about users, roles, and domains, refer to Configuring user accounts in Virtuozzo
Hybrid Infrastructure.

5. Register the appliance in the Cyber Protection service by using one of the following methods.
l [Only for tenants without two-factor authentication] Register the appliance in its graphical
interface.

145 © Acronis International GmbH, 2003-2024

 a. Under Agent options, in the Management Server field, click Change.
b. In the Server name/IP field, select Cloud.
The Cyber Protection service address appears. Do not change this address unless
instructed otherwise.
c. In the User name and Password fields, specify the credentials for your account in the
Cyber Protection service. The virtual appliance and the virtual machines that the appliance
manages are registered under this account.
d. Click OK.
l Register the appliance in the command-line interface.

Note
With this method, you need a registration token. For more information about how to
generate one, refer to "Generating a registration token" (p. 162).

a. Press CTRL+SHIFT+F2 to open the command-line interface.

b. Run the following command:

register_agent -o register -t cloud -a <service address> --token <registration

token>

Note
When you use a registration token, you must specify the exact data center address. This is
the URL that you see after you log in to the Cyber Protect console. For example,
https://eu2-cloud.company.com.

Do not use https://cloud.company.com here.

c. To return to the graphical interface of the appliance, press ALT+F1.

6. [If a proxy server is enabled in your network] Configure the proxy server.
a. Press CTRL+SHIFT+F2 to open the command-line interface.
b. Open the file /etc/Acronis/Global.config in a text editor.
c. Do one of the following:
l If the proxy settings were specified during the agent installation, find the following section:

<key name="HttpProxy">
<value name="Enabled" type="Tdword">"1"</value>
<value name="Host" type="TString">"ADDRESS"</value>
<value name="Port" type="Tdword">"PORT"</value>
<value name="Login" type="TString">"LOGIN"</value>
<value name="Password" type="TString">"PASSWORD"</value>
</key>

146 © Acronis International GmbH, 2003-2024

 l Otherwise, copy the above lines and paste them into the file between the <registry
name="Global">...</registry> tags.
d. Replace ADDRESS with the new proxy server host name/IP address, and PORT with the decimal
value of the port number.
e. If your proxy server requires authentication, replace LOGIN and PASSWORD with the proxy server
credentials. Otherwise, delete these lines from the file.
f. Save the file.
g. Open the file /opt/acronis/etc/aakore.yaml in a text editor.
h. Locate the env section or create it and add the following lines:

env:
http-proxy: proxy_login:proxy_password@proxy_address:port
https-proxy: proxy_login:proxy_password@proxy_address:port

i. Replace proxy_login and proxy_password with the proxy server credentials, and proxy_
address:port with the address and port number of the proxy server.
j. Run the reboot command.

Note
To be able to update a virtual appliance deployed behind a proxy, edit the appliance config.yaml
file ( /opt/acronis/etc/va-updater/config.yaml), by adding the following line to the bottom of
that file, and then entering values specific to your environment:

httpProxy: http://<proxy_login>:<proxy_password>@<proxy_address>:<port>

For example:

httpProxy: http://mylogin:[email protected]:8080

To protect the virtual machines in the Virtuozzo Hybrid Infrastructure cluster

1. Log in to your Cyber Protection account.

2. Navigate to Devices > Virtuozo Hybrid Infrastructure> <your cluster> > Default project >
admin or find your machines in Devices > All devices.

147 © Acronis International GmbH, 2003-2024

3. Select machines and apply a protection plan to them.

Deploying Agent for oVirt (Virtual Appliance)

Before you start

This appliance is a pre-configured virtual machine that you deploy in a Red Hat Virtualization/oVirt
data center. The appliance contains a protection agent that enables you to administer cyber
protection for all virtual machines in the data center.

System requirements for the agent

By default, the virtual machine with the agent uses 2 vCPUs and 4 GiB of RAM. These settings are
sufficient for most operations but you can edit them in Red Hat Virtualization/oVirt Administration
Portal.

To improve the backup performance and avoid failures related to insufficient RAM memory, we
recommend that you increase these resources to 4 vCPUs and 8 GiB of RAM in more demanding
cases. For example, increase the assigned resources when you expect the backup traffic to exceed
100 MB per second (for example, in 10-Gigabit networks) or if you back up simultaneously multiple
virtual machines with large hard drives (500 GB or more).

The size of the appliance virtual disk is 8 GiB.

How many agents do I need?

One agent can protect the entire data center. However, you can have more than one agent in the
data center if you need to distribute the backup traffic bandwidth load.

If you have more than one agent in the data center, the virtual machines are automatically
distributed between the agents, so that each agent manages a similar number of machines.

Automatic redistribution occurs when the load imbalance among the agents reaches 20 percent.
This may happen after you add or remove a machine or an agent. For example, you realize that you
need more agents to help with throughput and you deploy an additional virtual appliance to the

148 © Acronis International GmbH, 2003-2024

data center. The management server will assign the most appropriate machines to the new agent.
The old agents' load will reduce. When you remove an agent, the machines assigned to the agent
are redistributed among the remaining agents. However, this will not happen if an agent gets
corrupted or is deleted manually from Red Hat Virtualization/oVirt Administration Portal.
Redistribution will start only after you remove such an agent from the Cyber Protect console.

To check which agent manages a specific machine

1. In the Cyber Protect console, click Devices, and then select oVirt.
2. Click the gear icon in the upper right corner of the table, and under System, select the Agent
check box.
3. Check the name of the agent in the column that appears.

Limitations
The following operations are not supported for Red Hat Virtualization/oVirt virtual machines:

l Application-aware backup
l Running a virtual machine from a backup
l Replication of virtual machines
l Changed block tracking

Deploying the OVA template

1. Log in to your Cyber Protection account.
2. Click Devices > All devices > Add > Red Hat Virtualization (oVirt).
The .zip archive is downloaded to your machine.
3. Unpack the .zip archive. It contains one .ova file.
4. Upload the .ova file to a host in the Red Hat Virtualization/oVirt data center that you want to
protect.
5. Log in to Red Hat Virtualization/oVirt Administration Portal as an administrator. For more
information about the roles required for operations with virtual machines, refer to "Agent for
oVirt – required roles and ports" (p. 153).
6. From the navigation menu, select Compute > Virtual machines.

7. Click the vertical ellipsis icon above the main table, and then click Import.
8. In the Import Virtual Machine(s) window, do the following:
a. In Data center, select the data center that you want to protect.
b. In Source, select Virtual Appliance (OVA).
c. In Host, select the host on which you uploaded the .ova file.
d. In File Path, specify the path to the directory that contains the .ova file.
e. Click Load.
The oVirt virtual appliance template from the .ova file appears in the Virtual Machines on
Source panel.

149 © Acronis International GmbH, 2003-2024

 If the template does not appear in this panel, ensure that you have specified the correct path
to the file, the file is not damaged, and the host can be reached.
f. In Virtual Machines on Source, select the oVirt virtual appliance template, and then click the
right arrow.
The template appears in the Virtual machines to import panel.
g. Click Next.
9. In the new window, click the appliance name, and then configure the following settings:
l On the Network interfaces tab, configure the network interfaces.
l [Optional] On the General tab, change the default name of the virtual machine with the agent.

The deployment is now complete. Next, you have to configure the virtual appliance. For more
information on how to configure it, refer to "Configuring the virtual appliance" (p. 150).

Note
If you need more than one virtual appliance in your data center, repeat the steps above and deploy
additional virtual appliances. Do not clone an existing virtual appliance by using the Clone
VM option in Red Hat Virtualization/oVirt Administration Portal.

To exclude the virtual appliance from dynamic group backups, you must also exclude it from the list
of virtual machines in the Cyber Protect console. To exclude it, in Red Hat Virtualization/oVirt
Administration Portal, select the virtual machine with the agent, and then assign the tag acronis_
virtual_appliance to it.

Configuring the virtual appliance

After deploying the virtual appliance, you need to configure it so that it can reach both the oVirt
engine and the Cyber Protection service.

To configure the virtual appliance

1. Log in to Red Hat Virtualization/oVirt Administration Portal.

2. Select the virtual appliance that you want to configure, and then click the Console icon.
3. In the eth0 field, configure the network interfaces of the appliance.
Ensure that automatically assigned DHCP addresses (if any) are valid within the networks that
your virtual machine uses or assign them manually. Depending on the number of networks that
the appliance uses, there may be one or more interfaces to configure.
4. In the oVirt field, click Change to specify the oVirt engine address and credentials for accessing
it:
a. In the Server name/IP field, enter the DNS name or IP address of the engine.
b. In the User name and Password fields, enter the administrator credentials for this engine.
Ensure that this administrator account has the roles required for operations with Red Hat
Virtualization/oVirt virtual machines. For more information about these roles, refer to "Agent
for oVirt – required roles and ports" (p. 153).

150 © Acronis International GmbH, 2003-2024

 If Keycloak is the Single-Sign-On (SSO) provider for the oVirt engine (default in oVirt 4.5.1), use
the Keycloak format when specifying the user name. For example, specify the default
administrator account as admin@ovirt@internalsso instead of admin@internal.
c. [Optional] Click Check connection to ensure that the provided credentials are correct.
d. Click OK.
5. Register the appliance in the Cyber Protection service by using one of the following methods.
l [Only for tenants without two-factor authentication] Register the appliance in its graphical
interface.
a. Under Agent options, in the Management Server field, click Change.
b. In the Server name/IP field, select Cloud.
The Cyber Protection service address appears. Do not change this address unless
instructed otherwise.
c. In the User name and Password fields, specify the credentials for your account in the
Cyber Protection service. The virtual appliance and the virtual machines that the appliance
manages are registered under this account.
d. Click OK.
l Register the appliance in the command-line interface.

Note
With this method, you need a registration token. For more information about how to
generate one, refer to "Generating a registration token" (p. 162).

a. Press CTRL+SHIFT+F2 to open the command-line interface.

b. Run the following command:

register_agent -o register -t cloud -a <service address> --token <registration

token>

Note
When you use a registration token, you must specify the exact data center address. This is
the URL that you see after you log in to the Cyber Protect console. For example,
https://eu2-cloud.company.com.

Do not use https://cloud.company.com here.

c. To return to the graphical interface of the appliance, press ALT+F1.

6. [Optional] In the Name field, click Change to edit the default name for the virtual appliance,
which is localhost. This name is shown in the Cyber Protect console.
7. [Optional] In the Time field, click Change, and then select the time zone of your location to
ensure that the scheduled operations run at the appropriate time.

151 © Acronis International GmbH, 2003-2024

8. [Optional] [If a proxy server is enabled in your network] Configure the proxy server.
a. Press CTRL+SHIFT+F2 to open the command-line interface.
b. Open the file /etc/Acronis/Global.config in a text editor.
c. Do one of the following:
l If the proxy settings were specified during the agent installation, find the following section:

<key name="HttpProxy">
<value name="Enabled" type="Tdword">"1"</value>
<value name="Host" type="TString">"ADDRESS"</value>
<value name="Port" type="Tdword">"PORT"</value>
<value name="Login" type="TString">"LOGIN"</value>
<value name="Password" type="TString">"PASSWORD"</value>
</key>

l Otherwise, copy the above lines and paste them into the file between the <registry
name="Global">...</registry> tags.
d. Replace ADDRESS with the new proxy server host name/IP address, and PORT with the decimal
value of the port number.
e. If your proxy server requires authentication, replace LOGIN and PASSWORD with the proxy server
credentials. Otherwise, delete these lines from the file.
f. Save the file.
g. Open the file /opt/acronis/etc/aakore.yaml in a text editor.
h. Locate the env section or create it and add the following lines:

env:
http-proxy: proxy_login:proxy_password@proxy_address:port
https-proxy: proxy_login:proxy_password@proxy_address:port

i. Replace proxy_login and proxy_password with the proxy server credentials, and proxy_
address:port with the address and port number of the proxy server.
j. Run the reboot command.

Note
To be able to update a virtual appliance deployed behind a proxy, edit the appliance config.yaml
file ( /opt/acronis/etc/va-updater/config.yaml), by adding the following line to the bottom of
that file, and then entering values specific to your environment:

httpProxy: http://<proxy_login>:<proxy_password>@<proxy_address>:<port>

For example:

httpProxy: http://mylogin:[email protected]:8080

To protect virtual machines in the Red Hat Virtualization/oVirt data center

1. Log in to your Cyber Protection account.

2. Navigate to Devices > oVirt > <your cluster> or find your machines in Devices > All devices.

152 © Acronis International GmbH, 2003-2024

3. Select machines and apply a protection plan to them.

Agent for oVirt – required roles and ports

Required roles
For its deployment and operation, Agent for oVirt requires an administrator account with the
following roles assigned.

oVirt/Red Hat Virtualization 4.2 and 4.3/Oracle Virtualization Manager 4.3

l DiskCreator
l UserVmManager
l TagManager
l UserVmRunTimeManager
l VmCreator

oVirt/Red Hat Virtualization 4.4, 4.5

l SuperUser

Required ports
Agent for oVirt connects to the oVirt engine by using the URL that you specify when you configure
the virtual appliance. Usually, the engine URL has the following format: https://ovirt.company.com.
In this case, the HTTPS protocol and port 443 are used.

Non-default oVirt settings may require another port. You can find the exact port by analyzing the
URL format. For example:

oVirt engine URL Port Protocol

https://ovirt.company.com/ 443 HTTPS

http://ovirt.company.com/ 80 HTTP

https://ovirt.company.com:1234/ 1234 HTTPS

No additional ports are required for disk Read/Write operations, because the backup is performed
in the HotAdd mode.

Deploying Agent for Synology

Before you start

With Agent for Synology, you can back up files and folders from and to Synology NAS devices. The
NAS-specific properties and access permissions for shares, folders, and files are preserved.

153 © Acronis International GmbH, 2003-2024

Agent for Synology runs on the NAS device. Thus, you can use the resources of the device for off-
host data processing operations, such as backup replication, validation, and cleanup. To learn more
about these operations, refer to "Off-host data processing" (p. 190).

Note
Agent for Synology supports only NAS devices with x86_64 processors. ARM processors are not
supported.

You can recover a backup to the original or a new location on the NAS device, and to a network
folder that is accessible through that device. Backups in the cloud storage can also be recovered to a
non-original NAS device on which Agent for Synology is installed.

The table below summarizes the available backup sources and destinations.

Items to backup Where to backup

What to backup
(Backup source) (Backup destination)

Cloud storage
Local folder*
Local folder*
Files/folders
Network folder (SMB)**
Network folder (SMB)**
NFS folder

* Including USB drives that are attached to the NAS device.

Note
Encrypted folders are not supported. These folders are not shown in the Cyber Protection graphical
user interface.

** Using external network shares as backup source or backup destination via the SMB protocol is
only available for agents running on Synology DiskStation Manager 6.2.3 and later. The data hosted
on the Synology NAS itself, including in hosted network shares, can be backed up without
limitations.

Limitations
l Agent for Synology supports only NAS devices with x86_64 processors. ARM processors are not
supported.
l Backed-up encrypted shares are recovered as non-encrypted.
l Backed-up shares for which the File compression option is enabled are recovered with this
option disabled.
l You can recover to a Synology NAS device only backups that are created by Agent for Synology.

154 © Acronis International GmbH, 2003-2024

Downloading the setup program
The setup program for Agent for Synology is available as an SPK file.

Agent for Synology 7.x

To download the setup program

1. In the Cyber Protect console, navigate to Devices > All devices.

2. In the upper-right corner, click Add.
3. Under Network attached storage (NAS), click Synology.
The setup program is downloaded to your machine.

Agent for Synology 6.x

To download the setup program

1. In the Cyber Protect console, navigate to Devices > All devices.

2. In the upper-right corner, click Add.
3. Under Network attached storage (NAS), click Synology.
The setup program for Agent for Synology 7.x is downloaded to your machine.
You can safely stop the download process or ignore the downloaded file.
4. Click Download Agent for Synology 6.x.
The setup program for Agent for Synology 6.x is downloaded to your machine.

Installing Agent for Synology

To install Agent for Synology, run the SPK file in Synology DiskStation Manager.

Note
Agent for Synology supports only NAS devices with x86_64 processors. ARM processors are not
supported.

Agent for Synology 7.x

Prerequisites
l The NAS device runs DiskStation Manager 7.x.
l You are a member of the administrators group on the NAS device.
l There are at least 200 MB of free space on the NAS volume on which you want to install the
agent.
l An SSH client is available on your machine. This document uses Putty as an example.

To install Agent for Synology

1. Log in to Synology DiskStation Manager.

2. Open Package Center.

155 © Acronis International GmbH, 2003-2024

 3. Click Manual Install, and then click Browse.

4. Select the SPK file that you downloaded from the Cyber Protect console, and then click Next.
A warning that you will install a third-party software package is shown. This message is part of
the standard installation procedure.
5. To confirm that you want to install the package, click Agree.
6. Select the volume on which you want to install the agent, and then click Next.
7. Check the settings, and then click Done.
8. In Synology DiskStation Manager Package Center, open Cyber Protect Agent for Synology, and
then verify that you see the following screen.

9. In Synology DiskStation Manager Control Panel, go to Terminal & SNMP, and then enable the
SSH access to the NAS device.
10. Run the install script on the NAS device by using an SSH client (in this example, Putty).
The script enables the root access to DSM 7.0 or later, which is required to configure the agent.

156 © Acronis International GmbH, 2003-2024

 a. Start Putty, and then specify the IP address or host name of your Synology NAS device.

b. Click Open, and then log in as a Synology DSM administrator.

c. Run the following command.

sudo /var/packages/CyberProtectAgent/target/install/install

After the script starts, wait for 15 seconds during which the Cyber Protection services
initialize.
11. In Synology DiskStation Manager Control Panel, go to Terminal & SNMP, and then disable the
SSH access to the NAS device. The SSH access is no longer required.
12. In Synology DiskStation Manager Package Center, open Cyber Protect Agent for Synology.
13. Select the registration method.

157 © Acronis International GmbH, 2003-2024

 l [To register the agent by using credentials]
o In the User name and Password fields, specify credentials for the account under which the
agent will be registered. This account cannot be a partner administrator account.
l [To register the agent by using a registration token]
o In Registration address, specify the exact data center address. The exact data center
address is the URL that you see after you log in to the Cyber Protect console. For example,
https://us5-cloud.acronis.com.

Note
Do not use a URL format without the data center address. For example, do not use
https://cloud.acronis.com.

o In the Token field, specify the registration token.

For more information on how to generate a registration token, see "Generating a
registration token" (p. 162).
14. Click Register.

Agent for Synology 6.x

Prerequisites
l The NAS device runs DiskStation Manager 6.2.x.
l You are a member of the administrators group on the NAS device.
l There are at least 200 MB of free space on the NAS volume on which you want to install the
agent.

To install Agent for Synology

1. Log in to Synology DiskStation Manager.

2. Open Package Center.
3. Click Manual Install, and then click Browse.

4. Select the SPK file that you downloaded from the Cyber Protect console, and then click Next.
A warning that you will install a package without a digital signature is shown. This message is
part of the standard installation procedure.
5. To confirm that you want to install the package, click Yes.
6. Select the volume on which you want to install the agent, and then click Next.

158 © Acronis International GmbH, 2003-2024

 7. Check the settings, and then click Apply.
8. In Synology DiskStation Manager Package Center, open Cyber Protect Agent for Synology.
9. Select the registration method.

l [To register the agent by using credentials]

o In the User name and Password fields, specify credentials for the account under which the
agent will be registered. This account cannot be a partner administrator account.
l [To register the agent by using a registration token]
o In Registration address, specify the exact data center address. The exact data center
address is the URL that you see after you log in to the Cyber Protect console. For example,
https://us5-cloud.acronis.com.

Note
Do not use a URL format without the data center address. For example, do not use
https://cloud.acronis.com.

o In the Token field, specify the registration token.

For more information on how to generate a registration token, see "Generating a
registration token" (p. 162).
10. Click Register.

When the registration completes, the Synology NAS device appears in the Cyber Protect console, on
the Devices > Network Attached Storage tab.

To back up the data on the NAS device, apply a protection plan.

Updating Agent for Synology

You can update Agent for Synology 6.x to a newer version of Agent for Synology 6.x. Similarly, you
can update Agent for Synology 7.x to a newer version of Agent for Synology 7.x.

To update the agent, run the newer version of the setup program in Synology DiskStation Manager.
The original registration of the agent, its settings, and the plans that are applied to the protected
workloads will be preserved.

Note
You cannot update the agent from the Cyber Protect console.

159 © Acronis International GmbH, 2003-2024

Upgrading Agent for Synology 6.x to Agent for Synology 7.x is supported only by uninstalling the
older agent and installing the newer agent. In this case, all protection plans are revoked and you
must re-apply them manually.

Agent for Synology 7.x

Prerequisites
l You are a member of the administrators group on the NAS device.
l There are at least 200 MB of free space on the NAS volume on which you want to install the
agent.
l An SSH client is available on your machine. This document uses Putty as an example.

To update Agent for Synology

1. In DiskStation Manager, open Package Center.

2. Click Manual Install, and then click Browse.
3. Select the newer SPK file for Agent for Synology 7.x that you downloaded from the Cyber Protect
console, and then click Next.
A warning that you will install a third-party software package is shown. This message is part of
the standard installation procedure.
4. To confirm that you want to install the package, click Agree.
5. Check the settings, and then click Done.
6. In Synology DiskStation Manager Package Center, open Cyber Protect Agent for Synology, and
then verify that you see the following screen.

7. In Synology DiskStation Manager Control Panel, go to Terminal & SNMP, and then enable the
SSH access to the NAS device.
8. Run the install script on the NAS device by using an SSH client (in this example, Putty).
The script enables the root access to DSM 7.0 or later, which is required to configure the agent.

160 © Acronis International GmbH, 2003-2024

 a. Start Putty, and then specify the IP address or host name of your Synology NAS device.

b. Click Open, and then log in as a Synology DSM administrator.

c. Run the following command.

sudo /var/packages/CyberProtectAgent/target/install/install

9. In Synology DiskStation Manager Control Panel, go to Terminal & SNMP, and then disable the
SSH access to the NAS device. The SSH access is no longer required.

Agent for Synology 6.x

Prerequisites
l You are a member of the administrators group on the NAS device.
l There are at least 200 MB of free space on the NAS volume on which you want to install the
agent.

To update Agent for Synology

1. In DiskStation Manager, open Package Center.

2. Click Manual Install, and then click Browse.
3. Select the newer SPK file for Agent for Synology 6.x that you downloaded from the Cyber Protect
console, and then click Next.

161 © Acronis International GmbH, 2003-2024

 A warning that you will install a package without a digital signature is shown. This message is
part of the standard installation procedure.
4. To confirm that you want to install the package, click Yes.
5. Check the settings, and then click Apply.

Deploying agents through Group Policy

You can centrally install (or deploy) Agent for Windows onto machines that are members of an
Active Directory domain, by using Windows Group Policy.

In this section, you will find out how to set up a Group Policy object to deploy agents onto machines
in an entire domain or in its organizational unit.

Every time a machine logs on to the domain, the resulting Group Policy object will ensure that the
agent is installed and registered.

Prerequisites
l Active Directory domain with a domain controller running Microsoft Windows Server 2003 or
later.
l You must be a member of the Domain Admins group in this domain.
l You have downloaded the All agents for Windows setup program.
To download the setup program, in the Cyber Protect console, click the account icon in the top-
right corner, and then click Downloads. The download link is also available in the Add devices
pane.

To deploy agents through Group Policy

1. Generate a registration token as described in "Generating a registration token" (p. 162).

2. Create the .mst file, the .msi file, and the .cab files, as described in "Creating the transform file
and extracting the installation packages" (p. 165).
3. Set up the Group Policy object as described in "Setting up the Group Policy object" (p. 166).

Generating a registration token

A registration token passes the identity of a user to the agent setup program, without storing the
user credentials for the Cyber Protect console. This enables users to register any number of
machines under their account or apply protection plans to their workloads without having to log in.

Note
Protection plans are not applied automatically during machine registration. Applying a protection
plan is a separate task.

For security reasons, the tokens have limited lifetime, which you can adjust. The default lifetime is 3
days.

162 © Acronis International GmbH, 2003-2024

Users can generate registration tokens only for their own accounts. Administrators can generate
registration tokens for all user accounts in the tenant that they manage.

To generate a registration token

As a user

1. Log in to the Cyber Protect console.

2. Click Devices > All devices > Add.
The Add devices pane opens on the right.
3. Scroll down to Registration token, and then click Generate.

4. Specify the token lifetime.

5. Click Generate token.
6. Click Copy to copy the token to your device clipboard, or write the token down manually.

As an administrator

1. Log in to the Cyber Protect console as an administrator.

If you are already signed in to the management portal, you can go to the Cyber Protect console
by navigating to Monitoring > Usage, and then, under the Protection tab, clicking Manage
service.

163 © Acronis International GmbH, 2003-2024

 [For partner administrators who manage customer tenants] In the Cyber Protect console, select
the tenant with the user for whom you want to generate a token. You cannot generate a token
on the All customers level.

2. Under Devices, click All devices > Add.

The Add devices pane opens on the right.
3. Scroll down to Registration token, and then click Generate.

4. Specify the token lifetime.

5. Select the user for whom you want to generate a token.

Note
When you use the token, workloads will be registered under the user account that you select
here.

6. [Optional] To enable the user of the token to apply and revoke a protection plan on the added
workloads, select the plan from the drop-down list.

164 © Acronis International GmbH, 2003-2024

 Note that you will need to run a script that will apply or revoke a protection plan on the added
workloads. Refer to this knowledge base article for more details.
7. Click Generate token.
8. Click Copy to copy the token to your device clipboard, or write the token down manually.

To view or delete registration tokens

1. Log in to the Cyber Protect console.

2. Click Devices > All devices > Add.
3. Scroll down to Registration token, and then click Manage active tokens.
A list with the active tokens that are generated for your tenant opens on the right.

Note
For security reasons, in the Token column, only the first two characters of the token value are
shown.

4. [To delete a token] Select the token, and then click Delete.

Creating the transform file and extracting the installation packages

To deploy protection agents via Windows Group Policy, you need a transform file (.mst), and the
installation packages (.msi and .cab files).

Note
The procedure below uses the default registration option, which is registration by token. To learn
how to generate a registration token, refer to "Generating a registration token" (p. 162).

To create the .mst file and extract the installation packages (.msi and .cab files)

1. Log in as an administrator on any machine in the Active Directory domain.

2. Create a shared folder that will contain the installation packages. Ensure that domain users can
access the shared folder—for example, by leaving the default sharing settings for Everyone.
3. Run the agent setup program.
4. Click Create .mst and .msi files for unattended installation.
5. In What to install, select the components that you want to include in the installation, and then
click Done.
6. In Registration settings, click Specify, enter a registration token, and then click Done.
You can change the registration method from Use registration token (default) to Use
credentials or Skip registration. The Skip registration option presumes that you will register
the workloads manually later.
7. Review or modify the installation settings, which will be added to the .mst file, and then click
Proceed.
8. In Save the files to, specify the path to the shared folder that you created.
9. Click Generate.

165 © Acronis International GmbH, 2003-2024

 As a result, the .mst file, the .msi file, and the .cab files are created and copied to the shared folder
that you specified.

Next, set up the Windows Group Policy object. To learn how to do it, refer to "Setting up the Group
Policy object" (p. 166).

Setting up the Group Policy object

In this procedure you use the installation packages that you created in "Creating the transform file
and extracting the installation packages" (p. 165) to set up a Group Policy object (GPO). The GPO will
deploy the agents onto the machines in your domain.

To set up the Group Policy object

1. Log in to the domain controller as a domain administrator.

If the domain has more than one domain controller, log in to any of them as a domain
administrator.
2. [If you deploy agents in an organizational unit] Ensure that the organizational unit in which you
want to deploy the agents exists in this domain.
3. In the Windows Start menu, point to Administrative Tools, and then click Group Policy
Management (or Active Directory Users and Computers for Windows Server 2003).
4. [For Windows Server 2008 or later] Right-click the name of the domain or organizational unit,
and then click Create a GPO in this domain, and Link it here.
5. [For Windows Server 2003] Right-click the name of the domain or organizational unit, and then
click Properties. In the dialog box, click the Group Policy tab, and then click New.
6. Name the new Group Policy object Agent for Windows.
7. Open the Agent for Windows Group Policy object for editing:
l [In Windows Server 2008 or later] Under Group Policy Objects, right-click the Group Policy
object, and then click Edit.
l [In Windows Server 2003] Click the Group Policy object, and then click Edit.
8. In the Group Policy object editor snap-in, expand Computer Configuration.
9. [For Windows Server 2012 or later] Expand Policies > Software Settings.
10. [For Windows Server 2003 and Windows Server 2008] Expand Software Settings.
11. Right-click Software installation, point to New, and then click Package.
12. Select the agent's .msi installation package in the shared folder that you created, and then click
Open.
13. In the Deploy Software dialog box, click Advanced, and then click OK.
14. On the Modifications tab, click Add, and then select the .mst file in the shared folder that you
created.
15. Click OK to close the Deploy Software dialog box.

166 © Acronis International GmbH, 2003-2024

SSH connections to a virtual appliance
Use a Secure Socket Shell (SSH) connection when you remotely access a virtual appliance, for
maintenance purposes.

Starting the Secure Shell daemon

To allow SSH connections to a virtual appliance, start the Secure Shall daemon (sshd) on the
appliance.

To start the Secure Shall daemon

1. In the hypervisor software, open the console of the virtual appliance.

2. In the graphical user interface of the appliance, press CTRL+SHIFT+F2 to open the command-line
interface.
3. Run the following command:

/bin/sshd

4. [Only during the first connection to the appliance] Set the password for the root user.
To learn how to set the password, see "Setting the root password on a virtual appliance" (p. 167).

Note
We recommend that you stop the Secure Shell daemon when you do not use the SSH connection.

Setting the root password on a virtual appliance

Before establishing an SSH connection to a virtual appliance for the first time, you must set the root
password on the appliance.

To set the root password

1. In the hypervisor software, open the console of the virtual appliance.

2. In the graphical user interface of the appliance, press CTRL+SHIFT+F2 to open the command-line
interface.
3. Run the following command:

passwd

4. Specify a password, and then press Enter.

The password must contain at least nine characters and must have complexity score of three or
more. The complexity score is calculated automatically. To reach higher score, use a combination
of special symbols, uppercase and lowercase symbols, and digits.
5. Confirm the password, and then press Enter.

167 © Acronis International GmbH, 2003-2024

Accessing a virtual appliance via an SSH client

Prerequisites
l An SSH client must be available on the remote machine. The procedure below uses the WinSCP
client as an example. You can use any SSH client, by adapting the steps accordingly.
l The Secure Shell daemon (sshd) must be started on the virtual appliance. For more information,
see "Starting the Secure Shell daemon" (p. 167).

To access a virtual appliance via WinSCP

1. On the remote machine, open WinSCP.

2. Click Session > New Session.
3. In File protocol, select SCP.
4. In Host name, specify the IP address of your virtual appliance.
5. In User name and Password, specify root and the password for the root user.
6. Click Login.

A list of all directories on the virtual appliance is shown.

Updating agents
You can update all agents manually either by using the Cyber Protect console or by downloading
and running the installation file.

You can configure automatic updates for the following agents:

l Agent for Windows

l Agent for Linux
l Agent for Mac
l Cyber Files Cloud Agent for File Sync & Share

4.2 GB of free space in the following location is required to update an agent automatically, or
manually by using the Cyber Protect console:

l For Linux – the root directory

l For Windows – the volume where the agent is installed

5 GB of free space is required to update an agent in macOS – in the root directory.

168 © Acronis International GmbH, 2003-2024

Note
[For all agents provided in the form of a virtual appliance, including Agent for VMware, Agent for
Scale Computing, Agent for Virtuozzo Hybrid Infrastructure, Agent for RHV (oVirt)]

In order to perform automatic or manual update of a virtual appliance located behind a proxy, the
proxy server must be configured on each appliance as follows.

In the /opt/acronis/etc/va-updater/config.yaml file, add the following line to the bottom of the file
and enter the values specific to your environment:

httpProxy: http://proxy_login:proxy_password@proxy_address:port

Updating agents manually

You can update agents either by using the Cyber Protect console or by downloading and running
the installation file.

Virtual appliances with the following versions must be updated only by using the Cyber Protect
console:

l Agent for VMware (Virtual Appliance): version 12.5.23094 and later.

l Agent for Virtuozzo Hybrid Infrastructure (Virtual Appliance): version 12.5.23094 and later.

Agents with the following versions can also be updated by using the Cyber Protect console:

l Agent for Windows, Agent for VMware (Windows), Agent for Hyper-V: version 12.5.21670 and
later.
l Agent for Linux: version 12.5.23094 and later.
l Other agents: version 12.5.23094 and later.

To find the agent version, in the Cyber Protect console, select the machine, and then click Details.

To update earlier agent versions of those agents, download and install the newest version manually.
To find the download links, click All devices > Add.

Prerequisites
On Windows machines, Cyber Protect features require Microsoft Visual C++ 2017 Redistributable.
Ensure that it is already installed on your machine or install it before updating the agent. After the
installation, a restart may be required. You can find the Microsoft Visual C++ Redistributable
package on the Microsoft website: https://support.microsoft.com/help/2999226/update-for-
universal-c-runtime-in-windows.

To update an agent by using the Cyber Protect console

1. Click Settings > Agents.

The software displays the list of machines. The machines with outdated agent versions are
marked with an orange exclamation mark.

169 © Acronis International GmbH, 2003-2024

2. Select the machines that you want to update the agents on. The machines must be online.
3. Click Update agent.

Note
During the update, any backups that are in progress will fail.

To update Agent for VMware (Virtual Appliance) whose version is below 12.5.23094

1. Click Settings > Agents > the agent that you want to update > Details, and then examine the
Assigned virtual machines section. You will need to re-enter these settings after the update.
a. Make note of the position of the Automatic assignment switch.
b. To find out what virtual machines are manually assigned to the agent, click the Assigned: link.
The software displays the list of assigned virtual machines. Make note of the machines that
have (M) after the agent name in the Agent column.
2. Remove Agent for VMware (Virtual Appliance), as described in "Uninstalling agents". In step 5,
delete the agent from Settings > Agents, even though you are planning to install the agent
again.
3. Deploy Agent for VMware (Virtual Appliance), as described in "Deploying the OVF template".
4. Configure Agent for VMware (Virtual Appliance), as described in "Configuring the virtual
appliance".
If you want to reconstruct the locally attached storage, in step 7 do the following:
a. Add the disk containing the local storage to the virtual appliance.
b. Click Refresh > Create storage > Mount.
c. The software displays the original Letter and Label of the disk. Do not change them.
d. Click OK.
5. Click Settings > Agents > the agent that you want to update > Details, and then reconstruct the
settings that you made note of in step 1. If some virtual machines were manually assigned to the
agent, assign them again as described in "Virtual machine binding".
Once the agent configuration is completed, the protection plans that were applied to the old
agent are re-applied automatically to the new agent.
6. The plans with application-aware backup enabled require the guest OS credentials to be re-
entered. Edit these plans and re-enter the credentials.
7. The plans that back up ESXi configuration require the "root" password to be re-entered. Edit
these plans and re-enter the password.

To update the Cyber Protection definitions on a machine

1. Click Settings > Agents.

2. Select the machine on which you want to update the Cyber Protection definitions and click
Update definitions. The machine must be online.

To assign the Updater role to an agent

170 © Acronis International GmbH, 2003-2024

1. Click Settings > Agents.
2. Select the machine to which you want to assign the Updater role, click Details, and then in the
Cyber Protection definitions section, enable Use this agent to download and distribute
patches and updates.

Note
An agent with the Updater role can download and distribute patches only for Windows third-
party products. For Microsoft products, patch distribution is not supported by the Updater
agent.

To clear cached data on an agent

1. Click Settings > Agents.

2. Select the machine on which you want to clear the cached data (outdated update files and patch
management data) and click Clear cache.

Updating agents automatically

To facilitate management of multiple workloads, you can configure automatic updates for Agent for
Windows, Agent for Linux, and Agent for Mac. Automatic updates are available for agents version
15.0.26986 (released in May 2021) or later. Older agents must be updated manually to the latest
version, first.

Automatic updates are supported on machines running any of the following operating systems:

l Windows XP SP 3 and later

l Red Hat Enterprise Linux 6 and later, CentOS 6 and later
l OS X 10.9 Mavericks and later

The settings for automatic updates are preconfigured on a data center level. A company
administrator can customize these settings – for all machines in a company or a unit, or for
individual machines. If no custom settings are applied, then the settings from the upper level are
used, in this order:

1. Cyber Protection data center

2. Company (customer tenant)
3. Unit
4. Machine

For example, a unit administrator can configure custom auto-update settings for all machines in the
unit, which might differ from the setting applied to the machines on the company level. The
administrator can also configure different settings for one or more individual machines in the unit,
to which neither the unit settings nor the company settings will be applied.

After enabling the automatic updates, you can configure the following options:

171 © Acronis International GmbH, 2003-2024

l Update channel
The update channel defines which version of the agents will be used – the most up-to-date one or
the latest version from the previous release.
l Maintenance window
The maintenance window defines when updates can be installed. If the maintenance window is
disabled, updates can run anytime.
Even within the enabled maintenance window, updates will not be installed while the agent is
running any of the following operations:
o Backup
o Recovery
o Backup replication
o Virtual machine replication
o Testing a replica
o Running a virtual machine from backup (including finalization)
o Disaster recovery failover
o Disaster recovery failback
o Running a script (for Cyber Scripting functionality)
o Patch installation
o ESXi configuration backup

To customize auto-update settings

1. In the Cyber Protect console, go to Settings > Agents.

2. Select the scope for the settings:
l To change the settings for all machines, click Edit default agent update settings.
l To change the settings for specific machines, select the desired machines, and then click
Agent update settings.
3. Configure the settings according to your needs, and then click Apply.

To remove the custom auto-update settings

1. In the Cyber Protect console, go to Settings > Agents.

2. Select the scope for the settings:
l To remove the custom settings for all machines, click Edit default agent update settings.
l To remove the custom settings for specific machines, select the desired machines, and then
click Agent update settings.
3. Click Reset to default settings, and then click Apply.

To check the auto-update status

1. In the Cyber Protect console, go to Settings > Agents.

2. Click the gear icon in the upper right corner of the table, and then ensure that Auto-update
check box is selected.
3. Check the status that is shown in the Auto-update column.

172 © Acronis International GmbH, 2003-2024

Updating agents on BitLocker-protected workloads
Agent updates that introduce changes to Startup Recovery Manager interfere with BitLocker on
workloads on which both BitLocker and Startup Recovery Manager are enabled. In this case, after a
restart, the BitLocker recovery key is required. To mitigate this issue, suspend or disable BitLocker
before you update the agent.

Affected agent versions:

l 23.12.36943, released in December 2023

You can also check whether an update introduces changes to Startup Recovery Manager in the
release notes of the protection agent.

To update the agent on a workload with BitLocker and Startup Recovery Manager enabled

1. On the workload on which you want to update the agent, suspend or disable BitLocker.
2. Update the agent.
3. Restart the workload.
4. Enable BitLocker.

Preventing unauthorized uninstallation or modification

of agents
You can protect Agent for Windows against unauthorized uninstallation or modification, by enabling
the Password protection setting in a protection plan. This setting is available only when the Self-
protection setting is enabled.

To enable Password protection

1. In a protection plan, expand the Antivirus & Antimalware protection module (Active
Protection module for Cyber Backup editions).
2. Click Self-protection and ensure that the Self-protection switch is enabled.
3. Enable the Password protection switch.
4. In the window that opens, copy the password that you need to uninstall or modify the
components of a protected Agent for Windows.
This password is unique and you will not be able to recover it once you close this window. If you
lose or forget this password, you can edit the protection plan and create a new password.
5. Click Close.
6. In the Self-protection pane, click Done.
7. Save the protection plan.

173 © Acronis International GmbH, 2003-2024

Password protection will be enabled for the machines to which this protection plan is applied.
Password protection is only available for Agent for Windows version 15.0.25851 or newer. The
machines must be online.

You can apply a protection plan with Password protection enabled to a machine running macOS,
but no protection will be provided. You cannot apply such a plan to a machine running Linux.

Also, you cannot apply more than one protection plan with Password protection enabled to the
same Windows machine. To learn how to resolve a possible conflict, refer to Resolving plan conflicts.

To change the password in an existing protection plan

1. In the protection plan, expand the Antivirus & Antimalware protection module (Active
Protection module for Cyber Backup edition).
2. Click Self-protection.
3. Click Create new password.
4. In the window that opens, copy the password that you need to uninstall or modify the
components of a protected Agent for Windows.
This password is unique and you will not be able to recover it once you close this window. If you
lose or forget this password, you can edit the protection plan and create a new password.
5. Click Close.
6. In the Self-protection pane, click Done.
7. Save the protection plan.

Uninstalling agents
When you uninstall an agent from a workload, the workload is automatically removed from the
Cyber Protect console. If the workload is still shown after you uninstall the agent, for example, due
to a network problem, manually remove this workload from the console. For more information
about how to do it, refer to "Removing workloads from the Cyber Protect console" (p. 320).

Note
Uninstalling an agent does not delete any plans or backups.

To uninstall an agent

Windows

1. Sign in as an administrator to the machine with the agent .

2. In Control panel, go to Programs and Features (Add or Remove Programs in Windows XP).
3. Right-click Acronis Cyber Protect, and then select Uninstall.
4. [For password-protected agents] Specify the password that is required to uninstall the agent,
and then click Next.
5. [Optional] Select the Remove the logs and configuration settings check box.

174 © Acronis International GmbH, 2003-2024

 If you are planning to install the agent again, keep this check box cleared. If you select the check
box and then install the agent again, this workload might be duplicated in the Cyber Protect
console and its old backups might not be associated with it.
6. Click Uninstall.

Linux

1. On the machine with the agent, run /usr/lib/Acronis/BackupAndRecovery/uninstall/uninstall as

the root user.
2. [Optional] Select the Clean up all product traces (Remove the product's logs, tasks, vaults,
and configuration settings) check box.
If you are planning to install the agent again, keep this check box cleared. If you select the check
box and then install the agent again, this workload might be duplicated in the Cyber Protect
console and its old backups might not be associated with it.
3. Confirm your decision.

macOS

1. On the machine with the agent, double-click the installation .dmg file.
2. Wait until the operating system mounts the installation disk image.
3. Inside the image, double-click Uninstall.
4. If prompted, provide administrator credentials.
5. Confirm your decision.

To uninstall components that are bundled with Agent for Windows

You can uninstall individual components that are bundled with Agent for Windows, such as Cyber
Protect Monitor, Agent for Data Loss Prevention, or Bootable Media Builder, without uninstalling
Agent for Windows.

1. Sign in as an administrator to the machine with the agent.

2. Run the setup program, and then click Modify installed components.
3. Clear the check boxes next to the components that you want to uninstall, and then click Done.

To remove Agent for VMware (Virtual appliance)

1. By using the vSphere Client, log in to vCenter Server.

2. [If the virtual appliance is powered on] Right-click the virtual appliance, and then click Power >
Power Off. Confirm your decision.
3. [If the virtual appliance uses a locally attached storage on a virtual disk and you want to preserve
data on that disk] Remove the virtual storage from the virtual appliance.
a. Right-click the virtual appliance, and then click Edit Settings.
b. Select the disk with the storage, and then click Remove.
c. Under Removal Options, click Remove from virtual machine.
d. Click OK.

175 © Acronis International GmbH, 2003-2024

 As a result, the disk remains in the datastore. You can attach the disk to another virtual
appliance.
4. Right-click the virtual appliance, and then click Delete from Disk. Confirm your decision.
5. [Optional] [If you are not planning to use this appliance again] In the Cyber Protect console, go to
Backup storage > Locations, and then delete the location corresponding to the locally attached
storage.

Protection settings
To configure the general protection settings for Cyber Protection, in the Cyber Protect console, go to
Settings > Protection.

Automatic updates for components

By default, all agents can connect to the Internet and download updates.

An administrator can minimize the network bandwidth traffic by selecting one or several agents in
the environment and assigning the Updater role to them. Thus, the dedicated agents will connect to
the Internet and download updates. All other agents will connect to the dedicated updater agents
by using peer-to-peer technology, and then download the updates from them.

The agents without the Updater role will connect to the Internet if there is no dedicated updater
agent in the environment, or if the connection to a dedicated updater agent cannot be established
for about five minutes.

The updater agent distributes updates and patches for Antivirus and Antimalware protection,
Vulnerability assessment, and Patch management, but does not include updates of the agent
version.

Note
An agent with the Updater role can download and distribute patches only for Windows third-party
products. For Microsoft products, patch distribution is not supported by the Updater agent.

Before assigning the Updater role to an agent, ensure that the machine on which the agent runs is
powerful enough, and has a stable high-speed Internet connection and enough disk space.

To prepare a machine for the Updater role

1. On agent machine where you plan to enable the Updater role, apply the following firewall rules:
l Inbound (incoming) "updater_incoming_tcp_ports": allow connection to TCP ports 18018 and
6888 for all firewall profiles (public, private, and domain).
l Inbound (incoming) "updater_incoming_udp_ports": allow connection to UDP port 6888 for all
firewall profiles (public, private, and domain).
2. Restart the Acronis Agent Core Service.
3. Restart the Firewall Service.

176 © Acronis International GmbH, 2003-2024

If you do not apply these rules and the firewall is enabled, peer agents will download the updates
from the Cloud.

To assign the Updater role to a protection agent

1. In the Cyber Protect console, go to Settings > Agents.

2. Select the machine with the agent to which you want to assign the Updater role.
3. Click Details, and then enable the Use this agent to download and distribute patches and
updates switch.

The peer-to-peer update works as follows.

1. The agent with the Updater role checks by schedule the index file provided by the service
provider to update the core components.
2. The agent with the Updater role starts to download and distribute updates to all agents.

You can assign the Updater role to multiple agents in the environment. Thus, if an agent with the
Updater role is offline, other agents with this role can serve as the source for definition updates.

Updating the Cyber Protection definitions by schedule

On the Schedule tab, you can set up the schedule for automatic update of the Cyber Protection
definitions for each of the following components:

l Antimalware
l Vulnerability assessment
l Patch management

To change the definition updates setting, navigate to Settings > Protection > Protection
definitions update > Schedule.

Schedule type:

l Daily – define on which days of the week to update definitions.

Start at – select at what time to update definitions.
l Hourly – define more granular hourly schedule for updates.
Run every – define the periodicity of updates.
From ... To – define a specific time range for the updates.

Updating the Cyber Protection definitions on-demand

To update the Cyber Protection definitions for a particular machine on-demand

1. In the Cyber Protect console, go to Settings > Agents.

2. Select the machines on which you want to update the protection definitions, and then click
Update definitions.

Cache storage
The location of cached data is the following:

177 © Acronis International GmbH, 2003-2024

l On Windows machines: C:\ProgramData\Acronis\Agent\var\atp-downloader\Cache
l On Linux machines: /opt/acronis/var/atp-downloader/Cache
l On macOS machines: /Library/Application Support/Acronis/Agent/var/atp-downloader/Cache

To change the cache storage setting, navigate to Settings > Protection > Protection definitions
update > Cache Storage.

In Outdated update files and patch management data, specify after what period to remove
cached data.

Maximum cache storage size (GB) for agents:

l Updater role – define storage size for cache on the machines with the Updater role.
l Other roles – define storage size for cache on other machines.

Note
Cyber Protection collects samples of detected malware for additional analysis so that we can
improve our software. You can change this setting at any time in the Protection tab, by disabling
the Collect and upload malware samples to CPOC toggle.

Changing the service quota of machines

A service quota is automatically assigned when a protection plan is applied to a machine for the first
time.

The most appropriate quota is assigned, depending on the type of the protected machine, its
operating system, required level of protection, and the quota availability. If the most appropriate
quota is not available in your organization, the second-best quota is assigned. For example, if the
most appropriate quota is Web Hosting Server but it is not available, the Server quota is assigned.

Examples of quota assignment:

l A physical machine that runs a Windows Server or a Linux server operating system (such as
Ubuntu Server) is assigned the Server quota.
l A physical machine that runs a Windows or a Linux desktop operating system (such as Ubuntu
Desktop) is assigned the Workstation quota.
l A physical machine that runs Windows 10 with enabled Hyper-V role is assigned the Workstation
quota.
l A desktop machine that runs on a virtual desktop infrastructure and whose protection agent is
installed inside the guest operating system (for example, Agent for Windows), is assigned the
Virtual machine quota. This type of machine can also use the Workstation quota if the Virtual
machine quota is not available.
l A desktop machine that runs on a virtual desktop infrastructure and which is backed up in the
agentless mode (for example, by Agent for VMware or Agent for Hyper-V), is assigned the Virtual
machine quota.
l A Hyper-V or vSphere server is assigned the Server quota.

178 © Acronis International GmbH, 2003-2024

l A server with cPanel or Plesk is assigned the Web Hosting Server quota. It can also use the
Virtual machine or the Server quota, depending on the type of machine on which the web
server runs, if the Web Hosting Server quota is not available.
l The application-aware backup requires the Server quota, even for a workstation.

You can manually change the original assignment later. For example, to apply a more advanced
protection plan to the same machine, you might need to upgrade the machine's service quota. If the
features required by this protection plan are not supported by the currently assigned service quota,
the protection plan will fail.

Alternatively, you can change the service quota if you purchase a more appropriate quota after the
original one is assigned. For example, the Workstation quota is assigned to a virtual machine. After
you purchase a Virtual machines quota, you can manually assign this quota to the machine,
instead of the original Workstation quota.

You can also release the currently assigned service quota, and then assign this quota to another
machine.

You can change the service quota of an individual machine or for a group of machines.

To change the service quota of an individual machine

1. In the Cyber Protect console, go to Devices.

2. Select the desired machine, and then click Details.
3. In the Service quota section, click Change.
4. In the Change quota window, select the desired service quota or No quota, and then click
Change.

To change the service quota for a group of machines

1. In the Cyber Protect console, go to Devices.

2. Select more than one machine, and then click Assign quota.
3. In the Change quota window, select the desired service quota or No quota, and then click
Change.

Cyber Protection services installed in your environment

Cyber Protection installs some or all of the following services, depending on the Cyber Protection
options that you use.

Services installed in Windows

Service name Purpose

Acronis Managed Machine Provides backup, recovery, replication, retention, validation

Service functionality

Acronis Scheduler2 Service Executes scheduled tasks on certain events

179 © Acronis International GmbH, 2003-2024

 Acronis Active Protection Service Provides protection against ransomware

Acronis Cyber Protection Service Provides antimalware protection

Services installed in macOS

Service name and location Purpose

/Library/LaunchDaemons/com.acronis.aakore.plist Serves for communication between the agent

and management components

/Library/LaunchDaemons/com.acronis.cyber-protect- Provides detection of malware

service.plist

/Library/LaunchDaemons/com.acronis.mms.plist Provides backup and recovery functionality

/Library/LaunchDaemons/com.acronis.schedule.plist Executes scheduled tasks

Saving an agent log file

You can save an agent log to a .zip file. If a backup fails for an unknown reason, this file will help the
technical support personnel to identify the problem.

By default, the information in the log is optimized for the last three days, but you can change this
period.

To collect agent logs

1. Do one of the following:

l Under Devices, select the machine from which you want to collect the logs, and then click
Activities.
l Under Settings > Agents, select the machine from which you want to collect the logs, and
then click Details.
2. [Optional] To change the default period for which system information is included, click the arrow
next to the Collect system information button, and then select the period.
3. Click Collect system information.
4. If prompted by your web browser, specify where to save the file.

Site-to-site Open VPN - Additional information

When you create a recovery server, you configure its IP address in production network, and its
Test IP address.

After you perform failover (run the virtual machine in the cloud), and log in to the virtual machine to
check the IP address of the server, you see the IP address in production network.

When you perform test failover, you can reach the test server only by using the Test IP address,
which is visible only in the configuration of the recovery server.

180 © Acronis International GmbH, 2003-2024

To reach a test server from your local site, you must use the Test IP address.

Note
The network configuration of the server always shows the IP address in production network (as
the test server mirrors how the production server would look). This happens because the test IP
address does not belong to the test server, but to the VPN gateway, and is translated to the
production IP address using NAT.

The diagram below shows an example of the Site-to-site Open VPN configuration. Some of the
servers in the local environment are recovered to the cloud using failover (while the network
infrastructure is ok).

1. The customer enabled Disaster Recovery by:

a. configuring the VPN appliance (14), and connected it to the dedicated cloud VPN server (15)
b. protecting some of the local servers with Disaster Recovery (1, 2, 3, x8, and x10)
Some servers on the local site (like 4) are connected to networks which are not connected to
the VPN appliance. Such servers are not protected with Disaster Recovery.
2. Part of the servers (connected to different networks) work in the local site: (1, 2, 3, and 4)
3. The protected servers (1, 2, and 3) are being tested with test failover (11, 12, and 13)
4. Some servers in the local site are unavailable (x8, x10). After performing failover, they become
available in the cloud (8, and 10)
5. Some primary servers (7, and 9), connected to different networks, are available in the cloud
environment
6. (5) is a server in the Internet with a public IP address
7. (6) is a workstation connected to the cloud using a Point-to-site VPN connection (p2s)

181 © Acronis International GmbH, 2003-2024

In this example, the following connection setup is available (for example, "ping") from a server in the
From: row to a server in the To: column.

To: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Fr loc loc loc loc inter p pri fail pri fail test test test VPN VPN
o al al al al net 2 mar ove mar ove fail fail fail appl serv
m: s y r y r ove ove ove ianc er
r r r e

1 local dir via via via n via via via via via via via dire no
ect loc loc local o tun tun tun tun tun tun loca ct
al al route nel: nel: nel: nel: nel: nel: l
ro ro r1 loca loca loca loca NAT NAT rout
ut ut and l l l l (VP (VP er 1
er er Inter N N and
via via via via
1 2 net serv serv tun
loca loca loca loca
er) er) nel:
l l l l
NAT
rout rout rout rout via via
(VP
er 1 er 1 er 1 er 1 loca loca
N
and and and and l l
serv
Inte Inte Inte Inte rout rout
er)
rne rne rne rne er 1 er 1
t: t: t: t: and and via
pub pub pub pub Inte Inte loca
rne rne l
t: t: rout
pub pub er 1
and
Inte
rne
t:
pub

2 local dir via via via n via via via via via via via dire no
ect loc loc local o tun tun tun tun tun tun loca ct
al al route nel: nel: nel: nel: nel: nel: l
ro ro r1 loca loca loca loca NAT NAT rout
ut ut and l l l l (VP (VP er 1
er er Inter N N and
via via via via
1 2 net serv serv tun
loca loca loca loca
er) er) nel:
l l l l
NAT
rout rout rout rout via via
(VP
er 1 er 1 er 1 er 1 loca loca
N
and and and and l l
serv
Inte Inte Inte Inte rout rout
er)
rne rne rne rne er 1 er 1

182 © Acronis International GmbH, 2003-2024

 To: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

t: t: t: t: and and via

pub pub pub pub Inte Inte loca
rne rne l
t: t: rout
pub pub er 1
and
Inte
rne
t:
pub

3 local via via via via n via via via via via via via via no
loc loc loc local o tun tun tun tun tun tun loca local
al al al route nel: nel: nel: nel: nel: nel: l rout
ro ro ro r1 loca loca loca loca NAT NAT rout er
ut ut ut and l l l l (VP (VP er 1
er er er Inter N N and
via via via via
1 1 2 net serv serv tun
loca loca loca loca
er) er) nel:
l l l l
NAT
rout rout rout rout via via
(VP
er 1 er 1 er 1 er 1 loca loca
N
and and and and l l
serv
Inte Inte Inte Inte rout rout
er)
rne rne rne rne er 1 er 1
t: t: t: t: and and via
pub pub pub pub Inte Inte loca
rne rne l
t: t: rout
pub pub er 1
and
Inte
rne
t:
pub

4 local via via via via n via via via via via via via via no
loc loc loc local o loca loca loca loca tun tun tun local
al al al route l l l l nel: nel: nel: rout
ro ro ro r 2, rout rout rout rout NAT NAT NAT er 2
ut ut ut and er 2 er 2 er 2 er 2 (VP (VP (VP
er er er route and and and and N N N
2 2 2 r 1, tun tun tun tun serv serv serv
an an and nel: nel: nel: nel: er) er) er)
d d Inter loca loca loca loca
via via via
ro ro net l l l l

183 © Acronis International GmbH, 2003-2024

 To: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

ut ut via via via via loca loca loca

er er loca loca loca loca l l l
1 1 l l l l rout rout rout
rout rout rout rout er 2, er 2, er 2,
er 2, er 2, er 2, er 2, and and and
and and and and rout rout rout
loca loca loca loca er 1, er 1, er 1,
l l l l and and and
rout rout rout rout Inte Inte Inte
er 1, er 1, er 1, er 1, rne rne rne
and and and and t: t: t:
Inte Inte Inte Inte pub pub pub
rne rne rne rne
t: t: t: t:
pub pub pub pub

5 inter no no no no n via via via via via via via no no

net / Inte Inte Inte Inte Inte Inte Inte
a rne rne rne rne rne rne rne
t: t: t: t: t: t: t:
pub pub pub pub pub pub pub

6 p2s no no no no via via via via via via via via no no

Inter p2s p2s p2s p2s p2s p2s p2s
net VPN VPN VPN VPN VPN VPN VPN
(VP (VP (VP (VP - - -
N N N N NAT NAT NAT
serv serv serv serv (VP (VP (VP
er): er): er): er): N N N
loca loca loca loca serv serv serv
l l l l er) er) er)

via via via via via via via

Inte Inte Inte Inte Inte Inte Inte
rne rne rne rne rne rne rne
t: t: t: t: t: t: t:
pub pub pub pub pub pub pub

7 prim via via via via via n dire via via via via via no DHC
ary tu tu tu tu Inter o ct in tun tun VPN VPN tun P
nn nn nn nn net clou nel nel serv serv nel and
el el el el (via d: and and er: er: and DNS
an an VPN loca loca loca NAT NAT loca prot
d d serve l l l l ocol
loc loc r) rout rout rout s
al al er 1: er 1: er 1: only
ro ro loca loca NAT

184 © Acronis International GmbH, 2003-2024

 To: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

ut ut l l
er er
1 1
an
d2

8 failo via via via via via n dire via via via via via no DHC
ver tu tu tu tu Inter o ct in tun tun VPN VPN tun P
nn nn nn nn net clou nel nel serv serv nel and
el el el el (via d: and and er: er: and DNS
an an VPN loca loca loca NAT NAT loca prot
d d serve l l l l ocol
loc loc r) rout rout rout s
al al er 1: er 1: er 1: only
ro ro loca loca NAT
ut ut l l
er er
1 1
an
d2

9 prim via via via via via n via via dire via via via no DHC
ary tu tu tu tu Inter o tun tun ct in tun tun VPN P
nn nn nn nn net nel nel clou nel nel serv and
el el el el (via and and d: and and er: DNS
an an VPN loca loca loca loca loca NAT prot
d d serve l l l l l ocol
loc loc r) rout rout rout rout s
al al er 1: er 1: er 1: er 1: only
ro ro loca loca NAT NAT
ut ut l l
er er
1 1

10 failo via via via via via n via via dire via via via no DHC
ver tu tu tu tu Inter o tun tun ct in tun tun VPN P
nn nn nn nn net nel nel clou nel nel serv and
el el el el (via and and d: and and er: DNS
an an VPN loca loca loca loca loca NAT prot
d d serve l l l l l ocol
loc loc r) rout rout rout rout s
al al er 1: er 1: er 1: er 1: only
ro ro loca loca NAT NAT
ut ut l l
er er
1 1

185 © Acronis International GmbH, 2003-2024

 To: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

11 test no no no no via n no no no no dire via no DHC

failo Inter o ct in VPN P
ver net clou serv and
(via d: er: DNS
VPN loca loca prot
serve l l ocol
r) (rou s
tin only
g)

12 test no no no no via n no no no no dire via no DHC

failo Inter o ct in VPN P
ver net clou serv and
(via d: er: DNS
VPN loca loca prot
serve l l ocol
r) (rou s
tin only
g)

13 test no no no no via n no no no no via via no DHC

failo Inter o VPN VPN P
ver net serv serv and
(via er: er: DNS
VPN loca loca prot
serve l l ocol
r) (rou (rou s
tin tin only
g) g)

14 VPN dir dir via via via n no no no no no no no no

appl ect ect loc loc Inter o
ianc al al net
e ro ro (local
ut ut route
er er r 1)
1 2

15 VPN no no no no no n no no no no no no no no
serv o
er

186 © Acronis International GmbH, 2003-2024

License management for on-premises management
servers
For detailed information about how to activate an on-premises management server or how to
allocate licenses to it, refer to the Licensing section in the Cyber Protect user guide.

187 © Acronis International GmbH, 2003-2024

Defining how and what to protect

The Management tab

Note
The availability of this feature depends on the service quotas that are enabled for your account.

All plans that you created are available on the Management tab of the Cyber Protect console.

The following sections are available:

l Protection plans
l Remote management plans
l Scripting plans
l Monitoring plans
l Script repository
l Cloud applications backup
l Backup scanning
l Backup replication
l Validation
l Cleanup
l Conversion to VM
l VM replication

Plan statuses
For protection plans and VM replication plans, a status bar shows the following color-coded
statuses:

l OK (Green)
l Warning (Orange)
l Error (Dark orange)
l Critical (Red)
l The plan is running (Blue)
l The plan is disabled (Gray)

Click the status bar to see details about the plan statuses on all workloads to which the plan is
applied.

Click a specific status to see a list of all workloads with this status.

188 © Acronis International GmbH, 2003-2024

Protection plans
On the Management > Protection plans tab, you can see information about your existing
protection plans, perform actions with them, and create new plans.

For more information about the protection plans, refer to "Protection plans and modules" (p. 205).

Backup plans for cloud applications

The Management > Cloud applications backup tab shows cloud-to-cloud backup plans. These
plans back up applications running in the cloud by means of agents that run in the cloud and use
the cloud storage as a backup location.

In this section, you can perform the following operations:

l Create, view, run, stop, edit, and delete a backup plan

l View activities related to each backup plan
l View alerts related to each backup plan

For more information about cloud applications backup, refer to:

l Protecting Microsoft 365 data

l Protecting Google Workspace data

Running cloud-to-cloud backups manually

To prevent disrupting the Cyber Protection service, the number of manual cloud-to-cloud backup
runs is limited to 10 runs per Microsoft 365 or Google Workspace organization during an hour. After
this number has been reached, the number of runs allowed is reset to one per hour, and then an
additional run becomes available each hour thereafter (e.g. hour 1, 10 runs; hour 2, 1 run; hour 3, 2
runs) until a total of 10 runs per hour is reached.

Backup plans applied to groups of devices (mailboxes, drives, sites) or containing more than 10
devices cannot be run manually.

Backup scanning plans

To scan backups for malware (including ransomware), create a backup scanning plan.

Important
Backup scanning plans are not supported for all workloads and backup storages. For details, refer
to "Limitations" (p. 822).

To create a backup scanning plan

1. In the Cyber Protect console, go to Management > Backup scanning.

2. Click Create plan.
3. Specify the name of the plan and the following parameters:

189 © Acronis International GmbH, 2003-2024

 l Scan type:
o Cloud – this option cannot be changed. An automatically selected cloud agent will perform
the backup scan.
l Backups to scan:
o Locations – select locations with backup sets that you want to scan.
o Backups – select backup sets that you want to scan.
l Scan for:
o Malware – this option cannot be changed. The scan checks the selected backup sets for
malware (including ransomware).
l Encryption – to scan encrypted backup sets, specify the encryption password. If you select a
location or multiple backup sets and the specified password does not match a backup set, an
alert is created.
l Schedule – this option cannot be changed. In the cloud storage, the scan starts automatically.
4. Click Create.

As a result, a backup scanning plan is created and a cloud agent will scan for malware the locations
or the backup sets that you specified.

Off-host data processing

Note
This functionality is available in customer tenants for which the Advanced Backup – Servers or the
Advanced Backup – NAS quota is enabled as part of the Advanced Backup pack.

Replication, validation, and cleanup are usually performed by the protection agent that performs
the backup. This puts additional load on the machine on which the agent is running, even after the
backup process is complete. To offload the machine, you can create off-host data protection plans –
that is, separate plans for replication, validation, cleanup, and conversion to a virtual machine.

With the off-host data protection plans, you can do the following:

l Choose different agents for the backup and off-host data protection operations
l Schedule the off-host data processing operations during off-peak hours to minimize the network
bandwidth consumption
l Schedule the off-host data processing operations during non-business hours, if you do not want
to install a dedicated agent for off-host data processing

Note
The off-host data processing plans run according to the time settings (including the time zone) of
the machine on which the protection agent is installed. For a virtual appliance (for example, Agent
for VMware or Agent for Scale Computing HC3), you can configure the time zone in the graphical
user interface of the agent.

190 © Acronis International GmbH, 2003-2024

Backup replication

Note
This functionality is available in customer tenants for which the Advanced Backup – Servers or the
Advanced Backup – NAS quota is enabled as part of the Advanced Backup pack.

Backup replication is copying a backup to another location. As an off-host data processing

operation, it is configured in a backup replication plan.

Backup replication can also be part of a protection plan. For more information about this option,
refer to "Replication" (p. 419).

Creating a backup replication plan

To replicate backups as an off-host data processing operation, you create a backup replication plan.

To create a backup replication plan

1. In the Cyber Protect console, click Management > Backup replication.

2. Click Create plan.
3. In Agent, select the agent that will perform the replication.
You can select any agent that has access both to the source location and the replication
locations.
4. In Items to replicate, select the archives or backup locations to replicate.
To switch between archives and locations, use the Locations / Backups switch in the upper-right
corner.
If you select multiple encrypted archives, their encryption password must be the same. For
archives that use different encryption passwords, create separate plans.
5. In Destination, specify the replication location.
6. In How to replicate, select which backups (also known as recovery points) to replicate.
The following options are available:
l All backups
l Only full backups
l Only the last backup
For more information about these options, refer to "What to replicate" (p. 192).
7. In Schedule, configure the replication schedule.
When configuring the schedule of the backup replication plan, ensure that the last replicated
backup will still be available in its original location when the backup replication starts. If this
backup is not available in the original location, for example, because it was deleted by a
retention rule, the whole archive will be replicated as a full backup. This might be very time-
consuming and will use additional storage space.
8. In Retention rules, specify the retention rules for the target location.
The following options are available:

191 © Acronis International GmbH, 2003-2024

 l By number of backups
l By backup age (separate settings for monthly, weekly, daily, and hourly backups)
l By total size of backups
l Keep backups indefinitely

Note
Selecting this option will result in increased storage usage. You must delete the unnecessary
backups manually.

9. [If you selected encrypted archives in Items to replicate] Enable the Backup password switch,
and then provide the encryption password.
10. [Optional] To modify the plan options, click the gear icon, and then configure the options as
required.
11. Click Create.

What to replicate

Note
Some replication operations, such as replicating a whole location or replicating all backups in a
backup set, might be very time-consuming.

You can replicate individual backup sets or whole backup locations. When you replicate a backup
location, all backup sets in it are replicated.

Backup sets consist of backups (also known as recovery points). You must select which backups to
replicate.

The following options are available:

l All backups
All backups in the backup set are replicated every time the replication plan runs.
l Only full backups
Only the full backups in the backup set are replicated.
l Only the last backup
Only the newest backup in the backup set is replicated, regardless of its type (full, differential, or
incremental).

Select an option according to your needs and the backup scheme that you use. For example, if you
use the Always incremental (single-file) backup scheme and you want to replicate only the
newest incremental backup, in the backup replication plan, select Only last backup.

The following table summarizes which backups will be replicated with different backup schemes.

192 © Acronis International GmbH, 2003-2024

 Always Always full Weekly full, Daily Monthly full,
incremental incremental Weekly
(single-file) differential, Daily
incremental (GFS)

All backups All backups in the All backups in the All backups in the All backups in the
backup set backup set backup set backup set

Only full backups Only the first All backups One backup every One backup every
backup, which is week* month*
full

Only last backup Only the newest Only the newest Only the newest in Only the newest in
backup in the backup in the the backup set, the backup set,
backup set* backup set* regardless of its regardless of its
type* type*

* When configuring the schedule of the backup replication plan, ensure that the last replicated
backup will still be available in its original location when the backup replication starts. If this backup
is not available in the original location, for example, because it was deleted by a retention rule, the
whole archive will be replicated as a full backup. This might be very time-consuming and will use
additional storage space.

Supported locations
The following table summarizes backup locations supported by backup replication plans.

Backup location Supported as a source Supported as a target

Cloud storage + +

Local folder + +

Network folder + +

Public cloud + +

NFS folder – –

Secure Zone – –

Validation

Note
This functionality is available in customer tenants for which the Advanced Backup – Servers or the
Advanced Backup – NAS quota is enabled as part of the Advanced Backup pack.

By validating a backup, you verify that you can recover the data from it.

193 © Acronis International GmbH, 2003-2024

To validate a backup as an off-host data processing operation, you create a validation plan. For
more information about how to create one, refer to "Creating a validation plan" (p. 195).

The following validation methods are available:

l Checksum verification
l Run as virtual machine
o VM heartbeat
o Screenshot validation

You can select one or more of these methods. When more than one method is selected, the
operations for every validation method run consecutively. For more information about the methods,
refer to "VM heartbeat" (p. 198).

You can validate backup sets or backup locations. Validation of a backup location validates all
backup sets in it.

Supported locations
The following table shows the supported backup locations and validation methods.

Note
The validation option is not available for public cloud backups due to the prohibitive costs of
reading an entire archive from a public cloud.

Run as virtual machine

Checksum
Backup location
verification Screenshot
VM heartbeat
validation

Cloud storage + + +

Local folder + + +

Network folder + + +

NFS folder – – –

Secure Zone – – –

Validation status
After a successful validation, the backup is marked with a green dot and the label Validated.

If the validation fails, the backup is marked with a red dot. The validation fails even when only one of
the used validation methods fails. In some cases, this might be the result of a misconfiguration of
the validation plan – for example, using the VM heartbeat method for virtual machines on a wrong
host.

194 © Acronis International GmbH, 2003-2024

The validation status of a backup is updated with every new validation operation. The status for
each validation method is updated separately. That is why the validation of a backup in which one
method failed, will be shown as failed until the same validation method succeeds, even if the latest
validation operations do not use the failed method and complete successfully.

For more information about how to check the validation status, refer to "Checking the validation
status of a backup" (p. 200).

Creating a validation plan

To validate a backup set as an off-host data processing operation, you create a validation plan.

To create a validation plan

1. In the Cyber Protect console, click Management > Validation.

2. Click Create plan.
The template for a new validation plan opens.
3. [Optional] To modify the plan name, click the default name.
4. In Agent, select the agent that will perform the validation, and then click OK.
If you want to perform validation by running a virtual machine from a backup, select a machine
with Agent for VMware or Agent for Hyper-V. Otherwise, select any machine that has access to
the backup location.
5. In Items to validate, select the backups sets that you want to validate.
a. Select the scope for the plan – individual backup sets or entire locations, by clicking
Locations or Backups in the upper-right corner.
If the selected backups are encrypted, all of them must use the same encryption password.
For backups that use different encryption passwords, create separate plans.
b. Click Add.
c. Depending on the scope of the validation plan, select locations or a location and backup sets,
and then click Done.
d. Click Done.
6. In What to validate, select which backups (also known as recovery points) within the selected
backup sets to validate. The following options are available:
l All backups
l Only the last backup
7. In How to validate, select the validation method.
You can select one or both of the following options:
l Checksum verification
l Run as a virtual machine
For more information about the methods, refer to "VM heartbeat" (p. 198).
8. [If you selected Checksum verification] Click Done.
9. [If you selected Run as a virtual machine]. Configure the settings for this method.

195 © Acronis International GmbH, 2003-2024

 a. In Target machine, select the virtual machine type (ESXi or Hyper-V), the host, and the
machine name template, and then click OK.
The default name is [Machine Name]_validate.
b. In Datastore (for ESXi) or Path (for Hyper-V), select the datastore for the virtual machine.
c. Select one or both of the validation methods that Run as virtual machine provides:
l VM heartbeat
l Screenshot validation
d. [Optional] Click VM settings to change the memory size and network connections of the
virtual machine.
By default, the virtual machine is not connected to a network and the virtual machine
memory size equals that of the original machine.
e. Click Done.
10. [Optional] In the validation plan template, click Schedule, and then configure it.
11. [If the backup sets selected in Items to validate are encrypted] Enable the Backup password
switch, and then provide the encryption password.
12. [Optional] To modify the plan options, click the gear icon.
13. Click Create.

As a result, your validation plan is ready and will run according to the schedule that you configured.
To run the plan immediately, select it in Management > Validation, and then click Run now.

After the plan starts, you can check the running activities and drill down to their details in Cyber
Protect console, under Monitoring > Activities.

A validation plan might include multiple backups and one backup can be validated by multiple
validation plans.

Note
All backups are processed sequentially, one by one, by a single validation task.

Only one validation task can run at a time on a given agent. Multiple validation tasks can run in
parallel if they are executed by different agents: two simultaneous tasks require two agents, three
tasks - three agents, and so on.

The following table summarizes the possible statuses of the validation activity.

Activity result Plan with one backup Plan with multiple backups

Success All validation methods All validation methods succeeded in all backups
succeeded

Success with N/A At least one validation method failed in at least

warnings one backup

Fail At least one validation method At least one validation method failed in all backups
failed

196 © Acronis International GmbH, 2003-2024

Validation methods
In a validation plan, the following validation methods are available:

l Checksum verification
l Run as virtual machine
o VM heartbeat
o Screenshot validation

Checksum verification
Validation via checksum verification calculates a checksum for every data block that can be
recovered from the backup, and then compares it against the original checksum for that data block,
which was written during the backup process. The only exception is validation of file-level backups
that are located in the cloud storage. These backups are validated by checking the consistency of
the metadata saved in the backup.

Validation via checksum verification is a time-consuming process, even for an incremental or a

differential backup, which are small in size. The reason is that the validation operation checks not
only the data that is physically contained in a particular backup, but all of the data that needs to be
recovered – that is, previous backups might also need to be validated.

A successful validation via checksum verification means a high probability of data recovery.
However, the validation via this method does not check all factors that influence the recovery
process.

If you back up an operating system, we recommend that you use some of the following additional
operations:

l Test recovery under the bootable media to a spare hard drive.

l Running a virtual machine from the backup in an ESXi or Hyper-V environment.
l Running a validation plan in which the Run as virtual machine validation method is enabled.

Run as virtual machine

This method works only for disk-level backups that contain an operating system. To use it, you need
an ESXi or Hyper-V host and a protection agent (Agent for VMware or Agent for Hyper-V) that
manages this host.

The Run as virtual machine validation method is available in the following variants:

l VM heartbeat
l Screenshot validation

You must select at least one of them.

197 © Acronis International GmbH, 2003-2024

VM heartbeat
With this validation method, the agent runs a virtual machine from the backup, connects to VMware
Tools or Hyper-V Integration Services, and then checks the heartbeat response to ensure that the
operating system has started successfully. If the connection fails, the agent attempts to connect
every two minutes, a total of five times. If none of the attempts are successful, the validation fails.

Regardless of the number of validation plans and validated backups, the agent that performs
validation runs one virtual machine at a time. As soon as the validation result becomes clear, the
agent deletes the virtual machine and runs the next one.

Note
Use this method only when you validate backups of VMware virtual machines by running these
backups as virtual machines on an ESXi host, and backups of Hyper-V virtual machines by running
them as virtual machines on a Hyper-V host.

Screenshot validation
With this validation method, the agent runs a virtual machine from the backup, and while the virtual
machine is booting, screenshots are made. A machine intelligence (MI) module checks the
screenshots and if there is a login screen on them, it marks the backup as validated.

The screenshot is attached to the recovery point and you can download it in the Cyber Protect
console within one year of the validation. For more information on how to check the screenshot,
refer to "Checking the validation status of a backup" (p. 200).

If notifications are enabled for your user account, you will receive an email about the validation
status of the backup, in which the screenshot is attached. For more information about the
notifications, refer to Changing the notification settings for a user.

Screenshot validation is supported by agent version 15.0.30971 (released in November, 2022) and
later.

Note
Screenshot validation works best with backups of Windows and Linux systems with GUI-based login
screen. This method is not optimized for Linux systems with console login screen.

Changing the timeout for VM heartbeat and screenshot validation

When you validate a backup by running it as a virtual machine, you can configure the timeout
between booting the virtual machine, and sending the heartbeat request or taking a screenshot.

The default period is as follows:

l One minute – for backups stored on a local folder or a network share

l Five minutes – for backups stored in the cloud

You can change this by editing the configuration file for Agent for VMware or Agent for Hyper-V.

198 © Acronis International GmbH, 2003-2024

To change the timeout

1. Open the configuration file for editing. You can find the file in the following locations:
l For Agent for VMware or Agent for Hyper-V running in Windows: C:\Program
Files\BackupClient\BackupAndRecovery\settings.config
l For Agent for VMware (Virtual appliance): /bin/mms_settings.config
For more information on how to access the configuration file on a virtual appliance, see "SSH
connections to a virtual appliance" (p. 167).
2. Go to <validation>, and then change the values for local backups and cloud backups as needed:

<validation>
<run_vm>
<initial_timeout_minutes>
<local_backups>1</local_backups>
<cloud_backups>5</cloud_backups>
</initial_timeout_minutes>
</run_vm>
</validation>

3. Save the configuration file.

4. Restart the agent.
l [For Agent for VMware or Agent for Hyper-V running in Windows] Run the following
commands at the command prompt:

net stop mms

net start mms

l [For Agent for VMware (Virtual appliance)] Restart the virtual machine with the agent.

Configuring the number of retries in case of an error

To maximize the number of successful validations, you can configure automatic retries for
validation operations that end with an error.

To configure automatic retries

1. When creating a validation plan, click the gear icon.

2. In the Options pane, select Error handling.
3. Under Re-attempt, if an error occurs, click Yes.
4. In Number of attempts, configure the maximum number of retries if an error occurs.
The validation operation will run again until it finishes successfully or until the maximum number
of retries is reached.
5. In Interval between attempts, configure the timeout between two consecutive retries.
6. Click Done.

199 © Acronis International GmbH, 2003-2024

Checking the validation status of a backup
You can check the validation status of a backup in the Devices tab or in the Backup storage tab.

You can also see the status for each validation method and download the screenshot taken by the
screenshot validation method.

For more information about how the statuses work, refer to "Validation status" (p. 194).

To check the validation status of a backup

Devices

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the workload whose backup validation status you want to check, and then click Recovery.
3. [If more than one backup location is available] Select the backup location.
4. Select the backup whose status you want to check.

Backup storage

1. In the Cyber Protect console, go to Backup storage.

2. Select the location where your backup set is stored.
3. Select the backup set, and then click Show backups.
4. Select the backup whose validation status you want to check.

Cleanup
Cleanup is an operation that deletes outdated backups according to the retention rules. This
operation is only applicable to agents and workloads, and not cloud to cloud backups (which can
only be manually deleted).

Note
This functionality is available in customer tenants for which the Advanced Backup – Servers or the
Advanced Backup – NAS quota is enabled as part of the Advanced Backup pack.

Supported locations
Cleanup plans support all backup locations, except for NFS folders and Secure Zone.

To create a cleanup plan

1. In the Cyber Protect console, click Management > Cleanup.

2. Click Create plan.
3. In Agent, select the agent that will perform the cleanup.
You can select any agent that has access to the backup location.
4. In Items to clean up, select the archives or backup locations to clean up.
To switch between archives and locations, use the Locations / Backups switch in the upper-right
corner.

200 © Acronis International GmbH, 2003-2024

 If you select multiple encrypted archives, their encryption password must be the same. For
archives that use different encryption passwords, create separate plans.
5. In Schedule, configure the cleanup schedule.
6. In Retention rules, specify the retention rules.
The following options are available:
l By number of backups
l By backup age (separate settings for monthly, weekly, daily, and hourly backups)
l By total size of backups
7. [If you selected encrypted archives in Items to replicate] Enable the Backup password switch,
and then provide the encryption password.
8. [Optional] To modify the plan options, click the gear icon, and then configure the options as
required.
9. Click Create.

Conversion to a virtual machine

Conversion to a virtual machine is available only for disk-level backups. If a backup includes the
system volume and contains all of the information necessary for the operating system to start, the
resulting virtual machine can start on its own. Otherwise, you can add its virtual disks to another
virtual machine.

Note
VMs replicated via native Scale Computing VM replication functionality cannot be backed up.

You can create a separate plan for conversion to a virtual machine and run this plan manually or on
a schedule.

For information about prerequisites and limitations, refer to "What you need to know about
conversion" (p. 202).

Note
This functionality is available in customer tenants for which the Advanced Backup – Servers or the
Advanced Backup – NAS quota is enabled as part of the Advanced Backup pack.

To create a plan for conversion to a virtual machine

1. Click Management > Conversion to VM.

2. Click Create plan.
The software displays a new plan template.
3. [Optional] To modify the plan name, click the default name.
4. In Convert to, select the type of the target virtual machine. You can select one of the
following:
l VMware ESXi
l Microsoft Hyper-V

201 © Acronis International GmbH, 2003-2024

 l Scale Computing HC3
l VMware Workstation
l VHDX files

Note
To save storage space, each conversion to VHDX files or VMware Workstation overwrites the
VHDX/VMDK files in the target location that were created during the previous conversion.

5. Do one of the following:

l [For VMware ESXi, Hyper-V, and Scale Computing HC3] Click Host, select the target host, and
then specify the new machine name template.
l [For other virtual machine types] In Path, specify where to save the virtual machine files and
the file name template.
The default name is [Machine Name]_converted.
6. Click Agent, and then select the agent that will perform the conversion.
7. Click Items to convert, and then select the backups that this plan will convert to virtual
machines.
You can switch between selecting backups and selecting entire locations by using the Locations
/ Backups switch in the upper-right corner.
If the selected backups are encrypted, all of them must use the same encryption password. For
backups that use different encryption passwords, create separate plans.
8. [Only for VMware ESXi and Hyper-V] Click Datastore for ESXi or Path for Hyper-V, and then
select the datastore (storage) for the virtual machine.
9. [Only for VMware ESXi and Hyper-V] Select the disk provisioning mode. The default setting is
Thin for VMware ESXi and Dynamically expanding for Hyper-V.
10. [Optional] [For VMware ESXi, Hyper-V, and Scale Computing HC3] Click VM settings to modify
the memory size, the number of processors, or the network connections of the virtual machine.
11. [Optional] Click Schedule, and then change the schedule.
12. If the backups selected in Items to convert are encrypted, enable the Backup password switch,
and then provide the encryption password. Otherwise, skip this step.
13. [Optional] To modify the plan options, click the gear icon.
14. Click Create.

What you need to know about conversion

Supported virtual machine types

Conversion of a backup to a virtual machine can be done by the same agent that created the backup
or by another agent.

To perform a conversion to VMware ESXi, Hyper-V, or Scale Computing HC3, you need an ESXi,
Hyper-V, or Scale Computing HC3 host respectively and a protection agent (Agent for VMware, Agent
for Hyper-V, or Agent for Scale Computing HC3) that manages this host.

202 © Acronis International GmbH, 2003-2024

Conversion to VHDX files assumes that the files will be connected as virtual disks to a Hyper-V virtual
machine.

The following table summarizes the types of virtual machines that you can create with the Convert
to VM operation. The rows in the table show the type of converted virtual machines. The columns
show the agents that perform the conversion.

Age
Agent
Age Age nt Agent for
Agent Agent Age for Agent
nt nt for Virtuozzo
VM for for nt Scale for
for for oVir Hybrid
type VMw Wind for Compu Virtuo
Hyp Lin t Infrastru
are ows Mac ting zzo
er-V ux (KV cture
HC3
M)

VMware
+ – – – – – – – –
ESXi

Microso
ft – + – – – – – – –
Hyper-V

VMware
Workst + + + + – – – – –
ation

VHDX
+ + + + – – – – –
files

Scale
Comput – – – – – + – – –
ing HC3

Limitations
l Backups stored on NFS cannot be converted.
l Backups stored in Secure Zone can be converted only by the agent running on the same machine.
l Backups that contain Linux logical volumes (LVM) can be converted only if they were created by
Agent for VMware, Agent for Hyper-V, and Agent for Scale Computing HC3 and are directed to the
same hypervisor. Cross-hypervisor conversion is not supported.
l When backups of a Windows machine are converted to VMware Workstation or VHDX files, the
resulting virtual machine inherits the CPU type from the machine that performs the conversion.
As a result, the corresponding CPU drivers are installed in the guest operating system. If started
on a host with a different CPU type, the guest system displays a driver error. Update this driver
manually.

203 © Acronis International GmbH, 2003-2024

Regular conversion to virtual machine vs. running a virtual machine from a backup
Both operations provide you with a virtual machine that can be started in seconds if the original
machine fails.

Regular conversion to virtual machine takes CPU and memory resources. Files of the virtual
machine constantly occupy space on the datastore (storage). This may be not practical if a
production host is used for conversion. However, the virtual machine performance is limited only by
the host resources.

Running a virtual machine from a backup consumes resources only while the virtual machine is
running. The datastore (storage) space is required only to keep changes to the virtual disks.
However, the virtual machine may run slower, because the host does not access the virtual disks
directly, but communicates with the agent that reads data from the backup. In addition, the virtual
machine is temporary.

How the regular conversion to a virtual machine works

The way the regular conversion works depends on where you choose to create the virtual machine.

l If you choose to save the virtual machine as a set of files: each conversion re-creates the
virtual machine from scratch.
l If you choose to create the virtual machine on a virtualization server: when converting an
incremental or differential backup, the software incrementally updates the existing virtual
machine instead of re-creating it. Such conversion is normally faster. It saves network traffic and
CPU resource of the host that performs the conversion. If updating the virtual machine is not
possible, the software re-creates it from scratch.

The following is a detailed description of both cases.

If you choose to save the virtual machine as a set of files

As a result of the first conversion, a new virtual machine will be created. Every subsequent
conversion will re-create this machine from scratch. First, the old machine is temporarily renamed.
Then, a new virtual machine is created that has the previous name of the old machine. If this
operation succeeds, the old machine is deleted. If this operation fails, the new machine is deleted
and the old machine is given its previous name. This way, the conversion always ends up with a
single machine. However, extra storage space is required during conversion to store the old
machine.

If you choose to create the virtual machine on a virtualization server

The first conversion creates a new virtual machine. Any subsequent conversion works as follows:

l If there has been a full backup since the last conversion, the virtual machine is re-created from
scratch, as described earlier in this section.

204 © Acronis International GmbH, 2003-2024

l Otherwise, the existing virtual machine is updated to reflect changes since the last conversion. If
updating is not possible (for example, if you deleted the intermediate snapshots, see below), the
virtual machine is re-created from scratch.

Intermediate snapshots
To be able to update the converted virtual machine securely, the software stores an intermediate
hypervisor snapshot of this machine. The snapshot is named Replica... and must be kept.

The Replica... snapshot corresponds to the result of the latest conversion. You can go to this
snapshot if you want to return the machine to that state; for example, if you worked with the
machine and now you want to discard the changes made to it.

For converted Scale Computing HC3 virtual machines, an additional Utility Snapshot is created.
Only Cyber Protection service uses it.

Protection plans and modules

To protect your data, you must create protection plans, and then apply them to your workloads.

A protection plan consists of different protection modules. Enable the modules that you need and
configure their settings to create protection plans that meet your specific needs.

The following modules are available:

l Backup. Backs up your data sources to a local or cloud storage.

l "Implementing disaster recovery" (p. 698). Launches exact copies of your machines in the cloud
site and switches the workload from corrupted original machines to the recovery servers in the
cloud.
l Antivirus and Antimalware protection. Checks your workloads by using a built-in antimalware
solution.
l Endpoint Detection and Response (EDR). Detects suspicious activity on the workload, including
attacks that have gone unnoticed, and generates incidents to help you understand how an attack
happened and how to prevent it from happening again.
l URL filtering. Protects your machines from threats originating from the Internet, by blocking
access to malicious URLs and downloadable content.
l Windows Defender Antivirus. Manages the settings of Windows Defender Antivirus to protect
your environment.
l Microsoft Security Essentials. Manages the settings of Microsoft Security Essentials to protect
your environment.
l Vulnerability assessment. Checks Windows, Linux, macOS, Microsoft third-party products, and
macOS third-party products installed on your machines and notifies you about vulnerabilities.
l Patch management. Installs patches and updates for Windows, Linux, macOS, Microsoft third-
party products, and macOS third-party products on your machines, to resolve the detected
vulnerabilities.
l Data protection map. Discovers data in order to monitor the protection status of important files.

205 © Acronis International GmbH, 2003-2024

l Device control. Specifies devices that users are allowed or prohibited to use on your machines.
l Advanced Data Loss Prevention. Prevents leakage of sensitive data via peripheral devices (such as
printers or removable storage), or through internal and external network transfers, based on a
data flow policy.

Creating a protection plan

You can create a protection plan in the following ways:

l On the Devices tab. Select one or more workloads to protect, and then create a protection plan
for them.
l On the Management > Protection plans tab. Create a protection plan, and then select one or
more workloads to which to apply the plan.

When you create a protection plan, only the modules that are applicable to your type of workload
are shown.

You can apply a protection plan to more than one workload. You can also apply multiple protection
plans to the same workload. To learn more about possible conflicts, see "Resolving plan conflicts" (p.
211).

To create a protection plan

Devices

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the workloads that you want to protect, and then click Protect.
3. [If there are already applied plans] Click Add plan.
4. Click Create plan > Protection.
The protection plan panel opens.
5. [Optional] To rename the protection plan, click the pencil icon, and then enter the new name.
6. [Optional] To enable or disable a module in the plan, toggle the switch next to the module name.
7. [Optional] To configure a module, click it to expand it, and then change the settings according to
your needs.
8. When ready, click Create.

Note
To create a protection plan with encryption, specify an encryption password. For more
information, see "Encryption" (p. 420).

Management > Protection plans

1. In the Cyber Protect console, go to Management > Protection plans.

2. Click Create plan.
The template for a protection plan opens.
3. [Optional] To rename the protection plan, click the pencil icon, and then enter the new name.
4. [Optional] To enable or disable a module in the plan, toggle the switch next to the module name.

206 © Acronis International GmbH, 2003-2024

5. [Optional] To configure a module, click it to expand it, and then change the settings according to
your needs.
6. [Optional] To select the workloads to which you want to apply the plan, click Add devices.

Note
You can create a plan without applying it to any workloads. You can add workloads later, by
editing the plan. For more information about how to add a workload to a plan, see "Applying a
protection plan to a workload" (p. 208).

7. When ready, click Create.

Note
To create a protection plan with encryption, specify an encryption password. For more
information, see "Encryption" (p. 420).

To run a module on demand (such as Backup, Antivirus and Antimalware protection,

Vulnerability assessment, Patch management, or Data protection map), click Run now.

Watch the how-to video Creating the first protection plan.

For more information on the Disaster recovery module, see "Create a disaster recovery protection
plan" (p. 704).

For more information on the Device control module, see "Working with the Device control module"
(p. 347).

Actions with protection plans

After creating a protection plan, you can perform the following actions with it:

l Apply a plan to a workload or a device group.

l Rename a plan.
l Edit a plan.
You can enable and disable the modules in a plan, and change their settings.
l Enable or disable a plan.
A disabled plan will not run on the workloads to which it is applied.
This action is convenient for administrators who intend to protect the same workload with the
same plan later. The plan is not revoked from the workload and you can quickly restore the
protection by re-enabling the plan.
l Revoke a plan from a workload.
A revoked plan is not applied to the workload anymore.
This action is convenient for administrators who do not need rapid protection for the same
workload with the same plan again. To restore the protection provided by a revoked plan, you
must know the name of this plan, select it from the list of available plans, and then re-apply it to
the respective workload.

207 © Acronis International GmbH, 2003-2024

l Stop a plan.
This action stops all running backup operations on all workloads to which the plan is applied.
Backups will start again according to the plan schedule.
Antimalware scanning is not affected by this action and will proceed as configured in the
schedule.
l Clone a plan.
You can create an exact copy of an existing plan. The new plan is not assigned to any workloads.
l Export and import a plan.
You can export a plan as a JSON file, which you can import back later. Thus, you do not need to
create a new plan manually and configure its settings.

Note
You can import protection plans created in Cyber Protection 9.0 (released in March 2020) and
later. Plans created in earlier versions are not compatible with Cyber Protection 9.0 and later.

l Check the details of a plan.

l Check the activities and alerts related to a plan.
l Delete a plan.

Applying a protection plan to a workload

To protect a workload, you must apply a protection plan to it.

You can apply a plan from the Devices tab and from the Management > Protection plans tab.

Devices

1. Select one or more workloads that you want to protect.

2. Click Protect.
3. [If another protection plan was already applied to the selected workloads] Click Add plan.
4. A list of available protection plans is shown.
5. Select the protection plan that you want to apply, and then click Apply.

Management > Protection plans

1. In the Cyber Protect console, go to Management > Protection plans.

2. Select the protection plan that you want to apply.
3. Click Edit.
4. Click Manage devices.
5. In the Devices window, click Add.
6. Select the workloads to which you want to apply the plan, and then click Add.
7. In the Devices window, click Done.
8. In the protection plan panel, click Save.

To learn how to apply a protection plan to a device group, see "Applying a plan to a group" (p. 345).

208 © Acronis International GmbH, 2003-2024

Editing a protection plan
When you edit a plan, you can enable and disable the modules in it, and change their settings.

You can edit a protection plan for all workloads to which it is applied or only for selected workloads.

You can edit a plan from the Devices tab and from the Management > Protection plans tab.

Devices

1. Select one or more workloads to which the plan is applied.

2. Click Protect.
3. Select the protection plan that you want to edit.
4. Click the ellipsis icon (...) next to the plan name, and then click Edit.
5. Click a module that you want to edit, and then configure its settings as needed.
6. Click Save.
7. [If you have not selected all workloads to which the plan is applied] Select the scope of the edit:
l To edit the plan for all workloads to which it is applied, click Apply the changes to this
protection plan (this will affect other devices).
l To change the plan only for selected workloads, click Create a new protection plan only for
the selected devices.
As a result, the existing plan will be revoked from the selected workloads. A new protection
plan with the settings that you configured will be created and applied to these workloads.

Management > Protection plans

1. In the Cyber Protect console, go to Management > Protection plans.

2. Select the protection plan that you want to edit.
3. Click Edit.
4. Click the modules that you want to edit, and then configure their settings as needed.
5. Click Save.

Note
Editing a plan from the Management > Protection plans tab affects all workloads to which that
plan is applied.

Revoking a protection plan

When you revoke a plan, you remove it from one or more workloads. The plan still protects the
other workloads to which it is applied.

You can revoke a plan from the Devices tab and the Management > Protection plans tab.

Devices

1. Select the workloads from which you want to revoke the plan.
2. Click Protect.

209 © Acronis International GmbH, 2003-2024

3. Select the protection plan that you want to revoke.
4. Click the ellipsis icon (...) next to the plan name, and then click Revoke.

Management > Protection plans

1. In the Cyber Protect console, go to Management > Protection plans.

2. Select the protection plan that you want to revoke.
3. Click Edit.
4. Click Manage devices.
5. In the Devices window, select the workloads from which you want to revoke the plan.
6. Click Remove.
7. In the Devices window, click Done.
8. In the protection plan template, click Save.

Enabling or disabling a protection plan

An enabled plan is active and runs on the workloads to which it is applied. A disabled plan is inactive
– it is still applied to workloads but it does not run on them.

When you enable or disable a protection plan from the Devices tab, your action affects only the
selected workloads.

When you enable or disable a protection plan from the Management > Protection plans tab, your
action affects all workloads to which this plan is applied. Also, you can enable or disable multiple
protection plans.

Devices

1. Select the workload whose plan you want to disable.

2. Click Protect.
3. Select the protection plan that you want to disable.
4. Click the ellipsis icon (...) next to the plan name, and then click Enable or Disable, respectively.

Management > Protection plans

1. In the Cyber Protect console, go to Management > Protection plans.

2. Select one or more protection plans that you want to enable or disable.
3. Click Edit.
4. Click Enable or Disable, respectively.

Note
This action does not affect protection plans that were already in the target state. For example, if
your selection includes both enabled and disabled plans, and you click Enable, all selected plans will
be enabled.

210 © Acronis International GmbH, 2003-2024

Deleting a protection plan
When you delete a plan, it is revoked from all workloads and removed from the Cyber Protect
console.

You can delete a plan from the Devices tab and the Management > Protection plans tab.

Devices

1. Select any workload to which the protection plan that you want to delete is applied.
2. Click Protect.
3. Select the protection plan that you want to delete.
4. Click the ellipsis icon (...) next to the plan name, and then click Delete.

Management > Protection plans

1. In the Cyber Protect console, go to Management > Protection plans.

2. Select the protection plan that you want to delete.
3. Click Delete.
4. Confirm your choice by selecting the I confirm the deletion of plan check box, and then click
Delete.

Resolving plan conflicts

You can apply multiple protection plans to the same workload. For example, you may apply one
protection plan in which you enabled and configured only the Antivirus and Antimalware module,
and another protection plan in which you enabled and configured only the Backup module.

You can combine protection plans in which different modules are enabled. You can also combine
multiple protection plans in which only the Backup module is enabled. However, if any other
module is enabled in more than one plan, a conflict occurs. To apply the plan, first you must resolve
the conflict.

Conflict between a new and existing plan

If a new plan conflicts with an existing plan, you can resolve the conflict in one of the following ways:

l Create a new plan, apply it, and then disable the existing plan that conflicts with the new one.
l Create a new plan, and then disable it.

Conflict between an individual and group plan

If an individual protection plan conflicts with a group plan that is applied to a device group, you can
resolve the conflict in one of the following ways:

l Remove the workload from the device group, and then apply the individual protection plan to it.
l Edit the existing group plan or apply a new group plan to the device group.

211 © Acronis International GmbH, 2003-2024

License issue
A protection plan module might require that a specific service quota is assigned to the protected
workload. If the assigned service quota is not appropriate, you will not be able to run, update, or
apply the protection plan in which the respective module is enabled.

To resolve a license issue, do one of the following:

l Disable the module that is not supported by the currently assigned service quota, and then
continue using the protection plan.
l Change the assigned service quota manually. To learn how to do this, see "Changing the service
quota of machines" (p. 178).

Default protection plans

A default protection plan is a precofigured template that you can apply to your workloads, thus
ensuring quick protection. By using a default protection plan, you do not have to create new
protection plans from scratch.

When you apply a default protection plan for the first time, the template is copied to your tenant
and you can edit the modules in the plan and their settings.

The following default plans are available:

l Cyber Protect Essentials

This plan provides basic protection functionality and file-level backup.
l Remote workers
This plan is optimized for users who work remotely. It provides more frequent tasks (such as
backup, antimalware protection, and vulnerability assessment), stricter protection actions, and
optimized performance and power options.
l Office workers (third-party Antivirus)
This plan is optimized for users who work at the office and prefer third-party antivirus software.
In this plan, the Antivirus and Antimalware protection module is disabled.
l Office workers (Acronis Antivirus)
This plan is optimized for users who work at the office and prefer the Acronis antivirus software.

Comparison of the default protection plans

Modules and Default protection plans
options
Cyber Protect Remote workers Office workers Office workers
Essentials (third-party (Acronis
Antivirus) Antivirus)

Backup Available Available Available Available

What to back up Files/folders Entire machine Entire machine Entire machine

212 © Acronis International GmbH, 2003-2024

 Modules and Default protection plans
options
Cyber Protect Remote workers Office workers Office workers
Essentials (third-party (Acronis
Antivirus) Antivirus)

Items to back up [All Profiles Folder]

Continuous data Disabled Enabled Disabled Disabled

protection (CDP)

Where to back up Cloud storage Cloud storage Cloud storage Cloud storage

Schedule Monday to Friday Monday to Friday Monday to Friday Monday to Friday

at 11:00 PM at 12:00 AM at 11:00 PM at 11:00 PM

Additionally
enabled options
and start
conditions:

l If the machine
is turned off,
run missed
tasks at the
machine
startup
l Wake up from
the sleep or
hibernate
mode to start a
scheduled
backup
l Save battery
power: Do not
start when on
battery
l Do not start
when on
metered
connection

Backup scheme Always Always Always Always incremental

incremental incremental incremental

How long to keep Keep backups Monthly: 12 Monthly: 12 Monthly: 12

infinitely months months months

Weekly: 4 weeks Weekly: 4 weeks Weekly: 4 weeks

Daily: 7 days Daily: 7 days Daily: 7 days

213 © Acronis International GmbH, 2003-2024

 Modules and Default protection plans
options
Cyber Protect Remote workers Office workers Office workers
Essentials (third-party (Acronis
Antivirus) Antivirus)

Backup options Default options Default options, Default options Default options
plus:

l Performance
and backup
window (the
green set):
CPU priority:
Low
Output speed:
50%

Antivirus and Available Available Not available Available

Antimalware
protection

Active Protection Off Off – Off

Advanced On On – On
Antimalware

Network folder On On – On
protection

Server-side Off Off – Off

protection

Self protection On On – On

Cryptomining On On – On
process detection

Quarantine Remove Remove – Remove

quarantined files quarantined files quarantined files
after 30 days after 30 days after 30 days

Behavior engine Quarantine Quarantine – Quarantine

Exploit prevention Notify and stop the Notify and stop – Notify and stop the
process the process process

Real-time Quarantine Quarantine – Quarantine

protection

Schedule scan Quick Quick scan: Off – Quick scan:

scan:Quarantine Quarantine
Full scan:

214 © Acronis International GmbH, 2003-2024

 Modules and Default protection plans
options
Cyber Protect Remote workers Office workers Office workers
Essentials (third-party (Acronis
Antivirus) Antivirus)

At 02:20 PM, Quarantine At 02:20 PM,

Sunday to Sunday to
At 01:55 PM,
Saturday Saturday
Sunday to
Full scan:Off Saturday Full scan: Off

Additionally
enabled options
and start
conditions:

l If the machine
is turned off,
run missed
tasks at the
machine
startup
l Wake up from
the sleep or
hibernate
mode to start a
scheduled
backup
l Save battery
power: Do not
start when on
battery

Exclusions None None – None

URL filtering Available Available Available Available

Malicious website Always ask user Block Always ask user Always ask user
access

Categories to filter Default options Default options Default options Default options

Exclusions None None None None

Vulnerability Available Available Available Available

assessment

Vulnerability Microsoft Microsoft Microsoft Microsoft

assessment scope products, Windows products, products, Windows products, Windows
third-party Windows third- third-party third-party

215 © Acronis International GmbH, 2003-2024

 Modules and Default protection plans
options
Cyber Protect Remote workers Office workers Office workers
Essentials (third-party (Acronis
Antivirus) Antivirus)

products party products products products

Schedule At 01:15 PM, only At 02:20 PM, only At 01:15 PM, only At 01:15 PM, only
on Monday on Monday on Monday on Monday

Patch Available Available Available Available

management

Microsoft products All updates All updates All updates All updates

Windows third- Only major Only major Only major Only major
party products updates updates updates updates

Schedule At 03:10 PM, only At 02:20 PM, At 03:10 PM, only At 03:10 PM, only
on Monday Monday to Friday on Monday on Monday

Pre-update backup Off On Off Off

Data protection Not available Available Available Available

map

Extensions and – Default options Default options (66 Default options (66
exception rules and the following extensions to extensions to
additional detect) detect)
extensions:

Images

l .jpeg
l .jpg
l .png
l .gif
l .bmp
l .ico
l .wbmp
l .xcf
l .psd
l .tiff
l .dwg

Audio and video

l .avi,
l .mov,
l .mpeg,

216 © Acronis International GmbH, 2003-2024

 Modules and Default protection plans
options
Cyber Protect Remote workers Office workers Office workers
Essentials (third-party (Acronis
Antivirus) Antivirus)

l .mpg,
l .mkv
l .wav
l .aif
l .aifc
l .aiff
l .au
l .snd
l .mid
l .midi
l .mpga
l .mp3
l .oga
l .flac
l .opus
l .spx
l .ogg
l .ogx
l .mp4

Schedule – At 03:35 PM, At 03:40 PM, At 03:40 PM,

Monday to Friday Monday to Friday Monday to Friday

Note
The number of modules in a default protection plan may vary according to your Cyber Protection
license.

Applying a default protection plan

The initial default protection plans are templates the settings of which you cannot edit. When you
apply a default plan for the first time, the template is copied to your tenant as a preconfigured
protection plan and is enabled on the selected workloads.

The protection plan appears in the Management > Protection plans tab, and then you can
manage it there.

To apply a default protection plan for the first time

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the workloads that you want to protect.

217 © Acronis International GmbH, 2003-2024

3. Click Protect.
4. Select one of the default plans, and then click Apply.

Editing a default protection plan

You can edit a default protection plan after you apply it for the first time.

To edit an applied default protection plan

1. In the Cyber Protect console, go to Management > Protection plans.

2. Select the plan that you want to edit, and then click Edit.
3. Modify the modules that are included in this plan, or their options, and then click Save.

Important
Some of the options cannot be modified.

Individual protection plans for hosting control panel integrations

When you enable hosting control panel integrations on your web hosting servers that use
DirectAdmin, cPanel, or Plesk, the Cyber Protection service automatically creates an individual
protection plan under your user account for each workload. This protection plan is associated with
the particular workload that initiated the protection plan creation, and cannot be revoked or
assigned to other workloads.

To stop using an individual protection plan, you can delete it from the Cyber Protect console. You

can identify individual protection plans by the sign next to their name.

If you want a protection plan to protect multiple web hosting servers that use hosting control panel
integrations, you can create a regular protection plan in the Cyber Protect console and assign these
workloads to it. However, any modifications to a protection plan that is shared by multiple web
hosting control panels, can only be made in the Cyber Protect console, and not from within the
integrations.

#CyberFit Score for machines

#CyberFit Score provides you with a security assessment and scoring mechanism that evaluates the
security posture of your machine. It identifies security gaps in the IT environment and open attack
vectors to endpoints and provides recommended actions for improvements in the form of a report.
This feature is available in all Cyber Protect editions.

The #CyberFit Score functionality is supported on:

l Windows 7 (first version) and later versions

l Windows Server 2008 R2 and later versions

218 © Acronis International GmbH, 2003-2024

How it works
The protection agent that is installed on a machine performs a security assessment and calculates
the #CyberFit Score for the machine. The #CyberFit Score of a machine is automatically periodically
recalculated.

#CyberFit scoring mechanism

The #CyberFit Score for a machine is calculated, based on the following metrics:

l Antimalware protection 0-275

l Backup protection 0-175
l Firewall 0-175
l Virtual private network (VPN) 0-75
l Full disk encryption 0-125
l Network security 0-25

The maximum #CyberFit Score for a machine is 850.

Metric What is Recommendations to users Scoring

assessed?

Antimalware The agent checks Findings: 275 -

whether antimalware
l You have antimalware protection enabled (+275
antimalware software is
points)
software is installed on a
l You don’t have antimalware protection, your
installed on a machine
system may be at risk (0 points)
machine.
0 - no
Recommendations provided by #CyberFit Score:
antimalware
You should have an antimalware solution installed software is
and enabled on your machine to stay protected installed on a
from security risks. machine

You should refer to websites such as AV-Test or AV-

Comparatives for a list of recommended
antimalware solutions.

Backup The agent checks Findings: 175 - a backup

if a backup solution is
l You have a backup solution protecting your data
solution is installed on a
(+175 points)
installed on a machine
l No backup solution was found, your data may be
machine.
at risk (0 points) 0 - no backup
solution is
Recommendations provided by #CyberFit Score:
installed on a
We recommend that you back up your data machine
regularly to prevent data loss or ransomware

219 © Acronis International GmbH, 2003-2024

 attacks. Below are some backup solutions that you
should consider using:

l Acronis Cyber Protect / Cyber Backup / True

Image
l Windows Server Backup (Windows Server 2008
R2 and later)

Firewall The agent checks Findings: 100 - Windows

whether a public firewall
l You have a firewall enabled for public and
firewall is is enabled
private networks, or a 3-rd party firewall solution
available and
is found (+175 points) 75 - Windows
enabled in your
l You have a firewall enabled only for public private firewall
environment.
networks (+100 points) is enabled
The agent does l You have a firewall enabled only for private 175 - Windows
the following: networks (+75 points) public and
1. Checks l You have no firewall enabled, your network private firewall
Windows connection is not secure (0 points) are enabled
Firewall and Recommendations provided by #CyberFit Score: OR
Network a third-party
Protection We recommend that you enable firewall for your firewall
whether a public public and private networks to improve your solution is
firewall is turned security protection against malicious attacks on enabled
on. your system. Below, detailed guides are provided
on setting-up your Windows firewall, depending on 0 - neither a
2. Checks your security needs and network architecture: Windows
Windows firewall, nor a
Firewall and Guides for end-users/employees: third-party
Network How to set up Windows Defender Firewall on your firewall
Protection PC solution are
whether a enabled
private firewall is How to set up Windows Firewall on your PC
turned on. Guides for system administrators and engineers:
3. Checks for a 3- How to deploy Window Defender Firewall with
rd party firewall Advanced Security
solution/agent if
Windows public How to create Advanced Rules in Windows Firewall

and private
firewalls are
disabled.

Virtual Private The agent checks Findings: 75 - VPN is

Network (VPN) whether a VPN enabled and
l You have a VPN solution and can safely receive
solution is running
and send data across public and shared
installed on a
networks (+75 points) 0 - VPN is not
machine and
l No VPN solution was found, your connection to enabled
whether the VPN

220 © Acronis International GmbH, 2003-2024

 is enabled and public and shared networks is not secure (0
running. points)

Recommendations provided by #CyberFit Score:

We recommend that you use VPN to access your

corporate network and confidential data. It is critical
to use a VPN to keep your communications safe and
private, especially if you use complimentary
Internet access from a cafe, library, airport, or
elsewhere. Below are some VPN solutions that you
should consider using:

l Acronis Business VPN

l OpenVPN
l Cisco AnyConnect
l NordVPN
l TunnelBear
l ExpressVPN
l PureVPN
l CyberGhost VPN
l Perimeter 81
l VyprVPN
l IPVanish VPN
l Hotspot Shield VPN
l Fortigate VPN
l ZYXEL VPN
l SonicWall GVPN
l LANCOM VPN

Disk The agent checks Findings: 125 - all disks

encryption whether a are encrypted
l You have full disk encryption enabled, your
machine has disk
machine is protected against physical tampering 75 - at least
encryption
(+125 points) one of your
enabled.
l Only some hard drives are encrypted, your disks is
The agent checks machine may be at risk from physical tampering encrypted but
whether (+75 points) there are also
Windows l No disk encryption was found, your machine is at unencrypted
BitLocker is risk from physical tampering (0 points) disks
turned on.
Recommendations provided by #CyberFit Score: 0 - no disks
are encrypted
We recommend that you turn on Windows
BitLocker to improve protection of your data and
files.

Guide: How to turn on device encryption on

Windows

221 © Acronis International GmbH, 2003-2024

 Network The agent checks Findings: 25 - outgoing
security whether a NTLM traffic is
l Outgoing NTLM traffic to remote servers is
(outgoing machine has set to DenyAll
denied, your credentials are protected (+25
NTLM traffic to restricted
points) 0 - outgoing
remote outgoing NTLM
l Outgoing NTLM traffic to remote servers is not NTLM traffic is
servers) traffic to remote
denied, your credentials may be vulnerable to set to another
servers.
exposure (0 points) value

Recommendations provided by #CyberFit Score:

For better security protection, we recommend that

you deny all outgoing NTLM traffic to remote
servers. You can find information on how to change
the NTLM settings and add exceptions by following
the link below.

Guide: Restrict outgoing NTLM traffic to remote

servers

Based on the summed points awarded to each metric, the total #CyberFit Score of a machine can fit
one of the following ratings that reflect the endpoint's level of protection:

l 0 - 579 - Poor
l 580 - 669 - Fair
l 670 - 739 - Good
l 740 - 799 - Very good
l 800 - 850 - Excellent

You can see the #CyberFit Score for your machines in the Cyber Protect console: go to Devices > All
devices. In the list of devices, you can see the #CyberFit Score column. You can also run the
#CyberFit Score scan for a machine to check its security posture.

222 © Acronis International GmbH, 2003-2024

You can also get information about the #CyberFit Score in the corresponding widget and report
pages.

Running a #CyberFit Score scan

To run a #CyberFit Score scan

1. In the Cyber Protect console, go to Devices.

2. Select the machine and click #CyberFit Score.
3. If the machine has never been scanned before, then click Run a first scan.
4. After the scan is completed, you will see the total #CyberFit Score for the machine along with the
scores of each of the six assessed metrics - Antimalware, Backup, Firewall, Virtual Private
Network (VPN), Disk encryption, and NT LAN Manager (NTLM) traffic.

223 © Acronis International GmbH, 2003-2024

5. To check how to increase the score of each metric for which the security configurations could be
improved, expand the corresponding section and read the recommendations.

6. After addressing the recommendations, you can always recalculate the #CyberFit Score of the
machine by clicking on the arrow button right under the total #CyberFit Score.

224 © Acronis International GmbH, 2003-2024

Cyber Scripting
With Cyber Scripting, you can use scripts to automate routine operations on Windows and macOS
machines in your environment, such as installing software, modifying configurations, starting or
stopping services, and creating accounts. Thus, you can decrease the time that you spend on such
operations and reduce the risk of error when performing them manually.

Cyber Scripting is available for administrators and users on the customer level, as well as to partner
administrators (service providers). For more information about the different levels of
administration, see "Multitenancy support" (p. 313).

The scripts that you can use must be approved in advance. Only the administrators with the Cyber
administrator role can approve and test new scripts. For more information about changing the
script status, see "Changing the script status" (p. 235).

Depending on your user role, you can perform different operations with scripts and scripting plans.
For more information about the roles, see "User roles and Cyber Scripting rights" (p. 226).

Prerequisites
l The Cyber Scripting functionality requires the Advanced Management pack.
l To use all the features of Cyber Scripting such as script editing, script run, creation of scripting
plans, and so on, you must enable two-factor authentication for your account.

Limitations
l The following scripting languages are supported:
o PowerShell
o Bash
l Cyber Scripting operations can only run on target machines that have an installed protection
agent.

Supported platforms
Cyber Scripting is available for Windows and macOS workloads.

The following table summarizes the supported versions.

225 © Acronis International GmbH, 2003-2024

 Operating system Version

Windows Windows 7 SP1 and later – all editions

Windows 8/8.1 – all editions (x86, x64), except for the Windows RT
editions

Windows 10 – Home, Pro, Education, Enterprise, IoT Enterprise editions

Windows 11

Windows Server 2008 R2 SP1 and later – Standard, Enterprise,

Datacenter, Foundation, and Web editions

Windows Server 2012/2012 R2 – all editions

Windows Server 2016

Windows Server 2019

Windows Server 2022

Windows Storage Server (2008 R2, 2012, 2012 R2, 2016)

macOS macOS Mojave 10.14

macOS Catalina 10.15

macOS Big Sur 11

macOS Monterey 12

User roles and Cyber Scripting rights

The available actions with scripts and scripting plans depend on the script status and your user role.

Administrators can manage objects in their own tenant and in its child tenants. They cannot see or
access objects on an upper administration level, if any.

Lower-level administrators have only read-only access to the scripting plans applied to their
workloads by an upper-level administrator.

The following roles provide rights with regard to Cyber Scripting:

l Company administrator
This role grants full administrator rights in all services. With regard to Cyber Scripting, it grants
the same rights as the Cyber administrator role.

l Cyber administrator
This role grants full permissions, including approval of scripts that can be used in the tenant, and
the ability to run scripts with the Testing status.
l Administrator

226 © Acronis International GmbH, 2003-2024

 This role grants partial permissions, with the ability to run approved scripts as well as create and
run scripting plans that use approved scripts.
l Read-only administrator
This role grants limited permissions, with the ability to view scripts and protection plans that are
used in the tenant.
l User
This role grants partial permissions, with the ability to run approved scripts as well as create and
run scripting plans that use approved scripts, but only on the user's own machine.

The following table summarizes all available actions, depending on the script status and the user
role.

Script status
Role Object
Draft Testing Approved

Create Create

Edit Edit
Edit (Remove a
draft script from Apply Apply
a plan)
Enable Enable
Delete
Scripting plan Run Run
Revoke
Delete Delete
Disable
Revoke Revoke
Cyber
Stop
administrator Disable Disable

Company Stop Stop

administrator
Create Create
Create
Edit Edit
Edit
Change status Change status
Change status
Script Run Run
Clone
Clone Clone
Delete
Delete Delete
Cancel running
Cancel running Cancel running

View Create
Administrator
Revoke View Edit
User (for their own Scripting plan
Disable Cancel run Apply
workloads)
Stop Enable

227 © Acronis International GmbH, 2003-2024

 Run

Delete

Revoke

Disable

Stop

Create

Edit View Run

Script Clone Clone Clone

Delete Cancel running Cancel running

Cancel running

Scripting plan View View View

Read-only
administrator
Script View View View

Scripts
A script is a set of instructions that are interpreted at runtime and executed on a target machine.
Scripts provide a convenient solution for automating repetitive or complex tasks.

With Cyber Scripting, you can run a predefined script or create a custom script. You can view all
scripts that are available to you in Management > Script repository. The predefined scripts are
located in the Library section. The scripts that you created or cloned to your tenant are located in
the My scripts section.

You can use a script by including it in a scripting plan or by performing a Script quick run
operation.

Note
You can only use approved scripts that are created in your tenant or were cloned to it. If a script
was removed from the script repository or is in a Draft status, it will not run. You can check the
details of a scripting operation or cancel it in Monitoring > Activities.

The following table provides more information about the possible actions with a script, depending
on its status.

Status Possible actions

Draft The new scripts that you create and the scripts that you clone to your
repository are in Draft status. You are not allowed to run these scripts or
include them in scripting plans.

Testing Administrators with the Cyber administrator role can run these scripts

228 © Acronis International GmbH, 2003-2024

 Status Possible actions

and include them in scripting plans.

Approved You can run these scripts and include them in scripting plans.

Only administrators with the Cyber administrator role can change the status of a script or delete
an approved script. For more information, see "Changing the script status" (p. 235).

Creating a script
You can create a script by manually writing the code.

To create a script

1. In the Cyber Protect console, go to Management > Script repository.

2. In My Scripts, click Create script by using AI.
3. In the main pane, write the body of the script.

Important
When you create a script, include exit code checks for each operation. Otherwise, a failed
operation might be ignored and the scripting activity status in Monitoring > Activities might be
incorrectly shown as Succeeded.

4. Specify the script settings.

Setting Description

Script name Script name. The field is populated automatically, but you can change the value.

Description Script description. This setting is optional.

[For scripts generated by AI] The field will be populated automatically upon script
generation. You can edit the description provided by AI.

Language Script language. The available values are:

l PowerShell. This is the default value.
l Bash
[For scripts generated by AI] This setting is configured before the script generation.

Operating Operating system that is installed on the target workload on which the script will run.
system The available values are:
l Windows. This is the default value.
l macOS
[For scripts generated by AI] This setting is configured before the script generation.

Status Script status.

l Draft. This is the default value. The new scripts that you create and the scripts that
you clone to your repository are in the Draft status. You are not allowed to run
Draft scripts or include them in scripting plans.

229 © Acronis International GmbH, 2003-2024

 Setting Description

l Testing. Only administrators with the Cyber administrator role can change the
status of a script to Testing, run scripts in the Testing status, and run scripting
plans with such scripts.
l Approved. You can run Approved scripts and include them in scripting plans.
Only administrators with the Cyber administrator role can change the status of a
script or delete an approved script. For more information, see "Changing the script
status" (p. 235).

Tags The tags are not case-sensitive and can be up to 32 characters long. You cannot use
round and angle brackets, commas, or spaces.
This setting is optional.
[For scripts generated by AI] The AI-generated tag will be added automatically upon
script generation. You can manually delete this tag or add more tags.

5. [Only for scripts that require credentials] Specify the credentials.

You can use a single credential (for example, a token) or a pair of credentials (for example, a user
name and a password).
6. [Only for scripts that require arguments] Specify the arguments and their values, as follows:
a. Click Add.
b. In the Add arguments field, specify the argument.
c. Click Add.
d. In the second field that appears, specify the argument value.

Note
You can only specify arguments that you have already defined in the script body.

For example:

230 © Acronis International GmbH, 2003-2024

 e. Repeat the steps above if you need to add more than one argument.
7. Click Save.

The script is saved to your repository in the Draft status.

You cannot use the script until an administrator with the Cyber administrator role changes its
status to Approved. For more information, see "Changing the script status" (p. 235).

To use a script in another tenant that you manage, you must clone the script to that tenant. For
more information, see "Cloning a script" (p. 233).

Creating a script by using AI

Note
This functionality requires the Advanced Management pack.

You can use AI to transform prompts into powerful scripts, saving you time and efforts. You can use
the functionality in the following ways:

l Enter a prompt to ask AI to generate a script from scratch.

l Enter a prompt to ask AI to review and complete a code that you have entered in the script body.
You can use this capability when you have been struggling with more complex codes.

The functionality uses the GPT-4 model of OpenAI. You can use it to create up to 100 scripts for your
organization per calendar month, free of charge.

To create a script by using AI

1. In the Cyber Protect console, go to Management > Script repository.

2. In My Scripts, click Create a script by using AI.
3. In the prompt, enter a description of what the script should do. Ensure that the description that
you enter is as clear and detailed as possible.

For example:

I need a script that deletes Temporary files for all users (including user profiles +
Windows Temps) and disable Windows Update Service to allow the script to run

4. In the prompt, click the arrow button.

231 © Acronis International GmbH, 2003-2024

5. In the confirmation window, select Language and Operating system, and then click Generate.
The script that is generated by AI is displayed in the main pane. The name and description of the
script are automatically generated by AI so that they match the script. The AI-generated tag is
automatically assigned to the script.
6. Review the script that was generated by AI and if necessary, edit it manually.
7. If necessary, edit the script settings.

Setting Description

Script name Script name. The field is populated automatically, but you can change the value.

Description Script description. This setting is optional.

[For scripts generated by AI] The field will be populated automatically upon script
generation. You can edit the description provided by AI.

Language Script language. The available values are:

l PowerShell. This is the default value.
l Bash
[For scripts generated by AI] This setting is configured before the script generation.

Operating Operating system that is installed on the target workload on which the script will run.
system The available values are:
l Windows. This is the default value.
l macOS
[For scripts generated by AI] This setting is configured before the script generation.

Status Script status.

l Draft. This is the default value. The new scripts that you create and the scripts that
you clone to your repository are in the Draft status. You are not allowed to run
Draft scripts or include them in scripting plans.
l Testing. Only administrators with the Cyber administrator role can change the
status of a script to Testing, run scripts in the Testing status, and run scripting
plans with such scripts.
l Approved. You can run Approved scripts and include them in scripting plans.
Only administrators with the Cyber administrator role can change the status of a
script or delete an approved script. For more information, see "Changing the script
status" (p. 235).

Tags The tags are not case-sensitive and can be up to 32 characters long. You cannot use
round and angle brackets, commas, or spaces.
This setting is optional.
[For scripts generated by AI] The AI-generated tag will be added automatically upon
script generation. You can manually delete this tag or add more tags.

8. [Optional] [Only for scripts that require credentials] Specify the credentials.
You can use a single credential (for example, a token) or a pair of credentials (for example, a user
name and a password).

232 © Acronis International GmbH, 2003-2024

 9. [Only for scripts that require arguments] Specify the arguments and their values, as follows:
a. Click Add.
b. In the Add arguments field, specify the argument.
c. Click Add.
d. In the second field that appears, specify the argument value.

Note
You can only specify arguments that you have already defined in the script body.

For example:

e. Repeat the steps above if you need to add more than one argument.
10. Click Save.
The script is saved to your repository in the Draft status.
You cannot use the script until an administrator with the Cyber administrator role changes its
status to Approved. For more information, see "Changing the script status" (p. 235).
To use a script in another tenant that you manage, you must clone the script to that tenant. For
more information, see "Cloning a script" (p. 233).

Cloning a script
Cloning a script is necessary in the following cases:

l Before using a script from the Library. In this case, first you must clone the script to the My
Scripts section.
l When you want to clone scripts that you created in a parent tenant to its child tenants or units.

To clone a script

233 © Acronis International GmbH, 2003-2024

1. In Script repository, find the script that you want to clone.
2. Do one of the following:
l [If you clone a script from My Scripts] Click the ellipsis (...) next to the script name, and then
click Clone.
l [If you clone a script from Library] Click Clone next to the name of the script that you have
selected.
3. In the Clone script pop-up, select one of the following script statuses from the Status drop-
down list:
l Draft (by default) — this status does not allow you to execute the script right away.
l Testing — this status allows you to execute the script.
l Approved — this status allows you to execute the script.
4. [If you manage more than one tenant or unit] Select where you want to clone the script.
In the Clone script dialog box, you see only the tenants that you can manage and which have
the Advanced Management pack applied.

As a result, the script is cloned to the My Scripts section of the tenant or unit that you selected. If
you manage only one tenant with no units in it, the script is automatically copied to your My Scripts
section.

Important
Credentials that a script uses are not copied when you clone a script to a non-original tenant.

Editing or deleting a script

Note
Depending on your user role, you can perform different operations with scripts and scripting plans.
For more information about the roles, see "User roles and Cyber Scripting rights" (p. 226).

To edit a script

1. In Script repository, go to My Scripts, and then find the script that you want to edit.
2. Click the ellipsis (...) next to the script name, and then click Edit.
3. Edit the script, and then click Save.
4. [If you edit a script that is used by a scripting plan] Confirm your choice by clicking Save script.

Note
The latest version of the script will be used next time the scripting plan runs.

Script versions
A new version of the script is created if you edit any of the following script attributes:

l script body
l script name
l description

234 © Acronis International GmbH, 2003-2024

l script language
l credentials
l arguments

If you change other attributes, your edits will be added to the current script version. To learn more
about versions and how to compare them, refer to "Comparing script versions" (p. 236).

Note
The script status is updated only when you modify the value in the Status field. Only administrators
with the Cyber administrator role can change a script status.

To delete a script

1. In Script repository, go to My Scripts, and then find the script that you want to delete.
2. Click the ellipsis (...) next to the script name, and then click Delete.
3. Click Delete.
4. [If you want to delete a script that is used by a scripting plan] Confirm your choice by clicking
Save script.

Note
Scripting plans that use the deleted script will fail to run.

Changing the script status

A new script that is created and is in the Draft state cannot be used until its status is changed to
Approved. Depending on the use case, a script might be in status Testing for some period before it
is approved.

Note
Depending on your user role, you can perform different operations with scripts and scripting plans.
For more information about the roles, see "User roles and Cyber Scripting rights" (p. 226).

Prerequistes
l Your user is an administrator who is assigned the Cyber administrator role.
l A script with the corresponding state is available.

To change the script status

1. In Script repository, go to My Scripts.

2. Click the ellipsis (...) next to the script name, and then click Edit.
3. In the Status drop-down list, select the status.
4. Click Save.
5. [If you change the status of an approved script] To confirm the change, click Save script.

235 © Acronis International GmbH, 2003-2024

 Note
If the script status was downgraded to Draft, the scripting plans that use it will fail to run.
Only administrators with the Cyber administrator role can run scripts in the Testing status and
scripting plans with such scripts.

Comparing script versions

You can compare two versions of a script and revert to an earlier version. You can also check who
created a specific version, and when.

To compare script versions

1. In Script repository, go to My Scripts, and then find the script whose versions you want to
compare.
2. Click the ellipsis (...) next to the script name, and then click Version history.
3. Select two versions that you want to compare, and then click Compare versions.
Any changes in the body text of the script, its arguments or credentials are highlighted.

To revert to an earlier version

1. In the Compare script versions window, click Revert to this version.

2. In the Revert to a previous version pop-up, in the Status drop-down list, select the script
status.

The selected version is restored and saved as the latest one in the version history.

To restore a script, you can also select a version from the Version history window, and then click on
the Restore button.

Important
You can execute scripts only with the Testing or Approved statuses. For more information, see
"Changing the script status" (p. 235).

Downloading the output of a scripting operation

You can download the output of a scripting operation as a .zip file. It contains two text files – stdout
and stderr. In stdout, you can see the results of a successfully completed scripting operation. The
stderr file contains information about the errors that occurred during the scripting operation.

To download the output file

1. In the Cyber Protect console, go to Monitoring > Activities.

2. Click the Cyber Scripting activity whose output you want to download.
3. On the Activity details screen, click Download output.

236 © Acronis International GmbH, 2003-2024

Script repository
You can locate the script repository under the Management tab. In the repository, you can search
the scripts by their name and description. You can also use filters, or sort the scripts by their name
or status.

To manage a script, click the ellipsis (...) next to its name, and then select the desired action.
Alternatively, click the script and use the buttons on the screen that opens.

The script repository contains the following sections:

l My scripts
Here, you can find the scripts that you can directly use in your environment. These are the scripts
that you created from scratch and the scripts that you cloned here.
You can filter the scripts in this section by the following criteria:
o Tags
o Status
o Language
o Operating system
o Script owner
l Library
The library contains predefined scripts that you can use in your environment after cloning them
to the My scripts section. You can only inspect and clone these scripts.
You can filter the scripts in this section by the following criteria:
o Tags
o Language
o Operating system
For more information, see Vendor-Approved Scripts (70595).

Scripting plans
A scripting plan allows you to run a script on multiple workloads, to schedule the running of a script,
and to configure additional settings.

You can find the scripting plans that you created and the ones that are applied to your workloads in
Management > Scripting plans. Here, you can check the plan execution location, owner, or status.

A clickable bar shows the following color-coded statuses for scripting plans:

l Running (Blue)
l Checking for compatibility (Dark gray)
l Disabled (Light gray)
l OK (Green)
l Critical alert (Red)

237 © Acronis International GmbH, 2003-2024

l Error (Orange)
l Warning (Yellow)

By clicking the bar, you can see which status a plan has and on how many workloads. Each status is
also clickable.

On the Scripting plans tab, you can manage the plans by performing the following actions:

l Run
l Stop
l Edit
l Rename
l Disable
l Enable
l Clone
l Export. The plan configuration will be exported in a JSON format to the local machine.
l Delete

The visibility of a scripting plan and the available actions with it depend on the plan owner and your
user role. For example, company administrators can only see the partner-owned scripting plans that
are applied to their workloads, and cannot perform any actions with these plans.

For more information about who can create and manage scripting plans, refer to "User roles and
Cyber Scripting rights" (p. 226).

To manage a scripting plan

1. In the Cyber Protect console, go to Management > Scripting plans.

2. Find the plan that you want to manage, and then click the ellipsis (...) next to it.
3. Select the desired action, and then follow the instructions on the screen.

Creating a scripting plan

You can create a scripting plan in the following ways:

l On the Devices tab

Select workloads, and then create a scripting plan for them.
l On the Management > Scripting plans tab
Create a scripting plan, and then select the workloads to which to apply the plan.

To create a scripting plan on the Devices tab

1. In the Cyber Protect console, go to Devices > Machine with agents.

2. Select the workloads or the device groups to which you want to apply a scripting plan, and then
click Protect or Protect group, respectively.
3. [If there are already applied plans] Click Add plan.
4. Click Create plan > Scripting plan.

238 © Acronis International GmbH, 2003-2024

 A template for the scripting plan opens.
5. [Optional] To modify the scripting plan name, click the pencil icon.
6. Click Choose script, select the script that you want to use, and then click Done.

Note
You can only use your approved scripts from Script repository > My scripts. Only an
administrator with the Cyber administrator role can use scripts in the Testing status. For more
information about the roles, see "User roles and Cyber Scripting rights" (p. 226).

7. Configure the schedule and the start conditions for the scripting plan.
8. Choose under which account the script will run on the target workload. The following options are
available:
l System account (in macOS, this is the root account)
l Currently logged-in account
9. Specify how long the script can run on the target workload.
If the script cannot finish running within the set time frame, the Cyber Scripting operation will
fail.
The minimum value that you can specify is one minute and the maximum is 1440 minutes.
10. [Only for PowerShell scripts] Configure the PowerShell execution policy.
For more information about this policy, refer to the Microsoft documentation.
11. Click Create.

To create a scripting plan on the Scripting plans tab

1. In the Cyber Protect console, go to Management > Scripting plans.

2. Click Create plan.
A template for the scripting plan opens.
3. [Optional] To select the workloads or the device groups to which you want to apply the new plan,
click Add workloads.
a. Click Machines with agents to expand the list, and then select the desired workloads or
device groups.
b. Click Add.
For more information about how to create device groups on the partner level, refer to "Devices
tab" (p. 308).

Note
You can also select workloads or device groups after you create the plan.

4. [Optional] To modify the scripting plan name, click the pencil icon.
5. Click Choose script, select the script that you want to use, and then click Done.

239 © Acronis International GmbH, 2003-2024

 Note
You can only use your approved scripts from Script repository > My scripts. Only an
administrator with the Cyber administrator role can use scripts in the Testing status. For more
information about the roles, see "User roles and Cyber Scripting rights" (p. 226).

6. Configure the schedule and the start conditions for the scripting plan.
7. Choose under which account the script will run on the target workload. The following options are
available:
l System account (in macOS, this is the root account)
l Currently logged-in account
8. Specify how long the script can run on the target workload.
If the script cannot finish running within the set time frame, the Cyber Scripting operation will
fail.
The minimum value that you can specify is one minute and the maximum is 1440 minutes.
9. [Only for PowerShell scripts] Configure the PowerShell execution policy.
For more information about this policy, refer to the Microsoft documentation.
10. Click Create.

Schedule and start conditions

Schedule
You can configure a scripting plan to run once or repeatedly, and to start on a schedule or to be
triggered by a certain event.

The following options are available:

l Run once
For this option, you must configure the date and time when the plan will run.
l Schedule by time
With this option, you can configure scripting plans that run hourly, daily, or monthly.
To make the schedule effective only temporarily, select the Run within a date range check box,
and then configure the period during which the scheduled plan will run.
l When user logs in to the system
You can choose whether a specific user or any user who logs in triggers the scripting plan.
l When user logs off the system
You can choose whether a specific user or any user who logs off triggers the scripting plan.
l On the system startup
l When system is shut down

Note
This scheduling option only works with scripts that run under the system account.

240 © Acronis International GmbH, 2003-2024

l When system goes online

Start conditions
Start conditions add more flexibility to your scheduled plans. If you configure multiple conditions, all
of them must be met simultaneously in order for the plan to start.

Start conditions are not effective if you run the plan manually, by using the Run now option.

Condition Description

Run only if workload is The script will run when the target workload is connected to the Internet.
online

User is idle This condition is met when a screen saver is running on the machine or the
machine is locked.

User logged off With this condition, you can postpone a scheduled scripting plan until the user
of the target workload logs off.

Fits time interval With this condition, a scripting plan can only start within the specified time
interval. For example, you can use this condition to limit the User is logged off
condition.

Save battery power With this condition, you can ensure that the scripting plan would not be
interrupted because of a low battery. The following options are available:

l Do not start when on battery

The plan will start only if the machine is connected to a power source.
l Start when on battery if the battery level is higher than
The plan will start if the machine is connected to a power source or if the
battery level is higher than the specified value.

Do not start on metered This condition prevents the plan from starting if the target workload accesses
connection the Internet via a metered connection.

Do not start when This condition prevents the plan from starting if the target workload is
connected to the connected to any of the specified wireless networks. To use this condition, you
following Wi-Fi networks must specify the SSID of the forbidden network.

The restriction applies to all networks that contain the specified name as a
substring in their name, case-insensitive. For example, if you specify phone as
the network name, the plan will not start when the device is connected to any
of the following networks: John's iPhone, phone_wifi, or my_PHONE_wifi.

Check device IP address This condition prevents the plan from starting if any of the IP addresses of the
target workload are within or outside of the specified IP address range.

The following options are available:

l Start if outside IP range

l Start if within IP range

241 © Acronis International GmbH, 2003-2024

 Condition Description

Only IPv4 addresses are supported.

If start conditions are This option allows you to set the time interval after which the plan will run,
not met, run the task irrespective of any other conditions. The plan will start as soon as the other
anyway conditions are met or the specified period ends, depending on which comes
first.

This option is not available if you configured the scripting plan to run only
once.

Managing the target workloads for a plan

You can select the workloads or the device groups to which to apply a scripting plan while you
create the plan, or later.

Partner administrators can apply the same plan to workloads from different customers, and can
create device groups that contain workloads from different customers. To learn how to create a
static or a dynamic device group on the partner level, refer to the "Devices tab" (p. 308).

To add initial workloads to a plan

1. In the Cyber Protect console, go to Management > Scripting plans.

2. Click the name of the plan for which you want to specify target workloads.
3. Click Add workloads.
4. Select the desired workloads or device groups, and then click Add.

Note
To select a device group, click its parent level, and then, in the main pane, select the check box
next to its name.

5. To save the edited plan, click Save.

To manage existing workloads for a plan

1. In the Cyber Protect console, go to Management > Scripting plans.

2. Click the name of the plan whose target workloads you want to change.
3. Click Manage workloads.
The Devices screen lists the workloads to which the scripting plan is currently applied. If you
manage more than one tenant, the workloads are sorted by tenant.

242 © Acronis International GmbH, 2003-2024

 l To add new workloads or device groups, click Add.
a. Select the desired workloads or device groups. You can add workloads from all tenants
that you manage.

Note
To select a device group, click its parent level, and then, in the main pane, select the check
box next to its name.

b. Click Add.
l To remove workloads or device groups, select them, and then click Remove.
4. Click Done.
5. To save the edited plan, click Save.

Plans on different administration levels

The following table summarizes which plans administrators from different levels can see and
manage.

Administrator Administration level Plans Rights

Partner Partner level Own plans Full

administrator access

Customer plans (including plans in Full

units) access

Unit plans Full

access

Customer level Partner plans that are applied to Read-

workloads of this customer only
(for customers that are managed
by the service provider) Customer plans (including plans in Full
units) access

Unit plans Full

access

Unit level Partner plans that are applied to Read-

workloads of this unit only
(for customers that are managed
by the service provider) Customer plans that are applied to Read-

243 © Acronis International GmbH, 2003-2024

 Administrator Administration level Plans Rights

workloads of this unit only

Unit plans Full

access

Company Customer level Partner plans that are applied to Read-

administrator workloads of this customer or unit only

Customer plans (including plans in Full

units) access

Unit plans Full

access

Unit level Partner plans that are applied to Read-

workloads of this unit only

Customer plans that are applied to Read-

workloads of this unit only

Unit plans Full

access

Unit Unit level Partner plans that are applied to Read-

administrator workloads of this unit only

Customer plans that are applied to Read-

workloads of this unit only

Unit plans Full

access

Important
The owner of a plan is the tenant in which the plan was created. Thus, if a partner administrator
created a plan on the customer tenant level, the customer tenant is the owner of that plan.

Compatibility issues with scripting plans

In some cases, applying a scripting plan on a workload might cause compatibility issues. You might
observe the following compatibility issues:

l Incompatible operating system – this issue appears when the workload's operating system is not
supported.
l Unsupported agent – this issue appears when the version of the protection agent on the
workload is outdated and does not support the Cyber Scripting functionality.
l Insufficient quota – this issue appears when there is not enough service quota in the tenant to
assign to the selected workloads.

244 © Acronis International GmbH, 2003-2024

If the scripting plan is applied to up to 150 individually selected workloads, you will be prompted to
resolve the existing conflicts before saving the plan. To resolve a conflict, remove the root cause for
it or remove the affected workloads from the plan. For more information, see "Resolving
compatibility issues with scripting plans" (p. 245). If you save the plan without resolving the conflicts,
it will be automatically disabled for the incompatible workloads, and alerts will be shown.

If the scripting plan is applied to more than 150 workloads or to device groups, it will be saved, and
then checked for compatibility. The plan will be automatically disabled for the incompatible
workloads, and alerts will be shown.

Resolving compatibility issues with scripting plans

Depending on the cause of the compatibility issues, you can perform different actions to resolve the
compatibility issues as a part of the process of creating a new scripting plan.

Note
When resolving a compatibility issue by removing workloads from a plan, you cannot remove
workloads that are part of a device group.

To resolve the compatibility issues

1. Click Review issues.

2. [To resolve compatibility issues with incompatible operating systems]
a. On the Incompatible operating system tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
3. [To resolve compatibility issues with unsupported agents by removing workloads from the plan]
a. On the Unsupported agents tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
4. [To resolve compatibility issues with unsupported agents by updating the agent version] Click Go
to the Agents list.

Note
This option is available only for customer administrators.

5. [To resolve compatibility issues with insufficient quota by removing workloads from the plan]
a. On the Insufficient quota tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
6. [To resolve compatibility issues with insufficient quota by increasing the quota of the tenant]

Note
This option is available only for partner administrators.

245 © Acronis International GmbH, 2003-2024

 a. On the Insufficient quota tab, click Go to the Management portal.
b. Increase the service quota for the customer.

Script quick run

You can run a script immediately, without including it in a scripting plan. You cannot use this
operation on more than 150 workloads, on offline workloads, or on device groups.

The target workload must be assigned a service quota that supports the Script quick run
functionality, and the Advanced Management pack must be enabled for its tenant. An appropriate
service quota will be automatically assigned if it is available in the tenant.

Note
You can only use your approved scripts from Script repository > My scripts. Only an administrator
with the Cyber administrator role can use scripts in the Testing status. For more information
about the roles, see "User roles and Cyber Scripting rights" (p. 226).

You can start a quick run in the following ways:

l From the Devices tab

Select one or more workloads, and then select which script to run on it.
l From the Management > Scripting repository tab
Select a script, and then select one or more target workloads.

To run a script from the Devices tab

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the workload on which you want to run the script, and then click Protect.
3. Click Script quick run.
4. Click Choose script, select the script that you want to use, and then click Done.
5. Choose under which account the script will run on the target workload. The following options are
available:
l System account (in macOS, this is the root account)
l Currently logged-in account
6. Specify how long the script can run on the target workload.
If the script cannot finish running within the set time frame, the Cyber Script operation will fail.
You can use values between 1 and 1440 minutes.
7. [Only for PowerShell scripts] Configure the PowerShell execution policy.
For more information about this policy, see the Microsoft documentation.
8. Click Run now.

To run a script from the Scripting repository tab

1. In the Cyber Protect console, go to Management > Scripting repository.

2. Select the script that you want to run, and then click Script quick run.
3. Click Add workloads to select the target workloads, and then click Add.

246 © Acronis International GmbH, 2003-2024

4. Click Choose script, select the script that you want to use, and then click Done.
5. Choose under which account the script will run on the target workload. The following options are
available:
l System account (in macOS, this is the root account)
l Currently logged-in account
6. Specify how long the script can run on the target workload.
If the script cannot finish running within the set time frame, the Cyber Script operation will fail.
You can use values between 1 and 1440 minutes.
7. [Only for PowerShell scripts] Configure the PowerShell execution policy.
For more information about this policy, see the Microsoft documentation.
8. Click Run now.

Protection of collaboration and communication

applications
Zoom, Cisco Webex Meetings, Citrix Workspace, and Microsoft Teams are now widely used for
video/web conferencing and communications. The Cyber Protection service allows you to protect
your collaboration tools.

The protection configuration for Zoom, Cisco Webex Meetings, Citrix Workspace, and Microsoft
Teams is similar. In the example below, we will consider configuration for Zoom.

To set up Zoom protection

1. Install the protection agent on the machine where the collaboration application is installed.
2. Log in to the Cyber Protect console and apply a protection plan that has one of the following
modules enabled:
l Antivirus and Antimalware protection (with the Self-Protection and Active Protection
settings enabled) – if you have one of the Cyber Protect editions.
l Active Protection (with the Self-Protection setting enabled) – if you have one of the Cyber
Backup editions.
3. [Optional] For automatic update installation, configure the Patch management module in the
protection plan.

As a result, your Zoom application will be under protection that includes the following activities:

l Installing Zoom client updates automatically

l Protecting Zoom processes from code injections
l Preventing suspicious operations by Zoom processes
l Protecting the "hosts" file from adding the domains related to Zoom

247 © Acronis International GmbH, 2003-2024

Understanding your current level of protection

Monitoring
The Monitoring tab provides important information about your current level of protection, and
includes the following dashboards:

l Overview
l Activities
l Alerts
l Threat feed (for more information, see "Threat feed" (p. 288))

The Overview dashboard

The Overview dashboard provides a number of customizable widgets that give an overview of
operations related to the Cyber Protection service. Widgets for other services will be available in
future releases.

The widgets are updated every five minutes. The widgets have clickable elements that enable you to
investigate and troubleshoot issues. You can download the current state of the dashboard or send it
via email in the .pdf or/and .xlsx format.

You can choose from a variety of widgets, presented as tables, pie charts, bar charts, lists, and tree
maps. You can add multiple widgets of the same type with different filters.

The buttons Download and Send in Monitoring > Overview are not available in the Standard
editions of the Cyber Protection service.

To rearrange the widgets on the dashboard

Drag and drop the widgets by clicking on their names.

To edit a widget

248 © Acronis International GmbH, 2003-2024

Click the pencil icon next to the widget name. Editing a widget enables you to rename it, change the
time range, set filters, and group rows.

To add a widget

Click Add widget, and then do one of the following:

l Click the widget that you want to add. The widget will be added with the default settings.
l To edit the widget before adding it, click Customize when the widget is selected. After editing the
widget, click Done.

To remove a widget

Click the X sign next to the widget name.

The Activities dashboard

The Activities dashboard provides an overview of the current and past activities. By default, the
retention period is 90 days.

To customize the view of the Activities dashboard, click the gear icon, and then select the columns
that you want to see.

To see the activity progress in real time, select the Refresh automatically check box. However,
frequent updating of multiple activities degrades the performance of the management server.

You can search the listed activities by the following criteria:

l Device name
This is the machine on which the activity is carried out.
l Started by
This is the account who started the activity.

You can also filter the activities by the following properties:

l Status
For example, succeeded, failed, in progress, canceled.
l Type
For example, applying plan, deleting backups, installing software updates.
l Time
For example, the most recent activities, the activities from the past 24 hours, or the activities
during a specific period within the default retention period.

To see more details about an activity, select this activity from the list, and then, in the Activity
details panel, click All properties. For more information about the available properties, refer to the
Activity and Task API references in the Developer Network Portal.

249 © Acronis International GmbH, 2003-2024

The Alerts dashboard
The Alerts dashboard displays all your current alerts. Alerts listed are critical or error alerts, and are
typically related to tasks such as backup that have failed for some reason.

To filter alerts on the dashboard

1. From the View drop-down list, select one of the following criteria:
l Alert severity
l Alert category
l Alert type
l Monitoring type
l Date range: from ... to ...
l Workload
l Plan
l Customer
2. If you have selected the Alert category, from the Category drop-down list, select the category
of alerts that you want to view.
3. If you want to view all the alerts without filtering them, click All alert types.

Within each alert you can do the following:

l Access the relevant device the alert relates to by clicking the Devices link.
l Read and try to follow some advice in the Troubleshooting section of the alert.
l Access the relevant documentation and knowledge base article by clicking Search for solution.
The Search for solution functionality will pre-fill your request will the current alert details to
assist you the most effectively.

To sort alerts on the dashboard

On the alerts table, click on the arrow button next to one of the following column names:

l Alert severity
l Alert type
l Created
l Alert category
l Workload
l Plan

If the Advanced Automation service is enabled for your account, you can also create a new service
desk ticket directly from the alert.

To create a service desk ticket

250 © Acronis International GmbH, 2003-2024

1. In the relevant alert, click Create a new ticket.
Alternatively, when working in the table view mode, select an alert and then select Create a new
ticket in the right pane.
2. Define the following:
l In the header section, select the Billable check box if you want the time recorded on the ticket
to be billed to the customer. In addition, select the Email the customer check box if you want
to send ticket updates to the customer.
l In the General information section, define a ticket title. This field is pre-filled with an alert
summary but can be edited.
l In the Customer information section, the fields are pre-filled with the relevant information
from the alert.
l In the Configuration item or service section, the fields are pre-filled with the device linked to
the alert. You can reassign a device, as required.
l In the Support agent section, the fields are pre-filled with the default support agent, category,
and support group. You can reassign a different agent, as required.
l In the Ticket update section, the fields are pre-filled with the alert description and details.
The Status field is set as New by default, and can be changed.
l In the Attachments, Billable items, and Internal notes sections, add the relevant items as
required.
3. Click Done. When the ticket is created, a link to the ticket is added to the alert.
If an alert is closed, the related ticket is also automatically closed.

Note
You can only create one ticket per alert.

Alert types
Alerts will be generated for the following alert types:

l Backup alerts
l Disaster recovery alerts
l Antimalware protection alerts
l Licensing alerts
l URL Filtering alerts
l EDR alerts
l Device Control alerts
l System alerts

Backup alerts
Alert Description How to resolve the alert

Backup failed An alert is generated when Check the log of the faulty backup

251 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

the backup failed with a operation: click the workload to select

resolvable error while running it, click Activities, and then find the
or it was interrupted due to warning in the log. The message should
system shut down. point you to the root cause of the issue
the software notifies you about.

Backup succeeded with An alert is generated when Check logs of conversion to VM,
warnings the backup succeeded with replication, or validation plans. Issues
warnings. during these operations generate an
"Activity failed" or "Activity finished with
warning" alerts.

Backup is canceled An alert is generated every You can either start the backup
time a backup activity is manually by clicking Run now or wait
manually canceled by the until it runs at the next scheduled time.
user.

Backup canceled due to closed An alert is generated when Re-configure schedule or edit options
backup window the backup activity was of the backup plan in Performance
missed because it did not fit in and backup window. Expand the
the window specified in the section with your product for
backup options. instructions.

Backup is waiting This alert is generated Make sure that your backups are
anytime you have a running in the expected time windows
scheduling conflict and two and according to their schedule, and
backups tasks are initiated at avoid scheduling conflicts where
the same time. In this case, possible.
the second backup task is
queued until the first one is
finished or stopped.

Backup is not responding An alert is generated when The issue might be caused by a lockup.
the running backup has not Follow this article to collect the
shown any progress for some necessary troubleshooting information.
time, and may be frozen.

Backup did not start An alert is generated when Make sure you are using the latest
the scheduled backup failed build of your Acronis Backup product.
to start for unknown reason.
l If the agent machine was available
during the backup start time:

1. Edit the backup task start time.

2. If the alert appears again, recreate
the backup task.
3. If the newly created backup task
also triggers the alert, contact

252 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

Acronis Support for assistance.

l If the agent was offline:

1. Do not turn off machine during

backup time.
2. If machine was not turned off, make
sure Acronis Managed Machine
Service is running: Start -> Search ->
services.msc -> locate Acronis
Managed Machine Service. Contact
Acronis Support, if you need
assistance.

Backup status is unknown An alert is generated when 1. Check if the agent is expected to be
the backup agent was offline offline (for example, it is a notebook
at a scheduled backup time. that is outside the Management
The status of the resource Server network).
backups will be unknown until 2. If the agent should not be offline,
the backup agent becomes make sure Acronis Managed
online. Machine Service is running: Start ->
Search -> services.msc -> locate
Acronis Managed Machine Service
and check its status. Start the
service, if it is stopped.

Backup is missing An alert is generated when

there is not a successful
backup for more than [Days
from last backup] days.

Backup is corrupted An alert is generated when Follow steps from the article
the validation activity is Troubleshooting Issues with Corrupt
successful and shows that the Backups.
backup is corrupted.
If you need assistance with identifying
the root cause for archive corruption,
contact Acronis Support.

Continuous Data Protection An alert is generated if the Verify the following limitations:
failed continuous protection of
1. Continuous data protection is
backup failed.
supported only for the NTFS file
system and the following operating
systems:
l Desktop: Windows 7 and later
l Server: Windows Server 2008 R2
and later

253 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

2. CDP doesn't support Acronis

Secure Zone as a destination.
3. NFS folders that are mounted on
Windows are not supported.
4. Continuous replication is not
supported: if there are two
locations in the protection plan,
CDP slices are created only in the
first destination, and then the
changes are replicated to the
second one with the next backup.
5. If changes in a local protected
folder are applied from a network
source (e.g. when users access the
folder from network), CDP doesn't
detect them.
6. If a file is being used, e.g. some
changes are being made in an Excel
file, CDP doesn't detect the
changes. For the changes to be
detected by CDP save them and
close the file.

Hyper-V hosts configuration is An alert is generated when You should register these Agents for
not valid there are 2 or more Agents Hyper-V under different child units of
for Hyper-V installed on this account to avoid conflicts.
Hyper-V hosts with the same
host name, which is not
supported on the same
account level.

Validation failed An alert is generated when Check the log of the faulty operation:
the validation process of your click the machine to select it, click
backup cannot be completed. Activities, and then find the warning in
the log. The message should point you
to the root cause of the issue the
software notifies you about.

Failed to migrate the backups An alert is generated when it Migration of Acronis Cyber Backup
in the cloud storage to the new failed to migrate the backups Advanced archives is described here.
format in the cloud storage to the
Migration of Acronis Cyber Backup
new format.
archives is described here.

Before contacting Acronis Support,

please collect the following reports
using the migrate_archives tool:

254 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

migrate_archives.exe --
account=<Acronis Account> --
password=<password> --
subaccounts=All > report1.txt

migrate_archives.exe --
cmd=finishUpgrade --
account=<Acronis Account> --
password=<password> > report2.txt

Encryption password is An alert is generated when There is no way to recover encrypted

missing the database encryption key is backups if you lose or forget the
incorrect, corrupt, or missing. password. You must set the encryption
password locally, on the protected
device. You cannot set the encryption
password in the protection plan. For
more information, see Setting the
encryption password.

Upload is pending An alert is generated if

scheduled check finds that
Physical Data Shipping to
cloud archive for this backup
plan is not uploaded to
storage.

Backup recovery failed An alert is generated when Determine the exact date of the backup
the recovery operation fails failure and attempt recovery with the
when you try to recover files last successful backup.
or system backups.

Disaster recovery alerts

Alert Description How to resolve the alert

Storage quota exceeds An alert is generated when the Increase the quota or remove
soft quota is exceeded for some archives from the cloud
disaster recovery storage storage.

Quota is reached An alert is generated when:

l Soft quota is exceeded for

cloud servers.
l Soft quota is exceeded for
сompute point.
l Soft quota is exceeded for
public IP addresses.

255 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

Storage quota is exceeded An alert is generated when hard

quota is exceeded for disaster
recovery storage.

This storage is used by primary

and recovery servers. If the
overage for this quota is reached,
it is not possible to create
primary and recovery servers, or
add/extend disks of the existing
primary servers. If the overage
for this quota is exceeded, it is
not possible to initiate a failover
or just start a stopped server.
Running servers continue to run.

Quota is exceeded An alert is generated when: Consider purchasing additional

device quotas or disable backup
l Hard quota is exceeded for
tasks for the devices you no longer
cloud servers.
need to protect.
l Hard quota is exceeded for
сompute point.
l Hard quota is exceeded for
public IP addresses.

Failover error An alert is generated when a 1. Click Edit on the recovery

system problem occurred after server. For more information,
the fail-over action was see Creating a recovery server.
submitted. 2. Decrease CPU/RAM for the
recovery server.
3. Try the failover again.

Test failover error An alert is generated when a 1. Click Edit on the recovery
system problem occurred after server. For more information,
the test action was submitted. see Creating a recovery server.
2. Decrease CPU/RAM for the
recovery server.
3. Try the failover again.

Note
Make sure that there is the same
IP address in IP address in
production network as the one
configured in the DHCP server.

Failback error An alert is generated when a You can see the erroneous
system problem occurred after location in the list of backup

256 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

the fail-back was initiated. storages: it has a number instead

of a name (normally, a location
name matches one of the existing
end users names) and you have
not created this location. Remove
the erroneous location:

1. In the Cyber Protect console,

navigate to Backup Storage.
2. Find the location and click the
cross (x) icon to delete it.
3. Confirm your choice by clicking
Delete.
4. Retry the failover.

Failback is canceled An alert is generated when the Manually dismiss the alert from
failback was canceled by the the console.
user.

VPN connection error An alert is generated when the In case you have faced an issue
VPN connection failure occurs with deploying or connecting
due to reasons not depend on Acronis VPN appliance, please
the user's actions. Status report contact Acronis Support.
from VPN appliance is outdated.
Please send the following
information with your email:

l Screenshots of the error

messages (if there are any)
l Screenshot of the Acronis VPN
Appliance CLI interface
l Your Acronis Backup Cloud
data center and group name.

(Vpn Unreachable) Connectivity An alert is generated when the In case you have faced an issue
gateway is not reachable DR service can't reach with deploying or connecting
connectivity gateway. Status Acronis VPN appliance, please
report from connectivity gateway contact Acronis Support.
is outdated.
Please send the following
information with your email:

l Screenshots of the error

messages (if there are any)
l Screenshot of the Acronis VPN
Appliance CLI interface
l Your Acronis Backup Cloud
data center and group name

257 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

DR IP reassignment required An alert is generated if VPN Reassign the IP address. For more
appliance detects network information, see Reassigning IP
changes. addresses.

Connectivity gateway failure An alert is generated when it Use Connection Verification Tool
failed to deploy VPN server in the and check its output for errors.
cloud.
Allow Acronis software through
application control of your
firewalls and antimalware
software.

Primary server creation failure An alert is generated when the

primary server was not created
due to error.

Recovery server creation failure An alert is generated when the Make sure the recovery server
recovery server was not created matches the Software
due to error. requirements.

Delete Primary Server An alert is generated when a

primary server is deleted.

Server recovery failure An alert is generated when the Find the details. If the error
primary or recovery server failed message is generic or unclear, for
to recover. example "Internal error", navigate
to Disaster Recovery → Servers,
click to select the affected
machine and click Activities. Click
an activity, hold ctrl and left-click
the activity. Now you will be able
to see the ellipsis (...) sign near
every activity. Click and select
Task activity info.

Backup failed An alerts is generated when the 1. Verify the connection of the
backup of cloud server (primary backup location.
or server in production failover 2. Check the backup storage
state) failed. device (local backups).

Network limit exceeds An alert is generated when the

maximum number of cloud
networks is reached (5 networks).

Runbook failure An alert is generated when the It does not affect the product
runbook execution failed. functionality, and it can be safely
ignored. For more information,
see Creating a runbook.

258 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

Runbook warning An alert is generated when the It does not affect the product
runbook execution is completed functionality, and it can be safely
with warnings. ignored. For more information,
see Creating a runbook.

Runbook User Interaction An alert is generated when the It does not affect the product
Required runbook is waiting for user functionality, and it can be safely
interaction. ignored. For more information,
see Creating a runbook.

Internet traffic blocked An alert is generated when the

internet traffic was blocked by
the administrator.

Internet traffic unblocked An alert is generated when the

internet traffic was unblocked by
the administrator.

Local networks overlap An alert is generated when

identical or overlapping local
networks is detected.

Licensing switch insufficient An alert is generated when the l Make sure the tenant and user
server quota cloud servers quota is not have Web hosting servers
enough. quota or Servers quota
available for a physical server.
l Make sure the tenant and user
have Web hosting servers
quota or Virtual machines
quota available for a virtual
server. A virtual server cannot
use Servers quota.

Licensing switch insufficient An alert is generated when the For more information, see
offering item disaster recovery storage Disaster recovery quotas.
offering item is disabled.

Licensing switch error An alert is generated when the

disaster recovery upgrade
encountered an error.

Licensing switch insufficient An alert is generated when there In the management portal, check
compute points are no compute points available. and increase hard quota for
Compute points.

Licensing switch insufficient An alert is generated when the

servers offering items cloud servers offering item is
disabled.

259 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

Policy failed to create recovery An alert is generated when an Manually create Recovery Server
server error occurred while setting up without the Internet Access
the disaster recovery property. For more information,
infrastructure. see Creating recovery server

Backup processor auto test An alert is generated when the

failover rescheduled automated test failover run was
rescheduled.

Backup processor auto test An alert is generated when the

failover timeout reached automated test failover
operation expired.

Note
Each Automated Test Failover
run will consume chargeable
compute points.

Backup processor auto test An alert is generated when the 1. Start a test failover of the
failover overall failure last scheduled automated test recover server manually. For
failover of the recovery server more information, see
failed. Performing a test failover.
2. Wait for the next scheduled
date when automatic test
failover will be performed

Failback data transfer error An alert is generated when

failback data transfer fails.

Failback failed An alert is generated when there You can see the erroneous
is an error in the failback. location in the list of backup
storages: it has a number instead
of a name (normally, a location
name matches one of the existing
end users names) and you have
not created this location. Remove
the erroneous location:

1. In Cyber Protection, navigate

to backup storage.
2. Find the location and click the
cross (x) icon to delete it.
3. Confirm your choice by clicking
Delete.

Retry the failover.

Failback confirming failed An alert is generated when the

260 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

failback confirmation failed.

Failback machine is ready for An alert is generated when the

switchover machine is ready for switchover.

Failback switchover finished An alert is generated when the Manually dismiss the alert from
switchover is successful. the console.

Failback target agent offline An alert is generated when the

agent is offline.

Antimalware protection alerts

Alert Description How to resolve the alert

Suspicious remote An alert is generated when Manually dismiss the alert from the console.
connection activity is ransomware coming from a
detected remote connection is
detected.

Suspicious activity is An alert is generated when Manually dismiss the alert from the console. to
detected ransomware is detected in deactivate the alert.
the workload.
Depending on the option you have specified in
Active Protection plan, the malicious process is
stopped, the changes made by the process are
reverted or none actions have been taken yet
and you need to resolve this issue manually.

Read details of the alert to find out which

process is encrypting files and which files are
affected.

If you decide that the process encrypting the

files is sanctioned (false-positive alert), add this
process to Trusted processes:

1. Open Active Protection plan.

2. Click Edit to modify the settings.
3. In Trusted processes, specify trusted
processes that will never be considered
ransomware. Specify the full path to the
process executable, starting with the drive
letter. For example:
C:\Windows\Temp\er76s7sdkh.exe.

Cryptomining activity is An alert is generated when Manually dismiss the alert from the console.
detected Illicit cryptominers are
detected in the workload

261 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

MBR defence: Suspicious An alert is generated when Manually dismiss the alert from the console.
activity is detected and ransomware is detected in
suspended the workload (specifically
MBR / GPT partition is
modified by ransomware).

Unsupported network An alert is generated when Specify the local path for network folder
path is specified the recovery path provided protection (recovery path). Manually dismiss
by the administrator is not a the alert from the console
local folder path.

Critical process is added An alert is generated when a Manually dismiss the alert from the console.
as harmful to the Active critical process is added as a
Protection plan blocked process in the
Protection exclusions list.

Failed to apply Active An alert is generated when Check the error message to see why Active
Protection policy Active Protection policy Protection policy cannot be applied.
failed to be applied.

Secure Zone: An alert is generated when Manually dismiss the alert from the console.
Unauthorized operation ransomware is detected in
is detected and blocked the workload (ASZ partition
is modified by ransomware).

Active Protection service An alert is generated when Check the error message to see why Active
is not running the Active Protection service Protection service is not running.
crashed / is not running.

Active Protection service An alert is generated when Check Windows event logs for crashes of
is not available the Active Protection service Acronis Active Protection service (acronis_
is not available because a protection_service.exe).
driver is incompatible or
missing.

Conflict with another An alert is generated if Active Solution 1: If you want to use Acronis real-
security solution Protection is not available for time protection then uninstall third-party
machine '{{resourceName}}' antivirus on the machine.
because a conflict with
Solution 2: If you want to use the third-party
another security solution
antivirus, disable Acronis real-time protection,
was detected. To enable
URL filtering and Windows defender antivirus
Active Protection, disable or
in the protection plan.
uninstall the conflicting
security solution.

Quarantine action failed An alert is generated when Check the error message to see why
antimalware failed to quarantine failed.
quarantine a detected

262 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

malware.

Malicious process is An alert is generated when a Manually dismiss the alert from the console.
detected malware (process type) is
detected by Behavior engine.
The detected malware is
quarantined.

Malicious process is An alert is generated when a Manually dismiss the alert from the console.
detected, but not malware (process type) is
quarantined detected by Behavior engine.
The detected malware is not
quarantined.

Malware is detected and An alert is generated when a Manually dismiss the alert from the console.
blocked (ODS) malware is detected by
scheduled scan. The
detected malware is
quarantined.

Malware is detected and An alert is generated when a Manually dismiss the alert from the console.
blocked (RTP) malware is detected by Real-
Time protection. The
detected malware is
quarantined.

Malware is detected in a An alert is generated when a Manually dismiss the alert from the console.
backup malware is detected during
backup scanning.

Conflict detected An alert is generated when Disable or uninstall 3rd party security product,
between Real-time antimalware failed to or disable Real-time antimalware protection in
antimalware protection register with Windows the protection plan.
and a security product Security Center.

Failed to run the An alert is generated when it Check the error message to see why Microsoft
Microsoft Security failed to run the Microsoft Security Essentials module failed to run.
Essentials module Security Essentials module.

Real-time protection is An alert is generated when Disable or uninstall 3rd party security product,
not available because Real-time protection failed to or disable Real-time antimalware protection in
third-party antivirus turn on, because 3rd party the protection plan.
software is installed antivirus still have Real-time
protection enabled.

Real-time protection is An alert is generated when Check the error message to see why Acronis
not available due to Real-time protection is not failed to install driver on workload.
incompatible or missing available due to
driver

263 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

incompatible or missing
driver.

Cyber Protection (or An alert is generated when Manually dismiss the alert from the console.
Active Protection) service Cyber Protection Service
is not responding responds to health check
ping from console.

Security definition An alert is generated when Check the error message to see why security
update failed security definition update definition update failed.
failed.

Tamper Protection is An alert is generated when Disable Tamper Protection settings on the
enabled Microsoft Defender settings Windows workload.
cannot be changed because
tamper protection is
enabled.

Windows Defender An alert is generated when Check the error message to see why Windows
module execution failed Windows Defender module defender module failed to run.
execution failed.

Windows Defender is An alert is generated when Disable or uninstall 3rd party security product.
blocked by a third-party Windows Defender is
antivirus software blocked because a third
party Antivirus is installed on
the machine.

Group policy conflict An alert is generated when Disable group policy settings on the Windows
Microsoft Defender settings workload.
cannot be changed because
it is controlled by a group
policy.

Microsoft Security An alert is generated when Manually dismiss the alert from the console.
Essentials took action to Microsoft Security Essential
protect this machine deleted / quarantined a
from malware malware.

Microsoft Security An alert is generated when Manually dismiss the alert from the console.
Essentials detected Microsoft Security Essentials
malware detected malware or other
potentially unwanted
software.

264 © Acronis International GmbH, 2003-2024

Licensing alerts
Alert Description How to resolve the alert

Storage quota almost reached An alert is generated when the usage Consider purchasing additional
drops below 80% (after cleanup or storage or freeing up space in
quota upgrade). your cloud storage.

Storage quota exceeded An alert is generated when all 100% Buy more storage space. For
of the storage quota is used. more information on how to do
that, verify the how to purchase
more cloud storage.

Workload quota reached An alert is generated when usage for

offering item > 0 and usage > quota,
but usage <= quota + overage.

Workload quota exceeded An alert is generated when the usage

for offering item > quota + overage.

The workload has no quota to An alert is generated when:

apply a backup plan (resource
l The quota was removed manually:
has no service quota)
Device > Details > Service quota,
and then click Change and select
the No quota option.
l The Management Console offering
item is disabled.
l The Management Console
quota+overage value of the
offering item is decreased below
current usage.

Cannot protect a workload An alert is generated when the

with assigned quota offering item is not sufficient, and
you need to have:

l a dynamic group.
l a backup plan assigned to that
group.
l you added a resource that falls to
that dynamic group, but has some
qualities that forbid applying the
same backup plan to it.

Subscription license expired An alert is generated when the daily After a subscription expires, all
check for license/maintenance product functionality except
expiration alerts, asked the license recovery is blocked until further
server, and got the response that the subscription renewal. Backed

265 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

license is expired. up data is still accessible for

recovery. Purchase a new
license.

Note
If you have recently purchased
a new subscription but still
receive the message that
subscription is expired, you
need to import new
subscription from Acronis
Account: in Management
Console, go to Settings ->
Licenses and click Sync in the
top right corner. Subscriptions
will be synchronized.

Subscription license will expire An alert is generated when the daily Consider purchasing a new
soon check for license/maintenance subscription.
expiration alerts, asked the license
server, and got the response that the
license will expire in less than 30
days.

URL Filtering alerts

Alert Description How to resolve the alert

Malicious URL was blocked An alert is generated when a Check the URL filtering settings.
malicious URL is blocked by URL URL filtering is blocking pages
filtering. which are supposed to be blocked
according to the URL filtering
settings.

A malicious URL warning was An alert is generated when you Check the URL filtering settings.
ignored selected to proceed with the
malicious URL blocked by
URL filtering.

Conflict detected between URL An alert is generated when the Check the URL filtering settings.
filtering and a security product URL filtering cannot be enabled
due to a conflict with another
security product.

Website URL is blocked An alert is generated when a URL Check the URL filtering settings.
meets all the criteria specified in
the blocked category for URL

266 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

filtering.

EDR alerts
Alert Description How to resolve the alert

Incident Detected An alert is generated when an This alert informs you about a
incident is created or when the new incident or if an old incident
status for an existing incident is has been updated. You can view
updated. the alert and close it. You can
choose to open the incident for
further investigation if required.

Indicator of compromise (IOCs) An alert is generated when a new This alert is to inform you that an
detected indicator of compromise was IOC has been detected on one or
detected by EDR IOC threat many workloads. You will view
search service. the alert and then you can click
on the link in the alert to view
details about the IOC.

Failed to isolate the workload An alert is generated when the Take the necessary actions.
from the network user triggers the action to isolate
the machine from network, and
isolation action fails.

Failed to reconnect the workload An alert is generated when the Take the necessary actions.
to the network user triggers the action to
reconnect the machine back to
network, and the action failed.

Windows Defender Firewall An alert is generated when the This alert is to inform you that
settings was modified settings to the firewall were firewall details were modified on
modified on isolated machine. the isolated machine. It is
informative only and you can
close the alert after viewing it.

Device Control alerts

Alert Description How to resolve the alert

Device control and Data loss An alert is generated when the Disable the option on the
prevention will run with limited DeviceLock agent started on affected machines to avoid
functionality (Incompatible physical machine with CPU which alerts.
CPU detected) has supporting for CET technology.

Device control functionality is not An alert is generated when

yet supported on macOS Ventura DeviceLock agent started on

267 © Acronis International GmbH, 2003-2024

 Alert Description How to resolve the alert

physical macOS Ventura machine,

and the protection plan with
Device Control is applied to the
agent. Applicable only for versions
when there is a problem with the
kernel panic due DeviceLock driver.

Allowed transfer of sensitive data An alert is generated when

transferring for sensitivity content
is allowed.

Justified transfer of sensitive data An alert is generated when

transferring sensitivity content is
justified.

Denied transfer of sensitive data An alert is generated when

transferring sensitivity content is
blocked.

Review the results of Data Loss An alert is generated when it is

Prevention observation mode time to review the Observation
results:

l Advanced DLP Pack license is

not applied.
l A month passed since the
Observation mode was enabled
in any Protection plan applied to
at least one workload.
l A month passed since the last
similar alert was raised and
some usage of DLP in
Observation mode is detected.

Security identifier was changed for An alert is generated when we

user have the situation when a SID is
updated for known username. This
might happen when OS is re-
installed on a non-domain PC.

Peripheral device access is An alert is generated when some

blocked actions (read/write operations) for
supported devices are blocked.

Unable to connect to a remote SSL An alert is generated when the Add the resource to the
resource. access to a remote SSL resource is allowlist for remote hosts.
blocked due to additional
handshake prevention used at the
resource.

268 © Acronis International GmbH, 2003-2024

System alerts
Alert Description How to resolve the alert

Agent is outdated An alert is generated when the Go to Agents list and initiate
agent version is outdated. updating the agent.

Automatic update failed An alert is generated when the Try to perform a manual update.
agent auto update failed.

You need to restart device after An alert is generated when a Restart the workload.
installing a new agent reboot is required after remote
install was successful.

Activity failed An alert is generated when an Restart all Acronis services on

activity failed. the machine.

Activity succeeded with warnings An alert is generated when an

activity was successful but some
warnings were generated.

Activity is not responding An alert is generated when an

activity in progress is not
responding.

Plan deployment failed An alert is generated when the

protection plan deployment
failed.

Failed to convert user name to An alert is generated when the

SID schedule SID conversion failed.

Alert widgets
In the alert widgets, you can see the following details of alerts related to your workload:

Field Description

5 latest alerts A list of five latest alerts.

widget

Historical alerts A graphical widget showing alerts by alert severity, alert type and the time
summary range.

Active alerts A graphical widget showing active alerts by alert severity and alert type,
summary as well as the sum of active alerts.

Alerts history A table view of historical alerts.

Active alerts A table view of active alerts.

details

269 © Acronis International GmbH, 2003-2024

Cyber Protection
This widget shows the overall information about the size of backups, blocked malware, blocked
URLs, found vulnerabilities, and installed patches.

The upper row shows the current statistics:

l Backed up today – the sum of recovery point sizes for the last 24 hours
l Malware blocked – the number of currently active alerts about malware blocked
l URLs blocked – the number of currently active alerts about URLs blocked
l Existing vulnerabilities – the number of currently existing vulnerabilities
l Patches ready to install – the number of currently available patches to be installed

The lower row shows the overall statistics:

l The compressed size of all backups

l The accumulated number of blocked malware across all machines
l The accumulated number of blocked URLs across all machines
l The accumulated number of discovered vulnerabilities across all machines
l The accumulated number of installed updates/patches across all machines

Protection status
This widget shows the current protection status for all machines.

A machine can be in one of the following statuses:

l Protected – machines with applied protection plan.

l Unprotected – machines without applied protection plan. These include both discovered
machines and managed machines with no protection plan applied.
l Managed – machines with installed protection agent.
l Discovered – machines without installed protection agent.

If you click on the machine status, you will be redirected to the list of machines with this status for
more details.

270 © Acronis International GmbH, 2003-2024

Discovered machines
This widget shows the list of discovered machines during the specified time range.

Endpoint Detection and Response (EDR) widgets

Endpoint Detection and Response (EDR) includes seven widgets, all of which can be accessed from
the Overview dashboard; three of these widgets are also displayed by default within the EDR
functionality (see "Reviewing incidents" (p. 856)).

The seven widgets available are:

l Top incident distribution per workload

l Threat status (displayed in EDR)
l Incident severity history (displayed in EDR)
l Security incident MTTR

271 © Acronis International GmbH, 2003-2024

l Security incident burndown
l Detection by tactics (displayed in EDR)
l Workload network status

Top incident distribution per workload

This widget displays the top five workloads with the most incidents (click Show all to redirect to the
incident list, which is filtered according to the widget settings).

Hover over a workload row to view a breakdown of the current investigation state for the incidents;
the investigation states are Not started, Investigating, Closed, and False positive. Then click on
the workload you want to analyze further; the incident list is refreshed according to the widget
settings.

Threat status
This widget displays the current threat status for all workloads, highlighting the current number of
incidents that are not mitigated and that need investigating. The widget also indicates the number
of incidents that were mitigated (manually and/or automatically by the system).

Click on the Not mitigated number to display the incident list filtered to show incidents that are not
mitigated.

272 © Acronis International GmbH, 2003-2024

Incident severity history
This widget displays the evolution of attacks by severity, and can help indicate attack campaigns.
When spikes are visible, this can indicate that the organization is under attack.

Hover over the graph to view a breakdown of the incident history at a specific point in the previous
24 hours (the default period). Click on the severity level (Critical, High, or Medium) if you want to
view the list of related incidents; you are redirected to the incident list pre-filtered with incidents
matching the selected severity level.

Security incident MTTR

This widget displays the average resolution time for security incidents. It indicates how quickly
incidents are being investigated and resolved.

Click on a column to view a breakdown of the incidents according to severity (Critical, High, and
Medium), and an indication of how long it took to resolve the different severity levels. The % value
shown in parentheses indicates the increase or decrease in comparison to the previous time period.

273 © Acronis International GmbH, 2003-2024

Security incident burndown
This widget shows the efficiency rate in closing incidents; the number of open incidents are
measured against the number of closed incidents over a period of time.

Hover over a column to view a breakdown of the closed and open incidents for the selected day. If
you click the Open value, the incident list is displayed, and filtered to display incidents currently
open (in the Investigating or Not started states). If you click the Closed value, the incident list is
displayed, and filtered to display incidents that are no longer open (in the Closed or False positive
states).

The % value shown in parentheses indicates the increase or decrease in comparison to the previous
time period.

Detection by tactics
This widget displays the number of times specific attack techniques have been found in incidents
during the selected period.

The values in green and red indicate if there has been an increase or decrease over the previous
time period. In the example below, Privilege Escalation and Command and Control attacks have
seen an increase over the previous time period; this could indicate that your credential
management needs to be analyzed and security enhanced.

274 © Acronis International GmbH, 2003-2024

Workload network status
This widget displays the current network status of your workloads, and indicates how many
workloads are isolated and how many are connected.

Click the Isolated value to view the Workload with agents list (under the Workloads menu in the
Cyber Protect console), which is filtered to display isolated workloads. Click the Connected value to
view the Workload with agents list filtered to display connected workloads.

#CyberFit Score by machine

This widget shows for each machine the total #CyberFit Score, its compound scores, and findings for
each of the assessed metrics:

l Antimalware
l Backup
l Firewall
l VPN

275 © Acronis International GmbH, 2003-2024

l Encryption
l NTLM traffic

To improve the score of each of the metrics, you can view the recommendations that are available
in the report.

For more details about the #CyberFit Score, refer to "#CyberFit Score for machines".

Disk health monitoring

Disk health monitoring provides information about the current disk health status and a forecast
about it, so that you can prevent data loss that might be related to a disk failure. Both HDD and SSD
disks are supported.

Limitations
l Disk health forecast is supported only for machines running Windows.
l Only disks of physical machines are monitored. Disks of virtual machines cannot be monitored
and are not shown in the disk health widgets.
l RAID configurations are not supported. The disk health widgets do not include any information
about machines with RAID implementation.
l NVMe SSDs are not supported.

The disk health is represented by one of the following statuses:

l OK
Disk health is between 70% and 100%.
l Warning
Disk health is between 30% and 70%.
l Critical
Disk health is between 0% and 30%.
l Calculating disk data
The current disk status and forecast are being calculated.

276 © Acronis International GmbH, 2003-2024

How it works
The Disk Health Prediction Service uses an AI-based prediction model.

1. The protection agent collects the SMART parameters of the disks and passes this data to the Disk
Health Prediction Service:
l SMART 5 – Reallocated sectors count.
l SMART 9 – Power-on hours.
l SMART 187 – Reported uncorrectable errors.
l SMART 188 – Command timeout.
l SMART 197 – Current pending sector count.
l SMART 198 – Offline uncorrectable sector count.
l SMART 200 – Write error rate.
2. The Disk Health Prediction Service processes the received SMART parameters, makes forecasts,
and then provides the following disk health characteristics:
l Disk health current state: OK, warning, critical.
l Disk health forecast: negative, stable, positive.
l Disk health forecast probability in percentage.
The prediction period is one month.
3. The Monitoring Service receives these characteristics, and then shows the relevant information
in the disk health widgets in the Cyber Protect console.

Disk health widgets

The results of the disk health monitoring are presented in the following widgets that are available in
the Cyber Protect console.

l Disk health overview is a treemap widget with two levels of detail that can be switched by
drilling down.
o Machine level
Shows summarized information about the disk health status of the selected customer
machines. Only the most critical disk status is shown. The other statuses are shown in a tooltip
when you hover over a particular block. The machine block size depends on the total size of all
disks of the machine. The machine block color depends on the most critical disk status found.

277 © Acronis International GmbH, 2003-2024

 o Disk level
Shows the current disk health status of all disks for the selected machine. Each disk block
shows one of the following disk health forecasts and its probability in percentage:
n Will be degraded
n Will stay stable

278 © Acronis International GmbH, 2003-2024

 n Will be improved

l Disk health status is a pie chart widget that shows the number of disks for each status.

279 © Acronis International GmbH, 2003-2024

Disk health status alerts
The disk health check runs every 30 minutes, while the corresponding alert is generated once a day.
When the disk health changes from Warning to Critical, an alert always is generated.

Alert name Severity Disk health Description

status

Disk failure Warning (30 – 70) The <disk name> disk on this machine is likely to fail in
is possible the future. Run a full image backup of this disk as soon
as possible, replace it, and then recover the image to
the new disk.

Disk failure Critical (0 – 30) The <disk name> disk on this machine is in a critical
is imminent state, and will most likely fail very soon. We do not
recommend an image backup of this disk at this point,
as the added stress can cause the disk to fail. Back up
the most important files on this disk immediately and
replace it.

Data protection map

Note
This feature is available with the Advanced Backup pack.

The data protection map feature allows you to discover all data that are important for you and get
detailed information about number, size, location, protection status of all important files in a
treemap scalable view.

Each block size depends on the total number/size of all important files that belong to a
customer/machine.

Files can have one of the following protection statuses:

l Critical – there are 51-100% of unprotected files with the extensions specified by you that are not
being backed up and will not be backed up with the existing backup settings for the selected
machine/location.
l Low – there are 21-50% of unprotected files with the extensions specified by you that are not
being backed up and will not be backed up with the existing backup settings for the selected
machine/location.
l Medium – there are 1-20% of unprotected files with the extensions specified by you that are not
being backed up and will not be backed up with the existing backup settings for the selected
machine/location.
l High – all files with the extensions specified by you are protected (backed up) for the selected
machine/location.

280 © Acronis International GmbH, 2003-2024

The results of the data protection examination can be found on the monitoring dashboard, in the
Data Protection Map widget, a treemap widget that shows details on a machine level:

l Machine level – shows information about the protection status of important files per machines of
the selected customer.

To protect files that are not protected, hover over the block and click Protect all files. In the dialog
window, you can find information about the number of unprotected files and their location. To
protect them, click Protect all files.

You can also download a detailed report in CSV format.

Vulnerability assessment widgets

Vulnerable machines
This widget shows the vulnerable machines by the vulnerability severity.

The found vulnerability can have one of the following severity levels according to the Common
Vulnerability Scoring System (CVSS) v3.0:

l Secured: no vulnerabilities are found

l Critical: 9.0 - 10.0 CVSS
l High: 7.0 - 8.9 CVSS
l Medium: 4.0 - 6.9 CVSS

281 © Acronis International GmbH, 2003-2024

l Low: 0.1 - 3.9 CVSS
l None: 0.0 CVSS

Existing vulnerabilities
This widget shows currently existing vulnerabilities on machines. In the Existing vulnerabilities
widget, there are two columns showing timestamps:

l First detected – date and time when a vulnerability was detected initially on the machine.
l Last detected – date and time when a vulnerability was detected the last time on the machine.

Patch installation widgets

There are four widgets related to the patch management functionality.

Patch installation status

This widget shows the number of machines grouped by the patch installation status.

l Installed – all available patches are installed on a machine

l Reboot required – after patch installation reboot is required for a machine

282 © Acronis International GmbH, 2003-2024

l Failed – patch installation failed on a machine

Patch installation summary

This widget shows the summary of patches on machines by the patch installation status.

Patch installation history

This widget shows the detailed information about patches on machines.

Missing updates by categories

This widget shows the number of missing updates per category. The following categories are shown:

l Security updates
l Critical updates
l Other

283 © Acronis International GmbH, 2003-2024

Backup scanning details
This widget shows the detailed information about the detected threats in backups.

Recently affected
This widget shows detailed information about workloads that were affected by threats, such as
viruses, malware, and ramsomeware. You can find information about the detected threats, the time
when the threats were detected, and how many files were affected.

284 © Acronis International GmbH, 2003-2024

Downloading data for recently affected workloads
You can download the data for the recently affected workloads, generate a CSV file, and send it to
the recipients that you specify.

To download the data for the recently affected workloads

1. In the Recently affected widget, click Download data.

2. In the Time period field, enter the number of days for which you want to download data. The
maximum number of days that you can enter is 200.
3. In the Recipients field, enter the email addresses of all the people who will receive an email with
a link for downloading the CSV file.
4. Click Download.
The system starts generating the CSV file with the data for the workloads that were affected in
the time period that you specified. When the CSV file is complete, the system sends an email to
the recipients. Each recipient can then download the CSV file.

Cloud applications
This widget shows detailed information about cloud-to-cloud resources:

l Microsoft 365 users (mailbox, OneDrive)

l Microsoft 365 groups (mailbox, group site)
l Microsoft 365 public folders
l Microsoft 365 site collections
l Microsoft 365 Teams

285 © Acronis International GmbH, 2003-2024

l Google Workspace users (Gmail, Google Drive)
l Google Workspace shared drives

Additional information about cloud-to-cloud resources is also available in the following widgets:

l Activities
l Activity list
l 5 latest alerts
l Alerts history
l Active alerts summary
l Historical alerts summary
l Active alert details
l Locations summary

Software inventory widgets

The Software inventory table widget shows detailed information about the all the software that is
installed on Windows and macOS devices in your organization.

The Software overview widget shows the number of new, updated, and deleted applications on
Windows and macOS devices in your organization for a specified time period (7 days, 30 days, or the
current month).

286 © Acronis International GmbH, 2003-2024

When you hover over a certain bar on the chart, a tooltip with the following information shows:

New - the number of newly installed applications.

Updated - the number of updated applications.

Removed - the number of removed applications.

When you click the part of the bar for a certain status, you are redirected to the Software
Management -> Software Inventory page. The information in the page is filtered for the
corresponding date and status.

Hardware inventory widgets

The Hardware inventory and Hardware details table widgets show information about all the
hardware that is installed on physical and virtual Windows and macOS devices in your organization.

The Hardware changes table widget shows information about the added, removed, and changed
hardware on physical and virtual Windows and macOS devices in your organization for a specified
time period (7 days, 30 days, or the current month).

287 © Acronis International GmbH, 2003-2024

Remote sessions widget
This widget shows the detailed information about the remote desktop and file transfer sessions.

Smart protection

Threat feed
Acronis Cyber Protection Operations Center (CPOC) generates security alerts that are sent only to
the related geographic regions. These security alerts provide information about malware,
vulnerabilities, natural disasters, public health, and other types of global events that may affect your
data protection. The threat feed informs you about all the potential threats and allows you to
prevent them.

Note
The availability of this feature depends on the service quotas that are enabled for your account.

Some security alerts can be resolved by following a set of specific actions that are provided by the
security experts. Other security alerts just notify you about the upcoming threats but no
recommended actions are available.

288 © Acronis International GmbH, 2003-2024

Note
Malware alerts are generated only for machines that have the agent for Antimalware protection
installed.

How it works
Acronis Cyber Protection Operations Center monitors external threats and generates alerts about
malware, vulnerability, natural disaster, and public health threats. You will be able to see all these
alerts in the Cyber Protect console, in the Threat feed section. You can perform respective
recommended actions depending on the type of alert.

The main workflow of the threat feed is illustrated in the diagram below.

289 © Acronis International GmbH, 2003-2024

290 © Acronis International GmbH, 2003-2024
To run the recommended actions on received alerts from Acronis Cyber Protection Operations
Center, do the following:

1. In the Cyber Protect console, go to Monitoring> Threat feed to review if there are any existing
security alerts.
2. Select an alert in the list and review the provided details.
3. Click Start to launch the wizard.
4. Enable the actions that you want to be performed and machines to which these actions must be
applied. The following actions can be suggested:
l Vulnerability assessment – to scan machines for vulnerabilities
l Patch management – to install patches on the selected machines
l Antimalware Protection – to run full scan of the selected machines

Note
This action is available only for machines that have the agent for Anitmalware protection
installed.

l Backup of protected or unprotected machines – to back up protected and unprotected

workloads.
If there are no backups yet for the workload (in all accessible locations, cloud and local), or the
existing backups are encrypted, the system creates a full backup with the following name
format:
%workload_name%-Remediation
By default, the destination for the backup is the Cyber Protect Cloud storage, but you can
configure another location before you start the operation.
If a non-encrypted backup already exists, the system will create an incremental backup in the
existing archive.
5. Click Start.
6. On the Activities page, verify that the activity was successfully performed.

291 © Acronis International GmbH, 2003-2024

Deleting all alerts
Automatic clean-up from the threat feed is made after the following time periods:

l Natural disaster – 1 week

l Vulnerability – 1 month
l Malware – 1 month
l Public health – 1 week

Data protection map

The Data protection map functionality allows you

l To get detailed information about stored data (classification, locations, protection status, and
additional information) on your machines.
l To detect whether data are protected or not. The data are considered protected if they are
protected with backup (a protection plan with the backup module enabled).
l To perform actions for data protection.

How it works
1. First, you create a protection plan with the Data protection map module enabled.
2. Then, after the plan was performed and your data were discovered and analyzed, you will get the
visual representation of data protection on the Data protection map widget.
3. You can also go to Devices > Data protection map and find there information about
unprotected files per device.
4. You can take actions to protect the detected unprotected files on devices.

Managing the detected unprotected files

To protect the important files that were detected as unprotected, do the following:

1. In the Cyber Protect console, go to Devices > Data protection map.

In the list of devices, you can find general information about the number of unprotected files,
size of such files per device, and the last data discovery.
To protect files on a particular machine, click the Ellipsis icon and then Protect all files. You will
be redirected to the list of plans where you can create a protection plan with the backup module
enabled.
To delete the particular device with unprotected files from the list, click Hide until next data
discovery.
2. To view a more detailed information about the unprotected files on a particular device, click on
the name of the device.
You will see the number of unprotected files per extension and per location. Define the
extensions in the search field, for which you want to get the information about unprotected files.

292 © Acronis International GmbH, 2003-2024

3. To protect all unprotected files, click Protect all files. You will be redirected to the list of plans
where you can create a protection plan with the backup module enabled.

To get the information about the unprotected files in the form of report, click Download detailed
report in CSV.

Data protection map settings

To learn how to create a protection plan with the Data protection map module, refer to "Creating a
protection plan".

The following settings can be specified for the Data protection map module.

Schedule
You can define different settings to create the schedule according to which the task for data
protection map will be performed.

Field Description

Schedule the This setting defines when the task will run.
task run using
The following values are available:
the following
events l Schedule by time – This is the default setting. The task will run
according to the specified time.
l When user logs in to the system – By default, a login of any user will
trigger the task. You can modify this setting so that only a specific user
account can trigger the task.
l When user logs off the system – By default, a logoff of any user will
trigger the task. You can modify this setting so that only a specific user
account can trigger the task.

Note
The task will not run at system shutdown. Shutting down and logging
off are different events in the scheduling configuration.

l On the system startup – The task will run when the operating system
starts.
l On the system shutdown – The task will run when the operating
system shuts down.

Schedule type The field appears if in Schedule the task run using the following
events you have selected Schedule by time.

The following values are available:

l Monthly – Select the months and the weeks or days of the month
when the task will run.
l Daily – This is the default setting. Select the days of the week when the
task will run.

293 © Acronis International GmbH, 2003-2024

 Field Description

l Hourly – Select the days of the week, repetition number, and the time
interval in which the task will run.

Start at The field appears if in Schedule the task run using the following
events you have selected Schedule by time

Select the exact time when the task will run.

Run within a The field appears if, in Schedule the task run using the following
date range events, you have selected Schedule by time.

Set a range in which the configured schedule will be effective.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs in to the system.
login to the
The following values are available:
operating
system will l Any user - Use this option if you want the login of any user to trigger
initiate a task the task.
l The following user - Use this option if you want only the login of a
specific user account to trigger the task.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs off the system.
logout from the
The following values are available:
operating
system will l Any user - Use this option if you want the logout of any user to trigger
initiate a task the task.
l The following user - Use this option if you want only the logout of a
specific user account to trigger the task.

Start conditions Defines all conditions that must be met simultaneously for the task to
run.

Start conditions for antimalware scans are similar to the start conditions
for the Backup module that are described in "Start conditions".

You can define the following additional start conditions:

l Distribute task start time within a time window – This option

allows you to set the time frame for the task in order to avoid network
bottlenecks. You can specify the delay in hours or minutes. For
example, if the default start time is 10:00 AM and the delay is 60
minutes, then the task will start between 10:00 AM and 11:00 AM.
l If the machine is turned off, run missed tasks at the machine
startup
l Prevent the sleep or hibernate mode during task running – This
option is effective only for machines running Windows.
l If start conditions are not met, run the task anyway after –

294 © Acronis International GmbH, 2003-2024

 Field Description

Specify the period after which the task will run, regardless of the other
start conditions.

Note
Start conditions are not supported for Linux.

Extensions and exception rules

On the Extensions tab, you can define the list of file extensions that will be considered as important
during data discovery and checked whether they are protected. Use the following format for
defining extensions:

.html, .7z, .docx, .zip, .pptx, .xml

On the Exception rules tab, you can define which files and folders not to check on protection status
during data discovery.

l Hidden files and folders – if selected, hidden files and folders will be skipped during data
examination.
l System files and folders – if selected, system files and folders will be skipped during data
examination.

The Activities tab

The Activities tab provides an overview of activities from the past 90 days.

To filter activities on the dashboard

1. In the Device name field, specify the machine on which the activity is carried out.
2. From the Status dropdown list, select the status. For example, succeeded, failed, in progress,
canceled.
3. From the Remote actions dropdown list, select the action. For example, applying plan, deleting
backups, installing software updates.
4. In the Most recent field, set the period of activities. For example, the most recent activities, the
activities from the past 24 hours, or the activities during a specific period within the past 90 days.
5. If you are accessing the Activities tab as a partner administrator, you can filter the activities for a
specific customer that you manage.

To customize the view of the Activities tab, click the gear icon, and then select the columns that you
want to see. To see the activity progress in real time, select the Refresh automatically check box.

To cancel a running activity, click its name, and then, on the Details screen, click Cancel.

You can search the listed activities by the following criteria:

l Device name
This is the machine on which the activity is carried out.

295 © Acronis International GmbH, 2003-2024

l Started by
This is the account that started the activity.

Remote desktop activities can be filtered by the following properties:

l Creating plan
l Applying plan
l Revoking plan
l Deleting plan
l Remote connection
o Cloud remote desktop connection via RDP
o Cloud remote desktop connection via NEAR
o Cloud remote desktop connection via Apple Screen Sharing
o Remote desktop connection via web client
o Remote desktop connection via Quick Assist
o Direct remote desktop connection via RDP
o Direct remote desktop connection via Apple Screen Sharing
o File transfer
o File transfer via Quick Assist

l Remote action
o Shutting down a workload
o Restarting a workload
o Logging out remote user on the workload
o Emptying recycle bin for user on the workload
o Putting to sleep a workload

Cyber Protect Monitor

Cyber Protect Monitor shows information about the protection status of the machine on which
Agent for Windows or Agent for Mac is installed, and enables users to configure the backup
encryption and proxy server settings.

When Agent for File Sync & Share is installed on the machine, Cyber Protect Monitor provides access
to the File Sync & Share service. The File Sync & Share functionality is accessible after a mandatory
onboarding during which the users sign in to their own File Sync & Share account and select a
personal sync folder. For more information about Agent for File Sync & Share, see the Cyber Files
Cloud user guide.

Important
Cyber Protect Monitor is accessible to users who might not have administrative rights for the Cyber
Protection or the File Sync & Share service.

296 © Acronis International GmbH, 2003-2024

The table below summarizes the operations that are available for users without administrative
rights.

Installed agents Users can Users cannot

Agent for Windows l Apply the default protection plan to l Apply custom protection plans
or Agent for Mac their machines l Manage protection plans that are
l Check the protection status of their already applied
machines
l Receive Active Protection notifications
l Temporarily pause the backups of
their machines
l Configure the proxy server settings
l Change the backup encryption
settings

Warning!
Changing the encryption settings in
Cyber Protect Monitor overwrites the
settings in the protection plan and
affects all backups of the machine.
This operation can cause some
protection plans to fail. For more
information, see "Encryption" (p.
420).
There is no way to recover encrypted
backups if you lose or forget the
password.

Agent for Windows l Sync content between their local sync l Edit the file types that cannot be
and Agent for Sync folder and their File Sync & Share synced
and Share account
l Pause the sync operations
l Change the sync folder
Agent for Mac and l Check the file types that cannot be
Agent for Sync and
synced
Share

Configuring proxy server settings in Cyber Protect Monitor

You can configure the proxy server settings in Cyber Protect Monitor. The configuration will affect all
agents that are installed on the machine.

To configure the proxy server settings

1. Open Cyber Protect Monitor, and then click the gear icon in the top right corner.
2. Click Settings, and then click Proxy.
3. Enable the Use a proxy server switch, and then enter the proxy server address and port.

297 © Acronis International GmbH, 2003-2024

4. [If the proxy server access is password-protected] Enable the Password required switch, and
then enter the user name and password to access the proxy server.
5. Click Save.
The proxy server settings are saved in the http-proxy.yaml file.

Reports
Note
The availability of this feature depends on the service quotas that are enabled for your account.

A report about operations can include any set of dashboard widgets. All widgets show summary
information for the entire company.

Depending on the widget type, the report includes data for a time range or for the moment of
browsing or report generation. See "Reported data according to widget type" (p. 301).

All historical widgets show data for the same time range. You can change this range in the report
settings.

You can use default reports or create a custom report.

You can download a report or send it via email in XLSX (Excel) or PDF format.

The set of default reports depends on the Cyber Protection service edition that you have. The
default reports are listed below:

Report name Description

#CyberFit Score Shows the #CyberFit Score, based on the evaluation of security metrics and
by machine configurations for each machine, and recommendations for improvements.

Alerts Shows alerts that occurred during a specified time period.

Backup Shows the detailed information about detected threats in the backups.
scanning details

Daily activities Shows the summary information about activities performed during a specified time
period.

Data protection Shows the detailed information about the number, size, location, protection status of
map all important files on machines.

Detected Shows the details of the affected machines by number of blocked threats and the
threats healthy and vulnerable machines.

Discovered Shows all found machines in the organization network.

machines

Disk health Shows predictions when your HDD/SSD will break down and current disk status.
prediction

298 © Acronis International GmbH, 2003-2024

 Existing Shows the existing vulnerabilities for OS and applications in your organization. The
vulnerabilities report also displays the details of the affected machines in your network for every
product that is listed.

Software Shows information about the software that is installed on your company devices.
inventory

Hardware Shows information about the hardware that is available on your company devices.
inventory

Patch Shows the number of missing patches, installed patches, and applicable patches. You
management can drill down the reports to get the missing/installed patch information and details of
summary all the systems.

Summary Shows the summary information about the protected devices for a specified time
period.

Weekly Shows the summary information about activities performed during a specified time
activities period.

Remote Shows information about the remote desktop and file transfer sessions.
sessions

Actions with reports

To view a report, click its name.

To add a new report

1. In the Cyber Protect console, go to Reports.

2. Under the list of available reports, click Add report.
3. [To add a predefined report] Click the name of the predefined report.
4. [To add a custom report] Click Custom, and then add widgets to the report.
5. [Optional] Drag and drop the widgets to rearrange them.

To edit a report

1. In the Cyber Protect console, go to Reports.

2. In the list of reports, select the report that you want to edit.
You can do the following:
l Rename the report.
l Change the time range for all widgets in the report.
l Specify the report recipients and when the report will be send to them. The available formats
are PDF and XLSX.

To delete a report

1. In the Cyber Protect console, go to Reports.

2. In the list of reports, select the report that you want to delete.

299 © Acronis International GmbH, 2003-2024

3. Click the ellipsis icon (...), and then click Delete.
4. Confirm your choice by clicking Delete.

To schedule a report

1. In the Cyber Protect console, go to Reports.

2. In the list of reports, select the report that you want to schedule, and then click Settings.
3. Enable the Scheduled switch.
l Specify the email addresses of the recipients.
l Select the format of the report.

Note
You can export up to 1000 items in a PDF file and up to 10 000 items in a XLSX file. The
timestamps in the PDF and XLSX files use the local time of your machine.

l Select the language of the report.

l Configure the schedule.
4. Click Save.

To download a report

1. In the Cyber Protect console, go to Reports.

2. In the list of reports, select the report, and then click Download.
3. Select the format of the report.

To send a report

1. In the Cyber Protect console, go to Reports.

2. In the list of reports, select the report, and then click Send.
3. Specify the email addresses of the recipients.
4. Select the format of the report.
5. Click Send.

To export the report structure

1. In the Cyber Protect console, go to Reports.

2. In the list of reports, select the report.
3. Click ellipsis icon (...), and then click Export.

As a result, the report structure is saved on your machine as a JSON file.

To dump the report data

By using this option, you can export all data for a custom period, without filtering it, to a CSV file and
send the CSV file to an email recipient.

300 © Acronis International GmbH, 2003-2024

Note
You can export up to 150 000 items in a CSV file. The timestamps in the CSV file use Coordinated
Universal Time (UTC).

1. In the Cyber Protect console, go to Reports.

2. In the list of reports, select the report whose data you want to dump.
3. Click the ellipsis icon (...), and then click Dump data.
4. Specify the email addresses of the recipients.
5. In Time range, specify the custom period for which you want to dump data.

Note
Preparing CSV files for longer periods takes more time.

6. Click Send.

Reported data according to widget type

According to the data range that they display, widgets on the dashboard are two types:

l Widgets that display actual data at the moment of browsing or report generation.
l Widgets that display historical data.

When you configure a date range in the report settings to dump data for a certain period, the
selected time range will apply only for widgets that display historical data. For widgets that display
actual data at the moment of browsing, the time range parameter is not applicable.

The following table lists the available widgets and their data ranges.

Widget name Data displayed in widget and reports

#CyberFit Score by machine Actual

5 latest alerts Actual

Active alerts details Actual

Active alerts summary Actual

Activities Historical

Activity list Historical

Alerts history Historical

Attack tactics statistics Historical

Backup scanning details (threats) Historical

Backup status Historical - in columns Total runs and Number of successful

runs

301 © Acronis International GmbH, 2003-2024

 Actual - in all other columns

Blocked URLs Actual

Cloud applications Actual

Cyber protection Actual

Data protection map Historical

Devices Actual

Discovered machines Actual

Disk health overview Actual

Disk health status by physical Actual

devices

Existing vulnerabilities Historical

Hardware changes Historical

Hardware details Actual

Hardware inventory Actual

Historical alerts summary Historical

Incident severity history Historical

Locations summary Actual

Missing updates by categories Actual

Not protected Actual

Patch installation history Historical

Patch installation status Historical

Patch installation summary Historical

Protection status Actual

Recently affected Historical

Remote sessions Historical

Security incident burndown Historical

Security incident MTTR Historical

Software inventory Actual

Software overview Historical

302 © Acronis International GmbH, 2003-2024

Threat status Actual

Vulnerable machines Actual

Workload network status Actual

303 © Acronis International GmbH, 2003-2024

Managing workloads in the Cyber Protect
console
This section describes how to manage your workloads in the Cyber Protect console.

The Cyber Protect console

In the Cyber Protect console, you can manage workloads and plans, change the protection settings,
configure reports, or check the backup storage.

The Cyber Protect console provides access to additional services or features, such as File Sync &
Share or Antivirus and Antimalware protection, Patch management, Device control, and
Vulnerability assessment. The type and number of these services and features vary according to
your Cyber Protection license.

To check the dashboard with the most important information about your protection, go to
Monitoring > Overview.

Depending on your access permissions, you can manage the protection for one or multiple
customer tenants or units in a tenant. To switch the hierarchy level, use the drop-down list in the
navigation menu. Only the levels to which you have access are shown. To go to the management
portal, click Manage.

The Devices section is available in simple and table view. To switch between them, click the
corresponding icon in the top right corner.

The simple view shows only a few workloads.

304 © Acronis International GmbH, 2003-2024

The table view is enabled automatically when the number of workloads becomes larger.

Both views provide access to the same features and operations. This document describes access to
operations from the table view.

When a workload goes online or offline, it takes some time for its status to change in the Cyber
Protect console. The workload status is checked every minute. If the agent installed on the
corresponding machine is not transferring data, and there is no answer to five consecutive checks,
the workload is shown as offline. The workload is shown as back online when it answers to a status
check or starts transferring data.

What's new in the Cyber Protect console

When new features of Cyber Protect Cloud are available, you see a pop-up window with a brief
description of these features upon logging in to the Cyber Protect console.

You can also view the description of the new features by clicking the What's new link in the bottom-
left corner of the main Cyber Protect console window.

If there are no new features, the What's new link is not displayed.

305 © Acronis International GmbH, 2003-2024

Using the Cyber Protect console as a partner administrator
As a partner administrator, you can use the Cyber Protect console at the partner tenant (All
customers) level or at the customer tenant level.

Partner tenant (All customers) level

On the partner tenant (All customers) level, you can perform the following actions:

l Manage scripting plans for workloads from all your managed customer tenants.
You can apply the same scripting plan to workloads from different customers, and create device
groups with workloads from different customers. To learn how to create a static or a dynamic
device group on the partner level, see "Creating a static device group on the partner level" (p.
308) and "Creating a dynamic device group on the partner level" (p. 309). For more information
about the scripts and scripting plans, see "Cyber Scripting" (p. 225).
l Create monitoring plans for workloads from all your managed customer tenants.
l Create remote management plans for workloads from all your managed customer tenants.
l View and manage Endpoint Detection and Response (EDR) incidents for all customer tenants in
one incident management interface, rather than access each individual customer's incident
screen.
l Perform autodiscovery of machines for all your managed customer tenants.

Customer tenant level

On this level, you have the same rights as the company administrator on whose behalf you act.

Selecting a tenant level

You can select the tenant level on which to work in the Cyber Protect console.

Prerequisites
l You have rights to access both the Cyber Protect console and the management portal.
l You can manage more than one tenant or unit.

To select a tenant level in the Cyber Protect console

1. In the navigation menu in the left, click the arrow next to the customer tenant name.
2. Select one of the following options:
l To work on the partner level, select All customers.

306 © Acronis International GmbH, 2003-2024

l To work on the customer or unit level, select the name of that customer or unit.

Partner tenant level in the Cyber Protect console

When you use the Cyber Protect console on the partner tenant (All customers) level, a customized
view is available.

The Alerts and Activities tabs provide additional partner-related filters, while the Devices and the
Management tabs provide access only to the features or objects that are accessible to partner
administrators.

Alerts tab
Here, you can see the alerts from all your managed customers, search them, and filter them
according to the following criteria:

l Device
l Customer
l Plan

You can select multiple items for each of these criteria.

Activities tab
Here, you can see the activities from all the tenants that you manage or the activities in a specific
customer tenant.

307 © Acronis International GmbH, 2003-2024

You can filter the activities by customer, status, time, and type.

The following types of activities are automatically pre-selected on this level:

l Applying plan
l Creating the protection plan
l Protection plan
l Revoking plan
l Scripting

Devices tab
In the Machines with agents tab, you can see all workloads from your managed customer tenants,
and you can select workloads from one or more tenants. You can also create device groups that
include workloads from different tenants.

Important
When you work on the partner (All customers) level, you can perform a limited number of
operations with devices. For example, you cannot perform any of the following operations:

l See and manage existing protection plans on customer devices.

l Create new protection plans.
l Recover backups.
l Use Disaster Recovery.
l Access the Cyber Protection Desktop features.

To perform any of these operations, work on the customer level.

Software management tab

If the software inventory scanning is enabled for customer workloads, you can see the software
scanning results.

Viewing the workloads of specific customers

As a partner administrator, you can view the workloads belonging to the customer tenants that you
manage.

To view the workloads of a specific customer

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. In the tree, click Machines with agents to expand the list.
3. Click the name of the customer whose workloads you want to view and manage.

Creating a static device group on the partner level

You can create static device groups on the partner (All devices) level.

To create a static device group on the partner level

308 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Devices > Machines with agents.
2. Click the gear icon next to Machines with agents, and then click New group.

3. Specify the group name.

4. [Optional] Add a description.
5. Click OK.

Creating a dynamic device group on the partner level

You can create dynamic device groups on the partner (All devices) level.

To create a dynamic device group on the partner level

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. In the tree, click Machines with agents to expand the list.
3. Click All.
4. In the search field, specify the criteria according to which you want to create a dynamic device
group, and then click Search.
To learn more about the available search criteria, see "Search attributes for non-cloud-to-cloud
workloads" (p. 331) and "Search attributes for cloud-to-cloud workloads" (p. 330).
5. Click Save as, and then specify the group name.

6. [Optional] Add a description.

7. Click OK.

Performing autodiscovery of machines at the partner tenant level

You can perform autodiscovery of machines at the partner tenant (All customes) level.

Prerequisites
There is at least one machine with an installed protection agent in your customer's local network or
Active directory domain.

309 © Acronis International GmbH, 2003-2024

Important
Only agents that are installed on Windows machines can be discovery agents. If there are no
discovery agents in your customer's environments, you will not be able to use the Multiple devices
option in the Add devices panel.

Autodiscovery is not supported for adding Domain Controllers, due to additional permissions
required for the agent service to run.

Remote installation of agents is supported only for machines running Windows (Windows XP is not
supported). For remote installation on a machine running Windows Server 2012 R2, Windows
update KB2999226 must be installed.

To perform autodiscovery of machines at the partner tenant level

1. In the Cyber Protect console, select All Customers.

2. Go to Devices> All devices.
3. Click Add.
4. In Multiple devices, click Windows-only. The discovery wizard opens.
5. Select a customer tenant, and then select the discovery agent that will perform the scan to detect
machines.
6. Select the discovery method:
l Search Active Directory. Ensure that the machine with the discovery agent is the Active
Directory domain member.
l Scan local network. If the selected discovery agent could not find any machines, select
another discovery agent.
l Specify manually or import from file. Manually define the machines to be added or import
them from a text file.
7. [If the Active Directory discovery method is selected] Select how to search for machines:
l In organizational unit list. Select the group of machines to be added.
l By LDAP dialect query. Use the LDAP dialect query to select the machines. Search base
defines where to search, and in the Filter you can specify criteria for machine selection.

310 © Acronis International GmbH, 2003-2024

8. Depending on the discovery method that you selected, perform one of the following actions:

Discovery Action
method

Search Active In the list of discovered machines, select the machines that you want to add.
Directory

Scan local In the list of discovered machines, select the machines that you want to add.
network

Specify Specify the machine IP addresses or hostnames, or import the machine list from a
manually or text file. The file must contain IP addresses/hostnames, one per line. Here is an
import from a example of a file:
file
156.85.34.10
156.85.53.32
156.85.53.12
EN-L00000100
EN-L00000101

After adding machine addresses manually or importing from a file, the agent tries
to ping the added machines and define their availability.

9. Select the actions that must be performed after the discovery:

Option Description

Install agents You can select which components to install on the machines by clicking Select
and register components. For more details, see "Selecting components for installation" (p. 128).
machines

Logon This setting is available on the Select components screen.

account for The setting defines the account under which the services will run.
the agent You can select one of the following options:
service l Use Service User Accounts (default for the agent service)
Service User Accounts are Windows system accounts that are used to run
services. The advantage of this setting is that the domain security policies do not
affect these accounts' user rights. By default, the agent runs under the Local
System account.
l Create a new account
The account name will be Agent User for the agent.
l Use the following account
If you install the agent on a domain controller, the system prompts you to specify
existing accounts (or the same account) for the agent. For security reasons, the
system does not automatically create new accounts on a domain controller.
If you chose the Create a new account or Use the following account option,
ensure that the domain security policies do not affect the related accounts' rights. If
an account is deprived of the user rights assigned during the installation, the
component might work incorrectly or not work at all.

311 © Acronis International GmbH, 2003-2024

 Option Description

Register Use this option if the agent is already installed on the machines, and you only need
machines to register them in Cyber Protection. If no agent is found on the machines, they will
with installed be added as Unmanaged machines.
agents

Add as If you select this option, the agent will not be installed on the machines. You will be
unmanaged able to view them in the console and install or register the agent later.
machines

Restart the This option appears when Install agents and register machines is selected.
machine, if If you select this option, the machine will be restarted as many times as required to
required complete the installation.
Restart of the machine may be required in one of the following cases:
l Installation of prerequisites is completed, and restart is required to continue the
installation.
l Installation is completed but restart is required, as some files are locked during
installation.
l Installation is completed, but restart is required for other previously installed
software.

Do not This option appears when Restart the machine if required is selected.
restart if the If you select this option, the machine will not be automatically restarted if the user is
user logged logged in to the system. For example, if a user is working while installation requires
in restart, the system will not be restarted.
If the prerequisites were installed but the machine was not restarted because a user
was logged in, to complete the installation you must restart the machine, and then
start the installation again.
If the agent was installed but then the machine was not restarted, you must restart
the machine.

User where [If there are units in your organization] Select the user account of unit or subordinate
to register units under which you want to register the machines.
the machines [When performing autodiscovery on the partner tenant level] In the list of customer
tenants that you manage, expand the tree structure, and then select the user
account under which you want to register the machines.
[When performing autodiscovery as a customer administrator] If you selected Install
agents and register machines or Register machines with installed agents, there
is also an option to apply the protection plan to the machines. If you have several
protection plans, you can select which one to use.

10. Specify the credentials of the user with administrator rights for all of the machines.

312 © Acronis International GmbH, 2003-2024

 Important
Remote installation of agents works without any preparations only if you specify the credentials
of the built-in administrator account (the first account created when the operating system is
installed). If you want to define some custom administrator credentials, you must do additional
preparations as described in "Prerequisites" (p. 309).

11. The system checks connectivity to all of the machines. If the connection to some of the machines
fails, you can change the credentials for these machines.

After the discovery of machines is initiated, you can see the corresponding task in Monitoring>
Activities > Discovering machines activity.

Multitenancy support
The Cyber Protection service supports multitenancy, which implies administration on the following
levels:

l [For service providers] Partner tenant (All customers) level

This level is only available for partner administrators who manage customer tenants.
l Customer tenant level
This level is managed by company administrators.
Partner administrators can also work on this level in the customer tenants that they manage. On
this level, partner administrators have the same rights as the customer administrators on whose
behalf they act.
l Unit level
This level is managed by unit administrators and by company administrators from the parent
customer tenant.
Partner administrators who manage the parent customer tenant can also access the unit level.
On this level, they have the same rights as the customer administrators on whose behalf they act.

Administrators can manage objects in their own tenant and in its child tenants. They cannot see or
access objects on an upper administration level, if any.

For example, company administrators can manage protection plans both on the customer tenant
level and on the unit level. Unit administrators can manage only their own protection plans on the
unit level. They cannot manage any protection plans on the customer tenant level and cannot
manage the protection plans that are created by the customer administrator on the unit level.

Also, partner administrators can create and apply scripting plans in the customer tenants that they
manage. The company administrators in such tenants have only read-only access to the scripting
plans that are applied to their workloads by a partner administrator. However, customer
administrators can create and apply their own scripting or protection plans.

313 © Acronis International GmbH, 2003-2024

Workloads
A workload is any type of protected resource − for example, a physical machine, a virtual machine, a
mailbox, or a database instance. In the Cyber Protect console, the workload is shown as an object to
which you can apply a plan (protection plan, backup plan, or scripting plan).

Some workloads require installing a protection agent or deploying a virtual appliance. You can
install agents by using the graphical user interface or by using the command-line interface
(unattended installation). You can use the unattended installation to automate the installation
procedure. For more information about how to install protection agents, see "Installing and
deploying Cyber Protection agents" (p. 56).

A virtual appliance (VA) is a ready-made virtual machine that contains a protection agent. With a
virtual appliance, you can back up other virtual machines in the same environment without
installing a protection agent on them (agentless backup). The virtual appliances are available in
hypervisor-specific formats, such as .ovf, .ova, or .qcow. For more information about which
virtualization platforms support agentless backup, see "Supported virtualization platforms" (p. 31).

Important
Agents must be online at least once every 30 days. Otherwise, their plans will be revoked and the
workloads will become unprotected.

The table below summarizes the workload types and their respective agents.

Workload Agent Examples

type
(non-exhaustive
list)

Physical A protection agent is installed on every protected machine. Workstation

machines
Laptop

Server

Virtual Depending on the virtualization platform, the following backup VMware virtual
machines methods might be available: machine

l Agent-based backup − A protection agent is installed on every Hyper-V virtual

protected machine. machine
l Agentless backup − A protection agent is installed only on the
Kernel-based
hypervisor host, on a dedicated virtual machine, or is deployed
virtual machine
as a virtual appliance. This agent backs up all virtual machines in
(KVM) managed by
the environment.
oVirt

Microsoft 365 These workloads are backed up by a cloud agent for which no Microsoft 365
Business installation is required. mailbox
workloads
To use the cloud agent, you need to add your Microsoft 365 or Microsoft 365

314 © Acronis International GmbH, 2003-2024

 Workload Agent Examples
type
(non-exhaustive
list)

Google Google Workspace organization to the Cyber Protect console. OneDrive

Workspace
Additionally, a local Agent for Office 365 is available. It requires Microsoft Teams
workloads
installation and can only be used to back up Exchange Online
SharePoint site
mailboxes. For more information about the differences between the
local and the cloud agent, see "Protecting Microsoft 365 data" (p. Google mailbox
573).
Google Drive
.

Applications The data of specific applications is backed up by dedicated agents, SQL Server
such as Agent for SQL, Agent for Exchange, Agent for databases
MySQL/MariaDB, or Agent for Active Directory.
MySQL/MariaDB
databases

Oracle databases

Active Directory

Mobile A mobile app is installed on the protected devices. Android or iOS

devices devices

Websites The websites are backed up by a cloud agent for which no Websites accessed
installation is required. via the SFTP or
SSH protocols

For more information about which agent you need and where to install it, see "Which agent do I
need?" (p. 58)

Adding workloads to the Cyber Protect console

To start protecting your workloads, add them to the Cyber Protect console first.

Note
The workload types that you can add depend on the service quotas for your account. If a specific
workload type is missing, it is grayed out in the Add devices pane.

A partner administrator can enable the required service quotas in the Management portal. For
details, refer to "Information for partner administrators" (p. 319).

To add a workload

1. Log in to the Cyber Protect console.

2. Go to Devices > All devices, and then click Add.
The Add devices pane opens on the right.
3. Select the release channel.

315 © Acronis International GmbH, 2003-2024

4. Click the workload type that you want to add, and then follow the instructions for the specific
workload that you selected.

The following table summarizes the workload types and required actions.

Workloads to add Required action Procedure to follow

Multiple Windows Perform autodiscovery in your "Performing autodiscovery and

machines environment. manual discovery" (p. 123)

To perform autodiscovery, you need at

least one machine with an installed
protection agent in your local network or
Active Directory domain. This agent is
used as a discovery agent.

Windows workstations Install Agent for Windows. "Installing protection agents in

Windows" (p. 73)
Windows servers
or

"Unattended installation or
uninstallation in Windows" (p. 82)

macOS workstations Install Agent for macOS. "Installing protection agents in

macOS" (p. 78)

or

"Unattended installation and

uninstallation in macOS" (p. 106)

Linux servers Install Agent for Linux. "Installing protection agents in

Linux" (p. 75)

or

"Unattended installation or
uninstallation in Linux" (p. 100)

Mobile devices Install the mobile app. "Protecting mobile devices" (p. 566)

(iOS, Android)

Cloud-to-cloud workloads

Microsoft 365 Business Add your Microsoft 365 organization to "Protecting Microsoft 365 data" (p.
the Cyber Protect console and use the 573)
cloud agent to protect Exchange online
mailboxes, OneDrive files, Microsoft
Teams, and SharePoint sites.

Alternatively, you can install the local

Agent for Office 365. It only provides
backup of Exchange Online mailboxes.

316 © Acronis International GmbH, 2003-2024

 Workloads to add Required action Procedure to follow

For more information on the differences

between the local and the cloud agent,
refer to "Protecting Microsoft 365 data"
(p. 573).

Google Workspace Add your Google Workspace "Protecting Google Workspace

organization to the Cyber Protect data" (p. 613)
console and use the cloud agent to
protect Gmail mailboxes and Google
Drive files.

Virtual machines

VMware ESXi Deploy Agent for VMware (Virtual "Deploying Agent for VMware
Appliance) in your environment. (Virtual Appliance)" (p. 131)

Install Agent for VMware (Windows). "Installing protection agents in

Windows" (p. 73)
or

"Unattended installation or
uninstallation in Windows" (p. 82)

Virtuozzo Hybrid Deploy Agent for Virtuozzo Hybrid "Deploying Agent for Virtuozzo
infrastructure Infrastructure Hybrid Infrastructure (Virtual
(Virtual appliance) in your environment. Appliance)" (p. 140)

Hyper-V Install Agent for Hyper-V. "Installing protection agents in

Windows" (p. 73)

or

"Unattended installation or
uninstallation in Windows" (p. 82)

Virtuozzo Install Agent for Virtuozzo. "Installing protection agents in

Linux" (p. 75)

or

"Unattended installation or
uninstallation in Linux" (p. 100)

KVM Install Agent for Windows. "Installing protection agents in

Windows" (p. 73)

or

"Unattended installation or
uninstallation in Windows" (p. 82)

Install Agent for Linux. "Installing protection agents in

317 © Acronis International GmbH, 2003-2024

 Workloads to add Required action Procedure to follow

Linux" (p. 75)

or

"Unattended installation or
uninstallation in Linux" (p. 100)

Red Hat Virtualization Deploy Agent for oVirt (Virtual Appliance) "Deploying Agent for oVirt (Virtual
(oVirt) in your environment. Appliance)" (p. 148)

Citrix XenServer Install Agent for Windows. "Installing protection agents in

Windows" (p. 73)

or

"Unattended installation or
uninstallation in Windows" (p. 82)

Install Agent for Linux. "Installing protection agents in

Linux" (p. 75)

or

"Unattended installation or
uninstallation in Linux" (p. 100)

Nutanix AHV Install Agent for Windows. "Installing protection agents in

Windows" (p. 73)

or

"Unattended installation or
uninstallation in Windows" (p. 82)

Install Agent for Linux. "Installing protection agents in

Linux" (p. 75)

or

"Unattended installation or
uninstallation in Linux" (p. 100)

Oracle VM Install Agent for Windows. "Installing protection agents in

Windows" (p. 73)

or

"Unattended installation or
uninstallation in Windows" (p. 82)

Install Agent for Linux. "Installing protection agents in

Linux" (p. 75)
or

"Unattended installation or

318 © Acronis International GmbH, 2003-2024

 Workloads to add Required action Procedure to follow

uninstallation in Linux" (p. 100)

Scale Computing HC3 Deploy Agent for Scale Computing HC3 "Deploying Agent for Scale
(Virtual Appliance) in your environment. Computing HC3 (Virtual Appliance)"
(p. 135)

Network-attached storage

Synology Deploy Agent for Synology (Virtual "Deploying Agent for Synology" (p.
Appliance) in your environment. 153)

Applications

Microsoft SQL Server Install Agent for SQL. "Installing protection agents in
Windows" (p. 73)
Microsoft Exchange Install Agent for Exchange.
Server or

Microsoft Active Install Agent for Active Directory. "Unattended installation or

Directory uninstallation in Windows" (p. 82)

Oracle Database Install Agent for Oracle. "Protecting Oracle Database" (p.
637)

Website Configure the connection to the website. "Protecting websites and hosting
servers" (p. 643)

For more information about the available protection agents and where to install them, refer to
"Which agent do I need?" (p. 58)

Information for partner administrators

l A workload type might be missing in the Add devices pane if a required service quota is not
enabled in the Management portal. For more information about which service quotas are
required for which workloads, refer to Enabling or disabling offering items in the Partner
administrator guide.
l As a partner administrator, you cannot add workloads on the All customers level. To add a

319 © Acronis International GmbH, 2003-2024

workload, select an individual customer tenant.

Removing workloads from the Cyber Protect console

You can remove from the Cyber Protect console the workloads that you do not need to protect
anymore. The procedure depends on the workload type.

Alternatively, you can uninstall the agent on the protected workload. When you uninstall an agent,
the protected workload is automatically removed from the Cyber Protect console.

Important
When you remove a workload from the Cyber Protect console, all plans that are applied to that
workload are revoked. Removing a workload does not delete any plans or backups, and does not
uninstall the protection agent.

The following table summarizes the workload types and required actions.

Workloads to Required actions Procedure to follow

remove

Physical and virtual machines

Physical or 1. Remove the "To remove a workload from the Cyber Protect console" (p. 322)
virtual workload from
(Workload with protection agent)
machines on the Cyber
which a Protect console.
protection 2. [Optional]
agent is Uninstall the
installed protection
agent.

320 © Acronis International GmbH, 2003-2024

 Workloads to Required actions Procedure to follow
remove

Virtual 1. In the Cyber "To remove a workload from the Cyber Protect console" (p. 322)
machines that Protect console,
(Workload without a protection agent)
are backed up remove the
on the machine on
hypervisor level which the
(agentless protection agent
backup) is installed. All
virtual machines
that are backed
up by this agent
will be
automatically
removed from
the console.
2. [Optional]
Uninstall the
protection
agent.

Cloud-to-cloud workloads

Microsoft 365 Delete the Microsoft "To remove a workload from the Cyber Protect console" (p. 322)
Business 365 or the Google
(Cloud-to-cloud workload)
workloads Workspace
organization from
Google
the Cyber Protect
Workspace
console. All
workloads
resources in that
organization will be
automatically
removed from the
console.

Mobile devices

Android devices 1. Remove the "To remove a workload from the Cyber Protect console" (p. 322)
mobile device
iOS devices (Mobile device)
from the Cyber
Protect console.
2. [Optional] On
the mobile
device, uninstall
the app.

Network-attached storage

321 © Acronis International GmbH, 2003-2024

 Workloads to Required actions Procedure to follow
remove

Synology 1. Remove the "To remove a workload from the Cyber Protect console" (p. 322)
workload from
(Workload with a protection agent)
the Cyber
Protect console.
2. [Optional]
Uninstall the
protection
agent.

Applications

Microsoft SQL 1. In the Cyber "To remove a workload from the Cyber Protect console" (p. 322)
Server Protect console,
(Workload without a protection agent)
remove the
Microsoft
machine on
Exchange
which the
Server
protection agent
Microsoft Active is installed. The
Directory objects that are
backed up by
Oracle
this agent will be
Database
automatically
removed from
the console.
2. [Optional]
Uninstall the
protection
agent.

Websites Remove the website "To remove a workload from the Cyber Protect console" (p. 322)
from the Cyber
(Website)
Protect console.

To remove a workload from the Cyber Protect console

Workload with a protection agent

You can remove this type of workload directly.

1. In the Cyber Protect console, navigate to Devices > All devices.

2. Select the check box next to one or more workloads that you want to remove.
3. In the Actions pane, click Delete.
4. Confirm your choice by clicking Delete.
5. [Optional] Uninstall the agent as described in "Uninstalling agents" (p. 174).

Workload without a protection agent

322 © Acronis International GmbH, 2003-2024

To remove this type of workload, you need to remove the machine on which the protection agent is
installed.

1. In the Cyber Protect console, go to Devices > All devices.

2. In the upper right corner, click the gear icon, and then select the Agent check box.

The Agent column appears.

3. In the Agent column, check the name of the machine where the protection agent is installed.
4. In the Cyber Protect console, select the check box next to the machine on which the protection
agent is installed.
5. In the Actions pane, click Delete.
6. Confirm your choice by clicking Delete.
7. [Optional] Uninstall the agent as described in "Uninstalling agents" (p. 174).

Cloud-to-cloud workload

To remove workloads that are backed up by the cloud agent, delete your Microsoft 365 or Google
Workspace organization from the Cyber Protect console.

1. In the Cyber Protect console, navigate to Devices > Microsoft 365 or Devices > Google
Workspace.
2. Click the name of your Microsoft 365 or Google Workspace organization.
3. In the Actions pane, click Delete group.
4. Click Delete to confirm your action.

Mobile device

1. In the Cyber Protect console, navigate to Devices > All devices.

2. Select the check box next to the workload that you want to delete.
3. In the Actions pane, click Delete.
4. Confirm your choice by clicking Delete.
5. [Optional] Uninstall the app from the mobile device.

Website

1. In the Cyber Protect console, navigate to Devices > All devices.

2. Select the check box next to the workload that you want to delete.

323 © Acronis International GmbH, 2003-2024

3. In the Actions pane, click Delete.
4. Confirm your choice by clicking Delete.

Device groups
With device groups, you can protect multiple similar workloads with a group plan. The plan is
applied to the group as a whole and cannot be revoked from a member of the group.

A workload can be a member of more than one group. A workload that is included in a device group
can still be protected by individual plans.

You can add only workloads of the same type to a device group. For example, under Hyper-V, you
can only create groups of Hyper-V virtual machines. Under Machines with agents, you can only
create groups of machines with installed agents.

You cannot create device groups within any All-type group, such as the root group All devices, or
built-in groups like Machines with agents > All, Microsoft 365 > your organization > Users > All
users.

Built-in groups and custom groups

Built-in groups
After you register a workload in the Cyber Protect console, the workload appears in one of the built-
in root groups on the Devices tab, such as Machines with agents, Microsoft 365, or Hyper-V.

All registered non-cloud-to-cloud workloads are also listed in the All devices root group. A separate
built-in root group named after your tenant contains all non-cloud-to-cloud workloads and all units
in this tenant.

You cannot delete or edit the root groups, or apply plans to them.

Some of the root groups contain one or more levels of built-in subgroups, for example, Machines
with agents > All, Microsoft 365 > your organization > Teams > All teams, Google Workspace >
your organization > Shared Drives > All Shared Drives.

You cannot edit or delete built-in subgroups.

Custom groups
Protecting all workloads in a built-in group might not be convenient, because there might be
workloads that need different protection settings or a different protection schedule.

In some of the root groups, for example in Machines with agents, Microsoft 365, or Google
Workspace, you can create custom subgroups. These subgroups can be static or dynamic.

You can edit, rename, or delete any custom group.

324 © Acronis International GmbH, 2003-2024

Static groups and dynamic groups
You can create the following type of custom groups:

l Static
l Dynamic

Static groups
Static groups contain manually added workloads.

The content of a static group changes only when you explicitly add or remove a workload.

Example: You create a static group for the accounting department in your company, and then
manually add the accountants' machines to this group. When you apply a group plan, the machines
in that group become protected. If a new accountant is hired, you will have to add the accountant's
machine to the static group manually.

Dynamic groups
Dynamic groups contain workloads that match specific criteria. You define these criteria in advance
by creating a search query that includes attributes (for example, osType), their values (for example,
Windows), and search operators (for example, IN).

Thus, you can create a dynamic group for all machines whose operating system is Windows or a
dynamic group that contains all users in your Microsoft 365 organization whose email addresses
begin with john.

All workloads that have the required attributes and values are automatically added to the group and
any workload that loses a required attribute or value is automatically removed from the group.

Example 1: The host names of the machines that belong to the accounting department contain the
word accounting. You search for the machines whose names contain accounting, and then you save
the search results as a dynamic group. Then, you apply a protection plan to the group. If a new
accountant is hired, the accountant's machine will have accounting in its name and will be
automatically added to the dynamic group as soon as you register that machine in the Cyber Protect
console.

Example 2: The accounting department forms a separate Active Directory organizational unit (OU).
You specify the accounting OU as a required attribute, and then you save the search results as a
dynamic group. Then, you apply a protection plan to the group. If a new accountant is hired, the
accountant's machine will be added to the dynamic group as soon as it is added to the Active
Directory OU and is registered in the Cyber Protect console (regardless of which comes first).

Cloud-to-cloud groups and non-cloud-to-cloud groups

Cloud-to-cloud groups contain Microsoft 365 or Google Workspace workloads that are backed up by
a cloud agent.

325 © Acronis International GmbH, 2003-2024

Non-cloud-to-cloud groups contain all other workload types.

Supported plans for device groups

The following table summarizes the plans that you can apply to a device group.

Group Available plans Plan location

Cloud-to-cloud workloads Backup plan Management > Cloud applications

(Microsoft 365 and Google Workspace backup
workloads)

Protection plan Management > Protection plans

Remote Management > Remote

Non-cloud-to-cloud workloads
management plan management plans

Scripting plan Management > Scripting plans

Cloud resources, such as Microsoft 365 or Google Workspace users, OneDrive and Google Drive
shares, Microsoft Teams, or Azure AD groups are synchronized to the Cyber Protect console right
after you add a Microsoft 365 or Google Workspace organization to the console. Any further
changes in an organization are synchronized once a day.

If you need to synchronize a change immediately, in the Cyber Protect console, navigate to Devices
> Microsoft 365 or Devices > Google Workspace respectively, select the required organization,
and then click Refresh.

Creating a static group

You can create an empty static group and add workloads to it.

Alternatively, you can select workloads and create a new static group from your selection.

You cannot create device groups within any All-type group, such as the root group All devices, or
built-in groups like Machines with agents > All, Microsoft 365 > your organization > Users > All
users.

To create a static group

In the main window

1. Click Devices, and then select the root group that contains the workloads for which you want to
create a static group.
2. [Optional] To create a nested group, navigate to an existing static group.

Note
Creating nested static groups is not available for cloud-to-cloud workloads.

3. Click + New static group below the group tree or click New static group in the Actions pane.

326 © Acronis International GmbH, 2003-2024

4. Specify a name for the new group.
5. [Optional] Add a comment for the group.
6. Click OK.

In the group tree

1. Click Devices, and then select the root group that contains the workloads for which you want to
create a static group.
2. Click the gear icon next to the name of the group in which you want to create a new static group.

Note
Creating nested static groups is not available for cloud-to-cloud workloads.

3. Click New static group.

4. Specify a name for the new group.
5. [Optional] Add a comment for the group.
6. Click OK.

From selection

1. Click Devices, and then select the root group that contains the workloads for which you want to
create a static group.

Note
You cannot create device groups within any All-type group, such as the root group All devices,
or built-in groups like Machines with agents > All, Microsoft 365 > your organization > Users >
All users.

2. Select the check boxes next to workloads for which you want to create a new group, and then
click Add to group.
3. In the folder tree, select the parent level for the new group, and then click New static group.

Note
Creating nested static groups is not available for cloud-to-cloud workloads.

4. Specify a name for the new group.

5. [Optional] Add a comment for the group.
6. Click OK.
The new group appears in the folder tree.
7. Click Done.

Adding workloads to a static group

You can select the target group first, and then add workloads to it.

Alternatively, you can select the workloads first, and then add them to a group.

To add workloads to a static group

327 © Acronis International GmbH, 2003-2024

Selecting the target group first

1. Click Devices, and then navigate to your target group.

2. Select the target group, and then click Add devices.
3. In the folder tree, select the group that contains the required workloads.
4. Select the check boxes next to the workloads that you want to add, and then click Add.

Selecting the workloads first

1. Click Devices, and then select the root group that contains the required workloads.
2. Select the check boxes next to the workloads that you want to add, and then click Add to group.
3. In the folder tree, select the target group, and then click Done.

Creating a dynamic group

You create a dynamic group by searching for workloads that have specific attributes whose values
you define in a search query. Then you save the search results as a dynamic group.

The attributes that are supported for searching and creating dynamic groups differ for cloud-to-
cloud workloads and non-cloud-to-cloud workloads. For more information on supported attributes,
see "Search attributes for non-cloud-to-cloud workloads" (p. 331) and "Search attributes for cloud-
to-cloud workloads" (p. 330).

Dynamic groups are created in their respective root groups. Nested dynamic groups are not
supported.

You cannot create device groups within any All-type group, such as the root group All devices, or
built-in groups like Machines with agents > All, Microsoft 365 > your organization > Users > All
users.

To create a dynamic group

Non-cloud-to-cloud workloads

1. Click Devices, and then select the group that contains the workloads for which you want to
create a new dynamic group.
2. Search for workloads by using the supported search attributes and operators.
You can use multiple attributes and operators in a single query. For more information about the
supported attributes, see "Search attributes for non-cloud-to-cloud workloads" (p. 331).
3. Click Save as next to the search field.

328 © Acronis International GmbH, 2003-2024

 Note
The Save as button is not available when you are not allowed to create a dynamic group on a
specific level.For example, in the root group Devices > All devices.
Select another level (for example, Devices > Machines with agents > All), and then repeat the
steps above. With this search, you can create a dynamic group within Machines with agents,
and not within Machines with agents > All.

4. Specify a name for the new group.

5. [Optional] In the Comment field, add a description for the new group.
6. Click OK.

Cloud-to-cloud workloads

1. Click Devices, and then select Microsoft 365 or Google Workspace.

2. Select the group that contains the workloads for which you want to create a new dynamic group.
For example, Users > All users.
3. Search for workloads by using the supported search attributes and operators or by selecting
Microsoft 365 users from a specific Active Directory group.
You can use multiple attributes and operators in a single query. For more information about the
supported attributes, see "Search attributes for cloud-to-cloud workloads" (p. 330).

4. [Only for Microsoft 365 > Users] To select users from a specific Active Directory group, do the
following:
a. Navigate to Users > All users.
b. Click Select an Azure AD Group.
A list of the Active Directory groups in your organization opens.
In this list, you can search for a specific group or sort the groups by name or email.
c. Select the Active Directory group that you want, and then click Add.

329 © Acronis International GmbH, 2003-2024

 d. [Optional] To include or exclude specific users from the selected Active Directory group,
create a search query by using the supported search attributes and operators.
You can use multiple attributes and operators in a single query. For more information about
the supported attributes, see "Search attributes for cloud-to-cloud workloads" (p. 330).

5. Click Save as next to the search field.

Note
The Save as button is not available when you are not allowed to create a dynamic group on a
specific level. For example, in Microsoft 365 > your organization > Users.
Select another level (for example, Microsoft 365 > your organization > Users > All), and then
repeat the steps above. With this search, you can create a dynamic group within Microsoft 365
> your organization > Users >, and not within Users > All.

6. Specify a name for the new group.

7. [Optional] In the Comment field, add a description for the new group.
8. Click OK.

Search attributes for cloud-to-cloud workloads

The following table summarizes the attributes that you can use in your search queries for Microsoft
365 and Google Workspace workloads.

To see which attributes you can use in search queries for other types of workloads, refer to "Search
attributes for non-cloud-to-cloud workloads" (p. 331).

Attribute Meaning Can be used Search query examples Supported

in for group
creation

name Display name of a All cloud-to- name = 'My Name' Yes

Microsoft 365 or Google cloud
name LIKE '*nam*'
Workspace workload resources

email Email address for a Microsoft 365 email = 'my_group_ Yes

Microsoft 365 user or > Groups [email protected]'
group, or a Google
Microsoft 365 email LIKE '*@company*'
Workspace user
> Users
email NOT LIKE

330 © Acronis International GmbH, 2003-2024

 Attribute Meaning Can be used Search query examples Supported
in for group
creation

Google '*enterprise.com'
Workspace >
Users

siteName Name of a site that is Microsoft 365 siteName = 'my_site' Yes

associated with a > Groups
siteName LIKE
Microsoft 365 group
'*company.com*support*'

url Web address for a Microsoft 365 url = Yes

Microsoft 365 group or > Groups 'https://www.mycompany.com/'
SharePoint site
Microsoft 365 url LIKE '*www.mycompany.com*'
> Site
collections

Search attributes for non-cloud-to-cloud workloads

The following table summarizes the attributes that you can use in your search queries for non-
cloud-to-cloud workloads.

To see which attributes you can use in search queries for cloud-to-cloud workloads, refer to "Search
attributes for cloud-to-cloud workloads" (p. 330).

Supported
Attribute Meaning Search query examples for group
creation

General

name Workload name, such as: name = 'en-00' Yes

l Host name for physical

machines
l Name for virtual
machines
l Database name
l Email address for
mailboxes

id Device ID. id != '4B2A7A93-A44F-4155-BDE3- Yes

A023C57C9431'
To see the device ID, under
Devices, select the device,
click Details > All
properties.

331 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

The ID is shown in the id

field.

resourceType Workload type. resourceType = 'machine' Yes

Possible values: resourceType in ('mssql_aag_

database', 'mssql_database')
l 'machine'
l 'exchange'
l 'mssql_server'
l 'mssql_instance'
l 'mssql_database'
l 'mssql_database_folder'
l 'msexchange_database'
l 'msexchange_storage_
group'
l 'msexchange_
mailbox.msexchange'
l 'msexchange_
mailbox.office365'
l 'mssql_aag_group'
l 'mssql_aag_database'
l 'virtual_machine.vmww'
l 'virtual_
machine.vmwesx'
l 'virtual_host.vmwesx'
l 'virtual_
cluster.vmwesx'
l 'virtual_
appliance.vmwesx'
l 'virtual_
application.vmwesx'
l 'virtual_resource_
pool.vmwesx'
l 'virtual_center.vmwesx'
l 'datastore.vmwesx'
l 'datastore_
cluster.vmwesx'
l 'virtual_
network.vmwesx'
l 'virtual_data_
center.vmwesx'

332 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

l 'virtual_machine.vmww'
l 'virtual_
cluster.mshyperv'
l 'virtual_
machine.mshyperv'
l 'virtual_host.mshyperv'
l 'virtual_
network.mshyperv'
l 'virtual_
folder.mshyperv'
l 'virtual_data_
center.mshyperv'
l 'datastore.mshyperv'
l 'virtual_machine.msvs'
l 'virtual_
machine.parallelsw'
l 'virtual_
host.parallelsw'
l 'virtual_
cluster.parallelsw'
l 'virtual_machine.rhev'
l 'virtual_machine.kvm'
l 'virtual_machine.xen'
l 'bootable_media'

chassis Chassis type. chassis = 'laptop' Yes

chassis IN ('laptop', 'desktop')
Possible values:

l laptop
l desktop
l server
l other
l unknown

ip IP address (only for ip RANGE Yes

physical machines). ('10.250.176.1','10.250.176.50')

comment Comment for a device. It comment = 'important machine' Yes

can be specified
comment = '' (all machines without
automatically or manually.
a comment)

333 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

Default value:

l For physical machines

running Windows, the
computer description in
Windows is
automatically copied as
a comment. This value is
synchronized every 15
minutes.
l Empty for other devices.

Note
The automatic
synchronization is disabled
if there is manually added
text in the comment field.
To enable the
synchronization again,
clear this text.

To refresh the
automatically synchronized
comments for your
workloads, restart the
Managed Machine Service
in Windows Services or
run the following
commands at the
command prompt:

net stop mms

net start mms

To view a device comment,

under Devices, select the
device, click Details, and
then locate the Comment
section.

To add or change a
comment manually, click
Add or Edit.

334 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

For devices on which a

protection agent is
installed, there are two
separate comment fields:

l Agent comment
o For physical

machines running
Windows, the
computer description
in Windows is
automatically copied
as a comment. This
value is synchronized
every 15 minutes.
o Empty for other
devices.

Note
The automatic
synchronization is
disabled if there is
manually added text in
the comment field. To
enable the
synchronization again,
clear this text.

l Device comment
o If the agent comment
is specified
automatically, it is
copied as a device
comment. Manually
added agent
comments are not
copied as device
comments.
o Device comments are
not copied as agent
comments.

A device can have one or

both of these comments

335 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

specified, or have the both

of them blank. If the both
comments are specified,
the device comment has
priority.

To view an agent comment,

under Settings > Agents,
select the device with the
agent, click Details, and
then locate the Comment
section.

To view a device comment,

under Devices, select the
device, click Details, and
then locate the Comment
section.

To add or change a
comment manually, click
Add or Edit.

isOnline Workload availability. isOnline = true No

Possible values:

l true
l false

hasAsz Secure Zone availability. hasAsz = true Yes

Possible values:

l true
l false

tzOffset Timezone offset from tzOffset = 120 Yes

Coordinated Universal
tzOffset > 120
Time (UTC), in minutes.
tzOffset < 120

CPU, memory, disks

cpuArch CPU architecture. cpuArch = 'x64' Yes

Possible values:

l 'x64'

336 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

l 'x86'

cpuName CPU name. cpuName LIKE '%XEON%' Yes

memorySize RAM size in megabytes. memorySize < 1024 Yes

diskSize Hard drive size in gigabytes diskSize < 300GB No

or megabytes (only for diskSize >= 3000000MB
physical machines).

Operating system

osName Operating system name. osName LIKE '%Windows XP%' Yes

osType Operating system type. osType = 'windows' Yes

Possible values: osType IN ('linux', 'macosx')

l 'windows'
l 'linux'
l 'macosx'

osArch Operating system cpuArch = 'x86' Yes

architecture.

Possible values:

l 'x64'
l 'x86'

osProductType Operating system product osProductType = 'server' Yes

type.

Possible values:

l 'dc'
Stands for Domain
Controller.

337 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

Note
When the domain
controller role is
assigned on a Windows
server, the
osProductType changes
from server to dc. Such
machines will be not
included in the search
results for
osProductType='server'.

l 'server'
l 'workstation'

osSp Service pack of the osSp = 1 Yes

operating system.

osVersionMajor Major version of the osVersionMajor = 1 Yes

operating system.

osVersionMinor Minor version of the osVersionMinor > 1 Yes

operating system.

Agent

agentVersion Version of the installed agentVersion LIKE '12.0.*' Yes

protection agent.

hostId Internal ID of the hostId = '4B2A7A93-A44F-4155- Yes

protection agent. BDE3-A023C57C9431'

To see the protection agent

ID, under Devices, select
the device, click Details >
All properties. Check the
id value of the agent
property.

virtualType Virtual machine type. virtualType = 'vmwesx' Yes

Possible values:

l 'vmwesx'
VMware virtual
machines.
l 'mshyperv'

338 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

Hyper-V virtual
machines.
l 'pcs'
Virtuozzo virtual
machines.
l 'hci'
Virtuozzo Hybrid
Infrastructure virtual
machines.
l 'scale'
Scale Computing HC3
virtual machines.
l 'ovirt'
oVirt virtual machines

insideVm Virtual machine with an insideVm = true Yes

agent inside.

Possible values:

l true
l false

Location

tenant The name of the tenant to tenant = 'Unit 1' Yes

which the device belongs.

tenantId The identifier of the tenant tenantId = '3bfe6ca9-9c6a-4953- Yes

to which device belongs. 9cb2-a1323f454fc9'

To see the tenant ID, under

Devices, select the device,
click Details > All
properties. The ID is
shown in the ownerId field.

ou Devices that belong to the ou IN ('RnD', 'Computers') Yes

specified Active Directory
organizational unit.

Status

state Device state. state = 'backup' No

Possible values:

339 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

l 'idle'
l 'interactionRequired'
l 'canceling'
l 'backup'
l 'recover'
l 'install'
l 'reboot'
l 'failback'
l 'testReplica'
l 'run_from_image'
l 'finalize'
l 'failover'
l 'replicate'
l 'createAsz'
l 'deleteAsz'
l 'resizeAsz'

status Protection status. status = 'ok' No

Possible values: status IN ('error', 'warning')

l ok
l warning
l error
l critical
l protected
l notProtected

protectedByPlan Devices that are protected protectedByPlan = '4B2A7A93- No

by a protection plan with a A44F-4155-BDE3-A023C57C9431'
given ID.

To see the plan ID, in

Management >
Protection plans, select a
plan, click the bar in the
Status column, and then
click the status name. A
new search with the plan ID
will be created.

okByPlan Devices that are protected okByPlan = '4B2A7A93-A44F-4155- No

by a protection plan with a BDE3-A023C57C9431'
given ID and have an OK

340 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

status.

errorByPlan Devices that are protected errorByPlan = '4B2A7A93-A44F- No

by a protection plan with a 4155-BDE3-A023C57C9431'
given ID and have an Error
status.

warningByPlan Devices that are protected warningByPlan = '4B2A7A93-A44F- No

by a protection plan with a 4155-BDE3-A023C57C9431'
given ID and have a
Warning status.

runningByPlan Devices that are protected runningByPlan = '4B2A7A93-A44F- No

by a protection plan with a 4155-BDE3-A023C57C9431'
given ID and have a
Running status.

interactionByPlan Devices that are protected interactionByPlan = '4B2A7A93- No

by a protection plan with a A44F-4155-BDE3-A023C57C9431'
given ID and have an
Interaction Required
status.

lastBackupTime* The date and time of the lastBackupTime > '2023-03-11' No

last successful backup.
lastBackupTime <= '2023-03-11
The format is 'YYYY-MM-DD 00:15'
HH:MM'.
lastBackupTime is null

lastBackupTryTime* The time of the last backup lastBackupTryTime >= '2023-03- No

attempt. 11'

The format is 'YYYY-MM-DD

HH:MM'.

nextBackupTime* The time of the next nextBackupTime >= '2023-08-11' No

backup.

The format is 'YYYY-MM-DD

HH:MM'.

lastVAScanTime* The date and time of the lastVAScanTime > '2023-03-11' Yes
last successful vulnerability lastVAScanTime <= '2023-03-11
assessment. 00:15'

The format is 'YYYY-MM-DD lastVAScanTime is null

HH:MM'.

341 © Acronis International GmbH, 2003-2024

 Supported
Attribute Meaning Search query examples for group
creation

lastVAScanTryTime* The time of the last lastVAScanTimeTryTime >= '2022- Yes

vulnerability assessment 03-11'
attempt.

The format is 'YYYY-MM-DD

HH:MM'.

nextVAScanTime* The time of the next nextVAScanTime <= '2023-08-11' Yes

vulnerability assessment.

The format is 'YYYY-MM-DD

HH:MM'.

network_status Network isolation status for network_status= 'connected' Yes

Endpoint detection and
response (EDR).

Possible values:

l connected
l isolated

Note
If you skip the hour and minutes value, the start time is considered to be YYYY-MM-DD 00:00, and
the end time is considered to be YYYY-MM-DD 23:59:59. For example, lastBackupTime = 2023-01-20,
means that the search results will include all backups from the interval
lastBackupTime >= 2023-01-20 00:00 and lastBackup time <= 2023-01-20 23:59:59.

Search operators
The following table summarizes the operators that you can use for your search queries.

You can use more than one operator in a single query.

Operator Supported Meaning Examples

for

AND All workloads Logical conjunction name like 'en-00' AND tenant = 'Unit 1'
operator

OR All workloads Logical disjunction state = 'backup' OR state =

operator 'interactionRequired'

NOT All workloads Logical negation NOT(osProductType = 'workstation')

operator

342 © Acronis International GmbH, 2003-2024

 Operator Supported Meaning Examples
for

IN All workloads This operator osType IN ('windows', 'linux')

(<value1>,... checks if an
<valueN>) expression
matches any value
in a list of values.

NOT IN All workloads This operator is NOT osType IN ('windows', 'linux')

the opposite of the
IN operator.

LIKE 'wildcard All workloads This operator name LIKE 'en-00'

pattern' checks if an
name LIKE '*en-00'
expression
matches the name LIKE '*en-00*'
wildcard pattern.
name LIKE 'en-00_'
You can use the
following wildcard
operators:

l * or % The
asterisk and the
percent sign
represent zero,
one, or multiple
characters
l _ The
underscore
represents a
single character

NOT LIKE All workloads This operator is NOT name LIKE 'en-00'
'wildcard the opposite of the
NOT name LIKE '*en-00'
pattern' LIKE operator.
NOT name LIKE '*en-00*'
You can use the
following wildcard NOT name LIKE 'en-00_'
operators:

l * or % The
asterisk and the
percent sign
represent zero,
one, or multiple
characters
l _ The
underscore

343 © Acronis International GmbH, 2003-2024

 Operator Supported Meaning Examples
for

represents a
single character

RANGE All workloads This operator ip RANGE('10.250.176.1','10.250.176.50')

(<starting_ checks if an
name RANGE('a','d')
value>, expression is
<ending_value>) within a range of With this query, you can filter all names that begin
values (inclusive). with A, B, and C, such as Alice, Bob, Claire.
However, only the single letter D meets the
Search queries
requirements, so names with more letters, such
with alphanumeric
as Diana or Don will not be included.
strings use the
ASCII sort order To achieve the same result, you can also use the
but are case- following query:
insensitive.
name >= 'a' AND name <= 'd'

= or == All workloads Equal to operator osProductType = 'server'

!= or <> All workloads Not equal to id != '4B2A7A93-A44F-4155-BDE3-A023C57C9431'

operator

< Non-cloud- Less than operator memorySize < 1024

to-cloud
workloads

> Non-cloud- Greater than diskSize > 300GB

to-cloud operator.
workloads

<= Non-cloud- Less than or equal lastBackupTime <= '2022-03-11 00:15'

to-cloud to operator
workloads

>= Non-cloud- Greater than or nextBackupTime >= '2022-08-11'

to-cloud equal to operator
workloads

Editing a dynamic group

You edit a dynamic group by changing the search query that defines the group content.

In dynamic groups that are based on Active Directory, you can also change the Active Directory
group.

To edit a dynamic group

By changing the search query

344 © Acronis International GmbH, 2003-2024

1. Click Devices, navigate to the dynamic group that you want to edit, and then select it.
2. Click the gear icon next to the name of the group, and then click Edit. Alternatively, click Edit in
the Actions pane.
3. Change the search query by modifying the search attributes, their values, or the search
operators, and then click Search.
4. Click Save next to the search field.

By changing the Active Directory group

Note
This procedure applies to dynamic groups based on Active Directory. Active Directory-based
dynamic groups are available only in Microsoft 365 > Users.

1. Click Devices, navigate to Devices > Microsoft 365 > your organization > Users.
2. Select the dynamic group that you want to edit.
3. Click the gear icon next to the name of the group, and then click Edit. Alternatively, click Edit in
the Actions pane.
4. Change the group content by doing any of the following:
l Change the already selected Active Directory group by clicking its name, and then selecting a
new Active Directory group from the list that opens.
l Edit the search query, and then click Search.
The search query is limited to the currently selected Active Directory group.
5. Click Save next to the search field.

You can also save your edits without overwriting the current group. To save the edited configuration
as a new group, click the arrow button next to the search field, and then click Save as.

Deleting a group
When you delete a device group, all plans that are applied to that group will be revoked. The
workloads in the group will become unprotected if no other plans are applied to them.

To delete a device group

1. Click Devices, and then navigate to the group that you want to delete.
2. Click the gear icon next to the name of the group, and then click Delete.
3. Confirm your choice by clicking Delete.

Applying a plan to a group

You can apply a plan to a group by selecting the group first, and then assigning a plan to it.

Alternatively, you can open a plan for editing, and then add a group to it.

To apply a plan to a group

345 © Acronis International GmbH, 2003-2024

1. Click Devices, and then navigate to the group to which you want to apply a plan.
2. [For non-cloud-to-cloud workloads] Click Protect group.

A list of plans that can be applied is shown.

3. [For cloud-to-cloud workloads] Click Group backup.

A list of backup plans that can be applied is shown.

4. [To apply an existing plan] Select the plan, and then click Apply.
5. [To create a new plan] Click Create plan, select the plan type, and then create the new plan.
For more information about the available types of plans and how to create them, refer to
"Supported plans for device groups" (p. 326).

Note
Backup plans that are applied to cloud-to-cloud device groups are automatically scheduled to run
once a day. You cannot run these plans on demand by clicking Run now.

Revoking a plan from a group

You can revoke a plan from a group by selecting the group first, and then revoking the plan from it.

Alternatively, you can open the plan for editing, and then remove the group from it.

To revoke a plan from a group

1. Click Devices, and then navigate to the group from which you want to revoke a plan.
2. [For non-cloud-to-cloud workloads] Click Protect group.
A list of plans that are applied to the group is shown.
3. [For cloud-to-cloud workloads] Click Group backup.

346 © Acronis International GmbH, 2003-2024

 A list of backup plans that are applied to the group is shown.
4. Select the plan that you want to revoke.
5. [For non-cloud-to-cloud workloads] Click the ellipsis icon (...), and then click Revoke.
6. [For cloud-to-cloud workloads] Click the gear icon, and then click Revoke.

Working with the Device control module

A part of the Cyber Protection service protection plans, the device control module1 leverages a
functional subset of the agent for Data Loss Prevention2 on each protected computer to detect and
prevent unauthorized access and transmission of data over local computer channels. It provides
fine-grained control over a wide range of data leakage pathways including data exchange using
removable media, printers, virtual and redirected devices, and the Windows clipboard.

The module is available for Cyber Protect Essentials, Cyber Protect Standard, and Cyber Protect
Advanced editions that are licensed per workload.

Note
On Windows machines, the device control features require the installation of Agent for Data Loss
Prevention. It will be installed automatically for protected workloads if the Device control module
is enabled in their protection plans.

The device control module relies on the data loss prevention3 functions of the agent to enforce
contextual control over data access and transfer operations on the protected computer. These
include user access to peripheral devices and ports, document printing, clipboard copy / paste
operations, media format and eject operations, as well as synchronizations with locally connected
mobile devices. The agent for Data Loss Prevention includes a framework for all central
management and administration components of the device control module, and therefore it must
be installed on every computer to be protected with the device control module. The agent allows,
restricts, or denies user actions based on the device control settings it receives from the protection
plan that is applied to the protected computer.

1As part of a protection plan, the device control module leverages a functional subset of the data loss prevention

agent on each protected computer to detect and prevent unauthorized access and transmission of data over local
computer channels. These include user access to peripheral devices and ports, document printing, clipboard
copy/paste operations, media format and eject operations, as well as synchronizations with locally connected mobile
devices. The device control module provides granular, contextual control over the types of devices and ports that
users are allowed to access on the protected computer and the actions that users can take on those devices.
2A data loss prevention system’s client component that protects its host computer from unauthorized use,

transmission, and storage of confidential, protected, or sensitive data by applying a combination of context and
content analysis techniques and enforcing centrally managed data loss prevention policies. Cyber Protection provides
a fully featured data loss prevention agent. However, the functionality of the agent on a protected computer is limited
to the set of data loss prevention features available for licensing in Cyber Protection, and depends upon the protection
plan applied to that computer.
3A system of integrated technologies and organizational measures aimed at detecting and preventing accidental or

intentional disclosure / access to confidential, protected, or sensitive data by unauthorized entities outside or inside
the organization, or the transfer of such data to untrusted environments.

347 © Acronis International GmbH, 2003-2024

The device control module controls access to various peripheral devices, whether used directly on
protected computers or redirected in virtualization environments hosted on protected computers. It
recognizes devices redirected in Microsoft Remote Desktop Server, Citrix XenDesktop / XenApp /
XenServer, and VMware Horizon. It can also control data copy operations between the clipboard of
the guest operating system running on VMware Workstation / Player, Oracle VM VirtualBox, or
Windows Virtual PC, and the clipboard of the host operating system running on the protected
computer.

The device control module can protect computers running the following operating systems:

Device control

l Microsoft Windows 7 Service Pack 1 and later

l Microsoft Windows Server 2008 R2 and later
l macOS 10.15 (Catalina)
l macOS 11.2.3 (Big Sur)
l macOS 12 (Monterey)
l macOS 13 (Ventura)

Note
Agent for Data Loss Prevention for macOS supports only x64 processors. Apple silicon ARM-based
processors are not supported.

Data loss prevention

l Microsoft Windows 7 Service Pack 1 and later

l Microsoft Windows Server 2008 R2 and later

Note
Agent for Data Loss Prevention might be installed on unsupported macOS systems because it is an
integral part of Agent for Mac. In this case, the Cyber Protect console will indicate that Agent for
Data Loss Prevention is installed on the computer, but the device control and data loss prevention
functionality will not work. Device control functionality will only work on macOS systems that are
supported by Agent for Data Loss Prevention.

Limitation on the use of the agent for Data Loss Prevention with Hyper-V
Do not install Аgent for Data Loss Prevention on Hyper-V hosts in Hyper-V clusters because it might
cause BSOD issues, mainly in Hyper-V clusters with Clustered Shared Volumes (CSV).

If you use any of the following versions of Agent for Hyper-V, you need to manually remove Agent
for Data Loss Prevention:

l 15.0.26473 (C21.02)
l 15.0.26570 (C21.02 HF1)
l 15.0.26653 (C21.03)

348 © Acronis International GmbH, 2003-2024

l 15.0.26692 (C21.03 HF1)
l 15.0.26822 (C21.04)

To remove Agent for Data Loss Prevention, on the Hyper-V host, run the installer manually and clear
the Agent for Data Loss Prevention check box, or run the following command:

<installer_name> --remove-components=agentForDlp –quiet

You can enable and configure the device control module in the Device control section of your
protection plan in the Cyber Protect console. For instructions, see steps to enable or disable device
control.

The Device control section displays a summary of the module’s configuration:

l Access settings - Shows a summary of device types and ports with restricted (denied or read-only)
access, if any. Otherwise, indicates that all device types are allowed. Click this summary to view or
change the access settings (see steps to view or change access settings).
l Device types allowlist - Shows how many device subclasses are allowed by excluding from device
access control, if any. Otherwise, indicates that the allowlist is empty. Click this summary to view
or change the selection of allowed device subclasses (see steps to exclude device subclasses from
access control).
l USB devices allowlist - Shows how many USB devices/models are allowed by excluding from
device access control, if any. Otherwise, indicates that the allowlist is empty. Click this summary
to view or change the list of allowed USB devices/models (see steps to exclude individual USB
devices from access control).
l Exclusions - Shows how many access control exclusions have been set for Windows clipboard,
screenshot capture, printers, and mobile devices.

Using device control

This section covers step-by-step instructions for basic tasks when using the device control module.

349 © Acronis International GmbH, 2003-2024

Enable or disable device control
You can enable device control when creating a protection plan. You can change an existing
protection plan to enable or disable device control.

To enable or disable device control

1. In the Cyber Protect console, go to Devices > All devices.

2. Do one of the following to open the protection plan panel:
l If you are going to create a new protection plan, select a machine to protect, click Protect, and
then click Create plan.
l If you are going to change an existing protection plan, select a protected machine, click
Protect, click the ellipsis (...) next to the name of the protection plan, and then click Edit.
3. In the protection plan panel, navigate to the Device control area, and enable or disable Device
control.
4. Do one of the following to apply your changes:
l If creating a protection plan, click Create.
l If editing a protection plan, click Save.

You might also access the protection plan panel from the Management tab. However, this capability
is not available in all editions of the Cyber Protection service.

Enabling the use of the device control module on macOS

The device control settings of a protection plan become effective only after loading the device
control driver on the protected workload. This section describes how to load the device control
driver to enable the use of the device control module on macOS. This is a one-time operation that
requires administrator privileges on the endpoint machine.

Supported macOS versions:

l macOS 10.15 (Catalina) and later

l macOS 11.2.3 (Big Sur) and later
l macOS 12.2 (Monterey) and later
l macOS 13.2 (Ventura) and later

To enable the use of device control module on macOS

1. Install Agent for Mac on the machine that you want to protect.
2. Enable device control settings in the protection plan.
3. Apply the protection plan.

350 © Acronis International GmbH, 2003-2024

4. The "System Extension Blocked" warning will appear on the protected workload. Click Open
Security Preferences.

351 © Acronis International GmbH, 2003-2024

5. In the Security & Privacy pane that appears, select App Store and identified developers and
then click Allow.

6. In the dialog that appears, click Restart to restart the workload and activate the device control
settings.

Note
You do not have to repeat these steps if the device control setting are disabled and then enabled
again.

View or change access settings

From the protection plan panel, you can manage access settings for the device control module. In
this way, you can allow or deny access to certain types of devices, as well as enable or disable
notifications and alerts.

To view or change access settings

1. Open the protection plan panel for a protection plan and enable device control in that plan (see
steps to enable or disable device control).
2. Click the arrow icon next to the Device control switch to expand the settings, and then click the
link next to Access settings.

352 © Acronis International GmbH, 2003-2024

3. On the page for managing access settings that appears, view or change access settings as
appropriate.

Note
The access settings configured in Device control might be overridden when using both Device
control and Advanced DLP to protect a workload. See "Enabling Advanced Data Loss Prevention in
protection plans" (p. 835).

Enable or disable OS notification and service alerts

When managing access settings, you can enable or disable OS notification and service alerts,
informing of user attempts to perform actions that are not allowed.

To enable or disable OS notification

1. Follow the steps to view or change access settings.

2. On the page for managing access settings, select or clear the Show OS notification to end
users if they try to use a blocked device type or port check box.

To enable or disable service alerts

1. Follow the steps to view or change access settings.

2. On the page for managing access settings, select or clear the Show alert check box for the
desired device type/s.

The Show alert check box is available only for device types with restricted access (Read-only or
Denied access), except screenshot capture.

Exclude device subclasses from access control

From the protection plan panel, you can choose device subclasses to exclude from access control.
As a result, access to those devices is allowed regardless of the device control access settings.

To exclude device subclasses from access control

1. Open the protection plan panel for a protection plan and enable device control in that plan (see
steps to enable or disable device control).
2. Click the arrow icon next to the Device control switch to expand the settings, and then click the
link next to Device types allowlist.
3. On the page for managing the allowlist that appears, view or change the selection of device
subclasses to exclude from access control.

Exclude individual USB devices from access control

From the protection plan panel, you can specify individual USB devices or USB device models to
exclude from access control. As a result, access to those devices is allowed regardless of the device
control access settings.

To exclude a USB device from access control

353 © Acronis International GmbH, 2003-2024

1. Open the protection plan panel for a protection plan and enable device control in that plan (see
steps to enable or disable device control).
2. Click the arrow icon next to the Device control switch to expand the settings, and then click the
link next to USB devices allowlist.
3. On the page for managing the allowlist that appears, click Add from database.
4. On the page for selecting USB devices that appears, select the desired device/s from those
registered with the USB devices database.
5. Click the Add to allowlist button.

To stop excluding a USB device from access control

1. Open the protection plan panel for a protection plan and enable device control in that plan (see
steps to enable or disable device control).
2. Click the arrow icon next to the Device control switch to expand the settings, and then click the
link next to USB devices allowlist.
3. On the page for managing the allowlist that appears, click the delete icon at the end of list item
representing the desired USB device.

Add or remove USB devices from the database

To exclude a particular USB device from access control, you need to add it to the USB devices
database. Then, you can add devices to the allowlist by selecting from that database.

The following procedures apply to protection plans that have the device control feature enabled.

To add USB devices to the database

1. Open the protection plan of a device for editing:

Click the ellipsis (...) next to the name of the protection plan and select Edit.

Note
Device control must be enabled in the plan, so you can access the Device control settings.

2. Click the arrow icon next to the Device control switch to expand the settings, and then click the
link next to USB devices allowlist.
3. On the USB devices allowlist page that appears, click Add from database.
4. On the USB devices database management page that appears, click Add to database.
5. On the Add USB device dialog that appears, click the machine to which the USB device is
connected.
Only machines that are online are displayed in the list of computers.
The list of USB devices is displayed only for machines that have the agent for Data Loss
Prevention installed.
The USB devices are listed in tree view. The first level of the tree represents a device model. The
second level represents a specific device of that model.
A blue icon next to the description of the device indicates that the device is currently attached to
the computer. If the device is not attached to the computer, the icon is grayed out.

354 © Acronis International GmbH, 2003-2024

6. Select the check boxes for the USB devices that you want to add to the database, and then click
Add to database.
The selected USB devices are added to the database.
7. Close or save the protection plan.

To add USB devices to the database from the computer Details panel

Note
This procedure applies only for devices that are online and have the agent for Data Loss Prevention
installed on them. You cannot view the list of USB devices for a computer that is offline or does not
have the Data Loss Prevention agent installed.

1. In the Cyber Protect console, go to Devices > All devices.

2. Select a computer to which the desired USB device has ever been connected, and, in the menu to
the right, click Inventory.
The computer details panel opens.
3. On the computer details panel, click the USB Devices tab.
The list of USB devices that are known on the selected computer opens.
The USB devices are listed in tree view. The first level of the tree represents a device model. The
second level represents a specific device of that model.
A blue icon next to the description of the device indicates that the device is currently attached to
the computer. If the device is not attached to the computer, the icon is grayed out.
4. Select the check boxes for the USB devices that you want to add to the database and click Add to
database.

To add USB devices to the database from service alerts

1. In the Cyber Protect console, go to Monitoring > Alerts.

2. Locate a device control alert that informs of denying access to the USB device.
3. In the alert simple view, click Allow this USB device.
This excludes the USB device from access control, and adds it to the database for further
reference.

To add USB devices by importing a list of devices to the database

You can import a JSON file with a list of USB devices to the database. See "Import a list of
USB devices to the database" (p. 365).

To remove USB devices from the database

1. Open the protection plan of a device for editing:

Click the ellipsis (...) next to the name of the protection plan and select Edit.

Note
Device control must be enabled in the plan, so you can access the Device control settings.

355 © Acronis International GmbH, 2003-2024

2. Click the arrow next to the Device control switch to expand the settings, and then click the USB
devices allowlist row.
3. On the page for managing the allowlist that appears, click Add from database.
4. On the page for selecting USB devices from the database, click ellipsis (...) at the end of the list
item representing the device, click Delete, and confirm the deletion.
The USB devices are deleted from the database.
5. Close or save the protection plan.

View device control alerts

The device control module can be configured to raise alerts that inform of denied user attempts to
use certain device types (see Enable or disable OS notification and service alerts). Use the following
steps to view those alerts.

To view device control alerts

1. In the Cyber Protect console, go to Monitoring > Alerts.

2. Look for alerts with the following status: “Peripheral device access is blocked”.

See Device control alerts for further details.

Access settings
On the Access settings page, you can allow or deny access to devices of certain types, as well as
enable or disable OS notification and device control alerts.

Note
The access settings configured in Device control might be overridden when using both Device
control and Advanced DLP to protect a workload. See "Enabling Advanced Data Loss Prevention in
protection plans" (p. 835).

The access settings allow you to limit user access to the following device types and ports:

l Removable (access control by device type) - Devices with any interface for connecting to a
computer (USB, FireWire, PCMCIA, IDE, SATA, SCSI, etc.) that are recognized by the operating
system as removable storage devices (for example, USB sticks, card readers, magneto-optical
drives, etc.). The device control classifies all hard drives connected via USB, FireWire, and PCMCIA
as removable devices. It also classifies some hard drives (usually with SATA and SCSI) as
removable devices if they support the hot-plug function and do not have the running operating
system installed on them.
You can allow full access, read-only access, or deny access to removable devices to control data
copy operations to and from any removable device on a protected computer. Access rights do
not affect devices that are encrypted with BitLocker or FileVault (only HFS+ file system).
This device type is supported on both Windows and macOS.
l Encrypted removable (access control by device type) - Removable devices that are encrypted
with BitLocker (on Windows) or FileVault (on macOS) drive encryption.

356 © Acronis International GmbH, 2003-2024

 On macOS, only encrypted removable drives using the HFS+ (also known as HFS Plus or Mac OS
Extended, or HFS Extended) file system are supported. Encrypted removable drives using the
APFS file system are treated as removable drives.
You can allow full access, read-only access, or deny access to encrypted removable devices to
control data copy operations to and from any encrypted removable device on a protected
computer. Access rights affect only devices that are encrypted with BitLocker or FileVault (only
HFS+ file system).
This device type is supported on both Windows and macOS.
l Printers (access control by device type) - Physical printers with any interface for connecting to a
computer (USB, LPT, Bluetooth, etc.), as well as printers accessed from a computer on the
network.
You can allow or deny access to printers to control the printing of documents on any printer on a
protected computer.

Note
When you change the access setting for printers to Deny, the applications and processes
accessing the printers must be restarted to enforce the newly configured access settings. To
ensure that access settings are enforced correctly, restart the protected workloads.

This device type is supported only on Windows.

l Clipboard (access control by device type) - Windows clipboard.
You can allow or deny access to the clipboard to control the copy and paste operations through
the Windows clipboard on a protected computer.

Note
When you change the access setting for clipboard to Deny, the applications and processes
accessing the clipboard must be restarted to enforce the newly configured access settings. To
ensure that access settings are enforced correctly, restart the protected workloads.

This device type is supported only on Windows.

l Screenshot capture (access control by device type) - Enables capturing of screenshots of the
entire screen, the active window, or of selected portion of the screen.
You can allow or deny access to the screenshot capture to control the screenshot capturing on a
protected computer.

Note
When you change the access setting for screenshot capture to Deny, the applications and
processes accessing the screenshot capture must be restarted to enforce the newly configured
access settings. To ensure that access settings are enforced correctly, restart the protected
workloads.

This device type is supported only on Windows.

357 © Acronis International GmbH, 2003-2024

l Mobile devices (access control by device type) - Devices (such as Android-based smartphones,
etc.) that communicate with a computer via Media Transfer Protocol (MTP), with any interface
used for connecting to a computer (USB, IP, Bluetooth).
You can allow full access, allow read-only access, or deny access to mobile devices to control data
copy operations to and from any MTP-based mobile device on a protected computer.

Note
When you change the access setting for mobile devices to Read-only or Deny, the applications
and processes accessing the mobile devices must be restarted to enforce the newly configured
access settings. To ensure that access settings are enforced correctly, restart the protected
workloads.

This device type is supported only on Windows.

l Bluetooth (access control by device type) - External and internal Bluetooth devices with any
interface for connecting to a computer (USB, PCMCIA, etc.). This setting controls the use of the
devices of this type rather than data exchange using such devices.
You can allow or deny access to Bluetooth to control the use of any Bluetooth devices on a
protected computer.

Note
On macOS, the access rights for Bluetooth do not affect Bluetooth HID devices. The access to
these devices is always allowed to prevent wireless HID devices (mice and keyboards) from being
disabled on iMac and Mac Pro hardware.

This device type is supported on both Windows and macOS.

l Optical drives (access control by device type) - External and internal CD/DVD/BD drives
(including writers) with any interface for connecting to a computer (IDE, SATA, USB, FireWire,
PCMCIA, etc.).
You can allow full access, allow read-only access, or deny access to optical drives to control data
copy operations to and from any optical drive on a protected computer.
This device type is supported on both Windows and macOS.
l Floppy drives (access control by device type) - External and internal floppy drives with any
interface for connecting to a computer (IDE, USB, PCMCIA, etc.). There are some models of floppy
drives that the operating system recognizes as removable drives, in which case the device control
also identifies these drives as removable devices.
You can allow full access, allow read-only access, or deny access to floppy drives to control data
copy operations to and from any floppy drive on a protected computer.
This device type is supported only on Windows.
l USB (access control by device interface) - Any devices connected to a USB port, except hubs.
You can allow full access, allow read-only access, or deny access to USB port to control data copy
operations to and from devices connected to any USB port on a protected computer.
This device type is supported on both Windows and macOS.

358 © Acronis International GmbH, 2003-2024

l FireWire (access control by device interface) - Any devices connected to a FireWire (IEEE 1394)
port, except hubs.
You can allow full access, allow read-only access, or deny access to FireWire port to control data
copy operations to and from devices connected to any FireWire port on a protected computer.
This device type is supported on both Windows and macOS.
l Redirected devices (access control by device interface) - Mapped drives (hard, removable and
optical drives), USB devices, and the clipboard redirected to virtual application/desktop sessions.
The device control recognizes devices redirected via the Microsoft RDP, Citrix ICA, VMware PCoIP,
and HTML5/WebSockets remoting protocols in the Microsoft RDS, Citrix XenDesktop, Citrix
XenApp, Citrix XenServer, and VMware Horizon virtualization environments hosted on protected
Windows computers. It can also control data copy operations between the Windows clipboard of
the guest operating system running on VMware Workstation, VMware Player, Oracle VM
VirtualBox, or Windows Virtual PC, and the clipboard of the host operating system running on a
protected Windows computer.
This device type is supported only on Windows.
You can configure access to redirected devices as follows:
o Mapped drives - Allow full access, allow read-only access, or deny access to control data copy
operations to and from any hard drive, removable drive, or optical drive redirected to the
session hosted on a protected computer.
o Clipboard incoming - Allow or deny access to control data copy operations through the
clipboard to the session hosted on a protected computer.

Note
When you change the access setting for clipboard incoming to Deny, the applications and
processes accessing the clipboard must be restarted to enforce the newly configured access
settings. To ensure that access settings are enforced correctly, restart the protected
workloads.

o Clipboard outgoing - Allow or deny access to control data copy operations through the
clipboard from the session hosted on a protected computer.

Note
When you change the access setting for clipboard outgoing to Deny, the applications and
processes accessing the clipboard must be restarted to enforce the newly configured access
settings. To ensure that access settings are enforced correctly, restart the protected
workloads.

o USB ports - Allow or deny access to control data copy operations to and from devices
connected to any USB port redirected to the session hosted on a protected computer.

Device control settings affect all users equally. For example, if you deny access to removable
devices, you prevent any user from copying data to and from such devices on a protected computer.
It is possible to selectively allow access to individual USB devices by excluding them from access
control (see Device types allowlist and USB devices allowlist).

359 © Acronis International GmbH, 2003-2024

When access to a device is controlled by both its type and its interface, denying access at the
interface level takes precedence. For example, if access to USB ports is denied (device interface),
then access to mobile devices connected to a USB port is denied regardless of whether access to
mobile devices is allowed or denied (device type). To allow access to such a device, you must allow
both its interface and type.

Note
If the protection plan used on macOS has settings for device types that are supported only on
Windows, then the settings for these device types will be ignored on macOS.

Important
When a removable device, an encrypted removable device, a printer, or a Bluetooth device is
connected to a USB port, allowing access to that device overrides the access denial set at the USB
interface level. If you allow such a device type, access to the device is allowed regardless of whether
access to the USB port is denied.

OS notification and service alerts

You can configure the device control to display OS notification to end users if they try to use a
blocked device type on protected computers. When the Show OS notification to end users if they
try to use a blocked device type or port check box is selected in the access settings, the agent
displays a pop-up message in the notification area of the protected computer if any of the following
events occurs:

l A denied attempt to use a device on a USB or FireWire port. This notification appears whenever
the user plugs in a USB or FireWire device that is denied at the interface level (for example, when
denying access to the USB port) or at the type level (for example, when denying the use of
removable devices). The notification informs that the user is not allowed to access the specified
device/drive.
l A denied attempt to copy a data object (such as a file) from a certain device. This notification
appears when denying read access to the following devices: floppy drives, optical drives,
removable devices, encrypted removable devices, mobile devices, redirected mapped drives, and
redirected clipboard incoming data. The notification informs that the user is not allowed to get
the specified data object from the specified device.
The denied read notification is also displayed when denying read/write access to Bluetooth,
FireWire port, USB port, and redirected USB port.
l A denied attempt to copy a data object (such as a file) to a certain device. This notification
appears when denying write access to the following devices: floppy drives, optical drives,
removable devices, encrypted removable devices, mobile devices, local clipboard, screenshot
capture, printers, redirected mapped drives, and redirected clipboard outgoing data. The
notification informs that the user is not allowed to send the specified data object to the specified
device.

User attempts to access blocked device types on protected computers can raise alerts that are
logged in the Cyber Protect console. It is possible to enable alerts for each device type (excluding

360 © Acronis International GmbH, 2003-2024

screenshot capture) or port separately by selecting the Show alert check box in the access settings.
For example, if access to removable devices is restricted to read-only, and the Show alert check box
is selected for that device type, an alert is logged every time a user on a protected computer
attempts to copy data to a removable device. See Device control alerts for further details.

See also steps to enable or disable OS notification and service alerts.

Device types allowlist

On the Device types allowlist page, you can choose device subclasses to exclude from device
access control. As a result, access to those devices is allowed regardless of the access settings in the
device control module.

The device control module provides the option to allow access to devices of certain subclasses
within a denied device type. This option allows you to deny all devices of a certain type, except for
some subclasses of devices of this type. It can be useful, for example, when you need to deny access
to all USB ports while allowing the use of a USB keyboard and mouse at the same time.

When configuring the device control module, you can specify which device subclasses to exclude
from device access control. When a device belongs to an excluded subclass, access to that device is
allowed regardless of whether or not the device type or port is denied. You can selectively exclude
the following device subclasses from device access control:

l USB HID (mouse, keyboard, etc.) - When selected, allows access to Human Interface Devices
(mouse, keyboard, and so on) connected to a USB port even if USB ports are denied. By default,
this item is selected so that denying access to the USB port does not disable the keyboard or
mouse.
Supported on both Windows and macOS.
l USB and FireWire network cards - When selected, allows access to network cards connected to
a USB or FireWire (IEEE 1394) port even if USB ports and/or FireWire ports are denied.
Supported on both Windows and macOS.
l USB scanners and still image devices - When selected, allows access to scanners and still
image devices connected to a USB port even if USB ports are denied.
Supported only on Windows.
l USB audio devices - When selected, allows access to audio devices, such as headsets and
microphones, connected to a USB port even if USB ports are denied.
Supported only on Windows.
l USB cameras - When selected, allows access to Web cameras connected to a USB port even if
USB ports are denied.
Supported only on Windows.
l Bluetooth HID (mouse, keyboard, etc.) - When selected, allows access to Human Interface
Devices (mouse, keyboard, and so on) connected via Bluetooth even if Bluetooth is denied.
Supported only on Windows.
l Clipboard copy/paste within application - When selected, allows copying/pasting of data
through the clipboard within the same application even if the clipboard is denied.
Supported only on Windows.

361 © Acronis International GmbH, 2003-2024

Note
Settings for unsupported device subclasses are ignored if these settings are configured in the
applied protection plan.

When allowlisting device types, consider the following:

l With the device types allowlist, you can only allow a whole subclass of device. You cannot allow a
specific device model, while denying all other devices of the same subclass. For example, by
excluding USB cameras from device access control, you allow the use of any USB camera, no
matter their model and vendor. On how to allow individual devices/models, see USB devices
allowlist.
l Device types can only be selected from a closed list of device subclasses. If the device to allow is
of a different subclass, then it cannot be allowed by using device types allowlist. For example,
such a subclass as USB smartcard readers cannot be added to the allowlist. To allow a USB
smartcard reader when USB ports are denied, follow the instructions in USB devices allowlist.
l The device types allowlist only works for devices that use standard Windows drivers. The device
control may not recognize the subclass of some USB devices with proprietary drivers. As a result,
you cannot allow access to such USB devices by using the device types allowlist. In this case, you
could allow access on a per-device/model basis (see USB devices allowlist).

USB devices allowlist

The allowlist is intended to allow using certain USB devices regardless of any other device control
settings. You can add individual devices or device models to the allowlist to disable the access
control for those devices. For example, if you add a mobile device with a unique ID to the allowlist,
you allow the use of that particular device even though any other USB devices are denied.

On the USB devices allowlist page, you can specify individual USB devices or USB device models to
exclude from device access control. As a result, access to those devices is allowed regardless of the
access settings in the device control module.

There are two ways to identify devices in the allowlist:

l Model of device - Collectively identifies all devices of a certain model. Each device model is
identified by vendor ID (VID) and product ID (PID), such as USB\VID_0FCE&PID_E19E.
This combination of VID and PID does not identify a specific device, but an entire device model.
By adding a device model to the allowlist, you allow access to any device of that model. For
example, this way you can allow the use of USB printers of a particular model.
l Unique device - Identifies a certain device. Each unique device is identified by vendor ID (VID),
product ID (PID), and serial number, such as USB\VID_0FCE&PID_E19E\D55E7FCA.
Not all USB devices are assigned a serial number. You can add a device to the allowlist as a
unique device only if the device has been assigned a serial number during production. For
example, a USB stick that has a unique serial number.

362 © Acronis International GmbH, 2003-2024

To add a device to the allowlist, you first need to add it to the USB devices database. Then, you can
add devices to the allowlist by selecting from that database.

The allowlist is managed on a separate configuration page called USB devices allowlist. Each item
in the list represents a device or device model and has the following fields:

l Description - The operating system assigns a certain description when connecting the USB
device. You can modify the description of the device in the USB devices database (see USB
database management page).
l Device type - Displays Unique if the list item represents a unique device, or Model if it represents
a device model.
l Read-only - When selected, allows only receiving data from the device. If the device does not
support read-only access, then access to the device is blocked. Clear this check box to allow full
access to the device.
l Reinitialize - When selected, causes the device to simulate disconnecting/reconnecting when a
new user logs in. Some USB devices require reinitializing in order to function, so we recommend
that you select this check box for such devices (mouse, keyboard, etc.). We also recommend that
you clear this check box for data storage devices (USB sticks, optical drives, external hard drives,
etc.).
The device control may not be able to reinitialize some USB devices with proprietary drivers. If
there is no access to such a device, you must remove the USB device from the USB port, and then
insert it back.

Note
The Reinitialize field is hidden by default. To display it in the table, click the gear icon in the
upper right corner of the table, and then select the Reinitialize check box.

Note
The Read-only and Reinitialize fields are not supported on macOS. If these fields are configured
in the applied protection plan, they will be ignored.

You can add or remove devices/models from the allowlist as follows:

l Click Add from database above the list and then select the desired device/s from those
registered with the USB devices database. The selected device is added to the list, where you can
configure its settings and confirm the changes.
l Click Allow this USB device in an alert informing that access to the USB device is denied (see
Device control alerts). This adds the device to the allowlist and to the USB devices database.
l Click the delete icon at the end of a list item. This removes the respective device/model from the
allowlist.

USB devices database

The device control module maintains a database of USB devices from which you can add devices to
the list of exclusions (see USB devices allowlist). A USB device can be registered with the database in

363 © Acronis International GmbH, 2003-2024

any of these ways:

l Add a device on the page that appears when adding a device to the exclusion list (see USB
devices database management page).
l Add a device from the USB Devices tab of a computer's Inventory pane in the Cyber Protect
console (see List of USB devices on a computer).
l Allow the device from an alert on denying access to the USB device (see Device control alerts).

See also steps to add or remove USB devices from the database.

USB devices database management page

When configuring the allowlist for USB devices, you have the option to add a device from the
database. If you choose this option, a management page appears with a list of devices. On this page
you can view the list of all devices that are registered with the database, you can select devices to
add to the allowlist, and perform the following operations:

Register a device with the database

1. Click Add to database at the top of the page.

2. On the Add USB device dialog that appears, choose the machine to which the USB device is
connected.
Only machines that are online are displayed in the list of computers.
The list of USB devices is displayed only for machines that have the agent for Data Loss
Prevention installed.
The USB devices are listed in tree view. The first level of the tree represents a device model. The
second level represents a specific device of that model.
A blue icon next to the description of the device indicates that the device is currently attached to
the computer. If the device is not attached to the computer, the icon is grayed out.
3. Select the check box for the USB device that you want to register, and click Add to database.

Change the description of a device

1. On the USB devices database page click ellipsis (...) at the end of the list item representing the
device and then click Edit.
2. Make changes to the description in the dialog box that appears.

Remove a device from the database

1. Click the ellipsis (...) at the end of the list item representing the device.
2. Click Delete, and confirm the deletion.

For each device, the list on the page provides the following information:

l Description - A readable identifier of the device. You can change the description as needed.
l Device type - Displays Unique if the list item represents a unique device, or Model if it represents
a device model. A unique device must have a serial number along with a vendor ID (VID) and
product ID (PID), whereas a device model is identified by a combination of VID and PID.

364 © Acronis International GmbH, 2003-2024

l Vendor ID, Product ID, Serial number - These values together make up the device ID in the
form USB\VID_<vendor ID>&PID_<product ID>\<serial number>.
l Account - Indicates the tenant to which this device belongs. This is the tenant that contains the
user account that was used to register the device with the database.

Note
This column is hidden by default. To display it in the table, click the gear icon in the upper right
corner of the table, and then select Account.

The leftmost column is intended to select the devices to add to the allowlist: Select the check box for
each device to add, and then click the Add to allowlist button. To select or clear all check boxes,
click the check box in the column header.

You can search or filter the list of devices:

l Click Search at the top of the page and enter a search string. The list displays devices whose
description matches the string you typed.
l Click Filter, and then configure and apply a filter in the dialog box that appears. The list is limited
to devices with the type, vendor ID, product ID, and account that you selected when configuring
the filter. To cancel the filter and list all devices, click Reset to default.

Export the list of USB devices in the database

You can export the list of USB devices that are added to the database.

1. Open the protection plan of a device for editing.

2. Click the arrow icon next to the Device control switch to expand the settings, and then click the
USB devices allowlist row.
3. On the USB devices allowlist page, click Add from database.
4. On the USB devices database management page that appears, click Export.
The standard Browse dialog opens.
5. Select the location to which you want to save the file, enter a new file name if needed, and click
Save.

The list of USB devices is exported to a JSON file.

You can edit the resulting JSON file to add or remove devices from it, and make mass changes of
device descriptions.

Import a list of USB devices to the database

Instead of adding USB devices from the Cyber Protect console, you can import a list of USB devices.
The list is a file in JSON format.

365 © Acronis International GmbH, 2003-2024

Note
You can import JSON files to a database that does not contain the devices described in the file. To
import a modified file to the database from which it was exported, you must clear the database first
because you cannot import duplicate entries. If you export the list of USB devices, modify it, and try
to import to the same database without clearing it, the import will fail.

1. Open the protection plan of a device for editing.

2. Click the arrow icon next to the Device control switch to expand the settings, and then click the
USB devices allowlist row.
3. On the USB devices allowlist page, click Add from database.
4. On the USB devices database management page that appears, click Import.
The dialog Import USB devices from file opens.
5. Use drag and drop (or browse) for the file that you want to import.

The Cyber Protect console checks if the list contains duplicate entries that already exist in the
database and skips them. The USB devices that are not found in the database are appended to it.

List of USB devices on a computer

The Inventory panel of a computer in the Cyber Protect console includes the USB Devices tab. If the
computer is online and the agent for Data Loss Prevention is installed on it, the USB Devices tab
displays a list all USB devices that have ever been connected to that computer.

The USB devices are listed in tree view. The first level of the tree represents a device model. The
second level represents a specific device of that model.

For each device, the list provides the following information:

l Description - The operating system assigns a description when connecting the USB device. This
description can serve as a readable identifier of the device.
A blue icon next to the description of the device indicates that the device is currently attached to
the computer. If the device is not attached to the computer, the icon is grayed out.
l Device ID - The identifier that the operating system assigned to the device. This identifier has the
following format: USB\VID_<vendor ID>&PID_<product ID>\<serial number> where <serial
number> is optional. Examples: USB\VID_0FCE&PID_ADDE\D55E7FCA (device with a serial
number); USB\VID_0FCE&PID_ADDE (device without serial number).

To add devices to the USB devices database, select the check boxes of the desired devices, and then
click the Add to database button.

Excluding processes from access control

The access to Windows clipboard, screenshot capture, printers, and mobile devices is controlled
through hooks injected into processes. If processes are not hooked, the access to these devices will
not be controlled.

366 © Acronis International GmbH, 2003-2024

Note
Excluding processes from access control is not supported on macOS. If a list of excluded processes
is configured in the applied protection plan, it will be ignored.

On the Exclusions page, you can specify a list of processes that will not be hooked. This means that
clipboard (local and redirected), screenshot capture, printer, and mobile device access controls will
not be applied to such processes.

For example, you applied a protection plan that denies access to printers, then started the Microsoft
Word application. An attempt to print from this application will be blocked. But if you add the
Microsoft Word process to the list of exclusions, then the application will not be hooked. As a result,
printing from Microsoft Word will not be blocked, while printing from other applications will still be
blocked.

To add processes to exclusions

1. Open the protection plan of a device for editing:

Click the ellipsis (...) next to the name of the protection plan and select Edit.

Note
Device control must be enabled in the plan, so you can access the Device control settings.

2. Click the arrow next to the Device control switch to expand the settings, and then click the
Exclusions row.
3. On the Exclusions page, in the Processes and folders row, click +Add.
4. Add the processes that you want to exclude from the access control.
For example, C:\Folder\subfolder\process.exe.
You can use wildcards:
l * replaces any number of characters.
l ? replaces one character.
For example:
C:\Folder\*
*\Folder\SubFolder?\*
*\process.exe
5. Click the check mark, and then click Done.
6. In the protection plan, click Save.
7. Restart the processes that you excluded to ensure that the hooks are properly removed.

The excluded processes will have access to clipboard, screenshot capture, printers, and mobile
devices regardless of the access settings for those devices.

To remove a process from exclusions

Open the protection plan of a device for editing:

Click the ellipsis (...) next to the name of the protection plan and select Edit.

367 © Acronis International GmbH, 2003-2024

 Note
Device control must be enabled in the plan, so you can access the Device control settings.

1. Click the arrow next to the Device control switch to expand the settings, and then click the
Exclusions row.
2. On the Exclusions page, click the trash can icon next to the process that you want to remove
from the exclusions.
3. Click Done.
4. In the protection plan, click Save.
5. Restart the process to ensure that hooks are properly injected.

The access settings from the protection plan will be applied to the processes that you removed from
the exclusions.

To edit a process in exclusions

1. Open the protection plan of a device for editing:

Click the ellipsis (...) next to the name of the protection plan and select Edit.

Note
Device control must be enabled in the plan, so you can access the Device control settings.

2. Click the arrow next to the Device control switch to expand the settings, and then click the
Exclusions row.
3. On the Exclusions page, click the Edit icon next to the process that you want to edit.
4. Apply the changes and click the check mark to confirm.
5. Click Done.
6. In the protection plan, click Save.
7. Restart the affected processes to ensure that your changes are applied correctly.

Device control alerts

The device control maintains an event log by tracking user attempts to access controlled device
types, ports, or interfaces. Certain events can raise alerts that are logged in the Cyber Protect
console. For example, the device control module can be configured to prevent the use of removable
devices, with an alert logged whenever a user tries to copy data to or from such a device.

When configuring the device control module, you can enable alerts for most items listed under
device Type (except screenshot capture) or Ports. If alerts are enabled, each attempt by a user to
perform an operation that is not allowed generates an alert. For example, if access to removable
devices is restricted to read-only, and the Show alert option is selected for that device type, an alert
is generated every time a user on a protected computer attempts to copy data to a removable
device.

368 © Acronis International GmbH, 2003-2024

To view alerts in the Cyber Protect console, go to Monitoring > Alerts. Within each device control
alert, the console provides the following information about the respective event:

l Type—Warning.
l Status—Displays “Peripheral device access is blocked”.
l Message—Displays “Access to '<device type or port>' on '<computer name>' is blocked”. For
example, “Access to 'Removable' on 'accountant-pc' is blocked”.
l Date and time—The date and time that the event occurred.
l Device—The name of the computer on which the event occurred.
l Plan name—The name of the protection plan that caused the event.
l Source—The device type or port involved in the event. For example, in the event of a denied user
attempt to access a removable device, this field reads Removable device.
l Action—The operation that caused the event. For example, in the event of a denied user attempt
to copy data to a device, this field reads Write. For more information, see Action field values.
l Name—The name of the event target object, such as the file the user attempted to copy or the
device the user attempted to use. Not displayed if the target object cannot be identified.
l Information—Additional information about the event target device, such as the device ID for
USB devices. Not displayed if no additional information about the target device is available.
l User—The name of the user who caused the event.
l Process—The fully qualified path to the executable file of the application that caused the event.
In some cases, the process name might be displayed instead of the path. Not displayed if process
information is not available.

If an alert applies to a USB device (including removable devices and encrypted removable devices),
then, directly from the alert, the administrator can add the device to the allowlist, which prevents
the device control module from restricting access to that particular device. Clicking Allow this USB
device adds it to the USB devices allowlist in the device control module’s configuration, and also
adds it to the USB devices database for further reference.

See also steps to view device control alerts.

Action field values

Alert Action field can contain the following values:

l Read - Get data from the device or port.

l Write - Send data to the device or port.
l Format - Direct access (formatting, check disk, etc.) to the device. In the case of a port, applies to
the device connected to that port.
l Eject - Remove the device from the system or eject the media from the device. In the case of a
port, applies to the device connected to that port.
l Print - Send a document to the printer.
l Copy audio - Copy/paste audio data via the local clipboard.
l Copy file - Copy/paste a file via the local clipboard.

369 © Acronis International GmbH, 2003-2024

l Copy image - Copy/paste an image via the local clipboard.
l Copy text - Copy/paste text via the local clipboard.
l Copy unidentified content - Copy/paste other data via the local clipboard.
l Copy RTF data (image) - Copy/paste an image via the local clipboard using Rich Text Format.
l Copy RTF data (file) - Copy/paste a file via the local clipboard using Rich Text Format.
l Copy RTF data (text, image) - Copy/paste text along with an image via the local clipboard using
Rich Text Format.
l Copy RTF data (text, file) - Copy/paste text along with a file via the local clipboard using Rich
Text Format.
l Copy RTF data (image, file) - Copy/paste an image along with a file via the local clipboard using
Rich Text Format.
l Copy RTF data (text, image, file) - Copy/paste text along with an image and a file via the local
clipboard using Rich Text Format.
l Delete - Delete data from the device (for example, a removable device, a mobile device, and so
on).
l Device access - Access to some device or port (for example, a Bluetooth device, a USB port, and
so on).
l Incoming audio - Copy/paste audio data from the client computer to the hosted session via the
redirected clipboard.
l Incoming file - Copy/paste a file from the client computer to the hosted session via the
redirected clipboard.
l Incoming image - Copy/paste an image from the client computer to the hosted session via the
redirected clipboard.
l Incoming text - Copy/paste text from the client computer to the hosted session via the
redirected clipboard.
l Incoming unidentified content - Copy/paste other data from the client computer to the hosted
session via the redirected clipboard.
l Incoming RTF data (image) - Copy/paste an image from the client computer to the hosted
session via the redirected clipboard using Rich Text Format.
l Incoming RTF data (file) - Copy/paste a file from the client computer to the hosted session via
the redirected clipboard using Rich Text Format.
l Incoming RTF data (text, image) - Copy/paste text along with an image from the client
computer to the hosted session via the redirected clipboard using Rich Text Format.
l Incoming RTF data (text, file) - Copy/paste text along with a file from the client computer to the
hosted session via the redirected clipboard using Rich Text Format.
l Incoming RTF data (image, file) - Copy/paste an image along with a file from the client
computer to the hosted session via the redirected clipboard using Rich Text Format.
l Incoming RTF data (text, image, file) - Copy/paste text along with an image and a file from the
client computer to the hosted session via the redirected clipboard using Rich Text Format.
l Insert - Connect a USB device or a FireWire device.

370 © Acronis International GmbH, 2003-2024

l Outgoing audio - Copy/paste audio data from the hosted session to the client computer via the
redirected clipboard.
l Outgoing file - Copy/paste a file from the hosted session to the client computer via the
redirected clipboard.
l Outgoing image - Copy/paste an image from the hosted session to the client computer via the
redirected clipboard.
l Outgoing text - Copy/paste text from the hosted session to the client computer via the
redirected clipboard.
l Outgoing unidentified content - Copy/paste other data from the hosted session to the client
computer via the redirected clipboard.
l Outgoing RTF data (image) - Copy/paste an image from the hosted session to the client
computer via the redirected clipboard using Rich Text Format.
l Outgoing RTF data (file) - Copy/paste a file from the hosted session to the client computer via
the redirected clipboard using Rich Text Format.
l Outgoing RTF data (text, image) - Copy/paste text along with an image from the hosted session
to the client computer via the redirected clipboard using Rich Text Format.
l Outgoing RTF data (text, file) - Copy/paste text along with a file from the hosted session to the
client computer via the redirected clipboard using Rich Text Format.
l Outgoing RTF data (image, file) - Copy/paste an image along with a file from the hosted session
to the client computer via the redirected clipboard using Rich Text Format.
l Outgoing RTF data (text, image, file) - Copy/paste text along with an image and a file from the
hosted session to the client computer via the redirected clipboard using Rich Text Format.
l Rename - Rename files on a device (for example, on removable devices, mobile devices, and
others).

Wiping data from a managed workload

Note
Remote wipe is available with the Advanced Security pack.

Remote wipe allows a Cyber Protection service administrator and a machine owner to delete the
data on a managed machine – for example, if it gets lost or stolen. Thus, any unauthorized access to
sensitive information will be prevented.

Remote wipe is only available for machines running Windows versions 10 and later. To receive the
wipe command, the machine must be turned on and connected to the Internet.

371 © Acronis International GmbH, 2003-2024

To wipe data from a machine

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the machine whose data you want to wipe.

Note
You can wipe data from one machine at a time.

3. Click Details, and then click Wipe data.

If the machine that you selected is offline, the Wipe data option is inaccessible.
4. Confirm your choice.
5. Enter the credentials of this machine's local administrator, and then click Wipe data.

Note
You can check the details about the wiping process and who started it in Monitoring >
Activities.

Viewing workloads managed by RMM integrations

Note
This feature is only available if the Advanced Automation service is enabled.

When you integrate an RMM platform as part of the Advanced Automation service, you can view
and monitor information from devices that are managed by the RMM platform. This information is
available in the Cyber Protect console by navigating to Devices.

To view workloads managed by RMM integrations

1. Go to Devices > All devices.

2. (Optional) Sort the RMM integration column to locate the relevant integrations.

372 © Acronis International GmbH, 2003-2024

3. Select the relevant workload.
4. In the Actions pane, select Details.
5. In the displayed pane, one of three options is displayed, according to your configured workload:
l If Acronis services are defined for the workload without RMM integration: If the workload is
configured to work only with Acronis services, no RMM integration information is displayed.
l If Acronis services and an RMM integration is configured for the workload: The Acronis
services and RMM integration details are located in two tabs, Overview and RMM
integration. Click RMM integration to view the integration details, including the workload
name and type (provided by the RMM platform), description and location. In addition, any
installed and enabled RMM agent add-ons are also shown.
l If the workload is configured with an RMM integration only: The RMM integration details are
displayed, including the workload name and type (provided by the RMM platform), description
and location. In addition, any installed and enabled RMM agent add-ons are also shown.
Note that when the workload is configured with RMM integration (either in tandem with Acronis
services or with an RMM integration only), you can do the following:
l Initiate a remote connection (available for Datto RMM, N-able N-central, N-able RMM
integrations)
l Review installed add-ons on the third party RMM device (available for N-able RMM only)
l Directly access the third party RMM device's details (available for Datto RMM, N-able N-
central, NinjaOne)

CyberApp workloads
CyberApp workloads are created by ISVs (Independent software vendors) and appear in the Cyber
Protect console after you enable a CyberApp integration. The following conditions must be met:

l The Workloads and actions extension point must be enabled in the CyberApp.
l At least one Workload type must be defined in the CyberApp.
l The connector service hosted by the ISV must ensure that the CyberApp workloads are added
and updated to the Acronis platform.

For more information about Vendor Portal and creating CyberApps, see the Vendor Portal User
Guide.

Aggregated workloads
A physical workload may have Cyber Protect agent and one or several CyberApp agents installed at
the same time. In this case, the same workload will have more than one representation on the All
Devices screen - a separate record will be shown for the Acronis workload, and for each CyberApp
workload. If the automatic merging of workloads is enabled and configured from Vendor Portal or
from the Cyber Protect console, the system will compare the host addresses and the MAC addresses
of the Acronis workloads and the CyberApp workloads, and will merge all representations into a
single aggregated workload. You can also manually merge and unmerge workloads in the Cyber
Protect console.

373 © Acronis International GmbH, 2003-2024

Working with CyberApp workloads
Apart from the standard actions that are built-in to the Cyber Protect console, you can perform
actions that become available after the CyberApp workloads appear in the console: manually merge
workloads into an aggregated workload and perform custom actions that are configured in the
CyberApp.

Merge

Prerequisites
l Workloads from different sources are available for the tenant.

You can manually merge an Acronis workload with one or several CyberApp workloads into a single
aggregated workload.

To manually merge workloads into an aggregated workload

1. In the All devices screen, select the workloads that you want to merge.

Note
The merge action is displayed if you select workloads from different sources, such as an Acronis
workload and a CyberApp workload.

2. Click Merge workloads.

Perform custom actions

Prerequisites
l A CyberApp integration that has Workload actions defined is enabled for the tenant.

Custom actions are actions that are configured in the CyberApp, and become available for the
corresponding CyberApp workload when you enable the CyberApp integration for the tenant.

To perform custom actions

1. In the All devices screen, click the workload.

2. Click Integrated App actions.
3. Click the action.

Working with aggregated workloads

Apart from the standard actions that are built-in to the Cyber Protect console, you can perform the
following operations with aggregated workloads: view details, unmerge source workloads, and
perform custom actions that are configured in the CyberApps.

View details

374 © Acronis International GmbH, 2003-2024

Prerequisites
l At least one aggregated workload is available for the tenant.

To view the details of an aggregated workload

1. In the All devices screen, click the aggregated workload.

2. Click Details.
The details of the aggregated workload are separated into tabs. Each tab shows the details for
each workload representation.

Unmerge

Prerequisites
l At least one aggregated workload is available for the tenant.

When you unmerge an aggregated workload, it will no longer be displayed in the devices list.
Instead, you will view a separate entry for each source workload that has been merged into the
aggregate workload.

To unmerge an aggregated workload

1. In the All devices screen, click the aggregated workload that you want to unmerge.
2. Click Unmerge source workloads.
3. In the confirmation window, click Unmerge.

Perform custom actions

Prerequisites
l At least one CyberApp integration that has Workload actions defined is enabled for the tenant.

Custom actions are actions that are configured in the CyberApps and become available for the
corresponding CyberApp workload when you enable the CyberApp integration for the tenant.

To perform custom actions

1. In the All devices screen, click the workload.

2. Click Integrated App actions.
3. Depending on the available custom actions, do one of the following.
l If the aggregated workload has one CyberApp workload, click the action.
l If the aggregated workload has more than one CyberApp workload, click the name of the
CyberApp, and then click the action.

Linking workloads to specific users

Note
This feature is only available if the Advanced Automation service is enabled.

375 © Acronis International GmbH, 2003-2024

By linking a workload to a specific user, you can automatically link the workload to new service desk
tickets created by or assigned to the user.

To link a workload to a user

1. Go to Devices > All devices, and then select the relevant workload.
2. In the Actions pane, select Link to a user.
3. Select the relevant user.
You can also change the selected user for existing linked workloads, as required.
4. Click Done. The selected user is now displayed in the Linked user column.

To unlink a workload from a user

1. Go to Devices > All devices, and then select the relevant workload.
2. In the Actions pane, select Link to a user.
3. Click Unlink user.
4. Click Done.

Find the last logged in user

In order for the administrators to manage devices, they have to identify which user is and was
logged in to a device. This information is displayed in the Dashboard or in the workloads details.

You can enable or disable displaying the Last login information in Remote management plans.

In the Dashboard:

1. Click Devices. The All devices window is displayed.

2. In the Last login column, the name of the user who logged in the last time for each device is
displayed.
3. In the Last login time column, the time when the user logged in the last time for each device is
displayed.

In Device Details:

1. Click Devices. The All devices window is displayed.

2. Click on the device for which you want to verify the details.
3. Click the Details icon. The name of the user, the date and time of the last logins for the selected
device is displayed in the Last users logged in section.

Note
In the Last users logged in section there will be displayed up to 5 different users who logged in to
the device.

To show or hide Last login and Last login time columns In the Dashboard

376 © Acronis International GmbH, 2003-2024

1. Click Devices. The All devices window is displayed.
2. Click the gear icon in the upper right corner, and do one of the following in the General section:
l Enable the Last login and Last login time columns, if you want to show them on the
Dashboard.
l Disable the Last login and Last login time columns, if you want to hide them from the
Dashboard.

377 © Acronis International GmbH, 2003-2024

Managing the backup and recovery of
workloads and files
The backup module enables backup and recovery of physical and virtual machines, files, and
databases to local or cloud storage.

Backup
A protection plan with the Backup module enabled is a set of rules that specify how the given data
will be protected on a given machine.

A protection plan can be applied to multiple machines at the time of its creation, or later.

To create the first protection plan with the Backup module enabled

1. Select the machines that you want to back up.

2. Click Protect.
Protection plans that are applied to the machine are shown. If the machine does not have any
plans already assigned to it, then you will see the default protection plan that can be applied.
You can adjust the settings as needed and apply this plan or create a new one.
3. To create a new plan, click Create plan. Enable the Backup module and unroll the settings.

378 © Acronis International GmbH, 2003-2024

4. [Optional] To modify the protection plan name, click the default name.
5. [Optional] To modify the Backup module parameters, click the corresponding setting of the
protection plan panel.
6. [Optional] To modify the backup options, click Change next to Backup options.
7. Click Create.

To apply an existing protection plan

1. Select the machines that you want to back up.

2. Click Protect. If a common protection plan is already applied to the selected machines, click Add
plan.
The software displays previously created protection plans.

379 © Acronis International GmbH, 2003-2024

3. Select a protection plan to apply.
4. Click Apply.

Protection plan cheat sheet

The following table summarizes the available protection plan parameters. Use the table to create a
protection plan that best fits your needs.

ITEMS TO
BACK UP WHERE SCHEDULE HOW LONG TO
WHAT TO BACK UP TO BACK
Selection Backup schemes KEEP
UP
methods

Cloud Always incremental By backup age

Direct
(Single-file) (single rule/per
selection Local
Disks/volumes (physical backup set)
folder Always full
machines1) Policy rules
Network Weekly full, Daily By number of
File filters backups
folder incremental

1A machine that is backed up by an agent installed in the operating system.

380 © Acronis International GmbH, 2003-2024

 NFS*

Secure
Zone**
Monthly full, Weekly
Cloud
differential, Daily
Local incremental (GFS)

Disks/volumes (virtual Policy rules folder

Custom (F-D-I)
machines1) File filters Network
folder

NFS*

Cloud

Local
Direct folder Always incremental
selection (Single-file)
Files (physical machines Network
only2) Policy rules folder Always full By total size of
File filters NFS* Weekly full, Daily backups***

Secure incremental Keep indefinitely

Zone** Monthly full, Weekly

Local differential, Daily

folder incremental (GFS)

Direct Custom (F-D-I)

ESXi configuration Network
selection
folder

NFS*

Websites (files and MySQL Direct

Cloud —
databases) selection

Always full
System state
Cloud Weekly full, daily
Local incremental
Direct
SQL databases folder Custom (F-I)
selection
Network Always incremental
folder (Single-file) - only for SQL
Exchange databases
databases

Microsoft Direct Always incremental

Mailboxes Cloud
365 selection (Single-file)

1A virtual machine that is backed up at a hypervisor level by an external agent such as Agent for VMware or Agent for

Hyper-V. A virtual machine with an agent inside is treated as physical from the backup standpoint.
2A machine that is backed up by an agent installed in the operating system.

381 © Acronis International GmbH, 2003-2024

 Local
(local Agent folder
for Microsoft
365) Network
folder

Mailboxes

(cloud Agent
for Microsoft
Direct
365)
selection
Public folders
Cloud Up to 6 backups per day
Teams

OneDrive files Direct

selection
SharePoint
Online data Policy rules

Gmail Direct
mailboxes selection

Google Google Drive

Direct Cloud Up to 6 backups per day
Workspace files
selection
Shared drive
Policy rules
files

* Backup to NFS shares is not available in Windows.

** Secure Zone cannot be created on a Mac.

*** The By total size of backups retention rule is not available with the Always incremental
(single-file) backup scheme or when backing up to the cloud storage.

Selecting data to back up

Selecting entire machine

A backup of an entire machine is a backup of all its non-removable disks. For more information
about disk backup, refer to "Selecting disks or volumes" (p. 383).

Limitations
l Disk-level backups are not supported for encrypted APFS volumes that are locked. During a
backup of an entire machine, such volumes are skipped.
l The OneDrive root folder is excluded from backup operations by default. If you select to back up
specific OneDrive files and folders, they will be backed up. Files that are not available on the
device will have invalid contents in the backup set.

382 © Acronis International GmbH, 2003-2024

Selecting disks or volumes
A disk-level backup contains a copy of a disk or a volume in a packaged form. From a disk-level
backup, you can recover disks, volumes, folders, and files.

You can select the disks or volumes to back up for each individual workload in the protection plan
(direct selection) or you can configure policy rules for multiple workloads. Additionally, you can
exclude specific files from a backup, or include only specific files to it, by configuring file filters. For
more information, see "File filters (Inclusions/Exclusions)" (p. 438).

To select disks or volumes

Direct selection

Direct selection is available only for physical machines.

1. In What to back up, select Disks/volumes.

2. Click Items to back up.
3. In Select items for backup, select Directly.
4. For each of the workloads included in the protection plan, select the check boxes next to the
disks or volumes to back up.
5. Click Done.

By policy rules

1. In What to back up, select Disks/volumes.

2. Click Items to back up.
3. In Select items for backup, select Using policy rules.
4. Select any of the predefined rules, type your own rules, or combine both.
For more information about the available policy rules, see "Policy rules for disks and volumes" (p.
385).
The policy rules will be applied to all workloads that are included in the protection plan.
If none of the specified rules can be applied to a workload, the backup of that workload fails.
5. Click Done.

Limitations
l Disk-level backups are not supported for encrypted APFS volumes that are locked. During a
backup of an entire machine, such volumes are skipped.
l The OneDrive root folder is excluded from backup operations by default. If you select to back up
specific OneDrive files and folders, they will be backed up. Files that are not available on the
device will have invalid contents in the backup set.
l You can back up disks that are connected via the iSCSI protocol to a physical machine. However,
limitations apply if you use Agent for VMware or Agent for Hyper-V for backing up the iSCSI-
connected disks. For more information, see "Limitations" (p. 32).

383 © Acronis International GmbH, 2003-2024

What does a disk or volume backup store?
A disk or volume backup stores a disk or a volume file system as a whole and includes all of the
information necessary for the operating system to boot. It is possible to recover disks or volumes as
a whole from such backups as well as individual folders or files.

With the sector-by-sector (raw mode) backup option enabled, a disk backup stores all the disk
sectors. The sector-by-sector backup can be used for backing up disks with unrecognized or
unsupported file systems and other proprietary data formats.

Windows
A volume backup stores all files and folders of the selected volume independent of their attributes
(including hidden and system files), the boot record, the file allocation table (FAT) if it exists, the root
and the zero track of the hard disk with the master boot record (MBR).

A disk backup stores all volumes of the selected disk (including hidden volumes such as the vendor's
maintenance partitions) and the zero track with the master boot record.

The following items are not included in a disk or volume backup (as well as in a file-level backup):

l The swap file (pagefile.sys) and the file that keeps the RAM content when the machine goes into
hibernation (hiberfil.sys). After recovery, the files will be re-created in the appropriate place with
the zero size.
l If the backup is performed under the operating system (as opposed to bootable media or backing
up virtual machines at a hypervisor level):
o Windows shadow storage. The path to it is determined in the registry value VSS Default
Provider which can be found in the registry key HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup. This
means that in operating systems starting with Windows Vista, Windows Restore Points are not
backed up.
o If the Volume Shadow Copy Service (VSS) backup option is enabled, files and folders that are
specified in the HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot
registry key.

Linux
A volume backup stores all files and directories of the selected volume independent of their
attributes, a boot record, and the file system super block.

A disk backup stores all disk volumes as well as the zero track with the master boot record.

Mac
A disk or volume backup stores all files and directories of the selected disk or volume, plus a
description of the volume layout.

384 © Acronis International GmbH, 2003-2024

The following items are excluded:

l System metadata, such as the file system journal and Spotlight index
l The Trash
l Time machine backups

Physically, disks and volumes on a Mac are backed up at a file level. Bare metal recovery from disk
and volume backups is possible, but the sector-by-sector backup mode is not available.

Policy rules for disks and volumes

When you select disks or volumes to back up, you can use the following policy rules, according to
the operating system of the protected workload.

Windows

l [All Volumes] selects all volumes on the machine.

l Drive letter (for example, C:\) selects the volume with the specified drive letter.
l [Fixed Volumes (physical machines)] selects all volumes of a physical machine, other than
removable media. Fixed volumes include volumes on SCSI, ATAPI, ATA, SSA, SAS, and SATA
devices, and on RAID arrays.
l [BOOT+SYSTEM] selects the system and boot volumes. This is the minimal combination from which
you can recover an operating system.
l [Disk 1] selects the first disk of the machine, including all volumes on that disk. To select another
disk, type the corresponding number.

Linux

l [All Volumes] selects all mounted volumes on the machine.

l /dev/hda1 selects the first volume on the first IDE hard disk.
l /dev/sda1 selects the first volume on the first SCSI hard disk.
l /dev/md1 selects the first software RAID hard disk.
l To select other basic volumes, specify /dev/xdyN, where:
o "x" corresponds to the disk type
o "y" corresponds to the disk number (a for the first disk, b for the second disk, and so on)
o "N" is the volume number.
l To select a logical volume, specify its path as it appears after running the ls /dev/mapper
command under the root account.
For example:

[root@localhost ~]# ls /dev/mapper/

control vg_1-lv1 vg_1-lv2

This output shows two logical volumes, lv1 and lv2, that belong to the volume group vg_1. To
back up these volumes, specify:
/dev/mapper/vg_1-lv1
/dev/mapper/vg-l-lv2

385 © Acronis International GmbH, 2003-2024

macOS

l [All Volumes] selects all mounted volumes on the machine.

l [Disk 1] Selects the first disk of the machine, including all volumes on that disk. To select another
disk, specify the corresponding number.

Selecting files or folders

Use file-level backup to protect only specific data, for example, the files in your current project. File-
level backups are smaller than disk-level backups and save storage space.

Important
You cannot recover an operating system from a file-level backup.

You can select the files and folders to back up for each individual workload in the protection plan
(direct selection) or you can configure policy rules for multiple workloads. Additionally, you can
exclude specific files from a backup, or include only specific files in it, by configuring the filters. For
more information, see "File filters (Inclusions/Exclusions)" (p. 438).

To select files or folders

Direct selection

1. In What to back up, select Files/folders.

2. In Items to back up, click Specify.
3. In Select items for backup, select Directly.
4. Specify the files or folders to back up for each workload in the protection plan.
a. Click Select files and folders.
b. Click Local folder or Network folder.
Network folders must be accessible from the selected machine.
When you select Network folder as a source, you can back up data from network-attached
storages (NAS), such as NetApp devices. NAS devices from all vendors are supported.
c. In the folder tree, navigate to the required files or folders.
Alternatively, specify the path to them, and then click the arrow button.
d. [For shared folders] When prompted, specify the access credentials to the shared folder.
Backing up folders with anonymous access is not supported.
e. Select the required files and folders.
f. Click Done.

By policy rules

1. In What to back up, select Files/folders.

2. In Items to back up, click Specify.
3. In Select items for backup, select Using policy rules.
4. Select any of the predefined rules, type your own rules, or combine both.

386 © Acronis International GmbH, 2003-2024

 For more information about the available policy rules, see "Policy rules for files and folders" (p.
387).
The policy rules will be applied to all workloads that are included in the protection plan.
If none of the specified rules can be applied to a workload, the backup of that workload fails.
5. Click Done.

Limitations
l You can select files and folders when you back up physical machines or virtual machines on
which an agent is installed (agent-based backup). File-level backup is not available for virtual
machines that you back up in the agentless mode. For more information about the differences
between these types of backup, see "Agent-based and agentless backup" (p. 62).
l The OneDrive root folder is excluded from backup operations by default. If you select to back up
specific OneDrive files and folders, they will be backed up. Files that are not available on the
device will have invalid contents in the backup set.
l You can back up files and folders that are located on disks connected via the iSCSI protocol to a
physical machine. Some limitations apply if you use Agent for VMware or Agent for Hyper-V for
backing up the data on the iSCSI-connected disks.

Policy rules for files and folders

When you select files or folders to back up, you can use the following policy rules, according to the
operating system of the protected workload.

Windows

l Full path to a file or folder. For example, D:\Work\Text.doc or C:\Windows.

l Predefined rules:
o [All Files] selects all files on all volumes of the machine.
o [All Profiles Folder] selects the folder in which all user profiles are located. For example,
C:\Users or C:\Documents and Settings.
l Environment variables:
o %ALLUSERSPROFILE% selects the folder in which the common data of all user profiles is located.
For example, C:\ProgramData or C:\Documents and Settings\All Users.
o %PROGRAMFILES% selects the Program Files folder. For example, C:\Program Files.
o %WINDIR% selects the Windows folder. For example, C:\Windows.
You can use other environment variables or a combination of environment variables and text. For
example, to select the Java folder in the Program Files folder, specify: %PROGRAMFILES%\Java.

Linux

l Full path to a file or directory.

For example, to back up the file.txt file on volume /dev/hda3 that is mounted on
/home/usr/docs, specify /dev/hda3/file.txt or /home/usr/docs/file.txt.
l Predefined rules:

387 © Acronis International GmbH, 2003-2024

 o [All Profiles Folder] selects /home. By default, all user profiles are stored in this folder.
o /home selects the home directory of the common users.
o /root selects the root user's home directory.
o /usr selects the directory for all user-related programs.
o /etc selects the directory for system configuration files.

macOS

l Full path to a file or directory.

For example:
o To back up file.txt on a user's desktop, specify /Users/<user name>/Desktop/file.txt.
o To back up the Desktop, the Documents, and the Downloads folders of a user, specify /Users/<user
name>/Desktop, /Users/<user name>/Documents, and /Users/<user name>/Downloads.
o To back up the home folders of all users who have an account on this machine, specify /Users.
o To back up the folder in which the applications are installed, specify /Applications.
l Predefined rules
o [All Profiles Folder] selects /Users. By default, all user profiles are stored in this folder.

Selecting system state

Note
System state backup is available for machines running Windows 7 or later on which Agent for
Windows is installed. System state backup is not available for virtual machines that are backed up at
the hypervisor level (agentless backup).

To back up system state, in What to back up, select System state.

A system state backup is comprised of the following files:

l Task scheduler configuration

l VSS Metadata Store
l Performance counter configuration information
l MSSearch Service
l Background Intelligent Transfer Service (BITS)
l The registry
l Windows Management Instrumentation (WMI)
l Component Services Class registration database

Selecting ESXi configuration

A backup of an ESXi host configuration enables you to recover an ESXi host to bare metal. The
recovery is performed under bootable media.

The virtual machines running on the host are not included in the backup. They can be backed up
and recovered separately.

388 © Acronis International GmbH, 2003-2024

A backup of an ESXi host configuration includes:

l The bootloader and boot bank partitions of the host.

l The host state (configuration of virtual networking and storage, SSL keys, server network settings,
and local user information).
l Extensions and patches installed or staged on the host.
l Log files.

Prerequisites
l SSH must be enabled in the Security Profile of the ESXi host configuration.
l You must know the password for the 'root' account on the ESXi host.

Limitations
l ESXi configuration backup is not supported for hosts running VMware ESXi 7.0 and later.
l An ESXi configuration cannot be backed up to the cloud storage.

To select an ESXi configuration

1. Click Devices > All devices, and then select the ESXi hosts that you want to back up.
2. Click Protect.
3. In What to back up, select ESXi configuration.
4. In ESXi 'root' password, specify a password for the 'root' account on each of the selected hosts
or apply the same password to all of the hosts.

Continuous data protection (CDP)

Continuous data protection (CDP) is part of the Advanced Backup pack. It backs up critical data
immediately after this data is changed, ensuring that no changes will be lost if your system fails
between two scheduled backups. You can configure Continuous data protection for the following
data:

l Files or folders in specific locations

l Files modified by specific applications

Continuous data protection is supported only for the NTFS file system and the following operating
systems:

l Desktop: Windows 7 and later

l Server: Windows Server 2008 R2 and later

Only local folders are supported. Network folders cannot be selected for Continuous data
protection.

Continuous data protection is not compatible with the Application backup option.

389 © Acronis International GmbH, 2003-2024

How it works
Changes in the files and folders that are tracked by Continuous data protection are immediately
saved to a special CDP backup. There is only one CDP backup in a backup set, and it is always the
most recent one.

When a scheduled regular backup starts, Continuous data protection is put on hold because the
latest data is to be included in the scheduled backup. When the scheduled backup finishes,
Continuous data protection resumes, the old CDP backup is deleted, and a new CDP backup is
created. Thus, the CDP backup always stays the most recent backup in the backup set and stores
only the latest state of the tracked files or folders.

390 © Acronis International GmbH, 2003-2024

If your machine crashes during a regular backup, Continuous data protection resumes automatically
after the machine restarts and creates a CDP backup on top of the last successful scheduled
backup.

Continuous data protection requires that at least one regular backup is created before the CDP
backup. That is why, when you run a protection plan with Continuous data protection for the first
time, a full backup is created, and a CDP backup is immediately added on top of it. If you enable the
Continuous data protection option for an existing protection plan, the CDP backup is added to the
existing backup set.

Note
Continuous Data protection is enabled by default for protection plans that you create from the
Devices tab, if the Advanced Backup functionality is enabled for you and you are not using other
Advanced Backup features for the selected machines. If you already have a plan with Continuous
data protection for a selected machine, Continuous data protection will not be enabled by default
for that machine in newly created plans.
Continuous data protection is not enabled by default for plans created for device groups.

Supported data sources

You can configure Continuous data protection with the following data sources:

l Entire machine
l Disks/volumes
l Files/folders

391 © Acronis International GmbH, 2003-2024

After selecting the data source in What to backup section in the protection plan, in the Items to
protect continuously section, select the files, folders, or applications for Continuous data
protection. For more information on how to configure Continuous data protection, refer to
"Configuring a CDP backup" (p. 392).

Supported destinations
You can configure Continuous data protection with the following destinations:

l Local folder
l Network folder
l Cloud storage
l Acronis Cyber Infrastructure
l Location defined by a script

Note
You can define by a script only the locations listed above.

Configuring a CDP backup

You can configure Continuous data protection in the Backup module of a protection plan. For more
information on how to create a protection plan, refer to "Creating a protection plan" (p. 206).

To configure the Continuous data protection settings

1. In the Backup module of a protection plan, enable the Continuous data protection (CDP)
switch.
This switch is available only for the following data sources:
l Entire machine
l Disk/volumes
l Files/folders
2. In Items to protect continuously, configure Continuous data protection for Applications or
Files/folders, or both.
l Click Applications to configure CDP backup for files that are modified by specific applications.
You can select applications from predefined categories or add other applications by specifying
the path to the their executable file, for example:
o C:\Program Files\Microsoft Office\Office16\WINWORD.EXE
o *:\Program Files (x86)\Microsoft Office\Office16\WINWORD.EXE
l Click Files/folders to configure CDP backup for files in specific locations.
You can define these locations by using selection rules or by selecting the files and folders
directly.
o [For all machines] To create a selection rule, use the text box.
You can use the full paths to files or paths with wildcard characters (* and ?). The asterisk
matches zero or more characters. The question mark matches a single character.

392 © Acronis International GmbH, 2003-2024

 Important
To create a CDP backup for a folder, you must specify its content by using the asterisk
wildcard character:
Correct path:D:\Data\*
Incorrect path: D:\Data\

o [For online machines] To select files and folders directly:

n In Machine to browse from, select the machine on which the files or folders reside.
n Click Select files and folders to browse the selected machine.
Your direct selection creates a selection rule. If you apply the protection plan to multiple
machines and a selection rule is not valid for a machine, it will be skipped on this
machine.
3. In the protection plan pane, click Create.

As a result, the data that you specified will be backed up continuously between the scheduled
backups.

Selecting a destination
Click Where to back up, and then select one of the following:

l Cloud storage
Backups will be stored in the cloud data center.
l Local folders
If a single machine is selected, browse to a folder on the selected machine or type the folder
path.
If multiple machines are selected, type the folder path. Backups will be stored in this folder on
each of the selected physical machines or on the machine where the agent for virtual machines is
installed. If the folder does not exist, it will be created.
l Network folder
This is a folder shared via SMB/CIFS/DFS.
Browse to the required shared folder or enter the path in the following format:
o For SMB/CIFS shares: \\<host name>\<path>\ or smb://<host name>/<path>/
o For DFS shares: \\<full DNS domain name>\<DFS root>\<path>
For example, \\example.company.com\shared\files
Then, click the arrow button. If prompted, specify the user name and password for the shared
folder. You can change these credentials at any time by clicking the key icon next to the folder
name.
Backing up to a folder with anonymous access is not supported.
l Public cloud
This option is available as part of the Advanced Backup pack.

393 © Acronis International GmbH, 2003-2024

 It enables you to configure a direct backup to a public cloud compatible storage, without the need
to deploy additional components (such as Microsoft Azure or other virtual machines as
gateways). Select and connect to the relevant public cloud, as required.
For more information, see "Backing up workloads to public clouds" (p. 513).
l NFS folder (available for machines running Linux or macOS)
Verify that the nfs-utils package is installed on the Linux server where the Agent for Linux is
installed.
Browse to the required NFS folder or enter the path in the following format:
nfs://<host name>/<exported folder>:/<subfolder>
Then, click the arrow button.

Note
It is not possible to back up to an NFS folder protected with a password.

l Secure Zone (available if it is present on each of the selected machines)

Secure Zone is a secure partition on a disk of the backed-up machine. This partition has to be
created manually prior to configuring a backup. For information about how to create Secure
Zone, its advantages and limitations, refer to "About Secure Zone" (p. 395).

Advanced storage option

Note
This functionality is available only in the Advanced edition of the Cyber Protection service.

Defined by a script (available for machines running Windows)

You can store each machine's backups in a folder defined by a script. The software supports scripts
written in JScript, VBScript, or Python 3.5. When deploying the protection plan, the software runs the
script on each machine. The script output for each machine should be a local or network folder
path. If a folder does not exist, it will be created (limitation: scripts written in Python cannot create
folders on network shares). On the Backup storage tab, each folder is shown as a separate backup
location.

In Script type, select the script type (JScript, VBScript, or Python), and then import, or copy and
paste the script. For network folders, specify the access credentials with the read/write permissions.

Examples:

l The following JScript script outputs the backup location for a machine in the format
\\bkpsrv\<machine name>:

WScript.Echo("\\\\bkpsrv\\" + WScript.CreateObject("WScript.Network").ComputerName);

As a result, the backups of each machine will be saved in a folder of the same name on the server
bkpsrv.

394 © Acronis International GmbH, 2003-2024

l The following JScript script outputs the backup location in a folder on the machine where the
script runs:

WScript.Echo("C:\\Backup");

As a result, the backups of this machine will be saved in the folder C:\Backup on the same
machine.

Note
The location path in these scripts is case-sensitive. Therefore, C:\Backup and C:\backup are
displayed as different locations in the Cyber Protect console. Also, use upper case for the drive
letter.

About Secure Zone

Secure Zone is a secure partition on a disk of the backed-up machine. It can store backups of disks
or files of this machine.

Should the disk experience a physical failure, the backups located in the Secure Zone may be lost.
That's why Secure Zone should not be the only location where a backup is stored. In enterprise
environments, Secure Zone can be thought of as an intermediate location used for backup when an
ordinary location is temporarily unavailable or connected through a slow or busy channel.

Why use Secure Zone?

Secure Zone:

l Enables recovery of a disk to the same disk where the disk's backup resides.
l Offers a cost-effective and handy method for protecting data from software malfunction, virus
attack, human error.
l Eliminates the need for a separate media or network connection to back up or recover the data.
This is especially useful for roaming users.
l Can serve as a primary destination when using replication of backups.

Limitations
l Secure Zone cannot be organized on a Mac.
l Secure Zone is a partition on a basic disk. It cannot be organized on a dynamic disk or created as
a logical volume (managed by LVM).
l Secure Zone is formatted with the FAT32 file system. Because FAT32 has a 4-GB file size limit,
larger backups are split when saved to Secure Zone. This does not affect the recovery procedure
and speed.

395 © Acronis International GmbH, 2003-2024

How creating Secure Zone transforms the disk
l Secure Zone is always created at the end of the hard disk.
l If there is no or not enough unallocated space at the end of the disk, but there is unallocated
space between volumes, the volumes will be moved to add more unallocated space to the end of
the disk.
l When all unallocated space is collected but it is still not enough, the software will take free space
from the volumes you select, proportionally reducing the volumes' size.
l However, there should be free space on a volume, so that the operating system and applications
can operate; for example, create temporary files. The software will not decrease a volume where
free space is or becomes less than 25 percent of the total volume size. Only when all volumes on
the disk have 25 percent or less free space, will the software continue decreasing the volumes
proportionally.

As is apparent from the above, specifying the maximum possible Secure Zone size is not advisable.
You will end up with no free space on any volume, which might cause the operating system or
applications to work unstably and even fail to start.

Important
Moving or resizing the volume from which the system is booted requires a reboot.

How to create Secure Zone

1. Select the machine that you want to create Secure Zone on.
2. Click Details > Create Secure Zone .
3. Under Secure Zone disk, click Select, and then select a hard disk (if several) on which to create
the zone.
The software calculates the maximum possible size of Secure Zone.
4. Enter the Secure Zone size or drag the slider to select any size between the minimum and the
maximum ones.
The minimum size is approximately 50 MB, depending on the geometry of the hard disk. The
maximum size is equal to the disk's unallocated space plus the total free space on all of the disk's
volumes.
5. If all unallocated space is not enough for the size you specified, the software will take free space
from the existing volumes. By default, all volumes are selected. If you want to exclude some
volumes, click Select volumes. Otherwise, skip this step.

396 © Acronis International GmbH, 2003-2024

6. [Optional] Enable the Password protection switch and specify a password.
The password will be required to access the backups located in Secure Zone. Backing up to
Secure Zone does not require a password, unless the backup if performed under bootable
media.
7. Click Create.
The software displays the expected partition layout. Click OK.
8. Wait while the software creates Secure Zone.

You can now choose Secure Zone in Where to back up when creating a protection plan.

How to delete Secure Zone

1. Select a machine with Secure Zone.
2. Click Details.
3. Click the gear icon next to Secure Zone , and then click Delete.
4. [Optional] Specify the volumes to which the space freed from the zone will be added. By default,
all volumes are selected.
The space will be distributed equally among the selected volumes. If you do not select any
volumes, the freed space will become unallocated.
Resizing the volume from which the system is booted requires a reboot.
5. Click Delete.

397 © Acronis International GmbH, 2003-2024

As a result, Secure Zone will be deleted along with all backups stored in it.

Backup schedule
You can configure a backup to run automatically at a specific time, at specific intervals, or on a
specific event.

Scheduled backups for non-cloud-to-cloud resources run according to the time zone settings of the
workload on which the protection agent is installed. For example, if you apply the same protection
plan to workloads with different time zones settings, the backups will start according to the local
time zone of each workload.

Scheduling a backup includes the following actions:

l Selecting a backup scheme

l Configuring the time or selecting the event that triggers the backup
l Configuring optional setting and start conditions

Backup schemes
A backup scheme is a part of the protection plan schedule that defines which type of backup (full,
differential, or incremental) is created and when. You can select one of the predefined backup
schemes or create a custom scheme.

The available backup schemes and types depend on the backup location and source. For example, a
differential backup is not available when you back up SQL data, Exchange data, or system state. The
Always incremental (single-file) scheme is not supported for tape devices.

Backup scheme Description Configurable elements

Always incremental The first backup is full and might be time- l Schedule type:
(single-file) consuming. Subsequent backups are incremental monthly, weekly,
and significantly faster. daily, hourly
l Backup trigger: time
The backups use the single-file backup format1*.
or event
By default, backups are performed on a daily basis, l Start time
Monday to Friday. l Start conditions
We recommend that you use this scheme when l Additional options
you store your backups in the cloud storage,
because incremental backups are fast and involve
less network traffic.

1A backup format, in which the initial full and subsequent incremental backups are saved to a single .tibx file. This

format leverages the speed of the incremental backup method, while avoiding its main disadvantage–difficult deletion
of outdated backups. The software marks the blocks used by outdated backups as "free" and writes new backups to
these blocks. This results in extremely fast cleanup, with minimal resource consumption. The single-file backup format
is not available when backing up to locations that do not support random-access reads and writes.

398 © Acronis International GmbH, 2003-2024

 Backup scheme Description Configurable elements

Always full All backups in the backup set are full. l Schedule type:
monthly, weekly,
By default, backups are performed on a daily basis,
daily, hourly
Monday to Friday.
l Backup trigger: time
or event
l Start time
l Start conditions
l Additional options

Weekly full, Daily A full backup is created once a week and other l Backup trigger: time
incremental backups are incremental. or event
l Start time
The first backup is full and the other backups
during the week are incremental, then the cycle
l Start conditions
repeats. l Additional options

To select the day on which the weekly full backup is

created, in the protection plan, click the gear icon,
and then go to Backup options > Weekly backup.

By default, backups are performed on a daily basis,

Monday to Friday.

Monthly full, Weekly By default, incremental backups are performed on l Change the existing
differential, Daily a daily basis, Monday to Friday. Differential schedule per backup
incremental (GFS) backups are performed every Saturday. Full type:
o Schedule type:
backups are performed on the first day of each
month. monthly, weekly,
daily, hourly
Note o Backup trigger:
This is a predefined custom scheme. In the time or event
protection plan, it is shown as Custom. o Start time
o Start conditions
o Additional options
l Add new schedules
per backup type

Custom You must select the backup types (full, differential, l Change the existing
and incremental), and configure a separate schedule per backup
schedule for each of them*. type:
o Schedule type:

monthly, weekly,
daily, hourly
o Backup trigger:
time or event
o Start time
o Start conditions

399 © Acronis International GmbH, 2003-2024

 Backup scheme Description Configurable elements

o Additional options
l Add new schedules
per backup type

* After you create a protection plan, you cannot switch between Always incremental (single-file)
and the other backup schemes, and vice versa. Always incremental (single-file) is a single-file
format scheme, and the other schemes are multi-file format. If you want to switch between formats,
create a new protection plan.

Backup types
The following backup types are available:

l Full—a full backup contains all source data. This backup is self-sufficient. To recover data, you do
not need access to any other backups.

Note
The first backup created by any protection plan is a full backup.

l Incremental—an incremental backup stores changes to the data since the latest backup,
regardless of whether the latest backup is full, differential, or incremental. To recover data, you
need the whole chain of backups on which the incremental backup depends, back to the initial
full backup.
l Differential—a differential backup stores changes to the data since the latest full backup. To
recover data, you need both the differential backup and the corresponding full backup on which
the differential backup depends.

Running a backup on a schedule

To run a backup automatically at a specific time or on a specific event, enable a schedule in the
protection plan.

To enable a schedule

1. In the protection plan, expand the Backup module.

2. Click Schedule.
3. Enable the schedule switch.
4. Select the backup scheme.
5. Configure the schedule as required, and then click Done.
For more information about the available scheduling options, see "Schedule by time" (p. 401)
and "Schedule by events" (p. 403).
6. [Optional] Configure start conditions or additional scheduling options.
7. Save the protection plan.

As a result, a backup operation starts every time when the schedule conditions are met.

400 © Acronis International GmbH, 2003-2024

To disable a schedule

1. In the protection plan, expand the Backup module.

2. Click Schedule.
3. Disable the schedule switch.
4. Save the protection plan.

As a result, the backup runs only if you start it manually.

Note
If the schedule is disabled, the retention rules are not applied automatically. To apply them, run the
backup manually.

Schedule by time
The following table summarizes the scheduling options that are based on time. The availability of
these options depends on the backup scheme. For more information, see "Backup schemes" (p.
398).

Option Description Examples

Monthly Select the months, days of the month or Run a backup on January 1, and February
days of the week, and then select the 3, at 12:00 AM.
backup start time.
Run a backup on the first day of each
month, at 10:00 AM.

Run a backup on March 1, March 5, April

1, and April 5, at 09:00 AM.

Run a backup on the second and third

Friday of each month, at 11:00 AM.

Run a backup on the last Wednesday of

the month, at 10:30 PM.

Weekly Select the days of the week, and then Run a backup Monday to Friday, at 10:00
select the backup start time. AM.

Run a backup on Monday, at 11:00 PM.

Run a backup on Tuesday and Saturday,

at 08:00 AM.

Daily Select the days (everyday or weekdays Run a backup every day, at 11:45 AM.
only), and then select the backup start
Run a backup Monday to Friday, at 09:30
time.
PM.

Hourly Select the days of the week, and then Run a backup every hour between 08:00
select a time interval between two AM and 06:00 PM, Monday to Friday.
consecutive backups and the time range
Run a backup every 3 hours between

401 © Acronis International GmbH, 2003-2024

 Option Description Examples

within which the backups run. 01:00 AM and 06:00 PM, on Saturday and
Sunday.
When you configure the interval in
minutes, you can select a suggested
interval between 10 and 60 minutes, or
specify a custom one, for example, 45 or
75 minutes.

Additional options
When you schedule a backup by time, the following additional scheduling options are available.

To access them, in the Schedule pane, click Show more.

l If the machine is turned off, run missed tasks at the machine startup
Default setting: Disabled.
l Prevent the sleep or hibernate mode during backup
This option is applicable only to machines running Windows.
Default setting: Enabled.
l Wake up from the sleep or hibernate mode to start a scheduled backup
This option is applicable only to machines running Windows, in the power plans for which the
Allow wake timers option is enabled.

402 © Acronis International GmbH, 2003-2024

 This option does not use the Wake-on-LAN functionality and is not applicable to powered-off
machines.
Default setting: Disabled.

Schedule by events
To configure a backup that runs upon a specific event, select one of the following options.

Option Description Examples

Upon time A backup starts after a specified period Run a backup one day after the last
since last following the last successful backup. successful backup.
backup
Run a backup four hours after the last
successful backup.

403 © Acronis International GmbH, 2003-2024

 Option Description Examples

Note
This option depends on how the previous
backup completed. If a backup fails, the
next backup will not start automatically. In
this case, you must run the backup
manually and ensure that it completes
successfully, in order to reset the
schedule.

When a user A backup starts when a user logs in to the Run a backup when user John Doe logs
logs on to the machine. in.
system
You can configure this option for any login
or for a login of a specific user.

Note
Logging in with a temporary user profile
will not start a backup.

When a user A backup starts when a user logs off the Run a backup when every user logs off.
logs off the machine.
system
You can configure this option for any
logoff or for the logoff of a specific user.

Note
Logging off from a temporary user profile
will not start a backup.

Shutting down a machine will not start a

backup.

On the system A backup runs when the protected Run a backup when a user starts the
startup machine starts up. machine.

On the system A backup runs when the protected Run a backup when a user shuts down
shutdown machine shuts down. the machine.

On Windows A backup runs upon a Windows event that Run a backup when event 7 of type error
Event Log event you specify. and source disk is recorded in the
Windows System log.

The availability of these options depends on the backup source and the operating system of the
protected workloads. The table below summarizes the available options for Windows, Linux, and
macOS.

404 © Acronis International GmbH, 2003-2024

 Backup source (What to back up)

Entire Entire ESXi Microsoft Exchange SQL

machine, machines or configuratio 365 databases databases
Event Disks/volume Disk/volume n mailboxes and
s, or s (virtual mailboxes
Files/folders machines)
(physical
machines)

Upon
time Windows, Windows, Windows,
Windows Windows Windows
since last Linux, macOS Linux Linux
backup

When a
user logs
Windows N/A N/A N/A N/A N/A
on to the
system

When a
user logs
Windows N/A N/A N/A N/A N/A
off the
system

On the
Windows,
system N/A N/A N/A N/A N/A
Linux, macOS
startup

On the
system Windows N/A N/A N/A N/A N/A
shutdown

On
Windows
Windows N/A N/A Windows Windows Windows
Event Log
event

On Windows Event Log event

You can automatically run a backup when a specific event is recorded in a Windows Event log, such
as the Application log, Security log, or System log.

Note
You can browse the events and view their properties in Computer Management > Event Viewer
in Windows. To open the Security log, you need administrator rights.

405 © Acronis International GmbH, 2003-2024

Event parameters
The following table summarizes the parameters that you must specify when configuring the
On Windows Event Log event option.

Parameter Description

Log name The name of the log.

Select the name of a standard log (Application, Security, System)

or specify another log name. For example, Microsoft Office Sessions.

Event source The event source indicates the program or the system
component that caused the event. For example, disk.

Any event source that contains the specified text string will
trigger the scheduled backup. This option is not case-sensitive. For
example, if you specify service, both Service Control Manager and Time-
Service event sources will trigger a backup.

Event type Type of the event: Error, Warning, Information, Audit success, or
Audit failure.

Event ID The event ID identifies a particular kind of event within an event

source.

For example, an Error event with event source disk and event ID
7 occurs when Windows discovers a bad block on a disk, while an Error
event with event source disk and event ID 15 occurs when a disk is not
ready for access.

Example: Emergency backup in case of bad blocks on the hard disk

One or more bad blocks on a hard disk drive might indicate an imminent fail. That is why you might
want to create a backup when a bad block is detected.

When Windows detects a bad block on the disk, an error event with the event source disk and event
number 7 is recorded to the system log. In the protection plan, configure the following schedule:

l Schedule: On Windows Event log event

l Log name: System
l Event source: disk
l Event type: Error
l Event ID: 7

Important
To ensure that the backup completes despite the bad blocks, in Backup options, go to Error
handling, and then select the Ignore bad sectors check box.

406 © Acronis International GmbH, 2003-2024

Start conditions
To make a backup run only if specific conditions are met, configure one or more start conditions. If
you configure multiple conditions, all of them must be met simultaneously for the backup to start.
You can specify a period after which the backups will run, regardless of whether the conditions are
met. For more information about this backup option, see "Task start conditions" (p. 468).

Start conditions are not applicable when you start a backup manually.

The table below lists the start conditions available for various data under Windows, Linux, and
macOS.

Backup source (What to back up)

Entire Entire ESXi Microsoft Exchange SQL

machine, machines or configuratio 365 databases databases
Start Disks/volume Disk/volume n mailboxes and
condition s, or s (virtual mailboxes
Files/folders machines)
(physical
machines)

User is idle Windows N/A N/A N/A N/A N/A

The backup
Windows,
location's Windows, Windows,
Linux, Windows Windows Windows
host is Linux Linux
macOS
available

Users logged
Windows N/A N/A N/A N/A N/A
off

Fits the time Windows,

Windows,
interval Linux, N/A N/A N/A N/A
Linux
macOS

Save battery
Windows N/A N/A N/A N/A N/A
power

Do not start
when on
Windows N/A N/A N/A N/A N/A
metered
connection

Do not start
when
connected to Windows N/A N/A N/A N/A N/A
the following
Wi-Fi

407 © Acronis International GmbH, 2003-2024

 Backup source (What to back up)

Entire Entire ESXi Microsoft Exchange SQL

machine, machines or configuratio 365 databases databases
Start Disks/volume Disk/volume n mailboxes and
condition s, or s (virtual mailboxes
Files/folders machines)
(physical
machines)

networks

Check device
Windows N/A N/A N/A N/A N/A
IP address

User is idle
"User is idle" means that a screen saver is running on the machine or the machine is locked.

Example
Run a backup every day at 09:00 PM, preferably when the user is idle. If the user is still active by
11:00 PM, run the backup anyway.

l Schedule: Daily, Run every day. Start at: 09:00 PM.

l Condition: User is idle.
l Backup start conditions: Wait until the conditions are met, Start the task anyway after 2
hours.

As a result:

l If the user is idle before 09:00 PM, the backup starts at 09:00 PM.
l If the user becomes idle between 09:00 PM and 11:00 PM, the backup starts immediately.
l If the user is still active at 11:00 PM, the backup starts at 11:00 PM.

The backup location's host is available

"The backup location's host is available" means that the machine that hosts the backup location is
available over the network.

This condition is applicable to network folders, the cloud storage, and locations managed by a
storage node.

This condition does not cover the availability of the location itself—only the host availability. For
example, if the host is available, but the network folder on this host is not shared or the credentials
for the folder are no longer valid, the condition is still considered met.

408 © Acronis International GmbH, 2003-2024

Example
You run backups to a network folder every workday at 09:00 PM. If the machine that hosts the
folder is not available at that moment (for example, due to maintenance), you want to skip the
backup and wait for the scheduled start on the next workday.

l Schedule: Daily, Run Monday to Friday. Start at: 09:00 PM.

l Condition: The backup location's host is available.
l Backup start conditions: Skip the scheduled backup.

As a result:

l If the host is available at 09:00 PM, the backup starts immediately.

l If the host is not available at 09:00 PM, the backup starts the next workday (if the host is available
at 09:00 PM on this day).
l If the host is never available on workdays at 09:00 PM, the backup never starts.

Users logged off

Use this start condition to postpone a backup until all users log off from a Windows machine.

Example
You run a backup every Friday at 08:00 PM, preferably when all users are logged off. If one of the
users is still logged in at 11:00 PM, run the backup anyway.

l Schedule: Weekly, on Fridays. Start at: 08:00 PM.

l Condition: Users logged off.
l Backup start conditions: Wait until the conditions are met, Start the backup anyway after 3
hours.

As a result:

l If all users are logged off at 08:00 PM, the backup starts at 08:00 PM.
l If the last user logs off between 08:00 PM and 11:00 PM, the backup starts immediately.
l If there are still logged-in users at 11:00 PM, the backup starts at 11:00 PM.

Fits the time interval

Use this start condition to restrict a backup start to a specified interval.

Example
A company backs up user data and servers to different locations on the same network-attached
storage.

The workday starts at 08:00 AM and ends at 05:00 PM. User data should be backed up as soon as
the users log off, but not earlier than 04:30 PM.

409 © Acronis International GmbH, 2003-2024

The company's servers are backed up every day at 11:00 PM. User data should preferably be backed
up before 11:00 PM, in order to free network bandwidth for the server backups.

Backing up user data takes no more than one hour, so the latest backup start time is 10:00 PM. If a
user is still logged in within the specified time interval, or logs off at any other time, the backup of
the user data should be skipped.

l Event: When a user logs off the system. Specify the user account: Any user.
l Condition: Fits the time interval from 04:30 PM to 10:00 PM.
l Backup start conditions: Skip the scheduled backup.

As a result:

l If the user logs off between 04:30 PM and 10:00 PM, the backup starts immediately.
l If the user logs off at any other time, the backup is skipped.

Save battery power

Use this start condition to prevent a backup if a machine (for example, a laptop or a tablet) is not
connected to a power source. Depending on the value of the Backup start conditions option, the
skipped backup will or will not start after the machine is connected to a power source.

The following options are available:

l Do not start when on battery

A backup will start only if the machine is connected to a power source.
l Start when on battery if the battery level is higher than
A backup will start if the machine is connected to a power source or if the battery level is higher
than a specified value.

Example
You back up your data every workday at 09:00 PM. If your machine is not connected to a power
source, you want to skip the backup to save the battery power and wait until you connect the
machine to a power source.

l Schedule: Daily, Run Monday to Friday. Start at: 09:00 PM.

l Condition: Save battery power, Do not start when on battery.
l Backup start conditions: Wait until the conditions are met.

As a result:

l If the machine is connected to a power source at 09:00 PM, the backup starts immediately.
l If the machine is running on battery power at 09:00 PM, the backup starts when you connect the
machine to a power source.

Do not start when on metered connection

Use this start condition to prevent a backup (including a backup to a local disk) if the machine is
connected to the Internet through a connection that is set as metered in Windows. For more

410 © Acronis International GmbH, 2003-2024

information about metered connections in Windows, refer to https://support.microsoft.com/en-
us/help/17452/windows-metered-internet-connections-faq.

The additional start condition Do not start when connected to the following Wi-Fi networks is
automatically enabled when you enable the Do not start when on metered connection
condition. This is an additional measure to prevent backups over mobile hotspots. The following
network names are specified by default: android, phone, mobile, and modem.

To remove these names from the list, click the X sign. To add a new name, type it in the empty field.

Example
You back up your data every workday at 09:00 PM. If the machine is connected to the Internet by
using a metered connection, you want to skip the backup to save the network traffic and wait for the
scheduled start on the next workday.

l Schedule: Daily, Run Monday to Friday. Start at: 09:00 PM.

l Condition: Do not start when on metered connection.
l Backup start conditions: Skip the scheduled backup.

As a result:

l At 09:00 PM, if the machine is not connected to the Internet through a metered connection, the
backup starts immediately.
l At 09:00 PM, if the machine is connected to the Internet through a metered connection, the
backup starts on the next workday.
l If the machine is always connected to the Internet through a metered connection on workdays at
09:00 PM, the backup never starts.

Do not start when connected to the following Wi-Fi networks

Use this start condition to prevent a backup (including a backup to a local disk) if the machine is
connected to any of the specified wireless networks (for example, if you want to restrict backups
through a mobile phone hotspot).

You can specify the Wi-Fi network names, also known as service set identifiers (SSID). The restriction
applies to all networks that contain the specified name as a substring in their name, not case-
sensitive. For example, if you specify phone as the network name, the backup will not start when the
machine is connected to any of the following networks: John's iPhone, phone_wifi, or my_PHONE_wifi.

The start condition Do not start when connected to the following Wi-Fi is automatically enabled
when you enable the Do not start when on metered connection condition. The following
network names are specified by default: android, phone, mobile, and modem.

To remove these names from the list, click the X sign. To add a new name, type it in the empty field.

Example
You back up your data every workday at 09:00 PM. If the machine is connected to the Internet
through a mobile hotspot, you want to skip the backup and wait for the scheduled start on the next

411 © Acronis International GmbH, 2003-2024

workday.

l Schedule: Daily, Run Monday to Friday. Start at: 09:00 PM.

l Condition: Do not start when connected to the following networks, Network name: <SSID
of the hotspot network>.
l Backup start conditions: Skip the scheduled backup.

As a result:

l If the machine is not connected to the specified network at 09:00 PM, the backup starts
immediately.
l If the machine is connected to the specified network at 09:00 PM, the backup starts the next
workday.
l If the machine is always connected to the specified network on workdays at 09:00 PM, the backup
never starts.

Check device IP address

Use this start condition to prevent a backup (including a backup to a local disk) if any of the machine
IP addresses are within or outside of the specified IP address range. Thus, for example, you can
avoid large data transit charges when backing up machines of users who are overseas, or you can
prevent backups over a Virtual Private Network (VPN) connection.

The following options are available:

l Start if outside IP range

l Start if within IP range

With either option, you can specify several ranges. Only IPv4 addresses are supported.

Example
You back up your data every workday at 09:00 PM. If the machine is connected to the corporate
network by using a VPN tunnel, you want to skip the backup.

l Schedule: Daily, Run Monday to Friday. Start at 09:00 PM.

l Condition: Check device IP address, Start if outside IP range, From: <beginning of the VPN IP
address range>, To: <end of the VPN IP address range>.
l Backup start conditions: Wait until the conditions are met.

As a result:

l If the machine IP address is not in the specified range at 09:00 PM, the backup starts
immediately.
l If the machine IP address is in the specified range at 09:00 PM, the backup starts when the
machine obtains a non-VPN IP address.
l If the machine IP address is always in the specified range on workdays at 09:00 PM, the backup
never starts.

412 © Acronis International GmbH, 2003-2024

Additional scheduling options
You can configure the backups to run only if specific conditions are met, to run only during a
specified period, or to run with a delay compared to the schedule.

To configure start conditions

1. In the protection plan, expand the Backup module.

2. Click Schedule.
3. On the Schedule pane, click Show more.
4. Select the check boxes next to the start conditions that you want to include, and then click Done.
For more information about the available start conditions and how to configure them, see "Start
conditions" (p. 407).
5. Save the protection plan.

To configure a time range

1. In the protection plan, expand the Backup module.

2. Click Schedule.
3. Select the Run the plan within a date range check box.
4. Specify the period according to your needs, and then click Done.
5. Save the protection plan.

As a result, the backups will run only during the specified period.

To configure a delay

To avoid excessive network load when you back up multiple workloads to a network location, a
small random delay is configured as a backup option. You can disable it or change its setting.

1. In the protection plan, expand the Backup module.

2. Click Backup options, and then select Scheduling.
The delay value for each workload is selected randomly between zero and the maximum value
you specify. By default, the maximum value is 30 minutes.
For more information about this backup option, see "Scheduling" (p. 466)
The delay value for each workload is calculated when you apply the protection plan to that
workload, and remains the same until you edit the maximum delay value.
3. Specify the period according to your needs, and then click Done.
4. Save the protection plan.

Running a backup manually

You can manually run scheduled and unscheduled backups.

To run a backup manually

413 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Devices.
2. Select the workload for which you want to run a backup, and then click Protect.
3. Select the protection plan that you want to create the backup.
If no protection plan is applied to the workload, apply an existing plan or create a new one.
For more information about how to create a protection plan, see "Creating a protection plan" (p.
206).
4. [To create the default type of backup] In the protection plan, click the Run now icon.

Alternatively, in the protection plan, expand the Backup module, and then click the Run now
button.
5. [To create a specific type of backup] In the protection plan, expand the Backup module, click the
arrow next to the Run now button, and then select the backup type.

Note
Selecting the type is not available for backup schemes that use only one backup method, for
example, Always incremental (single-file) or Always full.

As a result, the backup operation starts. You can check its progress and its result on the Devices
tab, in the Status column.

Retention rules
To delete older backups automatically, configure the backup retention rules in the protection plan.

You can base the retention rules on any of the following backup properties:

l Number
l Age
l Size

414 © Acronis International GmbH, 2003-2024

The available retention rules and their options depend on the backup scheme. The rules are also
relevant to agents, workloads, and cloud to cloud backups. For more information, see "Retention
rules according to the backup scheme" (p. 415).

You can disable the automatic cleanup of older backups, by selecting the Keeping backups
infinitely option while configuring the retention rules. This might result in increased storage usage,
and you have to delete the unnecessary old backups manually.

Important tips
l Retention rules are part of the protection plan. If you revoke or delete a plan, the retention rules
in that plan will no longer be applied. For more information about how to delete the backups that
you no longer need, see "Deleting backups" (p. 507).
l If, according to the backup scheme and backup format, each backup is stored as a separate file,
you cannot delete a backup on which other incremental or differential backups depend. This
backup will be deleted according to the retention rules applied to the dependent backups. This
configuration may result in increased storage usage because the deletion of some backups is
postponed. Also, the backup age, number, or size of backups may exceed the values that you
specified. For more information about how to change this behavior, see "Backup consolidation"
(p. 428).
l By default, the newest backup that a protection plan creates is never deleted. However, if you
configure a retention rule to clean up the backups before starting a new backup operation, and
set the number of backups to keep to zero, the newest backup will also be deleted.

Warning!
If you apply this retention rule to a backup set with a single backup, and the backup operation
fails, you will not be able to recover your data, because the existing backup will be deleted before
a new one is created.

Retention rules according to the backup scheme

The available retention rules and their settings depend on the backup scheme that you use in the
protection plan. For more information about the backup schemes, see "Backup schemes" (p. 398).

The following table summarizes the available retention rules and their settings.

Backup scheme Schedule Available retention rules and settings

Always incremental Monthly By number of backups

(single-file)
Weekly By backup age (separate settings for monthly,
weekly, daily, and hourly backups)
Daily
Keep backups indefinitely
Hourly

Event-triggered backups

Always full Monthly By number of backups

415 © Acronis International GmbH, 2003-2024

 Backup scheme Schedule Available retention rules and settings

Weekly By backup age (separate settings for monthly,

weekly, daily, and hourly backups)
Daily
By total size of backups
Hourly
Keep backups indefinitely
Event-triggered backups

Weekly full, Daily Daily By number of backups

incremental
Event-triggered backups By backup age (separate settings for weekly and
daily backups)

By total size of backups

Keep backups indefinitely

Monthly full, Weekly Monthly By number of backups

differential, daily
Weekly By backup age (separate settings for full,
incremental
differential, and incremental backups)
Daily
By total size of backups
Hourly
Keep backups indefinitely
Event-triggered backups

Custom Monthly By number of backups

Weekly By backup age (separate settings for full,

differential, and incremental backups)
Daily
By total size of backups
Hourly
Keep backups indefinitely
Event-triggered backups

Why are there monthly backups with an hourly scheme?

Depending on the backup scheme, you can configure the By backup age option for one the
following backups:

l Monthly, weekly, daily, and hourly backups.

These setting are available with all non-custom backup schemes, and are based on time. All these
backups (monthly, weekly, daily, and hourly) are available, even if you configure your backups to
run hourly. See the example below.

Backup Description

Monthly A monthly backup is the first backup each month.

A weekly backup is the first backup on the day of the week that you
Weekly specify in the Weekly backup option. This day is considered as the
beginning of the week in terms of retention rules.

416 © Acronis International GmbH, 2003-2024

 Backup Description

If a weekly backup is also the first backup of the month, it is considered

a monthly backup. In this case, a weekly backup is created on the
selected day the following week.

A daily backup is the first backup of the day, unless this backup falls
Daily within the definition of a monthly or weekly backup. In this case, a daily
backup is created the following day.

An hourly backup is the first backup of the hour, unless this backup
Hourly falls within the definition of a monthly, weekly, or daily backup. In this
case, an hourly backup is created the next hour.

l Full, differential, and incremental backups.

These setting are available for the Custom backup scheme, and are based on the backup
method. The Monthly full, Weekly differential, Daily incremental is a pre-configured custom
scheme.

Example
You use the Always incremental (single-file) backup scheme with the default setting for hourly
backups:

l Scheduled by time.
l Backups run hourly: Monday to Friday, every 1 hour, from 08:00 AM to 06:00 PM.
l The Weekly backup option is set to Monday.

In the How long to keep section of the protection plan, you can apply retention rules to monthly,
weekly, daily, and hourly backups.

The following table summarizes the backup types that are created during an 8-day period.

Date Day of week Description

July 1 Monday The first backup each month is monthly, so the first backup
today is a monthly backup. The other backups during the day
are hourly.

This week, the first backup is considered a monthly backup.

That is why there is no weekly backup. The first backup next
week will be a weekly backup.

July 2 Tuesday The first backup is daily, the other backups during the day are
hourly.

July 3 Wednesday The first backup is daily, the other backups during the day are
hourly.

July 4 Thursday The first backup is daily, the other backups during the day are
hourly.

417 © Acronis International GmbH, 2003-2024

 Date Day of week Description

July 5 Friday The first backup is daily, the other backups during the day are
hourly.

July 6 Saturday The first backup is daily, the other backups during the day are
hourly.

July 7 Sunday The first backup is daily, the other backups during the day are
hourly.

July 8 Monday The first backup is weekly, the other backups during the day
are hourly.

Configuring retention rules

The retention rules are part of the protection plan, and their availability and options depend on the
backup scheme. For more information, see "Retention rules according to the backup scheme" (p.
415).

To configure the retention rules

1. In the protection plan, expand the Backup module.

2. Click How many to keep.
3. Select one of the following options:
l By number of backups
l By backup age
Separate settings for monthly, weekly, daily, and hourly backups are available. The maximum
value for all types is 9999.
You can also use a single setting for all backups.
l By total size of backups
This setting is not available with the Always incremental (single-file) backup scheme.
l Keep backups indefinitely
4. [If you did not select Keep backups indefinitely] Configure the values for the selected option.
5. [If you did not select Keep backups indefinitely] Select when the retention rules are applied:
l After backup
l Before backup
This option is not available when backing up Microsoft SQL Server clusters or Microsoft
Exchange Server clusters.
6. Click Done.
7. Save the protection plan.

418 © Acronis International GmbH, 2003-2024

Replication
With replication, each new backup is automatically copied to a replication location. The backups in
the replication location do not depend on the backups in the source location, and vice versa.

Only the last backup in the source location is replicated. However, if earlier backups are not
replicated (for example, due to a network connection problem), the replication operation will
include all backups that are created after the last successful replication.

If a replication operation is interrupted, the processed data will be used by the next replication
operation.

Note
This topic describes replication as a part of a protection plan. You can also create a separate backup
replication plan. For more information, see "Backup replication" (p. 191).

Usage examples
l Ensuring reliable recovery
Store your backups both on-site (for immediate recovery) and off-site (to guarantee that the
backups stay safe even in case of storage failure or a natural disaster that affects the primary
location).
l Using the cloud storage to protect data from a natural disaster
Replicate the backups to the cloud storage by transferring only the data changes.
l Keeping only the latest recovery points
Configure retention rules to delete the older backups from a fast storage, in order to save on
storage costs.

Supported locations
Location As source location As replication location

Local folder + +

Network folder + +

Cloud storage - +

Secure Zone + –

Public cloud + +

To enable replication

419 © Acronis International GmbH, 2003-2024

1. In a protection plan, expand the Backup module, and then click Add location.

Note
The Add location option is not available when you select the cloud storage in Where to back
up.

2. From the list of available locations, select the replication location.

The location appears in the protection plan as 2nd location, 3rd location, 4th location, or 5th
location, depending on the number of locations you added for replication.
3. [Optional] Click the gear icon to configure the options for the replication location.
l Performance and backup window – set the backup window for the selected location, as
described in "Performance and backup window" (p. 456). These settings define the replication
performance.
l Remove location – delete the currently selected replication location.
l [Only for the cloud storage] Physical Data Shipping – save the initial backup on a removable
storage device and ship it for upload to the cloud storage, instead of replicating it over the
Internet.
This option is suitable for locations with slow network connection or when you want to save
bandwidth on big file transfers over the network. Enabling the option does not require
advanced Cyber Protect service quotas, but you will need a Physical Data Shipping service
quota to create a shipping order and track it. See "Physical Data Shipping" (p. 460).

Note
This option is supported with protection agent version from release C21.06 or later.

4. [Optional] In the How many to keep row under the replication location, configure the retention
rules for that location, as described in "Retention rules" (p. 414).
5. [Optional] Repeat steps 1 – 4 to add more replication locations.
You can configure up to four replication locations (2nd location, 3rd location, 4th location, and
5th location). If you select Cloud storage, you cannot add more replication locations.

Important
If you enable backup and replication in the same protection plan, ensure that the replication
completes before the next scheduled backup. If the replication is still in progress, the scheduled
backup will not start―for example, a scheduled backup that runs once every 24 hours will not start
if the replication takes 26 hours to complete.

To avoid the this dependency, use a separate plan for backup replication. For more information
about this specific plan, see "Backup replication" (p. 191).

Encryption
The Advanced Encryption Standard (AES) cryptographic algorithm operates in Galois/Counter mode
(GCM) and uses a randomly generated 256-bit key. The encryption key is then encrypted with AES-

420 © Acronis International GmbH, 2003-2024

256 algorithm by using the SHA-2 (256-bit) hash of the password as a key. The password itself is not
stored anywhere on the disk or in the backups, and the password hash is used for verification.

With this two-level security, the backup data is protected from unauthorized access, but recovering
a lost password is not possible.

Note
Using the AES-256 algorithm with a strong password provides quantum-resistant encryption. It is
safe against cryptanalytic attacks that rely on quantum computing.

We recommend that you encrypt all backups that are stored in the cloud storage, especially if your
company is subject to regulatory compliance.

You can configure encryption in the following ways:

l In the protection plan

l As a machine property, by using the Cyber Protect Monitor or the command-line interface

Configuring encryption in the protection plan

In a protection plan, encryption is enabled by default. The AES-256 algorithm is used.

With a strong password, the AES-256 algorithm provides quantum-resistant encryption.

For accounts in the Compliance mode, you cannot configure encryption in the protection plan. For
more information on how to configure encryption on the protected device, see "Configuring
encryption as a machine property" (p. 421).

To configure encryption

1. In a protection plan, expand the Backup module.

2. In Encryption, click Specify password.
3. Specify and confirm the encryption password.
4. Click OK.

Warning!
There is no way to recover encrypted backups if you lose or forget the password.

You cannot change the encryption settings after you apply the protection plan. To use different
encryption settings, create a new plan.

Configuring encryption as a machine property

You can configure backup encryption as a machine property. In this case, backup encryption is not
configured in the protection plan, but on the protected workload. Encryption as a machine property
uses the AES algorithm with a 256-bit key (AES-256).

421 © Acronis International GmbH, 2003-2024

Note
Using the AES-256 algorithm with a strong password provides quantum-resistant encryption. It is
safe against cryptanalytic attacks that rely on quantum computing.

Configuring encryption as a machine property affects the protection plans in the following way:

l Protection plans that are already applied to the machine. If the encryption settings in a
protection plan are different, the backups will fail.
l Protection plans that will be applied to the machine later. The encryption settings saved on
the machine will override the encryption settings in the protection plan. Any backup will be
encrypted, even if encryption is disabled in the Backup module settings.

For accounts in the Compliance mode, only encryption as a machine property is available.

If you have more than one Agent for VMware connected to the same vCenter Server, and you
configure encryption as a machine property, you must use the same encryption password on all
machines with Agent for VMware, because of the load balancing between the agents.

You can configure encryption as a machine property in the following ways:

l On the command line

l In Cyber Protect Monitor (Available for Windows and macOS)

To configure encryption

On the command line

1. Log in as an administrator (in Windows) or the root user (in Linux).

2. On the command line, run the following command:
l For Windows:

<installation_path>\PyShell\bin\acropsh.exe -m manage_creds --set-password

<encryption_password>

By default, the installation path is %ProgramFiles%\BackupClient.

l For Linux:

/usr/sbin/acropsh -m manage_creds --set-password <encryption_password>

l For a virtual appliance:

/./sbin/acropsh -m manage_creds --set-password <encryption_password>

Warning!
There is no way to recover encrypted backups if you lose or forget the password.

In Cyber Protect Monitor

422 © Acronis International GmbH, 2003-2024

1. Log in as an administrator.
2. Click the Cyber Protect Monitor icon in the notification area (in Windows) or the menu bar (in
macOS).
3. Click the gear icon, and then click Settings > Encryption.
4. Select Set a password for this machine. Specify and confirm the encryption password.
5. Click Save.

Warning!
There is no way to recover encrypted backups if you lose or forget the password.

To reset the encryption settings

1. Log in as an administrator (in Windows) or root user (in Linux).

2. On the command line, run the following command:
l For Windows:

<installation_path>\PyShell\bin\acropsh.exe -m manage_creds --reset

By default, the installation path is %ProgramFiles%\BackupClient.

l For Linux:

/usr/sbin/acropsh -m manage_creds --reset

l For a virtual appliance:

/./sbin/acropsh -m manage_creds --reset

Important
If you reset the encryption as a machine property or change the encryption password after a
protection plan creates a backup, the next backup operation will fail. To continue backing up the
workload, create a new protection plan.

Notarization
Note
This feature is available with the Advanced Backup pack.

Notarization enables you to prove that a file is authentic and unchanged since it was backed up. We
recommend that you enable notarization when backing up your legal document files or other files
that require proved authenticity.

Notarization is available only for file-level backups. Files that have a digital signature are skipped,
because they do not need to be notarized.

Notarization is not available:

423 © Acronis International GmbH, 2003-2024

l If the backup format is set to Version 11
l If the backup destination is Secure Zone

How to use notarization

To enable notarization of all files selected for backup (except for the files that have a digital
signature), enable the Notarization switch when creating a protection plan.

When configuring recovery, the notarized files will be marked with a special icon, and you can verify
the file authenticity.

How it works
During a backup, the agent calculates the hash codes of the backed-up files, builds a hash tree
(based on the folder structure), saves the tree in the backup, and then sends the hash tree root to
the notary service. The notary service saves the hash tree root in the Ethereum blockchain database
to ensure that this value does not change.

When verifying the file authenticity, the agent calculates the hash of the file, and then compares it
with the hash that is stored in the hash tree inside the backup. If these hashes do not match, the file
is considered not authentic. Otherwise, the file authenticity is guaranteed by the hash tree.

To verify that the hash tree itself was not compromised, the agent sends the hash tree root to the
notary service. The notary service compares it with the one stored in the blockchain database. If the
hashes match, the selected file is guaranteed to be authentic. Otherwise, the software displays a
message that the file is not authentic.

Default backup options

The default values of backup options exist at the company, unit, and user level. When a unit or a
user account is created within a company or within a unit, it inherits the default values set for the
company or for the unit.

Company administrators, unit administrators, and every user without the administrator rights can
change a default option value against the pre-defined one. The new value will be used by default in
all protection plans created at the respective level after the change takes place.

When creating a protection plan, a user can override a default value with a custom value that will be
specific for this plan only.

To change a default option value

1. Do one of the following:

l To change the default value for the company, sign in to the Cyber Protect console as a
company administrator.
l To change the default value for a unit, sign in to the Cyber Protect console as an administrator
of the unit.

424 © Acronis International GmbH, 2003-2024

 l To change the default value for yourself, sign in to the Cyber Protect console by using an
account without the administrator rights.
2. Click Settings > System settings.
3. Expand the Default backup options section.
4. Select the option, and then make the necessary changes.
5. Click Save.

Backup options
To modify the backup options of a protection plan, in the Backup module, in the Backup options
field, click Change.

Availability of the backup options

The set of available backup options depends on:

l The environment the agent operates in (Windows, Linux, macOS).

l The type of the data being backed up (disks, files, virtual machines, application data).
l The backup destination (the cloud storage, local or network folder).

The following table summarizes the availability of the backup options.

Disk-level backup File-level backup Virtual machines SQL

and
Exchan
ge

Windo Linu mac Windo Linu mac ESX Hype Virtuoz Windo
ws x OS ws x OS i r-V zo ws

Alerts + + + + + + + + + +

Backup + + + + + + + + + -
consolidation

Backup file name + + + + + + + + + +

Backup format + + + + + + + + + +

Backup validation + + + + + + + + + +

Changed block + - - - - - + + - -
tracking (CBT)

Cluster backup - - - - - - - - - +
mode

Compression + + + + + + + + + +
level

425 © Acronis International GmbH, 2003-2024

Error handling

Re-attempt, if an + + + + + + + + + +
error occurs

Do not show + + + + + + + + + +
messages and
dialogs while
processing (silent
mode)

Ignore bad + - + + - + + + + -
sectors

Re-attempt, if an - - - - - - + + + -
error occurs
during VM
snapshot
creation

Fast + + + - - - - - - -
incremental/diffe
rential backup

File-level backup - - - + + + - - - -
snapshot

File filters + + + + + + + + + -

Forensic data + - - - - - - - - -

Log truncation - - - - - - + + - SQL

only

LVM snapshotting - + - - - - - - - -

Mount points - - - + - - - - - -

Multi-volume + + - + + - - - - -
snapshot

One-click + + - - - - - - - -
recovery

Performance and + + + + + + + + + +
backup window

Physical Data + + + + + + + + + -
Shipping

Pre/Post + + + + + + + + + +
commands

426 © Acronis International GmbH, 2003-2024

 Pre/Post data + + + + + + - - - +
capture
commands

Scheduling

Distribute start + + + + + + + + + +
times within a
time window

Limit the number - - - - - - + + + -

of simultaneously
running backups

Sector-by-sector + + - - - - + + + -
backup

Splitting + + + + + + + + + +

Task failure + + + + + + + + + +
handling

Task start + + - + + - + + + +
conditions

Volume Shadow + - - + - - - + - +
Copy Service
(VSS)

Volume Shadow - - - - - - + + - -
Copy Service
(VSS) for virtual
machines

Weekly backup + + + + + + + + + +

Windows event + - - + - - + + - +
log

Alerts

No successful backups for a specified number of consecutive days

The preset is: Disabled.

This option determines whether to generate an alert if no successful backups were performed by
the protection plan for a specified period of time. In addition to failed backups, the software counts
backups that did not run on schedule (missed backups).

The alerts are generated on a per-machine basis and are displayed on the Alerts tab.

You can specify the number of consecutive days without backups after which the alert is generated.

427 © Acronis International GmbH, 2003-2024

Backup consolidation
This option defines whether to consolidate backups during cleanup or to delete entire backup
chains.

The preset is: Disabled.

Consolidation is the process of combining two or more subsequent backups into a single backup.

If this option is enabled, a backup that should be deleted during cleanup is consolidated with the
next dependent backup (incremental or differential).

Otherwise, the backup is retained until all dependent backups become subject to deletion. This
helps avoid the potentially time-consuming consolidation, but requires extra space for storing
backups whose deletion is postponed. The backups' age or number can exceed the values specified
in the retention rules.

Important
Please be aware that consolidation is just a method of deletion, but not an alternative to deletion.
The resulting backup will not contain data that was present in the deleted backup and was absent
from the retained incremental or differential backup.

This option is not effective if any of the following is true:

l The backup destination is the cloud storage.

l The backup scheme is set to Always incremental (single-file).
l The backup format is set to Version 12.

Backups stored in the cloud storage, as well as single-file backups (both version 11 and 12 formats),
are always consolidated because their inner structure makes for fast and easy consolidation.

However, if version 12 format is used, and multiple backup chains are present (every chain being
stored in a separate .tibx file), consolidation works only within the last chain. Any other chain is
deleted as a whole, except for the first one, which is shrunk to the minimum size to keep the meta
information (~12 KB). This meta information is required to ensure the data consistency during
simultaneous read and write operations. The backups included in these chains disappear from the
GUI as soon as the retention rule is applied, although they physically exist until the entire chain is
deleted.

In all other cases, backups whose deletion is postponed are marked with the trash can icon ( ) in
the GUI. If you delete such a backup by clicking the X sign, consolidation will be performed.

Backup file name

This option defines the names of the backup files that are created by the protection plan or by the
cloud applications backup plan.

428 © Acronis International GmbH, 2003-2024

For backup files that are created by protection plans, you can see these names in a file manager
when you browse the backup location.

What is a backup file?

Each protection plan creates one or more files in the backup location, depending on which backup
scheme and which backup format is used. The following table lists the files that can be created per
machine or mailbox.

Always incremental (single-file) Other backup schemes

Version One TIB file and one XML metadata file Multiple TIB files and one XML metadata file
11 backup
format

Version One TIBX file per backup chain (a full or differential backup, and all incremental backups that
12 backup depend on it). If the size of a file stored in a local or network (SMB) folder exceeds 200 GB, the
format file is split to 200-GB files by default.

All files have the same name, with or without the addition of a timestamp or a sequence number.
You can define this name (referred to as the backup file name) when you create or edit a protection
plan or a cloud applications backup plan.

Note
Timestamp is added to the backup file name only in the version 11 backup format.

If you change a backup file name in a protection plan or a cloud applications backup plan, the next
backup will be a full backup.

If you specify a file name of an existing backup of the same machine, a full, incremental, or
differential backup will be created according to the plan schedule.

Note
If you move backup files (.tibx) from their original storage, do not rename them. Renamed files will
appear corrupted and you will not be able to recover data from them.

It is possible to set backup file names for locations that cannot be browsed by a file manager (such
as the cloud storage). In this case, you will see the custom names on the Backup storage tab.

Where can I see backup file names?

For protection plans, on the Backup storage tab, select the location, and then select the backup
archive.

l The default backup file name is shown on the Details panel.

l If you set a non-default backup file name, it will be shown directly on the Backup storage tab, in
the Name column.

429 © Acronis International GmbH, 2003-2024

For cloud applications backup plans, on the Backup storage tab, select the location, select the
backup archive, and then click the gear icon.

Limitations for backup file names

l A backup file name cannot end with a digit.
In the default backup file name, to prevent the name from ending with a digit, the letter "A" is
appended. When creating a custom name, always make sure that it does not end with a digit.
When using variables, the name must not end with a variable, because a variable might end with
a digit.
l A backup file name cannot contain the following symbols: ()&?*$<>":\|/#, line endings (\n), and
tabs (\t).

Note
Choose user-friendly backup file names. This will help you to easily distinguish backups when
browsing the backup location with a file manager.

Default backup file name

The default backup file name for backups of entire physical and virtual machines, disks/volumes,
files/folders, Microsoft SQL Server databases, Microsoft Exchange Server databases, and ESXi
configuration is [Machine Name]-[Plan ID]-[Unique ID]A.

The default name for Exchange mailbox backups and Microsoft 365 mailbox backups created by a
local Agent for Microsoft 365 is [Mailbox ID]_mailbox_[Plan ID]A.

The default name for Microsoft Azure backups is prefixed with [Mailbox ID]_. This prefix cannot be
removed.

The default name for cloud application backups created by cloud agents is [Resource Name]_
[Resource Type]_[Resource Id]_[Plan Id]A.

The default name consists of the following variables:

l [Machine Name] This variable is replaced with the name of the machine (the same name that is
shown in the Cyber Protect console).
l [Plan ID], [Plan Id] These variables are replaced with the unique identifier of the protection
plan. This value does not change if the plan is renamed.
l [Unique ID] This variable is replaced with the unique identifier of the selected machine. This
value does not change if the machine is renamed.
l [Mailbox ID] This variable is replaced with the mailbox user's principal name (UPN).
l [Resource Name] This variable is replaced with the cloud data source name, such as the user's
principal name (UPN), SharePoint site URL, or Shared drive name.
l [Resource Type] This variable is replaced with the cloud data source type, such as mailbox,
O365Mailbox, O365PublicFolder, OneDrive, SharePoint, GDrive.

430 © Acronis International GmbH, 2003-2024

l [Resource ID] This variable is replaced with the unique identifier of the cloud data source. This
value does not change if the cloud data source is renamed.
l "A" is a safeguard letter that is appended to prevent the name from ending with a digit.

The diagram below shows the default backup file name.

The diagram below shows the default backup file name for Microsoft 365 mailbox backups
performed by a local agent.

Names without variables

If you change the backup file name to MyBackup, the backup files will look like the following
examples. Both examples assume daily incremental backups scheduled at 14:40, starting from
September 13, 2016.

For the version 12 format with the Always incremental (single-file) backup scheme:

MyBackup.tibx

For the version 12 format with other backup schemes:

MyBackup.tibx
MyBackup-0001.tibx
MyBackup-0002.tibx
...

Using variables
Besides the variables that are used by default, you can use the following variables:

l The [Plan name] variable, which is replaced with the name of the protection plan.
l The [Virtualization Server Type] variable, which is replaced with "vmwesx" if virtual machines
are backed up by Agent for VMware or with "mshyperv" if virtual machines are backed up by
Agent for Hyper-V.

431 © Acronis International GmbH, 2003-2024

If multiple machines or mailboxes are selected for backup, the backup file name must contain the
[Machine Name], the [Unique ID], the [Mailbox ID], the [Resource Name], or the [Resource Id]
variable.

Creating backups in an existing backup archive

You can configure the backups of a workload to be added to an existing backup archive.

This option might be useful, for example, when a protection plan is applied to a single machine, and
you have to remove this machine from the Cyber Protect console, or uninstall the agent along with
its configuration settings. After you add the machine again or reinstall the agent, you can force the
protection plan to continue backing up to the original archive.

To configure the backups of a workload to be added to an existing backup archive

Non-cloud-to-cloud workloads

1. On the All devices screen, click the workload, and then click Protect.
2. In the protection plan settings, extend the Backup module.
3. Click Backup options, and then click Change.
4. On the Backup file name tab, click Select.
The Select button shows the backups in the location selected in the Where to back up section
of the protection plan.

Note
The Select button is only available for protection plans that are created for and applied to a
single workload.

5. Select an archive, and then click Done.

6. Click Done, and then click Apply.

Cloud-to-cloud workloads

1. On the Management > Cloud applications backup tab, select the plan.
2. Click Edit, and then click the gear icon next to the plan's name.
3. On the File backup name tab, click Select.

432 © Acronis International GmbH, 2003-2024

 Note
The Select button is only available for backup plans that are created for and applied to a single
workload.

4. Select a backup archive, and then click Done.

5. Click Done, and then click Save changes.

Backup format
The Backup format option defines the format of the backups created by the protection plan. This
option is available only for protection plans that already use the version 11 backup format. If this is
the case, you can change the backup format to version 12. After you switch the backup format to
version 12, the option becomes unavailable.

l Version 11
The legacy format preserved for backward compatibility.

Note
You cannot back up Database Availability Groups (DAG) by using the backup format version 11.
Backing up of DAG is supported only in the version 12 format.

l Version 12
The backup format that was introduced in Acronis Backup 12 for faster backup and recovery.
Each backup chain (a full or differential backup, and all incremental backups that depend on it) is
saved to a single TIBX file.

Backup format and backup files

For backup locations that can be browsed with a file manager (such as local or network folders), the
backup format determines the number of files and their extension. The following table lists the files
that can be created per machine or mailbox.

Always incremental (single-file) Other backup schemes

Version One TIB file and one XML metadata file Multiple TIB files and one XML metadata file
11 backup
format

Version One TIBX file per backup chain (a full or differential backup, and all incremental backups that
12 backup depend on it). If the size of a file stored in a local or network (SMB) folder exceeds 200 GB, the
format file is split to 200-GB files by default.

Changing the backup format to version 12 (TIBX)

If you change the backup format from version 11 (TIB format) to version 12 (TIBX format):

433 © Acronis International GmbH, 2003-2024

l The next backup will be full.
l In backup locations that can be browsed with a file manager (such as local or network folders), a
new TIBX file will be created. The new file will have the name of the original file, appended with
the _v12A suffix.
l Retention rules and replication will be applied only to the new backups.
l The old backups will not be deleted and will remain available on the Backup storage tab. You
can delete them manually.
l The old cloud backups will not consume the Cloud storage quota.
l The old local backups will consume the Local backup quota until you delete them manually.

In-archive deduplication
The TIBX backup format of version 12 supports in-archive deduplication that brings the following
advantages:

l Significantly reduced backup size, with built-in block-level deduplication for any type of data
l Efficient handling of hard links ensures that there are no storage duplicates
l Hash-based chunking

Note
In-archive deduplication is enabled by default for all backups in the TIBX format. You do not have to
enable it in the backup options, and you cannot disable it.

Backup format compatibility across different product versions

For information about backup format compatibility, see Backup archive compatibility across
different product versions (1689).

Backup validation
Validation is an operation that checks the possibility of data recovery from a backup. When this
option is enabled, each backup created by the protection plan is validated immediately after
creation, by using the checksum verification method. This operation is performed by the protection
agent.

The preset is: Disabled.

For more information about the validation via checksum verification, refer to "Checksum
verification" (p. 197).

Note
Depending on the settings chosen by your service provider, validation might not be available when
backing up to the cloud storage. Validation is also not available for backup locations on public
clouds.

434 © Acronis International GmbH, 2003-2024

Changed block tracking (CBT)
This option is effective for the following backups:

l Disk-level backups of virtual machines

l Disk-level backups of physical machines running Windows
l Backups of Microsoft SQL Server databases
l Backups of Microsoft Exchange Server databases

The preset is: Enabled.

This option determines whether to use Changed Block Tracking (CBT) when performing an
incremental or differential backup.

The CBT technology accelerates the backup process. Changes to the disk or database content are
continuously tracked at the block level. When a backup starts, the changes can be immediately
saved to the backup.

Cluster backup mode

Note
This feature is available with the Advanced Backup pack.

These options are effective for database-level backup of Microsoft SQL Server and Microsoft
Exchange Server.

These options are effective only if the cluster itself (Microsoft SQL Server Always On Availability
Groups (AAG) or Microsoft Exchange Server Database Availability Group (DAG)) is selected for
backup, rather than the individual nodes or databases inside of it. If you select individual items
inside the cluster, the backup will not be cluster-aware and only the selected copies of the items will
be backed up.

Microsoft SQL Server

This option determines the backup mode for SQL Server Always On Availability Groups (AAG). For
this option to be effective, Agent for SQL must be installed on all of the AAG nodes. For more
information about backing up Always On Availability Groups, refer to "Protecting Always On
Availability Groups (AAG)".

The preset is: Secondary replica if possible.

You can choose one of the following:

l Secondary replica if possible

If all secondary replicas are offline, the primary replica is backed up. Backing up the primary
replica may slow down the SQL Server operation, but the data will be backed up in the most
recent state.

435 © Acronis International GmbH, 2003-2024

l Secondary replica
If all secondary replicas are offline, the backup will fail. Backing up secondary replicas does not
affect the SQL server performance and allows you to extend the backup window. However,
passive replicas may contain information that is not up-to-date, because such replicas are often
set to be updated asynchronously (lagged).
l Primary replica
If the primary replica is offline, the backup will fail. Backing up the primary replica may slow down
the SQL Server operation, but the data will be backed up in the most recent state.

Regardless of the value of this option, to ensure the database consistency, the software skips
databases that are not in the SYNCHRONIZED or SYNCHRONIZING states when the backup starts.
If all databases are skipped, the backup fails.

Microsoft Exchange Server

This option determines the backup mode for Exchange Server Database Availability Groups (DAG).
For this option to be effective, Agent for Exchange must be installed on all of the DAG nodes. For
more information about backing up Database Availability Groups, refer to "Protecting Database
Availability Groups (DAG)".

The preset is: Passive copy if possible.

You can choose one of the following:

l Passive copy if possible

If all passive copies are offline, the active copy is backed up. Backing up the active copy may slow
down the Exchange Server operation, but the data will be backed up in the most recent state.
l Passive copy
If all passive copies are offline, the backup will fail. Backing up passive copies does not affect the
Exchange Server performance and allows you to extend the backup window. However, passive
copies may contain information that is not up-to-date, because such copies are often set to be
updated asynchronously (lagged).
l Active copy
If the active copy is offline, the backup will fail. Backing up the active copy may slow down the
Exchange Server operation, but the data will be backed up in the most recent state.

Regardless of the value of this option, to ensure the database consistency, the software skips
databases that are not in the HEALTHY or ACTIVE states when the backup starts. If all databases are
skipped, the backup fails.

Compression level

Note
This option is not available for cloud-to-cloud backups. Compression for these backups is enabled
by default with a fixed level that corresponds to the Normal level below.

436 © Acronis International GmbH, 2003-2024

The option defines the level of compression applied to the data being backed up. The available
levels are: None, Normal, High, Maximum.

The preset is: Normal.

A higher compression level means that the backup process takes more time, but the resulting
backup occupies less space. Currently, the High and Maximum levels work similarly.

The optimal data compression level depends on the type of data being backed up. For example,
even maximum compression will not significantly reduce the backup size if the backup contains
essentially compressed files, such as .jpg, .pdf or .mp3. However, formats such as .doc or .xls will be
compressed well.

Error handling
These options enable you to specify how to handle errors that might occur during backup.

Re-attempt, if an error occurs

The preset is: Enabled. Number of attempts: 10. Interval between attempts: 30 seconds.

When a recoverable error occurs, the program re-attempts to perform the unsuccessful operation.
You can set the time interval and the number of attempts. The attempts will be stopped as soon as
the operation succeeds or the specified number of attempts are performed, depending on which
comes first.

For example, if the backup destination on the network becomes unavailable or not reachable during
a running backup, the software will attempt to reach the destination every 30 seconds, but no more
than 30 times. The attempts will be stopped as soon as the connection is resumed or the specified
number of attempts is performed, depending on which comes first.

However, if the backup destination is not available when the backup starts, only 10 attempts will be
made.

Do not show messages and dialogs while processing (silent mode)

The preset is: Enabled.

With the silent mode enabled, the program will automatically handle situations requiring user
interaction (except for handling bad sectors, which is defined as a separate option). If an operation
cannot continue without user interaction, it will fail. Details of the operation, including errors, if any,
can be found in the operation log.

Ignore bad sectors

The preset is: Disabled.

When this option is disabled, each time the program comes across a bad sector, the backup activity
will be assigned the Interaction required status. In order to back up the valid information on a

437 © Acronis International GmbH, 2003-2024

rapidly dying disk, enable ignoring bad sectors. The rest of the data will be backed up and you will
be able to mount the resulting disk backup and extract valid files to another disk.

Note
Skipping bad sectors is not supported on Linux. You can back up Linux systems with bad sectors in
offline mode, by using the bootable media builder in the on-premises version of Cyber Protect.
Using the on-premises bootable media builder requires a separate license. Contact support for
assistance.

Re-attempt, if an error occurs during VM snapshot creation

The preset is: Enabled. Number of attempts: 3. Interval between attempts: 5 minutes.

When taking a virtual machine snapshot fails, the program re-attempts to perform the unsuccessful
operation. You can set the time interval and the number of attempts. The attempts will be stopped
as soon as the operation succeeds OR the specified number of attempts are performed, depending
on which comes first.

Fast incremental/differential backup

This option is effective for incremental and differential disk-level backup.

This option is not effective (always disabled) for volumes formatted with the JFS, ReiserFS3,
ReiserFS4, ReFS, or XFS file systems.

The preset is: Enabled.

Incremental or differential backup captures only data changes. To speed up the backup process, the
program determines whether a file has changed or not by the file size and the date/time when the
file was last modified. Disabling this feature will make the program compare the entire file contents
to those stored in the backup.

File filters (Inclusions/Exclusions)

Use file filters to include only specific files and folders in a backup, or to exclude specific files and
folders from a backup.

File filters are available for entire machine backups, disk-level backups, and file-level backups, unless
stated otherwise.

File filters are not available with the XFS, JFS, exFAT, and ReiserFS4 file systems. For more
information, see "Supported file systems" (p. 51).

File filters are not applicable to dynamic disks (LVM or LDM volumes) of virtual machines that are
backed up in the agentless mode, for example, by Agent for VMware, Agent for Hyper-V, or Agent for
Scale Computing.

To enable file filters

438 © Acronis International GmbH, 2003-2024

1. In a protection plan, expand the Backup module.
2. In Backup options, click Change.
3. Select File filters (Inclusions/Exclusions).
4. Use any of the options described below.

Inclusion and exclusion filters

There are two filters – inclusion filter and exclusion filter.

l Include only the files that match the following criteria

If you specify C:\File.exe in the inclusion filter, only this file will be backed up, even if you
selected Entire machine backup.

Note
This filter is not supported for file-level backups when the backup format is Version 11, and the
backup destination is not the cloud storage.

l Exclude the files that match the following criteria

If you specify C:\File.exe in the exclusion filter, this file will be skipped during a backup, even if
you selected Entire machine backup.

You can use both filters in the same time. The exclusion filter takes precedence over the inclusion
filter – that is, if you specify C:\File.exe in both fields, this file will be skipped during a backup.

Filter criteria
As filter criteria, you can use file and folder names, full paths to files and folders, and masks with
wildcard symbols.

The filter criteria are case insensitive. For example, by specifying C:\Temp, you will select C:\TEMP and
C:\temp.

l Name
Specify the name of the file or folder, such as Document.txt. All files and folders with that name
will be selected.
l Full path
Specify the full path to the file or folder, starting with the drive letter (when backing up Windows)
or the root directory (when backing up Linux or macOS). In Windows, Linux, and macOS, you can
use forward slashes (as in C:/Temp/File.tmp). In Windows, you can also use the traditional
backslashes (as in C:\Temp\File.tmp).

439 © Acronis International GmbH, 2003-2024

 Important
If the operating system of the backed-up machine is not detected correctly during a disk-level
backup, full path file filters will not work. For an exclusion filter, a warning will be shown. If there
is an inclusion filter, the backup will fail.
For example, a full path to a file could be C:\Temp\File.tmp. A full path filter, which includes the
drive letter or the root directory, such as C:\Temp\File.tmp or C:\Temp\*, will result in a warning or
failure.
A filter that does not use the drive letter or the root directory (for example, Temp\* or
Temp\File.tmp) or a filter that starts with an asterisk (for example, *C:\) will not result in warning
or failure. However, if the operating system of the backed-up machine is not detected correctly,
these filters will not work, either.

l Mask
You can use the following wildcard characters for the names and full paths: asterisk (*), double
asterisk (**) , and question mark (?).
The asterisk (*) represents zero or more characters. For example, the filter criterion Doc*.txt
matches the files Doc.txt and Document.txt.
The double asterisk (**) represents zero or more characters, including the slash character. For
example, **/Docs/**.txt matches all .txt files in all subfolders of all folders named Docs. You can
use the double asterisk (**) wildcard only for backups in the Version 12 format.
The question mark (?) represents only one character. For example, Doc?.txt matches the files
Doc1.txt and Docs.txt, but not the files Doc.txt or Doc11.txt.

File-level backup snapshot

This option is effective only for file-level backup.

This option defines whether to back up files one by one or by taking an instant data snapshot.

Note
Files that are stored on network shares are always backed up one by one.

The preset is:

l If only machines running Linux are selected for backup: Do not create a snapshot.
l Otherwise: Create snapshot if it is possible.

You can select one of the following:

l Create a snapshot if it is possible

Back up files directly if taking a snapshot is not possible.
l Always create a snapshot
The snapshot enables backing up of all files including files opened for exclusive access. The files
will be backed up at the same point in time. Choose this setting only if these factors are critical,

440 © Acronis International GmbH, 2003-2024

 that is, backing up files without a snapshot does not make sense. If a snapshot cannot be taken,
the backup will fail.
l Do not create a snapshot
Always back up files directly. Trying to back up files that are opened for exclusive access will
result in a read error. Files in the backup may be not time-consistent.

Forensic data
Viruses, malware, and ransomware can carry out malicious activities, such as stealing or changing
data. These activities may need to be investigated, which is possible only if digital evidence is
provided. However, pieces of digital evidence, such as files or activity traces, may be deleted or the
machine on which the malicious activity happened may become unavailable.

Backups with forensic data allow investigators to analyze disk areas that are not usually included in
a regular disk backup. The Forensic data backup option allows you to collect the following pieces of
digital evidence that can be used in forensic investigations: snapshots of unused disk space,
memory dumps, and snapshots of running processes.

Backups with forensic data are automatically notarized.

The Forensic data option is available only for entire machine backups of Windows machines that
run the following operating systems:

l Windows 8.1, Windows 10

l Windows Server 2012 R2 – Windows Server 2019

Backups with forensic data are not available for the following machines:

l Machines that are connected to your network through VPN and do not have direct access to the
Internet
l Machines with disks that are encrypted by BitLocker

Note
You cannot modify the forensic data settings after you apply a protection plan with enabled Backup
module to a machine. To use different forensic data settings, create a new protection plan.

You can store backups with forensic data in the following locations:

l Cloud storage
l Local folder

Note
The local folder location is supported only for external hard disks connected via USB.
Local dynamic disks are not supported as a location for backups with forensic data.

l Network folder

441 © Acronis International GmbH, 2003-2024

 Forensic backup process
The system performs the following during a forensic backup process:

1. Collects raw memory dump and the list of running processes.

2. Automatically reboots a machine into the bootable media.
3. Creates the backup that includes both the occupied and unallocated space.
4. Notarizes the backed-up disks.
5. Reboots into the live operating system and continues plan execution (for example, replication,
retention, validation and other).

To configure forensic data collection

1. In the Cyber Protect console, go to Devices > All devices. Alternatively, the protection plan can
be created from the Management tab.
2. Select the device and click Protect.
3. In the protection plan, enable the Backup module.
4. In What to back up, select Entire machine.
5. In Backup options, click Change.
6. Find the Forensic data option.
7. Enable Collect forensic data. The system will automatically collect a memory dump and create
a snapshot of running processes.

Note
Full memory dump may contain sensitive data such as passwords.

8. Specify the location.

9. Click Run Now to perform a backup with forensic data right away or wait until the backup is
created according to the schedule.
10. Go to Monitoring > Activities, verify that the backup with forensic data was successfully
created.

As a result, backups will include forensic data and you will be able to get them and analyze. Backups
with forensic data are marked and can be filtered among other backups in Backup storage >
Locations by using the Only with forensic data option.

How to get forensic data from a backup?

1. In the Cyber Protect console, go to Backup storage, select the location with backups that
include forensic data.
2. Select the backup with forensic data and click Show backups.
3. Click Recover for the backup with forensic data.

442 © Acronis International GmbH, 2003-2024

 l To get only the forensic data, click Forensic data.

The system will show a folder with forensic data. Select a memory dump file or any other
forensic file, and then click Download.

l To recover a full forensic backup, click Entire machine. The system will recover the backup
without the boot mode. Thus, it will be possible to check that the disk was not changed.

You can use the provided memory dump with several of third-party forensic software, for example,
use Volatility Framework at https://www.volatilityfoundation.org/ for further memory analysis.

Notarization of backups with forensic data

To ensure that a backup with forensic data is exactly the image that was taken and it was not
compromised, the backup module provides the notarization of backups with forensic data.

443 © Acronis International GmbH, 2003-2024

How it works
Notarization enables you to prove that a disk with forensic data is authentic and unchanged since it
was backed up.

During a backup, the agent calculates the hash codes of the backed-up disks, builds a hash tree,
saves the tree in the backup, and then sends the hash tree root to the notary service. The notary
service saves the hash tree root in the Ethereum blockchain database to ensure that this value does
not change.

When verifying the authenticity of the disk with forensic data, the agent calculates the hash of the
disk, and then compares it with the hash that is stored in the hash tree inside the backup. If these
hashes do not match, the disk is considered not authentic. Otherwise, the disk authenticity is
guaranteed by the hash tree.

To verify that the hash tree itself was not compromised, the agent sends the hash tree root to the
notary service. The notary service compares it with the one stored in the blockchain database. If the
hashes match, the selected disk is guaranteed to be authentic. Otherwise, the software displays a
message that the disk is not authentic.

The scheme below shows shortly the notarization process for backups with forensic data.

To verify the notarized disk backup manually, you can get the certificate for it and follow the
verification procedure shown with the certificate by using the tibxread tool.

Getting the certificate for backups with forensic data

To get the certificate for a backup with forensic data from the console, do the following:

1. Go to Backup storage and select the backup with forensic data.

2. Recover the entire machine.

444 © Acronis International GmbH, 2003-2024

3. The system opens the Disk Mapping view.
4. Click the Get certificate icon for the disk.
5. The system will generate the certificate and open a new window in the browser with the
certificate. Below the certificate you will see the instruction for manual verification of notarized
disk backup.

The tool "tibxread" for getting the backed-up data

Cyber Protection provides the tool, called tibxread, for manual check of the backed-up disk integrity.
The tool allows you to get data from a backup and calculate hash of the specified disk. The tool is
installed automatically with the following components: Agent for Windows, Agent for Linux, and
Agent for Mac.

The installation path: the same folder as the agent has (for example, C:\Program
Files\BackupClient\BackupAndRecovery).

The supported locations are:

l The local disk

l The network folder (CIFS/SMB) that can be accessed without the credentials.
In case of a password-protected network folder, you can mount the network folder to the local
folder by using the OS tools and then the local folder as the source for this tool.
l The cloud storage
You should provide the URL, port, and certificate. The URL and port can be obtained from the
Windows registry key or configuration files on Linux/Mac machines.
For Windows:

HKEY_LOCAL_
MACHINE\SOFTWARE\Acronis\BackupAndRecovery\Settings\OnlineBackup\FesAddressCache\Defa
ult\<tenant_login>\FesUri

For Linux:

/etc/Acronis/BackupAndRecovery.config

For macOS:

/Library/Application Support/Acronis/Registry/BackupAndRecovery.config

The certificate can be found in the following locations:

For Windows:

%allusersprofile%\Acronis\BackupAndRecovery\OnlineBackup\Default

For Linux:

/var/lib/Acronis/BackupAndRecovery/OnlineBackup/Default

445 © Acronis International GmbH, 2003-2024

 For macOS:

/Library/Application Support/Acronis/BackupAndRecovery/OnlineBackup/Default

The tool has the following commands:

l list backups
l list content
l get content
l calculate hash

list backups
Lists recovery points in a backup.

SYNOPSIS:

tibxread list backups --loc=URI --arc=BACKUP_NAME --raw

Options

--loc=URI
--arc=BACKUP_NAME
--raw
--utc
--log=PATH

Output template:

GUID Date Date timestamp

---- ------ --------------
<guid> <date> <timestamp>

<guid> – a backup GUID.

<date> – a creation date of the backup. Format is “DD.MM.YYYY HH24:MM:SS”. In local timezone by
default (can be changed by using the --utc option).

Output example:

GUID Date Date timestamp

---- ------ --------------
516FCE73-5E5A-49EF-B673-A9EACB4093B8 18.12.2019 16:01:05 1576684865
516FCE73-5E5A-49EF-B673-A9EACB4093B9 18.12.2019 16:02:05 1576684925

list content
Lists content in a recovery point.

SYNOPSIS:

446 © Acronis International GmbH, 2003-2024

 tibxread list content --loc=URI --arc=BACKUP_NAME --password --backup=RECOVERY_POINT_ID
--raw --log=PATH

Options

--loc=URI
--arc=BACKUP_NAME
--password
--backup=RECOVERY_POINT_ID
--raw
--log=PATH

Output template:

Disk Size Notarization status

-------- ------ ---------------------
<number> <size> <notarization_status>

<number> – identifier of the disk.

<size> – size in bytes.

<notarization_status> – the following statuses are possible: Without notarization, Notarized, Next
backup.

Output example:

Disk Size Notary status

-------- ------ --------------
1 123123465798 Notarized
2 123123465798 Notarized

get content
Writes content of the specified disk in the recovery point to the standard output (stdout).

SYNOPSIS:

tibxread get content --loc=URI --arc=BACKUP_NAME --password --backup=RECOVERY_POINT_ID -

-disk=DISK_NUMBER --raw --log=PATH --progress

Options

--loc=URI
--arc=BACKUP_NAME
--password
--backup=RECOVERY_POINT_ID
--disk=DISK_NUMBER
--raw

447 © Acronis International GmbH, 2003-2024

--log=PATH
--progress

calculate hash
Calculates the hash of the specified disk in the recovery point by using the SHA-2 (256-bit) algorithm
and writes it to the stdout.

SYNOPSIS:

tibxread calculate hash --loc=URI --arc=BACKUP_NAME --password --backup=RECOVERY_POINT_

ID --disk=DISK_NUMBER --raw --log=PATH --progress

Options

--loc=URI
--arc=BACKUP_NAME
--password
--backup=RECOVERY_POINT_ID
--disk=DISK_NUMBER
--raw
--log=PATH

Options description

Option Description

--arc=BACKUP_ The backup file name that you can get from the backup properties in the Cyber
NAME Protect console. The backup file must be specified with the extension .tibx.

-- The recovery point identifier

backup=RECOVE
RY_POINT_ID

--disk=DISK_ Disk number (the same as was written to the output of the "get content" command)
NUMBER

--loc=URI A backup location URI. The possible formats of the "--loc" option are:

l Local path name (Windows)

c:/upload/backups
l Local path name (Linux)
/var/tmp
l SMB/CIFS
\\server\folder
l Cloud storage
--loc=<IP_address>:443 --cert=<path_to_certificate> [--storage_path=/1]
<IP_address> – you can find it in the registry key in Windows: HKEY_LOCAL_

448 © Acronis International GmbH, 2003-2024

 MACHINE\SOFTWARE\Acronis\BackupAndRecovery\Settings\OnlineBackup\FesAdd
ressCache\Default\<tenant_login>\FesUri
<path_to_certificate> – a path to the certificate file to access Cyber Protect Cloud.
For example, in Windows this certificate is located in
C:\ProgramData\Acronis\BackupAndRecovery\OnlineBackup\Default\<username>.crt
where <username> – is your account name to access Cyber Protect Cloud.

--log=PATH Enables writing the logs by the specified PATH (local path only, format is the same as
for --loc=URI parameter). Logging level is DEBUG.

-- An encryption password for your backup. If the backup is not encrypted, leave this
password=PASS value empty.
WORD

--raw Hides the headers (2 first rows) in the command output. It is used when the
command output should be parsed.

Output example without "--raw":

GUID Date Date timestamp

---- ------ --------------
516FCE73-5E5A-49EF-B673-A9EACB4093B8 18.12.2019 16:01:05 1576684865
516FCE73-5E5A-49EF-B673-A9EACB4093B9 18.12.2019 16:02:05 1576684925

Output with"--raw":

516FCE73-5E5A-49EF-B673-A9EACB4093B8 18.12.2019 16:01:05 1576684865

516FCE73-5E5A-49EF-B673-A9EACB4093B9 18.12.2019 16:02:05 1576684925

--utc Shows dates in UTC

--progress Shows progress of the operation.

For example:

1%
2%
3%
4%
...
100%

Log truncation
This option is effective for backup of Microsoft SQL Server databases and for disk-level backup with
enabled Microsoft SQL Server application backup.

This option defines whether the SQL Server transaction logs are truncated after a successful backup.

The preset is: Enabled.

449 © Acronis International GmbH, 2003-2024

When this option is enabled, a database can be recovered only to a point in time of a backup
created by this software. Disable this option if you back up transaction logs by using the native
backup engine of Microsoft SQL Server. You will be able to apply the transaction logs after a
recovery and thus recover a database to any point in time.

LVM snapshotting
This option is effective only for physical machines.

This option is effective for disk-level backup of volumes managed by Linux Logical Volume Manager
(LVM). Such volumes are also called logical volumes.

This option defines how a snapshot of a logical volume is taken. The backup software can do this on
its own or rely on Linux Logical Volume Manager (LVM).

The preset is: By the backup software.

l By the backup software. The snapshot data is kept mostly in RAM. The backup is faster, and
unallocated space on the volume group is not required. Therefore, we recommend that you
change the preset only if you are experiencing problems with backing up logical volumes.
l By LVM. The snapshot is stored on unallocated space of the volume group. If the unallocated
space is missing, the snapshot will be taken by the backup software.

The snapshot is used only during the backup operation, and is automatically deleted when the
backup operation completes. No temporary files are kept.

Mount points
This option is effective only in Windows for a file-level backup of a data source that includes
mounted volumes or cluster shared volumes.

This option is effective only when you select for backup a folder that is higher in the folder hierarchy
than the mount point. (A mount point is a folder on which an additional volume is logically
attached.)

l If such folder (a parent folder) is selected for backup, and the Mount points option is enabled, all
files located on the mounted volume will be included in the backup. If the Mount points option is
disabled, the mount point in the backup will be empty.
During recovery of a parent folder, the mount point content will or will not be recovered,
depending on whether the Mount points option for recovery is enabled or disabled.
l If you select the mount point directly, or select any folder within the mounted volume, the
selected folders will be considered as ordinary folders. They will be backed up regardless of the
state of the Mount points option and recovered regardless of the state of the Mount points
option for recovery.

The preset is: Disabled.

450 © Acronis International GmbH, 2003-2024

Note
You can back up Hyper-V virtual machines residing on a cluster shared volume by backing up the
required files or the entire volume with file-level backup. Just power off the virtual machines to be
sure that they are backed up in a consistent state.

Example

Let's assume that the C:\Data1\ folder is a mount point for the mounted volume. The volume
contains folders Folder1 and Folder2. You create a protection plan for file-level backup of your
data.

If you select the check box for volume C and enable the Mount points option, the C:\Data1\ folder
in your backup will contain Folder1 and Folder2. When recovering the backed-up data, be aware of
proper using the Mount points option for recovery.

If you select the check box for volume C, and disable the Mount points option, the C:\Data1\ folder
in your backup will be empty.

If you select the check box for the Data1, Folder1 or Folder2 folder, the checked folders will be
included in the backup as ordinary folders, regardless of the state of the Mount points option.

Multi-volume snapshot
This option is effective for backups of physical machines running Windows or Linux.

This option applies to disk-level backup. This option also applies to file-level backup when the file-
level backup is performed by taking a snapshot. (The "File-level backup snapshot" option
determines whether a snapshot is taken during file-level backup).

This option determines whether to take snapshots of multiple volumes at the same time or one by
one.

The preset is:

l If at least one machine running Windows is selected for backup: Enabled.

l Otherwise: Disabled.

When this option is enabled, snapshots of all volumes being backed up are created simultaneously.
Use this option to create a time-consistent backup of data spanning multiple volumes; for instance,
for an Oracle database.

When this option is disabled, the volumes' snapshots are taken one after the other. As a result, if the
data spans several volumes, the resulting backup may be not consistent.

One-click recovery

Note
This feature is available with the Advanced Backup pack.

451 © Acronis International GmbH, 2003-2024

With One-click recovery you can automatically recover a disk backup of your Windows or Linux
machine. This backup can be a backup of the entire machine, or a backup of specific disks or
volumes on this machine.

One-click recovery supports the following operations:

l Automatic recovery from the latest backup

l Recovery from a specific backup (also know as recovery point) within the backup archive

One-click recovery supports the following backup storages:

l Secure Zone
l Local folder
l Network folder
l Cloud storage

Important
Suspend the BitLocker encryption until the next restart of your machine when you perform any of
the following operations:

l Creating, modifying, or deleting Secure Zone.

l Enabling or disabling Startup Recovery Manager.
l [Only if Startup Recovery Manager was not already enabled] Running the first backup after
enabling One-click recovery in the protection plan. This operation enables Startup Recovery
Manager automatically.
l Updating Startup Recovery Manager, for example by updating the protection.

If the BitLocker encryption was not suspended during these operations, you will need to specify
your Bitlocker PIN after restarting your machine.

Enabling One-click recovery

One-click recovery is a backup option in the protection plan. For more information on how to create
a plan, see "Creating a protection plan" (p. 206).

Note
Enabling One-click recovery also enables Startup Recovery Manager on the target machine. If
Startup Recovery Manager cannot be enabled, the backup operation that creates One-click recovery
backups will fail. For more information about Startup Recovery Manager, see "Startup Recovery
Manager" (p. 696).

To enable One-click recovery

1. In the protection plan, expand the Backup module.

2. In What to back up, select Entire machine or Disk/volumes.
3. [If you selected Disk/volumes]. In Items to back up, specify the disk or volumes to back up.
4. In Backup options, click Change, and then select One-click recovery.

452 © Acronis International GmbH, 2003-2024

5. Enable the One-click recovery switch.
6. [Optional] Enable the Recovery password switch, and then specify a password.

Important
We strongly recommend that you specify a recovery password. Ensure that the user who
performs One-click recovery on the target machine knows this password.

453 © Acronis International GmbH, 2003-2024

7. Click Done.
8. Configure the other elements of the protection plan according to your needs, and then save the
plan.

As a result, after the protection plan runs and creates a backup, One-click recovery becomes
accessible to the users of the protected machine.

Important
One-click recovery becomes temporarily unavailable when you update the protection agent. To re-
enable one-click recovery, run a backup. When the backup completes, you will be able to perform
one-click recovery again.

Disabling One-click recovery

You can disable One-click recovery for a specific workload in the following ways:

l Disable the One-click recovery option in the protection plan that is applied to the workload.
l Revoke the protection plan in which the One-click recovery option is enabled.
l Delete the protection plan in which the One-click recovery option is enabled.

Recovering a machine with One-click recovery

Prerequisites
l A protection plan with enabled One-click recovery backup option is applied to the machine.
l There is at least one disk backup of the machine.

To recover a machine

1. Reboot the machine that you want to recover.

2. During the reboot, press F11 to enter Startup Recovery Manager.
The rescue media window opens.
3. Select Acronis Cyber Protect.
4. [If a recovery password was specified in the protection plan] Enter the recovery password, and
then click OK.
5. Select a One-click recovery option.
l To recover the latest backup automatically, select the first option, and then click OK.
l To recover another backup within the backup archive, select the second option, and then click

454 © Acronis International GmbH, 2003-2024

 OK.

6. Confirm your choice by clicking Yes.

The rescue media window opens, and then disappears. The recovery procedure continues
without it.
7. [If you chose to recover a specific backup] Select the backup that you want to recover, and then
click OK.

After a while, the recovery starts and its progress is shown. When the recovery completes, your
machine reboots.

455 © Acronis International GmbH, 2003-2024

Performance and backup window
This option enables you to set one of three levels of backup performance (high, low, prohibited) for
every hour within a week. This way, you can define a time window when backups are allowed to
start and run. The high and low performance levels are configurable in terms of the process priority
and output speed.

This option is not available for backups executed by the cloud agents, such as website backups or
backups of servers located on the cloud recovery site.

This option is effective only for the backup and backup replication processes. Post-backup
commands and other operations included in a protection plan (for example, validation) will run
regardless of this option.

The preset is: Disabled.

When this option is disabled, backups are allowed to run at any time, with the following parameters
(no matter if the parameters were changed against the preset value):

l CPU priority: Low (in Windows, it corresponds to Below normal)

l Output speed: Unlimited

When this option is enabled, scheduled backups are allowed or blocked according to the
performance parameters specified for the current hour. At the beginning of an hour when backups
are blocked, a backup process is automatically stopped and an alert is generated. Even if scheduled

456 © Acronis International GmbH, 2003-2024

backups are blocked, a backup can be started manually. It will use the performance parameters of
the most recent hour when backups were allowed.

Note
You can configure performance and backup window for every replication location individually. To
access the settings of the replication location, in the protection plan, click the gear icon next to the
location name, and then click Performance and backup window.

Backup window
Each rectangle represents an hour within a week day. Click a rectangle to cycle through the
following states:

l Green: backup is allowed with the parameters specified in the green section below.
l Blue: backup is allowed with the parameters specified in the blue section below.
This state is not available if the backup format is set to Version 11.
l Gray: backup is blocked.

You can click and drag to change the state of multiple rectangles simultaneously.

457 © Acronis International GmbH, 2003-2024

CPU priority
This parameter defines the priority of the backup process in the operating system.

The available settings are: Low, Normal, High.

458 © Acronis International GmbH, 2003-2024

The priority of a process running in a system determines the amount of CPU and system resources
allocated to that process. Decreasing the backup priority will free more resources for other
applications. Increasing the backup priority might speed up the backup process by requesting the
operating system to allocate more resources like the CPU to the backup application. However, the
resulting effect will depend on the overall CPU usage and other factors like disk in/out speed or
network traffic.

This option sets the priority of the backup process (service_process.exe) in Windows and the
niceness of the backup process (service_process) in Linux and macOS.

The table below summarizes the mapping for this setting in Windows, Linux, and macOS.

Cyber Protection priority Windows Linux and macOS

priority niceness

Low Below normal 10

Normal Normal 0

High High -10

Output speed during backup

This parameter enables you to limit the hard drive writing speed (when backing up to a local folder)
or the speed of transferring the backup data through the network (when backing up to a network

459 © Acronis International GmbH, 2003-2024

share or to cloud storage).

When this option is enabled, you can specify the maximum allowed output speed:

l As a percentage of the estimated writing speed of the destination hard disk (when backing up to a
local folder) or of the estimated maximum speed of the network connection (when backing up to
a network share or cloud storage).
This setting works only if the agent is running in Windows.
l In KB/second (for all destinations).

Physical Data Shipping

This option is available if the backup or replication destination is the cloud storage and the backup
format is set to Version 12.

This option is effective for disk-level backups and file backups created by Agent for Windows, Agent
for Linux, Agent for Mac, Agent for VMware, Agent for Hyper-V, and Agent for Virtuozzo.

Use this option to ship the first full backup created by a protection plan to the cloud storage on a
hard disk drive by using the Physical Data Shipping service. The subsequent incremental backups
are performed over the network.

For local backups that are replicated to cloud, incremental backups continue and are saved locally
until the initial backup is uploaded in the cloud storage. Then all incremental changes are replicated
to the cloud and the replication continues per the backup schedule.

The preset is: Disabled.

About the Physical Data Shipping service

The Physical Data Shipping service web interface is available only to administrators.

For detailed instructions about using the Physical Data Shipping service and the order creation tool,
refer to the Physical Data Shipping Administrator's Guide. To access this document in the Physical
Data Shipping service web interface, click the question mark icon.

Overview of the physical data shipping process

1. [To ship backups that have cloud storage as the primary backup location]
a. Create a new protection plan with backup to cloud.
b. In the Backup options row, click Change.
c. In the list of available options, click Physical Data Shipping.
You can back up directly to a removable drive or back up to a local or a network folder, and then
copy/move the backup(s) to the drive.
2. [To ship local backups that are replicated to cloud]

Note
This option is supported with protection agent version from release C21.06 or later.

460 © Acronis International GmbH, 2003-2024

 a. Create a new protection plan with backup to a local or network storage.
b. Click Add location and select Cloud storage.
c. In the Cloud storage location row, click the gear wheel and select Physical Data Shipping.
3. Under Use Physical Data Shipping, click Yes and Done.
The Encryption option is enabled automatically in the protection plan because all backups that
are shipped must are encrypted.
4. In the Encryption row, click Specify a password and enter a password for encryption.
5. In the Physical Data Shipping row, select the removable drive where the initial backup will be
saved.
6. Click Create to save the protection plan.
7. After the first backup is complete, use the Physical Data Shipping service web interface to
download the order creation tool and create the order.
To access this web interface, log in to the management portal, click Overview > Usage, and then
click Manage service under Physical Data Shipping.

Important
Once the initial full backup is done, the subsequent backups must be performed by the same
protection plan. Another protection plan, even with the same parameters and for the same
machine, will require another Physical Data Shipping cycle.

8. Package the drives and ship them to the data center.

Important
Ensure that you follow the packaging instructions provided in the Physical Data Shipping
Administrator's Guide.

9. Track the order status by using the Physical Data Shipping service web interface. Note that the
subsequent backups will fail until the initial backup is uploaded to the cloud storage.

Pre/Post commands
The option enables you to define the commands to be automatically executed before and after the
backup procedure.

The following scheme illustrates when pre/post commands are executed.

Pre-backup command Backup Post-backup command

Examples of how you can use the pre/post commands:

l Delete some temporary files from the disk before starting backup.
l Configure a third-party antivirus product to be started each time before the backup starts.
l Selectively copy backups to another location. This option may be useful because the replication
configured in a protection plan copies every backup to subsequent locations.

The agent performs the replication after executing the post-backup command.

461 © Acronis International GmbH, 2003-2024

The program does not support interactive commands, i.e. commands that require user input (for
example, "pause").

Pre-backup command
To specify a command/batch file to be executed before the backup process starts

1. Enable the Execute a command before the backup switch.

2. In the Command... field, type a command or browse to a batch file. The program does not
support interactive commands, i.e. commands that require user input (for example, "pause".)
3. In the Working directory field, specify a path to a directory where the command/batch file will
be executed.
4. In the Arguments field specify the command’s execution arguments, if required.
5. Depending on the result you want to obtain, select the appropriate options as described in the
table below.
6. Click Done.

Check box Selection

Fail the Selected Cleared Selected Cleared

backup if
the
command
execution
fails*

Do not back Selected Selected Cleared Cleared

up until the
command
execution is
complete

Result

Preset Perform the backup N/A Perform the backup

after the command concurrently with the
Perform the backup only
is executed despite command execution
after the command is
execution failure or and irrespective of the
successfully executed. Fail
success. command execution
the backup if the command
result.
execution fails.

* A command is considered failed if its exit code is not equal to zero.

462 © Acronis International GmbH, 2003-2024

Note
If a script fails due to a conflict related to a required library version in Linux, exclude the LD_LIBRARY_
PATH and LD_PRELOAD environmental variables, by adding the following lines in your script:

#!/bin/sh
unset LD_LIBRARY_PATH
unset LD_PRELOAD

Post-backup command
To specify a command/executable file to be executed after the backup is completed

1. Enable the Execute a command after the backup switch.

2. In the Command... field, type a command or browse to a batch file.
3. In the Working directory field, specify a path to a directory where the command/batch file will
be executed.
4. In the Arguments field, specify the command execution arguments, if required.
5. Select the Fail the backup if the command execution fails check box if successful execution
of the command is critical for you. The command is considered failed if its exit code is not equal
to zero. If the command execution fails, the backup status will be set to Error.
When the check box is not selected, the command execution result does not affect the backup
failure or success. You can track the command execution result by exploring the Activities tab.
6. Click Done.

Pre/Post data capture commands

The option enables you to define the commands to be automatically run before and after data
capture (that is, taking the data snapshot). Data capture is performed at the beginning of the backup
procedure.

The following scheme illustrates when the pre/post data capture commands are run.

<---------------------------- Backup ---------------------------->

Pre-backup Pre-data Data Post-data Write data to Post-backup

command capture capture capture the backup command
command command set

Interaction with other backup options

Running of the pre/post data capture commands can be modified by other backup options.

If the Multi-volume snapshot option is enabled, the pre/post data capture commands will run only
once, because the snapshots for all volumes are created simultaneously. If the Multi-volume

463 © Acronis International GmbH, 2003-2024

snapshot option is disabled, the pre/post data capture commands will run for every volume that is
being backed up because the snapshots are created sequentially, one volume after another.

If the Volume Shadow Copy Service (VSS) option is enabled, the pre/post data capture commands
and the Microsoft VSS actions will run as follows:

Pre-data capture commands > VSS Suspend > Data capture > VSS Resume > Post-data capture commands

By using the pre/post data capture commands, you can suspend and resume a database or
application that is not compatible with VSS. Because the data capture takes seconds, the database
or application idle time will be minimal.

Pre-data capture command

To specify a command/batch file to be executed before data capture

1. Enable the Execute a command before the data capture switch.

2. In the Command... field, type a command or browse to a batch file. The program does not
support interactive commands, i.e. commands that require user input (for example, "pause".)
3. In the Working directory field, specify a path to a directory where the command/batch file will
be executed.
4. In the Arguments field specify the command’s execution arguments, if required.
5. Depending on the result you want to obtain, select the appropriate options as described in the
table below.
6. Click Done.

Check box Selection

Fail the backup Selected Cleared Selected Cleared

if the command
execution fails*

Do not perform Selected Selected Cleared Cleared

the data
capture until
the command
execution is
complete

Result

Preset Perform the data N/A Perform the data

capture after the capture concurrently
Perform the data capture
command is with the command
only after the command is
executed despite and irrespective of
successfully executed. Fail
execution failure or the command
the backup if the
success. execution result.
command execution fails.

* A command is considered failed if its exit code is not equal to zero.

464 © Acronis International GmbH, 2003-2024

Note
If a script fails due to a conflict related to a required library version in Linux, exclude the LD_LIBRARY_
PATH and LD_PRELOAD environmental variables, by adding the following lines in your script:

#!/bin/sh
unset LD_LIBRARY_PATH
unset LD_PRELOAD

Post-data capture command

To specify a command/batch file to be executed after data capture

1. Enable the Execute a command after the data capture switch.

2. In the Command... field, type a command or browse to a batch file. The program does not
support interactive commands, i.e. commands that require user input (for example, "pause".)
3. In the Working directory field, specify a path to a directory where the command/batch file will
be executed.
4. In the Arguments field specify the command’s execution arguments, if required.
5. Depending on the result you want to obtain, select the appropriate options as described in the
table below.
6. Click Done.

Check box Selection

Fail the Selected Cleared Selected Cleared

backup if the
command
execution
fails*

Do not back Selected Selected Cleared Cleared

up until the
command
execution is
complete

Result

Preset Continue the backup N/A Continue the backup

after the command is concurrently with the
Continue the
executed despite command execution and
backup only after
command execution irrespective of the
the command is
failure or success. command execution
successfully
result.
executed.

* A command is considered failed if its exit code is not equal to zero.

465 © Acronis International GmbH, 2003-2024

Scheduling
This option defines whether backups start exactly as scheduled or with a delay, and how many
virtual machines are backed up simultaneously.

For more information about how to configure the backup schedule, see "Running a backup on a
schedule" (p. 400).

The preset is: Distribute backup start times within a time window. Maximum delay: 30
minutes.

You can select one of the following:

l Start all backups exactly as scheduled

Backups of physical machines will start exactly as scheduled. Virtual machines will be backed up
one by one.
l Distribute start times within a time window
Backups of physical machines will start with a delay from the scheduled time. The delay value for
each machine is selected randomly and ranges from zero to the maximum value you specify. You
may want to use this setting when backing up multiple machines to a network location, to avoid
excessive network load. The delay value for each machine is determined when the protection
plan is applied to the machine and remains the same until you edit the protection plan and
change the maximum delay value.
Virtual machines will be backed up one by one.
l Limit the number of simultaneously running backups by
Use this option to manage the parallel backup of virtual machines that are backed up on the
hypervisor level (agentless backup).
Protection plans in which this option is selected can run together with other protection plans that
are operated by the same agent at the same time. When you select this option, you must specify
the number of parallel backups per plan. The total number of machines that are backed up
simultaneously by all plans is limited to 10 per agent. To learn how to change the default limit,
see "Limiting the total number of simultaneously backed-up virtual machines" (p. 670).
Protection plans in which this option is not selected run the backup operations sequentially, one
virtual machine after another.

Sector-by-sector backup
The option is effective only for disk-level backup.

This option defines whether an exact copy of a disk or volume on a physical level is created.

The preset is: Disabled.

If this option is enabled, all disk or volume's sectors will be backed up, including unallocated space
and those sectors that are free of data. The resulting backup will be equal in size to the disk being

466 © Acronis International GmbH, 2003-2024

backed up (if the "Compression level" option is set to None). The software automatically switches to
the sector-by-sector mode when backing up drives with unrecognized or unsupported file systems.

Note
It will be impossible to perform a recovery of application data from the backups which were created
in the sector-by-sector mode.

Splitting
This option enables you to select the method of splitting of large backups into smaller files.

Note
Splitting is not available in protection plans that use the cloud storage as a backup location.

The preset is:

l If the backup location is a local or network (SMB) folder, and the backup format is Version 12:
Fixed size - 200 GB
This setting allows the backup software to work with large volumes of data on the NTFS file
system, without negative effects caused by file fragmentation.
l Otherwise: Automatic

The following settings are available:

l Automatic
A backup will be split if it exceeds the maximum file size supported by the file system.
l Fixed size
Enter the desired file size or select it from the drop-down list.

Task failure handling

This option determines the program behavior when a scheduled execution of a protection plan fails
or your machine restarts while a backup is running. This option is not effective when a protection
plan is started manually.

If this option is enabled, the program will try to execute the protection plan again. You can specify
the number of attempts and the time interval between the attempts. The program stops trying as
soon as an attempt completes successfully or the specified number of attempts is performed,
depending on which comes first.

If this option is enabled and your machine restarts while a backup is running, the backup operation
will not fail. A few minutes after the restart, the backup operation will continue automatically and
complete the backup file with the missing data. In this use case, the option Interval between
attempts is not relevant.

The preset is: Enabled.

467 © Acronis International GmbH, 2003-2024

Note
This option is not effective in forensic backups.

Task start conditions

This option is effective in Windows and Linux operating systems.

This option determines the program behavior in case a task is about to start (the scheduled time
comes or the event specified in the schedule occurs), but the condition (or any of multiple
conditions) is not met. For more information about conditions refer to "Start conditions" (p. 407).

The preset is: Wait until the conditions from the schedule are met.

Wait until the conditions from the schedule are met

With this setting, the scheduler starts monitoring the conditions and launches the task as soon as
the conditions are met. If the conditions are never met, the task will never start.

To handle the situation when the conditions are not met for too long and further delaying the task is
becoming risky, you can set the time interval after which the task will run irrespective of the
condition. Select the Run the task anyway after check box and specify the time interval. The task
will start as soon as the conditions are met OR the maximum time delay lapses, depending on which
comes first.

Skip the task execution

Delaying a task might be unacceptable, for example, when you need to execute a task strictly at the
specified time. Then it makes sense to skip the task rather than wait for the conditions, especially if
the tasks occur relatively often.

Volume Shadow Copy Service (VSS)

This option is applicable only to Windows operating systems.

It defines whether a backup can succeed if one or more Volume Shadow Copy Service (VSS) writers
fail and which provider has to notify the VSS-aware applications that the backup will start.

Using the Volume Shadow Copy Service ensures the consistent state of all data used by the
applications; in particular, completion of all database transactions at the moment of taking the data
snapshot by the backup software. Data consistency, in turn, ensures that the application will be
recovered in the correct state and become operational immediately after recovery.

The snapshot is used only during the backup operation, and is automatically deleted when the
backup operation completes. No temporary files are kept.

You may also use Pre/Post data capture commands to ensure that the data is backed up in a
consistent state. For instance, specify pre-data capture commands that will suspend the database

468 © Acronis International GmbH, 2003-2024

and flush all caches to ensure that all transactions are completed, and then specify post-data
capture commands that will resume the database operations after the snapshot is taken.

Note
Files and folders that are specified in the HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot registry
key are not backed up. In particular, offline Outlook Data Files (.ost) are not backed up because they
are specified in the OutlookOST value of this key.

Ignore failed VSS writers

You can select one of the following:

l Ignore failed VSS writers

With this option, you can achieve successful backups even when one or more VSS writers fail.

Important
Application-aware backups will always fail if the application-specific writer fails. For example, if
you are making application-aware backup of SQL Server data, and SqlServerWriter fails, the
backup operation will also fail.

When this option is enabled, up to three consecutive attempts for a VSS snapshot will be made.
In the first attempt, all VSS writers are required. If this attempt fails, it will be repeated. If the
second attempt also fails, the failed VSS writers will be excluded from the scope of the backup
operation, and then a third attempt will be made. If the third attempt is successful, the backup
will complete with a warning about the failed VSS writers. If the third attempt is not successful,
the backup will fail.

l Require successful processing for all VSS writers

If any of the VSS writers fails, the backup operation will also fail.

Select the snapshot provider

You can select one of the following:

l Automatically select snapshot provider

Automatically select among the hardware snapshot provider, software snapshot providers, and
Microsoft Software Shadow Copy provider.
l Use Microsoft Software Shadow Copy provider
We recommend that you choose this option when backing up application servers (Microsoft
Exchange Server, Microsoft SQL Server, Microsoft SharePoint, or Active Directory).

Enable VSS full backup

If this option is enabled, the logs of Microsoft Exchange Server and of other VSS-aware applications
(except for Microsoft SQL Server) will be truncated after each successful full, incremental or

469 © Acronis International GmbH, 2003-2024

differential disk-level backup.

The preset is: Disabled.

Leave this option disabled in the following cases:

l If you use Agent for Exchange or third-party software for backing up the Exchange Server data.
This is because the log truncation will interfere with the consecutive transaction log backups.
l If you use third-party software for backing up the SQL Server data. The reason for this is that the
third-party software will take the resulting disk-level backup for its "own" full backup. As a result,
the next differential backup of the SQL Server data will fail. The backups will continue failing until
the third-party software creates the next "own" full backup.
l If other VSS-aware applications are running on the machine and you need to keep their logs for
any reason.

Important
Enabling this option does not result in the truncation of Microsoft SQL Server logs. To truncate the
SQL Server log after a backup, enable the Log truncation backup option.

Volume Shadow Copy Service (VSS) for virtual machines

This option defines whether quiesced snapshots of virtual machines are taken.

The preset is: Enabled.

When this option is disabled, a non-quiesced snapshot is taken. The virtual machine will be backed
up in a crash-consistent state.

When this option is enabled, the transactions of all VSS-aware applications running in the virtual
machine are completed, and then a quiesced snapshot is taken.

If a quiesced snapshot cannot be taken after the number of re-attempts specified in the "Error
handling" option, and application backup is enabled, the backup fails.

If a quiesced snapshot cannot be taken after the number of re-attempts specified in the "Error
handling" option, and application backup is disabled, a crash-consistent backup is created. To make
the backup fail instead of creating a crash-consistent backup, select the Fail backup if taking a
quiesced snapshot is not possible check box.

The following table summarizes the available settings and their results.

Quiesced snapshot was taken Quiesced snapshot was not taken

successfully
Settings
Application Application Application Application
backup enabled backup disabled backup enabled backup disabled

Volume Shadow Quiesced snapshot Quiesced snapshot Backup fails. Non-quiesced

Copy Service is taken. is taken. snapshot is taken.
(VSS) for virtual Application- Application- Crash-consistent

470 © Acronis International GmbH, 2003-2024

 Quiesced snapshot was taken Quiesced snapshot was not taken
successfully
Settings
Application Application Application Application
backup enabled backup disabled backup enabled backup disabled

machines enabled consistent backup consistent backup backup is created.

is created. is created.
Fail backup if
taking a quiesced
snapshot is not
possible not
selected

Volume Shadow Quiesced snapshot Quiesced snapshot Backup fails. Backup fails.
Copy Service is taken. is taken.
(VSS) for virtual Application- Application-
machines enabled consistent backup consistent backup
Fail backup if is created. is created.
taking a quiesced
snapshot is not
possible selected

Volume Shadow Non-quiesced Non-quiesced Non-quiesced Non-quiesced

Copy Service snapshot is taken. snapshot is taken. snapshot is taken. snapshot is taken.
(VSS) for virtual Crash-consistent Crash-consistent Crash-consistent Crash-consistent
machines disabled backup is created. backup is created. backup is created. backup is created.

Enabling Volume Shadow Copy Service (VSS) for virtual machines also triggers the pre‐freeze
and post‐thaw scripts that you might have on the backed-up virtual machine. For more information
on these scripts, refer to "Running pre‐freeze and post‐thaw scripts automatically" (p. 663).

To take a quiesced snapshot, the backup software applies VSS inside a virtual machine by using
VMware Tools, Hyper-V Integration Services, Virtuozzo Guest Tools, Red Hat Virtualization Guest
Tools, or QEMU Guest Tools, respectively.

Note
For Red Hat Virtualization (oVirt) virtual machines, we recommend that you install QEMU Guest
Tools instead of Red Hat Virtualization Guest Tools. Some versions of Red Hat Virtualization Guest
Tools do not support application-consistent snapshots.

This option does not affect Scale Computing HC3 virtual machines. For them, quiescing depends on
whether Scale Tools are installed on the virtual machine.

Weekly backup
This option determines which backups are considered "weekly" in retention rules and backup
schemes. A "weekly" backup is the first backup created after a week starts.

471 © Acronis International GmbH, 2003-2024

The preset is: Monday.

Windows event log

This option is effective only in Windows operating systems.

This option defines whether the agents have to log events of the backup operations in the
Application Event Log of Windows (to see this log, run eventvwr.exe or select Control Panel >
Administrative tools > Event Viewer). You can filter the events to be logged.

The preset is: Disabled.

Recovery

Recovery cheat sheet

The following table summarizes the available recovery methods. Use the table to choose a recovery
method that best fits your need.

Note
You cannot recover backups in the Cyber Protect console for tenants in the Compliance mode. For
more information on how to recover such backups, refer to "Recovering backups for tenants in the
Compliance mode" (p. 1032).

What to recover Recovery method

Physical machine Using the Cyber Protect console

(Windows or Linux) Using bootable media

Physical machine
Using bootable media
(Mac)

Virtual machine Using the Cyber Protect console

(VMware, Hyper-V, Red Hat Virtualization (oVirt),
or Scale Computing HC3) Using bootable media

Virtual machine or container

(Virtuozzo, Virtuozzo Hybrid Server, or Virtuozzo Using the Cyber Protect console
Hybrid Infrastructure)

ESXi configuration Using bootable media

Using the Cyber Protect console

Files/Folders Downloading files from the cloud storage

Using bootable media

472 © Acronis International GmbH, 2003-2024

 Extracting files from local backups

System state Using the Cyber Protect console

SQL databases Using the Cyber Protect console

Exchange databases Using the Cyber Protect console

Exchange mailboxes Using the Cyber Protect console

Websites Using the Cyber Protect console

Microsoft 365

Mailboxes
Using the Cyber Protect console
(local Agent for Microsoft 365)

Mailboxes
Using the Cyber Protect console
(cloud Agent for Microsoft 365)

Public folders Using the Cyber Protect console

OneDrive files Using the Cyber Protect console

SharePoint Online data Using the Cyber Protect console

Google Workspace

Mailboxes Using the Cyber Protect console

Google Drive files Using the Cyber Protect console

Shared drive files Using the Cyber Protect console

Cross-platform recovery
Cross-platform recovery is available for backups of entire machines and backups of disks that
contain an operating system.

A cross-platform recovery is performed in the following cases:

l A backup is created by one type of agent but it is recovered by another type of agent.
l An agent-based backup is recovered on the hypervisor level (agentless recovery), or an agentless
backup is recovered by an agent (agent-based recovery).
l A backup is recovered to dissimilar hardware (including virtual hardware).

473 © Acronis International GmbH, 2003-2024

Note
Some peripheral devices, such as printers, might not be recovered correctly when you perform a
cross-platform recovery.

The table bellow shows a few examples of cross-platform recovery.

Cross-platform recovery

Agentless backup Agent-based recovery

Agent-based backup Agentless recovery

Backup by Agent for Windows Recovery by Agent for VMware

Backup by Agent for VMware Recovery by Agent for Hyper-V

Backup by Agent for Windows that is installed on a Recovery by Agent for VMware (agentless) on the
VMware ESXi virtual machine (agent-based) same VMware ESXi host

Backup by Agent for Windows Recovery by Agent for Windows that is installed on
a machine with dissimilar hardware

Backup of a physical machine Recovery as a virtual machine

Note for Mac users

l Starting with 10.11 El Capitan, certain system files, folders, and processes are flagged for
protection with an extended file attribute com.apple.rootless. This feature is called System
Integrity Protection (SIP). The protected files include preinstalled applications and most of the
folders in /system, /bin, /sbin, /usr.
The protected files and folders cannot be overwritten during a recovery under the operating
system. If you need to overwrite the protected files, perform the recovery under bootable media.
l Starting with macOS Sierra 10.12, rarely used files can be moved to iCloud by the Store in Cloud
feature. Small footprints of these files are kept on the file system. These footprints are backed up
instead of the original files.
When you recover a footprint to the original location, it is synchronized with iCloud and the
original file becomes available. When you recover a footprint to a different location, it cannot be
synchronized and the original file will be unavailable.

Safe recovery
Use safe recovery with Entire machine or Disks/volumes backups of Windows workloads to
ensure that you recover only malware-free data, even if the backup contains infected files.

During a safe recovery operation, the backup is automatically scanned for malware. Then, the
protection agent recovers the backup on the target workload and deletes any infected files. As a
result, a malware-free backup is recovered.

Additionally, one of the following statuses is assigned to the backup:

474 © Acronis International GmbH, 2003-2024

l Malware detected
l No malware
l Not scanned

You can use the status to filter the backup archives.

Limitations
l Safe recovery is supported for physical and virtual Windows machines on which a protection
agent is installed.
l Safe recovery is supported for Entire machine and Disks/volumes backups.
l Only NTFS volumes are scanned for malware. Non-NTFS volumes are recovered without
antimalware scanning.
l Safe recovery is not supported for the Continuous data protection (CDP) backup in the archive. To
recover the data from the CDP backup, run an additional Files/folders recovery operation. For
more operation about the CDP backups, see "Continuous data protection (CDP)" (p. 389).

Recovering a machine

Recovering physical machines

This section describes recovery of physical machines by using the web interface.

Use bootable media instead of the web interface if you need to recover:

l A machine running macOS

l A machine from a tenant in the Compliance mode
l Any operating system to bare metal or to an offline machine
l The structure of logical volumes (volumes created by Logical Volume Manager in Linux). The
media enables you to recreate the logical volume structure automatically.

Note
You cannot recover disk-level backups of Intel-based Macs to Macs that use Apple silicon
processors, and vice-versa. You can recover files and folders.

475 © Acronis International GmbH, 2003-2024

Recovery with restart
Recovery of an operating system and recovery of volumes that are encrypted with BitLocker
requires a restart. You can choose whether to restart the machine automatically or assign it the
Interaction required status. The recovered operating system goes online automatically.

Important
Backed-up encrypted volumes are recovered as non-encrypted.

Recovery of BitLocker-encrypted volumes requires that there is a non-encrypted volume on the

same machine, and that this volume has at least 1 GB of free space. If either condition is not met,
the recovery fails.

Recovering an encrypted system volume does not require any additional actions. To recover an
encrypted non-system volume, you must lock it first, for example, by opening a file that resides on
this volume. Otherwise, the recovery will continue without restart and the recovered volume might
not be recognized by Windows.

Note
If the recovery fails and your machine restarts with the Cannot get file from partition error, try
disabling Secure Boot. For more information on how to do it, refer to Disabling Secure Boot in the
Microsoft documentation.

To recover a physical machine

1. Select the backed-up machine.

2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Do any of the following:
l If the backup location is cloud or shared storage (i.e. other agents can access it), click Select
machine, select a target machine that is online, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
l Recover the machine as described in "Recovering disks by using bootable media".
4. Click Recover > Entire machine.
The software automatically maps the disks from the backup to the disks of the target machine.
To recover to another physical machine, click Target machine, and then select a target machine
that is online.

476 © Acronis International GmbH, 2003-2024

5. If you are unsatisfied with the mapping result or if the disk mapping fails, click Volume mapping
to re-map the disks manually.
The mapping section also enables you to choose individual disks or volumes for recovery. You
can switch between recovering disks and volumes by using the Switch to... link in the upper-
right corner.

477 © Acronis International GmbH, 2003-2024

6. [Only available for Windows machines on which a protection agent is installed] Enable the Safe
recovery switch to ensure that the recovered data is malware-free. For more information about
how safe recovery works, see "Safe recovery" (p. 474).
7. Click Start recovery.
8. Confirm that you want to overwrite the disks with their backed-up versions. Choose whether to
restart the machine automatically.
The recovery progress is shown on the Activities tab.

Physical machine to virtual

You can recover a physical machine to a virtual machine on one of the supported hypervisors. This
is also a mechanism to migrate a physical machine to a virtual machine. For more information about
supported P2V migration paths, refer to "Machine migration".

This section describes the recovery of a physical machine as a virtual machine by using the web
interface. This operation can be performed if at least one agent for the relevant hypervisor is
installed and registered in Acronis Management Server. For example, recovery to VMware ESXi
requires at least one Agent for VMware, recovery to Hyper-V requires at least one Agent for Hyper-V
installed and registered in the environment.

Recovery through the web interface is not available for tenants in the Compliance mode.

Note
You cannot recover macOS virtual machines to Hyper-V hosts, because Hyper-V does not support
macOS. You can recover macOS virtual machines to a VMware host that is installed on Mac
hardware.

Also, you cannot recover backups of macOS physical machines as virtual machines.

To recover a physical machine as a virtual machine

1. Select the backed-up machine.

2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Do any of the following:
l If the backup location is cloud or shared storage (i.e. other agents can access it), click Select
machine, select a machine that is online, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
l Recover the machine as described in "Recovering disks by using bootable media".
4. Click Recover > Entire machine.
5. In Recover to, select Virtual machine.
6. Click Target machine.

478 © Acronis International GmbH, 2003-2024

 a. Select the hypervisor.

Note
At least one agent for that hypervisor must be installed and registered in Acronis
Management Server.

b. Select whether to recover to a new or existing machine. The new machine option is
preferable as it does not require the disk configuration of the target machine to exactly
match the disk configuration in the backup.
c. Select the host and specify the new machine name, or select an existing target machine.
d. Click OK.
7. [For Virtuozzo Hybrid Infrastructure] Click VM settings to select Flavor. Optionally, you can
change the memory size, the number of processors, and the network connections of the virtual
machine.

Note
Selecting flavor is a required step for Virtuozzo Hybrid Infrastructure.

8. [Optional] Configure additional recovery options:

l [Not available for Virtuozzo Hybrid Infrastructure] Click Datastore for ESXi or Path for Hyper-
V, and then select the datastore (storage) for the virtual machine.
l Click Disk mapping to select the datastore (storage), interface, and provisioning mode for
each virtual disk. The mapping section also enables you to choose individual disks for
recovery.
For Virtuozzo Hybrid Infrastructure, you can only select the storage policy for the target disks.
To do so, select the desired target disk, and then click Change. In the blade that opens, click
the gear icon, select the storage policy, and then click Done.
l [For VMware ESXi, Hyper-V, and Red Hat Virtualization/oVirt] Click VM settings to change the
memory size, the number of processors, and the network connections of the virtual machine.

479 © Acronis International GmbH, 2003-2024

 9. [Only available for Windows machines on which a protection agent is installed] Enable the Safe
recovery switch to ensure that the recovered data is malware-free. For more information about
how safe recovery works, see "Safe recovery" (p. 474).
10. Click Start recovery.
11. When recovering to an existing virtual machine, confirm that you want to overwrite the disks.

The recovery progress is shown on the Activities tab.

Recovering a virtual machine

You can recover virtual machines from their backups.

Note
You cannot recover backups in the Cyber Protect console for tenants in the Compliance mode. For
more information on how to recover such backups, refer to "Recovering backups for tenants in the
Compliance mode" (p. 1032).

Prerequisites

l A virtual machine must be stopped during the recovery to this machine. By default, the software
stops the machine without a prompt. When the recovery is completed, you have to start the

480 © Acronis International GmbH, 2003-2024

 machine manually. You can change the default behavior by using the VM power management
recovery option (click Recovery options > VM power management).

Procedure

1. Do one of the following:

l Select a backed-up machine, click Recovery, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
2. Click Recover > Entire machine.
3. If you want to recover to a physical machine, select Physical machine in Recover to. Otherwise,
skip this step.
Recovery to a physical machine is possible only if the disk configuration of the target machine
exactly matches the disk configuration in the backup.
If this is the case, continue to step 4 in "Physical machine". Otherwise, we recommend that you
perform the V2P migration by using bootable media.
4. [Optional] By default, the software automatically selects the original machine as the target
machine. To recover to another virtual machine, click Target machine, and then do the
following:
a. Select the hypervisor (VMware ESXi, Hyper-V, Virtuozzo, Virtuozzo Hybrid Infrastructure,
Scale Computing HC3, or oVirt).
Only Virtuozzo virtual machines can be recovered to Virtuozzo. For more information about
V2V migration, refer to "Machine migration".
b. Select whether to recover to a new or existing machine.
c. Select the host and specify the new machine name, or select an existing target machine.
d. Click OK.
5. Setup up the additional recovery options that you need.
l [Optional] [Not available for Virtuozzo Hybrid Infrastructure and Scale Computing HC3] To
select the datastore for the virtual machine, click Datastore for ESXi, Path for Hyper-V and
Virtuozzo, or Storage domain for Red Hat Virtualization (oVirt), and then select the datastore
(storage) for the virtual machine.
l [Optional] To view the datastore (storage), interface, and the provisioning mode for each
virtual disk, click Disk mapping. You can change these settings, unless you are recovering a
Virtuozzo container or Virtuozzo Hybrid Infrastructure virtual machine.
For Virtuozzo Hybrid Infrastructure, you can only select the storage policy for the target disks.
To do so, select the desired target disk, and then click Change. In the blade that opens, click
the gear icon, select the storage policy, and then click Done.
The mapping section also enables you to choose individual disks for recovery.
l [Optional] [Available for VMware ESXi, Hyper-V, and Virtuozzo] To change the memory size, the
number of processors, and the network connections of the virtual machine, click VM settings.
l [For Virtuozzo Hybrid Infrastructure] To change the memory size and the number of
processors of the virtual machine, select Flavor.

481 © Acronis International GmbH, 2003-2024

6. [Only available for Windows machines on which a protection agent is installed] Enable the Safe
recovery switch to ensure that the recovered data is malware-free. For more information about
how safe recovery works, see "Safe recovery" (p. 474).
7. Click Start recovery.
8. When recovering to an existing virtual machine, confirm that you want to overwrite the disks.
The recovery progress is shown on the Activities tab.

Recovering disks by using bootable media

For information about how to create bootable media, refer to "Creating physical bootable media" (p.
677).

Note
You cannot recover disk-level backups of Intel-based Macs to Macs that use Apple silicon
processors, and vice-versa. You can recover files and folders.

To recover disks by using bootable media

1. Boot the target machine by using bootable media.

2. [Only when recovering a Mac] If you are recovering APFS-formatted disks/volumes to a non-
original machine or to bare metal, re-create the original disk configuration manually:

482 © Acronis International GmbH, 2003-2024

 a. Click Disk Utility.
b. Erase and format the target disk into APFS. For instructions, refer to
https://support.apple.com/en-us/HT208496#erasedisk.
c. Re-create the original disk configuration. For instructions, refer to
https://support.apple.com/guide/disk-utility/add-erase-or-delete-apfs-volumes-
dskua9e6a110/19.0/mac/10.15.
d. Click Disk Utility > Quit Disk Utility.
3. Click Manage this machine locally or click Rescue Bootable Media twice, depending on the
media type you are using.
4. If a proxy server is enabled in your network, click Tools > Proxy server, and then specify the
proxy server host name/IP address, port, and credentials. Otherwise, skip this step.
5. [Optional] When recovering Windows or Linux, click Tools > Register media in the Cyber
Protection service, and then specify the registration token that you obtained when
downloading the media. If you do this, you will not need to enter credentials or a registration
code to access the cloud storage, as described in step 8.
6. On the welcome screen, click Recover.
7. Click Select data, and then click Browse.

8. Specify the backup location:

l To recover from cloud storage, select Cloud storage. Enter the credentials of the account to
which the backed up machine is assigned.
When recovering Windows or Linux, you have the option to request a registration code and
use it instead of the credentials. Click Use registration code > Request the code. The
software shows the registration link and the registration code. You can copy them and
perform the registration steps on a different machine. The registration code is valid for one
hour.
l To recover from a local or a network folder, browse to the folder under Local folders or
Network folders.
l To recover from backup locations on public cloud storage such as Microsoft Azure, Amazon
S3, Wasabi or S3 compatible, first click Register media in the Cyber Protection service, and
then configure recovery using the web interface. For more information about managing
media remotely via the web interface, see "Remote operations with bootable media" (p. 693).
Click OK to confirm your selection.
9. Select the backup from which you want to recover the data. If prompted, type the password for
the backup.

10. In Backup contents, select the disks that you want to recover. Click OK to confirm your
selection.
11. Under Where to recover, the software automatically maps the selected disks to the target disks.
If the mapping is not successful or if you are unsatisfied with the mapping result, you can re-map
disks manually.

483 © Acronis International GmbH, 2003-2024

 Note
Changing disk layout may affect the operating system bootability. Please use the original
machine's disk layout unless you feel fully confident of success.

12. [When recovering Linux] If the backed-up machine had logical volumes (LVM) and you want to
reproduce the original LVM structure:
a. Ensure that the number of the target machine disks and each disk capacity are equal to or
exceed those of the original machine, and then click Apply RAID/LVM.
b. Review the volume structure, and then click Apply RAID/LVM to create it.
13. [Optional] Click Recovery options to specify additional settings.
14. Click OK to start the recovery.

Using Universal Restore

The most recent operating systems remain bootable when recovered to dissimilar hardware,
including the VMware or Hyper-V platforms. If a recovered operating system does not boot, use the
Universal Restore tool to update the drivers and modules that are critical for the operating system
startup.

Universal Restore is applicable to Windows and Linux.

To apply Universal Restore

1. Boot the machine from the bootable media.

2. Click Apply Universal Restore.
3. If there are multiple operating systems on the machine, choose the one to apply Universal
Restore to.
4. [For Windows only] Configure the additional settings.
5. Click OK.

Universal Restore in Windows

Preparation

Prepare drivers
Before applying Universal Restore to a Windows operating system, make sure that you have the
drivers for the new HDD controller and the chipset. These drivers are critical to start the operating
system. Use the CD or DVD supplied by the hardware vendor or download the drivers from the
vendor’s website. The driver files should have the *.inf extension. If you download the drivers in the
*.exe, *.cab or *.zip format, extract them using a third-party application.

The best practice is to store drivers for all the hardware used in your organization in a single
repository sorted by device type or by the hardware configurations. You can keep a copy of the
repository on a DVD or a flash drive; pick some drivers and add them to the bootable media; create

484 © Acronis International GmbH, 2003-2024

the custom bootable media with the necessary drivers (and the necessary network configuration)
for each of your servers. Or, you can simply specify the path to the repository every time Universal
Restore is used.

Check access to the drivers in bootable environment

Make sure you have access to the device with drivers when working under bootable media. Use
WinPE-based media if the device is available in Windows but Linux-based media does not detect it.

Universal Restore settings

Automatic driver search

Specify where the program will search for the Hardware Abstraction Layer (HAL), HDD controller
driver and network adapter driver(s):

l If the drivers are on a vendor's disc or other removable media, turn on the Search removable
media.
l If the drivers are located in a networked folder or on the bootable media, specify the path to the
folder by clicking Add folder.

In addition, Universal Restore will search the Windows default driver storage folder. Its location is
determined in the registry value DevicePath, which can be found in the registry key HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion. This storage folder is usually
WINDOWS/inf.

Universal Restore will perform the recursive search in all the sub-folders of the specified folder, find
the most suitable HAL and HDD controller drivers of all those available, and install them into the
system. Universal Restore also searches for the network adapter driver; the path to the found driver
is then transmitted by Universal Restore to the operating system. If the hardware has multiple
network interface cards, Universal Restore will try to configure all the cards' drivers.

Mass storage drivers to install anyway

You need this setting if:

l The hardware has a specific mass storage controller such as RAID (especially NVIDIA RAID) or a
fibre channel adapter.
l You migrated a system to a virtual machine that uses a SCSI hard drive controller. Use SCSI
drivers bundled with your virtualization software or download the latest drivers versions from the
software manufacturer website.
l If the automatic drivers search does not help to boot the system.

Specify the appropriate drivers by clicking Add driver. The drivers defined here will be installed,
with appropriate warnings, even if the program finds a better driver.

485 © Acronis International GmbH, 2003-2024

Universal Restore process
After you have specified the required settings, click OK.

If Universal Restore cannot find a compatible driver in the specified locations, it will display a
prompt about the problem device. Do one of the following:

l Add the driver to any of the previously specified locations and click Retry.
l If you do not remember the location, click Ignore to continue the process. If the result is not
satisfactory, reapply Universal Restore. When configuring the operation, specify the necessary
driver.

Once Windows boots, it will initialize the standard procedure for installing new hardware. The
network adapter driver will be installed silently if the driver has the Microsoft Windows signature.
Otherwise, Windows will ask for confirmation on whether to install the unsigned driver.

After that, you will be able to configure the network connection and specify drivers for the video
adapter, USB and other devices.

Universal Restore in Linux

Universal Restore can be applied to Linux operating systems with a kernel version of 2.6.8 or later.

When Universal Restore is applied to a Linux operating system, it updates a temporary file system
known as the initial RAM disk (initrd). This ensures that the operating system can boot on the new
hardware.

Universal Restore adds modules for the new hardware (including device drivers) to the initial RAM
disk. As a rule, it finds the necessary modules in the /lib/modules directory. If Universal Restore
cannot find a module it needs, it records the module’s file name into the log.

Universal Restore may modify the configuration of the GRUB boot loader. This may be required, for
example, to ensure the system bootability when the new machine has a different volume layout
than the original machine.

Universal Restore never modifies the Linux kernel.

Reverting to the original initial RAM disk

You can revert to the original initial RAM disk if necessary.

The initial RAM disk is stored on the machine in a file. Before updating the initial RAM disk for the
first time, Universal Restore saves a copy of it to the same directory. The name of the copy is the
name of the file, followed by the _acronis_backup.img suffix. This copy will not be overwritten if
you run Universal Restore more than once (for example, after you have added missing drivers).

To revert to the original initial RAM disk, do any of the following:

486 © Acronis International GmbH, 2003-2024

l Rename the copy accordingly. For example, run a command similar to the following:

mv initrd-2.6.16.60-0.21-default_acronis_backup.img initrd-2.6.16.60-0.21-default

l Specify the copy in the initrd line of the GRUB boot loader configuration.

Recovering files

Recovering files in the Cyber Protect console

Note
You cannot recover backups in the Cyber Protect console for tenants in the Compliance mode. For
more information on how to recover such backups, refer to "Recovering backups for tenants in the
Compliance mode" (p. 1032).

1. Select the machine that originally contained the data that you want to recover.
2. Click Recovery.
3. Select the recovery point. Note that recovery points are filtered by location.
If the selected machine is physical and it is offline, recovery points are not displayed. Do any of
the following:
l [Recommended] If the backup location is cloud or shared storage (i.e. other agents can access
it), click Select machine, select a target machine that is online, and then select a recovery
point.
l Select a recovery point on the Backup storage tab.
l Download the files from the cloud storage.
l Use bootable media.
4. Click Recover > Files/folders.
5. Browse to the required folder or use the search bar to obtain the list of the required files and
folders.
Search is language-independent.
You can use one or more wildcard characters (* and ?). For more details about using wildcards,
refer to "Mask " (p. 440).

Note
Search is not available for disk-level backups that are stored in the cloud storage.

6. Select the files that you want to recover.

7. If you want to save the files as a .zip file, click Download, select the location to save the data to,
and click Save. Otherwise, skip this step.
Downloading is not available if your selection contains folders or the total size of the selected
files exceeds 100 MB. To retrieve larger amounts of data from the cloud, use the procedure
"Downloading files from the cloud storage" (p. 488).
8. Click Recover.

487 © Acronis International GmbH, 2003-2024

 In Recover to, click to select the target for the recovery operation, or leave the default target.
The default target varies according to the source of the backup.
The following targets are available:
l The source machine (if a protection agent is installed on it).
This is the machine that originally contained the files that you want to recover.
l Other machines on which a protection agent is installed – physical machines, virtual machines,
and virtualization hosts on which a protection agent is installed, or virtual appliances.
You can recover files to physical machines, virtual machines, and virtualization hosts on which
a protection agent is installed. You cannot recover files to virtual machines on which a
protection agent is not installed (except for Virtuozzo virtual machines).
l Virtuozzo containters or virtual machines.
You can recover files to Virtuozzo containers and virtual machines with some limitations. For
more information about them, refer to "Limitations for recovering files in the Cyber Protect
console" (p. 492).
9. In Path, select the recovery destination. You can select one of the following:
l [When recovering to the original machine] The original location.
l A local folder or locally attached storage on the target machine.

Note
Symbolic links are not supported.

l A network folder that is accessible from the target machine.

10. Click Start recovery.
11. Select one of the file overwriting options:
l Overwrite existing files
l Overwrite an existing file if it is older
l Do not overwrite existing files
The recovery progress is shown on the Activities tab.

Downloading files from the cloud storage

In the Web Restore console, you can browse the cloud storage, view the contents of the backups,
and download backed-up files and folders.

Note
You can access the Web Restore console only if you are a customer Cyber Protection administrator
or a customer tenant user. The partner level user roles are not allowed.

Limitations
l You cannot download backed-up disks, volumes, or whole recovery points.
l When you browse disk-level backups, logical volumes (such as LVM and LDM) are not shown.
l You cannot browse backups of system state, SQL databases, and Exchange databases.

488 © Acronis International GmbH, 2003-2024

To download files and folders from the cloud storage

1. In the Cyber Protection console, select the required workload, and then click Recovery.
2. [If multiple backup locations are available] Select the backup location, and then click More ways
to recover.
3. Click Download files.
4. Under Machines, click the workload name, and then click the backup archive.
A backup archive contains one or more backups (recovery points).
5. Click the backup number (recovery point) from which you want to download files or folders, and
then navigate to the required items.
6. Select the check boxes next to the items that you want to download.

Note
If you select multiple items, they will be downloaded as a ZIP file.

7. Click Download.

Verifying file authenticity with Notary Service

If notarization was enabled during backup, you can verify the authenticity of a backed-up file.

To verify the file authenticity

1. Select the file as described in steps 1-6 of the "Recovering files by using the web interface"
section, or steps 1-5 of the "Downloading files from the cloud storage" section.

2. Ensure that the selected file is marked with the following icon: . This means that the file is
notarized.
3. Do one of the following:
l Click Verify.
The software checks the file authenticity and displays the result.
l Click Get certificate.
A certificate that confirms the file notarization is opened in a web browser window. The
window also contains instructions that allow you to verify the file authenticity manually.

489 © Acronis International GmbH, 2003-2024

Signing a file with ASign

Note
This feature is available with the Advanced Backup pack.

ASign is a service that allows multiple people to sign a backed-up file electronically. This feature is
available only for file-level backups stored in the cloud storage.

Only one file version can be signed at a time. If the file was backed up multiple times, you must
choose the version to sign, and only this version will be signed.

For example, ASign can be used for electronic signing of the following files:

l Rental or lease agreements

l Sales contracts
l Asset purchase agreements
l Loan agreements
l Permission slips
l Financial documents
l Insurance documents
l Liability waivers
l Healthcare documents
l Research papers
l Certificates of product authenticity
l Nondisclosure agreements
l Offer letters
l Confidentiality agreements
l Independent contractor agreements

To sign a file version

1. Select the file as described in steps 1-6 of the "Recovering files by using the web interface"
section, or steps 1-5 of the "Downloading files from the cloud storage" section.
2. Ensure that the correct date and time is selected on the left panel.
3. Click Sign this file version.
4. Specify the password for the cloud storage account under which the backup is stored. The login
of the account is displayed in the prompt window.
The ASign service interface is opened in a web browser window.
5. Add other signees by specifying their email addresses. It is not possible to add or remove signees
after sending invitations, so ensure that the list includes everyone whose signature is required.
6. Click Invite to sign to send invitations to the signees.
Each signee receives an email message with the signature request. When all the requested
signees sign the file, it is notarized and signed through the notary service.

490 © Acronis International GmbH, 2003-2024

 You will receive notifications when each signee signs the file and when the entire process is
complete. You can access the ASign web page by clicking View details in any of the email
messages that you receive.
7. Once the process is complete, go to the ASign web page and click Get document to download a
.pdf document that contains:
l The Signature Certificate page with the collected signatures.
l The Audit Trail page with history of activities: when the invitation was sent to the signees,
when each signee signed the file, and so on.

Recovering files by using bootable media

For information about how to create bootable media, refer to "Creating bootable media".

To recover files by using bootable media

1. Boot the target machine by using the bootable media.

2. Click Manage this machine locally or click Rescue Bootable Media twice, depending on the
media type you are using.
3. If a proxy server is enabled in your network, click Tools > Proxy server, and then specify the
proxy server host name/IP address, port, and credentials. Otherwise, skip this step.
4. [Optional] When recovering Windows or Linux, click Tools > Register media in the Cyber
Protection service, and then specify the registration token that you obtained when
downloading the media. If you do this, you will not need to enter credentials or a registration
code to access the cloud storage, as described in step 7.
5. On the welcome screen, click Recover.
6. Click Select data, and then click Browse.

7. Specify the backup location:

l To recover from cloud storage, select Cloud storage. Enter the credentials of the account to
which the backed up machine is assigned.
When recovering Windows or Linux, you have the option to request a registration code and
use it instead of the credentials. Click Use registration code > Request the code. The
software shows the registration link and the registration code. You can copy them and
perform the registration steps on a different machine. The registration code is valid for one
hour.
l To recover from a local or a network folder, browse to the folder under Local folders or
Network folders.
l To recover from backup locations on public cloud storage such as Microsoft Azure, Amazon
S3, Wasabi or S3 compatible, first click Register media in the Cyber Protection service, and
then configure recovery using the web interface. For more information about managing
media remotely via the web interface, see "Remote operations with bootable media" (p. 693).
Click OK to confirm your selection.
8. Select the backup from which you want to recover the data. If prompted, type the password for
the backup.

491 © Acronis International GmbH, 2003-2024

 9. In Backup contents, select Folders/files.
10. Select the data that you want to recover. Click OK to confirm your selection.
11. Under Where to recover, specify a folder. Optionally, you can prohibit overwriting of newer
versions of files or exclude some files from recovery.
12. [Optional] Click Recovery options to specify additional settings.
13. Click OK to start the recovery.

Extracting files from local backups

You can browse the contents of backups and extract files that you need.

Requirements
l This functionality is available only in Windows by using File Explorer.
l The backed-up file system must be one of the following: FAT16, FAT32, NTFS, ReFS, Ext2, Ext3,
Ext4, XFS, or HFS+.

Prerequisites
l A protection agent must be installed on the machine from which you browse a backup.
l The backup must be stored in a local folder or on a network share (SMB/CIFS).

To extract files from a backup

1. Browse to the backup location by using File Explorer.

2. Double-click the backup file. The file names are based on the following template:
<machine name> - <protection plan GUID>
3. If the backup is encrypted, enter the encryption password. Otherwise, skip this step.
File Explorer displays the recovery points.
4. Double-click the recovery point.
File Explorer displays the backed-up data.
5. Browse to the required folder.
6. Copy the required files to any folder on the file system.

Limitations for recovering files in the Cyber Protect console

Tenants in the Compliance mode

You cannot recover backups in the Cyber Protect console for tenants in the Compliance mode. For
more information on how to recover such backups, refer to "Recovering backups for tenants in the
Compliance mode" (p. 1032).

492 © Acronis International GmbH, 2003-2024

Recovery to Virtuozzo containters or Virtuozzo virtual machines
l QEMU Guest Agent must be installed on the target virtual machine.
l [Only applicable when recovering to conatiners] Mount points inside containers cannot be used
as target for recovery. For example, you cannot recover files to a second hard disk or an NFS
share mounted to a container.
l When recovering files to a Windows virtual machine, and if the "File-level security" (p. 498)
recovery option is enabled, the archive bit attribute is set to the recovered files.
l Files with non-ANSI characters in their names are recovered with incorrect names on machines
running Windows Server 2012 or older and machines running Windows 7 or older.
l To recover files to CentOS or Red Hat Enterprise Linux virtual machines that run on Virtuozzo
Hybrid Server, you must edit the qemu-ga file, as follows:
o On the target virtual machine, navigate to /etc/sysconfig/, and then open the qemu-ga file for
editing.
o Navigate to the following line, and then delete everything after the equals sign (=):

BLACKLIST_RPC=

o Restart QEMU Guest Agent by running the following command:

systemctl restart qemu-guest-agent

Recovering system state

Note
You cannot recover backups in the Cyber Protect console for tenants in the Compliance mode. For
more information on how to recover such backups, refer to "Recovering backups for tenants in the
Compliance mode" (p. 1032).

1. Select the machine for which you want to recover the system state.
2. Click Recovery.
3. Select a system state recovery point. Note that recovery points are filtered by location.
4. Click Recover system state.
5. Confirm that you want to overwrite the system state with its backed-up version.
The recovery progress is shown on the Activities tab.

Recovering ESXi configuration

To recover an ESXi configuration, you need Linux-based bootable media. For information about how
to create bootable media, refer to "Creating physical bootable media" (p. 677).

If you are recovering an ESXi configuration to a non-original host and the original ESXi host is still
connected to the vCenter Server, disconnect and remove this host from the vCenter Server to avoid

493 © Acronis International GmbH, 2003-2024

 unexpected issues during the recovery. If you want to keep the original host along with the
recovered one, you can add it again after the recovery is complete.

The virtual machines running on the host are not included in an ESXi configuration backup. They can
be backed up and recovered separately.

To recover an ESXi configuration

1. Boot the target machine by using the bootable media.

2. Click Manage this machine locally.
3. On the welcome screen, click Recover.
4. Click Select data, and then click Browse.
5. Specify the backup location:
l Browse to the folder under Local folders or Network folders.
Click OK to confirm your selection.
6. In Show, select ESXi configurations.
7. Select the backup from which you want to recover the data. If prompted, type the password for
the backup.
8. Click OK.
9. In Disks to be used for new datastores, do the following:
l Under Recover ESXi to, select the disk where the host configuration will be recovered. If you
are recovering the configuration to the original host, the original disk is selected by default.
l [Optional] Under Use for new datastore, select the disks where new datastores will be
created. Be careful because all data on the selected disks will be lost. If you want to preserve
the virtual machines in the existing datastores, do not select any disks.
10. If any disks for new datastores are selected, select the datastore creation method in How to
create new datastores: Create one datastore per disk or Create one datastore on all
selected HDDs.
11. [Optional] In Network mapping, change the result of automatic mapping of the virtual switches
present in the backup to the physical network adapters.
12. [Optional] Click Recovery options to specify additional settings.
13. Click OK to start the recovery.

Recovery options
To modify the recovery options, click Recovery options when configuring recovery.

Availability of the recovery options

The set of available recovery options depends on:

l The environment the agent that performs recovery operates in (Windows, Linux, macOS, or
bootable media).
l The type of data being recovered (disks, files, virtual machines, application data).

The following table summarizes the availability of the recovery options.

494 © Acronis International GmbH, 2003-2024

 Disks Files Virtual SQL and
machine Exchang
s e

Window Linux Bootabl Window Linux macO Bootabl ESXi, Window

s e media s S e media Hyper-V, s
and
Virtuozz
o

Backup + + + + + + + + +
validation

Boot mode + - - - - - - + -

Date and - - - + + + + - -
time for
files

Error + + + + + + + + +
handling

File - - - + + + + - -
exclusions

File-level - - - + - - - - -
security

Flashback + + + - - - - + -

Full path - - - + + + + - -
recovery

Mount - - - + - - - - -
points

Performan + + - + + + - + +
ce

Pre/post + + - + + + - + +
commands

SID + - - - - - - - -
changing

VM power - - - - - - - + -
manageme
nt

Windows + - - + - - - Hyper-V +
event log only

495 © Acronis International GmbH, 2003-2024

Backup validation
This option defines whether to validate a backup to ensure that the backup is not corrupted, before
data is recovered from it. This operation is performed by the protection agent.

The preset is: Disabled.

For more information about the validation via checksum verification, refer to "Checksum
verification" (p. 197).

Note
Depending on the settings chosen by your service provider, validation might not be available when
backing up to the cloud storage.

Boot mode
This option is effective when recovering a physical or a virtual machine from a disk-level backup that
contains a Windows operating system.

This option enables you to select the boot mode (BIOS or UEFI) that Windows will use after the
recovery. If the boot mode of the original machine is different from the selected boot mode, the
software will:

l Initialize the disk to which you are recovering the system volume, according to the selected boot
mode (MBR for BIOS, GPT for UEFI).
l Adjust the Windows operating system so that it can start using the selected boot mode.

The preset is: As on the target machine.

You can choose one of the following:

l As on the target machine

The agent that is running on the target machine detects the boot mode currently used by
Windows and makes the adjustments according to the detected boot mode.
This is the safest value that automatically results in bootable system unless the limitations listed
below apply. Since the Boot mode option is absent under bootable media, the agent on media
always behaves as if this value is chosen.
l As on the backed-up machine
The agent that is running on the target machine reads the boot mode from the backup and
makes the adjustments according to this boot mode. This helps you recover a system on a
different machine, even if this machine uses another boot mode, and then replace the disk in the
backed-up machine.
l BIOS
The agent that is running on the target machine makes the adjustments to use BIOS.
l UEFI
The agent that is running on the target machine makes the adjustments to use UEFI.

496 © Acronis International GmbH, 2003-2024

Once a setting is changed, the disk mapping procedure will be repeated. This will take some time.

Recommendations
If you need to transfer Windows between UEFI and BIOS:

l Recover the entire disk where the system volume is located. If you recover only the system
volume on top of an existing volume, the agent will not be able to initialize the target disk
properly.
l Remember that BIOS does not allow using more than 2 TB of disk space.

Limitations
l Transferring between UEFI and BIOS is supported for:
o 64-bit Windows operating systems starting with Windows 7
o 64-bit Windows Server operating systems starting with Windows Server 2008 SP1
l Transferring between UEFI and BIOS is not supported if the backup is stored on a tape device.

When transferring a system between UEFI and BIOS is not supported, the agent behaves as if the As
on the backed-up machine setting is chosen. If the target machine supports both UEFI and BIOS,
you need to manually enable the boot mode corresponding to the original machine. Otherwise, the
system will not boot.

Date and time for files

This option is effective only when recovering files.

This option defines whether to recover the files' date and time from the backup or assign the files
the current date and time.

If this option is enabled, the files will be assigned the current date and time.

The preset is: Enabled.

Error handling
These options enable you to specify how to handle errors that might occur during recovery.

Re-attempt, if an error occurs

The preset is: Enabled. Number of attempts: 30. Interval between attempts: 30 seconds.

When a recoverable error occurs, the program re-attempts to perform the unsuccessful operation.
You can set the time interval and the number of attempts. The attempts will be stopped as soon as
the operation succeeds OR the specified number of attempts are performed, depending on which
comes first.

Do not show messages and dialogs while processing (silent mode)

The preset is: Disabled.

497 © Acronis International GmbH, 2003-2024

With the silent mode enabled, the program will automatically handle situations requiring user
interaction where possible. If an operation cannot continue without user interaction, it will fail.
Details of the operation, including errors, if any, can be found in the operation log.

Save system information if a recovery with reboot fails

This option is effective for a disk or volume recovery to a physical machine running Windows or
Linux.

The preset is: Disabled.

When this option is enabled, you can specify a folder on the local disk (including flash or HDD drives
attached to the target machine) or on a network share where the log, system information, and crash
dump files will be saved. This file will help the technical support personnel to identify the problem.

File exclusions
This option is effective only when recovering files.

The option defines which files and folders to skip during the recovery process and thus exclude
from the list of recovered items.

Note
Exclusions override the selection of data items to recover. For example, if you select to recover file
MyFile.tmp and to exclude all .tmp files, file MyFile.tmp will not be recovered.

File-level security
This option is effective when recovering files from disk- and file-level backups of NTFS-formatted
volumes.

This option defines whether to recover NTFS permissions for files along with the files.

The preset is: Enabled.

You can choose whether to recover the permissions or let the files inherit their NTFS permissions
from the folder to which they are recovered.

Flashback
This option is effective when recovering disks and volumes on physical and virtual machines, except
for Mac.

This option works only if the volume layout of the disk being recovered exactly matches that of the
target disk.

If the option is enabled, only the differences between the data in the backup and the target disk
data are recovered. This accelerates recovery of physical and virtual machines. The data is
compared at the block level.

When recovering a physical machine, the preset is: Disabled.

498 © Acronis International GmbH, 2003-2024

When recovering a virtual machine, the preset is: Enabled.

Full path recovery

This option is effective only when recovering data from a file-level backup.

If this option is enabled, the full path to the file will be re-created in the target location.

The preset is: Disabled.

Mount points
This option is effective only in Windows for recovering data from a file-level backup.

Enable this option to recover files and folders that were stored on the mounted volumes and were
backed up with the enabled Mount points option.

The preset is: Disabled.

This option is effective only when you select for recovery a folder that is higher in the folder
hierarchy than the mount point. If you select for recovery folders within the mount point or the
mount point itself, the selected items will be recovered regardless of the Mount points option
value.

Note
Please be aware that if the volume is not mounted at the moment of recovery, the data will be
recovered directly to the folder that has been the mount point at the time of backing up.

Performance
This option defines the priority of the recovery process in the operating system.

The available settings are: Low, Normal, High.

The preset is: Normal.

The priority of a process running in a system determines the amount of CPU and system resources
allocated to that process. Decreasing the recovery priority will free more resources for other
applications. Increasing the recovery priority might speed up the recovery process by requesting the
operating system to allocate more resources to the application that will perform the recovery.
However, the resulting effect will depend on the overall CPU usage and other factors like disk I/O
speed or network traffic.

Pre/Post commands
The option enables you to define the commands to be automatically executed before and after the
data recovery.

Example of how you can use the pre/post commands:

499 © Acronis International GmbH, 2003-2024

l Launch the Checkdisk command in order to find and fix logical file system errors, physical errors
or bad sectors to be started before the recovery starts or after the recovery ends.

The program does not support interactive commands, i.e. commands that require user input (for
example, "pause".)

A post-recovery command will not be executed if the recovery proceeds with reboot.

Pre-recovery command
To specify a command/batch file to be executed before the recovery process starts

1. Enable the Execute a command before the recovery switch.

2. In the Command... field, type a command or browse to a batch file. The program does not
support interactive commands, i.e. commands that require user input (for example, "pause".)
3. In the Working directory field, specify a path to a directory where the command/batch file will
be executed.
4. In the Arguments field specify the command’s execution arguments, if required.
5. Depending on the result you want to obtain, select the appropriate options as described in the
table below.
6. Click Done.

Check box Selection

Fail the Selected Cleared Selected Cleared

recovery if
the
command
execution
fails*

Do not Selected Selected Cleared Cleared

recover
until the
command
execution is
complete

Result

Preset Perform the N/A Perform the recovery

recovery after the concurrently with the
Perform the recovery only
command is command execution
after the command is
executed despite and irrespective of the
successfully executed. Fail
execution failure or command execution
the recovery if the
success. result.
command execution failed.

* A command is considered failed if its exit code is not equal to zero.

500 © Acronis International GmbH, 2003-2024

Post-recovery command
To specify a command/executable file to be executed after the recovery is completed

1. Enable the Execute a command after the recovery switch.

2. In the Command... field, type a command or browse to a batch file.
3. In the Working directory field, specify a path to a directory where the command/batch file will
be executed.
4. In the Arguments field, specify the command execution arguments, if required.
5. Select the Fail the recovery if the command execution fails check box if successful execution
of the command is critical for you. The command is considered failed if its exit code is not equal
to zero. If the command execution fails, the recovery status will be set to Error.
When the check box is not selected, the command execution result does not affect the recovery
failure or success. You can track the command execution result by exploring the Activities tab.
6. Click Done.

Note
A post-recovery command will not be executed if the recovery proceeds with reboot.

SID changing
This option is effective when recovering Windows 8.1/Windows Server 2012 R2 or earlier.

This option is not effective when recovery to a virtual machine is performed by Agent for VMware,
Agent for Hyper-V, Agent for Scale Computing HC3, or Agent for oVirt.

The preset is: Disabled.

The software can generate a unique security identifier (Computer SID) for the recovered operating
system. You only need this option to ensure operability of third-party software that depends on
Computer SID.

Microsoft does not officially support changing SID on a deployed or recovered system. So use this
option at your own risk.

VM power management
These options are effective when recovery to a virtual machine is performed by Agent for VMware,
Agent for Hyper-V, Agent for Virtuozzo, Agent for Scale Computing HC3, or Agent for oVirt.

Power off target virtual machines when starting recovery

The preset is: Enabled.

Recovery to an existing virtual machine is not possible if the machine is online, and so the machine
is powered off automatically as soon as the recovery starts. Users will be disconnected from the
machine and any unsaved data will be lost.

501 © Acronis International GmbH, 2003-2024

Clear the check box for this option if you prefer to power off virtual machines manually before the
recovery.

Power on the target virtual machine when recovery is complete

The preset is: Disabled.

After a machine is recovered from a backup to another machine, there is a chance the existing
machine's replica will appear on the network. To be on the safe side, power on the recovered virtual
machine manually, after you take the necessary precautions.

Windows event log

This option is effective only in Windows operating systems.

This option defines whether the agents have to log events of the recovery operations in the
Application Event Log of Windows (to see this log, run eventvwr.exe or select Control Panel >
Administrative tools > Event Viewer). You can filter the events to be logged.

The preset is: Disabled.

Operations with backups

The Backup storage tab

The Backup storage tab provides access to all backups, including backups of offline machines,
backups of machines that are no longer registered in the Cyber Protection service, backups to public
clouds such as Microsoft Azure, and orphaned backups1.

Backups created via acrocmd are flagged as orphaned. Backups created in the 12.5 version of the
product are also identified as orphaned.

Note
Please note that orphaned backups are also charged.

Backups that are stored in a shared location (such as an SMB or NFS share) are visible to all users
that have the read permission for the location.

In Windows, backup files inherit the access permissions from their parent folder. Therefore, we
recommend that you restrict the read permissions for this folder.

In the cloud storage, users have access only to their own backups.

An administrator can view backups to cloud on behalf of any account that belongs to the given unit
or company and its child groups, by selecting the cloud storage for the account. To select the device
that you want to use to obtain data from cloud, click Change in the Machine to browse from row.

1An orphaned backup is a backup that is not associated to a protection plan anymore.

502 © Acronis International GmbH, 2003-2024

The Backup storage tab shows the backups of all machines ever registered under the selected
account.

Backups created by the cloud Agent for Microsoft 365 and backups of Google Workspace data are
shown not in the Cloud storage location, but in a separate section named Cloud applications
backups.

Backup locations that are used in protection plans are automatically added to the Backup storage
tab. To add a custom folder (for example, a detachable USB device) to the list of backup locations,
click Browse and specify the folder path.

If you added or removed some backups by using a file manager, click the gear icon next to the
location name, and then click Refresh.

Warning!
Do not try editing the backup files manually because this may result in file corruption and make the
backups unusable. Also, we recommend that you use the backup replication instead of moving
backup files manually.

A backup location (except for the cloud storage) disappears from the Backup storage tab if all
machines that had ever backed up to the location were deleted from the Cyber Protection service.
This ensures that you do not have to pay for the backups stored in this location. As soon as a
backup to this location occurs, the location is re-added along with all backups that are stored in it.

On the Backup storage tab, you can filter backups in the list by using the following criteria:

l Only with forensic data – only backups having forensic data will be shown.
l Only pre-update backups created by Patch management – only backups that were created
during patch management run before patch installation will be shown.

To select a recovery point by using the Backup storage tab

1. On the Backup storage tab, select the location where the backups are stored.
The software displays all backups that your account is allowed to view in the selected location.
The backups are combined in groups. The group names are based on the following template:
<machine name> - <protection plan name>
2. Select a group from which you want to recover the data.
3. [Optional] Click Change next to Machine to browse from, and then select another machine.
Some backups can only be browsed by specific agents. For example, you must select a machine
running Agent for SQL to browse the backups of Microsoft SQL Server databases.

Important
Please be aware that the Machine to browse from is a default destination for recovery from a
physical machine backup. After you select a recovery point and click Recover, double check the
Target machine setting to ensure that you want to recover to this specific machine. To change
the recovery destination, specify another machine in Machine to browse from.

503 © Acronis International GmbH, 2003-2024

4. Click Show backups.
5. Select the recovery point.

To add a location for a backup

Note
This operation is available only if you have an online agent.

On the Backup storage tab, click Add location.

Select a location from one of the following locations types, and then click Done:

l Local folder
l Network folder
l Secure Zone
l NFS folder
l Public cloud

Mounting volumes from a backup

Mounting volumes from a disk-level backup lets you access the volumes as though they were
physical disks.

Mounting volumes in the read/write mode enables you to modify the backup content; that is, save,
move, create, delete files or folders, and run executables consisting of one file. In this mode, the
software creates an incremental backup that contains the changes you make to the backup content.
Note that none of the subsequent backups will contain these changes.

Requirements
l This functionality is available only in Windows by using File Explorer.
l Agent for Windows must be installed on the machine that performs the mount operation.
l The backed-up file system must be supported by the Windows version that the machine is
running.
l The backup must be stored in a local folder, on a network share (SMB/CIFS), or in the Secure
Zone.

Usage scenarios
l Sharing data
Mounted volumes can be easily shared over the network.
l "Band-aid" database recovery solution
Mount a volume that contains an SQL database from a recently failed machine. This will provide
access to the database until the failed machine is recovered. This approach can also be used for
granular recovery of Microsoft SharePoint data by using SharePoint Explorer.
l Offline virus removal

504 © Acronis International GmbH, 2003-2024

 If a machine is infected, mount its backup, clean it with an antivirus program (or find the latest
backup that is not infected), and then recover the machine from this backup.
l Error check
If a recovery with volume resize has failed, the reason may be an error in the backed-up file
system. Mount the backup in the read/write mode. Then, check the mounted volume for errors
by using the chkdsk /r command. After the errors are fixed and a new incremental backup is
created, recover the system from this backup.

To mount a volume from a backup

1. Browse to the backup location by using File Explorer.

2. Double-click the backup file. The file names are based on the following template:
<machine name> - <protection plan GUID>
3. If the backup is encrypted, enter the encryption password. Otherwise, skip this step.
File Explorer displays the recovery points.
4. Double-click the recovery point.
File Explorer displays the backed-up volumes.

Note
Double-click a volume to browse its content. You can copy files and folders from the backup to
any folder on the file system.

5. Right-click a volume to mount, and then select one of the following options:
a. Mount

Note
Only the last backup in the archive (backup chain) can be mounted in read-write mode.

b. Mount in read-only mode.

6. If the backup is stored on a network share, provide access credentials. Otherwise, skip this step.
The software mounts the selected volume. The first unused letter is assigned to the volume.

To unmount a volume

1. Browse to Computer (This PC in Windows 8.1 and later) by using File Explorer.
2. Right-click the mounted volume.
3. Click Unmount.
4. [Optional] If the volume was mounted in the read/write mode, and its content was modified,
select whether to create an incremental backup containing the changes. Otherwise, skip this
step.

The software unmounts the selected volume.

505 © Acronis International GmbH, 2003-2024

Validating backups
By validating a backup, you verify that you can recover the data from it. For more information about
this operation, refer to "Validation" (p. 193).

Note
This functionality is available in customer tenants for which the Advanced Backup – Servers or the
Advanced Backup – NAS quota is enabled as part of the Advanced Backup pack.

To validate a backup

1. Select the backed-up workload.

2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the workload is offline, the recovery points are not displayed. Do any of the following:
l If the backup location is cloud or shared storage (that is, other agents can access it), click
Select machine, select a target workload that is online, and then select a recovery point.
l Select a recovery point on the Backup storage tab. For more information about the backups
there, refer to "The Backup storage tab" (p. 502).
4. Click the gear icon, and then click Validate.
5. Select the agent that will perform the validation.
6. Select the validation method.
7. If the backup is encrypted, provide the encryption password.
8. Click Start.

Exporting backups
The export operation creates a self-sufficient copy of a backup in the location that you specify. The
original backup remains untouched. Exporting backups allows you to separate a specific backup
from a chain of incremental and differential backups for fast recovery, for writing onto removable or
detachable media, or for other purposes.

Note
This functionality is available in customer tenants for which the Advanced Backup – Servers or the
Advanced Backup – NAS quota is enabled as part of the Advanced Backup pack.

The result of an export operation is always a full backup. If you want to replicate the entire backup
chain to a different location and preserve multiple recovery points, use a backup replication plan.
For more information about this plan, refer to "Backup replication" (p. 191).

The backup file name of the exported backup is the same as that of the original backup, except for
the sequence number. If multiple backups from the same backup chain are exported to the same
location, a four-digit sequence number is appended to the file names of all backups except for the
first one.

506 © Acronis International GmbH, 2003-2024

The exported backup inherits the encryption settings and password from the original backup. When
exporting an encrypted backup, you must specify the password.

To export a backup

1. Select the backed-up workload.

2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the workload is offline, the recovery points are not displayed. Do any of the following:
l If the backup location is cloud or shared storage (that is, other agents can access it), click
Select machine, select a target workload that is online, and then select a recovery point.
l Select a recovery point on the Backup storage tab. For more information about the backups
there, refer to "The Backup storage tab" (p. 502).
4. Click the gear icon, and then click Export.
5. Select the agent that will perform the export.
6. If the backup is encrypted, provide the encryption password. Otherwise, skip this step.
7. Specify the export destination.
8. Click Start.

Deleting backups
A backup archive contains one or more backups. You can delete specific backups (recovery points)
in an archive or the whole archive.

Deleting the backup archive deletes all backups in it. Deleting all backups of a workload deletes the
backup archives that contain these backups.

You can delete backups by using the Cyber Protect console – on the Devices tab and on the Backup
storage tab. Also, you can delete backups from the cloud storage by using the Web Restore console.

Warning!
If immutable storage is disabled, backed-up data is permanently deleted and cannot be recovered.

To delete backups or backup archives

On the Devices tab

This procedure applies only to online workloads.

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the workload backups of which you want to delete.
3. Click Recovery.
4. [If more than one backup location is available] Select the backup location.
5. [To delete all backups of the workload] Click Delete all.
Deleting all backups also deletes the backup archives that contain these backups.

507 © Acronis International GmbH, 2003-2024

6. [To delete a specific backup] Select the backup (recovery point) that you want to delete, and then
click Actions > Delete.
7. [When deleting all backups] Select the check box, and then click Delete to confirm your decision.
8. [When deleting a specific backup] Click Delete to confirm your decision.

On the Backup storage tab

This procedure applies to online and offline workloads.

1. In the Cyber Protect console, go to Backup storage.

2. Select the location from which you want to delete backups.
3. Select the backup archive from which you want to delete backups.
The archive name uses the following template:
l Non-cloud-to-cloud backup archives: <workload name> - <protection plan name>
l Cloud-to-cloud backup archives: <user name> or <drive name> or <team name> - <cloud
service> - <protection plan name>
4. [To delete the whole backup archive] Click Delete.
Deleting a backup archive deletes all backups in that archive.
5. [To delete a specific backup in the backup archive] Click Show backups.
a. Select the backup (recovery point) that you want to delete.
b. Click Actions > Delete.
6. [When deleting a backup archive] Select the check box, and then click Delete to confirm your
decision.
7. [When deleting a specific backup] Click Delete to confirm your decision.

In the Web Restore console

This procedure applies only to backup archives in the cloud storage.

1. In the Cyber Protection console, go to Devices > All devices.

2. Select the workload backups of which you want to delete, and then click Recovery.
3. [If multiple backup locations are available] Select the backup location, and then click More ways
to recover.
4. Click Download files.
You are redirected to the Web Restore console.
5. In the Web Restore console, under Machines, click the workload name.
6. Under Last version, click the date, and then click Delete.
This action is only available on the backup archive level. You cannot drill down the archive and
delete specific backups from it.
7. Click Delete to confirm your decision.

Deleting backups outside the Cyber Protect console

We recommend that you delete backups by using the Cyber Protect console. If you delete backups
from the cloud storage by using the Web Restore console or delete local backups by using a file

508 © Acronis International GmbH, 2003-2024

manager, you must refresh the backup location to sync the changes to the Cyber Protect console.

Prerequisite

l An online agent that can access the backup location must be selected as Machine to browse
from in the Cyber Protect console.

To refresh a backup location

1. In the Cyber Protect console, go to Backup storage.

2. Select the backup location in which the deleted backups were stored.
3. In the Actions pane, click Refresh.

Understanding the detection of bottlenecks

The bottleneck detection feature helps you understand where you can improve performance by
highlighting which component in your system was the slowest during a backup or recovery process.

As bottlenecks always occur in any transmission event, it does not necessarily mean they need to be
resolved. Your backups may be already fast enough and meet your backup windows perfectly, as
well as meet your SLAs, so there is typically nothing you need to actually resolve.

You can easily view and track bottlenecks in the Activity details tab. To do this, in the Cyber Protect
console, go to Monitoring > Activities, and then click the relevant activity. For more information
about viewing bottlenecks, see "Viewing bottleneck details" (p. 511) and "On what workloads,
agents, and backup locations are bottlenecks shown?" (p. 512).

What is a bottleneck?
Bottlenecks are typically caused due to a slow component in the processing chain, in other words, a
component that the other components wait for.

The bottleneck detection feature enables you to track these slow components during the backup
and recovery process, helping you understand which of the following component types is the
slowest:

l Source: At a glance, you can determine if the reading speed from the backup/recovery source is
causing a bottleneck.
l Destination: Understand if the writing speed to the backup/recovery destination is affecting

509 © Acronis International GmbH, 2003-2024

 performance.
l Agent: Understand if the agent is processing the data fast enough.

The bottleneck type, whether from the source, destination, or agent, can change at different times
during the backup/recovery activity. The percentages shown in the Bottleneck section of the
Activity details tab below (for example, Read data from source (workload): 63%), represent the
percentage of time when this type of bottleneck was encountered. In this case, for 63% of the
recovery activity time, the bottleneck type was reading data, in other words, the slow speed in
reading data from the backup archive by the agent.

Similarly, for 30% of the time, the bottleneck was due to the slow speed in writing data to the
recovery destination (Write data to destination: 30%).

Note
It is normal behavior to see bottleneck statistics in the Activity details tab. These statistics are only
available for tasks more than one minute long.

How to reduce bottlenecks

As mentioned above, the bottleneck detection feature highlights the read and write data flow
between backup components. The read statistics refer to the data flow from the data source to the

510 © Acronis International GmbH, 2003-2024

agent which performs the backup/recovery operation, and the write statistics refer to the data flow
between the agent and the backup archive (the destination).

Тo reduce bottlenecks and improve the read/write data flow performance, you should analyze the
channel between the agent and the data source/backup archive. For example, you can try
benchmarking your hard disks if the agent is backing up some local files.

Viewing bottleneck details

You can view detected bottlenecks for any type of backup, backup replication, or recovery process
(to any type of destination folder or location), including virtual machine backups, machine backups,
and file/folder backups. You can also view bottlenecks for virtual machine replication and failback
activities.

For more information on the definition and core concepts of bottleneck types, see "Understanding
the detection of bottlenecks" (p. 509).

To view bottleneck details

1. In the Cyber Protect console, go to Monitoring > Activities.

2. Click on the relevant activity.
In the Activity details tab, the Bottleneck section is shown in blue.

511 © Acronis International GmbH, 2003-2024

3. Click Show details to view the most frequently encountered bottleneck during the
backup/recovery operation.
The Bottleneck section expands to show a summary of the relevant bottleneck types.

In the example above, the bottleneck that accounted for 63% of the entire operation's time was
caused by the Read operation (performed by the agent).

Note
The bottleneck values update dynamically every minute while the corresponding activity is
running.

On what workloads, agents, and backup locations are bottlenecks shown?

The detection of bottlenecks is available for the following types of workloads, agents, and backup
locations:

l Disk/image-level backups performed by:

o Agent for Azure
o Agent for Windows
o Agent for Linux
o Agent for MAC
o Agent for VMware (both Virtual Appliance and Windows, including VM replication and failback
from replica (restore from replica) activities)
o Agent for Hyper-V
o Agent for Scale Computing
o Agent for oVirt (KVM)
o Agent for Virtuozzo Infrastructure Platform
o Agent for Virtuozzo
o Agent for VMware Cloud Director (vCD-BA)
l File-level backups
o Agent for Windows
o Agent for Linux
o Agent for MAC

512 © Acronis International GmbH, 2003-2024

l Application-level backups
o Agent for SQL
o Agent for Exchange
o Agent for MySQL/MariaDB
o Agent for Oracle
o Agent for SAP HANA
l Backup locations
o Acronis Cloud storage (including partner hosted storage)
o Public Cloud storage
o Network shares (SMB + NFS)
o Local folders
o Locations defined by script
o Acronis Secure Zone

Backing up workloads to public clouds

Note
This feature is part of the Advanced Backup pack, which in turn is part of the Cyber Protection
service. Note that when you add this functionality to a protection plan, you may be subject to
additional charges.

You can select public cloud services, such as Microsoft Azure and Amazon S3 (Simple Storage
Service), as backup destinations in the Cyber Protect console.

To configure backup locations on public clouds, you must be a Company administrator or Unit
administrator, or have one of the following roles defined in the Cyber Protection service: Cyber
administrator, Administrator, or User.

Defining a backup location in Microsoft Azure

Note
To configure backup locations on Microsoft Azure you must have one of the following roles defined
in the Cyber Protection service: Company administrator, User, Cyber administrator.

To back up a workload to Microsoft Azure, you need to define the Microsoft Azure backup location
in the Cyber Protect console, and connect to the relevant Microsoft Azure subscription. This can be
done in the following ways:

l When creating or editing a protection plan.

l When defining and managing backup storage locations.

513 © Acronis International GmbH, 2003-2024

Important
Both administrators and non-administrator users can back up workloads to Microsoft Azure.

Non-administrator users can add access to a Microsoft Azure subscription (see "Managing access to
Microsoft Azure subscriptions" (p. 528)), but can only apply protection plans where the backup
location is connected to the Microsoft Azure subscription they added themselves, and for workloads
registered in the Cyber Protect console under their name.

Administrators can apply protection plans where the backup location is connected to Microsoft
Azure subscriptions they added themselves or to subscriptions added by any other administrator,
and for workloads registered in the Cyber Protect console under any user.

To define a backup location in Microsoft Azure

1. In the Cyber Protect console, do one of the following:

l If you are creating or editing a protection plan, go to Devices and select the relevant workload
you want to back up to Microsoft Azure. In the Backup section of the selected workload's
protection plan, click the link in the Where to back up row.
For more information about working with protection plans, see "Protection plans and
modules" (p. 205).
l If you are managing your backup storage locations and want to add Microsoft Azure as a new
location, go to Backup storage.
For more information about managing your backup storage locations, see "The Backup
storage tab" (p. 502).
2. Click Add location.
3. From the Public clouds drop-down list, select Microsoft Azure.
4. If the relevant Microsoft Azure subscription is already registered in the Cyber Protect console,
select it from the list of subscriptions.
If the relevant subscription is not registered in the Cyber Protect console, click Add and in the
displayed dialog, click Sign in. You are redirected to the Microsoft login page. For more
information about adding and defining access to a Microsoft Azure subscription, see "Adding
access to a Microsoft Azure subscription" (p. 529).
5. In the Storage account field, select the relevant account.

Note
Only Microsoft Azure storage accounts with regular endpoint suffixes that contain
core.windows.net are currently supported. In addition, the selected storage account must be a
StorageV2 account type.

The Location name and Access tier fields are automatically filled by default, according to the
storage account selected. The location name displayed is microsoft_azure_[storage account]
and the access tier selected is Default (Hot). Both fields can be modified, as required.

514 © Acronis International GmbH, 2003-2024

 Note
When changing the location name, enter a unique location name (the name must be unique to
the customer tenant). If the name you add already exists in the storage account, Acronis adds a
suffix number to the name. For example, if Microsoft Azure Storage already exists, the name is
automatically updated to Microsoft Azure Storage_01.

6. Click Add.
If you are creating or editing a protection plan, the Microsoft Azure backup location is set as the
location in Where to back up row. When the backup is run (either manually or when
scheduled), the backup is saved in the defined location.
If you are managing your backup storage locations, you can view and update the location details
as required. The Microsoft Azure location is also available when defining a backup location for
workloads. For more information, see "Viewing and updating public cloud backup locations" (p.
519).

Defining a backup location in Amazon S3

Note
To configure backup locations on Amazon S3, you must have one of the following roles defined in
the Cyber Protection service: Company administrator, User, Cyber administrator.

515 © Acronis International GmbH, 2003-2024

To back up a workload to Amazon S3, you must define the Amazon S3 backup location in the Cyber
Protect console, and then connect to the relevant Amazon S3 connection. You can do this in the
following ways:

l When creating or editing a protection plan.

l When defining and managing backup storage locations.

Important
Both administrators and non-administrator users can back up workloads to Amazon S3.

Non-administrator users can add access to an Amazon S3 connection (see "Managing access to
other public cloud storage services" (p. 532)), but can only apply protection plans where the backup
location is connected to the Amazon S3 connection they added themselves, and for workloads
registered in the Cyber Protect console under their name.

Administrators can apply protection plans where the backup location is connected to Amazon S3
connections they added themselves or to subscriptions added by any other administrator, and for
workloads registered in the Cyber Protect console under any user.

To define a backup location in Amazon S3

1. In the Cyber Protect console, do one of the following:

l If you are creating or editing a protection plan, go to Devices, and then select the workload
that you want to back up to Amazon S3. In the Backup section of the selected workload's
protection plan, click the link in the Where to back up row.
For more information about working with protection plans, see "Protection plans and
modules" (p. 205).
l If you are managing your backup storage locations and want to add Amazon S3 as a new
location, go to Backup storage.
For more information about managing your backup storage locations, see "The Backup
storage tab" (p. 502).
2. Click Add location.
3. From the Public clouds drop-down list, select Amazon S3.
4. If the relevant Amazon S3 connection is already registered in the Cyber Protect console, select it
from the list.
If the relevant connection is not registered in the Cyber Protect console, click Add new
connection. For more information about adding and defining access to an Amazon S3
connection, see "Adding access to a public cloud connection" (p. 532). When the connection is
added, continue to the next step.

516 © Acronis International GmbH, 2003-2024

5. Define the following:
l In the Location name field, enter the name of the backup location.

Note
The location name must be unique to the customer tenant. If the name you add already exists
in the connection, Acronis adds a suffix number to the name. For example, if Amazon S3
storage already exists, the name will be automatically updated to Amazon S3 storage 1.

l In the Storage Class field, select from one of the following supported storage classes:
o S3 Standard
o Standard - Infrequent Access (S3 Standard-IA)
o One Zone - Infrequent Access (S3 One Zone-IA)
o S3 Intelligent Tiering
l In the Bucket field, select the relevant Amazon S3 bucket.
6. Click Add.
If you are creating or editing a protection plan, the Amazon S3 backup location is set as the
location in the Where to back up row. When the backup is run (either manually or when
scheduled), the backup is saved in the defined location.
If you are managing your backup storage locations, you can view and update the location details
as required. The Amazon S3 location is also available when defining a backup location for
workloads. For more information, see "Viewing and updating public cloud backup locations" (p.
519).

517 © Acronis International GmbH, 2003-2024

Defining a backup location in Wasabi

Note
To configure backup locations in Wasabi, you must have one of the following roles defined in the
Cyber Protection service: Company administrator, User, Cyber administrator.

To back up a workload to Wasabi, you must define the Wasabi backup location in the Cyber Protect
console, and connect to the relevant Wasabi connection. You can do this in the following ways:

l When creating or editing a protection plan.

l When defining and managing backup storage locations.

Important
Both administrators and non-administrator users can back up workloads to Wasabi.

Non-administrator users can add access to a Wasabi connection (see "Managing access to other
public cloud storage services" (p. 532)), but can only apply protection plans where the backup
location is connected to the Wasabi connection they added themselves, and for workloads
registered in the Cyber Protect console under their name.

Administrators can apply protection plans where the backup location is connected to Wasabi
connections they added themselves or to subscriptions added by any other administrator, and for
workloads registered in the Cyber Protect console under any user.

To define a backup location in Wasabi

1. In the Cyber Protect console, do one of the following:

l If you are creating or editing a protection plan, go to Devices, and then select the workload
that you want to back up to Wasabi. In the Backup section of the selected workload's
protection plan, click the link in the Where to back up row.
For more information about working with protection plans, see "Protection plans and
modules" (p. 205).
l If you are managing your backup storage locations and want to add Wasabi as a new location,
go to Backup storage.
For more information about managing your backup storage locations, see "The Backup
storage tab" (p. 502).
2. Click Add location.
3. From the Public clouds drop-down list, select Wasabi.
4. If the relevant Wasabi connection is already registered in the Cyber Protect console, select it
from the list of connections.
If the relevant connection is not registered in the Cyber Protect console, click Add new
connection. For more information about adding and defining access to a Wasabi connection,

518 © Acronis International GmbH, 2003-2024

 see "Adding access to a public cloud connection" (p. 532). When the connection is added,
continue to the next step.

5. Define the following:

l In the Location name field, enter the name of the backup location.

Note
The location name must be unique to the customer tenant. If the name you add already exists
in the connection, Acronis adds a suffix number to the name. For example, if Wasabi storage
already exists, the name will be automatically updated to Wasabi storage 1.

l In the Bucket field, select the relevant Wasabi bucket.

6. Click Add.
If you are creating or editing a protection plan, the Wasabi backup location is set as the location
in the Where to back up row. When the backup is run (either manually or when scheduled), the
backup is saved in the defined location.
If you are managing your backup storage locations, you can view and update the location details
as required. The Wasabi location is also available when defining a back up location for
workloads. For more information, see "Viewing and updating public cloud backup locations" (p.
519).

Viewing and updating public cloud backup locations

You can view and update the Microsoft Azure, Amazon S3, and Wasabi backup locations you define
in the Backup storage module, or when creating or editing a protection plan.

For information about removing access to a Microsoft Azure subscription from the Cyber Protect
console, see "Removing access to a Microsoft Azure subscription" (p. 531). For information about
removing access to other public cloud connections, see "Managing access to other public cloud
storage services" (p. 532).

519 © Acronis International GmbH, 2003-2024

Note
You cannot manually refresh or delete a public cloud backup location in the Backup storage
module. The contents of the backup location are updated automatically after each backup or
recovery operation.

To view public cloud backup locations

1. In the Cyber Protect console, go to Backup storage.

A list of backup locations is displayed, with details of the storage capacity and number of
backups assigned to each location.
For more information about working with the listed backup locations, see "The Backup storage
tab" (p. 502).
2. Select the relevant location.
Any current backups for the selected location are listed.
3. (Optional) Click on a backup to view more details for the backup.

To update a public cloud backup location in a protection plan

1. Go to the relevant protection plan, and select Edit.

2. Click the link in the Where to back up row.
3. Select from the list of existing backup locations, or click Add location to add a new location.
If the relevant Microsoft Azure subscription or public cloud connection is already registered in
the Cyber Protect console, select it from the displayed list.
If you are adding a new Microsoft Azure subscription, you will be prompted to authenticate your
Microsoft account details (see "Adding access to a Microsoft Azure subscription" (p. 529). For
more information about the required permissions when connecting to Microsoft Azure, see
article Microsoft Azure connection security and audit (72684).

Managing public cloud account access

To enable Acronis Cyber Protection services in public cloud platforms, access to the relevant public
cloud accounts needs to be configured.

For example, when working with Microsoft Azure, access to your Microsoft Azure subscription is
required. Once added in the Cyber Protect console, the subscription can be selected when you
configure a direct backup to Microsoft Azure. Similarly, when working with Amazon S3 and Wasabi,
the relevant access keys that are associated with specific backup-related policies are required.

Access to public clouds is managed through the Infrastructure menu in the Cyber Protect console.

Important
Backup validation is disabled for backups on public cloud storage, to avoid excessive egress traffic
costs. In addition, you cannot currently ”re-attach” a backup location on a public cloud to the same
or different customer tenant if the location was previously removed. For more information, contact
the Support team.

520 © Acronis International GmbH, 2003-2024

Access requirements needed to backup to public cloud storage
When directly backing up to public cloud storage services, there are a number of access
requirements to consider for each platform:

l Microsoft Azure
l Amazon S3
l Wasabi

Backing up to Microsoft Azure

To connect to a Microsoft Azure subscription, you must have several permissions. For more
information about them, see article Microsoft Azure connection security and audit (72684).

Backing up to Amazon S3
When you back up to Amazon S3, there are several requirements when defining Amazon S3 backup
locations:

l Supported storage classes

l Policy permissions
l Access keys
l Bucket settings

Supported storage classes

The following Amazon S3 storage classes are currently supported:

l S3 Standard
l Standard - Infrequent Access (S3 Standard-IA)
l One Zone - Infrequent Access (S3 One Zone-IA)
l S3 Intelligent Tiering

Policy permissions
When you back up to Amazon S3, your Amazon account must have the minimum permissions
applied to ensure Acronis can back up the relevant workloads to Amazon S3. This means that the
relevant users should have access to the AWS Management Console, and have the relevant policy
applied to the group(s) they are assigned to.

Examples

The following example policy shows the minimum set of permissions for a wide scope of resources.
Note that * indicates all resources.

521 © Acronis International GmbH, 2003-2024

 {

"Version": "2012-10-17",

"Statement": [

"Effect": "Allow",

"Action": "s3:ListAllMyBuckets",

"Resource": "*"

},

"Effect": "Allow",

"Action": [

"s3:GetBucketLocation",

"s3:GetBucketObjectLockConfiguration"

],

"Resource": "*"

},

"Effect": "Allow",

"Action": "sts:GetFederationToken",

"Resource": "*"

},

"Effect": "Allow",

"Action": [

"s3:GetBucketLocation",

"s3:PutObject",

"s3:GetObject",

"s3:DeleteObject"

],

"Resource": "*"

},

522 © Acronis International GmbH, 2003-2024

 {

"Effect": "Allow",

"Action": [

"s3:ListBucket"

],

"Resource": "*"

The following example policy shows the minimum permissions limited to a specific bucket. Note
that [BUCKETNAME] should be replaced with the name of the bucket.

"Version": "2012-10-17",

"Statement": [

"Effect": "Allow",

"Action": "s3:ListAllMyBuckets",

"Resource": "*"

},

"Effect": "Allow",

"Action": [

"s3:GetBucketLocation",

"s3:GetBucketObjectLockConfiguration"

],

"Resource": "arn:aws:s3:::[BUCKETNAME]"

},

"Effect": "Allow",

"Action": "sts:GetFederationToken",

523 © Acronis International GmbH, 2003-2024

 "Resource": "*"

},

"Effect": "Allow",

"Action": [

"s3:GetBucketLocation",

"s3:PutObject",

"s3:GetObject",

"s3:DeleteObject"

],

"Resource": "arn:aws:s3:::[BUCKETNAME]/*"

},

"Effect": "Allow",

"Action": [

"s3:ListBucket"

],

"Resource": "arn:aws:s3:::[BUCKETNAME]"

Access keys
Access keys are required by Acronis for each Amazon S3 connection, and are used when defining
the Amazon S3 connection. For more information about generating access keys and access key IDs,
see the Amazon S3 documentation.

Bucket settings
When using Amazon S3 buckets as the backup location, ensure that the bucket is configured with
the default settings, including the blocking of all public access (by default this is set to On). For more
information about working with buckets, see the Amazon S3 documentation.

Note
Acronis does not currently support bucket versioning and object locking in Amazon S3, even when
enabled on the bucket.

524 © Acronis International GmbH, 2003-2024

Backing up to Wasabi
When you backup to Wasabi, there are a number of requirements you need to consider when
defining backup locations:

l Policy permissions
l Access keys
l Bucket settings

Policy permissions
When you define a backup location in Wasabi, ensure that the relevant policies are applied to the
relevant groups and users in Wasabi.

Examples

The following example policy shows the minimum set of permissions with a wide scope of
resources. Note that * indicates any resource.

"Version": "2012-10-17",

"Statement": [

"Effect": "Allow",

"Action": "s3:ListAllMyBuckets",

"Resource": "*"

},

"Effect": "Allow",

"Action": "s3:GetBucketLocation",

"Resource": "*"

},

"Effect": "Allow",

"Action": [

"iam:CreateRole",

"iam:AttachRolePolicy",

"sts:GetCallerIdentity",

525 © Acronis International GmbH, 2003-2024

 "sts:AssumeRole"

],

"Resource": "*"

},

"Effect": "Allow",

"Action": [

"s3:PutObject",

"s3:GetObject",

"s3:DeleteObject"

],

"Resource": "*"

},

"Effect": "Allow",

"Action": "s3:ListBucket",

"Resource": "*"

The following example policy shows limited permissions with a limited scope of resources. Note that
[BUCKETNAME] should be replaced with the name of the bucket, and [ACCOUNTID] with the ID of the
Wasabi account.

"Version": "2012-10-17",

"Statement": [

"Effect": "Allow",

"Action": "s3:ListAllMyBuckets",

526 © Acronis International GmbH, 2003-2024

 "Resource": "*"

},

"Effect": "Allow",

"Action": "s3:GetBucketLocation",

"Resource": "arn:aws:s3:::[BUCKETNAME]"

},

"Effect": "Allow",

"Action": [

"iam:CreateRole",

"iam:AttachRolePolicy",

"sts:GetCallerIdentity",

"sts:AssumeRole"

],

"Resource": "arn:aws:iam::[ACCOUNTID]:*"

},

"Effect": "Allow",

"Action": [

"s3:PutObject",

"s3:GetObject",

"s3:DeleteObject"

],

"Resource": "arn:aws:s3:::[BUCKETNAME]/*"

},

"Effect": "Allow",

"Action": "s3:ListBucket",

"Resource": "arn:aws:s3:::[BUCKETNAME]"

527 © Acronis International GmbH, 2003-2024

 ]

Access keys
Access keys are required by Acronis for each Wasabi connection, and are used when defining the
Wasabi connection. For more information about generating access keys and access key IDs, see the
Wasabi documentation.

Bucket settings
When using Wasabi buckets as the backup location, ensure that the bucket is configured with the
default settings. For more information about working with buckets, see the Wasabi documentation.

Note
Acronis does not currently support bucket versioning and object locking in Wasabi, even when
enabled on the bucket.

Managing access to Microsoft Azure subscriptions

By connecting to the relevant Microsoft Azure subscriptions in the Cyber Protect console, you can
directly back up the relevant workloads to Microsoft Azure.

Connection to a subscription can be configured when creating a backup location via the Devices or
Backup storage menu, as described in "Defining a backup location in Microsoft Azure" (p. 513).

Alternatively, these Microsoft Azure subscriptions can be configured in the Public clouds screen (go
to Infrastructure > Public clouds). Here you can also manage your subscriptions, including
renewing access to the subscription, viewing subscription properties and activities, or removing the
subscription.

Depending on your assigned user role, you may be able to manage Microsoft Azure subscriptions
added by other users within your organization. For example, if you are a Company administrator or
Unit administrator, or have been assigned the Cyber administrator or Administrator role in the
Cyber Protection service, you can view and manage Microsoft Azure subscriptions added by other
administrators, and subscriptions added by non-administrator users. Non-administrator users can
only view and access Microsoft Azure subscriptions they added to the Cyber Protect console.

Note
Partners can manage the Microsoft Azure subscriptions of customers below their level in the
hierarchy. However, when a partner selects All customers, the Infrastructure menu in the Cyber
Protect console is not available.

528 © Acronis International GmbH, 2003-2024

Important
When connecting to a Microsoft Azure subscription, Acronis requires the minimum permissions to
connect to the subscription. For more information about the required permissions, refer to article
Microsoft Azure connection security and audit (72684).

Adding access to a Microsoft Azure subscription

By adding a Microsoft Azure subscription in the Cyber Protect console, Acronis can securely access
your subscription and directly back up the relevant workloads to Microsoft Azure.

To add access to a Microsoft Azure subscription

1. In the Cyber Protect console, go to Infrastructure > Public clouds.

2. Click Add, and from the displayed list of options, select Microsoft Azure.
3. In the displayed dialog, click Sign in. You are redirected to the Microsoft login page.

Note
You must be assigned with one of the following roles in Microsoft Azure AD in order to complete
the connection to the subscription: Cloud Application Administrator, Application Administrator,
or Global Administrator. You must also be assigned the Owner role for each selected
subscription.

4. In the Microsoft login screen, enter your login credentials and accept the requested permissions.
The connection process starts, and may take several minutes.
For more information about securely accessing your Microsoft Azure and subscription, refer to
article Microsoft Azure connection security and audit (72684).
5. When the connection is complete, select the relevant subscription from the drop-down list in the
displayed dialog, and click Add subscription.

The subscription is added to the list of public clouds.

To renew the annual access certificate for the subscription, see "Renewing access to a Microsoft
Azure subscription" (p. 530).

529 © Acronis International GmbH, 2003-2024

 To remove access to the subscription, see "Removing access to a Microsoft Azure subscription"
(p. 531).

Note
If the Microsoft Azure account you are logged into includes access to multiple Microsoft Azure
ADs, including ADs in which you were invited as a guest user, only the default user directory is
selected. If you want to use a directory in which you are a guest user, you need to create a new
user in that specific Microsoft Azure AD. You can then log in to that account and connect to the
relevant subscription.

Renewing access to a Microsoft Azure subscription

Once registered in the Cyber Protect console, access to a Microsoft Azure subscription is
automatically set for one year by Acronis using a free and unique access certificate. When the
certificate nears its expiry date, you can quickly and easily renew it.

To renew the access certificate for your Microsoft Azure subscription

1. In the Cyber Protect console, go to Infrastructure > Public clouds.

2. Select the relevant subscription from the displayed list.

Note
The Access status column indicates the current status of the access certificate for each
subscription and shows one of two statuses: OK or Expired.

3. In the right pane, click Renew access.

Alternatively, click the Subscription tab, and then click Renew in the Access expiration date
field.

530 © Acronis International GmbH, 2003-2024

4. In the Microsoft login screen, enter your login credentials and accept the requested permissions.
The connection process starts, and may take several minutes.
When the authentication is successful, access is automatically renewed for one year.
For more information about the required permissions, refer to article Microsoft Azure
connection security and audit (72684).

Removing access to a Microsoft Azure subscription

You should remove access to the Microsoft Azure subscription if you are not backing up workloads
to Microsoft Azure.

To remove access to a Microsoft Azure subscription

Important
You cannot remove a subscription if it is currently being used to backup to Microsoft Azure.

1. In the Cyber Protect console, go to Infrastructure > Public clouds.

2. Select the relevant subscription from the displayed list.
3. In the right pane, click Delete.

Note
You can only remove a subscription you added. You can also remove a subscription if you are a
Company administrator or Unit administrator, or were assigned the role of Cyber administrator
or Administrator in the Cyber Protection service.

4. In the displayed confirmation message, click Remove.

531 © Acronis International GmbH, 2003-2024

Managing access to other public cloud storage services

Note
This section refers to managing access for all public cloud storage services other than Microsoft
Azure, which is described in "Managing access to Microsoft Azure subscriptions" (p. 528).

By connecting to the relevant public cloud account in the Cyber Protect console, you can directly
back up workloads to the relevant public cloud storage.

You can configure connections to public cloud storage accounts when creating a backup location via
the Devices or Backup storage menu. Alternatively, you can configure public cloud connections in
the Public clouds screen (go to Infrastructure > Public clouds). Here you can also manage your
connection, including renewing access to the connection, viewing connection properties and
activities, or removing the connection.

Depending on your assigned user role, you may be able to manage public cloud connections added
by other users within your organization. For example, if you are a Company administrator or Unit
administrator, or have been assigned the Cyber administrator or Administrator role in the Cyber
Protection service, you can view and manage public cloud connections added by other
administrators, as well as connections added by non-administrator users. Non-administrator users
can only view and access public cloud connections they added to the Cyber Protect console.

Note
Partners can manage the public cloud connections of customers below their level in the hierarchy.
However, when a partner selects All customers, the Infrastructure menu in the Cyber Protect
console is not available.

Important
When connecting to a public cloud connection, Acronis requires a number of permissions. For more
information, see "Access requirements needed to backup to public cloud storage" (p. 521).

Adding access to a public cloud connection

After adding a public cloud connection (such as Amazon S3 or Wasabi) in the Cyber Protect console,
Acronis can securely access your cloud resources and directly back up workloads to the relevant
public cloud storage.

To add access to a public cloud connection

1. In the Cyber Protect console, go to Infrastructure > Public clouds.

2. Click Add, and select one of the following options:
l Amazon S3
In the displayed dialog, define the following:
o Connection name: The name for the Amazon S3 connection.
o Access key ID: The user Access key ID for the Amazon S3 service.

532 © Acronis International GmbH, 2003-2024

 o Access key: The user Access key for the Amazon S3 service.
The Access key and Access key ID enable Acronis to access the storage classes and buckets
for the relevant connection. For more information about the access keys and permissions
required by Acronis, see "Access requirements needed to backup to public cloud storage"
(p. 521).

l Wasabi
In the displayed dialog, define the following:
o Connection name: The name for the Wasabi connection.
o Access key ID: The user Access key ID for the Wasabi service.
o Access key: The user Access key for the Wasabi service.
The Access key and Access key ID enable Acronis to access the storage classes and buckets
for the relevant connection. For more information about the access keys and permissions
required by Acronis, see "Access requirements needed to backup to public cloud storage"

533 © Acronis International GmbH, 2003-2024

 (p. 521).

3. Click Connect.
The connection process starts, and may take several minutes. When finished, the connection is
added to the list of public clouds.
To renew the annual access certificate for the connection, see "Renewing access to a public cloud
connection" (p. 534).
To remove access to the connection, see "Removing access to a public cloud connection" (p. 535).

Renewing access to a public cloud connection

After a public cloud connection is registered in the Cyber Protect console, Acronis automatically
assigns a free and unique access certificate that enables access to the public cloud connection. The
certificate is valid for one year. When the certificate nears its expiry date, you can renew it.

To renew the access certificate for your public cloud connection

1. In the Cyber Protect console, go to Infrastructure > Public clouds.

2. Select the relevant connection from the list.

Note
The Access status column indicates the current status of the access certificate for each
connection and shows one of two statuses: OK or Expired.

3. In the right pane, click Renew access.

Alternatively, click the Connection tab, and then click Renew in the Creation date row.

534 © Acronis International GmbH, 2003-2024

 When the authentication is successful, access is automatically renewed for one year.

Removing access to a public cloud connection

You should remove access to public cloud connections if you are not backing up workloads to public
clouds.

To remove access to a public cloud connection

Important
You cannot remove a connection if it is currently used for backups to a public cloud.

1. In the Cyber Protect console, go to Infrastructure > Public clouds.

2. Select the connection from the list.
3. In the right pane, click Delete.

Note
You can only remove a connection you added. You can also remove a connection if you are a
Company administrator or Unit administrator, or were assigned the role of Cyber administrator
or Administrator in the Cyber Protection service.

4. In the displayed confirmation message, click Delete.

535 © Acronis International GmbH, 2003-2024

Protecting Microsoft applications

Protecting Microsoft SQL Server and Microsoft Exchange Server

Note
Microsoft SQL backup is supported only for databases running on NFTS, REFS, and FAT32 file
systems. ExFat is not supported.

There are two methods of protecting Microsoft applications:

l Database backup
This is a file-level backup of the databases and the metadata associated with them. The
databases can be recovered to a live application or as files.
l Application-aware backup
This is a disk-level backup that also collects the applications' metadata. This metadata enables
browsing and recovery of the application data without recovering the entire disk or volume. The
disk or volume can also be recovered as a whole. This means that a single solution and a single
protection plan can be used for both disaster recovery and data protection purposes.

For Microsoft Exchange Server, you can opt for Mailbox backup. This is a backup of individual
mailboxes via the Exchange Web Services protocol. The mailboxes or mailbox items can be
recovered to a live Exchange Server or to Microsoft 365. Mailbox backup is supported for Microsoft
Exchange Server 2010 Service Pack 1 (SP1) and later.

Protecting Microsoft SharePoint

A Microsoft SharePoint farm consists of front-end servers that run SharePoint services, database
servers that run Microsoft SQL Server, and (optionally) application servers that offload some
SharePoint services from the front-end servers. Some front-end and application servers may be
identical to each other.

To protect an entire SharePoint farm:

l Back up all of the database servers with application-aware backup.

l Back up all of the unique front-end servers and application servers with usual disk-level backup.

The backups of all servers should be done on the same schedule.

To protect only the content, you can back up the content databases separately.

Protecting a domain controller

A machine running Active Directory Domain Services can be protected by application-aware backup.
If a domain contains more than one domain controller, and you recover one of them, a
nonauthoritative restore is performed and a USN rollback will not occur after the recovery.

536 © Acronis International GmbH, 2003-2024

Recovering applications
The following table summarizes the available application recovery methods.

From a database backup From an application-aware From a

backup disk
backup

Microsoft SQL Server Databases to a live SQL Server Entire machine Entire
instance machine
Databases to a live SQL Server
Databases as files instance

Databases as files

Microsoft Exchange Databases to a live Exchange Entire machine Entire

Server machine
Databases as files Databases to a live Exchange

Granular recovery to a live Databases as files

Exchange or to Microsoft 365*
Granular recovery to a live
Exchange or to Microsoft 365*

Microsoft SharePoint Databases to a live SQL Server Entire machine Entire

database servers instance machine
Databases to a live SQL Server
Databases as files instance

Granular recovery by using Databases as files

SharePoint Explorer
Granular recovery by using
SharePoint Explorer

Microsoft SharePoint - - Entire

front-end web servers machine

Active Directory - Entire machine -

Domain Services

* Granular recovery is also available from a mailbox backup. Recovery of Exchange data items to
Microsoft 365, and vice versa, is supported on the condition that Agent for Microsoft 365 is installed
locally.

Prerequisites
Before configuring the application backup, ensure that the requirements listed below are met.

To check the VSS writers state, use the vssadmin list writers command.

Common requirements
For Microsoft SQL Server, ensure that:

537 © Acronis International GmbH, 2003-2024

l At least one Microsoft SQL Server instance is started.
l The SQL writer for VSS is turned on.

For Microsoft Exchange Server, ensure that:

l The Microsoft Exchange Information Store service is started.

l Windows PowerShell is installed. For Exchange 2010 or later, the Windows PowerShell version
must be at least 2.0.
l Microsoft .NET Framework is installed.
For Exchange 2007, the Microsoft .NET Framework version must be at least 2.0.
For Exchange 2010 or later, the Microsoft .NET Framework version must be at least 3.5.
l The Exchange writer for VSS is turned on.

Note
Agent for Exchange needs a temporary storage to operate. By default, the temporary files are
located in %ProgramData%\Acronis\Temp. Ensure that you have at least as much free space on the
volume where the %ProgramData% folder is located as 15 percent of an Exchange database size.
Alternatively, you can change the location of the temporary files before creating Exchange backups
as described in Changing Temp Files and Folder Location (40040).

On a domain controller, ensure that:

l The Active Directory writer for VSS is turned on.

When creating a protection plan, ensure that:

l For physical machines and machines with the agent installed inside, the Volume Shadow Copy
Service (VSS) backup option is enabled.
l For virtual machines, the Volume Shadow Copy Service (VSS) for virtual machines backup option
is enabled.

Additional requirements for application-aware backups

When creating a protection plan, ensure that Entire machine is selected for backup. The Sector-by-
sector backup option must be disabled in a protection plan, otherwise it will be impossible to
perform a recovery of application data from such backups. If the plan is executed in the Sector-by-
sector mode due to an automatic switch to this mode, then recovery of application data will also be
impossible.

Requirements for ESXi virtual machines

If the application runs on a virtual machine that is backed up by Agent for VMware, ensure that:

l The virtual machine being backed up meets the requirements for application-consistent backup
and restore listed in the article "Windows Backup Implementations" in the VMware
documentation: https://code.vmware.com/docs/1674/virtual-disk-programming-
guide/doc/vddkBkupVadp.9.6.html.

538 © Acronis International GmbH, 2003-2024

l VMware Tools is installed and up-to-date on the machine.
l User Account Control (UAC) is disabled on the machine. If you do not want to disable UAC, you
must provide the credentials of the built-in domain administrator (DOMAIN\Administrator) when
enabling application backup.
If you do not want to disable UAC, you must provide the credentials of the built-in domain
administrator (DOMAIN\Administrator) when enabling application backup.

Note
Use the built-in domain administrator account that was configured as part of the creation of the
domain. Accounts created later are not supported.

Requirements for Hyper-V virtual machines

If the application runs on a virtual machine that is backed up by Agent for Hyper-V, ensure that:

l The guest operating system is Windows Server 2008 or later.

l For Hyper-V 2008 R2: the guest operating system is Windows Server 2008/2008 R2/2012.
l The virtual machine has no dynamic disks.
l The network connection exists between the Hyper-V host and the guest operating system. This is
required to execute remote WMI queries inside the virtual machine.
l User Account Control (UAC) is disabled on the machine. If you do not want to disable UAC, you
must provide the credentials of the built-in domain administrator (DOMAIN\Administrator) when
enabling application backup.
If you do not want to disable UAC, you must provide the credentials of the built-in domain
administrator (DOMAIN\Administrator) when enabling application backup.

Note
Use the built-in domain administrator account that was configured as part of the creation of the
domain. Accounts created later are not supported.

l The virtual machine configuration matches the following criteria:

o Hyper-V Integration Services is installed and up-to-date. The critical update is
https://support.microsoft.com/en-us/help/3063109/hyper-v-integration-components-update-
for-windows-virtual-machines
o In the virtual machine settings, the Management > Integration Services > Backup (volume
checkpoint) option is enabled.
o For Hyper-V 2012 and later: the virtual machine has no checkpoints.
o For Hyper-V 2012 R2 and later: the virtual machine has a SCSI controller (check Settings >
Hardware).

Database backup
Before backing up databases, ensure that the requirements listed in "Prerequisites" are met.

539 © Acronis International GmbH, 2003-2024

Select the databases as described below, and then specify other settings of the protection plan as
appropriate.

Selecting SQL databases

A backup of an SQL database contains the database files (.mdf, .ndf), log files (.ldf), and other
associated files. The files are backed with the help of the SQL Writer service. The service must be
running at the time that the Volume Shadow Copy Service (VSS) requests a backup or recovery.

The SQL transaction logs are truncated after each successful backup. SQL log truncation can be
disabled in the protection plan options.

To select SQL databases

1. Click Devices > Microsoft SQL.

The software shows the tree of SQL Server Always On Availability Groups (AAG), machines
running Microsoft SQL Server, SQL Server instances, and databases.
2. Browse to the data that you want to back up.
Expand the tree nodes or double-click items in the list to the right of the tree.
3. Select the data that you want to back up. You can select AAGs, machines running SQL Server,
SQL Server instances, or individual databases.
l If you select an AAG, all databases that are included into the selected AAG will be backed up.
For more information about backing up AAGs or individual AAG databases, refer to
"Protecting Always On Availability Groups (AAG)".
l If you select a machine running an SQL Server, all databases that are attached to all SQL
Server instances running on the selected machine will be backed up.
l If you select a SQL Server instance, all databases that are attached to the selected instance will
be backed up.
l If you select databases directly, only the selected databases will be backed up.
4. Click Protect. If prompted, provide credentials to access the SQL Server data.
If you use Windows authentication, the account must be a member of the Backup Operators or
Administrators group on the machine and a member of the sysadmin role on each of the
instances that you are going to back up.
If you use SQL Server authentication, the account must be a member of the sysadmin role on
each of the instances that you are going to back up.

Selecting Exchange Server data

The following table summarizes the Microsoft Exchange Server data that you can select for backup
and the minimal user rights required to back up the data.

Exchange version Data items User rights

2007 Storage groups Membership in the Exchange Organization

Administrators role group

540 © Acronis International GmbH, 2003-2024

 2010/2013/2016/2019 Databases, Database Membership in the Server Management role
Availability Groups (DAG) group.

A full backup contains all of the selected Exchange Server data.

An incremental backup contains the changed blocks of the database files, the checkpoint files, and a
small number of the log files that are more recent than the corresponding database checkpoint.
Because changes to the database files are included in the backup, there is no need to back up all the
transaction log records since the previous backup. Only the log that is more recent than the
checkpoint needs to be replayed after a recovery. This makes for faster recovery and ensures
successful database backup, even with circular logging enabled.

The transaction log files are truncated after each successful backup.

To select Exchange Server data

1. Click Devices > Microsoft Exchange.

The software shows the tree of Exchange Server Database Availability Groups (DAG), machines
running Microsoft Exchange Server, and Exchange Server databases. If you configured Agent for
Exchange as described in "Mailbox backup" (p. 547), mailboxes are also shown in this tree.
2. Browse to the data that you want to back up.
Expand the tree nodes or double-click items in the list to the right of the tree.
3. Select the data that you want to back up.
l If you select a DAG, one copy of each clustered database will be backed up. For more
information about backing up DAGs, refer to "Protecting Database Availability Groups (DAG)"
(p. 543).
l If you select a machine running Microsoft Exchange Server, all databases that are mounted to
the Exchange Server running on the selected machine will be backed up.
l If you select databases directly, only the selected databases will be backed up.
l If you configured Agent for Exchange as described in "Mailbox backup" (p. 547), you can select
mailboxes for backup.
If your selection includes multiple databases, they are processed two at a time. When the backup
of the first group finishes, the backup of the next group will begin.
4. If prompted, provide the credentials to access the data.
5. Click Protect.

Protecting Always On Availability Groups (AAG)

Note
This feature is available with the Advanced Backup pack.

SQL Server high-availability solutions overview

The Windows Server Failover Clustering (WSFC) functionality enables you to configure a highly
available SQL Server through redundancy at the instance level (Failover Cluster Instance, FCI) or at

541 © Acronis International GmbH, 2003-2024

the database level (AlwaysOn Availability Group, AAG). You can also combine both methods.

In a Failover Cluster Instance, SQL databases are located on a shared storage. This storage can only
be accessed from the active cluster node. If the active node fails, a failover occurs and a different
node becomes active.

In an availability group, each database replica resides on a different node. If the primary replica
becomes not available, a secondary replica residing on a different node is assigned the primary role.

Thus, the clusters are already serving as a disaster recovery solution themselves. However, there
might be cases when the clusters cannot provide data protection: for example, in case of a database
logical corruption, or when the entire cluster is down. Also cluster solutions do not protect from
harmful content changes, as they usually immediately replicate to all cluster nodes.

Supported cluster configurations

This backup software supports only the Always On Availability Group (AAG) for SQL Server 2012 or
later. Other cluster configurations, such as Failover Cluster Instances, database mirroring, and log
shipping are not supported.

How many agents are required for cluster data backup and recovery?
For successful data backup and recovery of a cluster Agent for SQL has to be installed on each node
of the WSFC cluster.

Backing up databases included in an AAG

1. Install Agent for SQL on each node of the WSFC cluster.
2. Select the AAG to backup as described in "Selecting SQL databases".
You must select the AAG itself to backup all databases of the AAG. To backup a set of databases,
define this set of databases in all nodes of the AAG.

Warning!
The database set must be exactly the same in all nodes. If even one set is different, or not
defined on all nodes, the cluster backup will not work correctly.

3. Configure the "Cluster backup mode" backup option.

Recovery of databases included in an AAG

1. Select the databases that you want to recover, and then select the recovery point from which
you want to recover the databases.
When you select a clustered database under Devices > Microsoft SQL > Databases, and then
click Recover, the software shows only the recovery points that correspond to the times when
the selected copy of the database was backed up.
The easiest way to view all recovery points of a clustered database is to select the backup of the
entire AAG on the Backup storage tab. The names of AAG backups are based on the following
template: <AAG name> - <protection plan name> and have a special icon.

542 © Acronis International GmbH, 2003-2024

2. To configure recovery, follow the steps described in "Recovering SQL databases", starting from
step 5.
The software automatically defines a cluster node to which the data will be recovered. The
node's name is displayed in the Recover to field. You can manually change the target node.

Important
A database that is included in an Always On Availability Group cannot be overwritten during a
recovery because Microsoft SQL Server prohibits this. You need to exclude the target database
from the AAG before the recovery. Or, just recover the database as a new non-AAG one. When
the recovery is completed, you can reconstruct the original AAG configuration.

Protecting Database Availability Groups (DAG)

Note
This feature is available with the Advanced Backup pack.

Exchange Server clusters overview

The main idea of Exchange clusters is to provide high database availability with fast failover and no
data loss. Usually, it is achieved by having one or more copies of databases or storage groups on the
members of the cluster (cluster nodes). If the cluster node hosting the active database copy or the
active database copy itself fails, the other node hosting the passive copy automatically takes over
the operations of the failed node and provides access to Exchange services with minimal downtime.
Thus, the clusters are already serving as a disaster recovery solution themselves.

However, there might be cases when failover cluster solutions cannot provide data protection: for
example, in case of a database logical corruption, or when a particular database in a cluster has no
copy (replica), or when the entire cluster is down. Also cluster solutions do not protect from harmful
content changes, as they usually immediately replicate to all cluster nodes.

Cluster-aware backup
With cluster-aware backup, you back up only one copy of the clustered data. If the data changes its
location within the cluster (due to a switchover or a failover), the software will track all relocations of
this data and safely back it up.

Supported cluster configurations

Cluster-aware backup is supported only for Database Availability Group (DAG) in Exchange Server
2010 or later. Other cluster configurations, such as Single Copy Cluster (SCC) and Cluster Continuous
Replication (CCR) for Exchange 2007, are not supported.

DAG is a group of up to 16 Exchange Mailbox servers. Any node can host a copy of mailbox
database from any other node. Each node can host passive and active database copies. Up to 16
copies of each database can be created.

543 © Acronis International GmbH, 2003-2024

How many agents are required for cluster-aware backup and recovery?
For successful backup and recovery of clustered databases, Agent for Exchange has to be installed
on each node of the Exchange cluster.

Note
After you install the agent on one of the nodes, the Cyber Protect console displays the DAG and its
nodes under Devices > Microsoft Exchange > Databases. To install Agents for Exchange on the
rest of the nodes, select the DAG, click Details, and then click Install agent next to each of the
nodes.

Backing up the Exchange cluster data

1. When creating a protection plan, select the DAG as described in "Selecting Exchange Server data"
(p. 540).
2. Configure the "Cluster backup mode" (p. 435) backup option.
3. Specify other settings of the protection plan as appropriate.

Important
For cluster-aware backup, ensure to select the DAG itself. If you select individual nodes or
databases inside the DAG, only the selected items will be backed up and the Cluster backup mode
option will be ignored.

Recovering the Exchange cluster data

1. Select the recovery point for the database that you want to recover. Selecting an entire cluster
for recovery is not possible.
When you select a copy of a clustered database under Devices > Microsoft Exchange >
Databases > <cluster name> > <node name> and click Recover, the software shows only the
recovery points that correspond to the times when this copy was backed up.

544 © Acronis International GmbH, 2003-2024

 The easiest way to view all recovery points of a clustered database is to select its backup on the
Backup storage tab.
2. Follow the steps described in "Recovering Exchange databases" (p. 557), starting from step 5.
The software automatically defines a cluster node to which the data will be recovered. The
node's name is displayed in the Recover to field. You can manually change the target node.

Application-aware backup
Application-aware disk-level backup is available for physical machines, ESXi virtual machines, and
Hyper-V virtual machines.

When you back up a machine running Microsoft SQL Server, Microsoft Exchange Server, or Active
Directory Domain Services, enable Application backup for additional protection of these
applications' data.

Why use application-aware backup?

By using application-aware backup, you ensure that:

l The applications are backed up in a consistent state and thus will be available immediately after
the machine is recovered.
l You can recover the SQL and Exchange databases, mailboxes, and mailbox items without
recovering the entire machine.
l The SQL transaction logs are truncated after each successful backup. SQL log truncation can be
disabled in the protection plan options. The Exchange transaction logs are truncated on virtual
machines only. You can enable the VSS full backup option if you want to truncate Exchange
transaction logs on a physical machine.
l If a domain contains more than one domain controller, and you recover one of them, a
nonauthoritative restore is performed and a USN rollback will not occur after the recovery.

What do I need to use application-aware backup?

On a physical machine, Agent for SQL and/or Agent for Exchange must be installed, in addition to
Agent for Windows.

On a virtual machine, no agent installation is required; it is presumed that the machine is backed up
by Agent for VMware (Windows) or Agent for Hyper-V.

545 © Acronis International GmbH, 2003-2024

Note
For Hyper-V and VMware ESXi virtual machines that are running Windows Server 2022, application-
aware backup is not supported in the agentless mode – that is, when the backup is performed by
Agent for Hyper-V or Agent for VMware, respectively. To protect Microsoft applications on these
machines, install Agent for Windows inside the guest operating system.

Agent for VMware (Virtual Appliance) can create application-aware backups, but cannot recover
application data from them. To recover application data from backups created by this agent, you
need Agent for VMware (Windows), Agent for SQL, or Agent for Exchange on a machine that has
access to the location where the backups are stored. When configuring recovery of application data,
select the recovery point on the Backup storage tab, and then select this machine in Machine to
browse from.

Other requirements are listed in the "Prerequisites" and "Required user rights" sections.

Note
Application-aware backups of Hyper-V virtual machines may fail with the error "WMI 'ExecQuery'
failed executing query." or "Failed to create a new process via WMI" if the backups are performed
on a host under high load, due to no or delayed response from Windows Management
Instrumentation. Retry these backups in a time slot when the load on the host is lower.

Required user rights for application-aware backups

An application-aware backup contains metadata of VSS-aware applications that are present on the
disk. To access this metadata, the agent needs an account with the appropriate rights, which are
listed below. You are prompted to specify this account when enabling application backup.

l For SQL Server:

The account must be a member of the Backup Operators or Administrators group on the
machine and a member of the sysadmin role on each of the instances that you are going to back
up.

Note
Only Windows authentication is supported.

l For Exchange Server:

Exchange 2007: The account must be a member of the Administrators group on the machine,
and a member of the Exchange Organization Administrators role group.
Exchange 2010 and later: The account must be a member of the Administrators group on the
machine, and a member of the Organization Management role group.
l For Active Directory:
The account must be a domain administrator.

546 © Acronis International GmbH, 2003-2024

Additional requirement for virtual machines
If the application runs on a virtual machine that is backed up by Agent for VMware or Agent for
Hyper-V, ensure that User Account Control (UAC) is disabled on the machine.

If you do not want to disable UAC, you must provide the credentials of the built-in domain
administrator (DOMAIN\Administrator) when enabling application backup.

Note
Use the built-in domain administrator account that was configured as part of the creation of the
domain. Accounts created later are not supported.

Additional requirements for machines running Windows

For all Windows versions, you must disable the User Account Control (UAC) policies to allow
application-aware backups.

If you do not want to disable UAC, you must provide the credentials of the built-in domain
administrator (DOMAIN\Administrator) when enabling application backup.

Note
Use the built-in domain administrator account that was configured as part of the creation of the
domain. Accounts created later are not supported.

To disable the UAC policies in Windows

1. In the Registry Editor, locate the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System
2. Change the EnableLUA value to 0.
3. Restart the machine.

Mailbox backup
Mailbox backup is supported for Microsoft Exchange Server 2010 Service Pack 1 (SP1) and later.

Mailbox backup is available if at least one Agent for Exchange is registered on the management
server. The agent must be installed on a machine that belongs to the same Active Directory forest as
Microsoft Exchange Server.

Before backing up mailboxes, you must connect Agent for Exchange to the machine running the
Client Access server role (CAS) of Microsoft Exchange Server. In Exchange 2016 and later, the CAS
role is not available as a separate installation option. It is automatically installed as part of the
Mailbox server role. Thus, you can connect the agent to any server running the Mailbox role.

547 © Acronis International GmbH, 2003-2024

 Note
You can recover mailboxes and mailbox items also from database backups and application-aware
backups. For more information, see "Recovering Exchange mailboxes and mailbox items" (p. 559).
With database backups and application-aware backups you cannot create protection plans for
individual mailboxes.

To connect Agent for Exchange to CAS

1. Click Devices > Add.

2. Click Microsoft Exchange Server.
3. Click Exchange mailboxes.
If no Agent for Exchange is registered on the management server, the software suggests that you
install the agent. After the installation, repeat this procedure from step 1.
4. [Optional] If multiple Agents for Exchange are registered on the management server, click Agent,
and then change the agent that will perform the backup.
5. In Client Access server, specify the fully qualified domain name (FQDN) of the machine where
the Client Access role of Microsoft Exchange Server is enabled.
In Exchange 2016 and later, the Client Access services are automatically installed as part of the
Mailbox server role. Thus, you can specify any server running the Mailbox role. We refer to this
server as CAS later in this section.
6. In Authentication type, select the authentication type that is used by the CAS. You can select
Kerberos (default) or Basic.
7. [Only for basic authentication] Select which protocol will be used. You can select HTTPS (default)
or HTTP.
8. [Only for basic authentication with the HTTPS protocol] If the CAS uses an SSL certificate that was
obtained from a certification authority, and you want the software to check the certificate when
connecting to the CAS, select the Check SSL certificate check box. Otherwise, skip this step.
9. Provide the credentials of an account that will be used to access the CAS. The requirements for
this account are listed in "Required user rights".
10. Click Add.

As a result, the mailboxes appear under Devices > Microsoft Exchange > Mailboxes.

Selecting Exchange Server mailboxes

Select the mailboxes as described below, and then specify other settings of the protection plan as
appropriate.

To select Exchange mailboxes

1. Click Devices > Microsoft Exchange.

The software shows the tree of Exchange databases and mailboxes.
2. Click Mailboxes, and then select the mailboxes that you want to back up.
3. Click Protect.

548 © Acronis International GmbH, 2003-2024

Required user rights
To access mailboxes, Agent for Exchange needs an account with the appropriate rights. You are
prompted to specify this account when configuring various operations with mailboxes.

Membership of the account in the Organization Management role group enables access to any
mailbox, including mailboxes that will be created in the future.

The minimum required user rights are as follows:

l The account must be a member of the Server Management and Recipient Management role
groups.
l The account must have the ApplicationImpersonation management role enabled for all users
or groups of users whose mailboxes the agent will access.
For information about configuring the ApplicationImpersonation management role, refer to the
following Microsoft knowledge base article: https://msdn.microsoft.com/en-
us/library/office/dn722376.aspx.

Recovering SQL databases

You can recover SQL databases from database backups and application-aware backups. For more
information about the difference between the two backup types, refer to "Protecting Microsoft SQL
Server and Microsoft Exchange Server" (p. 536).

You can recover SQL databases to the original instance, to a different instance on the original
machine, or to an instance on a non-original machine. When you perform recovery to a non-original
machine, Agent for SQL must be installed on the target machine.

Also, you can recover databases as files.

If you use Windows authentication for the SQL instance, you must provide credentials for an
account that is a member of the Backup Operators or Administrators group on the machine and
a member of the sysadmin role on the target instance. If you use SQL Server authentication, you
must provide credentials for an account that is a member of the sysadmin role on the target
instance.

System databases are recovered as user databases, with some distinctions. To learn more about
these distinctions, refer to "Recovering system databases" (p. 556).

During a recovery, you can check the progress of the operation in the Cyber Protect console, on the
Monitoring > Activities tab.

Recovering SQL databases to the original machine

You can recover SQL databases to their original instance, to a different instance on the original
machine, or to an instance on a non-original target machine.

To recover SQL databases to the original machine

From a database backup

549 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Devices > Microsoft SQL.
2. Select the SQL Server instance or click the instance name to select specific databases that you
want to recover, and then click Recovery.
If the machine is offline, the recovery points are not displayed. To recover data to a non-original
machine, refer to "Recovering SQL databases to a non-original machine" (p. 551).
3. Select a recovery point.
The recovery points are filtered by location.
4. Click Recover > Databases to an instance.
By default, the instance and the databases are recovered to the original ones. You can also
recover an original database as a new database.
5. [When recovering to a non-original instance on the same machine] Click Target SQL Server
instance, select the target instance, and then click Done.
6. [When recovering a database as a new database] Click the database name, and then in Recover
to, select New database.
l Specify the new database name.
l Specify the new database path.
l Specify the log path.
7. [Optional] [Not available when recovering a database as a new database] To change the
database state after recovery, click the database name, choose one of the following states, and
then click Done.
l Ready to use (RESTORE WITH RECOVERY) (default)
After the recovery completes, the database will be ready for use. Users will have full access to
it. The software will roll back all uncommitted transactions of the recovered database that are
stored in the transaction logs. You will not be able to recover additional transaction logs from
the native Microsoft SQL backups.
l Non-operational (RESTORE WITH NORECOVERY)
After the recovery completes, the database will be non-operational. Users will have no access
to it. The software will keep all uncommitted transactions of the recovered database. You will
be able to recover additional transaction logs from the native Microsoft SQL backups and thus
reach the necessary recovery point.
l Read-only (RESTORE WITH STANDBY)
After the recovery completes, users will have read-only access to the database. The software
will undo any uncommitted transactions. However, it will save the undo actions in a temporary
standby file so that the recovery effects can be reverted.
This value is primarily used to detect the point in time when a SQL Server error occurred.
8. Click Start recovery.

From an application-aware backup

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the machine that originally contained the data that you want to recover, and then click
Recovery.

550 © Acronis International GmbH, 2003-2024

 If the machine is offline, the recovery points are not displayed. To recover data to a non-original
machine, refer to "Recovering SQL databases to a non-original machine" (p. 551).
3. Select a recovery point.
The recovery points are filtered by location.
4. Click Recover > SQL databases.
5. Select the SQL Server instance or click the instance name to select specific databases that you
want to recover, and then click Recover.
By default, the instance and the databases are recovered to the original ones. You can also
recover an original database as a new database.
6. [When recovering to a non-original instance on the same machine] Click Target SQL Server
instance, select the target instance, and then click Done.
7. [When recovering a database as a new database] Click the database name, and then in Recover
to, select New database.
l Specify the new database name.
l Specify the new database path.
l Specify the log path.
8. [Optional] [Not available when recovering a database as a new database] To change the
database state after recovery, click the database name, choose one of the following states, and
then click Done.
l Ready to use (RESTORE WITH RECOVERY) (default)
After the recovery completes, the database will be ready for use. Users will have full access to
it. The software will roll back all uncommitted transactions of the recovered database that are
stored in the transaction logs. You will not be able to recover additional transaction logs from
the native Microsoft SQL backups.
l Non-operational (RESTORE WITH NORECOVERY)
After the recovery completes, the database will be non-operational. Users will have no access
to it. The software will keep all uncommitted transactions of the recovered database. You will
be able to recover additional transaction logs from the native Microsoft SQL backups and thus
reach the necessary recovery point.
l Read-only (RESTORE WITH STANDBY)
After the recovery completes, users will have read-only access to the database. The software
will undo any uncommitted transactions. However, it will save the undo actions in a temporary
standby file so that the recovery effects can be reverted.
This value is primarily used to detect the point in time when a SQL Server error occurred.
9. Click Start recovery.

Recovering SQL databases to a non-original machine

You can recover both application-aware backups and database backups to SQL Server instances on
non-original target machines on which Agent for SQL is installed. The backups must be located on
the cloud storage or on a shared storage that the target machine can access.

551 © Acronis International GmbH, 2003-2024

 The SQL Server version on the target machine must be the same as the version on the source
machine, or newer.

To recover SQL databases to a non-original machine

From Backup storage

This procedure applies to application-aware backups and database backups.

1. In the Cyber Protect console, go to Backup storage.

2. Select the location of the backup set from which you want to recover data.
3. In Machine to browse from, select the target machine.
This is the machine to which you will recover data. The target machine must be online.

4. Select the backup set, and then in the Actions pane, click Show backups.
Application-aware backup sets and database backup sets have different icons.

5. Select the recovery point from which you want to recover data.
6. [For database backups] Click Recover SQL databases.
7. [For application-aware backups] Click Recover > SQL databases.
8. Select the SQL Server instance or click the instance name to select specific databases that you
want to recover, and then click Recover.
9. [If there is more than one SQL instance on the target machine] Click Target SQL Server
instance, select the target instance, and then click Done.
10. Click the database name, specify the new database path and log path, and then click Done.
You can specify the same path in both fields, for example:

C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\

11. Click Start recovery.

From Devices

This procedure only applies to application-aware backups.

552 © Acronis International GmbH, 2003-2024

 1. In the Cyber Protect console, go to Devices > All devices.
2. Select the machine that originally contained the data that you want to recover, and then click
Recovery.
3. [If the source machine is online] Click More ways to recover.

4. Click Select machine to select the target machine, and then click OK.
This is the machine to which you will recover data. The target machine must be online.
5. Select a recovery point.
The recovery points are filtered by location.
6. Click Recover > SQL databases.
7. Select the SQL Server instance or click the instance name to select specific databases that you
want to recover, and then click Recover.
8. [If there is more than one SQL instance on the target machine] Click Target SQL Server
instance, select the target instance, and then click Done.
9. Click the database name, specify the new database path and log path, and then click Done.
You can specify the same path in both fields, for example:

C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\

10. Click Start recovery.

Recovering SQL databases as files

You can recover databases as files. This option might be useful if you need to extract data for data
mining, audit, or further processing by third-party tools. To learn how to attach the SQL database
files to a SQL Server instance, refer to "Attaching SQL Server databases" (p. 556).

You can recover databases as files to the original machine or to non-original target machines, on
which Agent for SQL is installed. When you recover data to non-original machines, the backups must
be located on the cloud storage or on a shared storage that the target machine can access.

Note
Recovering databases as files is the only recovery method if you use Agent for VMware (Windows).
Recovering databases by using Agent for VMware (Virtual Appliance) is not possible.

To recover SQL databases as files

553 © Acronis International GmbH, 2003-2024

From a database backup

This procedure applies to online source machines.

1. In the Cyber Protect console, go to Devices > Microsoft SQL.

2. Select the databases that you want to recover, and then click Recovery.
3. Select a recovery point.
The recovery points are filtered by location.
4. Click Recover > Databases as files.
5. [When recovering to a non-original machine] In Recover to, select the target machine.
This is the machine to which you will recover data. The target machine must be online.
To change the selection, click the machine name, select another machine, and then click OK.

6. In Path, click Browse, select a local or network folder to save the files to, and then click Done.
7. Click Start recovery.

From an application-aware backup

This procedure applies to online source machines.

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the machine that originally contained the data that you want to recover, and then click
Recovery.
3. Select a recovery point.
The recovery points are filtered by location.
4. Click Recover > SQL databases, select the databases that you want to recover, and then click
Recover as files.
5. [When recovering to a non-original machine] In Recover to, select the target machine.
This is the machine to which you will recover data. The target machine must be online.
To change the selection, click the machine name, select another machine, and then click OK.

554 © Acronis International GmbH, 2003-2024

 6. In Path, click Browse, select a local or network folder to save the files to, and then click Done.
7. Click Start recovery.

From a backup on an offline machine

This procedure applies to application-aware backups and database backups on source machines
that are offline.

1. In the Cyber Protect console, go to Backup storage.

2. Select the location of the backup set from which you want to recover data.
3. In Machine to browse from, select the target machine.
This is the machine to which you will recover data. The target machine must be online.

4. Select the backup set, and then in the Actions pane, click Show backups.
Application-aware backup sets and database backup sets have different icons.

5. Select the recovery point from which you want to recover data.
6. [For database backups] Click Recover SQL databases.
7. [For application-aware backups] Click Recover > SQL databases.
8. Select the SQL Server instance or click the instance name to select specific databases that you
want to recover, and then click Recover as files.
9. In Path, click Browse, select a local or a network folder to save the files to, and then click Done.
10. Click Start recovery.

555 © Acronis International GmbH, 2003-2024

Recovering system databases
All system databases of an instance are recovered at once. When recovering system databases, the
software automatically restarts the destination instance in the single-user mode. After the recovery
completes, the software restarts the instance and recovers other databases (if any).

Other things to consider when recovering system databases:

l System databases can only be recovered to an instance of the same version as the original
instance.
l System databases are always recovered in the "ready to use" state.

Recovering the master database

System databases include the master database. The master database records information about
all databases of the instance. Hence, the master database in a backup contains information about
databases which existed in the instance at the time of the backup. After recovering the master
database, you may need to do the following:

l Databases that have appeared in the instance after the backup was done are not visible by the
instance. To bring these databases back to production, attach them to the instance manually by
using SQL Server Management Studio.
l Databases that have been deleted after the backup was done are displayed as offline in the
instance. Delete these databases by using SQL Server Management Studio.

Attaching SQL Server databases

This section describes how to attach a database in SQL Server by using SQL Server Management
Studio. Only one database can be attached at a time.

Attaching a database requires any of the following permissions: CREATE DATABASE, CREATE ANY
DATABASE, or ALTER ANY DATABASE. Normally, these permissions are granted to the sysadmin
role of the instance.

To attach a database

1. Run Microsoft SQL Server Management Studio.

2. Connect to the required SQL Server instance, and then expand the instance.
3. Right-click Databases and click Attach.
4. Click Add.
5. In the Locate Database Files dialog box, find and select the .mdf file of the database.
6. In the Database Details section, make sure that the rest of database files (.ndf and .ldf files) are
found.
Details. SQL Server database files may not be found automatically, if:
l They are not in the default location, or they are not in the same folder as the primary
database file (.mdf). Solution: Specify the path to the required files manually in the Current

556 © Acronis International GmbH, 2003-2024

 File Path column.
l You have recovered an incomplete set of files that make up the database. Solution: Recover
the missing SQL Server database files from the backup.
7. When all of the files are found, click OK.

Recovering Exchange databases

This section describes recovery from both database backups and application-aware backups.

You can recover Exchange Server data to a live Exchange Server. This may be the original Exchange
Server or an Exchange Server of the same version running on the machine with the same fully
qualified domain name (FQDN). Agent for Exchange must be installed on the target machine.

The following table summarizes the Exchange Server data that you can select for recovery and the
minimal user rights required to recover the data.

Exchange version Data items User rights

2007 Storage Membership in the Exchange Organization Administrators

groups role group.

2010/2013/2016/2019 Databases Membership in the Server Management role group.

Alternatively, you can recover the databases (storage groups) as files. The database files, along with
transaction log files, will be extracted from the backup to a folder that you specify. This can be
useful if you need to extract data for an audit or further processing by third-party tools, or when the
recovery fails for some reason and you are looking for a workaround to mount the databases
manually.

If you use only Agent for VMware (Windows), recovering databases as files is the only available
recovery method. Recovering databases by using Agent for VMware (Virtual Appliance) is not
possible.

We will refer to both databases and storage groups as "databases" throughout the below
procedures.

To recover Exchange databases to a live Exchange Server

1. Do one of the following:

l When recovering from an application-aware backup, under Devices, select the machine that
originally contained the data that you want to recover.
l When recovering from a database backup, click Devices > Microsoft Exchange > Databases,
and then select the databases that you want to recover.
2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Do one of the following:
l [Only when recovering from an application-aware backup] If the backup location is cloud or
shared storage (i.e. other agents can access it), click Select machine, select an online machine

557 © Acronis International GmbH, 2003-2024

 that has Agent for Exchange, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
The machine chosen for browsing in either of the above actions becomes a target machine for
the Exchange data recovery.
4. Do one of the following:
l When recovering from an application-aware backup, click Recover > Exchange databases,
select the databases that you want to recover, and then click Recover.
l When recovering from a database backup, click Recover > Databases to an Exchange
server.
5. By default, the databases are recovered to the original ones. If the original database does not
exist, it will be recreated.
To recover a database as a different one:
a. Click the database name.
b. In Recover to, select New database.
c. Specify the new database name.
d. Specify the new database path and log path. The folder you specify must not contain the
original database and log files.
6. Click Start recovery.

The recovery progress is shown on the Activities tab.

To recover Exchange databases as files

1. Do one of the following:

l When recovering from an application-aware backup, under Devices, select the machine that
originally contained the data that you want to recover.
l When recovering from a database backup, click Devices > Microsoft Exchange > Databases,
and then select the databases that you want to recover.
2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Do one of the following:
l [Only when recovering from an application-aware backup] If the backup location is cloud or
shared storage (i.e. other agents can access it), click Select machine, select an online machine
that has Agent for Exchange or Agent for VMware, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
The machine chosen for browsing in either of the above actions becomes a target machine for
the Exchange data recovery.
4. Do one of the following:
l When recovering from an application-aware backup, click Recover > Exchange databases,
select the databases that you want to recover, and then click Recover as files.
l When recovering from a database backup, click Recover > Databases as files.

558 © Acronis International GmbH, 2003-2024

5. Click Browse, and then select a local or a network folder to save the files to.
6. Click Start recovery.

The recovery progress is shown on the Activities tab.

Mounting Exchange Server databases

After recovering the database files, you can bring the databases online by mounting them. Mounting
is performed by using Exchange Management Console, Exchange System Manager, or Exchange
Management Shell.

The recovered databases will be in a Dirty Shutdown state. A database that is in a Dirty Shutdown
state can be mounted by the system if it is recovered to its original location (that is, information
about the original database is present in Active Directory). When recovering a database to an
alternate location (such as a new database or as the recovery database), the database cannot be
mounted until you bring it to a Clean Shutdown state by using the Eseutil /r <Enn> command.
<Enn> specifies the log file prefix for the database (or storage group that contains the database) into
which you need to apply the transaction log files.

The account you use to attach a database must be delegated an Exchange Server Administrator role
and a local Administrators group for the target server.

For details about how to mount databases, see the following articles:

l Exchange 2010 or later: http://technet.microsoft.com/en-us/library/aa998871.aspx

l Exchange 2007: http://technet.microsoft.com/en-us/library/aa998871(v=EXCHG.80).aspx

Recovering Exchange mailboxes and mailbox items

You can recover Exchange mailboxes and mailbox items from the following backups:

l Database backups
l Application-aware backups
l Mailbox backups

You can recover the following items:

l Mailboxes (except for archive mailboxes)

l Public folders

Note
Available only from database backups. See "Selecting Exchange Server data" (p. 540).

l Public folder items

l Email folders
l Email messages
l Calendar events
l Tasks

559 © Acronis International GmbH, 2003-2024

l Contacts
l Journal entries
l Notes

You can use search to locate the items.

The mailboxes or mailbox items can be recovered to a live Exchange Server or to Microsoft 365.

Recovery to an Exchange Server

Granular recovery can be performed to Microsoft Exchange Server 2010 Service Pack 1 (SP1) and
later. The source backup may contain databases or mailboxes of any supported Exchange version.

Granular recovery can be performed by Agent for Exchange or Agent for VMware (Windows). The
target Exchange Server and the machine running the agent must belong to the same Active
Directory forest.

When a mailbox is recovered to an existing mailbox, the existing items with matching IDs are
overwritten.

Recovery of mailbox items does not overwrite anything. Instead, the full path to a mailbox item is
recreated in the target folder.

Requirements on user accounts

A mailbox being recovered from a backup must have an associated user account in Active Directory.

User mailboxes and their contents can be recovered only if their associated user accounts are
enabled. Shared, room, and equipment mailboxes can be recovered only if their associated user
accounts are disabled.

A mailbox that does not meet the above conditions is skipped during recovery.

If some mailboxes are skipped, the recovery will succeed with warnings. If all mailboxes are skipped,
the recovery will fail.

Recovery to Microsoft 365

Recovery of Exchange data items to Microsoft 365, and vice versa, is supported on the condition that
Agent for Microsoft 365 is installed locally.

Recovery can be performed from backups of Microsoft Exchange Server 2010 and later.

When a mailbox is recovered to an existing Microsoft 365 mailbox, the existing items are kept intact,
and the recovered items are placed next to them.

When recovering a single mailbox, you need to select the target Microsoft 365 mailbox. When
recovering several mailboxes within one recovery operation, the software will try to recover each
mailbox to the mailbox of the user with the same name. If the user is not found, the mailbox is
skipped. If some mailboxes are skipped, the recovery will succeed with warnings. If all mailboxes are
skipped, the recovery will fail.

560 © Acronis International GmbH, 2003-2024

For more information about recovery to Microsoft 365, refer to "Protecting Microsoft 365 data" (p.
573).

Recovering mailboxes
To recover mailboxes from an application-aware backup or a database backup

1. [Only when recovering from a database backup to Microsoft 365] If Agent for Microsoft 365 is
not installed on the machine running Exchange Server that was backed up, do one of the
following:
l If there is not Agent for Microsoft 365 in your organization, install Agent for Microsoft 365 on
the machine that was backed up (or on another machine with the same Microsoft Exchange
Server version).
l If you already have Agent for Microsoft 365 in your organization, copy libraries from the
machine that was backed up (or from another machine with the same Microsoft Exchange
Server version) to the machine with Agent for Microsoft 365, as described in "Copying
Microsoft Exchange libraries".
2. Do one of the following:
l When recovering from an application-aware backup: under Devices, select the machine that
originally contained the data that you want to recover.
l When recovering from a database backup, click Devices > Microsoft Exchange > Databases,
and then select the database that originally contained the data that you want to recover.
3. Click Recovery.
4. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Use other ways to recover:
l [Only when recovering from an application-aware backup] If the backup location is cloud or
shared storage (i.e. other agents can access it), click Select machine, select an online machine
that has Agent for Exchange or Agent for VMware, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
The machine chosen for browsing in either of the above actions will perform the recovery
instead of the original machine that is offline.
5. Click Recover > Exchange mailboxes.
6. Select the mailboxes that you want to recover.
You can search mailboxes by name. Wildcards are not supported.

561 © Acronis International GmbH, 2003-2024

 7. Click Recover.
8. [Only when recovering to Microsoft 365]:
a. In Recover to, select Microsoft 365.
b. [If you selected only one mailbox in step 6] In Target mailbox, specify the target mailbox.
c. Click Start recovery.
Further steps of this procedure are not required.
Click Target machine with Microsoft Exchange Server to select or change the target machine.
This step allows recovery to a machine that is not running Agent for Exchange.
Specify the fully qualified domain name (FQDN) of a machine where the Client Access role (in
Microsoft Exchange Server 2010/2013) or Mailbox role (in Microsoft Exchange Server 2016 or
later) is enabled. The machine must belong to the same Active Directory forest as the machine
that performs the recovery.
9. If prompted, provide the credentials of an account that will be used to access the machine. The
requirements for this account are listed in "Required user rights".
10. [Optional] Click Database to re-create any missing mailboxes to change the automatically
selected database.
11. Click Start recovery.
The recovery progress is shown on the Activities tab.
To recover a mailbox from a mailbox backup

1. Click Devices > Microsoft Exchange > Mailboxes.

2. Select the mailbox to recover, and then click Recovery.
You can search mailboxes by name. Wildcards are not supported.
If the mailbox was deleted, select it on the Backup storage tab, and then click Show backups.
3. Select a recovery point. Note that recovery points are filtered by location.
4. Click Recover > Mailbox.
5. Perform steps 8-11 of the above procedure.

Recovering mailbox items

To recover mailbox items from an application-aware backup or a database backup

1. [Only when recovering from a database backup to Microsoft 365] If Agent for Microsoft 365 is
not installed on the machine running Exchange Server that was backed up, do one of the
following:
l If there is not Agent for Microsoft 365 in your organization, install Agent for Microsoft 365 on
the machine that was backed up (or on another machine with the same Microsoft Exchange
Server version).
l If you already have Agent for Microsoft 365 in your organization, copy libraries from the
machine that was backed up (or from another machine with the same Microsoft Exchange
Server version) to the machine with Agent for Microsoft 365, as described in "Copying
Microsoft Exchange libraries".
2. Do one of the following:

562 © Acronis International GmbH, 2003-2024

 l When recovering from an application-aware backup: under Devices, select the machine that
originally contained the data that you want to recover.
l When recovering from a database backup, click Devices > Microsoft Exchange > Databases,
and then select the database that originally contained the data that you want to recover.
3. Click Recovery.
4. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Use other ways to recover:
l [Only when recovering from an application-aware backup] If the backup location is cloud or
shared storage (i.e. other agents can access it), click Select machine, select an online machine
that has Agent for Exchange or Agent for VMware, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
The machine chosen for browsing in either of the above actions will perform the recovery
instead of the original machine that is offline.
5. Click Recover > Exchange mailboxes.
6. Click the mailbox that originally contained the items that you want to recover.
7. Select the items that you want to recover.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, and date.
l For events: search by title and date.
l For tasks: search by subject and date.
l For contacts: search by name, email address, and phone number.
When an email message is selected, you can click Show content to view its contents, including
attachments.

Note
Click the name of an attached file to download it.

To be able to select folders, click the recover folders icon.

8. Click Recover.
9. To recover to Microsoft 365, select Microsoft 365 in Recover to.
To recover to an Exchange Server, keep the default Microsoft Exchange value in Recover to.

563 © Acronis International GmbH, 2003-2024

 [Only when recovering to an Exchange Server] Click Target machine with Microsoft Exchange
Server to select or change the target machine. This step allows recovery to a machine that is not
running Agent for Exchange.
Specify the fully qualified domain name (FQDN) of a machine where the Client Access role (in
Microsoft Exchange Server 2010/2013) or Mailbox role (in Microsoft Exchange Server 2016 or
later) is enabled. The machine must belong to the same Active Directory forest as the machine
that performs the recovery.
10. If prompted, provide the credentials of an account that will be used to access the machine. The
requirements for this account are listed in "Required user rights".
11. In Target mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original target
machine is selected, you must specify the target mailbox.
12. [Only when recovering email messages] In Target folder, view or change the target folder in the
target mailbox. By default, the Recovered items folder is selected. Due to Microsoft Exchange
limitations, events, tasks, notes, and contacts are restored to their original location regardless of
any different Target folder specified.
13. Click Start recovery.
The recovery progress is shown on the Activities tab.
To recover a mailbox item from a mailbox backup

1. Click Devices > Microsoft Exchange > Mailboxes.

2. Select the mailbox that originally contained the items that you want to recover, and then click
Recovery.
You can search mailboxes by name. Wildcards are not supported.
If the mailbox was deleted, select it on the Backup storage tab, and then click Show backups.
3. Select a recovery point. Note that recovery points are filtered by location.
4. Click Recover > Email messages.
5. Select the items that you want to recover.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, and date.
l For events: search by title and date.
l For tasks: search by subject and date.
l For contacts: search by name, email address, and phone number.
When an email message is selected, you can click Show content to view its contents, including
attachments.

Note
Click the name of an attached file to download it.

When an email message is selected, you can click Send as email to send the message to an
email address. The message is sent from your administrator account's email address.

To be able to select folders, click the recover folders icon:

564 © Acronis International GmbH, 2003-2024

6. Click Recover.
7. Perform steps 9-13 of the above procedure.

Copying Microsoft Exchange Server libraries

When recovering Exchange mailboxes or mailbox items to Microsoft 365, you may need to copy the
following libraries from the machine that was backed up (or from another machine with the same
Microsoft Exchange Server version) to the machine with Agent for Microsoft 365.

Copy the following files, according to the Microsoft Exchange Server version that was backed up.

Microsoft Exchange Server Libraries Default location

version

Microsoft Exchange Server 2010 ese.dll %ProgramFiles%\Microsoft\Exchange

Server\V14\bin
esebcli2.dll

store.exe

Microsoft Exchange Server 2013 ese.dll %ProgramFiles%\Microsoft\Exchange

Server\V15\bin

msvcr110.dll %WINDIR%\system32

Microsoft Exchange Server 2016, ese.dll %ProgramFiles%\Microsoft\Exchange

2019 Server\V15\bin

msvcr110.dll %WINDIR%\system32

msvcp110.dll

The libraries should be placed in the folder %ProgramData%\Acronis\ese. If this folder does not exist,
create it manually.

Changing the SQL Server or Exchange Server access credentials

You can change access credentials for SQL Server or Exchange Server without re-installing the agent.

To change the SQL Server or Exchange Server access credentials

1. Click Devices, and then click Microsoft SQL or Microsoft Exchange.

2. Select the Always On Availability Group, Database Availability Group, SQL Server instance, or
Exchange Server for which you want to change the access credentials.
3. Click Specify credentials.
4. Specify the new access credentials, and then click OK.

To change the Exchange Server access credentials for mailbox backup

1. Click Devices > Microsoft Exchange, and then expand Mailboxes.

2. Select the Exchange Server for which you want to change the access credentials.
3. Click Settings.

565 © Acronis International GmbH, 2003-2024

4. Under Exchange administrator account, specify the new access credentials, and then click
Save.

Protecting mobile devices

The Cyber Protect app allows you to back up your mobile data to the Cloud storage and then
recover it in case of loss or corruption. Note that backup to the cloud storage requires an account
and the Cloud subscription.

Supported mobile devices

You can install the Cyber Protect app on a mobile device that runs one of the following operating
systems:

l iOS 14 to iOS 16 (iPhone, iPod, iPad)

l Android 9 to Android 13

What you can back up

l Contacts (name, phone number, and email)
l Photos (the original size and format of your photos are preserved)
l Videos
l Calendars
l Reminders (only on iOS devices)

What you need to know

l You can back up the data only to the cloud storage.
l Any time you open the app, you will see the summary of data changes and can start a backup
manually.
l The Continuous backup functionality is enabled by default. If this setting is turned on, the Cyber
Protect app automatically detects new data on the fly and uploads it to the Cloud.
l The Use Wi-Fi only option is enabled by default in the app settings. If this setting is turned on,
the Cyber Protect app will back up your data only when a Wi-Fi connection is available. If the Wi-Fi
connection is lost, a backup process does not start. For the app to use cellular connection as well,
turn this option off.
l The battery optimization on your device might prevent the Cyber Protect app from proper
operation. To run backups on time, you should stop the battery optimization for the app.
l You have two ways to save energy:
o The Back up while charging functionality which is disabled by default. If this setting is turned
on, the Cyber Protect app will back up your data only when your device is connected to a
power source. When the device is disconnected from a power source during a continuous
backup process, the backup is paused.

566 © Acronis International GmbH, 2003-2024

 o The Save power mode which is enabled by default. If this setting is turned on, the Cyber
Protect app will back up your data only when your device battery is not low. When the device
battery gets low, the continuous backup is paused.
l You can access the backed-up data from any mobile device registered under your account. This
helps you transfer the data from an old mobile device to a new one. Contacts and photos from an
Android device can be recovered to an iOS device and vice versa. You can also download a photo,
video, or contact to any device by using the Cyber Protect console.
l The data backed up from mobile devices registered under your account is available only under
this account. Nobody else can view or recover your data.
l In the Cyber Protect app, you can recover only the latest data versions. If you need to recover
from a specific backup version, use the Cyber Protect console on either a tablet or a computer.
l Retention rules are not applied to backups of mobile devices.
l [Only for Android devices] If an SD card is present during a backup, the data stored on this card is
also backed up. The data will be recovered to an SD card, to the folder Recovered by Backup if it
is present during recovery, or the app will ask for a different location to recover the data to.

Where to get the Cyber Protect app

Depending on your mobile device, install the app from the App Store or Google Play.

How to start backing up your data

1. Open the app.
2. Sign in with your account.
3. Tap Set up to create your backup. Note that this button occurs only when you have no backup of
your mobile device.
4. Select the data categories that you want to back up. By default, all categories are selected.
5. [optional step] Enable Encrypt Backup to protect your backup by encryption. In this case, you
will need to also:
a. Enter an encryption password twice.

Note
Make sure you remember the password, because a forgotten password can never be
restored or changed.

b. Tap Encrypt.
6. Tap Back up.
7. Allow the app access to your personal data. If you deny access to some data categories, they will
not be backed up.

The backup starts.

567 © Acronis International GmbH, 2003-2024

How to recover data to a mobile device

Warning!
To recover mobile data, you must use the end-user account.

1. Open the Cyber Protect app.

2. Tap Browse.
3. Tap the device name.
4. Do one of the following:
l To recover all of the backed-up data, tap Recover all. No more actions are required.
l To recover one or more data categories, tap Select, and then tap the check boxes for the
required data categories. Tap Recover. No more actions are required.
l To recover one or more data items belonging to the same data category, tap the data
category. Proceed to further steps.
5. Do one of the following:
l To recover a single data item, tap it.
l To recover several data items, tap Select, and then tap the check boxes for the required data
items.
6. Tap Recover.

How to review data via the Cyber Protect console

1. On a computer, open a browser and type the Cyber Protect console URL.
2. Sign in with your account.
3. In All devices, click Recover under your mobile device name.
4. Do any of the following:
l To download all photos, videos, contacts, calendars, or reminders, select the respective data
category. Click Download.

568 © Acronis International GmbH, 2003-2024

 l To download individual photos, videos, contacts, calendars, or reminders, click the respective
data category name, and then select the check boxes for the required data items. Click
Download.

l To preview a photo, or a contact, click the respective data category name, and then click the
required data item.

Protecting Hosted Exchange data

What items can be backed up?

You can back up user mailboxes, shared mailboxes, and group mailboxes. Optionally, you can
choose to back up the archive mailboxes (In-Place Archive) of the selected mailboxes.

569 © Acronis International GmbH, 2003-2024

What items can be recovered?
The following items can be recovered from a mailbox backup:

l Mailboxes
l Email folders
l Email messages
l Calendar events
l Tasks
l Contacts
l Journal entries
l Notes

You can use search to locate the items.

When recovering mailboxes, mailbox items, public folders, and public folder items, you can select
whether to overwrite the items in the target location.

When a mailbox is recovered to an existing mailbox, the existing items with matching IDs are
overwritten.

Recovery of mailbox items does not overwrite anything. Instead, the full path to a mailbox item is
recreated in the target folder.

Selecting Exchange Online mailboxes

Select the mailboxes as described below, and then specify other settings of the protection plan as
appropriate.

To select Exchange Online mailboxes

1. Click Devices > Hosted Exchange.

2. If multiple Hosted Exchange organizations were added to the Cyber Protection service, select the
organization whose users' data you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up the mailboxes of all users and all shared mailboxes (including mailboxes that will
be created in the future), expand the Users node, select All users, and then click Group
backup.
l To back up individual user or shared mailboxes, expand the Users node, select All users,
select the users whose mailboxes you want to back up, and then click Backup.
l To back up all group mailboxes (including mailboxes of groups that will be created in the
future), expand the Groups node, select All groups, and then click Group backup.
l To back up individual group mailboxes, expand the Groups node, select All groups, select the
groups whose mailboxes you want to back up, and then click Backup.

570 © Acronis International GmbH, 2003-2024

 Recovering mailboxes and mailbox items

Recovering mailboxes
1. Click Devices > Hosted Exchange.
2. If multiple Hosted Exchange organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Do one of the following:
l To recover a user mailbox, expand the Users node, select All users, select the user whose
mailbox you want to recover, and then click Recovery.
l To recover a shared mailbox, expand the Users node, select All users, select the shared
mailbox that you want to recover, and then click Recovery.
l To recover a group mailbox, expand the Groups node, select All groups, select the group
whose mailbox you want to recover, and then click Recovery.
l If the user, group, or the shared mailbox was deleted, select the item in the Cloud
applications backups section of the Backup storage tab, and then click Show backups.
You can search users and groups by name. Wildcards are not supported.
4. Select a recovery point.
5. Click Recover > Entire mailbox.
6. If multiple Hosted Exchange organizations are added to the Cyber Protection service, click
Hosted Exchange organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
7. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
8. Click Start recovery.
9. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
10. Click Proceed to confirm your decision.

Recovering mailbox items

1. Click Devices > Hosted Exchange.
2. If multiple Hosted Exchange organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Do one of the following:
l To recover items from a user mailbox, expand the Users node, select All users, select the
user whose mailbox originally contained the items that you want to recover, and then click
Recovery.

571 © Acronis International GmbH, 2003-2024

 l To recover items from a shared mailbox, expand the Users node, select All users, select the
shared mailbox that originally contained the items that you want to recover, and then click
Recovery.
l To recover items from a group mailbox, expand the Groups node, select All groups, select the
group whose mailbox originally contained the items that you want to recover, and then click
Recovery.
l If the user, group, or the shared mailbox was deleted, select the item in the Cloud
applications backups section of the Backup storage tab, and then click Show backups.
You can search users and groups by name. Wildcards are not supported.
4. Select a recovery point.
5. Click Recover > Email messages.
6. Browse to the required folder or use search to obtain the list of the required items.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, attachment name, and date.
l For events: search by title and date.
l For tasks: search by subject and date.
l For contacts: search by name, email address, and phone number.
7. Select the items that you want to recover. To be able to select folders, click the "recover folders"

icon:
Additionally, you can do any of the following:
l When an item is selected, click Show content to view its contents, including
attachments. Click the name of an attached file to download it.
l When an email message or a calendar item is selected, click Send as email to send the item
to the specified email addresses. You can select the sender and write a text to be added to the
forwarded item.
l Only if the backup is not encrypted, you used search, and selected a single item in the search
results: click Show versions to select the item version to recover. You can select any backed-
up version, earlier or later than the selected recovery point.
8. Click Recover.
9. If multiple Hosted Exchange organizations were added to the Cyber Protection service, click
Hosted Exchange organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
10. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
11. [Only when recovering to a user or a shared mailbox] In Path, view or change the target folder in
the target mailbox. By default, the Recovered items folder is selected.
Group mailbox items are always recovered to the Inbox folder.
12. Click Start recovery.

572 © Acronis International GmbH, 2003-2024

13. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
14. Click Proceed to confirm your decision.

Protecting Microsoft 365 data

Why back up Microsoft 365 data?

Even though Microsoft 365 is a set of cloud services, regular backups provide an additional layer of
protection from user errors and intentional malicious actions. You can recover deleted items from a
backup even after the Microsoft 365 retention period has expired. Also, you can keep a local copy of
the Exchange Online mailboxes if it is required for regulatory compliance.

Backed-up data is automatically compressed and it uses less space on the backup location than on
its original location. The compression level for cloud-to-cloud backups is fixed and corresponds to
the Normal level of non-cloud-to-cloud backups. For more information about these levels, refer to
"Compression level" (p. 436).

Cloud agent and local agent

For Microsoft 365 workloads, two agents are available:

l Cloud agent
The cloud agent provides extended backup functionality, which is directly accessible in the Cyber
Protect console. No installation is required. For more information, see "Using the cloud Agent for
Microsoft 365" (p. 582).
l Local agent
The local agent only provides backup of Exchange online mailboxes. This agent must be installed
on a Windows machine that is connected to the Internet. For more information, see "Using the
locally installed Agent for Office 365" (p. 578).

Azure Information Protection (AIP) is supported with both agents.

Note
For tenants in the Compliance mode, only the local agent is available. These tenants can back up
only Microsoft 365 mailboxes. They cannot use the extended functionality provided by the cloud
agent.

The following table summarizes the functionality of the agents.

Local agent Cloud agent

Data items that can be Exchange Online: user l Exchange Online:

backed up mailboxes and shared mailboxes o user mailboxes and shared

573 © Acronis International GmbH, 2003-2024

 Local agent Cloud agent

(including mailboxes of users on mailboxes (including

a Kiosk plan and mailboxes on mailboxes of users on a
litigation hold) Kiosk plan and mailboxes
on litigation hold)
o group mailboxes
o public folders
l OneDrive: user files and
folders
l SharePoint Online:
o classic site collections

o group (team) sites

o communication sites
o individual data items
l Microsoft 365 Teams:
o entire teams

o team channels
o channel files
o team mailboxes
o files and email messages in
team mailboxes
o meetings
o team sites
l OneNote notebooks: as part
of OneDrive, SharePoint
Online, and Microsoft 365
Teams backups

Backup of archive mailboxes No Yes

(In-Place Archive)

Backup schedule User-defined Up to six times per day*

Backup locations Cloud storage, local folder, network Cloud storage only
folder
(including partner-hosted storage)

Automatic protection of new No Yes, by applying a protection plan

Microsoft 365 users, groups, to the All users, All groups, All
sites, and teams sites, All teams groups

Protecting more than one No Yes

Microsoft 365 organization

Granular recovery Yes Yes

Recovery to another user Yes Yes

within one organization

574 © Acronis International GmbH, 2003-2024

 Local agent Cloud agent

Recovery to another No Yes

organization

Recovery to an on-premises No No
Microsoft Exchange Server

Maximum number of items When backing up to the cloud 10 000 protected items (mailboxes,
that can be backed up storage: 5000 mailboxes per OneDrives, or sites) per company**
without performance company
degradation
When backing up to other
destinations: 2000 mailboxes per
protection plan (no limitation for
number of mailboxes per
company)

Maximum number of manual No 10 manual runs during an hour

backup runs

Maximum number of No 10 operations, including Google

simultaneous recovery Workspace recovery operations
operations

* The default option is Once a day. With the Advanced Backup pack, you can schedule up to six
backups per day. The backups start at approximate intervals that depend on the current load of the
cloud agent, which serves multiple customers in a data center. This ensures even load during the
day and equal quality of service for all customers.

Note
The protection schedule might be affected by the operation of third-party services, for example, the
accessibility of Microsoft 365 servers, throttling settings on the Microsoft servers, and others. See
also https://docs.microsoft.com/en-us/graph/throttling.

** We recommend that you back up your protected items gradually and in this order:

1. Mailboxes.
2. After all mailboxes are backed up, proceed with OneDrives.
3. After OneDrive backup is completed, proceed with the SharePoint Online sites.

The first full backup may take several days, depending on the number of protected items and their
size.

575 © Acronis International GmbH, 2003-2024

Required user rights

In Cyber Protection
The local agent must be registered under a company administrator account and used on the
customer tenant level. Company administrators acting on the unit level, unit administrators, and
users cannot back up or recover Microsoft 365 data.

The cloud agent can be used both on a customer tenant level and on a unit level. For more
information about these levels and their respective administrators, see "Administering Microsoft
365 organizations added on different levels" (p. 583).

In Microsoft 365
Your account must be assigned the global administrator role in Microsoft 365.

To discover, back up, and recover Microsoft 365 public folders, at least one of your Microsoft 365
administrator accounts must have a mailbox and read/write rights to the public folders that you
want to back up.

l The local agent will log in to Microsoft 365 by using this account. To enable the agent to access
the contents of all mailboxes, this account will be assigned the ApplicationImpersonation
management role. If you change the account password, update the password in the Cyber
Protect console, as described in "Changing the Microsoft 365 access credentials" (p. 580).
l The cloud agent does not log in to Microsoft 365. You need to log into Microsoft 365 as a global
administrator once, in order to grant the cloud agent the permissions required for its operation.
The following permissions in Microsoft 365 are required:
o Sign in and read user profiles
o Read and write files in all site collections
o Read and write all users' full profiles
o Read and write all groups
o Read directory data
o Read all channel messages
o Read and write managed metadata
o Read and write items and lists in all site collections
o Have full control of all site collection
o Read and write items in all site collections
o Use Exchange Web Services with full access to all mailboxes
l The cloud agent does not store your account credentials and does not use them to perform
backup and recovery. Changing the credentials, disabling the account, or deleting the account
does not affect the operation of the cloud agent.

576 © Acronis International GmbH, 2003-2024

Limitations
l With the local agent, you can protect up to 5000 workloads. With the cloud agent, you can protect
up to 50000 workloads.
l All users with a mailbox or OneDrive are shown in the Cyber Protect console, including users
without a Microsoft 365 license and users who are blocked from signing in to the Microsoft 365
services.
l A mailbox backup includes only folders visible to users. The Recoverable items folder and its
subfolders (Deletions, Versions, Purges, Audits, DiscoveryHold, Calendar Logging) are not
included in a mailbox backup.
l Automatic creation of users, public folders, groups, or sites during a recovery is not possible. For
example, if you want to recover a deleted SharePoint Online site, first create a new site manually,
and then specify it as the target site during a recovery.
l You cannot simultaneously recover items from different recovering points, even though you can
select such items from the search results.
l During a backup, any sensitivity labels that are applied to the content will be preserved.
Therefore, sensitive content might not be shown if it is recovered to a non-original location and
its user has different access permissions.
l You cannot apply more than one individual backup plan to the same workload.
l When an individual backup plan and a group backup plan are applied to the same workload, the
settings in the individual plan take precedence.

Microsoft 365 seats licensing report

Company administrators can download a report about the protected Microsoft 365 seats and their
licensing. The report is in the CSV format and includes information about the licensing status of a
seat and the reason why a license is used. The report includes also the protected seat name,
associated email, group, Microsoft 365 organization, name and type of the protected workload.

This report is only available for tenants in which a Microsoft 365 Organization is registered.

To download the Microsoft 365 seats licensing report

1. Log in to the Cyber Protect console as a company administrator.

2. Click the account icon in the upper-right corner.
3. Click Microsoft 365 seats licensing report.

Logging
Actions with cloud-to-cloud resources, such as viewing the content of backed-up emails,
downloading attachments or files, recovering emails to non-original mailboxes, or sending them as
emails may violate user privacy. These actions are logged in Monitoring > Audit log in the
Management Portal.

577 © Acronis International GmbH, 2003-2024

Using the locally installed Agent for Office 365

Adding a Microsoft 365 organization

To add a Microsoft 365 organization

1. Log in to the Cyber Protect console as a company administrator.

2. Click the account icon in the upper-right corner, and then click Downloads > Agent for Office
365.
3. Download the agent and install it on a Windows machine that is connected to the Internet.
4. In the Cyber Protect console, go to Devices > Microsoft Office 365 (Local agent).
5. In the window that opens, enter your application ID, application secret, and Microsoft 365 tenant
ID. For more information on how to find these, refer to "Obtaining application ID and application
secret" (p. 578).
6. Click OK.

As a result, your organization data items appear in the Cyber Protect console, on the Microsoft
Office 365 (Local agent) tab.

Important
There must be only one locally installed Agent for Office 365 in an organization (company group).

Obtaining application ID and application secret

To use the modern authentication for Office 365, you need to create a custom application in the
Entra admin center and grant it specific API permissions. Thus, you will obtain the application ID,
application secret, and directory (tenant) ID that you need to enter in the Cyber Protect console.

Note
On the machine where Agent for Office 365 is installed, ensure that you allow access to
graph.microsoft.com through port 443.

To create an application in Entra admin center

1. Log in to the Entra admin center as an administrator.

2. Navigate to Azure Active Directory > App registrations, and then click New registration.
3. Specify a name for your custom application, for example, Cyber Protection.
4. In Supported Account types, select Accounts in this organizational directory only.
5. Click Register.

Your application is now created. In the Entra admin center, navigate to the application's Overview
page and check your application (client) ID and directory (tenant) ID.

578 © Acronis International GmbH, 2003-2024

 For more information on how to create an application in the Entra admin center, refer to the
Microsoft documentation.

To grant your application the necessary API permissions

1. In the Entra admin center, navigate to the application's API permissions, and then click Add a
permission.
2. Select the APIs my organization uses tab, and then search for Office 365 Exchange Online.
3. Click Office 365 Exchange Online, and then click Application permissions.
4. Select the full_access_as_app check box, and then click Add permissions.
5. In API permissions, click Add a permission.
6. Select Microsoft Graph.
7. Select Application permissions.
8. Expand the Directory tab, and then select the Directory.Read.All check box. Click Add
permissions.
9. Check all permissions, and then click Grant admin consent for <your application's name>.
10. Confirm your choice by clicking Yes.

To create an application secret

1. In the Entra admin center, navigate to your application's Certificates & secrets > New client
secret.
2. In the dialog box that opens, select Expires: Never, and then click Add.
3. Check your application secret in the Value field and make sure that you remember it.

For more information on the application secret, refer to the Microsoft documentation.

579 © Acronis International GmbH, 2003-2024

Changing the Microsoft 365 access credentials
You can change access credentials for Microsoft 365 without re-installing the agent.

To change the Microsoft 365 access credentials

1. Click Devices > Microsoft Office 365 (Local agent).

2. Select the Microsoft 365 organization.
3. Click Specify credentials.
4. Enter your application ID, application secret, and Microsoft 365 tenant ID. For more information
on how to find these, refer to "Obtaining application ID and application secret" (p. 578).
5. Click OK.

Protecting Exchange Online mailboxes

What items can be backed up?

You can back up user mailboxes and shared mailboxes. Group mailboxes and archive mailboxes (In-
Place Archive) cannot be backed up.

What items can be recovered?

The following items can be recovered from a mailbox backup:

l Mailboxes
l Email folders
l Email messages
l Calendar events
l Tasks
l Contacts
l Journal entries
l Notes

You can use search to locate the items.

When a mailbox is recovered to an existing mailbox, the existing items with matching IDs are
overwritten.

Recovery of mailbox items does not overwrite anything. Instead, the full path to a mailbox item is
recreated in the target folder.

Selecting Microsoft 365 mailboxes

Select the mailboxes as described below, and then specify other settings of the protection plan as
appropriate.

To select mailboxes

580 © Acronis International GmbH, 2003-2024

1. Click Microsoft Office 365 (Local agent).
2. Select the mailboxes that you want to back up.
3. Click Backup.

Recovering mailboxes and mailbox items

Recovering mailboxes
1. Click Microsoft Office 365 (Local agent).
2. Select the mailbox to recover, and then click Recovery.
You can search mailboxes by name. Wildcards are not supported.
If the mailbox was deleted, select it on the Backup storage tab, and then click Show backups.
3. Select a recovery point. Note that recovery points are filtered by location.
4. Click Recover > Mailbox.
5. In Target mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist, you must specify the
target mailbox.
6. Click Start recovery.

Recovering mailbox items

1. Click Microsoft Office 365 (Local agent).
2. Select the mailbox that originally contained the items that you want to recover, and then click
Recovery.
You can search mailboxes by name. Wildcards are not supported.
If the mailbox was deleted, select it on the Backup storage tab, and then click Show backups.
3. Select a recovery point. Note that recovery points are filtered by location.
4. Click Recover > Email messages.
5. Select the items that you want to recover.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, attachment name, and date.
l For events: search by title and date.
l For tasks: search by subject and date.
l For contacts: search by name, email address, and phone number.
When an email message is selected, you can click Show content to view its contents, including
attachments.

Note
Click the name of an attached file to download it.

When an email message is selected, you can click Send as email to send the message to an
email address. The message is sent from your administrator account's email address.

581 © Acronis International GmbH, 2003-2024

 To be able to select folders, click the "recover folders" icon:
6. Click Recover.
7. In Target mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist, you must specify the
target mailbox.
8. Click Start recovery.
9. Confirm your decision.

The mailbox items are always recovered to the Recovered items folder of the target mailbox.

Using the cloud Agent for Microsoft 365

Adding a Microsoft 365 organization

An administrator can add one or more Microsoft 365 organizations to a customer tenant or to a
unit.

Company administrators add organizations to customer tenants. Unit administrators and customer
administrators acting on the unit level add organizations to units.

To add a Microsoft 365 organization

1. Depending on where you need to add the organization, log in to the Cyber Protect console as a
company administrator or unit administrator.
2. [For company administrators acting on the unit level] In the management portal, navigate to the
desired unit.
3. Click Devices > Add > Microsoft 365 Business.
The software redirects you to the Microsoft 365 login page.
4. Sign in with the Microsoft 365 global administrator credentials.
Microsoft 365 displays a list of permissions that are necessary to back up and recover your
organization's data.
5. Confirm that you grant the Cyber Protection service these permissions.

As a result, your Microsoft 365 organization appears under the Devices tab in the Cyber Protect
console.

Useful tips
l The cloud agent synchronizes with Microsoft 365 every 24 hours, starting from the moment when
the organization is added to the Cyber Protection service. If you add or remove a user, group, or
site, you will not see this change in the Cyber Protect console immediately. To synchronize the
change immediately, select the organization on the Microsoft 365 page, and then click Refresh.
For more information about synchronizing the resources of a Microsoft 365 organization and the
Cyber Protect console, refer to "Discovering Microsoft 365 resources" (p. 584).

582 © Acronis International GmbH, 2003-2024

l If you applied a protection plan to the All users, All groups, or All sites group, the newly added
items will be included in the backup only after synchronization.
l According to Microsoft policy, when a user, group, or site is removed from the Microsoft 365
graphical user interface, it remains available via an API for a few days. During this period, the
removed item is inactive (grayed out) in the Cyber Protect console and is not backed up. When
the removed item becomes unavailable via the API, it disappears from the Cyber Protect console.
Its backups (if any) can be found at Backup Storage > Cloud applications backups.

Administering Microsoft 365 organizations added on different levels

Company administrators have full access to the Microsoft 365 organizations that are added to the
customer tenant level.

Company administrators have limited access to the organizations that are added to a unit. In these
organizations, shown with the unit name in brackets, company administrators can do the following:

l Recover data from backups.

Company administrators can recover data to all organizations in the tenant, regardless of the
level on which these organizations are added.
l Browse backups and recovery points in backups.
l Delete backups and recovery points in backups.
l View alerts and activities.

Company administrators, when acting on the customer tenant level, cannot do the following:

l Add Microsoft 365 organizations to units.

l Delete Microsoft 365 organizations from units.
l Synchronize Microsoft 365 organizations that were added to a unit.
l View, create, edit, delete, apply, run, or revoke protection plans for data items in the Microsoft
365 organizations that are added to a unit.

Unit administrators and company administrators acting on the unit level have full access to the
organizations that are added to a unit. However, they do not have access to any resources from the
parent customer tenant, including the protection plans that are created in it.

Deleting a Microsoft 365 organization

Deleting a Microsoft 365 organization does not affect the existing backups of this organization's
data. If you do not need these backups anymore, delete them first, and then delete the Microsoft
365 organization. Otherwise, the backups will still use cloud storage space that might be billed.

For more information about how to delete backups, see "To delete backups or backup archives" (p.
507).

To delete a Microsoft 365 organization

1. Depending on where the organization is added, sign in to the Cyber Protect console as a
company administrator or unit administrator.

583 © Acronis International GmbH, 2003-2024

2. [For company administrators acting on the unit level] In the management portal, navigate to the
desired unit.
3. Go to Devices > Microsoft 365.
4. Select the organization, and then click Delete group.

As a result, the backup plans applied to this group will be revoked.

However, you should additionally revoke access rights of the Backup Service application to Microsoft
365 organization data manually.

To revoke access rights

1. Log in to Microsoft 365 under a global administrator.

2. Go to Admin Center > Azure Active Directory > Enterprise applications > All applications.
3. Select the Backup Service application and drill down to it.
4. Go to the Properties tab, and then, on the action panel, click Delete.
5. Confirm the deletion operation.

As a result, access rights to the Microsoft 365 organization data will be revoked from the Backup
Service application.

Discovering Microsoft 365 resources

When you add a Microsoft 365 organization to the Cyber Protection service, the resources in this
organization, such as mailboxes, OneDrive storages, Microsoft Teams, and SharePoint sites, are
synchronized to the Cyber Protect console. This operation is called discovery and it is logged in
Monitoring > Activities.

After the discovery operation completes, you can see the resources of the Microsoft 365
organization on the Devices > Microsoft 365 tab in the Cyber Protect console, and you can apply
backup plans to them.

An automatic discovery operation runs once a day to keep the list of resources in the Cyber Protect
console up to date. You can also synchronize this list on demand, by re-running a discovery
operation manually.

To re-run a discovery operation manually

1. In the Cyber Protect console, go to Devices > Microsoft 365.

2. Select your Microsoft 365 organization, and then, in the Actions pane, click Refresh.

584 © Acronis International GmbH, 2003-2024

Note
You can manually run a discovery operation up to 10 times per hour. When this number is reached,
the allowed runs are reset to one per hour, and then every hour an additional run becomes
available, until a total of 10 runs per hour is reached again.

Setting the frequency of Microsoft 365 backups

By default, Microsoft 365 backups run once a day and no additional scheduling options are
available.

If the Advanced Backup pack is enabled in your tenant, you can configure more frequent backups.
You can select the number of backups per day, but you cannot configure the backup start time. The
backups start automatically at approximate intervals that depend on the current load of the cloud
agent, which serves multiple customers in a data center. This ensures even load during the day, and
equal quality of service for all customers.

The following options are available.

Scheduling options Approximate interval between each backup

Once a day 24 hours

Twice a day (default) 12 hours

3 times a day 8 hours

6 times a day 4 hours

Note
Depending on the load on the cloud agent and possible throttling on the Microsoft 365 side, a
backup might start later than scheduled or take longer to complete. If a backup takes longer that
the average interval between two backups, the next backup will be rescheduled, which might result
in fewer backups per day than selected. For example, only two backups per day might be able to
complete, even though you selected six per day.

Backups of group mailboxes can only run once a day.

Protecting Exchange Online data

What items can be backed up?

You can back up user mailboxes, shared mailboxes, and group mailboxes. Optionally, you can
choose to back up the online archive mailboxes (In-Place Archive) of the selected mailboxes.

Starting from version 8.0 of the Cyber Protection service, you can back up public folders. If your
organization was added to the Cyber Protection service before the version 8.0 release, you need to
re-add the organization to obtain this functionality. Do not delete the organization, simply repeat

585 © Acronis International GmbH, 2003-2024

the steps described in "Adding a Microsoft 365 organization" (p. 582). As a result, the Cyber
Protection service obtains the permission to use the corresponding API.

What items can be recovered?

The following items can be recovered from a mailbox backup:

l Mailboxes
l Email folders
l Email messages
l Calendar events
l Tasks
l Contacts
l Journal entries
l Notes

The following items can be recovered from a public folder backup:

l Subfolders
l Posts
l Email messages

You can use search to locate the items.

When recovering mailboxes, mailbox items, public folders, and public folder items, you can select
whether to overwrite the items in the target location.

Selecting mailboxes
Select the mailboxes as described below, and then specify other settings of the protection plan as
appropriate.

To select Exchange Online mailboxes

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose users' data you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up the mailboxes of all users and all shared mailboxes (including mailboxes that will
be created in the future), expand the Users node, select All users, and then click Group
backup.
l To back up individual user or shared mailboxes, expand the Users node, select All users,
select the users whose mailboxes you want to back up, and then click Backup.
l To back up all group mailboxes (including mailboxes of groups that will be created in the
future), expand the Groups node, select All groups, and then click Group backup.
l To back up individual group mailboxes, expand the Groups node, select All groups, select the
groups whose mailboxes you want to back up, and then click Backup.

586 © Acronis International GmbH, 2003-2024

 Note
The cloud Agent for Microsoft 365 uses an account with the appropriate rights to access a
group mailbox. Thus, to back up a group mailbox, at least one of the group owners must be
licensed Microsoft 365 user with a mailbox. If the group is private or with hidden
membership, the owner must also be a member of the group.

4. On the protection plan panel:

l Ensure that the Microsoft 365 mailboxes item is selected in What to back up.
If some of the individually selected users do not have the Exchange service included in their
Microsoft 365 plan, you will not be able to select this option.
If some of the selected users for group backup do not have the Exchange service included in
their Microsoft 365 plan, you will be able to select this option, but the protection plan will not
be applied to those users.
l If you do not want to backup the archive mailboxes, disable the Archive mailbox switch.

Selecting public folders

Select the public folders as described below, and then specify other settings of the protection plan
as appropriate.

Note
Public folders consume licenses from your backup quota for Microsoft 365 seats.

To select Exchange Online public folders

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, expand the
organization whose data you want to back up. Otherwise, skip this step.
3. Expand the Public folders node, and then select All public folders.
4. Do one of the following:
l To back up all public folders (including public folders that will be created in the future), click
Group backup.
l To back up individual public folders, select the public folders that you want to back up, and
then click Backup.
5. On the protection plan panel, ensure that the Microsoft 365 mailboxes item is selected in What
to back up.

Recovering mailboxes and mailbox items

Recovering mailboxes
1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.

587 © Acronis International GmbH, 2003-2024

 3. Do one of the following:
l To recover a user mailbox, expand the Users node, select All users, select the user whose
mailbox you want to recover, and then click Recovery.
l To recover a shared mailbox, expand the Users node, select All users, select the shared
mailbox that you want to recover, and then click Recovery.
l To recover a group mailbox, expand the Groups node, select All groups, select the group
whose mailbox you want to recover, and then click Recovery.
l If the user, group, or the shared mailbox was deleted, select the item in the Cloud
applications backups section of the Backup storage tab, and then click Show backups.
You can search users and groups by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain mailboxes, select Mailboxes in Filter by content.

5. Click Recover > Entire mailbox.

6. If multiple Microsoft 365 organizations are added to the Cyber Protection service, click Microsoft
365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
7. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
You cannot create a new target mailbox during recovery. To recover a mailbox to a new one, first
you need to create the target mailbox in the desired Microsoft 365 organization, and then let the
cloud agent synchronize the change. The cloud agent automatically synchronizes with Microsoft
365 every 24 hours. To synchronize the change immediately, in the Cyber Protect console, select
the organization on the Microsoft 365 page, and then click Refresh.
8. Click Start recovery.
9. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
10. Click Proceed to confirm your decision.

Recovering mailbox items

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Do one of the following:
l To recover items from a user mailbox, expand the Users node, select All users, select the
user whose mailbox originally contained the items that you want to recover, and then click

588 © Acronis International GmbH, 2003-2024

 Recovery.
l To recover items from a shared mailbox, expand the Users node, select All users, select the
shared mailbox that originally contained the items that you want to recover, and then click
Recovery.
l To recover items from a group mailbox, expand the Groups node, select All groups, select the
group whose mailbox originally contained the items that you want to recover, and then click
Recovery.
l If the user, group, or the shared mailbox was deleted, select the item in the Cloud
applications backups section of the Backup storage tab, and then click Show backups.
You can search users and groups by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain mailboxes, select Mailboxes in Filter by content.

5. Click Recover > Email messages.

6. Browse to the required folder or use search to obtain the list of the required items.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, attachment name, and date. You can
select a start date or an end date (both inclusive), or both dates to search within a time range.
l For events: search by title and date.
l For tasks: search by subject and date.
l For contacts: search by name, email address, and phone number.
7. Select the items that you want to recover. To be able to select folders, click the "recover folders"

icon:
You cannot create a new target mailbox during recovery. To recover a new mailbox item to a
new mailbox, first you need to create the target new mailbox item in Microsoft 365 organization,
and then let the cloud agent synchronize the change. The cloud agent automatically
synchronizes with Microsoft 365 every 24 hours. To synchronize the change immediately, in the
Cyber Protect console, select the organization on the Microsoft 365 page, and then click
Refresh.
Additionally, you can do any of the following:
l When an item is selected, click Show content to view its contents, including attachments.
Click the name of an attached file to download it.
l When an email message or a calendar item is selected, click Send as email to send the item
to the specified email addresses. You can select the sender and write a text to be added to the
forwarded item.
l Only if the backup is not encrypted, you used search, and selected a single item in the search
results: click Show versions to select the item version to recover. You can select any backed-
up version, earlier or later than the selected recovery point.
8. Click Recover.

589 © Acronis International GmbH, 2003-2024

 9. If multiple Microsoft 365 organizations were added to the Cyber Protection service, click
Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
10. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
11. [Only when recovering to a user or a shared mailbox] In Path, view or change the target folder in
the target mailbox. By default, the Recovered items folder is selected.
Group mailbox items are always recovered to the Inbox folder.
12. Click Start recovery.
13. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
14. Click Proceed to confirm your decision.

Recovering entire mailboxes to PST data files

Note
In-place archive cannot be restored as a part of recovery to PST files. To restore in-place archive
along with mailbox, refer to "Recovering mailboxes" (p. 587).

To recover mailbox

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Do one of the following:
l To recover a user mailbox to PST data file, expand the Users node, select All users, select the
mailbox you want to recover, and then click Recovery.
l To recover a shared mailbox to PST data file, expand the Users node, select All users, select
the mailbox that you want to recover, and then click Recovery.
l To recover a group mailbox to PST data file, expand the Groups node, select All groups, select
the group whose mailbox you want to recover, and then click Recovery.
You can search users and groups by name. Wildcards are not supported.
If the user, group, or the shared Outlook data file was deleted, select the item in the Cloud
applications backups section of the Backup storage tab, and then click Show backups.
4. Click Recover > As PST files.
5. Set the password to encrypt the archive with the PST files.
The password must contain at least one symbol.
6. Confirm the password and click Done.

590 © Acronis International GmbH, 2003-2024

7. The selected mailbox items will be recovered as PST data files and archived in ZIP format. The
maximum size of one PST file is limited to 2 GB, so if the data you are recovering exceeds 2 GB, it
will be split into several PST files. The ZIP archive will be protected with the password you set.
8. You will receive an email with a link to a ZIP archive containing the created PST files.
9. The administrator will receive an email notification that you have performed the recovery
procedure.

Note
Mailbox recovery to PST files can be time-consuming, as it involves not only data transfer, but also
data transformation using complex algorithms.

To download the archive with PST files and complete recovery

1. Do one of the following:

l To download the archive from the email, follow the Download files link.
The archive is available for download within 24 hours. If the link expires, repeat the recovery
procedure.
l To download the archive from the Cyber Protect console:
a. Go to Backup Storage > PST files.
b. Select the latest highlighted archive.
c. Click Download in the right pane.
The archive will be downloaded to the default download directory on your computer.
2. Extract the PST files from the archive using the password you set to encrypt the archive.
3. Open the PST files with Microsoft Outlook.
The resulting PST files could be much smaller in size that the original mailbox. That is normal.

Important
Do not import these files to Microsoft Outlook by using the Import and Export Wizard.
Open the files by double-clicking them or right-clicking them and selecting Open with... >
Microsoft Outlook in the context menu.

Recovering mailbox items to PST files

Note
In-place archive cannot be restored as a part of recovery to PST files. To restore in-place archive
along with mailbox, refer to "Recovering mailboxes" (p. 587).

To recover mailbox items

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Do one of the following:

591 © Acronis International GmbH, 2003-2024

 l To recover items from a user mailbox, expand the Users node, select All users, select the
user whose mailbox originally contained the items that you want to recover, and then click
Recovery.
l To recover items from a shared mailbox, expand the Users node, select All users, select the
shared mailbox that originally contained the items that you want to recover, and then click
Recovery.
l To recover items from a group mailbox, expand the Groups node, select All groups, select the
group whose mailbox originally contained the items that you want to recover, and then click
Recovery.
l If the user, group, or the shared mailbox was deleted, select the item in the Cloud
applications backups section of the Backup storage tab, and then click Show backups.
You can search users and groups by name. Wildcards are not supported.
4. Click Recover > Email messages.
5. Browse to the required folder or use search to obtain the list of the required items.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, attachment name, and date.
l For events: search by title and date.
l For tasks: search by subject and date.
l For contacts: search by name, email address, and phone number.
6. Select the items that you want to recover. To be able to select folders, click the "recover folders"

icon:
Additionally, you can do any of the following:
l When an item is selected, click Show content to view its contents, including
attachments. Click the name of an attached file to download it.
l When an email message or a calendar item is selected, click Send as email to send the item
to the specified email addresses. You can select the sender and write a text to be added to the
forwarded item.
l Only if the backup is not encrypted, you used search, and selected a single item in the search
results: click Show versions to select the item version to recover. You can select any backed-
up version, earlier or later than the selected recovery point.
7. Click Recover as PST files.
8. Set the password to encrypt the archive with the PST files.
The password should contain at least one symbol.
9. Confirm the password and click DONE.

The selected mailbox items will be recovered as PST data files and archived in ZIP format. The
maximum size of one PST file is limited to 2 GB, so if the data you are recovering exceeds 2 GB, it will
be split into several PST files. The ZIP archive will be protected with the password you set.

You will receive an email with a link to a ZIP archive containing the created PST files.

592 © Acronis International GmbH, 2003-2024

The administrator will receive an email notification that you have performed the recovery
procedure.

To download the archive with PST files and complete recovery

1. Do one of the following:

l To download the archive from the email, follow the Download files link.
The archive is available for download within 24 hours. If the link expires, repeat the recovery
procedure.
l To download the archive from the Cyber Protect console:
a. Go to Backup Storage > PST files.
b. Select the latest highlighted archive.
c. Click Download in the right pane.
The archive will be downloaded to the default download directory on your computer.
2. Extract the PST files from the archive using the password you set to encrypt the archive.
3. Open the PST files with Microsoft Outlook.
The resulting PST files could be much smaller in size that the original mailbox. That is normal.

Important
Do not import these files to Microsoft Outlook by using the Import and Export Wizard.
Open the files by double-clicking them or right-clicking them and selecting Open with... >
Microsoft Outlook in the context menu.

Recovering public folders and folder items

In order to recover a public folder or public folder items, at least one administrator of the target
Microsoft 365 organization must have the Owner's rights for the target public folder. If the recovery
fails with an error about denied access, assign these rights in the target folder properties, select the
target organization in the Cyber Protect console, click Refresh, and then repeat the recovery.

To recover a public folder or folder items

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations are added to the Cyber Protection service, expand the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Do one of the following:
l Expand the Public folders node, select All public folders, select the public folder that you
want to recover or that originally contained the items that you want to recover, and then click
Recovery.
l If the public folder was deleted, select it in the Cloud applications backups section of the
Backup storage tab, and then click Show backups.
You can search public folders by name. Wildcards are not supported.
4. Select a recovery point.
5. Click Recover data.

593 © Acronis International GmbH, 2003-2024

 6. Browse to the required folder or use search to obtain the list of the required items.
You can search email messages and posts by subject, sender, recipient, and date. Wildcards are
not supported.
7. Select the items that you want to recover. To be able to select folders, click the "recover folders"

icon:
Additionally, you can do any of the following:
l When an email message or a post is selected, click Show content to view its contents,
including attachments. Click the name of an attached file to download it.
l When an email message or a post is selected, click Send as email to send the item to
specified email addresses. You can select the sender and write a text to be added to the
forwarded item.
l Only if the backup is not encrypted, you used search, and selected a single item in the search
results: click Show versions to select the item version to recover. You can select any backed-
up version, earlier or later than the selected recovery point.
8. Click Recover.
9. If multiple Microsoft 365 organizations were added to the Cyber Protection service, click
Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
10. In Recover to public folder, view, change, or specify the target public folder.
By default, the original folder is selected. If this folder does not exist or a non-original
organization is selected, you must specify the target folder.
You cannot create a new public folder during recovery. To recover a public folder to a new one,
first you need to create the target public folder in the desired Microsoft 365 organization, and
then let the cloud agent synchronize the change. The cloud agent automatically synchronizes
with Microsoft 365 every 24 hours. To synchronize the change immediately, in the Cyber Protect
console, select the organization on the Microsoft 365 page, and then click Refresh.

11. In Path, view or change the target subfolder in the target public folder. By default, the original
path will be recreated.
12. Click Start recovery.
13. Select one of the overwriting options:

Option Description

Overwrite All existing files in the destination location are overwritten.

existing items

Do not overwrite If the destination location contains a file of the same name, that file is not
existing items overwritten and the source file is not saved to the destination location.

14. Click Proceed to confirm your decision.

594 © Acronis International GmbH, 2003-2024

Protecting OneDrive files

What items can be backed up?

You can back up an entire OneDrive, or individual files and folders.

A separate option in the backup plan enables the backup of OneNote notebooks.

Files are backed up together with their sharing permissions. Advanced permission levels (Design,
Full, Contribute) are not backed up.

Some files may contain sensitive information and the access to them may be blocked by a data loss
prevention (DLP) rule in Microsoft 365. These files are not backed up, and no warnings are displayed
after the backup operation completes.

Limitations
Backing up OneDrive content is not supported for shared mailboxes. To back up this content,
convert the shared mailbox to a regular user account and ensure that OneDrive is enabled for that
account.

What items can be recovered?

You can recover an entire OneDrive or any file or folder that was backed up.

You can use search to locate the items.

You can choose whether to recover the sharing permissions or let the files inherit the permissions
from the folder to which they are recovered.

Sharing links for files and folders are not recovered.

Selecting OneDrive files

Select the files as described below, and then specify other settings of the protection plan as
appropriate.

To select OneDrive files

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose users' data you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up the files of all users (including users that will be created in the future), expand the
Users node, select All users, and then click Group backup.
l To back up the files of individual users, expand the Users node, select All users, select the
users whose files you want to back up, and then click Backup.

595 © Acronis International GmbH, 2003-2024

4. On the protection plan panel:
l Ensure that the OneDrive item is selected in What to back up.
If some of the individually selected users do not have the OneDrive service included in their
Microsoft 365 plan, you will not be able to select this option.
If some of the selected users for group backup do not have the OneDrive service included in
their Microsoft 365 plan, you will be able to select this option, but the protection plan will not
be applied to those users.
l In Items to back up, do one of the following:
o Keep the default setting [All] (all files).
o Specify the files and folders to back up by adding their names or paths.
You can use wildcard characters (*, **, and ?). For more details about specifying paths and
using wildcards, refer to "File filters".
o Specify the files and folders to back up by browsing.
The Browse link is available only when creating a protection plan for a single user.
l [Optional] In Items to back up, click Show exclusions to specify the files and folders to skip
during the backup.
File exclusions override the file selection; i.e. if you specify the same file in both fields, this file
will be skipped during a backup.
l [Optional] To back up the OneNote notebooks, enable the Include OneNote switch.

Recovering OneDrive and OneDrive files

Recovering an entire OneDrive

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Users node, select All users, select the user whose OneDrive you want to recover,
and then click Recovery.
If the user was deleted, select the user in the Cloud applications backups section of the Backup
storage tab, and then click Show backups.
You can search users by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain OneDrive files, select OneDrive in Filter by
content.

5. Click Recover > Entire OneDrive.

6. If multiple Microsoft 365 organizations were added to the Cyber Protection service, click
Microsoft 365 organization to view, change, or specify the target organization.

596 © Acronis International GmbH, 2003-2024

 By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
You cannot create a new OneDrive target during recovery. To recover a OneDrive to a new one,
first you need to create the target OneDrive in Microsoft 365 organization, and then let the cloud
agent synchronize the change. The cloud agent automatically synchronizes with Microsoft 365
every 24 hours. To synchronize the change immediately, in the Cyber Protect console, select the
organization on the Microsoft 365 page, and then click Refresh.

7. In Recover to drive, view, change, or specify the target user.

By default, the original user is selected. If this user does not exist or a non-original organization
is selected, you must specify the target user.
8. Select whether to recover the sharing permissions for the files.
9. Click Start recovery.
10. Select one of the overwriting options:

Option Description

Overwrite an If there is a file with the same name in the destination location, and it is older than
existing file if it the source file, the source file will be saved in the destination location, replacing
is older the older version.

Overwrite All existing files in the destination location are overwritten, regardless of their last
existing files modified date.

Do not If there is a file with the same name in the destination location, no changes are
overwrite applied to it, and the source file is not saved to the destination location.
existing files

Note
When you recover OneNote notebooks, both Overwrite an existing file if it is older and
Overwrite existing files will result in overwriting the exiting OneNote notebooks.

11. Click Proceed to confirm your decision.

Recovering OneDrive files

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Users node, select All users, select the user whose OneDrive files you want to
recover, and then click Recovery.
If the user was deleted, select the user in the Cloud Applications Backups section of the
Backup storage tab, and then click Show backups.
You can search users by name. Wildcards are not supported.
4. Select a recovery point.

597 © Acronis International GmbH, 2003-2024

 Note
To see only the recovery points that contain OneDrive files, select OneDrive in Filter by
content.

5. Click Recover > Files/folders.

6. Browse to the required folder or use search to obtain the list of the required files and folders.
7. Select the files that you want to recover.
If the backup is not encrypted and you selected a single file, you can click Show versions to
select the file version to recover. You can select any backed-up version, earlier or later than the
selected recovery point.
8. If you want to download a file, select the file, click Download, select the location to save the file
to, and then click Save. Otherwise, skip this step.
9. Click Recover.
10. If multiple Microsoft 365 organizations were added to the Cyber Protection service, click
Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
You cannot create a new OneDrive during recovery. To recover a file to a new OneDrive, first you
need to create the target OneDrive in the desired Microsoft 365 organization, and then let the
cloud agent synchronize the change. The cloud agent automatically synchronizes with Microsoft
365 every 24 hours. To synchronize the change immediately, in the Cyber Protect console, select
the organization on the Microsoft 365 page, and then click Refresh.
11. In Recover to drive, view, change, or specify the target user.
By default, the original user is selected. If this user does not exist or a non-original organization
is selected, you must specify the target user.
12. In Path, view or change the target folder in the target user's OneDrive. By default, the original
location is selected.
13. Select whether to recover the sharing permissions for the files.
14. Click Start recovery.
15. Select one of the file overwriting options:

Option Description

Overwrite an If there is a file with the same name in the destination location, and it is older than
existing file if it the source file, the source file will be saved in the destination location, replacing
is older the older version.

Overwrite All existing files in the destination location are overwritten, regardless of their last
existing files modified date.

Do not If there is a file with the same name in the destination location, no changes are
overwrite applied to it, and the source file is not saved to the destination location.
existing files

598 © Acronis International GmbH, 2003-2024

 Note
When you recover OneNote notebooks, both Overwrite an existing file if it is older and
Overwrite existing files will result in overwriting the exiting OneNote notebooks.

16. Click Proceed to confirm your decision.

Protecting SharePoint Online sites

What items can be backed up?

You can back up SharePoint classic site collections, group (modern team) sites, and communication
sites. Also, you can select individual subsites, lists, and libraries for backup.

A separate option in the backup plan enables the backup of OneNote notebooks.

The following items are skipped during a backup:

l The Look and Feel site settings (except for Title, description, and logo).
l Site page comments and page comments settings (comments On/Off).
l The Site features site settings.
l Web part pages and web parts embedded in the wiki pages (due to SharePoint Online API
limitations).
l Checked out files—files that are manually checked out for editing and all files that are created or
uploaded in libraries, for which the option Require Check Out was enabled. To backup these
files, first check them in.
l External data and Managed Metadata types of columns.
l The default site collection "domain-my.sharepoint.com". This is a collection where all of the
organization users’ OneDrive files reside.
l The contents of the recycle bin.

Limitations
l Titles and descriptions of sites/subsites/lists/columns are truncated during a backup if the
title/description size is greater than 10000 bytes.
l You cannot back up previous versions of files created in SharePoint Online. Only the latest
versions of the files are protected.
l You cannot back up the Preservation Hold library.
l You cannot back up sites created in the Business Productivity Online Suite (BPOS), the
predecessor of Microsoft 365.
l You cannot back up the settings for sites that use the managed path /portals (for example,
https://<tenant>.sharepoint.com/portals/...).
l Information Rights Management (IRM) settings of a list or a library can be recovered only if IRM is
enabled in the target Microsoft 365 organization.

599 © Acronis International GmbH, 2003-2024

What items can be recovered?
The following items can be recovered from a site backup:

l Entire site
l Subsites
l Lists
l List items
l Document libraries
l Documents
l List item attachments
l Site pages and wiki pages

You can use search to locate the items.

Items can be recovered to the original or a non-original site. The path to a recovered item is the
same as the original one. If the path does not exist, it is created.

You can choose whether to recover the sharing permissions or let the items inherit the permissions
from the parent object after the recovery.

What items cannot be recovered?

l Subsites based on the Visio Process Repository template.
l Lists of the following types: Survey list, Task list, Picture library, Links, Calendar, Discussion
Board, External, and Import Spreadsheet.
l Lists for which multiple content types are enabled.

Selecting SharePoint Online data

Select the data as described below, and then specify other settings of the protection plan as
appropriate.

To select SharePoint Online data

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose users' data you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up all classic SharePoint sites in the organization, including sites that will be created in
the future, expand the Site collections node, select All site collections, and then click Group
backup.
l To back up individual classic sites, expand the Site collections node, select All site
collections, select the sites that you want to back up, and then click Backup.
l To back up all group (modern team) sites, including sites that will be created in the future,
expand the Groups node, select All groups, and then click Group backup.

600 © Acronis International GmbH, 2003-2024

 l To back up individual group (modern team) sites, expand the Groups node, select All groups,
select the groups whose sites you want to back up, and then click Backup.
4. On the protection plan panel:
l Ensure that the SharePoint sites item is selected in What to back up.
l In Items to back up, do one of the following:
o Keep the default setting [All] (all items of the selected sites).
o Specify the subsites, lists, and libraries to back up by adding their names or paths.
To back up a subsite or a top-level site list/library, specify its display name in the following
format: /display name/**
To back up a subsite list/library, specify its display name in the following format: /subsite
display name/list display name/**
The display names of subsites, lists, and libraries are shown on the Site contents page of a
SharePoint site or subsite.
o Specify the subsites to back up by browsing.
The Browse link is available only when creating a protection plan for a single site.
l [Optional] In Items to back up, click Show exclusions to specify the subsites, lists, and
libraries to skip during the backup.
Item exclusions override the item selection; i.e. if you specify the same subsite in both fields,
this subsite will be skipped during a backup.
l [Optional] To back up the OneNote notebooks, enable the Include OneNote switch.

Recovering SharePoint Online data

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Do one of the following:
l To recover data from a group (modern team) site, expand the Groups node, select All groups,
select the group whose site originally contained the items that you want to recover, and then
click Recovery.
l To recover data from a classic site, expand the Site Collections node, select All site
collections, select the site that originally contained the items that you want to recover, and
then click Recovery.
l If the site was deleted, select it in the Cloud applications backups section of the Backup
storage tab, and then click Show backups.
You can search groups and sites by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain SharePoint sites, select SharePoint sites in Filter
by content.

601 © Acronis International GmbH, 2003-2024

 5. Click Recover SharePoint files.
6. Browse to the required folder or use search to obtain the list of the required data items.
7. Select the items that you want to recover.
If the backup is not encrypted, you used search, and selected a single item in the search results,
you can click Show versions to select the item version to recover. You can select any backed-up
version, earlier or later than the selected recovery point.
8. [Optional] To download an item, select the item, click Download, select the location in which you
want to save the item, and then click Save.
9. Click Recover.
10. If multiple Microsoft 365 organizations were added to the Cyber Protection service, click
Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
11. In Recover to site, view, change, or specify the target site.
You cannot create a new SharePoint site during recovery. To recover a SharePoint site to a new
one, first you need to create the target site in the desired Microsoft 365 organization, and then
let the cloud agent synchronize the change. The cloud agent automatically synchronizes with
Microsoft 365 every 24 hours. To synchronize the change immediately, in the Cyber Protect
console, select the organization on the Microsoft 365 page, and then click Refresh.
12. Select whether to recover the sharing permissions of the recovered items.
13. Click Start recovery.
14. Select one of the overwriting options:

Option Description

Overwrite an If there is a file with the same name in the destination location, and it is older than
existing file if it the source file, the source file will be saved in the destination location, replacing
is older the older version.

Overwrite All existing files in the destination location are overwritten, regardless of their last
existing files modified date.

Do not If there is a file with the same name in the destination location, no changes are
overwrite applied to it, and the source file is not saved to the destination location.
existing files

Note
When you recover OneNote notebooks, both Overwrite an existing file if it is older and
Overwrite existing files will result in overwriting the exiting OneNote notebooks.

15. Click Proceed to confirm your decision.

602 © Acronis International GmbH, 2003-2024

Protecting Microsoft 365 Teams

What items can be backed up?

You can back up entire teams. This includes team name, team members list, team channels and
their content, team mailbox and meetings, and team site.

A separate option in the backup plan enables the backup of OneNote notebooks.

What items can be recovered?

l Entire team
l Team channels
l Channel files
l Team mailbox
l Email folders in the team mailbox
l Email messages in the team mailbox
l Meetings
l Team site

You cannot recover conversations in team channels, but you can download them as a single html
file.

Limitations
The following items are not backed up:

l The settings of the general channel (moderation preferences) – due to a Microsoft Teams beta
API limitation.
l The settings of the custom channels (moderation preferences) – due to a Microsoft Teams beta
API limitation.
l Meeting notes.
Messages in the chat section . This section contains private one-on-one chats and
l

group chats.
l Stickers and praises.

Backup and recovery are supported for the following channel tabs:

l Word
l Excel
l PowerPoint
l PDF
l Document Library

603 © Acronis International GmbH, 2003-2024

Selecting teams
Select teams as described below, and then specify other settings of the protection plan as
appropriate.

To select teams

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose teams you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up all the teams in the organization (including teams that will be created in the
future), expand the Teams node, select All teams, and then click Group backup.
l To back up individual teams, expand the Teams node, select All teams, select the teams that
you want to back up, and then click Backup.
You can search teams by name. Wildcards are not supported.
4. On the protection plan panel:
l Ensure that the Microsoft Teams item is selected in What to back up.
l [Optional] In How long to keep, set the cleanup options.
l [Optional] If you want to encrypt your backup, enable the Encryption switch, and then set
your password and select the encryption algorithm.
l [Optional] To back up the OneNote notebooks, enable the Include OneNote switch.

Recovering an entire team

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up teams you want to recover. Otherwise, skip this step.
3. Expand the Teams node, select All teams, select the team that you want to recover, and then
click Recovery.
You can search teams by name. Wildcards are not supported.
4. Select a recovery point.
5. Click Recover > Entire Team.
If multiple Microsoft 365 organizations were added to the Cyber Protection service,
click Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
6. In Recover to team, view the target team or select another.
By default, the original team is selected. If this team does not exist (for example, it was deleted)
or you selected an organization that does not contain the original team, you must select a target
team from the drop-down list.
You can recover a team only into an existing team. You cannot create teams during recovery
operations.

604 © Acronis International GmbH, 2003-2024

7. Click Start recovery.
8. Select one of the overwriting options:
l Overwrite existing content if it is older
l Overwrite existing content
l Do not overwrite existing content

Note
When you recover OneNote notebooks, both of the options Overwrite existing content if it is
older and Overwrite existing content will result in overwriting the exiting OneNote notebooks.

9. Click Proceed to confirm your decision.

When you delete a channel in Microsoft Teams' graphic interface, it is not immediately removed
from the system. Thus, when you recover the whole team, this channel's name cannot be used and
a postfix will be added to it.

Conversations are recovered as a single html file in the Files tab of the channel. You can find this file
in a folder named according to the following pattern: <Team name>_<Channel name>_conversations_
backup_<date of recovery>T<time of recovery>Z.

Note
After recovering a team or team channels, go to Microsoft Teams, select the channels that were
recovered, and then click their Files tab. Otherwise, the subsequent backups of these channels will
not include this tab's content – due to a Microsoft Teams beta API limitation.

Recovering team channels or files in team channels

To recover team channels

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up teams you want to recover. Otherwise, skip this step.
3. Expand the Teams node, select All teams, select the team whose channels you want to recover,
and then click Recovery.
4. Select a recovery point.
5. Click Recover > Channels.
6. Select the channels that you want to recover, and then click Recover. To select a channel in the
main pane, select the check box in front of its name.
The following search options are available:
l For Conversations: sender, subject, content, language, attachment name, date or date range.
l For Files: file name or folder name, file type, size, date or date range of the last change.

Note
You can also download the files locally, instead of recovering them.

605 © Acronis International GmbH, 2003-2024

 7. If multiple Microsoft 365 organizations were added to the Cyber Protection service, click
Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
8. In Recover to team, view, change, or specify the target team.
By default, the original team is selected. If this team does not exist or a non-original organization
is selected, you must specify the target team.
9. In Recover to channel, view, change, or specify the target channel.
10. Click Start recovery.
11. Select one of the overwriting options:
l Overwrite existing content if it is older
l Overwrite existing content
l Do not overwrite existing content

Note
When you recover OneNote notebooks, both of the options Overwrite existing content if it is
older and Overwrite existing content will result in overwriting the exiting OneNote notebooks.

12. Click Proceed to confirm your decision.

Conversations are recovered as a single html file in the Files tab of the channel. You can find this file
in a folder named according to the following pattern: <Team name>_<Channel name>_conversations_
backup_<date of recovery>T<time of recovery>Z.

Note
After recovering a team or team channels, go to Microsoft Teams, select the channels that were
recovered, and then click their Files tab. Otherwise, the subsequent backups of these channels will
not include this tab's content – due to a Microsoft Teams beta API limitation.

To recover files in a team channel

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up teams you want to recover. Otherwise, skip this step.
3. Expand the Teams node, select All teams, select the team whose channels you want to recover,
and then click Recovery.
4. Select a recovery point.
5. Click Recover > Channels.
6. Select the desired channel, and then open the Files folder.
Browse to the required items or use search to obtain the list of the required items. The following
search options are available: file name or folder name, file type, size, date or date range of the
last change.

606 © Acronis International GmbH, 2003-2024

 7. [Optional] To download an item, select the item, click Download, select the location in which you
want to save the item, and then click Save.
8. Select the items that you want to recover, and then click Recover
9. If multiple Microsoft 365 organizations were added to the Cyber Protection service, click
Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
10. In Recover to team, view, change, or specify the target team.
By default, the original team is selected. If this team does not exist or a non-original organization
is selected, you must specify the target team.
11. In Recover to channel, view, change, or specify the target channel.
12. Select whether to recover the sharing permissions of the recovered items.
13. Click Start recovery.
14. Select one of the overwriting options:
l Overwrite existing content if it is older
l Overwrite existing content
l Do not overwrite existing content

Note
When you recover OneNote notebooks, both of the options Overwrite existing content if it is
older and Overwrite existing content will result in overwriting the exiting OneNote notebooks.

15. Click Proceed to confirm your decision.

You cannot recover individual conversations. In the main pane, you can only browse the
Conversation folder or download its content as a single html file. To do so, click the "recover

folders" icon , select the desired Conversations folder, and then click Download.

You can search the messages in the Conversation folder by:

l Sender
l Content
l Attachment name
l Date

Recovering a team mailbox

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up teams you want to recover. Otherwise, skip this step.
3. Expand the Teams node, select All teams, select the team whose mailbox you want to recover,
and then click Recovery.
You can search teams by name. Wildcards are not supported.
4. Select a recovery point.

607 © Acronis International GmbH, 2003-2024

 5. Click Recover > Email messages.

6. Click the "recover folders" icon , select the root mailbox folder, and then click Recover.

Note
You can also recover individual folders from the selected mailbox.

7. Click Recover.
8. If multiple Microsoft 365 organizations were added to the Cyber Protection service,
click Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
9. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
10. Click Start recovery.
11. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
12. Click Proceed to confirm your decision.

Recovering team mailbox items to PST files

To recover team mailbox items

1. Click Microsoft 365.

2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up data you want to recover. Otherwise, skip this step.
3. You can search users and groups by name. Wildcards are not supported.
4. Expand the Teams node, select All teams, select a team whose mailbox originally contained the
items that you want to recover, and then click Recovery.
5. Click Recover > Email messages.
6. Browse to the required folder or use search to obtain the list of the required items.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, attachment name, and date.
l For events: search by title and date.
l For tasks: search by subject and date.
l For contacts: search by name, email address, and phone number.
7. Select the items that you want to recover. To be able to select folders, click the "recover folders"

icon:
Additionally, you can do any of the following:

608 © Acronis International GmbH, 2003-2024

 l When an item is selected, click Show content to view its contents, including
attachments. Click the name of an attached file to download it.
l When an email message or a calendar item is selected, click Send as email to send the item
to the specified email addresses. You can select the sender and write a text to be added to the
forwarded item.
l When the backup is not encrypted, you used search, and selected a single item from the
search results: click Show versions to view the item version. You can select any backed-up
version, no matter if it is earlier or later than the selected recovery point.
8. Click Recover as PST files.
9. Set the password to encrypt the archive with the PST files.
The password should contain at least one symbol.
10. Confirm the password and click DONE.

The selected mailbox items will be recovered as PST data files and archived in ZIP format. The
maximum size of one PST file is limited to 2 GB, so if the data you are recovering exceeds 2 GB, it will
be split into several PST files. The ZIP archive will be protected with the password you set.

You will receive an email with a link to a ZIP archive containing the created PST files.

The administrator will receive an email notification that you have performed the recovery
procedure.

To download the archive with PST files and complete recovery

1. Do one of the following:

l To download the archive from the email, follow the Download files link.
The archive is available for download within 24 hours. If the link expires, repeat the recovery
procedure.
l To download the archive from the Cyber Protect console:
a. Go to Backup Storage > PST files.
b. Select the latest highlighted archive.
c. Click Download in the right pane.
The archive will be downloaded to the default download directory on your computer.
2. Extract the PST files from the archive using the password you set to encrypt the archive.
3. In Microsoft Outlook open or import the PST files. To learn how to do it, refer to Microsoft
documentation.

Recovering email messages and meetings

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up teams you want to recover. Otherwise, skip this step.
3. Expand the Teams node, select All teams, select the team whose email messages or meetings
you want to recover, and then click Recovery.
You can search teams by name. Wildcards are not supported.

609 © Acronis International GmbH, 2003-2024

 4. Select a recovery point.
5. Click Recover > Email messages.
6. Browse to the required item or use search to obtain the list of the required items.
The following search options are available:
l For email messages: search by subject, sender, recipient, and date.
l For meetings: search by event name and date.
7. Select the items that you want to recover, and then click Recover.

Note
You can find the meetings in the Calendar folder.

Additionally, you can do any of the following:

l When an item is selected, click Show content to view its contents, including
attachments. Click the name of an attached file to download it.
l When an email message or a meeting is selected, click Send as email to send the item to the
specified email addresses. You can select the sender and write a text to be added to the
forwarded item.
8. If multiple Microsoft 365 organizations were added to the Cyber Protection service,
click Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must specify the target organization.
9. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
10. Click Start recovery.
11. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
12. Click Proceed to confirm your decision.

Recovering a team site or specific items of a site

1. Click Microsoft 365.
2. If multiple Microsoft 365 organizations were added to the Cyber Protection service, select the
organization whose backed-up teams you want to recover. Otherwise, skip this step.
3. Expand the Teams node, select All teams, select the team whose site you want to recover, and
then click Recovery.
You can search teams by name. Wildcards are not supported.
4. Select a recovery point.
5. Click Recover > Team site.
6. Browse to the required item or use search to obtain the list of the required items.

610 © Acronis International GmbH, 2003-2024

 7. [Optional] To download an item, select the item, click Download, select the location in which you
want to save the item, and then click Save.
8. Select the items that you want to recover, and then click Recover.
9. If multiple Microsoft 365 organizations were added to the Cyber Protection service,
click Microsoft 365 organization to view, change, or specify the target organization.
By default, the original organization and team are selected. If this organization is no longer
registered in the Cyber Protection service, you must specify the target organization.
10. In Recover to team, view, change, or specify the target team.
By default, the original team is selected. If this team does not exist or a non-original organization
is selected, you must specify the target site.
11. Select whether to recover the sharing permissions of the recovered items.
12. Click Start recovery.
13. Select one of the overwriting options:
l Overwrite existing content if it is older
l Overwrite existing content
l Do not overwrite existing content

Note
When you recover OneNote notebooks, both of the options Overwrite existing content if it is
older and Overwrite existing content will result in overwriting the exiting OneNote notebooks.

14. Click Proceed to confirm your decision.

Protecting OneNote notebooks

By default, OneNote notebooks are included in the backups of OneDrive files, Microsoft Teams, and
SharePoint sites.

To exclude the OneNote notebooks from these backups, disable the Include OneNote switch in the
respective backup plan.

Recovering backed-up OneNote notebooks

To learn how to recover a backed-up OneNote notebook, refer to the respective topic:

l For OneDrive backups, see "Recovering an entire OneDrive" (p. 596) or "Recovering OneDrive
files" (p. 597).
l For Teams backups, see "Recovering an entire team" (p. 604), "Recovering team channels or files
in team channels" (p. 605) or "Recovering a team site or specific items of a site" (p. 610).
l For SharePoint site backups, see "Recovering SharePoint Online data" (p. 601).

Supported versions
l OneNote (OneNote 2016 and later)
l OneNote for Windows 10

611 © Acronis International GmbH, 2003-2024

Limitations and known issues
l OneNote notebooks saved in OneDrive or SharePoint are limited to 2 GB. You cannot recover
larger OneNote notebooks to OneDrive or SharePoint targets.
l OneNote notebooks with section groups are not supported.
l In backed-up OneNote notebooks that contain sections with non-default names, the first section
is shown with the default name (such as New section or Untitled section). This might affect the
section order in notebooks with multiple sections.
l When you recover OneNote notebooks, both of the options Overwrite existing content if it is
older and Overwrite existing content will result in overwriting the exiting OneNote notebooks.
l When you recover an entire team, a team site, or the Site Assets folder of a team site, and you
selected the Overwrite existing content if it is older or the Overwrite existing content
option, the default OneNote notebook of that team will not be overwritten. The recovery
succeeds with the warning Failed to update the properties of file '/sites/<Team
name>/SiteAssets/<OneNote notebook name>'.

Protecting Microsoft 365 collaboration app seats

You can use the Advanced Email Security pack, that provides real-time protection for your Microsoft
365, Google Workspace, or Open-Xchange mailboxes:

l Antimalware and anti-spam

l URL scan in emails
l DMARC analysis
l Anti-phishing
l Impersonation protection
l Attachments scan
l Content disarm and reconstruction
l Graph of trust

You can also enable Microsoft 365 collaboration app seats, which allows the protection of Microsoft
365 cloud collaboration applications from content-borne security threats. These applications include
OneDrive, SharePoint, and Teams.

Advanced Email Security can be enabled per workload or per gigabyte and will impact your licensing
model.

To get to Advanced Email Security onboarding from Cyber Protect Cloud console

1. Click Devices > Microsoft 365.

2. Click the Users node and then click the Go to Email Security link at the top right.

Learn more about Advanced Email Security in the Advanced Email Security data sheet.

For configuration instructions, see Advanced Email Security with Perception Point.

612 © Acronis International GmbH, 2003-2024

Protecting Google Workspace data
Note
This feature is not available for tenants in the Compliance mode. For more information, refer to
"Compliance mode" (p. 1031).

What does Google Workspace protection mean?

l Cloud-to-cloud backup and recovery of Google Workspace user data (Gmail mailboxes, Calendars,
Contacts, Google Drives) and Google Workspace Shared drives.
l Granular recovery of emails, files, contacts, and other items.
l Support for several Google Workspace organizations and cross-organization recovery.
l Optional notarization of the backed-up files by means of the Ethereum blockchain database.
When enabled, you can prove that a file is authentic and unchanged since it was backed up.
l Optional full-text search. When enabled, you can search emails by their content.
l Up to 5000 items (mailboxes, Google Drives, and Shared drives) per company can be protected
without performance degradation.
l Backed-up data is automatically compressed and it uses less space on the backup location than
on its original location. The compression level for cloud-to-cloud backups is fixed and
corresponds to the Normal level of non-cloud-to-cloud backups. For more information about
these levels, refer to "Compression level" (p. 436).

Required user rights

In Cyber Protection
In Cyber Protection , you need to be a company administrator acting on a customer tenant level.
Company administrators acting on a unit level, unit administrators, and users cannot back up or
recover Google Workspace data.

In Google Workspace
To add your Google Workspace organization to the Cyber Protection service, you must be signed in
as a Super Admin with enabled API access (Security > API reference > Enable API access in the
Google Admin console).

The Super Admin password is not stored anywhere and is not used to perform backup and
recovery. Changing this password in Google Workspace does not affect Cyber Protection service
operation.

If the Super Admin who added the Google Workspace organization is deleted from Google
Workspace or assigned a role with less privileges, the backups will fail with an error like 'Access
denied'. In this case, repeat the procedure described in "Adding a Google Workspace organization"

613 © Acronis International GmbH, 2003-2024

(p. 614), and specify valid Super Admin credentials. To avoid this case, we recommend that you
create a dedicated Super Admin user for backup and recovery purposes.

About the backup schedule

Because the cloud agent serves multiple customers, it determines the start time for each protection
plan on its own, to ensure an even load during a day and an equal quality of service for all of the
customers.

Each protection plan runs daily at the same time of day.

The default option is Once a day. With the Advanced Backup pack, you can schedule up to six
backups per day. The backups start at approximate intervals that depend on the current load of the
cloud agent, which serves multiple customers in a data center. This ensures even load during the
day and equal quality of service for all customers.

Limitations
l The console shows only users that have an assigned Google Workspace license and a mailbox or
Google Drive.
l Documents in the native Google formats are backed up as generic office documents and are
shown with a different extension in the Cyber Protect console – such as .docx or .pptx, for
example. The documents are converted back to their original format during recovery.
l No more than 10 manual backup runs during an hour.
l No more than 10 simultaneous recovery operations (this number includes both Microsoft 365
and Google Workspace recovery).
l You cannot simultaneously recover items from different recovering points, even though you can
select such items from the search results.
l The backups of deleted Google Workspace user accounts are not automatically deleted from the
cloud storage. These backups are billed for the storage space that they use.
l You cannot apply more than one individual backup plan to the same workload.
l When an individual backup plan and a group backup plan are applied to the same workload, the
settings in the individual plan take precedence.

Logging
Actions with cloud-to-cloud resources, such as viewing the content of backed-up emails,
downloading attachments or files, recovering emails to non-original mailboxes, or sending them as
emails may violate user privacy. These actions are logged in Monitoring > Audit log in the
Management Portal.

Adding a Google Workspace organization

To add a Google Workspace organization to the Cyber Protection service, you need a dedicated
personal Google Cloud project. For more information about how to create and configure such a

614 © Acronis International GmbH, 2003-2024

project, refer to "Creating a personal Google Cloud project" (p. 615).

To add a Google Workspace organization by using a dedicated personal Google Cloud project

1. Log in to the Cyber Protect console as a company administrator.

2. Click Devices > Add > Google Workspace.
3. Enter the email address of a Super Administrator of your Google Workspace account.
For this procedure, it is irrelevant whether 2-Step Verification is enabled for the Super
Administrator email account.
4. Browse for the JSON file that contains the private key of the service account that you created in
your Google Cloud project.
You can also paste the file content as text.

5. Click Confirm.

As a result, your Google Workspace organization appears under the Devices tab in the Cyber
Protect console.

Useful tips
l After adding a Google Workspace organization, the user data and Shared drives in both the
primary domain and all the secondary domains, if there are any, will be backed up. The backed-
up resources will be displayed in one list, and will not be grouped by their domain.
l The cloud agent synchronizes with Google Workspace every 24 hours, starting from the moment
when the organization is added to the Cyber Protection service. If you add or remove a user or
Shared drive, you will not see this change in the Cyber Protect console immediately. To
synchronize the change immediately, select the organization on the Google Workspace page,
and then click Refresh.
For more information about synchronizing the resources of a Google Workspace organization
and the Cyber Protect console, refer to "Discovering Google Workspace resources" (p. 619).
l If you applied a protection plan to the All users or All Shared drives group, the newly added
items will be included in the backup only after the synchronization.
l According to Google policy, when a user or Shared drive is removed from the Google Workspace
graphical user interface, it remains available via an API for a few days. During this period, the
removed item is inactive (grayed out) in the Cyber Protect console and is not backed up. When
the removed item becomes unavailable via the API, it disappears from the Cyber Protect console.
Its backups (if any) can be found at Backup storage > Cloud applications backups.

Creating a personal Google Cloud project

To add your Google Workspace organization to the Cyber Protection service by using a dedicated
Google Cloud project, you need to do the following:

1. Create a new Google Cloud project.

2. Enable the required APIs for this project.
3. Configure the credentials for this project:

615 © Acronis International GmbH, 2003-2024

 a. Configure the OAuth consent screen.
b. Create and configure the service account for the Cyber Protection service.
4. Grant the new project access to your Google Workspace account.

Note
This topic contains a description of third-party user interface that might be subject to change
without prior notice.

To create a new Google Cloud project

1. Sign in to the Google Cloud Platform (console.cloud.google.com) as a Super Administrator.

2. In the Google Cloud Platform console, click the project picker in the upper-left corner.

3. In the screen that opens, select an organization, and then click New project.

4. Specify a name for your new project.

5. Click Create.

As a result, your new Google Cloud project is created.

To enable the required APIs for this project

1. In the Google Cloud Platform console, select your new project.

2. From the navigation menu, select APIs and services > Enabled APIs and services.
3. Disable all the APIs that are enabled by default in this project, one by one:
a. Scroll down the Enabled APIs and services page, and then click the name of an enabled API.
The API/Service details page of the selected API opens.
b. Click Disable API, and then confirm your choice by clicking Disable.
c. [If prompted] Confirm your choice by clicking Confirm.
d. Go back to APIs and services > Enabled APIs and services, and disable the next API.
4. From the navigation menu, select APIs and services > Library.
5. In the API library, enable the following APIs, one by one:
l Admin SDK API
l Gmail API
l Google Calendar API
l Google Drive API
l Google People API

616 © Acronis International GmbH, 2003-2024

 Use the search bar to find the required APIs. To enable an API, click its name, and then click
Enable. To search for the next API, go back to the API library, by selecting APIs and services >
Library from the navigation menu.

To configure the OAuth consent screen

1. From the navigation menu in the Google Cloud Platform, select APIs and services > OAuth
consent screen.
2. In the window that opens, select Internal for user type, and then click Create.
3. In the App name field, specify a name for your application.
4. In the User support email field, enter the Super Administrator email.
5. In the Developer contact information field, enter the Super Administrator email.
6. Leave all other fields blank, and then click Save and continue.
7. On the Scopes page, click Save and continue, without changing anything.
8. On the Summary page, verify your settings, and then click Back to dashboard.

To create and configure the service account for the Cyber Protection service

1. From the navigation menu in the Google Cloud Platform, select IAM & Admin > Service
accounts.
2. Click Create service account.
3. Specify a name for the service account.
4. [Optional] Specify a description for the service account.
5. Click Create and continue.
6. Do not change anything in the Grant this service account access to the project and Grant
users access to this service account steps.
7. Click Done.
The Service accounts page opens.
8. On the Service accounts page, select the new service account, and then under Actions, click
Manage keys.
9. Under Keys, click Add key > Create new key, and then select the JSON key type.
10. Click Create.
As a result, a JSON file with the private key of the service account is automatically downloaded to
your machine. Store this file securely because you need it to add your Google Workspace
organization to the Cyber Protection service.

To grant the new project access to your Google Workspace account

1. From the navigation menu in the Google Cloud Platform, select IAM & Admin > Service
Accounts.
2. In the list, find the service account that you created, and then copy the client ID that is shown in
the OAuth 2.0 Client ID column.
3. Sign in to the Google Admin console (admin.google.com) as a Super Administrator.
4. From the navigation menu, select Security > Access and data control > API controls.

617 © Acronis International GmbH, 2003-2024

5. Scroll down the API controls page, and then under Domain-wide delegation, click Manage
domain-wide delegation.
The Domain-wide delegation page opens.
6. On the Domain-wide delegation page, click Add new.
The Add a new client ID window opens.
7. In the Client ID field, enter the client ID of your service account client.
8. In the OAuth scopes field, copy and paste the following comma-delimited list of scopes:

https://mail.google.com,https://www.googleapis.com/auth/contacts,https://www.googlea
pis.com/auth/calendar,https://www.googleapis.com/auth/admin.directory.user.readonly,
https://www.googleapis.com/auth/admin.directory.domain.readonly,https://www.googleap
is.com/auth/drive,https://www.googleapis.com/auth/gmail.modify

Alternatively, you can add the scopes one per line:

l https://mail.google.com
l https://www.googleapis.com/auth/contacts
l https://www.googleapis.com/auth/calendar
l https://www.googleapis.com/auth/admin.directory.user.readonly
l https://www.googleapis.com/auth/admin.directory.domain.readonly
l https://www.googleapis.com/auth/drive
l https://www.googleapis.com/auth/gmail.modify
9. Click Authorise.

As a result, your new Google Cloud project can access the data in your Google Workspace account.
To back up the data, you need to link this project to the Cyber Protection service. For more
information on how to do this, refer to "To add a Google Workspace organization by using a
dedicated personal Google Cloud project" (p. 615).

If you need to revoke the access of your Google Cloud project to your Google Workspace account,
and respectively the access of the Cyber Protection service, delete the API client that your project
uses.

To revoke access to your Google Workspace account

1. In the Google Admin console (admin.google.com), sign in as a Super Administrator.

2. From the navigation menu, select Security > Access and data control > API controls.
3. Scroll down the API controls page, and then under Domain-wide delegation, click Manage
domain-wide delegation.
The Domain-wide delegation page opens.
4. On the Domain-wide delegation page, select the API client that your project uses, and then click
Delete.
As a result, your Google Cloud project and the Cyber Protection service will not be able to access
your Google Workspace account and back up the data in it.

618 © Acronis International GmbH, 2003-2024

Discovering Google Workspace resources
When you add a Google Workspace organization to the Cyber Protection service, the resources in
this organization, such as mailboxes and Google Drives, are synchronized to the Cyber Protect
console. This operation is called discovery and it is logged in Monitoring > Activities.

After the discovery operation completes, you can see the resources of the Google Workspace
organization on the Devices > Google Workspace tab in the Cyber Protect console, and you can
apply backup plans to them.

An automatic discovery operation runs once a day to keep the list of resources in the Cyber Protect
console up to date. You can also synchronize this list on demand, by re-running a discovery
operation manually.

To re-run a discovery operation manually

1. In the Cyber Protect console, go to Devices > Google Workspace.

2. Select your Google Workspace organization, and then, in the Actions pane, click Refresh.

Note
You can manually run a discovery operation up to 10 times per hour. When this number is reached,
the allowed runs are reset to one per hour, and then every hour an additional run becomes
available, until a total of 10 runs per hour is reached again.

Setting the frequency of Google Workspace backups

By default, Google Workspace backups run once a day and no additional scheduling options are
available.

If the Advanced Backup pack is enabled in your tenant, you can configure more frequent backups.
You can select the number of backups per day, but you cannot configure the backup start time. The
backups start automatically at approximate intervals that depend on the current load of the cloud
agent, which serves multiple customers in a data center. This ensures even load during the day, and
equal quality of service for all customers.

The following options are available.

Scheduling options Approximate interval between each backup

Once a day 24 hours

619 © Acronis International GmbH, 2003-2024

 Scheduling options Approximate interval between each backup

Twice a day (default) 12 hours

3 times a day 8 hours

6 times a day 4 hours

Note
Depending on the load on the cloud agent and possible throttling on the Google Workspace side, a
backup might start later than scheduled or take longer to complete. If a backup takes longer that
the average interval between two backups, the next backup will be rescheduled, which might result
in fewer backups per day than selected. For example, only two backups per day might be able to
complete, even though you selected six per day.

Protecting Gmail data

What items can be backed up?

You can back up Gmail users' mailboxes. A mailbox backup also includes the Calendar and Contacts
data. Optionally, you can choose to back up the shared calendars.

The following items are skipped during a backup:

l The Birthdays, Reminders, Tasks calendars

l Folders attached to calendar events
l The Directory folder in Contacts

The following Calendar items are skipped, due to Google Calendar API limitations:

l Appointment slots
l The conferencing field of an event
l The calendar setting All-day event notifications
l The calendar setting Auto-accept invitations (in calendars for rooms or shared spaces)

The following Contacts items are skipped, due to Google People API limitations:

l The Other contacts folder

l The external profiles of a contact (Directory profile, Google profile)
l The contact field File as

What items can be recovered?

The following items can be recovered from a mailbox backup:

l Mailboxes
l Email folders (According to Google terminology, "labels". Labels are presented in the backup
software as folders, for consistency with other data presentation.)

620 © Acronis International GmbH, 2003-2024

l Email messages
l Calendar events
l Contacts

You can use search to locate items in a backup.

When recovering mailboxes and mailbox items, you can select whether to overwrite the items in the
target location.

Limitations
l Contact photos cannot be recovered
l The Out of office calendar item is recovered as a regular calendar event, due to Google Calendar
API limitations

Selecting Gmail mailboxes

Select the mailboxes as described below, and then specify other settings of the protection plan as
appropriate.

To select Gmail mailboxes

1. Click Google Workspace.

2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose users' data you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up the mailboxes of all users (including mailboxes that will be created in the future),
expand the Users node, select All users, and then click Group backup.
l To back up individual user mailboxes, expand the Users node, select All users, select the
users whose mailboxes you want to back up, and then click Backup.
4. On the protection plan panel:
l Ensure that the Gmail item is selected in What to back up.
l If you want to back up calendars that are shared with the selected users, enable the Include
shared calendars switch.
l Decide whether you need full-text search through the backed-up email messages. To access
this option, click the gear icon > Backup options > Full-text search.

Recovering mailboxes and mailbox items

Recovering mailboxes
1. Click Google Workspace.
2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Users node, select All users, select the user whose mailbox you want to recover,
and then click Recovery.

621 © Acronis International GmbH, 2003-2024

 If the user was deleted, select the user in the Cloud applications backups section of the Backup
storage tab, and then click Show backups.
You can search users and groups by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain mailboxes, select Gmail in Filter by content.

5. Click Recover > Entire mailbox.

6. If multiple Google Workspace organizations are added to the Cyber Protection service, click
Google Workspace organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must select a new target organization from the available registered
organizations.
7. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
You cannot create a new target mailbox during recovery. To recover a mailbox to a new one, first
you need to create the target mailbox in the desired Google Workspace organization, and then
let the cloud agent synchronize the change. The cloud agent automatically synchronizes with
Google Workspace every 24 hours. To synchronize the change immediately, in the Cyber Protect
console, select the organization on the Google Workspace page, and then click Refresh.
8. Click Start recovery.
9. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
10. Click Proceed to confirm your decision.

Recovering mailbox items

1. Click Google Workspace.
2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Users node, select All users, select the user whose mailbox originally contained the
items that you want to recover, and then click Recovery.
If the user was deleted, select the user in the Cloud applications backups section of the Backup
storage tab, and then click Show backups.
You can search users and groups by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain mailboxes, select Gmail in Filter by content.

622 © Acronis International GmbH, 2003-2024

 5. Click Recover > Email messages.
6. Browse to the required folder. If the backup is not encrypted, you can use search to obtain the
list of the required items.
The following search options are available. Wildcards are not supported.
l For email messages: search by subject, sender, recipient, date, attachment name, and
message content.
When searching by date, you can select a start date or an end date (both inclusive), or both
dates to search within a time range.
Searching by attachment name or in the message content gives results only if the Full-text
search option was enabled during backup. You can specify the language of the message
fragment that will be searched as an additional parameter.
l For events: search by title and date.
l For contacts: search by name, email address, and phone number.
7. Select the items that you want to recover. To be able to select folders, click the "recover folders"

icon:
Additionally, you can do any of the following:
l When an item is selected, click Show content to view its contents, including
attachments. Click the name of an attached file to download it.
l Only if the backup is not encrypted, you used search, and selected a single item in the search
results: click Show versions to select the item version to recover. You can select any backed-
up version, earlier or later than the selected recovery point.
8. Click Recover.
9. If multiple Google Workspace organizations were added to the Cyber Protection service, click
Google Workspace organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must select a new target organization from the available registered
organizations.
10. In Recover to mailbox, view, change, or specify the target mailbox.
By default, the original mailbox is selected. If this mailbox does not exist or a non-original
organization is selected, you must specify the target mailbox.
11. In Path, view or change the target folder in the target mailbox. By default, the original folder is
selected.
12. Click Start recovery.
13. Select one of the overwriting options:
l Overwrite existing items
l Do not overwrite existing items
14. Click Proceed to confirm your decision.

623 © Acronis International GmbH, 2003-2024

Protecting Google Drive files

What items can be backed up?

You can back up an entire Google Drive, or individual files and folders. Files are backed up together
with their sharing permissions.

Important
The following items are not backed up:

l The Shared with me folder

l The Computers folder (created by the Backup and Sync client)

Limitations
Out of the Google-specific file formats, Google Docs, Google Sheets, and Google Slides are fully
supported for backup and recovery. Other Google-specific formats might not be fully supported or
might not be supported at all – for example, Google Drawings files are recovered as .svg files,
Google Sites files are recovered as .txt files, Google Jamboard files are recovered as .pdf files, and
Google My Maps files are skipped during a backup.

Note
File formats that are not Google-specific – for example, .txt, .docx, .pptx, .pdf, .jpg, .png, .zip, are
fully supported for backup and recovery.

What items can be recovered?

You can recover an entire Google Drive, or any file or folder that was backed up.

You can choose whether to recover the sharing permissions or let the files inherit the permissions
from the folder to which they are recovered.

Limitations
l Comments in files are not recovered.
l Sharing links for files and folders are not recovered.
l The read-only Owner settings for shared files (Prevent editors from changing access and
adding new people and Disable options to download, print and copy for commenters and
viewers) cannot be changed during a recovery.
l Ownership of a shared folder cannot be changed during a recovery if the Prevent editors from
changing access and adding new people option is enabled for this folder. This setting prevents
the Google Drive API from listing the folder permissions. Ownership of the files in the folder is
recovered correctly.

624 © Acronis International GmbH, 2003-2024

Selecting Google Drive files
Select the files as described below, and then specify other settings of the protection plan as
appropriate.

To select Google Drive files

1. Click Google Workspace.

2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose users' data you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up the files of all users (including users that will be created in the future), expand the
Users node, select All users, and then click Group backup.
l To back up the files of individual users, expand the Users node, select All users, select the
users whose files you want to back up, and then click Backup.
4. On the protection plan panel:
l Ensure that the Google Drive item is selected in What to back up.
l In Items to back up, do one of the following:
o Keep the default setting [All] (all files).
o Specify the files and folders to back up by adding their names or paths.
You can use wildcard characters (*, **, and ?). For more details about specifying paths and
using wildcards, refer to "File filters".
o Specify the files and folders to back up by browsing.
The Browse link is available only when creating a protection plan for a single user.
l [Optional] In Items to back up, click Show exclusions to specify the files and folders to skip
during the backup.
File exclusions override the file selection; i.e. if you specify the same file in both fields, this file
will be skipped during a backup.
l If you want to enable notarization of all files selected for backup, enable the Notarization
switch. For more information about notarization, refer to "Notarization".

Recovering Google Drive and Google Drive files

Recovering an entire Google Drive

1. Click Google Workspace.
2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Users node, select All users, select the user whose Google Drive you want to
recover, and then click Recovery.
If the user was deleted, select the user in the Cloud applications backups section of the Backup
storage tab, and then click Show backups.

625 © Acronis International GmbH, 2003-2024

 You can search users by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain Google Drive files, select Google Drive in Filter by
content.

5. Click Recover > Entire Drive.

6. If multiple Google Workspace organizations were added to the Cyber Protection service, click
Google Workspace organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must select a new target organization from the available registered
organizations.
7. In Recover to drive, view, change, or specify the target user or the target Shared drive.
By default, the original user is selected. If this user does not exist or a non-original organization
is selected, you must specify the target user or the target Shared drive.
If the backup contains shared files, the files will be recovered to the root folder of the target
drive.
8. Select whether to recover the sharing permissions for the files.
9. Click Start recovery.
10. Select one of the overwriting options:

Option Description

Overwrite an If there is a file with the same name in the destination location, and it is older than
existing file if it the source file, the source file will be saved in the destination location, replacing
is older the older version.

Overwrite All existing files in the destination location are overwritten, regardless of their last
existing files modified date.

Do not If there is a file with the same name in the destination location, no changes are
overwrite applied to it, and the source file is not saved to the destination location.
existing files

11. Click Proceed to confirm your decision.

Recovering Google Drive files

1. Click Google Workspace.
2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Users node, select All users, select the user whose Google Drive files you want to
recover, and then click Recovery.
If the user was deleted, select the user in the Cloud applications backups section of the Backup
storage tab, and then click Show backups.

626 © Acronis International GmbH, 2003-2024

 You can search users by name. Wildcards are not supported.
4. Select a recovery point.

Note
To see only the recovery points that contain Google Drive files, select Google Drive in Filter by
content.

5. Click Recover > Files/folders.

6. Browse to the required folder or use search to obtain the list of the required files and folders.
7. Select the files that you want to recover.
If the backup is not encrypted and you selected a single file, you can click Show versions to
select the file version to recover. You can select any backed-up version, earlier or later than the
selected recovery point.
8. If you want to download a file, select the file, click Download, select the location to save the file
to, and then click Save. Otherwise, skip this step.
9. Click Recover.
10. If multiple Google Workspace organizations were added to the Cyber Protection service, click
Google Workspace organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must select a new target organization from the available registered
organizations.
11. In Recover to drive, view, change, or specify the target user or the target Shared drive.
By default, the original user is selected. If this user does not exist or a non-original organization
is selected, you must specify the target user or the target Shared drive.
12. In Path, view or change the target folder in the target user's Google Drive or in the target Shared
drive. By default, the original location is selected.
13. Select whether to recover the sharing permissions for the files.
14. Click Start recovery.
15. Select one of the file overwriting options:

Option Description

Overwrite an If there is a file with the same name in the destination location, and it is older than
existing file if it the source file, the source file will be saved in the destination location, replacing
is older the older version.

Overwrite All existing files in the destination location are overwritten, regardless of their last
existing files modified date.

Do not If there is a file with the same name in the destination location, no changes are
overwrite applied to it, and the source file is not saved to the destination location.
existing files

16. Click Proceed to confirm your decision.

627 © Acronis International GmbH, 2003-2024

Protecting Shared drive files

What items can be backed up?

You can back up an entire Shared drive, or individual files and folders. Files are backed up together
with their sharing permissions.

Important
The Shared with me folder is not backed up.

Limitations
l A Shared drive without members cannot be backed up, due to Google Drive API limitations.
l Out of the Google-specific file formats, Google Docs, Google Sheets, and Google Slides are fully
supported for backup and recovery. Other Google-specific formats might not be fully supported
or might not be supported at all – for example, Google Drawings files are recovered as .svg files,
Google Sites files are recovered as .txt files, Google Jamboard files are recovered as .pdf files,
and Google My Maps files are skipped during a backup.

Note
File formats that are not Google-specific – for example, .txt, .docx, .pptx, .pdf, .jpg, .png, .zip,
are fully supported for backup and recovery.

What items can be recovered?

You can recover an entire Shared drive, or any file or folder that was backed up.

You can choose whether to recover the sharing permissions or let the files inherit the permissions
from the folder to which they are recovered.

The following items are not recovered:

l Sharing permissions for a file that was shared with a user outside the organization are not
recovered if sharing outside the organization is disabled in the target Shared drive.
l Sharing permissions for a file that was shared with a user who is not a member of the target
Shared drive are not recovered if Sharing with non-members is disabled in the target Shared
drive.

Limitations
l Comments in files are not recovered.
l Sharing links for files and folders are not recovered.

Selecting Shared drive files

Select the files as described below, and then specify other settings of the protection plan as
appropriate.

628 © Acronis International GmbH, 2003-2024

To select Shared drive files

1. Click Google Workspace.

2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose users' data you want to back up. Otherwise, skip this step.
3. Do one of the following:
l To back up the files of all Shared drive (including Shared drive that will be created in the
future), expand the Shared drives node, select All Shared drives, and then click Group
backup.
l To back up the files of individual Shared drives, expand the Shared drives node, select All
Shared drives, select the Shared drives to back up, and then click Backup.
4. On the protection plan panel:
l In Items to back up, do one of the following:
o Keep the default setting [All] (all files).
o Specify the files and folders to back up by adding their names or paths.
You can use wildcard characters (*, **, and ?). For more details about specifying paths and
using wildcards, refer to "File filters".
o Specify the files and folders to back up by browsing.
The Browse link is available only when creating a protection plan for a single Shared drive.
l [Optional] In Items to back up, click Show exclusions to specify the files and folders to skip
during the backup.
File exclusions override the file selection; i.e. if you specify the same file in both fields, this file
will be skipped during a backup.
l If you want to enable notarization of all files selected for backup, enable the Notarization
switch. For more information about notarization, refer to "Notarization".

Recovering Shared drive and Shared drive files

Recovering an entire Shared drive

1. Click Google Workspace.
2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Shared drives node, select All Shared drives, select the Shared drive that you want
to recover, and then click Recovery.
If the Shared drive was deleted, select it in the Cloud applications backups section of the
Backup storage tab, and then click Show backups.
You can search Shared drives by name. Wildcards are not supported.
4. Select a recovery point.
5. Click Recover > Entire Shared drive.
6. If multiple Google Workspace organizations were added to the Cyber Protection service, click
Google Workspace organization to view, change, or specify the target organization.

629 © Acronis International GmbH, 2003-2024

 By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must select a new target organization from the available registered
organizations.
7. In Recover to drive, view, change, or specify the target Shared drive or the target user. If you
specify a user, the data will be recovered to this user's Google Drive.
By default, the original Shared drive is selected. If this Shared drive does not exist or a non-
original organization is selected, you must specify the target Shared drive or the target user.
8. Select whether to recover the sharing permissions for the files.
9. Click Start recovery.
10. Select one of the overwriting options:

Option Description

Overwrite an If there is a file with the same name in the destination location, and it is older than
existing file if it the source file, the source file will be saved in the destination location, replacing
is older the older version.

Overwrite All existing files in the destination location are overwritten, regardless of their last
existing files modified date.

Do not If there is a file with the same name in the destination location, no changes are
overwrite applied to it, and the source file is not saved to the destination location.
existing files

11. Click Proceed to confirm your decision.

Recovering Shared drive files

1. Click Google Workspace.
2. If multiple Google Workspace organizations were added to the Cyber Protection service, select
the organization whose backed-up data you want to recover. Otherwise, skip this step.
3. Expand the Shared drives node, select All Shared drives, select the Shared drive that originally
contained the files you want to recover, and then click Recovery.
If the Shared drive was deleted, select it in the Cloud applications backups section of the
Backup storage tab, and then click Show backups.
You can search Shared drives by name. Wildcards are not supported.
4. Select a recovery point.
5. Click Recover > Files/folders.
6. Browse to the required folder or use search to obtain the list of the required files and folders.
7. Select the files that you want to recover.
If the backup is not encrypted and you selected a single file, you can click Show versions to
select the file version to recover. You can select any backed-up version, earlier or later than the
selected recovery point.
8. If you want to download a file, select the file, click Download, select the location to save the file
to, and then click Save. Otherwise, skip this step.

630 © Acronis International GmbH, 2003-2024

 9. Click Recover.
10. If multiple Google Workspace organizations were added to the Cyber Protection service, click
Google Workspace organization to view, change, or specify the target organization.
By default, the original organization is selected. If this organization is no longer registered in the
Cyber Protection service, you must select a new target organization from the available registered
organizations.
11. In Recover to drive, view, change, or specify the target Shared drive or the target user. If you
specify a user, the data will be recovered to this user's Google Drive.
By default, the original Shared drive is selected. If this Shared drive does not exist or a non-
original organization is selected, you must specify the target Shared drive or the target user.
12. In Path, view or change the target folder in the target Shared drive or the target user's Google
Drive. By default, the original location is selected.
13. Select whether to recover the sharing permissions for the files.
14. Click Start recovery.
15. Select one of the file overwriting options:

Option Description

Overwrite an If there is a file with the same name in the destination location, and it is older than
existing file if it the source file, the source file will be saved in the destination location, replacing
is older the older version.

Overwrite All existing files in the destination location are overwritten, regardless of their last
existing files modified date.

Do not If there is a file with the same name in the destination location, no changes are
overwrite applied to it, and the source file is not saved to the destination location.
existing files

16. Click Proceed to confirm your decision.

Notarization
Notarization enables you to prove that a file is authentic and unchanged since it was backed up. We
recommend that you enable notarization when backing up your legal document files or other files
that require proved authenticity.

Notarization is available only for backups of Google Drive files and Google Workspace Shared drive
files.

How to use notarization

To enable notarization of all files selected for backup, enable the Notarization switch when creating
a protection plan.

When configuring recovery, the notarized files will be marked with a special icon, and you can verify
the file authenticity.

631 © Acronis International GmbH, 2003-2024

How it works
During a backup, the agent calculates the hash codes of the backed-up files, builds a hash tree
(based on the folder structure), saves the tree in the backup, and then sends the hash tree root to
the notary service. The notary service saves the hash tree root in the Ethereum blockchain database
to ensure that this value does not change.

When verifying the file authenticity, the agent calculates the hash of the file, and then compares it
with the hash that is stored in the hash tree inside the backup. If these hashes do not match, the file
is considered not authentic. Otherwise, the file authenticity is guaranteed by the hash tree.

To verify that the hash tree itself was not compromised, the agent sends the hash tree root to the
notary service. The notary service compares it with the one stored in the blockchain database. If the
hashes match, the selected file is guaranteed to be authentic. Otherwise, the software displays a
message that the file is not authentic.

Verifying file authenticity with Notary Service

If notarization was enabled during backup, you can verify the authenticity of a backed-up file.

To verify the file authenticity

1. Do one of the following:

l To verify the authenticity of a Google Drive file, select the file as described in steps 1-7 of the
"Recovering Google Drive files" section.
l To verify the authenticity of a Google Workspace Shared drive file, select the file as described
in steps 1-7 of the "Recovering Shared drive files" section.

2. Ensure that the selected file is marked with the following icon: . This means that the file is
notarized.
3. Do one of the following:
l Click Verify.
The software checks the file authenticity and displays the result.
l Click Get certificate.
A certificate that confirms the file notarization is opened in a web browser window. The
window also contains instructions that allow you to verify the file authenticity manually.

Search in cloud-to-cloud backups

When recovering data, you can search for specific backed-up items instead of browsing the backup
archive.

In non-encrypted backups, search is always available. Only enhanced (index-based) search is

supported.

632 © Acronis International GmbH, 2003-2024

The index-based search is faster and provides additional options, such as showing versions of the
backed-up items, searching in attachment names, and full-text search in Gmail backups.

In encrypted backups, you can also enable enhanced (index-based) search. If you do not enable the
enhanced search, basic search will be available for backups of Microsoft 365 mailboxes. For all other
workloads, search will not be available.

The table below summarizes the available options for encrypted backups.

Workload What to Enhanced search is disabled Enhanced search is enabled

type recover

Microsoft 365 workloads

Mailbox Email Basic (non-index based) search is Enhanced (index-based) search is

messages available available

OneDrive Files/folders Search is not available Enhanced (index-based) search is

available

SharePoint SharePoint Search is not available Enhanced (index-based) search is

site files available

Teams Channels Search is not available Enhanced (index-based) search is

available

Email Basic (non-index based) search is Enhanced (index-based) search is

messages available available

Team site Search is not available Enhanced (index-based) search is

available

Google Workspace workloads

Mailbox Email Search is not available Enhanced (index-based) search is

messages available

Google Drive Files/folders Search is not available Enhanced (index-based) search is

available

Shared Files/folders Search is not available Enhanced (index-based) search is

Drives available

Full-text search
Full-text search is available only for Gmail backups, and it is enabled by default. With it, you can
search in the body text of the backed-up emails. If this option is disabled, you can search only by
subject, sender, recipient, and date.

A full-text search index takes between 10 and 30 percent of the storage space occupied by the Gmail
backup. An index without full-text search data is significantly smaller. To save storage space, you can
disable the full-text search and clear the portion of the index that contains the full-text search data.

633 © Acronis International GmbH, 2003-2024

Search indexes
Search indexes provide enhanced search capabilities in cloud-to-cloud backup archives.

The archives are automatically indexed after each backup operation. The indexing process does not
affect the backup performance because indexing and backing up are done by different software
components.

Showing search results becomes available after the indexing operation completes, which might take
up to 24 hours. Indexing the first backup, which is full, usually takes longer than indexing the
successive incremental backups.

All indexes contain metadata that supports the main searching functionality— search by subject,
sender, recipient, or date. The indexes for Gmail backups contain additional data if full-text search is
enabled.

Checking the size of a search index

Search indexes grow bigger with time. The indexes for backup archives in which full-text search is
enabled, might take up to 30 percent of the archive size.

To check the size of a search index

1. Log in to the Cyber Protect console as administrator.

2. On the Backup storage tab, click Cloud applications backup.
3. Check the value in the Index size column.

Updating, rebuilding, or deleting indexes

To troubleshoot search-related issues in cloud-to-cloud backups, you can update, rebuild, or delete
search indexes.

Note
We recommend that you contact the Support team before updating, rebuilding, or deleting an
index.

To update, rebuild, or delete an index

1. Log in to the Cyber Protect console as an administrator.

2. On the Backup storage tab, click Cloud applications backup.
Select the archive the index of which you want to update, rebuild, or delete.
The availability of these actions depend on the administrator level and role, as follows:

634 © Acronis International GmbH, 2003-2024

 Account Role Can update Can rebuild Can delete
level index index index

Partner Company administrator + + +

tenant
Protection cyber administrator + - -

Protection administrator + - -

Protection read-only administrator - - -

Customer Company administrator + - -

tenant
Protection administrator + - -

Protection read-only administrator - - -

Unit Unit administrator + - -

Protection administrator + - -

Protection read-only administrator - - -

3. In the Actions pane, select the action that you want to perform:
l Update index—the recovery points in the archive are checked, and the missing indexes are
added.
l Rebuild index—the indexes for all recovery points in the archive are deleted, and then the
indexes are created again.
l Delete index—the indexes for all recovery points in the archive are deleted.
4. [For encrypted archives] Specify the encryption password, and then click OK.
5. Select the scope of the action, and then click OK.
Depending on the archive and the selected action, one or more of the following options are
available:
l Metadata only
l Content only
l Metadata and content search

Enabling enhanced search in encrypted backups

When creating a backup plan for encrypted cloud-to-cloud backup, you can enable enhanced (index-
based) search.

If you do not enable enhanced search, basic search will be available for backups of Microsoft 365
mailboxes. For all other workloads, search will not be available. For more information about the
available options, see "Search in cloud-to-cloud backups" (p. 632).

Note
This functionality is available in selected data centers and might not be accessible to all customers.

635 © Acronis International GmbH, 2003-2024

To enable search in encrypted backups

1. When creating a backup plan, enable the Encryption switch.

2. Specify and confirm the encryption password.
3. Select the Allow enhanced search in encrypted backups check box.
4. Click Done.

Note
You cannot disable encryption or change the encryption password later. To create a non-encrypted
backup or change the encryption password, create a new backup plan.

Enabling or disabling enhanced search in existing plans

You can edit an existing plan for encrypted backup to enable or disable enhanced (index-
based) search.

If you do not enable enhanced search, basic search will be available for backups of Microsoft 365
mailboxes. For all other workloads, search will not be available. For more information about the
available options, see "Search in cloud-to-cloud backups" (p. 632).

In non-encrypted backups, enhanced search is always available. This option cannot be disabled.

To enable or disable enhanced search in encrypted backups

1. When editing a backup plan in which encryption is enabled, click the gear icon in the upper right
corner.
2. On the Search options tab, toggle the switch as required.
3. Click Done.
4. Click Save settings.

Note
If you re-enable enhanced search, all archives created by this backup plan will be indexed again.
This is a time-consuming operation.

Disabling full-text search for Gmail backups

Full-text search is available only for Gmail backups, and it is enabled by default. With it, you can
search in the body text of the backed-up emails. If this option is disabled, you can search only by
subject, sender, recipient, and date.

You might want to disable full-text search if you need to keep the size of the search index minimal.

To disable full-text search

1. When creating or editing a backup plan, click the gear icon in the upper right corner.
2. On the Full-text search tab, disable the switch.
3. Click Done.

636 © Acronis International GmbH, 2003-2024

4. [When creating a plan] Click Apply.
5. [When editing a plan] Click Save settings.

Note
If you re-enable full-text search, all archives created by this backup plan will be indexed again. This
is a time-consuming operation.

Protecting Oracle Database

Note
This feature is available with the Advanced Backup pack.

Protection of Oracle Database is described in a separate document available at https://dl.managed-

protection.com/u/pdf/OracleBackup_whitepaper_en-US.pdf

Protecting SAP HANA

Note
This feature is available with the Advanced Backup pack.

Protection of SAP HANA is described in a separate document available at https://dl.managed-

protection.com/u/pdf/SAP_HANA_backup_whitepaper_en-US.pdf

Protecting MySQL and MariaDB data

You can protect MySQL or MariaDB data with application-aware backup. It collects application
metadata and allows granular recovery on the instance, database, or table level.

Note
Application-aware backup of MySQL or MariaDB data is available with the Advanced Backup pack.

To protect a physical or virtual machine that runs MySQL or MariaDB instances with application-
aware backup, you need to install Agent for MySQL/MariaDB on this machine. Agent for
MySQL/MariaDB is bundled with Agent for Linux (64-bit) and therefore can be installed only on 64-
bit Linux-based operating systems. See "Supported operating systems and environments" (p. 23).

To download the Agent for Linux (64-bit) installation file

1. Log in to the Cyber Protect console.

2. Click the account icon in the upper-right corner, and then select Downloads.
3. Click Agent for Linux (64-bit).
The installation file is downloaded to your machine. To install the agent, proceed as described in
"Installing protection agents in Linux" (p. 75) or "Unattended installation or uninstallation in

637 © Acronis International GmbH, 2003-2024

 Linux" (p. 100). Ensure that you select Agent for MySQL/MariaDB, which is an optional
component.

To recover databases and tables to a live instance, Agent for MySQL/MariaDB needs a temporary
storage to operate. By default, the /tmp directory is used. You can change this directory by setting
the ACRONIS_MYSQL_RESTORE_DIR environment variable.

Limitations
l MySQL or MariaDB clusters are not supported.
l MySQL or MariaDB instances running in Docker containers are not supported.
l MySQL or MariaDB instances running on operating systems that use BTRFS file system are not
supported.
l System databases (sys, mysql, information-schema, and performance_schema) and databases that
do not contain any tables cannot be recovered to live instances. However, these databases can be
recovered as files, when recovering the whole instance.
l Recovery is supported only to target instances of the same version as the backed-up instance or
later, with the following restrictions:
o Recovery from MySQL 5.x instances to MySQL 8.x instances is not supported.
o Recovery to a later MySQL 5.x version (including the minor versions) is supported only via
recovery of the whole instance as files. Before attempting recovery, consult the official MySQL
upgrade guide for the target version, for example, the MySQL 5.7 upgrade guide.
l Recovery from backups stored on Secure Zone is not supported.
l Databases and tables cannot be recovered by Agent for MySQL/MariaDB that is running on a
machine on which AppArmor is installed. You can still recover an instance as files, or the entire
machine.
l Recovery to target databases that are configured with symbolic links is not supported. You can
recover the backed-up databases as new databases, by changing their name.

Known issues
If you encounter issues while recovering data from password protected Samba shares, log out from
the Cyber Protect console, and then log in back to it. Select the desired recovery point, and then click
MySQL/MariaDB databases. Do not click Entire machine or Files/folders.

Configuring an application-aware backup

Prerequisites
l At least one MySQL or MariaDB instance must be running on the selected machine.
l On the machine where the MySQL or MariaDB instance is running, the protection agent must be
started under the root user.
l Application-aware backup is available only when the Entire machine is selected as a backup
source in the protection plan.

638 © Acronis International GmbH, 2003-2024

l The Sector-by-sector backup option must be disabled in the protection plan. Otherwise, it is
impossible to recover application data.

To configure an application-aware backup

1. In the Cyber Protect console, select one or more machines on which MySQL or MariaDB
instances are running.
You can have one or more instances on each machine.
2. Create a protection plan with the backup module enabled.
3. In What to back up, select Entire machine.
4. Click Application backup, and then enable the switch next to MySQL/MariaDB Server.
5. Select how to specify the MySQL or MariaDB instances:
l For all workloads
Use this option if you run instances with identical configurations on multiple servers. The
same connection parameters and access credentials will be used for all instances.
l For specific workloads
Use this option to specify the connection parameters and access credentials for each instance.
6. Click Add instance to configure the connection parameters and access credentials.
a. Select the connection type, and then specify the following:
l [For TCP socket] IP address and port.
l [For Unix socket] Socket path.
b. Specify the credentials of a user account that has the following privileges for the instance:
l FLUSH_TABLES or RELOAD for all databases and tables (*.*)
l SELECT for the information_schema.tables
c. Click OK.
7. Click Done.

Recovering data from an application-aware backup

From an application-aware backup, you can recover MySQL or MariaDB instances, databases, and
tables. You can also recover the entire server on which the instances are running, or files and
folders from this server.

The table below summarizes all recovery options.

What to Recover Recover to

recover as

MySQL Entire Machine* on which Agent for Linux is installed

Server machine

MariaDB
Server

MySQL Files or Machine* on which Agent for Linux is installed

Server folders

639 © Acronis International GmbH, 2003-2024

 What to Recover Recover to
recover as

MariaDB
Server

Instance Files Machine* on which Agent for MySQL/MariaDB is installed

Database The same Machine* on which Agent for MySQL/MariaDB is installed

database
l Original instance
New l Another instance
database l Original database
l New database

Table The same Machine* on which Agent for MySQL/MariaDB is installed

table
l Original instance
New table l Another instance
l Original database
l Original table
l New table

* A virtual machine with an agent inside is treated as a physical machine from the backup
standpoint.

Recovering the entire server

To learn how to recover the entire server on which MySQL or MariaDB instances are running, refer
to "Recovering a machine" (p. 475).

Recovering instances
From an application-aware backup, you can recover MySQL or MariaDB instances as files.

To recover an instance

1. In the Cyber Protect console, select the machine that originally contained the data that you want
to recover.
2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Do one of the following:
l If the backup location is cloud or shared storage (that is, other agents can access it), click
Select machine, select an online machine that has Agent for MySQL/MariaDB, and then select
a recovery point.
l Select a recovery point on the Backup storage tab.
The machine chosen for browsing in either of the above actions becomes a target machine for
the recovery.

640 © Acronis International GmbH, 2003-2024

 4. Click Recover > MySQL/MariaDB databases.
5. Select the instance that you want to recover, and then click Recover as files.
6. Under Path, select the directory to which the files will be recovered.
7. Click Start recovery.

Recovering databases
From an application-aware backup, you can recover databases to live MySQL or MariaDB instances.

1. In the Cyber Protect console, select the machine that originally contained the data that you want
to recover.
2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Do one of the following:
l If the backup location is cloud or shared storage (that is, other agents can access it), click
Select machine, select an online machine that has Agent for MySQL/MariaDB, and then select
a recovery point.
l Select a recovery point on the Backup storage tab.
The machine chosen for browsing in either of the above actions becomes a target machine for
the recovery.
4. Click Recover > MySQL/MariaDB databases.
5. Click the name of the desired instance to drill down to its databases.
6. Select one or more databases that you want to recover.
7. Click Recover.
8. Click Target MySQL/MariaDB instance to specify the connection parameters and access
credentials for the target instance.
l Verify the instance to which you want to recover data. By default, the original instance is
selected.
l Specify the credentials of a user account that can access the target instance. This user account
must have the following privileges assigned for all databases and tables (*.*):
o INSERT
o CREATE
o DROP
o LOCK_TABLES
o ALTER
o SELECT
l Click OK.
9. Verify the target database.
By default, the original database is selected.
To recover a database as a new one, click the name of the target database and change it. This
action is only available when you recover a single database.
10. Under Overwrite existing databases, select the overwriting mode.

641 © Acronis International GmbH, 2003-2024

 By default, overwriting is enabled and the backed-up database will replace the target database
that has the same name.
If overwriting is disabled, the backed-up database will be skipped during the recovery operation
and will not replace the target database that has the same name.
11. Click Start recovery.

Recovering tables
From an application-aware backup, you can recover tables to live MySQL or MariaDB instances.

1. In the Cyber Protect console, select the machine that originally contained the data that you want
to recover.
2. Click Recovery.
3. Select a recovery point. Note that recovery points are filtered by location.
If the machine is offline, the recovery points are not displayed. Do one of the following:
l If the backup location is cloud or shared storage (that is, other agents can access it), click
Select machine, select an online machine that has Agent for MySQL/MariaDB, and then select
a recovery point.
l Select a recovery point on the Backup storage tab.
The machine chosen for browsing in either of the above actions becomes a target machine for
the recovery.
4. Click Recover > MySQL/MariaDB databases.
5. Click the name of the desired instance to drill down to its databases.
6. Click the name of the desired database to drill down to its tables.
7. Select one or more tables that you want to recover.
8. Click Recover.
9. Click Target MySQL/MariaDB instance to specify the connection parameters and access
credentials for the target instance.
l Verify the instance to which you want to recover data. By default, the original instance is
selected.
l Specify the credentials of a user account that can access the target instance. This user account
must have the following privileges assigned for all databases and tables (*.*):
o INSERT
o CREATE
o DROP
o LOCK_TABLES
o ALTER
o SELECT
l Click OK.
10. Verify the target table.
By default, the original table is selected.

642 © Acronis International GmbH, 2003-2024

 To recover a table as a new one, click the name of the target table and change it. This action is
only available when you recover a single table.
11. Under Overwrite existing tables, select the overwriting mode.
By default, overwriting is enabled and the backed-up table will replace the target table that has
the same name.
If overwriting is disabled, the backed-up table will be skipped during the recovery operation and
will not replace the target table that has the same name.
12. Click Start recovery.

Recovering stored routines

When you recover a whole MySQL instance, the stored routines are automatically recovered.

When you recover an individual database to a non-original instance or recover it as a new database,
the stored routines are not automatically recovered. You can recover them manually, by exporting
them in an SQL file, and then adding them to the recovered database.

To export the stored routines and add them to a recovered database

1. On the machine with the original MySQL instance, open Terminal.

2. Run the following command to export the stored routines.
3.
mysqldump -p [source_database_name] --routines --no-create-info --no-data >
[exported_db_routines.sql]

4. On the machine where the database is recovered, open the MySQL command line client.
5. Run the following commands to add the routines to the recovered database.

mysql> use [recovered_database_name];

mysql> source [path_to_exported_db_routines.sql];

Protecting websites and hosting servers

Protecting websites
A website can be corrupted as a result of unauthorized access or a malware attack. Back up your
website if you want to easily revert it to a healthy state, in case of corruption.

What do I need to back up a website?

The website must be accessible via the SFTP or SSH protocol. You do not need to install an agent,
just add a website as described later in this section.

What items can be backed up?

You can back up the following items:

643 © Acronis International GmbH, 2003-2024

l Website content files
All files accessible to the account you specify for the SFTP or SSH connection.
l Linked databases (if any) hosted on MySQL servers.
All databases accessible to the MySQL account you specify.

If your website employs databases, we recommend that you back up both the files and the
databases, to be able to recover them to a consistent state.

Limitations
l The only backup location available for website backup is the cloud storage.
l It is possible to apply several protection plans to a website, but only one of them can run on a
schedule. Other plans need to be started manually.
l The only available backup option is "Backup file name".
l The website protection plans are not shown on the Management > Protection planstab.

Backing up a website
To add a website

1. Click Devices > Add.

2. Click Website.
3. Configure the following access settings for the website:
l In Website name, create and type a name for your website. This name will be displayed in the
Cyber Protect console.
l In Host, specify the host name or IP address that will be used to access the website via SFTP
or SSH. For example, my.server.com or 10.250.100.100.
l In Port, specify the port number.
l In User name and Password, specify the credentials of the account that can be used to
access the website via SFTP or SSH.

Important
Only the files that are accessible to the specified account will be backed up.

Instead of a password, you can specify your private SSH key. To do this, select the Use SSH
private key instead of password check box, and then specify the key.
4. Click Next.
5. If your website uses MySQL databases, configure the access settings for the databases.
Otherwise, click Skip.
a. In Connection type, select how to access the databases from the cloud:
l Via SSH from host—The databases will be accessed via the host specified in step 3.
l Direct connection—The databases will be accessed directly. Choose this setting only if the
databases are accessible from the Internet.
b. In Host, specify the name or IP address of the host where the MySQL server is running.

644 © Acronis International GmbH, 2003-2024

 c. In Port, specify the port number for the TCP/IP connection to the server. The default port
number is 3306.
d. In User name and Password, specify the MySQL account credentials.

Important
Only the databases that are accessible to the specified account will be backed up.

e. Click Create.
The website appears in the Cyber Protect console under Devices > Websites.

To change the connection settings

1. Select the website under Devices > Websites.

2. Click Details.
3. Click the pencil icon next to the website or the database connection settings.
4. Do the necessary changes, and then click Save.

To create a protection plan for websites

1. Select a website or several websites under Devices > Websites.

2. Click Protect.
3. [Optional] Enable backup of databases.
If several websites are selected, backup of databases is disabled by default.
4. [Optional] Change the retention rules.
5. [Optional] Enable encryption of backups.
6. [Optional] Click the gear icon to edit the Backup file name option. This makes sense in two
cases:
l If you backed up this website earlier and want to continue the existing sequence of backups
l If you want to see the custom name on the Backup storage tab
7. Click Apply.

You can edit, revoke, and delete protection plans for websites in the same way as for machines.
These operations are described in "Operations with protection plans".

Recovering a website
To recover a website

1. Do one of the following:

l Under Devices > Websites, select the website that you want to recover, and then click
Recovery.
You can search websites by name. Wildcards are not supported.
l If the website was deleted, select it in the Cloud applications backups section of the Backup
storage tab, and then click Show backups.
To recover a deleted website, you need to add the target site as a device.
2. Select the recovery point.

645 © Acronis International GmbH, 2003-2024

3. Click Recover, and then select what you want to recover: Entire website, Databases (if any), or
Files/folders.
To ensure that your website is in a consistent state, we recommend that you recover both files
and databases, in any order.
4. Depending on your choice, follow one of the procedures described below.

To recover the entire website

1. In Recover to website, view or change the target website.

By default, the original website is selected. If it does not exist, you must select the target website.
2. Select whether to recover the sharing permissions of the recovered items.
3. Click Start recovery, and then confirm the action.

To recover the databases

1. Select the databases that you want to recover.

2. If you want to download a database as a file, click Download, select the location to save the file
to, and then click Save. Otherwise, skip this step.
3. Click Recover.
4. In Recover to website, view or change the target website.
By default, the original website is selected. If it does not exist, you must select the target website.
5. Click Start recovery, and then confirm the action.

To recover the website files/folders

1. Select the files/folders that you want to recover.

2. If you want to save a file, click Download, select the location to save the file to, and then click
Save. Otherwise, skip this step.
3. Click Recover.
4. In Recover to website, view or change the target website.
By default, the original website is selected. If it does not exist, you must select the target website.
5. Select whether to recover the sharing permissions of the recovered items.
6. Click Start recovery, and then confirm the action.

Protecting web hosting servers

You can protect Linux-based web hosting servers that run Plesk, cPanel, DirectAdmin, VirtualMin , or
ISPManager control panels. Servers that run web hosting control panels from other vendors are
protected as regular workloads.

Quotas
Servers that run Plesk, cPanel, DirectAdmin, VirtualMin , or ISPManager control panels are
considered web hosting servers. Each backed-up web hosting server consumes the Web hosting
servers quota. If this quota is disabled or the overage for this quota is exceeded, a quota will be
assigned as follows or the backups will fail:

646 © Acronis International GmbH, 2003-2024

l If the server is physical, the Servers quota will be used. If this quota is disabled or the overage for
this quota is exceeded, the backup will fail.
l If the server is virtual, the Virtual machines quota will be used. If this quota is disabled or the
overage for this quota is exceeded, the backup will fail.

Integrations for DirectAdmin, cPanel, and Plesk

Web hosting administrators that use DirectAdmin, Plesk or cPanel, can integrate these control
panels with the Cyber Protection service to gain several powerful capabilities, including:

l Backing up entire web hosting server to the cloud storage with disk-level backup
l Recovering the entire server, including all websites and accounts
l Performing granular recovery and downloading of accounts, websites, individual files, mailboxes,
or databases
l Enabling resellers and customers to perform self-service recovery of their own data

To perform the integration, you need to use a Cyber Protection service extension. For detailed
information, please refer to the corresponding integration guides:
l DirectAdmin Integration Guide
l WHM and cPanel Integration Guide
l Plesk Integration Guide

Special operations with virtual machines

Running a virtual machine from a backup (Instant Restore)

You can run a virtual machine from a disk-level backup that contains an operating system. This
operation, also known as instant restore, enables you to spin up a virtual server in seconds. The
virtual disks are emulated directly from the backup and thus do not consume space on the
datastore (storage). The storage space is required only to keep changes to the virtual disks.

We recommend that you leave this temporary virtual machine working for up to three days. Then,
you can completely remove it or convert it to a regular virtual machine (finalize) without downtime.

As long as the temporary virtual machine exists, retention rules cannot be applied to the backup
being used by that machine. Backups of the original machine can continue to run.

Usage examples
l Disaster recovery
Instantly bring a copy of a failed machine online.
l Testing a backup
Run the machine from the backup and ensure that the guest OS and applications are functioning
properly.
l Accessing application data

647 © Acronis International GmbH, 2003-2024

 While the machine is running, use application's native management tools to access and extract
the required data.

Prerequisites
l At least one Agent for VMware or Agent for Hyper-V must be registered in the Cyber Protection
service.
l The backup can be stored in a network folder or in a local folder of the machine where Agent for
VMware or Agent for Hyper-V is installed. If you select a network folder, it must be accessible
from that machine. A virtual machine can also be run from a backup stored in the cloud storage,
but it works slower because this operation requires intense random-access reading from the
backup.
l The backup must contain an entire machine or all of the volumes that are required for the
operating system to start.
l Backups of both physical and virtual machines can be used. Backups of Virtuozzo containers
cannot be used.
l Backups that contain Linux logical volumes (LVM) must be created by Agent for VMware or Agent
for Hyper-V. The virtual machine must be of the same type as the original machine (ESXi or Hyper-
V).

Running the machine

1. Do one of the following:
l Select a backed-up machine, click Recovery, and then select a recovery point.
l Select a recovery point on the Backup storage tab.
2. Click Run as VM.
The software automatically selects the host and other required parameters.

648 © Acronis International GmbH, 2003-2024

3. [Optional] Click Target machine, and then change the virtual machine type (ESXi or Hyper-V),
the host, or the virtual machine name.
4. [Optional] Click Datastore for ESXi or Path for Hyper-V, and then select the datastore for the
virtual machine.
Changes to the virtual disks accumulate while the machine is running. Ensure that the selected
datastore has enough free space. If you are planning to preserve these changes by making the
virtual machine permanent, select a datastore that is suitable for running the machine in
production.
5. [Optional] Click VM settings to change the memory size and network connections of the virtual
machine.
6. [Optional] Select the VM power state (On/Off).
7. Click Run now.

As a result, the machine appears in the web interface with one of the following icons: or

. Such virtual machines cannot be selected for backup.

649 © Acronis International GmbH, 2003-2024

Note
You can perform the Run as virtual machine (Instant Restore) operation with backups in Microsoft
Azure. However, this operation results in significant egress traffic, which will be added to your
Microsoft Azure subscription bill. Typical egress traffic for a Windows machine running from a
Microsoft Azure backup would be approximately 5 GB from virtual machine power up until login.

Deleting the machine

We recommend that you do not delete a temporary virtual machine directly in vSphere/Hyper-V.
This might lead to artifacts in the web interface. Also, the backup from which the machine was
running may remain locked for a while (it cannot be deleted by retention rules).

To delete a virtual machine that is running from a backup

1. On the All devices tab, select a machine that is running from a backup.
2. Click Delete.

The machine is removed from the web interface. It is also removed from the vSphere or Hyper-V
inventory and datastore (storage). All changes that occurred to the data while the machine was
running are lost.

Finalizing the machine

While a virtual machine is running from a backup, the virtual disks' content is taken directly from
that backup. Therefore, the machine will become inaccessible or even corrupted if the connection is
lost to the backup location or to the protection agent.

You have the option to make this machine permanent, i.e. recover all of its virtual disks, along with
the changes that occurred while the machine was running, to the datastore that stores these
changes. This process is named finalization.

Finalization is performed without downtime. The virtual machine will not be powered off during
finalization.

The location of the final virtual disks is defined in the parameters of the Run as VM operation
(Datastore for ESXi or Path for Hyper-V). Prior to starting the finalization, ensure that free space,
sharing capabilities, and performance of this datastore are suitable for running the machine in
production.

Note
Finalization is not supported for Hyper-V running in Windows Server 2008/2008 R2 and Microsoft
Hyper-V Server 2008/2008 R2 because the necessary API is missing in these Hyper-V versions.

To finalize a machine that is running from a backup

1. On the All devices tab, select a machine that is running from a backup.
2. Click Finalize.

650 © Acronis International GmbH, 2003-2024

3. [Optional] Specify a new name for the machine.
4. [Optional] Change the disk provisioning mode. The default setting is Thin.
5. Click Finalize.

The machine name changes immediately. The recovery progress is shown on the Activities tab.
Once the recovery is completed, the machine icon changes to that of a regular virtual machine.

What you need to know about finalization

Finalization vs. regular recovery

The finalization process is slower than a regular recovery for the following reasons:

l During a finalization, the agent performs random access to different parts of the backup. When
an entire machine is being recovered, the agent reads data from the backup sequentially.
l If the virtual machine is running during the finalization, the agent reads data from the backup
more often, to maintain both processes simultaneously. During a regular recovery, the virtual
machine is stopped.

Finalization of machines running from cloud backups

Because of intensive access to the backed-up data, the finalization speed highly depends on the
connection bandwidth between the backup location and the agent. The finalization will be slower
for backups located in the cloud as compared to local backups. If the Internet connection is very
slow or unstable, the finalization of a machine running from a cloud backup may fail. We
recommend that you run virtual machines from local backups if you are planning to perform
finalization, and have the choice.

Note
Finalization speed depends on whether the agent is connected to a VMware ESXi host or vCenter, as
described in step 3 of "Configuring the virtual appliance" (p. 132). Connection to a VMware vCenter
can slow down the finalization operation due to the specifics of VMware APIs. To speed up the
finalization operation, use a separate Agent for VMware for performing the Run as VM operation
followed by finalization, where this Agent will be connected to an ESXi host instead of a vCenter.

Working in VMware vSphere

This section describes operations that are specific for VMware vSphere environments.

Replication of virtual machines

Replication is available only for VMware ESXi virtual machines.

Replication is the process of creating an exact copy (replica) of a virtual machine, and then
maintaining the replica in sync with the original machine. By replicating a critical virtual machine,
you will always have a copy of this machine in a ready-to-start state.

651 © Acronis International GmbH, 2003-2024

The replication can be started manually or on the schedule you specify. The first replication is full
(copies the entire machine). All subsequent replications are incremental and are performed with
Changed Block Tracking, unless this option is disabled.

Replication vs. backing up

Unlike scheduled backups, a replica keeps only the latest state of the virtual machine. A replica
consumes datastore space, while backups can be kept on a cheaper storage.

However, powering on a replica is much faster than a recovery and faster than running a virtual
machine from a backup. When powered on, a replica works faster than a VM running from a backup
and does not load the Agent for VMware.

Usage examples
l Replicate virtual machines to a remote site.
Replication enables you to withstand partial or complete datacenter failures, by cloning the
virtual machines from a primary site to a secondary site. The secondary site is usually located in a
remote facility that is unlikely to be affected by environmental, infrastructure, or other factors
that might cause the primary site failure.
l Replicate virtual machines within a single site (from one host/datastore to another).
Onsite replication can be used for high availability and disaster recovery scenarios.

What you can do with a replica

l Test a replica
The replica will be powered on for testing. Use vSphere Client or other tools to check if the replica
works correctly. Replication is suspended while testing is in progress.
l Failover to a replica
Failover is a transition of the workload from the original virtual machine to its replica. Replication
is suspended while a failover is in progress.
l Back up the replica
Both backup and replication require access to virtual disks, and thus impact the performance of
the host where the virtual machine is running. If you want to have both a replica and backups of a
virtual machine, but don't want to put additional load on the production host, replicate the
machine to a different host, and set up backups of the replica.

Limitations
l The following types of virtual machines cannot be replicated:
o Fault-tolerant machines running on ESXi 5.5 and lower.
o Machines running from backups.
o Replicas of virtual machines.
l Some hardware changes, such as adding a network interface card (NIC) to the ESXi host or
removing a NIC from it, result in changing the internal IDs of the host. This change affects the VM

652 © Acronis International GmbH, 2003-2024

 replication plans. After such a change, you must recreate the VM replication plans in which the
ESXi host is selected as a source or target. Otherwise, the VM replication plans will fail.

Creating a replication plan

A replication plan must be created for each machine individually. It is not possible to apply an
existing plan to other machines.

To create a replication plan

1. Select a virtual machine to replicate.

2. Click Replication.
The software displays a new replication plan template.
3. [Optional] To modify the replication plan name, click the default name.
4. Click Target machine, and then do the following:
a. Select whether to create a new replica or use an existing replica of the original machine.
b. Select the ESXi host and specify the new replica name, or select an existing replica.
The default name of a new replica is [Original Machine Name]_replica.
c. Click OK.
5. [Only when replicating to a new machine] Click Datastore, and then select the datastore for the
virtual machine.
6. [Optional] Click Schedule to change the replication schedule.
By default, replication is performed on a daily basis, Monday to Friday. You can select the time to
run the replication.
If you want to change the replication frequency, move the slider, and then specify the schedule.
You can also do the following:
l Set a date range for when the schedule is effective. Select the Run the plan within a date
range check box, and then specify the date range.
l Disable the schedule. In this case, replication can be started manually.
7. [Optional] Click the gear icon to modify the replication options.
8. Click Apply.
9. [Optional] To run the plan manually, click Run now on the plan panel.

As a result of running a replication plan, the virtual machine replica appears in the All devices list

with the following icon:

Testing a replica
To prepare a replica for testing

1. Select a replica to test.

2. Click Test replica.
3. Click Start testing.

653 © Acronis International GmbH, 2003-2024

4. Select whether to connect the powered-on replica to a network. By default, the replica will not be
connected to a network.
5. [Optional] If you chose to connect the replica to the network, select the Stop original virtual
machine check box to stop the original machine before powering on the replica.
6. Click Start.

To stop testing a replica

1. Select a replica for which testing is in progress.

2. Click Test replica.
3. Click Stop testing.
4. Confirm your decision.

Failing over to a replica

To failover a machine to a replica

1. Select a replica to failover to.

2. Click Replica actions.
3. Click Failover.
4. Select whether to connect the powered-on replica to a network. By default, the replica will be
connected to the same network as the original machine.
5. [Optional] If you chose to connect the replica to the network, clear the Stop original virtual
machine check box to keep the original machine online.
6. Click Start.

While the replica is in a failover state, you can choose one of the following actions:

l Stop failover
Stop failover if the original machine was fixed. The replica will be powered off. Replication will be
resumed.
l Perform permanent failover to the replica
This instant operation removes the 'replica' flag from the virtual machine, so that replication to it
is no longer possible. If you want to resume replication, edit the replication plan to select this
machine as a source.
l Failback
Perform failback if you failed over to the site that is not intended for continuous operations. The
replica will be recovered to the original or a new virtual machine. Once the recovery to the
original machine is complete, it is powered on and replication is resumed. If you choose to
recover to a new machine, edit the replication plan to select this machine as a source.

Stopping failover
To stop a failover

654 © Acronis International GmbH, 2003-2024

1. Select a replica that is in the failover state.
2. Click Replica actions.
3. Click Stop failover.
4. Confirm your decision.

Performing a permanent failover

To perform a permanent failover

1. Select a replica that is in the failover state.

2. Click Replica actions.
3. Click Permanent failover.
4. [Optional] Change the name of the virtual machine.
5. [Optional] Select the Stop original virtual machine check box.
6. Click Start.

Failing back
To failback from a replica

1. Select a replica that is in the failover state.

2. Click Replica actions.
3. Click Failback from replica.
The software automatically selects the original machine as the target machine.
4. [Optional] Click Target machine, and then do the following:
a. Select whether to failback to a new or existing machine.
b. Select the ESXi host and specify the new machine name, or select an existing machine.
c. Click OK.
5. [Optional] When failing back to a new machine, you can also do the following:
l Click Datastore to select the datastore for the virtual machine.
l Click VM settings to change the memory size, the number of processors, and the network
connections of the virtual machine.
6. [Optional] Click Recovery options to modify the failback options.
7. Click Start recovery.
8. Confirm your decision.

Replication options
To modify the replication options, click the gear icon next to the replication plan name, and then
click Replication options.

Changed Block Tracking (CBT)

This option is similar to the backup option "Changed Block Tracking (CBT)".

655 © Acronis International GmbH, 2003-2024

Disk provisioning
This option defines the disk provisioning settings for the replica.

The preset is: Thin provisioning.

The following values are available: Thin provisioning, Thick provisioning, Keep the original
setting.

Error handling
This option is similar to the backup option "Error handling".

Pre/Post commands
This option is similar to the backup option "Pre/Post commands".

Volume Shadow Copy Service VSS for virtual machines

This option is similar to the backup option "Volume Shadow Copy Service VSS for virtual machines".

Failback options
To modify the failback options, click Recovery options when configuring failback.

Error handling
This option is similar to the recovery option "Error handling".

Performance
This option is similar to the recovery option "Performance".

Pre/Post commands
This option is similar to the recovery option "Pre/Post commands".

VM power management
This option is similar to the recovery option "VM power management".

Seeding an initial replica

To speed up replication to a remote location and save network bandwidth, you can perform replica
seeding.

Important
To perform replica seeding, Agent for VMware (Virtual Appliance) must be running on the target
ESXi.

To seed an initial replica

656 © Acronis International GmbH, 2003-2024

1. Do one of the following:
l If the original virtual machine can be powered off, power it off, and then skip to step 4.
l If the original virtual machine cannot be powered off, continue to the next step.
2. Create a replication plan.
When creating the plan, in Target machine, select New replica and the ESXi that hosts the
original machine.
3. Run the plan once.
A replica is created on the original ESXi.
4. Export the virtual machine (or the replica) files to an external hard drive.
a. Connect the external hard drive to the machine where vSphere Client is running.
b. Connect vSphere Client to the original vCenter\ESXi.
c. Select the newly created replica in the inventory.
d. Click File > Export > Export OVF template.
e. In Directory, specify the folder on the external hard drive.
f. Click OK.
5. Transfer the hard drive to the remote location.
6. Import the replica to the target ESXi.
a. Connect the external hard drive to the machine where vSphere Client is running.
b. Connect vSphere Client to the target vCenter\ESXi.
c. Click File > Deploy OVF template.
d. In Deploy from a file or URL, specify the template that you exported in step 4.
e. Complete the import procedure.
7. Edit the replication plan that you created in step 2. In Target machine, select Existing replica,
and then select the imported replica.

As a result, the software will continue updating the replica. All replications will be incremental.

Agent for VMware - LAN-free backup

If your ESXi uses a SAN attached storage, install the agent on a machine connected to the same SAN.
The agent will back up the virtual machines directly from the storage rather than via the ESXi host
and LAN. This capability is called a LAN-free backup.

The diagram below illustrates a LAN-based and a LAN-free backup. LAN-free access to virtual
machines is available if you have a fibre channel (FC) or iSCSI Storage Area Network. To completely
eliminate transferring the backed-up data via LAN, store the backups on a local disk of the agent's
machine or on a SAN attached storage.

657 © Acronis International GmbH, 2003-2024

To enable the agent to access a datastore directly

1. Install Agent for VMware on a Windows machine that has network access to the vCenter Server.
2. Connect the logical unit number (LUN) that hosts the datastore to the machine. Consider the
following:
l Use the same protocol (i.e. iSCSI or FC) that is used for the datastore connection to the ESXi.
l The LUN must not be initialized and must appear as an "offline" disk in Disk Management. If
Windows initializes the LUN, it may become corrupted and unreadable by VMware vSphere.

As a result, the agent will use the SAN transport mode to access the virtual disks, i.e. it will read raw
LUN sectors over iSCSI/FC without recognizing the VMFS file system (which Windows is not aware
of).

Limitations
l In vSphere 6.0 and later, the agent cannot use the SAN transport mode if some of the VM disks
are located on a VMware Virtual Volume (VVol) and some are not. Backups of such virtual
machines will fail.
l Encrypted virtual machines, introduced in VMware vSphere 6.5, will be backed up via LAN, even if
you configure the SAN transport mode for the agent. The agent will fall back on the NBD
transport because VMware does not support SAN transport for backing up encrypted virtual
disks.

658 © Acronis International GmbH, 2003-2024

Example
If you are using an iSCSI SAN, configure the iSCSI initiator on the machine running Windows where
Agent for VMware is installed.

To configure the SAN policy

1. Log on as an administrator, open the command prompt, type diskpart, and then press Enter.
2. Type san, and then press Enter. Ensure that SAN Policy : Offline All is displayed.
3. If another value for SAN Policy is set:
a. Type san policy=offlineall.
b. Press Enter.
c. To check that the setting has been applied correctly, perform step 2.
d. Restart the machine.

To configure an iSCSI initiator

1. Go to Control Panel > Administrative Tools > iSCSI Initiator.

Note
To find the Administrative Tools applet, you may need to change the Control Panel view to
something other than Home or Category, or use search.

2. If this is the first time that Microsoft iSCSI Initiator is launched, confirm that you want to start the
Microsoft iSCSI Initiator service.
3. On the Targets tab, type the fully qualified domain name (FQDN) name or the IP address of the
target SAN device, and then click Quick Connect.
4. Select the LUN that hosts the datastore, and then click Connect.
If the LUN is not displayed, ensure that the zoning on the iSCSI target enables the machine
running the agent to access the LUN. The machine must be added to the list of allowed iSCSI
initiators on this target.
5. Click OK.

The ready SAN LUN should appear in Disk Management as shown in the screenshot below.

659 © Acronis International GmbH, 2003-2024

Using a locally attached storage
You can attach an additional disk to Agent for VMware (Virtual Appliance) so the agent can back up
to this locally attached storage. This approach eliminates the network traffic between the agent and
the backup location.

A virtual appliance that is running on the same host or cluster with the backed-up virtual machines
has direct access to the datastore(s) where the machines reside. This means the appliance can
attach the backed-up disks by using the HotAdd transport, and therefore the backup traffic is
directed from one local disk to another. If the datastore is connected as Disk/LUN rather than NFS,
the backup will be completely LAN-free. In the case of NFS datastore, there will be network traffic
between the datastore and the host.

Using a locally attached storage presumes that the agent always backs up the same machines. If
multiple agents work within the vSphere, and one or more of them use locally attached storages,
you need to manually bind each agent to all machines it has to back up. Otherwise, if the machines
are redistributed among the agents by the management server, a machine's backups may be
dispersed over multiple storages.

You can add the storage to an already working agent or when deploying the agent from an OVF
template.

To attach a storage to an already working agent

660 © Acronis International GmbH, 2003-2024

1. In VMware vSphere inventory, right click the Agent for VMware (Virtual Appliance).
2. Add the disk by editing the settings of the virtual machine. The disk size must be at least 10 GB.

Warning!
Be careful when adding an already existing disk. Once the storage is created, all data previously
contained on this disk will be lost.

3. Go to the virtual appliance console. The Create storage link is available at the bottom of the
screen. If it is not, click Refresh.
4. Click the Create storage link, select the disk and specify a label for it. The label length is limited
to 16 characters, due to file system restrictions.

To select a locally attached storage as a backup destination

l When creating a protection plan, in Where to back up, select Local folders, and then type the
letter corresponding to the locally attached storage, for example, D:\.

Note
Locally Attached Storage (LAS) is designed for relatively small environments with a single agent
(Virtual Appliance). We have tested Locally Attached Storage units of up to 5 TB in size. You can
attach larger disks at your own risk, but such configurations are not supported. For more than 5 TB
of backup data, we recommend that you use other types of storage. For example, you can create
and attach a VMware virtual disk to any random virtual machine and create a network share on it,
which will then be used as backup destination instead of a LAS.

Virtual machine binding

This section gives you an overview of how the Cyber Protection service organizes the operation of
multiple agents within VMware vCenter.

The below distribution algorithm works for both virtual appliances and agents installed in Windows.

Distribution algorithm
The virtual machines are automatically evenly distributed between Agents for VMware. By evenly,
we mean that each agent manages an equal number of machines. The amount of storage space
occupied by a virtual machine is not counted.

However, when choosing an agent for a machine, the software tries to optimize the overall system
performance. In particular, the software considers the agent and the virtual machine location. An
agent hosted on the same host is preferred. If there is no agent on the same host, an agent from the
same cluster is preferred.

Once a virtual machine is assigned to an agent, all backups of this machine are delegated to this
agent.

661 © Acronis International GmbH, 2003-2024

Redistribution
Redistribution takes place each time the established balance breaks, or, more precisely, when a load
imbalance among the agents reaches 20 percent. This may happen when a machine or an agent is
added or removed, or a machine migrates to a different host or cluster, or if you manually bind a
machine to an agent. If this happens, the Cyber Protection service redistributes the machines using
the same algorithm.

For example, you realize that you need more agents to help with throughput and deploy an
additional virtual appliance to the cluster. The Cyber Protection service will assign the most
appropriate machines to the new agent. The old agents' load will reduce.

When you remove an agent from the Cyber Protection service, the machines assigned to the agent
are distributed among the remaining agents. However, this will not happen if an agent gets
corrupted or is deleted manually from vSphere. Redistribution will start only after you remove such
agent from the web interface.

Viewing the distribution result

You can view the result of the automatic distribution:

l in the Agent column for each virtual machine on the All devices section
l in the Assigned virtual machines section of the Details panel when an agent is selected in the
Settings > Agents section

Manual binding
The Agent for VMware binding lets you exclude a virtual machine from this distribution process by
specifying the agent that must always back up this machine. The overall balance will be maintained,
but this particular machine can be passed to a different agent only if the original agent is removed.

To bind a machine with an agent

1. Select the machine.

2. Click Details.
In the Assigned agent section, the software shows the agent that currently manages the
selected machine.
3. Click Change.
4. Select Manual.
5. Select the agent to which you want to bind the machine.
6. Click Save.

To unbind a machine from an agent

1. Select the machine.

2. Click Details.

662 © Acronis International GmbH, 2003-2024

 In the Assigned agent section, the software shows the agent that currently manages the
selected machine.
3. Click Change.
4. Select Automatic.
5. Click Save.

Disabling automatic assignment for an agent

You can disable the automatic assignment for Agent for VMware to exclude it from the distribution
process by specifying the list of machines that this agent must back up. The overall balance will be
maintained between other agents.

Automatic assignment cannot be disabled for an agent if there are no other registered agents, or if
automatic assignment is disabled for all other agents.

To disable automatic assignment for an agent

1. Click Settings > Agents.

2. Select Agent for VMware for which you want to disable the automatic assignment.
3. Click Details.
4. Disable the Automatic assignment switch.

Usage examples
l Manual binding comes in handy if you want a particular (very large) machine to be backed up by
Agent for VMware (Windows) via a fibre channel while other machines are backed up by virtual
appliances.
l It is necessary to bind VMs to an agent if the agent has a locally attached storage.
l Disabling the automatic assignment enables you to ensure that a particular machine is
predictably backed up on the schedule you specify. The agent that only backs up one VM cannot
be busy backing up other VMs when the scheduled time comes.
l Disabling the automatic assignment is useful if you have multiple ESXi hosts that are separated
geographically. If you disable the automatic assignment, and then bind the VMs on each host to
the agent running on the same host, you can ensure that the agent will never back up any
machines running on the remote ESXi hosts, thus saving network traffic.

Running pre‐freeze and post‐thaw scripts automatically

With VMware Tools, you can automatically run custom pre‐freeze and post‐thaw scripts on virtual
machines that you back up in the agentless mode. Thus, for example, you can run custom quiescing
scripts and create application‐consistent backups for virtual machines running applications that are
not VSS-aware.

Prerequisites
The pre‐freeze and post‐thaw scripts must be located in a specific folder on the virtual machine.

663 © Acronis International GmbH, 2003-2024

l For Windows virtual machines, the location of this folder depends on the ESXi version of the host.
For example, for virtual machines running on an ESXi 6.5 host, this folder is C:\Program
Files\VMware\VMware Tools\backupScripts.d\. You must create the backupScritps.d folder
manually. Do not store other types of files in this folder because this may cause VMware Tools to
become unstable.
For more information about the location of the pre‐freeze and post‐thaw scripts for other ESXi
versions, refer to the VMware documentation.
l For Linux virtual machines, copy your scripts to the /usr/sbin/pre-freeze-script and
/usr/sbin/post-thaw-script directories, respectively. The scripts in /usr/sbin/pre-freeze-script
are run when you create a snapshot and those in /usr/sbin/post-thaw-script are run when the
snapshot is finalized. The scripts must be executable by the VMware Tools user.

To run pre‐freeze and post‐thaw scripts automatically

1. Ensure that VMware Tools are installed on the virtual machine.

2. On the virtual machine, put your custom scripts in the required folder.
3. In the protection plan for this machine, enable the Volume Shadow Copy Service (VSS) for
virtual machines option.
This creates a VMware snapshot with the Quiesce guest file system option enabled, which in
turn triggers the pre-freeze and post-thaw scripts inside the virtual machine.

You do not need to run custom quiescing scripts on virtual machines running VSS-aware
applications, such as Microsoft SQL Server or Microsoft Exchange. To create an application-
consistent backup for such machines, enable the Volume Shadow Copy Service (VSS) for virtual
machines option in the protection plan.

Support for virtual machine migration

This section contains information about migration of virtual machines within a vSphere
environment, including migration between ESXi hosts that are part of a vSphere cluster.

vMotion allows moving the state and configuration of a virtual machine to another host, while the
machine's disks remain in the same location on a shared storage. Storage vMotion allows moving
the disks of a virtual machine from one datastore to another.

l Migration with vMotion, including Storage vMotion, is not supported for a virtual machine that
runs Agent for VMware (Virtual Appliance), and is disabled automatically. This virtual machine is
added to the VM overrides list in the vSphere cluster configuration.
l When a backup of a virtual machine starts, migration with vMotion, including Storage vMotion, is
automatically disabled. This virtual machine is temporarily added to the VM overrides list in the
vSphere cluster configuration. After the backup finishes, the VM overrides settings are
automatically reverted to their previous state.
l A backup cannot start for a virtual machine while its migration with vMotion, including Storage
vMotion, is in progress. The backup for this machine will start when its migration finishes.

664 © Acronis International GmbH, 2003-2024

Managing virtualization environments
You can view the vSphere, Hyper-V, and Virtuozzo environments in their native presentation. Once
the corresponding agent is installed and registered, the VMware, Hyper-V, or Virtuozzo tab
appears under Devices.

In the VMware tab, you can back up the following vSphere infrastructure objects:

l Data center
l Folder
l Cluster
l ESXi host
l Resource pool

Each of these infrastructure objects works as a group object for virtual machines. When you apply a
protection plan to any of these group objects, all virtual machines included in it, will be backed up.
You can back up either the selected group machines by clicking Protect, or the parent group
machines in which the selected group is included by clicking Protect group.

For example, you have selected the Stefano cluster and then selected the resource pool inside it. If
you click Protect, all virtual machines included in the selected resource pool will be backed up. If
you click Protect group, all virtual machines included in the Stefano cluster will be backed up.

The VMware tab enables you to change access credentials for the vCenter Server or stand-alone
ESXi host without re-installing the agent.

To change the vCenter Server or ESXi host access credentials

665 © Acronis International GmbH, 2003-2024

1. Under Devices, click VMware.
2. Click Hosts and Clusters.
3. In the Hosts and Clusters list (to the right of the Hosts and Clusters tree), select the vCenter
Server or stand-alone ESXi host that was specified during the Agent for VMware installation.
4. Click Details.
5. Under Credentials, click the user name.
6. Specify the new access credentials, and then click OK.

Viewing backup status in vSphere Client

You can view backup status and the last backup time of a virtual machine in vSphere Client.

This information appears in the virtual machine summary (Summary > Custom
attributes/Annotations/Notes, depending on the client type and vSphere version). You can also
enable the Last backup and Backup status columns on the Virtual Machines tab for any host,
datacenter, folder, resource pool, or the entire vCenter Server.

To provide these attributes, Agent for VMware must have the following privileges in addition to
those described in "Agent for VMware - necessary privileges":

l Global > Manage custom attributes

l Global > Set custom attribute

Agent for VMware – necessary privileges

To perform any operations with vCenter objects, such as virtual machines, ESXi hosts, clusters,
vCenter, and more, Agent for VMware authenticates on vCenter or ESXi host by using the vSphere
credentials provided by a user. The vSphere account, used for connection to vSphere by Agent for
VMware, must have the required privileges on all levels of vSphere infrastructure starting from the
vCenter level.

Specify the vSphere account with the necessary privileges during Agent for VMware installation or
configuration. If you need to change the account later, refer to "Managing virtualization
environments" (p. 665).

To assign the permissions to a vSphere user on the vCenter level

1. Log in to vSphere web client.

2. Right-click on vCenter and then click Add permission.
3. Select or add a new user with the required role (the role must include all the required
permissions from the table below).
4. Select the Propagate to children option.

666 © Acronis International GmbH, 2003-2024

 Object Privilege Operation

Back Recover Recover Run VM

up a to a new to an from
VM VM existing backup
VM

Cryptographic Add disk +*

operations

(starting with vSphere

6.5)

Direct Access +*

Datastore Allocate space + + +

Browse datastore +

Configure datastore + + + +

Low level file operations +

Global Licenses + + + +

Disable methods + + +

Enable methods + + +

Manage custom attributes + + +

Set custom attribute + + +

Host > Configuration Storage partition +

configuration

Host > Local operations Create VM +

Delete VM +

667 © Acronis International GmbH, 2003-2024

 Reconfigure VM +

Network Assign network + + +

Resource Assign VM to resource pool + + +

Virtual machine > Add existing disk + + +

Configuration

Add new disk + + +

Add or remove device + +

Advanced + + +

Change CPU count +

Disk change tracking + +

Disk lease + +

Memory +

Remove disk + + + +

Rename +

Set annotation +

Settings + + +

Virtual machine > Guest Guest Operation Program +**

Operations Execution

Guest Operation Queries +**

Guest Operation +**

Modifications

Virtual machine > Acquire guest control +

Interaction ticket (in vSphere 4.1 and
5.0)

Configure CD media + +

Guest operating system +

management by VIX API (in
vSphere 5.1 and later)

Power off + +

Power on + + +

Virtual machine > Create from existing + + +

Inventory

668 © Acronis International GmbH, 2003-2024

 Create new + + +

Register +

Remove + + +

Unregister +

Virtual machine > Allow disk access + + +

Provisioning

Allow read-only disk access + +

Allow virtual machine + + + +

download

Virtual machine > State Create snapshot + + +

Virtual machine >

Snapshot management
(vSphere 6.5 and later)

Remove snapshot + + +

vApp Add virtual machine +

* This privilege is required for backing up encrypted machines only.

** This privilege is required for application-aware backups only.

Backing up clustered Hyper-V machines

In a Hyper-V cluster, virtual machines may migrate between cluster nodes. Follow these
recommendations to set up a correct backup of clustered Hyper-V machines:

1. A machine must be available for backup no matter what node it migrates to. To ensure that
Agent for Hyper-V can access a machine on any node, the agent service must run under a
domain user account that has administrative privileges on each of the cluster nodes.
We recommend that you specify such an account for the agent service during the Agent for
Hyper-V installation.
2. Install Agent for Hyper-V on each node of the cluster.
3. Register all of the agents in the Cyber Protection service.

High Availability of a recovered machine

When you recover backed-up disks to an existing Hyper-V virtual machine, the machine's High
Availability property remains as is.

When you recover backed-up disks to a new Hyper-V virtual machine, the resulting machine is not
highly available. It is considered as a spare machine and is normally powered off. If you need to use

669 © Acronis International GmbH, 2003-2024

the machine in the production environment, you can configure it for High Availability from the
Failover Cluster Management snap-in.

Limiting the total number of simultaneously backed-up virtual

machines
In the Scheduling backup option, you can limit the number of simultaneously backed-up virtual
machines per protection plan.

When an agent runs multiple plans at the same time, the number of simultaneously backed-up
machines adds up. This might affect the backup performance and overload the host and the virtual
machine storage. You can avoid such issues by configuring a limitation on the agent level.

To limit the number of simultaneous backups on the agent level

Agent for VMware (Windows)

1. On the machine with the agent, create a new text document, and then open it in a text editor.
2. Copy and paste the following lines into the file.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_
MACHINE\SOFTWARE\Acronis\MMS\Configuration\ManagedMachine\SimultaneousBackupsLimits]
"MaxNumberOfSimultaneousBackups"=dword:00000001

3. Replace 00000001 with the hexadecimal value of the limit that you want to set.
For example, 00000001 is 1 and 0000000A is 10.
4. Save the document as limit.reg.
5. Run the file as an administrator.
6. Confirm that you want to edit the Windows registry.
7. Restart the agent.
a. In the Start menu, click Run.
b. Type cmd, and then click OK.
c. On the command line, run the following commands:

net stop mms

net start mms

Agent for Hyper-V

1. On the machine with the agent, create a new text document, and then open it in a text editor.
2. Copy and paste the following lines into the file.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_

670 © Acronis International GmbH, 2003-2024

 MACHINE\SOFTWARE\Acronis\MMS\Configuration\ManagedMachine\SimultaneousBackupsLimits]
"MaxNumberOfSimultaneousBackups"=dword:00000001

3. Replace 00000001 with the hexadecimal value of the limit that you want to set.
For example, 00000001 is 1 and 0000000A is 10.
4. Save the document as limit.reg.
5. Run the file as an administrator.
6. Confirm that you want to edit the Windows registry.
7. Restart the agent.
a. In the Start menu, click Run.
b. Type cmd, and then click OK.
c. On the command line, run the following commands:

net stop mms

net start mms

Virtual appliances

This procedure applies to Agent for VMware (Virtual Appliance), Agent for Scale Computing, Agent
for Virtuozzo Hybrid Infrastructure, and Agent for oVirt.

1. In the console of the virtual appliance, press CTRL+SHIFT+F2 to open the command-line
interface.
2. Open the /etc/Acronis/MMS.config file in a text editor.
3. Locate the following section:

<key name="SimultaneousBackupsLimits">
<value name="MaxNumberOfSimultaneousBackups" type="Tdword">"10"</value>
</key>

4. Replace 10 with the maximum number of simultaneous backups that you want to set.
5. Save the file.
6. Restart the agent by running the reboot command.

Machine migration
You can perform machine migration by recovering its backup to a non-original machine.

The following table summarizes the available migration options.

671 © Acronis International GmbH, 2003-2024

 Available recovery destinations

Backed- Scale
Hype Virtuozzo Virtuozzo
up ESXi Compu RHV/o
Physi r-V Hybrid
machine virtua ting Virt
cal virtua Infrastru
type l Virtu HC3 virtual
machi l cture
machi al Contai virtual machi
ne machi virtual
ne machi ner machin ne
ne machine
ne e

Physical
+ + + - - + +* +
machine

VMware
ESXi virtual + + + - - + +* +
machine

Hyper-V
virtual + + + - - + +* +
machine

Virtuozzo
virtual + + + + - + +* +
machine

Virtuozzo
- - - - + - - -
container

Virtuozzo
Hybrid
Infrastructu + + + - - + +* +
re virtual
machine

Scale
Computing
+ + + - - + + +
HC3 virtual
machine

Red Hat
Virtualizatio
n/oVirt + + + - - + +* +
virtual
machine

*If Secure Boot is enabled on the source machine, the recovered VM will not be able to start up
unless you disable Secure Boot in the VM console after the recovery.

672 © Acronis International GmbH, 2003-2024

Note
You cannot recover macOS virtual machines to Hyper-V hosts, because Hyper-V does not support
macOS. You can recover macOS virtual machines to a VMware host that is installed on Mac
hardware.

For more information on how to perform the migration operations, see the following topics:

l For physical-to-virtual (P2V) migration, see "Physical machine to virtual" (p. 478).
l For virtual-to-virtual (V2V) migration, see "Recovering a virtual machineYou can recover virtual
machines from their backups. You cannot recover backups in the Cyber Protect console for
tenants in the Compliance mode. For more information on how to recover such backups, refer to
"Recovering backups for tenants in the Compliance mode" (p. 1).PrerequisitesA virtual machine
must be stopped during the recovery to this machine. By default, the software stops the machine
without a prompt. When the recovery is completed, you have to start the machine manually. You
can change the default behavior by using the VM power management recovery option (click
Recovery options > VM power management).ProcedureDo one of the following:Select a backed-
up machine, click Recovery, and then select a recovery point.Select a recovery point on the
Backup storage tab.Click Recover > Entire machine.If you want to recover to a physical machine,
select Physical machine in Recover to. Otherwise, skip this step.Recovery to a physical machine is
possible only if the disk configuration of the target machine exactly matches the disk
configuration in the backup.If this is the case, continue to step 4 in "Physical machine". Otherwise,
we recommend that you perform the V2P migration by using bootable media.[Optional] By
default, the software automatically selects the original machine as the target machine. To recover
to another virtual machine, click Target machine, and then do the following:Select the hypervisor
(VMware ESXi, Hyper-V, Virtuozzo, Virtuozzo Hybrid Infrastructure, Scale Computing HC3, or
oVirt).Only Virtuozzo virtual machines can be recovered to Virtuozzo. For more information about
V2V migration, refer to "Machine migration".Select whether to recover to a new or existing
machine.Select the host and specify the new machine name, or select an existing target
machine.Click OK.Setup up the additional recovery options that you need.[Not available for
Virtuozzo Hybrid Infrastructure and Scale Computing HC3] To select the datastore for the virtual
machine, click Datastore for ESXi, Path for Hyper-V and Virtuozzo, or Storage domain for Red Hat
Virtualization (oVirt), and then select the datastore (storage) for the virtual machine.To view the
datastore (storage), interface, and the provisioning mode for each virtual disk, click Disk mapping.
You can change these settings, unless you are recovering a Virtuozzo container or Virtuozzo
Hybrid Infrastructure virtual machine.For Virtuozzo Hybrid Infrastructure, you can only select the
storage policy for the target disks. To do so, select the desired target disk, and then click Change.
In the blade that opens, click the gear icon, select the storage policy, and then click Done.The
mapping section also enables you to choose individual disks for recovery.[Available for VMware
ESXi, Hyper-V, and Virtuozzo] To change the memory size, the number of processors, and the
network connections of the virtual machine, click VM settings.[For Virtuozzo Hybrid
Infrastructure] To change the memory size and the number of processors of the virtual machine,
select Flavor. [Only available for Windows machines on which a protection agent is installed]
Enable the Safe recovery switch to ensure that the recovered data is malware-free. For more

673 © Acronis International GmbH, 2003-2024

 information about how safe recovery works, see "Safe recovery" (p. 1).Click Start recovery.When
recovering to an existing virtual machine, confirm that you want to overwrite the disks.The
recovery progress is shown on the Activities tab." (p. 1).
l For virtual-to-physical (V2P) migration, see "Recovering a virtual machineYou can recover virtual
machines from their backups. You cannot recover backups in the Cyber Protect console for
tenants in the Compliance mode. For more information on how to recover such backups, refer to
"Recovering backups for tenants in the Compliance mode" (p. 1).PrerequisitesA virtual machine
must be stopped during the recovery to this machine. By default, the software stops the machine
without a prompt. When the recovery is completed, you have to start the machine manually. You
can change the default behavior by using the VM power management recovery option (click
Recovery options > VM power management).ProcedureDo one of the following:Select a backed-
up machine, click Recovery, and then select a recovery point.Select a recovery point on the
Backup storage tab.Click Recover > Entire machine.If you want to recover to a physical machine,
select Physical machine in Recover to. Otherwise, skip this step.Recovery to a physical machine is
possible only if the disk configuration of the target machine exactly matches the disk
configuration in the backup.If this is the case, continue to step 4 in "Physical machine". Otherwise,
we recommend that you perform the V2P migration by using bootable media.[Optional] By
default, the software automatically selects the original machine as the target machine. To recover
to another virtual machine, click Target machine, and then do the following:Select the hypervisor
(VMware ESXi, Hyper-V, Virtuozzo, Virtuozzo Hybrid Infrastructure, Scale Computing HC3, or
oVirt).Only Virtuozzo virtual machines can be recovered to Virtuozzo. For more information about
V2V migration, refer to "Machine migration".Select whether to recover to a new or existing
machine.Select the host and specify the new machine name, or select an existing target
machine.Click OK.Setup up the additional recovery options that you need.[Not available for
Virtuozzo Hybrid Infrastructure and Scale Computing HC3] To select the datastore for the virtual
machine, click Datastore for ESXi, Path for Hyper-V and Virtuozzo, or Storage domain for Red Hat
Virtualization (oVirt), and then select the datastore (storage) for the virtual machine.To view the
datastore (storage), interface, and the provisioning mode for each virtual disk, click Disk mapping.
You can change these settings, unless you are recovering a Virtuozzo container or Virtuozzo
Hybrid Infrastructure virtual machine.For Virtuozzo Hybrid Infrastructure, you can only select the
storage policy for the target disks. To do so, select the desired target disk, and then click Change.
In the blade that opens, click the gear icon, select the storage policy, and then click Done.The
mapping section also enables you to choose individual disks for recovery.[Available for VMware
ESXi, Hyper-V, and Virtuozzo] To change the memory size, the number of processors, and the
network connections of the virtual machine, click VM settings.[For Virtuozzo Hybrid
Infrastructure] To change the memory size and the number of processors of the virtual machine,
select Flavor. [Only available for Windows machines on which a protection agent is installed]
Enable the Safe recovery switch to ensure that the recovered data is malware-free. For more
information about how safe recovery works, see "Safe recovery" (p. 1).Click Start recovery.When
recovering to an existing virtual machine, confirm that you want to overwrite the disks.The
recovery progress is shown on the Activities tab." (p. 1) and "Recovering disks by using bootable
media" (p. 482).

674 © Acronis International GmbH, 2003-2024

Migration via a bootable media
As an alternative to the machine migration that you perform in the Cyber Protect console, you can
recover a machine by using a bootable media.

We recommend that you use a bootable media in the following cases:

l Performing a migration that is not natively supported.

For example, use a bootable media to recover a physical machine or a non-Virtuozzo virtual
machine as a Virtuozzo virtual machine on a Virtuozzo host.
l Performing migration of a Linux machine that contains logical volumes (LVM).
Use Agent for Linux or bootable media to create the backup, and then use a bootable media to
recover the backup.
l Providing drivers for specific hardware that is critical for the system bootability.
Build a bootable media that can use the required drivers. For more information, see "Bootable
Media Builder" (p. 678).

Microsoft Azure and Amazon EC2 virtual machines

To back up a Microsoft Azure or Amazon EC2 virtual machine, install a protection agent on the
machine. The backup and recovery operations are the same as with a physical machine.
Nevertheless, the machine is counted as virtual when you set quotas for the number of machines.

The difference from a physical machine is that Microsoft Azure and Amazon EC2 virtual machines
cannot be booted from bootable media. If you need to recover to a new Microsoft Azure or Amazon
EC2 virtual machine, follow the procedure below.

Note
The following recovery procedure applies only for backups of machines that contain all necessary
drivers to run in Microsoft Azure natively (backups created of an Azure VM, a local Hyper-V machine,
or the source machine being a Windows Server 2016 and up). For cross-platform recovery, please
see this knowledge base article.

To recover a machine as a Microsoft Azure or Amazon EC2 virtual machine

1. Create a new virtual machine from an image/template in Microsoft Azure or Amazon EC2. The
new machine must have the same disk configuration as the machine that you want to recover.
2. Install Agent for Windows or Agent for Linux on the new machine.
3. Recover the backed-up machine as described in "Physical machine". When configuring the
recovery, select the new machine as the target machine.

Creating bootable media to recover operating systems

Bootable media is a CD, DVD, USB flash drive, or other removable media that allows you to run the
protection agent either in a Linux-based environment or a Windows Preinstallation

675 © Acronis International GmbH, 2003-2024

Environment/Windows Recovery Environment (WinPE/WinRE), without the help of an operating
system. The main purpose of the bootable media is to recover an operating system that cannot
start.

Note
Bootable media does not support hybrid drives.

Custom or ready-made bootable media?

By using Bootable Media Builder, you can create custom bootable media (Linux-based or WinPE-
based) for Windows, Linux, or macOS computers. In the both Linux-based and WinPE/WinRE-based
custom bootable media, you can configure additional settings, such as automatic registration,
network settings, or proxy server settings. In the WinPE/WinRE-based custom bootable media, you
can also add additional drivers.

Alternatively, you can download a ready-made bootable media (Linux-based only). You can use the
ready-made bootable media for recovery operations and access to the Universal Restore feature.

Linux-based or WinPE/WinRE-based bootable media?

Linux-based
Linux-based bootable media contains a protection agent based on a Linux kernel. The agent can
boot and perform operations on any PC-compatible hardware, including bare metal, and machines
with corrupted or non-supported file systems.

WinPE/WinRE-based
WinPE-based bootable media contains a minimal Window system called Windows Preinstallation
Environment (WinPE) and a Cyber Protection plugin for WinPE, that is, a modification of the
protection agent that can run in the preinstallation environment. WinRE-based bootable media uses
Windows Recovery Environment and does not require installation of additional Windows packages.

WinPE proved to be the most convenient bootable solution in large environments with
heterogeneous hardware.

Advantages:

l Using Cyber Protection in Windows Preinstallation Environment provides more functionality than
using Linux-based bootable media. Having booted PC-compatible hardware into WinPE, you can
use not only the protection agent, but also PE commands and scripts, and other plugins that you
have added to the PE.
l PE-based bootable media helps overcome some Linux-related bootable media issues, such as
support for certain RAID controllers or certain levels of RAID arrays only. Media based on WinPE
2.x and later allows dynamic loading of the necessary device drivers.

Limitations:

676 © Acronis International GmbH, 2003-2024

l Bootable media based on WinPE versions earlier than 4.0 cannot boot on machines that use
Unified Extensible Firmware Interface (UEFI).

Creating physical bootable media

We highly recommend that you create and test the bootable media as soon as you start using disk-
level backup. Also, it is a good practice to re-create the media after each major update of the
protection agent.

You can recover either Windows or Linux by using the same media. To recover macOS, create a
separate media on a machine running macOS.

To create physical bootable media in Windows or Linux

1. Create a custom bootable media ISO file or download the ready-made ISO file.
To create a custom ISO file, use "Bootable Media Builder" (p. 678).
To download the ready-made ISO file, in the Cyber Protect console, select a machine, and then
click Recover > More ways to recover... > Download ISO image.
2. [Optional] In the Cyber Protect console, generate a registration token. The registration token is
displayed automatically when you download a ready-made ISO file.
This token allows the bootable media to access the cloud storage, without prompting you to
enter a login and password.
3. Create physical bootable media in one of the following ways:
l Burn the ISO file to a CD/DVD.
l Create a bootable USB flash drive by using the ISO file and one of the free tools available
online.
Use ISO to USB or RUFUS if you need to boot an UEFI machine, and Win32DiskImager for a BIOS
machine. In Linux, using the dd utility makes sense.
For virtual machines, you can connect the ISO file as a CD/DVD drive to the machine that you
want to recover.

To create physical bootable media in macOS

1. On a machine where Agent for Mac is installed, click Applications > Rescue Media Builder.
2. The software displays the connected removable media. Select the one that you want to make
bootable.

Warning!
All data on the disk will be erased.

3. Click Create.
4. Wait while the software creates the bootable media.

677 © Acronis International GmbH, 2003-2024

Bootable Media Builder
Bootable Media Builder is a dedicated tool for creating bootable media. It is installed as an optional
component on the machine where the protection agent is installed.

Why use Bootable Media Builder?

The ready-made bootable media that is available for download in the Cyber Protect console is based
on a Linux kernel. Unlike Windows PE, it does not allow injecting custom drivers on the fly.

Bootable Media Builder allows you to create customized Linux-based and WinPE-based bootable
media images.

32-bit or 64-bit?
Bootable Media Builder creates bootable media with both 32-bit and 64-bit components. In most
cases, you will need a 64-bit media to boot a machine that uses Unified Extensible Firmware
Interface (UEFI).

Linux-based bootable media

To create a Linux-based bootable media

1. Start Bootable Media Builder.

2. In Bootable media type, select Default (Linux-based media).
3. Select how volumes and network resources will be represented:
l Bootable media with a Linux-like volume representation displays the volumes as, for example,
hda1 and sdb2. It tries to reconstruct MD devices and logical volumes (LVM) before starting a
recovery.
l Bootable media with Windows-like volume representation displays the volumes as, for
example, C: and D:. It provides access to dynamic volumes (LDM).
4. [Optional] Specify the parameters of the Linux kernel. Separate multiple parameters with spaces.
For example, to be able to select a display mode for the bootable agent each time the media
starts, type: vga=ask. For more information about the available parameters, refer to "Kernel
parameters" (p. 679).
5. [Optional] Select the language for the bootable media.
6. [Optional] Select the boot mode (BIOS or UEFI) that Windows will use after the recovery.
7. Select the component to be placed on the media – the Cyber Protection bootable agent.
8. [Optional] Specify the timeout interval for the boot menu. If this setting is not configured, the
loader will wait for you to select whether to boot the operating system (if present) or the
component.
9. [Optional] If you want to automate the bootable agent operations, select the Use the following
script check box. Then, select one of the scripts and specify the script parameters. For more
information about the scripts, refer to "Scripts in bootable media" (p. 681).

678 © Acronis International GmbH, 2003-2024

10. [Optional] Select how to register the bootable media in the Cyber Protection service on booting
up. For more information about the registration settings, refer to "Registering the bootable
media" (p. 689).
11. Specify the network settings for the network adapters of the booted machine or keep the
automatic DHCP configuration.
12. [Optional] If a proxy server is enabled in your network, specify its host name/IP address and
port.
13. Select the file type of the created bootable media:
l ISO image
l ZIP file
14. Specify a file name for the bootable media file.
15. Check your settings in the summary screen, and then click Proceed.

Kernel parameters
You can specify one or more parameters of the Linux kernel that will be automatically applied when
the bootable media starts. These parameters are typically used when you experience problems
while working with the bootable media. Normally, you can leave this field empty.

You can also specify any of these parameters by pressing F11 while you are in the boot menu.

Parameters
When specifying multiple parameters, separate them with spaces.

l acpi=off
Disables Advanced Configuration and Power Interface (ACPI). You may want to use this
parameter when experiencing problems with a particular hardware configuration.
l noapic
Disables Advanced Programmable Interrupt Controller (APIC). You may want to use this
parameter when experiencing problems with a particular hardware configuration.
l vga=ask
Prompts for the video mode to be used by the bootable media's graphical user interface. Without
the vga parameter, the video mode is detected automatically.
l vga= mode_number
Specifies the video mode to be used by the bootable media's graphical user interface. The mode
number is given by mode_number in the hexadecimal format—for example: vga=0x318
The screen resolution and the number of colors corresponding to a mode number may be
different on different machines. We recommend that you use the vga=ask parameter first to
choose a value for mode_number.
l quiet
Disables displaying of startup messages when the Linux kernel is loading, and starts the
management console after the kernel is loaded.

679 © Acronis International GmbH, 2003-2024

 This parameter is implicitly specified when creating the bootable media, but you can remove this
parameter while you are in the boot menu.
If this parameter is removed, all startup messages will be displayed, followed by a command
prompt. To start the management console from the command prompt, run the command:
/bin/product
l nousb
Disables loading of the USB (Universal Serial Bus) subsystem.
l nousb2
Disables USB 2.0 support. USB 1.1 devices still work with this parameter. This parameter allows
you to use some USB drives in the USB 1.1 mode if they do not work in the USB 2.0 mode.
l nodma
Disables direct memory access (DMA) for all IDE hard disk drives. Prevents the kernel from
freezing on some hardware.
l nofw
Disables the FireWire (IEEE1394) interface support.
l nopcmcia
Disables the detection of PCMCIA hardware.
l nomouse
Disables the mouse support.
l module_name =off
Disables the module whose name is given by module_name. For example, to disable the use of the
SATA module, specify: sata_sis=off
l pci=bios
Forces the use of PCI BIOS instead of accessing the hardware device directly. You may want to
use this parameter if the machine has a non-standard PCI host bridge.
l pci=nobios
Disables the use of PCI BIOS; only direct hardware access methods will be allowed. You may want
to use this parameter when the bootable media fails to start, which may be caused by the BIOS.
l pci=biosirq
Uses PCI BIOS calls to get the interrupt routing table. You may want to use this parameter if the
kernel is unable to allocate interrupt requests (IRQs) or discover secondary PCI buses on the
motherboard.
These calls might not work properly on some machines. But this may be the only way to get the
interrupt routing table.
l LAYOUTS=en-US, de-DE, fr-FR, ...
Specifies the keyboard layouts that can be used in the bootable media's graphical user interface.
Without this parameter, only two layouts can be used: English (USA) and the layout that
corresponds to the language selected in the media's boot menu.
You can specify any of the following layouts:
Belgian: be-BE

680 © Acronis International GmbH, 2003-2024

 Czech: cz-CZ
English: en-GB
English (USA): en-US
French: fr-FR
French (Swiss): fr-CH
German: de-DE
German (Swiss): de-CH
Italian: it-IT
Polish: pl-PL
Portuguese: pt-PT
Portuguese (Brazilian): pt-BR
Russian: ru-RU
Serbian (Cyrillic): sr-CR
Serbian (Latin): sr-LT
Spanish: es-ES
When working under a bootable media, use CTRL + SHIFT to cycle through the available layouts.

Scripts in bootable media

If you want the bootable media to perform a predefined set of operations, you can specify a script
while creating the media with Bootable Media Builder. Thus, every time a machine is booted from
the media, the specified script will run and the user interface will not be shown.

You can select one of the predefined scripts or create a custom script by following the scripting
conventions.

Predefined scripts
Bootable Media Builder provides the following predefined scripts:

l Recovery from the cloud storage (entire_pc_cloud)

l Recovery from a network share (entire_pc_share)

The scripts are located in the following folders on the machine where Bootable Media Builder is
installed:

l In Windows: %ProgramData%\Acronis\MediaBuilder\scripts\
l In Linux: /var/lib/Acronis/MediaBuilder/scripts/

Recovery from the cloud storage

In Bootable Media Builder, specify the following script parameters:

1. The backup file name.

2. [Optional] A password that the script will use to access encrypted backups.

681 © Acronis International GmbH, 2003-2024

Recovery from a network share
In Bootable Media Builder, specify the following script parameters:

l The path to the network share.

l The user name and password for the network share.
l The backup file name. To find out the backup file name:
a. In the Cyber Protect console, go to Backup storage > Locations.
b. Select the network share (click Add location if the share is not listed).
c. Select the backup.
d. Click Details. The file name is displayed under Backup file name.
l [Optional] A password that the script will use to access encrypted backups.

Custom scripts

Important
Creating custom scripts requires the knowledge of the Bash command language and JavaScript
Object Notation (JSON). If you are not familiar with Bash, a good place to learn it is
http://www.tldp.org/LDP/abs/html. The JSON specification is available at http://www.json.org.

Files of a script
Your script must be located in the following directories on the machine where Bootable Media
Builder is installed:

l In Windows: %ProgramData%\Acronis\MediaBuilder\scripts\
l In Linux: /var/lib/Acronis/MediaBuilder/scripts/

The script must consist of at least three files:

l <script_file>.sh - a file with your Bash script. When creating the script, use only a limited set of
shell commands, which you can find at https://busybox.net/downloads/BusyBox.html. Also, the
following commands can be used:
o acrocmd - the command-line utility for backup and recovery
o product - the command that starts the bootable media user interface
This file and any additional files that the script includes (for example, by using the dot command)
must be located in the bin subfolder. In the script, specify the additional file paths as
/ConfigurationFiles/bin/<some_file>.
l autostart - a file for starting <script_file>.sh. The file contents must be as follows:

#!/bin/sh
. /ConfigurationFiles/bin/variables.sh
. /ConfigurationFiles/bin/<script_file>.sh
. /ConfigurationFiles/bin/post_actions.sh

682 © Acronis International GmbH, 2003-2024

l autostart.json - a JSON file that contains the following:
o The script name and description to be displayed in Bootable Media Builder.
o The names of the script variables to be configured via Bootable Media Builder.
o The parameters of controls that will be displayed in Bootable Media Builder for each variable.

Structure of autostart.json

Top-level object
Pair
Required Description
Name Value type

displayName string Yes The script name to be displayed in Bootable Media

Builder.

description string No The script description to be displayed in Bootable

Media Builder.

timeout number No A timeout (in seconds) for the boot menu before
starting the script. If the pair is not specified, the
timeout will be ten seconds.

variables object No Any variables for <script_file>.sh that you want to

configure via Bootable Media Builder.

The value should be a set of the following pairs: the

string identifier of a variable and the object of the
variable (see the table below).

Variable object
Pair
Required Description
Name Value type

displayName string Yes The variable name used in <script_file>.sh.

type string Yes The type of a control that is displayed in Bootable

Media Builder. This control is used to configure the
variable value.

For all supported types, see the table below.

description string Yes The control label that is displayed above the control in
Bootable Media Builder.

default string if type No The default value for the control. If the pair is not
is string, specified, the default value will be an empty string or a

683 © Acronis International GmbH, 2003-2024

 multiString, zero, based on the control type.
password, or
The default value for a check box can be 0 (the cleared
enum
state) or 1 (the selected state).
number if
type is number,
spinner, or
checkbox

order number Yes The control order in Bootable Media Builder. The
higher the value, the lower the control is placed relative
(non-
to other controls defined in autostart.json. The initial
negative)
value must be 0.

min number No The minimum value of the spin control in a spin box. If
the pair is not specified, the value will be 0.
(for spinner
only)

max number No The maximum value of the spin control in a spin box. If
the pair is not specified, the value will be 100.
(for spinner
only)

step number No The step value of the spin control in a spin box. If the
pair is not specified, the value will be 1.
(for spinner
only)

items array of Yes The values for a drop-down list.

strings
(for enum only)

required number No Specifies if the control value can be empty (0) or not (1).
If the pair is not specified, the control value can be
(for string,
empty.
multiString,
password, and
enum)

Control type
Name Description

string A single-line, unconstrained text box used to enter or edit short strings.

multiString A multi-line, unconstrained text box used to enter or edit long strings.

password A single-line, unconstrained text box used to enter passwords securely.

number A single-line, numeric-only text box used to enter or edit numbers.

spinner A single-line, numeric-only text box used to enter or edit numbers, with a spin

684 © Acronis International GmbH, 2003-2024

 control. Also, called a spin box.

enum A standard drop-down list, with a fixed set of predetermined values.

checkbox A check box with two states - the cleared state or the selected state.

The sample autostart.json below contains all possible types of controls that can be used to
configure variables for <script_file>.sh.

"displayName": "Autostart script name",

"description": "This is an autostart script description.",

"variables": {

"var_string": {

"displayName": "VAR_STRING",

"type": "string", "order": 1,

"description": "This is a 'string' control:", "default": "Hello,

world!"

},

"var_multistring": {

"displayName": "VAR_MULTISTRING",

"type": "multiString", "order": 2,

"description": "This is a 'multiString' control:",

"default": "Lorem ipsum dolor sit amet,\nconsectetur adipiscing elit."

},

"var_number": {

"displayName": "VAR_NUMBER",

"type": "number", "order": 3,

"description": "This is a 'number' control:", "default": 10

},

"var_spinner": {

"displayName": "VAR_SPINNER",

"type": "spinner", "order": 4,

"description": "This is a 'spinner' control:",

"min": 1, "max": 10, "step": 1, "default": 5

685 © Acronis International GmbH, 2003-2024

 },

"var_enum": {

"displayName": "VAR_ENUM",

"type": "enum", "order": 5,

"description": "This is an 'enum' control:",

"items": ["first", "second", "third"], "default": "second"

},

"var_password": {

"displayName": "VAR_PASSWORD",

"type": "password", "order": 6,

"description": "This is a 'password' control:", "default": "qwe"

},

"var_checkbox": {

"displayName": "VAR_CHECKBOX",

"type": "checkbox", "order": 7,

"description": "This is a 'checkbox' control", "default": 1

WinPE-based and WinRE-based bootable media

You can create WinRE images without any additional preparation, or create WinPE images after
installing Windows Automated Installation Kit (AIK) or Windows Assessment and Deployment Kit
(ADK).

WinRE images
Creating WinRE images is supported for the following operation systems:

l Windows 7 (64-bit)
l Windows 8 (32-bit and 64-bit)
l Windows 8.1 (32-bit and 64-bit)
l Windows 10 (32-bit and 64-bit)
l Windows 11 (64-bit)
l Windows Server 2012 (64-bit)
l Windows Server 2016 (64-bit)

686 © Acronis International GmbH, 2003-2024

l Windows Server 2019 (64-bit)
l Windows Server 2022 (64-bit)

WinPE images
After installing Windows Automated Installation Kit (AIK), or Windows Assessment and Deployment
Kit (ADK), Bootable Media Builder supports WinPE distributions that are based on any the following
kernels:

l Windows Vista (PE 2.0)

l Windows Vista SP1 and Windows Server 2008 (PE 2.1)
l Windows 7 (PE 3.0) with or without the supplement for Windows 7 SP1 (PE 3.1)
l Windows 8 (PE 4.0)
l Windows 8.1 (PE 5.0)
l Windows 10 (PE 10.0.1xxx)
l Windows 11 (PE 10.0.2xxx)

Bootable Media Builder supports both 32-bit and 64-bit WinPE distributions. The 32-bit WinPE
distributions can also work on 64-bit hardware. However, you need a 64-bit distribution to boot a
machine that uses Unified Extensible Firmware Interface (UEFI).

Note
PE images based on WinPE 4 and later require approximately 1 GB of RAM to work.

Creating WinPE or WinRE bootable media

Bootable Media Builder provides two methods of integrating Cyber Protection with WinPE and
WinRE:

l Creating an ISO file with the Cyber Protection plugin from scratch.
l Adding the Cyber Protection plugin to a WIM file for any future purpose (manual ISO building,
adding other tools to the image and so on).

To create WinPE or WinRE bootable media

1. On the machine where the protection agent is installed, run Bootable Media Builder.
2. In Bootable media type, select Windows PE or Windows PE (64-bit). A 64-bit media is required
to boot a machine that uses Unified Extensible Firmware Interface (UEFI).
3. Select the subtype of the bootable media: WinRE or WinPE.
Creating WinRE bootable media does not require installation of any additional packages.
To create a 64-bit WinPE media, you must download Windows Automated Installation Kit (AIK) or
Windows Assessment and Deployment Kit (ADK). To create 32-bit WinPE media, in addition to
downloading the AIK or ADK, you need to do the following:
a. Click Download the Plug-in for WinPE (32-bit).
b. Save the plugin to %PROGRAM_FILES%\BackupClient\BootableComponents\WinPE32.
4. [Optional] Select the language for the bootable media.

687 © Acronis International GmbH, 2003-2024

 5. [Optional] Select the boot mode (BIOS or UEFI) that Windows will use after the recovery.
6. Specify the network settings for the network adapters of the booted machine or keep the
automatic DHCP configuration.
7. [Optional] Select how to register the bootable media in the Cyber Protection service on booting
up. For more information about the registration settings, refer to "Registering the bootable
media" (p. 689).
8. [Optional] Specify the Windows drivers to be added to the bootable media.
After you boot a machine into Windows PE or Windows RE, the drivers can help you access the
device where the backup is located. Add 32-bit drivers if you use a 32-bit WinPE or WinRE
distribution or 64-bit drivers if you use a 64-bit WinPE or WinRE distribution.
To add the drivers:
l Click Add, and then specify the path to the necessary .inf file for a corresponding SCSI, RAID,
SATA controller, network adapter, tape drive, or other device.
l Repeat this procedure for each driver that you want to include in the resulting WinPE or
WinRE media.
9. Select the file type of the created bootable media:
l ISO image
l WIM image
10. Specify the full path to the resulting image file, including the file name.
11. Check your settings in the summary screen, and then click Proceed.

To create a PE image (ISO file) from the resulting WIM file

l Replace the default boot.wim file in your Windows PE folder with the newly created WIM file. For
the above example, type:

copy c:\RecoveryWIMMedia.wim c:\winpe_x86\ISO\sources\boot.wim

l Use the Oscdimg tool. For the above example, type:

oscdimg -n -bc:\winpe_x86\etfsboot.com c:\winpe_x86\ISO c:\winpe_x86\winpe_x86.iso

Warning!
Do not copy and paste this example. Type the command manually, otherwise it will fail.

Preparation: WinPE 2.x and 3.x

To be able to create or modify PE 2.x or 3.x images, install Bootable Media Builder and Windows
Automated Installation Kit (AIK) on the same machine.

To prepare a machine

1. Download the AIK image file from the Microsoft website, as follows:
l For Windows Vista (PE 2.0): https://www.microsoft.com/en-
us/download/details.aspx?id=10333

688 © Acronis International GmbH, 2003-2024

 l For Windows Vista SP1 and Windows Server 2008 (PE 2.1): https://www.microsoft.com/en-
us/download/details.aspx?id=9085
l For Windows 7 (PE 3.0): https://www.microsoft.com/en-gb/download/details.aspx?id=5753
For Windows 7 SP1 (PE 3.1), you also need the AIK supplement available at
https://www.microsoft.com/en-us/download/details.aspx?id=5188
2. Burn the image file to a DVD disk or a USB flash drive.
3. From image file, install the following:
l Microsoft .NET Framework (NETFXx86 or NETFXx64, depending on your hardware)
l MSXML (Microsoft XML parser)
l Windows AIK
4. Install Bootable Media Builder on the same machine.

Preparation: WinPE 4.0 and later

To be able to create or modify PE 4 or later images, install Bootable Media Builder and Windows
Assessment and Deployment Kit (ADK) on the same machine.

To prepare a machine

1. Download the ADK setup program from the Microsoft website.

The following Windows versions are supported:
l Windows 11 (PE 10.0.2xxx)
l Windows 10 (PE 10.0.1xxx)
l Windows 8.1 (PE 5.0)
l Windows 8 (PE 4.0)
2. Install Assessment and Deployment Kit.
3. Install Bootable Media Builder.

Registering the bootable media

Registering the bootable media in the Cyber Protection service allows accessing the cloud storage
for your backups. You can preconfigure the registration while creating the bootable media. If the
registration is not preconfigured, you can register the media after booting a machine with it.

To preconfigure the registration in the Cyber Protection service

1. In Bootable Media Builder, navigate to Bootable media registration.

2. In Service URL, specify the Cyber Protection service address.
3. [Optional] In Display name, specify a name for the booted machine.
4. To set the automatic registration in the Cyber Protection service, select the Register the
bootable media automatically check box, and then select the level of automatic registration:
l Ask for registration token at booting up
The token has to be provided every time when a machine is booted from this bootable media.
l Use the following token
The machine will be registered automatically when it is booted from this bootable media.

689 © Acronis International GmbH, 2003-2024

To register the bootable media after booting a machine from it

1. Boot the machine from the bootable media.

2. In the startup window, click Register media.
3. In Server, specify the Cyber Protection service address.
4. In Registration token, enter the registration token.
5. Click Register.

Network settings
While creating bootable media, you can preconfigure the network connections that will be used by
the bootable agent. The following parameters can be preconfigured:

l IP address
l Subnet mask
l Gateway
l DNS server
l WINS server

After the bootable agent starts on a machine, the configuration is applied to the machine’s network
interface card (NIC). If the settings have not been preconfigured, the agent uses DHCP auto
configuration.

You can also configure the network settings manually when the bootable agent is running on the
machine.

Preconfiguring multiple network connections

You can preconfigure TCP/IP settings for up to ten network interface cards (NICs). To ensure that
each NIC will be assigned the appropriate settings, create the media on the server for which the
media is customized. When you select an existing NIC in the wizard window, its settings are selected
and saved on the media. The MAC address of each existing NIC is also saved on the media.

You can change the settings, except for the MAC address, or configure the settings for a non-
existent NIC.

After the bootable agent starts on the server, it retrieves the list of available NICs. This list is sorted
by the slots that the NICs occupy, the closest to the processor is on top.

The bootable agent assigns each known NIC the appropriate settings, and identifies the NICs by
their MAC addresses. After the NICs with known MAC addresses are configured, the remaining NICs
are assigned the settings that you made for non-existent NICs, starting from the upper non-
assigned NIC.

You can customize the bootable media for any machine, and not only for the machine where the
media is created. To do so, configure the NICs according to their slot order on that machine: NIC1
occupies the slot closest to the processor, NIC2 is in the next slot, and so on. When the bootable

690 © Acronis International GmbH, 2003-2024

agent starts on that machine, it will not find the NICs with known MAC addresses and will configure
the NICs in the same order as you did.

Example

The bootable agent can use one of the network adapters for communication with the management
console through the production network. Automatic configuration can be done for this connection.
Sizeable data for recovery can be transferred through the second NIC, included in the dedicated
backup network by means of static TCP/IP settings.

Connecting to a machine booted from bootable media

Local connection
To operate directly on the machine booted from bootable media, click Manage this machine
locally in the startup window.

After a machine boots from bootable media, the machine terminal displays a startup window with
the IP addresses obtained from DHCP or set according to the preconfigured values.

Configuring network settings

To change the network settings for a current session, in the startup window, click Configure
network. The Network Settings window that appears allows you to configure the network settings
for each network interface card (NIC) of the machine.

The changes that are made during a session will be lost after the machine reboots.

Adding VLANs
In the Network Settings window, you can add virtual local area networks (VLANs). Use this
functionality if you need access to a backup location that is included in a specific VLAN.

VLANs are mainly used to divide a local area network into segments. A NIC that is connected to an
access port of the switch always has access to the VLAN specified in the port configuration. A NIC
connected to a trunk port of the switch can access the VLANs allowed in the port configuration only
if you specify the VLANs in the network settings.

To enable access to a VLAN via a trunk port

1. Click Add VLAN.

2. Select the NIC that provides access to the local area network that includes the required VLAN.
3. Specify the VLAN identifier.

After you click OK, a new entry appears in the list of network adapters.

If you need to remove a VLAN, click the required VLAN entry, and then click Remove VLAN.

691 © Acronis International GmbH, 2003-2024

Local operations with bootable media
Operations with bootable media are similar to the recovery operations that are performed under a
running operating system. The differences are as follows:

1. Under bootable media with a Windows-like volume representation, a volume has the same drive
letter as in Windows. Volumes that do not have drive letters in Windows (such as the System
Reserved volume) are assigned free letters in order of their sequence on the disk.
If the bootable media cannot detect Windows on the machine or detects more than one, all
volumes, including those without drive letters, are assigned letters in order of their sequence on
the disk. Thus, the volume letters may differ from those seen in Windows. For example, the D:
drive under the bootable media might correspond to the E: drive in Windows.

Note
It is advisable to assign unique names to the volumes.

2. The bootable media with a Linux-like volume representation shows local disks and volumes as
unmounted (sda1, sda2...).
3. Tasks cannot be scheduled. If you need to repeat an operation, configure it from scratch.
4. The log lifetime is limited to the current session. You can save the entire log or the filtered log
entries to a file.

Setting up a display mode

When you boot a machine via Linux-based bootable media, a display video mode is detected
automatically based on the hardware configuration (monitor and graphics card specifications). If the
video mode is detected incorrectly, do the following:

1. In the boot menu, press F11.

2. On the command line, enter vga=ask, and then proceed with booting.
3. From the list of supported video modes, choose the appropriate mode by typing its number (for
example, 318), and then press Enter.

If you do not want to follow this procedure every time you boot a given hardware configuration,
recreate the bootable media with the appropriate mode number (in the example above, vga=0x318)
specified in the Kernel parameters field.

Recovery with bootable media on-premises

1. Boot your machine from the bootable media.
2. Click Manage this machine locally.
3. Click Recover.
4. In What to recover, click Select data.
5. Select the backup file that you want to recover from.

692 © Acronis International GmbH, 2003-2024

 6. In the lower left pane, select the drives/volumes or files/folders that you want to recover, and
then click OK.
7. Configure the overwriting rules.
8. Configure the recovery exclusions.
9. Configure the recovery options.
10. Check that your settings are correct, and then click OK.

Remote operations with bootable media

Note
This feature is available with the Advanced Backup pack.

To see the bootable media in the Cyber Protect console, first you need to register it as described in
"Registering the bootable media" (p. 689).

After you register the media in the Cyber Protect console, it appears on the Devices > Bootable
media tab. A bootable media disappears from this tab when it has been offline for more than 30
days.

You can manage the bootable media remotely in the Cyber Protect console. For example, you can
recover data, restart the or shut down the machine booted with the media, or view information,
activities, and alerts about the media.

Important
You cannot update the bootable media remotely, on the Settings > Agents tab in the Cyber Protect
console.

To update the bootable media, create a new one, as described in the "Bootable Media Builder" (p.
678) section. Alternatively, download the ready-made media, by clicking your account icon
> Downloads > Bootable media in the Cyber Protect console.

To recover files or folders with bootable media remotely

1. In the Cyber Protect console, go to Devices > Bootable media.

1. Select the media that you want to use for data recovery.
2. Click Recovery.
3. Select the location, and then select the backup that you need. Note that backups are filtered by
location.
4. Select the recovery point, and then click Recover files/folders.
5. Browse to the required folder or use the search bar to obtain the list of the required files and
folders.
Search is language-independent.
You can use one or more wildcard characters (* and ?). For more details about using wildcards,
refer to "File filters (Inclusions/Exclusions)" (p. 438).
6. Click to select the files that you want to recover, and then click Recover.

693 © Acronis International GmbH, 2003-2024

 7. In Path, select the recovery destination.
8. [Optional] For advanced recovery configuration, click Recovery options. For more information,
refer to "Recovery options" (p. 494).
9. Click Start recovery.
10. Select one of the file overwriting options:
l Overwrite existing files
l Overwrite an existing file if it is older
l Do not overwrite existing files
Choose whether to restart the machine automatically.
11. Click Proceed to start the recovery. The recovery progress is shown on the Activities tab.

To recover disks, volumes, or entire machines with bootable media remotely

1. On the Devices tab, go to the Bootable media group, and then select the media that you want
to use for data recovery.
2. Click Recovery.
3. Select the location, and then select the backup that you need. Note that backups are filtered by
location.
4. Select the recovery point, and then click Recover > Entire machine.
If necessary, configure the target machine and volume mapping as described in "Recovering
physical machinesThis section describes recovery of physical machines by using the web
interface.Use bootable media instead of the web interface if you need to recover:A machine
running macOSA machine from a tenant in the Compliance modeAny operating system to bare
metal or to an offline machineThe structure of logical volumes (volumes created by Logical
Volume Manager in Linux). The media enables you to recreate the logical volume structure
automatically.You cannot recover disk-level backups of Intel-based Macs to Macs that use Apple
silicon processors, and vice-versa. You can recover files and folders.Recovery with
restartRecovery of an operating system and recovery of volumes that are encrypted with
BitLocker requires a restart. You can choose whether to restart the machine automatically or
assign it the Interaction required status. The recovered operating system goes online
automatically.Backed-up encrypted volumes are recovered as non-encrypted. Recovery of
BitLocker-encrypted volumes requires that there is a non-encrypted volume on the same
machine, and that this volume has at least 1 GB of free space. If either condition is not met, the
recovery fails.Recovering an encrypted system volume does not require any additional actions.
To recover an encrypted non-system volume, you must lock it first, for example, by opening a file
that resides on this volume. Otherwise, the recovery will continue without restart and the
recovered volume might not be recognized by Windows.If the recovery fails and your machine
restarts with the Cannot get file from partition error, try disabling Secure Boot. For more
information on how to do it, refer to Disabling Secure Boot in the Microsoft documentation.To
recover a physical machineSelect the backed-up machine.Click Recovery.Select a recovery point.
Note that recovery points are filtered by location.If the machine is offline, the recovery points are
not displayed. Do any of the following:If the backup location is cloud or shared storage (i.e. other
agents can access it), click Select machine, select a target machine that is online, and then select

694 © Acronis International GmbH, 2003-2024

 a recovery point.Select a recovery point on the Backup storage tab.Recover the machine as
described in "Recovering disks by using bootable media".Click Recover > Entire machine.The
software automatically maps the disks from the backup to the disks of the target machine.To
recover to another physical machine, click Target machine, and then select a target machine that
is online.If you are unsatisfied with the mapping result or if the disk mapping fails, click Volume
mapping to re-map the disks manually.The mapping section also enables you to choose
individual disks or volumes for recovery. You can switch between recovering disks and volumes
by using the Switch to... link in the upper-right corner. [Only available for Windows machines on
which a protection agent is installed] Enable the Safe recovery switch to ensure that the
recovered data is malware-free. For more information about how safe recovery works, see "Safe
recovery" (p. 1).Click Start recovery.Confirm that you want to overwrite the disks with their
backed-up versions. Choose whether to restart the machine automatically.The recovery progress
is shown on the Activities tab." (p. 1).
5. For advanced recovery configuration, click Recovery options. For more information, refer to
"Recovery options" (p. 494).
6. Click Start recovery.
7. Confirm that you want to overwrite the disks with their backed-up versions. Choose whether to
restart the machine automatically.
8. The recovery progress is shown on the Activities tab.

To restart the booted machine remotely

1. On the Devices tab, go to the Bootable media group, and then select the media that you want
to use for data recovery.
2. Click Reboot.
3. Confirm that you want to restart the machine booted with the media.

To shut down the booted machine remotely

1. On the Devices tab, go to the Bootable media group, and then select the media that you want
to use for data recovery.
2. Click Shut down.
3. Confirm that you want to shut down the machine booted with the media.

To view information about the bootable media

1. On the Devices tab, go to the Bootable media group, and then select the media that you want
to use for data recovery.
2. Click Details, Activities, or Alerts to see the corresponding information.

To delete bootable media remotely

1. On the Devices tab, go to the Bootable media group, and then select the media that you want
to use for data recovery.
2. Click Delete to delete the bootable media from the Cyber Protect console.
3. Confirm that you want to delete the bootable media.

695 © Acronis International GmbH, 2003-2024

Startup Recovery Manager
Startup Recovery Manager is a bootable component that resides on the hard drive. With Startup
Recovery Manager, you can start the bootable rescue utility without using a separate bootable
media.

If a failure occurs, restart the machine, wait for the prompt Press F11 for Acronis Startup
Recovery Manager to appear, and then press F11 or select the Startup Recovery Manager from the
boot menu (if you use the GRUB boot loader). Startup Recovery Manager starts and you can
perform a recovery.

Limitations
l [Not applicable to GRUB that is installed to the master boot record] Activating Startup Recovery
Manager overwrites the master boot record (MBR) with its own boot code. As a result, you might
need to reactivate any third-party boot loaders after the activation.
l [Not applicable to GRUB] Before activating Startup Recovery Manager in Linux, we recommend
that you install the boot loader to the root partition's boot record or to the /boot partitions' boot
record instead of installing it to the master boot record. Otherwise, manually reconfigure the
boot loader after the activation.

Activating Startup Recovery Manager

To enable the boot-time prompt Press F11 for Acronis Startup Recovery Manager (or add the
Startup Recovery Manager item to GRUB menu), you must activate Startup Recovery Manager.

Note
Activating Startup Recovery Manager on a machine with non-encrypted system volume requires at
least 100 MB of free space on this machine. Recovery with restart requires additional 100 MB.

To activate Startup Recovery Manager on a machine that has a BitLocker-encrypted volume, this
machine must have at least one non-encrypted volume on which there are at least 500 MB of free
space. Recovery with restart requires additional 500 MB of free space.

Backup operations that create One-click recovery backups will fail if Startup Recovery Manager is
not activated.

To activate Startup Recovery Manager

On a Windows or Linux machine with an agent

1. In the Cyber Protect console, select the machine on which you want to activate Startup Recovery
Manager.
2. Click Details.
3. Enable the Startup Recovery Manager switch.

On a machine without an agent

696 © Acronis International GmbH, 2003-2024

1. Boot the machine by using a bootable media.
2. In the bootable media graphical interface, click Tools > Activate Startup Recovery Manager.
3. Select Activate.
4. Click OK.
5. On the Details tab, check the Result row to verify that the activation succeeded, and then click
Close.

Deactivating Startup Recovery Manager

Deactivation disables the boot-time prompt Press F11 for Acronis Startup Recovery Manager (or
removes the Startup Recovery Manager item from the GRUB menu).

If Startup Recovery Manager is not activated, you can still recover a machine that fails to boot by
using a separate bootable media.

Note
Backup operations that create One-click recovery backups will fail if Startup Recovery Manager is
not activated.

To deactivate Startup Recovery Manager

On a Windows or Linux machine with an agent

1. In the Cyber Protect console, select the machine on which you want to deactivate Startup
Recovery Manager.
2. Click Details.
3. Disable the Startup Recovery Manager switch.

On a machine without an agent

1. Boot the machine by using a bootable media.

2. In the bootable media graphical interface, click Tools > Deactivate Startup Recovery Manager.
3. Select Deactivate.
4. Click OK.
5. On the Details tab, check the Result row to verify that the deactivation succeeded, and then
click Close.

697 © Acronis International GmbH, 2003-2024

Implementing disaster recovery
Note
l This functionality does not support Microsoft Azure backup locations.

About Cyber Disaster Recovery Cloud

Cyber Disaster Recovery Cloud (DR) – a part of Cyber Protection that provides disaster recovery
as a service (DRaaS). Cyber Disaster Recovery Cloud provides you with a fast and stable solution to
launch the exact copies of your machines on the cloud site and switch the workload from the
corrupted original machines to the recovery servers in the cloud in case of a man-made or a natural
disaster.

You can set up and configure disaster recovery in the following ways:

l Create a protection plan that includes the disaster recovery module and apply it to your devices.
This will automatically set up default disaster recovery infrastructure. See Create a disaster
recovery protection plan.
l Set up the disaster recovery cloud infrastructure manually and control each step. See "Setting up
recovery servers" (p. 742).

The key functionality

Note
Some features might require additional licensing, depending on the applied licensing model.

l Manage the Cyber Disaster Recovery Cloud service from a single console
l Extend up to 23 local networks to the cloud, by using a secure VPN tunnel
l Establish the connection to the cloud site without any VPN appliance1 deployment (the cloud-only
mode)
l Establish the point-to-site connection to your local and cloud sites
l Protect your machines by using recovery servers in the cloud
l Protect applications and appliances by using primary servers in the cloud
l Perform automatic disaster recovery operations for encrypted backups
l Perform a test failover in the isolated network
l Use runbooks to spin up the production environment in the cloud

1[Disaster Recovery] A special virtual machine that enables connection between the local network and the cloud site

via a secure VPN tunnel. The VPN appliance is deployed on the local site.

698 © Acronis International GmbH, 2003-2024

Software requirements

Supported operating systems

Protection with a recovery server has been tested for the following operating systems:

l CentOS 6.6, 7.x, 8.x

l Debian 9.x, 10.x, 11.x
l Red Hat Enterprise Linux 6.6, 7.x, 8.x
l Ubuntu 16.04, 18.04, 20.x, 21.x
l Oracle Linux 7.3 and 7.9 with Unbreakable Enterprise Kernel
l Windows Server 2008 R2
l Windows Server 2012/2012 R2
l Windows Server 2016 – all installation options, except for Nano Server
l Windows Server 2019 – all installation options, except for Nano Server
l Windows Server 2022 – all installation options, except for Nano Server

The software may work with other Windows operating systems and Linux distributions, but this is
not guaranteed.

Note
Protection with a recovery server has been tested for Microsoft Azure VM with the following
operating systems.

l Windows Server 2008 R2

l Windows Server 2012/2012 R2
l Windows Server 2016 – all installation options, except for Nano Server
l Windows Server 2019 – all installation options, except for Nano Server
l Windows Server 2022 – all installation options, except for Nano Server
l Ubuntu Server 20.04 LTS - Gen2 (Canonical). For more information about accessing the recovery
server console, see https://kb.acronis.com/content/71616.

Supported virtualization platforms

Protection of virtual machines with a recovery server has been tested for the following virtualization
platforms:

l VMware ESXi 5.1, 5.5, 6.0, 6.5, 6.7, 7.0

l Windows Server 2008 R2 with Hyper-V
l Windows Server 2012/2012 R2 with Hyper-V
l Windows Server 2016 with Hyper-V – all installation options, except for Nano Server
l Windows Server 2019 with Hyper-V – all installation options, except for Nano Server
l Windows Server 2022 with Hyper-V – all installation options, except for Nano Server

699 © Acronis International GmbH, 2003-2024

l Microsoft Hyper-V Server 2012/2012 R2
l Microsoft Hyper-V Server 2016
l Kernel-based Virtual Machines (KVM) — fully virtualized guests (HVM) only. Paravirtualized guests
(PV) are not supported.
l Red Hat Enterprise Virtualization (RHEV) 3.6
l Red Hat Virtualization (RHV) 4.0
l Citrix XenServer: 6.5, 7.0, 7.1, 7.2

The VPN appliance has been tested for the following virtualization platforms:

l VMware ESXi 5.1, 5.5, 6.0, 6.5, 6.7

l Windows Server 2008 R2 with Hyper-V
l Windows Server 2012/2012 R2 with Hyper-V
l Windows Server 2016 with Hyper-V – all installation options, except for Nano Server
l Windows Server 2019 with Hyper-V – all installation options, except for Nano Server
l Windows Server 2022 with Hyper-V – all installation options, except for Nano Server
l Microsoft Hyper-V Server 2012/2012 R2
l Microsoft Hyper-V Server 2016

The software may work with other virtualization platforms and versions, but this is not guaranteed.

Limitations
The following platforms and configurations are not supported in Cyber Disaster Recovery Cloud:

1. Unsupported platforms:
l Agents for Virtuozzo
l macOS
l Windows desktop operating systems are not supported due to Microsoft product terms.
l Windows Server Azure Edition
Azure Edition is a special version of Windows Server that was built specifically to run either as
an Azure IaaS virtual machine (VM) in Azure or as a VM on an Azure Stack HCI cluster. Unlike
the Standard and Datacenter editions, Azure Edition is not licensed to run on bare metal
hardware, Windows client Hyper-V, Windows Server Hyper-V, third-party hypervisors, or in
third-party clouds.
2. Unsupported configurations:
Microsoft Windows
l Dynamic disks are not supported
l Windows desktop operating systems are not supported (due to Microsoft product terms)
l Active Directory service with FRS replication is not supported
l Removable media without either GPT or MBR formatting (so-called "superfloppy") are not
supported
Linux

700 © Acronis International GmbH, 2003-2024

 l File systems without a partition table
l Linux workloads that are backed up with an agent from a guest OS and have volumes with the
following advanced Logical Volume Manager (LVM) configurations: Striped volumes, Mirrored
volumes, RAID 0, RAID 4, RAID 5, RAID 6, or RAID 10 volumes.

Note
Workloads with multiple operating systems installed are not supported.

3. Unsupported backup types:

l Continuous data protection (CDP) recovery points are incompatible.

Important
If you create a recovery server from a backup having a CDP recovery point, then during the
failback or creating backup of a recovery server, you will loose the data contained in the CDP
recovery point.

l Forensic backups cannot be used for creating recovery servers.

A recovery server has one network interface. If the original machine has several network interfaces,
only one is emulated.

Cloud servers are not encrypted.

Cyber Disaster Recovery Cloud trial version

You can use a trial version of Acronis Cyber Disaster Recovery Cloud for a period of 30 days. In this
case, Disaster Recovery has the following limitations for partner tenants:

l No access to public internet for recovery and primary servers. You cannot assign public IP
addresses to the servers.
l IPsec Multi-site VPN is not available.

Limitations when using Geo-redundant Cloud Storage

Geo-redundant Cloud Storage provides a secondary location for your backup data. The secondary
location is in a region that is geographically distinct from the primary storage location. Geographical
separation of regions ensures that - if there is a disaster that affects one of the regions and makes
the backup data unrecoverable - the other region will not be affected, and operations will continue.

Important
The Disaster Recovery service is not supported if the backup storage location is switched from the
primary location to the geo-redundant secondary location.

701 © Acronis International GmbH, 2003-2024

Disaster Recovery compatibility with encryption
software
Disaster recovery is compatible with the following disk-level encryption software:

l Microsoft BitLocker Drive Encryption

l McAfee Endpoint Encryption
l PGP Whole Disk Encryption

Note
l For workloads with disk-level encryption, we recommend that you install the protection agent in
the guest operating system of the workload, and perform agent-based backups.
l Failover and failback will not be supported for agentless backups of encrypted workloads.

For more information about the Cyber Protection compatibility with encryption software, see
"Compatibility with encryption software" (p. 40).

Compute points
In Disaster Recovery, compute points are used for primary servers and recovery servers during test
failover and production failover. Compute points reflect the compute resources used for running
the servers (virtual machines) in the cloud.

The consumption of compute points during disaster recovery depends on the server's parameters,
and the duration of the time period in which the server is in failover state. The more powerful the
server and the longer the time period, the more compute points will be consumed. And the more
compute points are consumed, the higher the price that you will be charged.

All servers that are running in the Acronis Cloud will be charged for compute points, depending on
their configured flavor, and regardless of their state (powered on or powered off).

Recovery servers in Standby state do not consume compute points and will not be charged for
compute points.

In the table below, you can see an example for eight servers in the cloud with different flavors, and
the corresponding compute points that they will consume per hour. You can change the flavors of
the servers in the Details tab.

Type CPU RAM Compute points

F1 1 vCPU 2 GB 1

F2 1 vCPU 4 GB 2

F3 2 vCPU 8 GB 4

702 © Acronis International GmbH, 2003-2024

 Type CPU RAM Compute points

F4 4 vCPU 16 GB 8

F5 8 vCPU 32 GB 16

F6 16 vCPU 64 GB 32

F7 16 vCPU 128 GB 64

F8 16 vCPU 256 GB 128

Using the information in the table, you can easily estimate how many compute points a server
(virtual machine) will consume.

For example, if you want to protect with Disaster Recovery one virtual machine with 4 vCPU* of 16
GB RAM, and one virtual machine with 2 vCPU with 8 GB of RAM, the first virtual machine will
consume 8 compute points per hour, and the second virtual machine – 4 compute points per hour.
If both virtual machines are in failover, the total consumption will be 12 compute points per hour, or
288 compute points for the whole day (12 compute points x 24 hours = 288 compute points).

* vCPU refers to a physical central processing unit (CPU) that is assigned to a virtual machine, and is
a time-dependent entity.

Note
If the overage for the Compute points quota is reached, all primary and recovery servers will be
shut down. It will not be possible to use these servers until the beginning of the next billing period,
or until you increase the quota. The default billing period is a full calendar month.

Setting up the disaster recovery functionality

Note
Some features might require additional licensing, depending on the applied licensing model.

To set up the disaster recovery functionality

1. Configure the connectivity type to the cloud site:

l Point-to-site connection
l Site-to-site OpenVPN connection
l Multi-site IPsec VPN connection
l Cloud-only mode
2. Create a protection plan with the backup module enabled and select the entire machine or
system plus boot volumes for backing up. At least one protection plan is required for creating a
recovery server.
3. Apply the protection plan to the local servers to be protected.
4. Create the recovery servers for each of your local servers that you want to protect.

703 © Acronis International GmbH, 2003-2024

5. Perform a test failover to check how it works.
6. [Optional] Create the primary servers for application replication.

As a result, you have set up the disaster recovery functionality to protect your local servers from a
disaster.

If a disaster occurs, you can fail over the workload to the recovery servers in the cloud. At least one
recovery point must be created before failing over to recovery servers. When your local site is
recovered from a disaster, you can switch the workload back to your local site by performing
failback. For more information about the failback process, see "Prerequisites" (p. 755) and
"Prerequisites" (p. 760).

Create a disaster recovery protection plan

Create a protection plan that includes the Disaster Recovery module and apply it to your devices.

By default, when creating a new protection plan, the Disaster Recovery module is disabled. After you
enable the disaster recovery functionality and apply the plan to your devices, the cloud network
infrastructure is created, including a recovery server for each protected device. The recovery server is
a virtual machine in the cloud that is a copy of the selected device. For each of the selected devices a
recovery server with default settings is created in a standby state (virtual machine not running). The
recovery server is sized automatically depending on the CPU and RAM of the protected device.
Default cloud network infrastructure is also created automatically: VPN gateway and networks on
the cloud site, to which the recovery servers are connected.

If you revoke, delete, or switch off the Disaster Recovery module of a protection plan, the recovery
servers and cloud networks are not deleted automatically. You can remove the disaster recovery
infrastructure manually, if needed.

Note
l After you configure disaster recovery, you will be able to perform a test or production failover
from any of the recovery points generated after the recovery server was created for the device.
Recovery points that were generated before the device was protected with disaster recovery (e.g.
before the recovery server was created) cannot be used for failover.
l A disaster recovery protection plan cannot be enabled if the IP address of a device cannot be
detected. For example, when virtual machines are backed up agentless and are not assigned an
IP address.
l When you apply a protection plan, the same networks and IP addresses are assigned in the cloud
site. The IPsec VPN connectivity requires that network segments of the cloud and local sites do
not overlap. If a Multi-site IPsec VPN connectivity is configured, and you apply a protection plan
to one or several devices later, you must additionally update the cloud networks and reassign the
IP addresses of the cloud servers. For more information, see "Reassigning IP addresses" (p. 732).

To create a disaster recovery protection plan

704 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Devices > All devices.
2. Select the machines that you want to protect.
3. Click Protect, and then click Create plan.
The protection plan default settings open.
4. Configure the backup options.
To use the disaster recovery functionality, the plan must back up the entire machine, or only the
disks, required for booting up and providing the necessary services, to a cloud storage.
5. Enable the Disaster recovery module by clicking the switch next to the module name.
6. Click Create.
The plan is created and applied to the selected machines.

What to do next
l You can edit the default configuration of the recovery server. For more information, see "Setting
up recovery servers" (p. 742).
l You can edit the default networking configuration. For more information, see "Setting up
connectivity" (p. 707).
l You can learn more about the recovery server default parameters and the cloud network
infrastructure. For more information, see "Editing the Recovery server default parameters" (p.
705) and "Cloud network infrastructure" (p. 706).

Editing the Recovery server default parameters

When you create and apply a disaster recovery protection plan, a recovery server with default
parameters is created. You can edit these default parameters later.

Note
A recovery server is created only if it does not exist. Existing recovery servers are not changed or
recreated.

To edit the recovery server default parameters

1. Go to Devices > All devices.

2. Select a device, and click Disaster recovery.
3. Edit the recovery server default parameters.
The recovery server parameters are described in the following table.

Recovery server Default Description

parameter value

CPU and RAM auto The number of virtual CPUs and the amount of
RAM for the recovery server. The default settings
will be automatically determined based on the
original device CPU and RAM configuration.

705 © Acronis International GmbH, 2003-2024

 Cloud network auto Cloud network to which the server will be
connected. For details on how cloud networks are
configured, see Cloud network infrastructure.

IP address in auto The IP address that the server will have in the
production production network. By default, the IP address of
network the original machine is set.

Test IP address disabled Test IP address gives you the capability to test a
failover in the isolated test network and to
connect to the recovery server via RDP or SSH
during a test failover. In the test failover mode,
the VPN gateway will replace the test IP address
with the production IP address by using the NAT
protocol. If a test IP address is not specified, the
console will be the only way to access the server
during a test failover.

Internet Access enabled Enable the recovery server to access the Internet
during a real or test failover. By default, TCP port
25 is denied for outbound connections.

Use Public address disabled Having a public IP address makes the recovery
server available from the Internet during a failover
or test failover. If you do not use a public IP
address, the server will be available only in your
production network. To use a public IP address,
you must enable internet access. The public IP
address will be shown after you complete the
configuration. By default, TCP port 443 is open for
inbound connections.

Set RPO threshold disabled RPO threshold defines the maximum allowable
time interval between the last recovery point and
the current time. The value can be set within 15 –
60 minutes, 1 – 24 hours, 1 – 14 days.

Cloud network infrastructure

The cloud network infrastructure consists of the VPN gateway on the cloud site and the cloud
networks to which the recovery servers will be connected.

Note
Applying a disaster recovery protection plan creates recovery cloud network infrastructure only if it
does not exist. Existing cloud networks are not changed or recreated.

The system checks devices IP addresses and if there are no existing cloud networks where an IP
address fits, it automatically creates suitable cloud networks. If you already have existing cloud

706 © Acronis International GmbH, 2003-2024

networks where the recovery servers IP addresses fit, the existing cloud networks will not be
changed or recreated.

l If you do not have existing cloud networks or you setup disaster recovery configuration for the
first time, the cloud networks will be created with maximum ranges recommended by IANA for
private use (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) based on your devices IP address range.
You can narrow your network by editing the network mask.
l If you have devices on multiple local networks, the network on the cloud site may become a
superset of the local networks. You may reconfigure networks in the Connectivity section. See
"Managing networks" (p. 726).
l If you need to set up Site-to-site Open VPN connectivity, download the VPN appliance and set up
it. See "Configuring Site-to-site Open VPN" (p. 718). Make sure your cloud networks ranges match
your local network ranges connected to the VPN appliance.
l To change the default network configuration, click the Go to connectivity link on the Disaster
Recovery module of the Protection plan, or navigate to Disaster Recovery > Connectivity.

Setting up connectivity
This section explains the network concepts necessary for you to understand how it all works in
Cyber Disaster Recovery Cloud. You will learn how to configure different types of connectivity to the
cloud site, depending on your needs. Finally, you will learn how to manage your networks in the
cloud and manage the settings of the VPN appliance and VPN gateway.

Networking concepts

Note
Some features might require additional licensing, depending on the applied licensing model.

With Cyber Disaster Recovery Cloud you can define the following connectivity types to the cloud site:

l Cloud-only mode
This type of connection does not require a VPN appliance deployment on the local site.
The local and cloud networks are independent networks. This type of connection implies either
the failover of all the local site's protected servers or partial failover of independent servers that
do not need to communicate with the local site.
Cloud servers on the cloud site are accessible through the point-to-site VPN, and public IP
addresses (if assigned).
l Site-to-site Open VPN connection
This type of connection requires a VPN appliance deployment on the local site.
The Site-to-site Open VPN connection allows to extend your networks to the cloud and retain the
IP addresses.
Your local site is connected to the cloud site by means of a secure VPN tunnel. This type of
connection is suitable in case you have tightly dependent servers on the local site, such as a web

707 © Acronis International GmbH, 2003-2024

 server and a database server. In case of partial failover, when one of these servers is recreated on
the cloud site while the other stays on the local site, they will still be able to communicate with
each other via a VPN tunnel.
Cloud servers on the cloud site are accessible through the local network, point-to-site VPN, and
public IP addresses (if assigned).
l Multi-site IPsec VPN connection
This type of connection requires a local VPN device that supports IPsec IKE v2.
When you start configuring the Multi-site IPsec VPN connection, Cyber Disaster Recovery Cloud
automatically creates a cloud VPN gateway with a public IP address.
With Multi-site IPsec VPN your local sites are connected to the cloud site by means of a secure
IPsec VPN tunnel.
This type of connection is suitable for Disaster Recovery scenarios when you have one or several
local sites hosting critical workloads or tightly dependent services.
In case of partial failover of one of the servers, the server is recreated on the cloud site while the
others remain on the local site, and they are still able to communicate with each other through an
IPsec VPN tunnel.
In case of partial failover of one of the local sites, the rest of the local sites remain operational,
and will still be able to communicate with each other through an IPsec VPN tunnel.
l Point-to-site remote VPN access
A secure Point-to-site remote VPN access to your cloud and local site workloads from outside by
using your endpoint device.
For a local site access, this type of connection requires a VPN appliance deployment on the local
site.

Cloud-only mode
The cloud-only mode does not require a VPN appliance deployment on the local site. It implies that
you have two independent networks: one on the local site, another on the cloud site. Routing is
performed with the router on the cloud site.

How routing works

In case the cloud-only mode is established, routing is performed with the router on the cloud site so
that servers from different cloud networks can communicate with each other.

708 © Acronis International GmbH, 2003-2024

Site-to-site Open VPN connection

Note
The availability of this feature depends on the service quotas that are enabled for your account.

To understand how networking works in Cyber Disaster Recovery Cloud, we will consider a case
when you have three networks with one machine each in the local site. You are going to configure
the protection from a disaster for the two networks – Network 10 and Network 20.

On the diagram below, you can see the local site where your machines are hosted, and the cloud
site where the cloud servers are launched in case of a disaster.

With the Cyber Disaster Recovery Cloud solution you can fail over all the workload from the
corrupted machines in the local site to the cloud servers in the cloud. You can protect up to 23
networks with Cyber Disaster Recovery Cloud.

709 © Acronis International GmbH, 2003-2024

To establish a Site-to-site Open VPN communication between the local and cloud sites, a VPN
appliance and a VPN gateway are used. When you start configuring the Site-to-site Open VPN
connection in the Cyber Protect console, the VPN gateway is automatically deployed in the cloud
site. Then, you must deploy the VPN appliance on your local site, add the networks to be protected,
and register the appliance in the cloud. Cyber Disaster Recovery Cloud creates a replica of your local
network in the cloud. A secure VPN tunnel is established between the VPN appliance and the VPN
gateway. It provides your local network extension to the cloud. The production networks in the
cloud are bridged with your local networks. The local and cloud servers can communicate through
this VPN tunnel as if they are all in the same Ethernet segment. Routing is performed with your local
router.

For each source machine to be protected, you must create a recovery server on the cloud site. It
stays in the Standby state until a failover event happens. If a disaster happens and you start a
failover process (in the production mode), the recovery server representing the exact copy of your
protected machine is launched in the cloud. It may be assigned the same IP address as the source
machine and it can be launched in the same Ethernet segment. Your clients can continue working
with the server, without noticing any background changes.

You can also start a failover process in the test mode. This means that the source machine is still
working and at the same time the respective recovery server with the same IP address is launched
in the cloud. To prevent IP address conflicts, a special virtual network is created in the cloud – test
network. The test network is isolated to prevent duplication of the source machine IP address in
one Ethernet segment. To access the recovery server in the test failover mode, when you create a

710 © Acronis International GmbH, 2003-2024

recovery server, you must assign a Test IP address to it. There are other parameters for the
recovery server that can be specified, they will be considered in the respective sections below.

How routing works

When a Site-to-site connection is established, routing between cloud networks is performed with
your local router. The VPN server does not perform routing between cloud servers located in
different cloud networks. If a cloud server from one network wants to communicate to a server
from another cloud network, the traffic goes through the VPN tunnel to the local router on the local
site, then the local router routes it to another network, and it goes back through the tunnel to the
destination server on the cloud site.

VPN gateway
The major component that allows communication between the local and cloud sites is the VPN
gateway. It is a virtual machine in the cloud on which special software is installed, and network is
specifically configured. The VPN gateway has the following functions:

l Connects the Ethernet segments of your local network and production network in the cloud in
the L2 mode.
l Provides iptables and ebtables rules.
l Works as a default router and NAT for the machines in the test and production networks.
l Works as a DHCP server. All machines in the production and test networks get the network
configuration (IP addresses, DNS settings) via DHCP. Every time a cloud server will get the same IP
address from the DHCP server. If you need to set up the custom DNS configuration, you should
contact the support team.
l Works as a caching DNS.

VPN gateway network configuration

The VPN gateway has several network interfaces:

l External interface, connected to the Internet

l Production interfaces, connected to the production networks
l Test interface, connected to the test network

In addition, two virtual interfaces are added for Point-to-site and Site-to-site connections.

When the VPN gateway is deployed and initialized, the bridges are created – one for the external
interface, and one for the client and production interfaces. Though the client-production bridge and
the test interface use the same IP addresses, the VPN gateway can route packages correctly by using
a specific technique.

VPN appliance
The VPN appliance is a virtual machine on the local site with Linux that has special software
installed, and a special network configuration. It allows communication between the local and cloud
sites.

711 © Acronis International GmbH, 2003-2024

Recovery servers
A recovery server – a replica of the original machine based on the protected server backups stored
in the cloud. Recovery servers are used for switching workloads from the original servers in case of
a disaster.

When creating a recovery server, you must specify the following network parameters:

l Cloud network (required): a cloud network to which a recovery server will be connected.
l IP address in production network (required): an IP address with which a virtual machine for a
recovery server will be launched. This address is used in both the production and test networks.
Before launching, the virtual machine is configured for getting the IP address via DHCP.
l Test IP address (optional): an IP address to access a recovery server from the client-production
network during the test failover, to prevent the production IP address from being duplicated in
the same network. This IP address is different from the IP address in the production network.
Servers in the local site can reach the recovery server during the test failover via the test IP
address, while access in the reverse direction is not available. Internet access from the recovery
server in the test network is available if the Internet access option was selected during the
recovery server creation.
l Public IP address (optional): an IP address to access a recovery server from the Internet. If a
server has no public IP address, it can be reached only from the local network.
l Internet access (optional): it allows a recovery server to access the Internet (in both the
production and test failover cases).

Public and test IP address

If you assign the public IP address when creating a recovery server, the recovery server becomes
available from the Internet through this IP address. When a packet comes from the Internet with the
destination public IP address, the VPN gateway remaps it to the respective production IP address by
using NAT, and then sends it to the corresponding recovery server.

712 © Acronis International GmbH, 2003-2024

If you assign the test IP address when creating a recovery server, the recovery server becomes
available in the test network through this IP address. When you perform the test failover, the
original machine is still running while the recovery server with the same IP address is launched in
the test network in the cloud. There is no IP address conflict as the test network is isolated. The
recovery servers in the test network are reachable by their test IP addresses, which are remapped to
the production IP addresses through NAT.

713 © Acronis International GmbH, 2003-2024

For more information about Site-to-site Open VPN, see "Site-to-site Open VPN - Additional
information" (p. 180).

Primary servers
A primary server – a virtual machine that does not have a linked machine on the local site if
compared to a recovery server. Primary servers are used for protecting an application by
replication, or running various auxiliary services (such as a web server).

Typically, a primary server is used for real-time data replication across servers running crucial
applications. You set up the replication by yourself, using the application's native tools. For example,
Active Directory replication, or SQL replication, can be configured among the local servers and the
primary server.

Alternatively, a primary server can be included in an AlwaysOn Availability Group (AAG) or Database
Availability Group (DAG).

Both methods require a deep knowledge of the application and the administrator rights. A primary
server constantly consumes computing resources and space on the fast disaster recovery storage. It
needs maintenance on your side: monitoring the replication, installing software updates, and
backing up. The benefits are the minimal RPO and RTO with a minimal load on the production
environment (as compared to backing up entire servers to the cloud).

Primary servers are always launched only in the production network and have the following network
parameters:

714 © Acronis International GmbH, 2003-2024

l Cloud network (required): a cloud network to which a primary server will be connected.
l IP address in production network (required): an IP address that the primary server will have in
the production network. By default, the first free IP address from your production network is set.
l Public IP address (optional): an IP address to access a primary server from the Internet. If a
server has no public IP address, it can be reached only from the local network, not through the
Internet.
l Internet access (optional): allows a primary server to access the Internet.

Multi-site IPsec VPN connection

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can use the Multi-site IPsec VPN connectivity to connect a single local site, or multiple local sites
to the Cyber Disaster Recovery Cloud through a secure L3 IPsec VPN connection.

This connectivity type is useful for Disaster Recovery scenarios if you have one of the following use
cases:

l you have one local site hosting critical workloads.

l you have multiple local sites hosting critical workloads, for example offices in different locations.
l you use third-party software sites, or managed service providers sites and are connected to them
through an IPsec VPN tunnel.

To establish a Multi-site IPsec VPN communication between the local sites and the cloud site, a VPN
gateway is used. When you start configuring the Multi-site IPsec VPN connection in the Cyber
Protect console, the VPN gateway is automatically deployed in the cloud site. You should configure
the cloud network segments and make sure that they do not overlap with the local network
segments. A secure VPN tunnel is established between local sites and the cloud site. The local and
cloud servers can communicate through this VPN tunnel as if they are all in the same Ethernet
segment.

For each source machine to be protected, you must create a recovery server on the cloud site. It
stays in the Standby state until a failover event happens. If a disaster happens and you start a
failover process (in the production mode), the recovery server representing the exact copy of your
protected machine is launched in the cloud. Your clients can continue working with the server,
without noticing any background changes.

You can also launch a failover process in the test mode. This means that the source machine is still
working and at the same time the respective recovery server is launched in the cloud in a special
virtual network that is created in the cloud – test network. The test network is isolated to prevent
duplication of IP addresses in the other cloud network segments.

715 © Acronis International GmbH, 2003-2024

VPN gateway
The major component that allows communication between the local sites and the cloud site is the
VPN gateway. It is a virtual machine in the cloud on which the special software is installed, and the
network is specifically configured. The VPN gateway serves the following functions:

l Connects the Ethernet segments of your local network and production network in the cloud in
the L3 IPsec mode.
l Works as a default router and NAT for the machines in the test and production networks.
l Works as a DHCP server. All machines in the production and test networks get the network
configuration (IP addresses, DNS settings) via DHCP. Every time a cloud server will get the same IP
address from the DHCP server.
If you prefer, you can set up a custom DNS configuration. For more information, see "Configuring
custom DNS servers" (p. 733).
l Works as a caching DNS.

How routing works

Routing between the cloud networks is performed with the router on the cloud site so that servers
from different cloud networks can communicate with each other.

Point-to-site remote VPN access

Note
The availability of this feature depends on the service quotas that are enabled for your account.

The Point-to-site connection is a secure connection from the outside by using your endpoint devices
(such as computer or laptop) to the cloud and local sites through a VPN. It is available after you
establish a Site-to-site Open VPN connection to the Cyber Disaster Recovery Cloud site. This type of
connection is useful in the following cases:

l In many companies, the corporate services and web resources are available only from the
corporate network. You can use the Point-to-site connection to securely connect to the local site.
l In case of a disaster, when a workload is switched to the cloud site and your local network is
down, you may need direct access to your cloud servers. This is possible through the Point-to-site
connection to the cloud site.

For the Point-to-site connection to the local site, you need to install the VPN appliance on the local
site, configure the Site-to-site connection, and then the Point-to-site connection to the local site.
Thus, your remote employees will have access to the corporate network through L2 VPN.

The scheme below shows the local site, cloud site, and communications between servers
highlighted in green. The L2 VPN tunnel connects your local and cloud sites. When a user establishes
a Point-to-site connection, the communications to the local site are performed through the cloud
site.

716 © Acronis International GmbH, 2003-2024

The Point-to-site configuration uses certificates to authenticate to the VPN client. Additionally user
credentials are used for authentication. Note the following about the Point-to-site connection to the
local site:

l Users should use their Cyber Protect Cloud credentials to authenticate in the VPN client. They
must have either a "Company Administrator" or a "Cyber Protection" user role.
l If you re-generated the OpenVPN configuration, you need to provide the updated configuration
to all of the users using the Point-to-site connection to the cloud site.

Automatic deletion of unused customer environments on the cloud site

The Disaster Recovery service tracks the usage of the customer environments created for disaster
recovery purposes and automatically deletes them if they are unused.

The following criteria are used to define if the customer tenant is active:

l Currently, there is at least one cloud server or there were cloud server(s) in the last seven days.
OR

l The VPN access to local site option is enabled and either the Site-to-site Open VPN tunnel is
established or there are data reported from the VPN appliance for the last 7 days.

All the rest of the tenants are considered as inactive tenants. For such tenants the system performs
the following:

l Deletes the VPN gateway and all cloud resources related to the tenant.
l Unregisters the VPN appliance.

The inactive tenants are rolled back to their state before the connectivity was configured.

717 © Acronis International GmbH, 2003-2024

Initial connectivity configuration
This section describes connectivity configuration scenarios.

Configuring Cloud-only mode

To configure a connection in the cloud-only mode

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.

2. Select Cloud-only and click Configure.
As a result, the VPN gateway and cloud network with the defined address and mask are
deployed on the cloud site.

To learn how to manage your networks in the cloud and set up the VPN gateway settings, refer to
"Managing cloud networks".

Configuring Site-to-site Open VPN

Note
The availability of this feature depends on the service quotas that are enabled for your account.

Requirements for the VPN appliance

System requirements
l 1 CPU
l 1 GB RAM
l 8 GB disk space

Ports
l TCP 443 (outbound) – for VPN connection
l TCP 80 (outbound) – for automatic update of the appliance

Ensure that your firewalls and other components of your network security system allow connections
through these ports to any IP address.

Configuring a Site-to-site Open VPN connection

The VPN appliance extends your local network to the cloud through a secure VPN tunnel. This kind
of connection is often referred to as a "Site-to-site" (S2S) connection. You can follow the procedure
below or watch the video tutorial.

To configure a connection through the VPN appliance

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.

2. Select Site-to-site Open VPN connection, and click Configure.

718 © Acronis International GmbH, 2003-2024

 The system starts deploying the VPN gateway in the cloud. This will take some time. Meanwhile,
you can proceed to the next step.

Note
The VPN gateway is provided without additional charge. It will be deleted if the Disaster
Recovery functionality is not used, i.e. no primary or recovery server is present in the cloud for
seven days.

3. In the VPN appliance block, click Download and deploy. Depending on the virtualization
platform you are using, download the VPN appliance for VMware vSphere or Microsoft Hyper-V.
4. Deploy the appliance and connect it to the production networks.
In vSphere, ensure that Promiscuous mode and Forged transmits are enabled and set to
Accept for all virtual switches that connect the VPN appliance to the production networks. To
access these settings, in vSphere Client, select the host > Summary > Network, and then select
the switch > Edit settings... > Security.
In Hyper-V, create a Generation 1 virtual machine with 1024 MB of memory. Also, we
recommend that you enable Dynamic Memory for the machine. Once the machine is created,
go to Settings > Hardware > Network Adapter > Advanced Features and select the Enable
MAC address spoofing check box.
5. Power on the appliance.
6. Open the appliance console and log in with the "admin"/"admin" user name and password.
7. [Optional] Change the password.
8. [Optional] Change the network settings if needed. Define which interface will be used as the
WAN for Internet connection.
9. Register the appliance in the Cyber Protection service by using the credentials of the company
administrator.
These credentials are only used once to retrieve the certificate. The data center URL is
predefined.

Note
If two-factor authentication is configured for your account, you will also be prompted to enter
the TOTP code. If two-factor authentication is enabled but not configured for your account, you
cannot register the VPN appliance. First, you must go to the Cyber Protect console login page
and complete the two-factor authentication configuration for your account. For more details on
two-factor authentication, go to the Management Portal Administrator's Guide.

Once the configuration is complete, the appliance will have the Online status. The appliance
connects to the VPN gateway and starts to report information about networks from all active
interfaces to the Cyber Disaster Recovery Cloud service. The Cyber Protect console shows the
interfaces, based on the information from the VPN appliance.

719 © Acronis International GmbH, 2003-2024

Configuring Multi-site IPsec VPN

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can configure a Multi-site IPsec VPN connection in the following two ways:

l from the Disaster Recovery > Connectivity tab.

l by applying a protection plan on one or several devices, and then manually switching from the
automatically created Site-to-site Open VPN connection to a Multi-site IPsec VPN connection,
configuring the Multi-site IPsec VPN settings, and reassigning IP addresses.

To configure a Multi-site IPsec VPN connection from the Connectivity tab

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.

2. In the Multi-site VPN connection section, click Configure.
A VPN gateway is deployed on the cloud site.
3. Configure the Multi-site IPsec VPN settings.

To configure a Multi-site IPsec VPN connection from a protection plan

1. In the Cyber Protect console, go to Devices.

2. Apply a protection plan to one or multiple devices from the list.
The recovery server and the cloud infrastructure settings are automatically configured for Site-to
site Open VPN connectivity.
3. Go to Disaster Recovery > Connectivity.
4. Click Show properties.
5. Click Switch to Multi-site IPsec VPN.
6. Configure the Multi-site IPsec VPN settings.
7. Reassign the IP addresses of the cloud network and cloud servers.

Configuring the Multi-site IPsec VPN settings

Note
The availability of this feature depends on the service quotas that are enabled for your account.

After you configure a Multi-site IPsec VPN, you must configure the cloud site and the local sites
settings on the Disaster Recovery > Connectivity tab.

Prerequisites
l Multi-site IPsec VPN connectivity is configured. For more information about configuring the Multi-
site IPsec VPN connectivity, see "Configuring Multi-site IPsec VPN" (p. 720).
l Each local IPsec VPN gateway has a public IP address.

720 © Acronis International GmbH, 2003-2024

l Your cloud network has enough IP addresses for the cloud servers that are copies of your
protected machines (in the production network), and for the recovery servers (with one or two IP
addresses, depending on your needs).
l [If you use a firewall between the local sites and the cloud site] The following IP protocols and
UDP ports are allowed on the local sites: IP Protocol ID 50 (ESP), UDP Port 500 (IKE), and UDP Port
4500.
l The NAT-T configuration on the local sites is disabled.

To configure a Multi-site IPsec VPN connection

1. Add one or more networks to the cloud site.

a. Click Add Network.

Note
When you add a cloud network, a corresponding test network is added automatically with
the same network address and mask for performing test failovers. The cloud servers in the
test network have the same IP addresses as the ones in the cloud production network. If you
need to access a cloud server from the production network during a test failover, when you
create a recovery server, assign it a second test IP address.

b. In the Network address field, type the IP address of the network.

c. In the Network mask field, type the mask of the network.
d. Click Add.
2. Configure the settings for each local site that you want to connect to the cloud site, following the
recommendations for the local sites. For more information about these recommendations, see
"General recommendations for local sites" (p. 722).
a. Click Add Connection.
b. Enter a name for the of the local VPN gateway.
c. Enter the public IP address of the local VPN gateway.
d. [Optional] Enter a description of the local VPN gateway.
e. Click Next.
f. In the Pre-shared key field, type the pre-shared key, or click Generate a new pre-shared
key to use an automatically generated value.

Note
You must use the same pre-shared key for the local and the cloud VPN gateways.

g. Click IPsec/IKE security settings to configure the settings. For more information about the
settings that you can configure, see "IPsec/IKE security settings" (p. 722).

721 © Acronis International GmbH, 2003-2024

 Note
You can use the default settings, which are populated automatically, or use custom values.
Only IKEv2 protocol connections are supported. The default Startup action when
establishing the VPN is Add (your local VPN gateway initiates the connection), but you can
change it to Start (the cloud VPN gateway initiates the connection) or Route (suitable for
firewalls that support the route options).

h. Configure the Network policies.

The network policies specify the networks to which the IPsec VPN connects. Type the IP
address and mask of the network using the CIDR format. The local and cloud network
segments should not overlap.
i. Click Save.

General recommendations for local sites

Note
The availability of this feature depends on the service quotas that are enabled for your account.

When you configure the local sites for your Multi-site IPsec VPN connectivity, consider the following
recommendations:

l For each IKE Phase, set at least one of the values that are configured in the cloud site for the
following parameters: Encryption algorithm, Hash algorithm, and Diffie-Hellman group numbers.
l Enable Perfect forward secrecy with at least one of the values for Diffie-Hellman group numbers
that is configured in the cloud site for IKE Phase 2.
l Configure the same Lifetime value for IKE Phase 1 and IKE Phase 2 as in the cloud site.
l Configurations with NAT traversal (NAT-T) are not supported. Disable the NAT-T configuration on
the local site. Otherwise, the additional UDP encapsulation cannot be negotiated.
l The Startup action configuration defines which side initiates the connection. The default value
Add means that the local site initiates the connection, and cloud site is waiting for the connection
initiation. Change the value to Start if you want the cloud site to initiate the connection, or to
Route if you want both sides to be able to initiate the connection (suitable for firewalls that
support the route option).

For more information and configuration examples for different solutions, see:

l This series of knowledge base articles

l This video example

IPsec/IKE security settings

Note
The availability of this feature depends on the service quotas that are enabled for your account.

The following table provides more information about the Psec/IKE security parameters.

722 © Acronis International GmbH, 2003-2024

 Parameter Description

Encryption algorithm The encryption algorithm that will be used to

ensure that data is not viewable while in transit. By
default, all algorithms are selected. You must
configure at least one of the selected algorithms on
your local gateway device for each IKE phase.

Hash algorithm The hash algorithm that will be used to verify the
data integrity and authenticity. By default, all
algorithms are selected. You must configure at
least one of the selected algorithms on your local
gateway device for each IKE phase.

Diffie-Hellman group numbers The Diffie-Hellman group numbers define the

strength of the key that is used in the Internet Key
Exchange (IKE) process.

Higher group numbers are more secure but

require additional time for the key to compute.

By default, all groups are selected. You must

configure at least one of the selected groups on
your local gateway device for each IKE phase.

Lifetime (seconds) The lifetime value determines the duration of a

connection instance with a set of
encryption/authentication keys for user packets,
from successful negotiation to expiry.

Range for Phase 1: 900-28800 seconds with default

28800.

Range for Phase 2: 900-3600 seconds with default

3600.

The lifetime for Phase 2 must be less than the

lifetime for Phase 1.

The connection is re-negotiated through the keying

channel before it expires, see Rekey margin time.
If the local and the remote side do not agree on the
lifetime, a clutter of superseded connections will
occur on the side with the longer lifetime. See also
Rekey margin time and Rekey fuzz.

Rekey margin time (seconds) The margin time before connection expiration or
keying-channel expiration, during which the local
side of the VPN connection attempts to negotiate a
replacement. The exact time of the rekey is
randomly selected based on the value of Rekey
fuzz. Relevant only locally, the remote side does

723 © Acronis International GmbH, 2003-2024

 Parameter Description

not need to agree on it. Range: 900-3600 seconds.

The default value is 3600.

Replay window size (packet) The IPsec replay window size for this connection.

The default -1 uses the value configured with

charon.replay_window in the strongswan.conf file.

Values larger than 32 are supported only when

using the Netlink backend.

A value of 0 disables the IPsec replay protection.

Rekey fuzz (%) The maximum percentage by which marginbytes,

marginpackets and margintime are randomly
increased to randomize rekeying intervals
(important for hosts with many connections).

The Rekey fuzz value can exceed 100%. The value

of marginTYPE, after the random increase, must
not exceed lifeTYPE, where TYPE is one of bytes,
packets or time.

The value 0% disables randomization. Relevant

only locally, the remote side does not need to
agree on it.

DPD timeout (seconds) Time after which a dead peer detection (DPD)
timeout occurs. You can specify value 30 or higher.
The default value is 30.

Dead peer detection (DPD) timeout The action to take after a dead peer detection
action (DPD) timeout occurs.

Restart - Restart the session when DPD timeout

occurs.

Clear - End the session when DPD timeout occurs.

None - Take no action when DPD timeout occurs.

Startup action Determines which side initiates the connection and

establishes the tunnel for the VPN connection.

Add - your local VPN gateway initiates the

connection.

Start - the cloud VPN gateway initiates the

connection.

Route - suitable for VPN gateways that support the

route option. The tunnel is up only when there is
traffic initiated from either the local VPN gateway,

724 © Acronis International GmbH, 2003-2024

 Parameter Description

or the cloud VPN gateway.

Recommendations for the Active Directory Domain Services availability

If your protected workloads need to authenticate in a domain controller, we recommend that you
have an Active Directory Domain Controller (AD DC) instance at the Disaster Recovery site.

Active Directory Domain Controller for L2 Open VPN connectivity

With the L2 Open VPN connectivity, the IP addresses of the protected workloads are retained in the
cloud site during a test failover or a production failover. Therefore, the AD DC during a test failover
or a production failover has the same IP address as in the local site.

With custom DNS you can set your own custom DNS server for all cloud servers. For more
information, see "Configuring custom DNS servers" (p. 733).

Active Directory Domain Controller for L3 IPsec VPN connectivity

With L3 IPsec VPN connectivity, the IP addresses of the protected workloads are not retained in the
cloud site. Therefore, we recommend that you have an additional dedicated AD DC instance as a
primary server in the cloud site before you perform a production failover.

The recommendations for a dedicated AD DC instance that is configured as a primary server in the
cloud site are the following:

l Turn off Windows firewall.

l Join the primary server to the Active Directory service.
l Ensure that the primary server has Internet access.
l Add the Active Directory feature.

With custom DNS you can set your own custom DNS server for all cloud servers. For more
information, see "Configuring custom DNS servers" (p. 733).

Configuring Point-to-site remote VPN access

Note
The availability of this feature depends on the service quotas that are enabled for your account.

If you need to connect to your local site remotely, you can configure the Point-to-site connection to
the local site. You can follow the procedure below or watch the video tutorial.

Prerequisites
l A Site-to-site Open VPN connectivity is configured.
l The VPN appliance is installed on the local site.

To configure the Point-to-site connection to the local site

725 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.
2. Click Show properties.
3. Enable the VPN access to local site option.
4. Ensure that your user who needs to establish the Point-to-site connection to the local site has:
l a user account in Cyber Protect Cloud. These credentials are used for authentication in the
VPN client. Otherwise, create a user account in Cyber Protect Cloud.
l a "Company Administrator" or "Cyber Protection" user role.
5. Configure the OpenVPN client:
a. Download the OpenVPN client version 2.4.0 or later from the following location
https://openvpn.net/community-downloads/.
b. Install the OpenVPN client on the machine from which you want to connect to the local site.
c. Click Download configuration for OpenVPN. The configuration file is valid for users in your
organization with the "Company Administrator" or "Cyber Protection" user role.
d. Import the downloaded configuration to OpenVPN.
e. Log in to the OpenVPN client with your Cyber Protect Cloud user credentials (see step 4
above).
f. [Optional] If two-factor authentication is enabled for your organization, then you should
provide the one-time generated TOTP code.

Important
If you enabled two-factor authentication for your account, you need to re-generate the
configuration file and renew it for your existing OpenVPN clients. Users must re-log in to Cyber
Protect Cloud to set up two-factor authentication for their accounts.

As a result, your user will be able to connect to machines on the local site.

Network management
This section describes network management scenarios.

Managing networks

Note
Some features might require additional licensing, depending on the applied licensing model.

Site-to-site Open VPN connection

To add a network on the local site and extend it to the cloud

1. On the VPN appliance, set up the new network interface with the local network that you want to
extend in the cloud.
2. Log in to the VPN appliance console.
3. In the Networking section, set up network settings for the new interface.

726 © Acronis International GmbH, 2003-2024

The VPN appliance starts to report information about networks from all active interfaces to Cyber
Disaster Recovery Cloud. The Cyber Protect console shows the interfaces based on the information
from the VPN appliance.

To delete a network extended to the cloud

1. Log in to the VPN appliance console.

2. In the Networking section, select the interface that you want to delete, and then click Clear
network settings.
3. Confirm the operation.

As a result, the local network extension to the cloud via a secure VPN tunnel will be stopped. This
network will operate as an independent cloud segment. If this interface is used to pass the traffic
from (to) the cloud site, all of your network connections from (to) the cloud site will be disconnected.

To change the network parameters

1. Log in to the VPN appliance console.

2. In the Networking section, select the interface that you want to edit.
3. Click Edit network settings.
4. Select one of the two possible options:
l For automatic network configuration via DHCP, click Use DHCP. Confirm the operation.
l For manual network configuration, click Set static IP address. The following settings are
available for editing:
o IP address: the IP address of the interface in the local network.
o VPN gateway IP address: the special IP address which is reserved for the cloud segment
of network for the proper Cyber Disaster Recovery Cloud service work.
o Network mask: network mask of the local network.
o Default gateway: default gateway on the local site.
o Preferred DNS server: primary DNS server on the local site.
o Alternate DNS server: secondary DNS server on the local site.

727 © Acronis International GmbH, 2003-2024

l Make the necessary changes and confirm them by pressing Enter.

Cloud-only mode
You can have up to 23 networks in the cloud.

To add a new cloud network

1. Go to Disaster Recovery > Connectivity.

2. On Cloud site, click Add cloud network.
3. Define the cloud network parameters: the network address and mask. When ready, click Done.

As a result, the additional cloud network with the defined address and mask will be created on the
cloud site.

To delete a cloud network

Note
You cannot delete a cloud network if there is at least one cloud server in it. First, delete the cloud
server, and then delete the network.

1. Go to Disaster Recovery > Connectivity.

2. On Cloud site, click the network address that you want to delete.
3. Click Delete and confirm the operation.

To change cloud network parameters

1. Go to Disaster Recovery > Connectivity.

2. On Cloud site, click the network address that you want to edit.
3. Click Edit.
4. Define the network address and mask, and click Done.

IP address reconfiguration
For proper disaster recovery performance, the IP addresses assigned to the local and cloud servers
must be consistent. If there is any inconsistency or mismatch in IP addresses, you will see the
exclamation mark next to the corresponding network in Disaster Recovery > Connectivity.

728 © Acronis International GmbH, 2003-2024

Some of the commonly known reasons of IP address inconsistency are listed below:

1. A recovery server was migrated from one network to another or the network mask of the cloud
network was changed. As a result, cloud servers have the IP addresses from networks to which
they are not connected.
2. The connectivity type was switched from one without Site-to-site connection to a Site-to-site
connection. As a result, a local server is placed in the network different from the one that was
created for the recovery server on the cloud site.
3. The connectivity type was switched from Site-to-site Open VPN to Multi-site IPsec VPN, or from
Multi-site IPsec VPN to Site-to-site Open VPN. For more information about this scenario, see
Switching connections and Reassigning IP addresses.
4. Editing the following network parameters on the VPN appliance site:
l Adding an interface via the network settings
l Editing the network mask manually via the interface settings
l Editing the network mask via DHCP
l Editing the network address and mask manually via the interface settings
l Editing the network mask and address via DHCP
As a result of the actions listed above, the network on the cloud site may become a subset or
superset of the local network, or the VPN appliance interface may report the same network
settings for different interfaces.

To resolve the issue with network settings

1. Click the network that requires IP address reconfiguration.

You will see a list of servers in the selected network, their status, and IP addresses. The servers
whose network settings are inconsistent are marked with the exclamation mark.
2. To change network settings for a server, click Go to server. To change network settings for all
servers at once, click Change in the notification block.
3. Change the IP addresses as needed by defining them in the New IP and New test IP fields.
4. When ready, click Confirm.

Move servers to a suitable network

When you create a disaster recovery protection plan and apply it on selected devices, the system
checks devices IP addresses and automatically creates cloud networks if there are not existing cloud
networks where IP address fits. By default, the cloud networks are configured with maximum
ranges recommended by IANA for private use (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). You can
narrow your network by editing the network mask.

In case if the selected devices was on the multiple local networks, the network on the cloud site may
become a superset of the local networks. In this case, to reconfigure cloud networks:

1. Click the cloud network that requires network size reconfiguration and then click Edit.
2. Reconfigure the network size with the correct settings.
3. Create other required networks.
4. Click the notification icon next to the number of devices connected to the network.

729 © Acronis International GmbH, 2003-2024

5. Click Move to a suitable network.
6. Select the servers that you want to move to suitable networks and then click Move.

Managing the VPN appliance settings

Note
The availability of this feature depends on the service quotas that are enabled for your account.

In the Cyber Protect console (Disaster Recovery > Connectivity), you can:

l Download log files.

l Unregister the appliance (if you need to reset the VPN appliance settings or switch to the cloud-
only mode).

To access these settings, click the i icon in the VPN appliance block.

In the VPN appliance console, you can:

l Change the password for the appliance.

l View/change the network settings and define which interface to use as the WAN for the Internet
connection.
l Register/change the registration account (by repeating the registration).
l Restart the VPN service.
l Reboot the VPN appliance.
l Run the Linux shell command (only for advanced troubleshooting cases).

Reinstalling the VPN gateway

If there is an issue with the VPN gateway which you cannot resolve, you might want to reinstall the
VPN gateway. Possible issues include the following:

l The VPN gateway is in Error status.

l The VPN gateway is in Pending status for a long time.
l The VPN gateway status is undetermined for a long time.

Reinstalling the VPN gateway process includes the following automatic actions: deleting the existing
VPN gateway virtual machine completely, installing a new virtual machine from the template, and
applying the settings of the previous VPN gateway on the new virtual machine.

Prerequisites:
One of the connectivity types to the cloud site must be set.

To reinstall the VPN gateway

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.

2. Click the gear icon of the VPN gateway, and select Reinstall VPN gateway.

730 © Acronis International GmbH, 2003-2024

3. In the Reinstall VPN gateway dialog, enter your login.
4. Click Reinstall.

Enabling and disabling the Site-to-site connection

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can enable the Site-to-site connection in the following cases:

l If you need the cloud servers on the cloud site to communicate with servers on the local site.
l After a failover to the cloud, the local infrastructure is recovered, and you want to fail back your
servers to the local site.

To enable the site-to-site connection

1. Go to Disaster Recovery > Connectivity.

2. Click Show properties, and then enable the Site-to-site connection option.

As a result, the site-to-site VPN connection is enabled between the local and cloud sites. The Cyber
Disaster Recovery Cloud service gets the network settings from the VPN appliance and extends the
local networks to the cloud site.

If you do not need cloud servers on the cloud site to communicate with servers on the local site, you
can disable the Site-to-site connection.

To disable the site-to-site connection

1. Go to Disaster Recovery > Connectivity.

2. Click Show properties, and then disable the Site-to-site connection option.

As a result, the local site is disconnected from the cloud site.

Switching the Site-to-site connection type

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can easily switch form a Site-to-site Open VPN connection to a Multi-site IPsec VPN connection,
and from a Multi-site IPsec VPN connection to a Site-to-site Open VPN connection.

When you switch the connectivity type, the active VPN connections are deleted, but the cloud
servers and network configurations are preserved. However, you will still need to reassign the
IP addresses of the cloud networks and servers.

The following table compares the basic characteristics of the Site-to-site Open VPN connection and
the Multi-site IPsec VPN connection.

731 © Acronis International GmbH, 2003-2024

 Site-to-site Open VPN Multi-site IPsec VPN

Local site support Single Single, Multiple

VPN Gateway mode L2 Open VPN L3 IPsec VPN

Network segments Extends the local network to the Local networks and
cloud network cloud network segments
should not overlap

Supports Point-to-Site access Yes No

to local site

Supports Point-to-Site access Yes Yes

to cloud site

Requires a public IP offering No Yes

item

To switch form a Site-to-site Open VPN connection to a Multi-site IPsec VPN connection

1. In the Cyber Protect console, go to Disaster Recovery -> Connectivity.

2. Click Show properties.
3. Click Switch to multi-site IPsec VPN.
4. Click Reconfigure.
5. Reassign the IP addresses of the cloud network and cloud servers.
6. Configure the Multi-site IPsec connection settings.

To switch form a Multi-site IPsec VPN connection to a Site-to-site Open VPN connection

1. In the Cyber Protect console, go to Disaster Recovery -> Connectivity.

2. Click Show properties.
3. Click Switch to site-to-site Open VPN.
4. Click Reconfigure.
5. Reassign the IP addresses of the cloud network and cloud servers.
6. Configure the Site-to-site connection settings.

Reassigning IP addresses

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You must reassign the IP addresses of the cloud networks and the cloud servers in order to
complete the configuration in the following cases:

l After you switch from Site-to-site Open VPN to Multi-site IPsec VPN, or the opposite.
l After you apply a protection plan (if the Multi-site IPsec VPN connectivity is configured).

732 © Acronis International GmbH, 2003-2024

To reassign the IP address of a cloud network

1. In the Connectivity tab, click the IP address of the cloud network.

2. In the Network pop-up, click Edit.
3. Type the new the network address and network mask.
4. Click Done.

After you reassign the IP address of a cloud network, you must reassign the cloud servers that
belong to the reassigned cloud network.

To reassign the IP address of a server

1. In the Connectivity tab, click the IP address of the server in the cloud network.
2. In the Servers pop-up, click Change IP address.
3. In the Change IP address pop-up, type the new IP address of the server, or use the
automatically generated IP address which is part of the reassigned cloud network.

Note
Cyber Disaster Recovery Cloud automatically assigns IP addresses from the cloud network to all
cloud servers that were part of the cloud network before the reassignment of the network IP
address. You can use the suggested IP addresses to reassign the IP addresses of all the cloud
servers at once.

4. Click Confirm.

Configuring custom DNS servers

Note
The availability of this feature depends on the service quotas that are enabled for your account.

When you configure a connectivity, Cyber Disaster Recovery Cloud creates your cloud network
infrastructure. The cloud DHCP server automatically assigns default DNS servers to the recovery
servers and primary servers, but you can change the default settings and configure custom
DNS servers. The new DNS settings will be applied at the time of the next request to the DHCP
server.

Prerequisites:
One of the connectivity types to the cloud site must be set.

To configure a custom DNS server

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.

2. Click Show properties.
3. Click Default (Provided by Cloud Site).
4. Select Custom servers.
5. Type the IP address of the DNS server.

733 © Acronis International GmbH, 2003-2024

6. [Optional] If you want to add another DNS server, click Add, and type the DNS server IP address.

Note
After you add the custom DNS servers, you can also add the default DNS servers. In that way, if
the custom DNS servers are unavailable, Cyber Disaster Recovery Cloud will use the default
DNS servers.

7. Click Done.

Deleting custom DNS servers

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can delete DNS servers from the custom DNS list.

Prerequisites:
Custom DNS servers are configured.

To delete a custom DNS server

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.

2. Click Show properties.
3. Click Custom servers.
4. Click the delete icon next to the DNS server.

Note
The delete operation is disabled when only one custom DNS server is available. If you want to
delete all custom DNS servers, select Default (provided by Cloud Site) .

5. Click Done.

Configuring local routing

In addition to your local networks that are extended to the cloud through the VPN appliance, you
may have other local networks that are not registered in the VPN appliance but have servers which
need to communicate with cloud servers. To establish the connectivity between such local servers
and cloud servers, you need to configure the local routing settings.

To configure local routing

1. Go to Disaster Recovery>Connectivity.
2. Click Show properties, and then click Local routing.

734 © Acronis International GmbH, 2003-2024

3. Specify the local networks in the CIDR notation.
4. Click Save.

As a result, the servers from the specified local networks can communicate with the cloud servers.

Allowing DHCP traffic over L2 VPN

If devices on your local site get their IP address from a DHCP server, you can protect the DHCP
server with Disaster Recovery, fail it over to the cloud, and then allow the DHCP traffic to run over L2
VPN. Thus, your DHCP server will be running in the cloud, but will continue assigning IP addresses to
your local devices.

Prerequisites:

A Site-to-site L2 VPN connectivity type to the cloud site must be set.

To allow the DHCP traffic via the L2 VPN connection

1. Go to Disaster Recovery > Connectivity tab.

2. Click Show Properties.
3. Enable the Allow DHCP traffic via L2 VPN switch.

Managing point-to-site connection settings

Note
The availability of this feature depends on the service quotas that are enabled for your account.

In the Cyber Protect console, go to Disaster Recovery > Connectivity and then click Show
properties in the upper right corner.

735 © Acronis International GmbH, 2003-2024

VPN access to local site
This option is used for managing VPN access to the local site. By default it is enabled. If it is disabled,
then the Point-to-site access to the local site will be not allowed.

Download configuration for OpenVPN

This will download the configuration file for the OpenVPN client. The file is required to establish a
Point-to-site connection to the cloud site.

Re-generate configuration
You can re-generate the configuration file for the OpenVPN client.

This is required in the following cases:

l If you suspect that the configuration file is compromised.

l If two-factor authentication was enabled for your account.

As soon as the configuration file is updated, connecting by means of the old configuration file
becomes not possible. Make sure to distribute the new file among the users who are allowed to use
the Point-to-site connection.

Active point-to-site connections

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can view all active point-to-site connections in Disaster recovery > Connectivity. Click the
machine icon on the blue Point-to-site line and you will see the detailed information about active
point-to-site connections grouped by the user name.

736 © Acronis International GmbH, 2003-2024

Working with logs
Disaster Recovery collects logs for the VPN appliance and the VPN gateway. The logs are saved as
.txt files, which are compressed in a .zip archive. You can download and extract the archive, and use
the information for troubleshooting or monitoring purposes.

The following list describes the log files that are part of the .zip archive, and the information that
they contain.

dnsmasq.config.txt - The file contains information about the configuration of the service that
provides DNS and DHCP addresses.

dnsmsq.leases.txt - The file contains information about the current DHCP address leases.

dnsmasq_log.txt - The file contains logs of the dnsmasq service.

ebtables.txt - The file contains information about the firewall tables.

free.txt - The file contains information about the free memory.

ip.txt - The file contains the logs from the configuration of the network interfaces, including their
names which can be used in the configuration of the Capturing network packets settings.

NetworkManager_log.txt - The file contains logs from the NetworkManager service.

NetworkManager_status.txt - The file contains information about the status of the NetworkManager
service.

openvpn@p2s_log.txt - The file contains logs from the OpenVPN service.

openvpn@p2s_status.txt - The file contains information about the status of the VPN tunnels.

737 © Acronis International GmbH, 2003-2024

ps.txt - The file contains information about the currently running processes on the VPN gateway or
VPN appliance.

resolf.conf.txt - The file contains information about the configuration of the DNS servers.

routes.txt - The file contains information about the networking routes.

uname.txt - The file contains information about the current version of the kernel of the operating
system.

uptime.txt - The file contains information about the length of period for which the operating system
has not been restarted.

vpnserver_log.txt - The file contains logs from the VPN service.

vpnserver_status.txt - The file contains information about the status of the VPN server.

For more information about log files that are specific to the IPsec VPN connectivity, see "Multi-site
IPSec VPN log files" (p. 742).

Downloading the logs of the VPN appliance

You can download and extract the archive that contains the logs of the VPN appliance, and use the
information for troubleshooting or monitoring purposes.

To download the logs of the VPN appliance

1. On the Connectivity page, click the gear icon next to the VPN appliance.
2. Click the Download log.
3. [Optional] Select Capture network packets, and configure the settings. For more information,
see "Capturing network packets" (p. 739).
4. Click Done.
5. When the .zip archive is ready for download, click Download log, and save it locally.

Downloading the logs of the VPN gateway

You can download and extract the archive that contains the logs of the VPN gateway, and use the
information for troubleshooting or monitoring purposes.

To download the logs of the VPN gateway

1. On the Connectivity page, click the gear icon next to the VPN gateway.
2. Click the Download log.
3. [Optional] Select Capture network packets, and then configure the settings. For more
information, see "Capturing network packets" (p. 739).
4. Click Done.
5. When the .zip archive is ready for download, click Download log, and save it locally.

738 © Acronis International GmbH, 2003-2024

Capturing network packets
To troubleshoot and analyze the communication between the local production site and a primary or
recovery server, you can choose to collect network packets on the VPN gateway or VPN appliance.

After collecting 32000 network packets, or reaching time limit, capturing network packets stops, and
the results are written in a .libpcap file that is added to the logs .zip archive.

The following table provides more information about the Capture network packets settings that
you can configure.

Setting Description

Network The network interface on which to capture network packets. If you want to
interface capture network packets on all network interfaces, select Any.
name

Time limit The time limit for capturing network packets. The maximum value you can set is
(seconds) 1800.

Filtering An extra filter to apply on the captured network packets.

You can enter a string containing protocols, ports, directions, and their
combinations, separated by space, such as: "and", "or", "not", " ( ", " ) ", "src",
"dst", "net", "host", "port", "ip", "tcp", "udp", "icmp", "arp", "esp".

If you want to use brackets, surround them with spaces. You can also enter IP
addresses and network addresses, for example: "icmp or arp" and "port 67 or
68".

For more information about the values that you can enter, see the Linux
tpcdump help.

Troubleshooting the IPsec VPN configuration

Note
The availability of this feature depends on the service quotas that are enabled for your account.

When you configure or use the IPsec VPN connection, you might experience problems.

You can learn more about the problems that you encountered in the IPsec log files, and check the
Troubleshooting IPsec VPN configuration issues topic for possible solutions of some of the common
problems that might occur.

Troubleshooting IPsec VPN configuration issues

Note
The availability of this feature depends on the service quotas that are enabled for your account.

739 © Acronis International GmbH, 2003-2024

The following table describes the IPsec VPN configuration problems that occur most often, and
explains how to troubleshoot them.

Problem Possible solution

I see the following error message: IKE Click Retry and check if a more specific error
phase 1 negotiation error. Check the message appears. For example, a more specific
IPsec IKE settings on the Cloud and error message may be an error message about an
the Local sites. algorithm mismatch or an incorrect Pre-shared
key.

Note
For security reasons, the following restrictions
apply to the IPsec VPN connectivity:

l IKEv1 is called for deprecation in RFC8247 and

is not supported due to security risks. Only
IKEv2 protocol connections are supported.
l The following Encryption algorithms are not
considered secure and are not supported: DES,
and 3DES.
l The following Hash algorithms are not
considered secure and are not supported:
SHA1, and MD5.
l Diffie-Hellman group number 2 is not
considered secure and is not supported.

The connection between my local site Check:

and the cloud site stays in status
l If the UDP port 500 is open (when you use a
Connecting.
firewall).
l The connectivity between the local site and the
cloud site.
l If the IP address of the local site is correct.

The connection between my local site You see this status when the Startup action for
and the cloud site stays in status Waiting cloud site is set to Add, which means that the cloud
for a connection. site is waiting for the local site to initiate the
connection.

Initiate connection from the local site.

The connection between my local site You see this status when the Startup action for
and the cloud site stays in status Waiting cloud site is set to Route.
for traffic.
If you are expecting a connection from the local
site, do the following:

l From the local site, try to ping the virtual

machine in the cloud site. This is a standard
behavior necessary for establishing a tunnel for

740 © Acronis International GmbH, 2003-2024

 Problem Possible solution

some devices, for example Cisco ASA. (Route

mode)
l Ensure that the local site established a tunnel by
setting the Startup action of the local site to
Start.

The connection between my local site This issue may be due to the following reasons:
and the cloud site is established, but I
l Network mapping in the cloud IPsec site is
can see that one or more of the network
different from the network mapping in the local
policies are down.
site.
Ensure that the network mappings and the
sequence of the network policies in the local
and cloud sites match exactly.
l This state is correct when the Startup action of
the local site and/or of the cloud site is set to
Route (for example, on Cisco ASA devices), and
currently there is no traffic. You can try to ping
to make sure that the tunnel is established. If
the ping is not working, check the network
mapping on the local and the cloud site.

I want restart a specific IPsec connection. To restart a specific IPsec connection:

1. In the Disaster recovery > Connectivity

screen, click the IPsec connection.
2. Click Disable connection.
3. Click the IPsec connection again.
4. Click Enable connection.

Downloading the IPsec VPN log files

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can find additional information about the IPsec connectivity in the log files on the VPN server.
The log files are compressed in a .zip archive that you can download and extract.

Prerequisites
Multi-site IPsec VPN connectivity is configured.

To download the .zip archive with the log files

1. In the Cyber Protect console, go to Disaster Recovery > Connectivity.

2. Click the gear icon next to the VPN gateway of the cloud site.
3. Click Download log.

741 © Acronis International GmbH, 2003-2024

4. Click Done.
5. When the .zip archive is ready for download, click Download log, and save it locally.

Multi-site IPSec VPN log files

Note
The availability of this feature depends on the service quotas that are enabled for your account.

The following list describes the IPsec VPN log files that are part of the zip archive, and the
information that they contain.

l ip.txt - The file contains the logs from the configuration of the network interfaces. You must see
two IP addresses - a public IP address, and a local IP address. If you do not see these IP addresses
in the log, there is a problem. Contact the Support team.

Note
The mask for the public IP address must be 32.

l swanctl-list-loaded-config.txt - The file contains information about all IPsec sites.

If you do not see a site in the file, then the IPsec configuration was not applied. Try to update the
configuration and save it, or contact the Support team.
l swanctl-list-active-sas.txt - The file contains connections and policies that are in status active
or a connecting.

Setting up recovery servers

This section describes the concepts of failover and failback, creation of a recovery server, and the
disaster recovery operations.

Creating a recovery server

To create a recovery server that will be a copy of your workload, follow the procedure below. You
can also watch the video tutorial that demonstrates the process.

Important
When you perform a failover, you can select only recovery points that were created after the
creation of the recovery server.

Prerequisites
l A protection plan must be applied to the original machine that you want to protect. This plan
must back up the entire machine, or only the disks, required for booting up and providing the
necessary services, to a cloud storage.
l One of the connectivity types to the cloud site must be set.

To create a recovery server

742 © Acronis International GmbH, 2003-2024

1. On the All devices tab, select the machine that you want to protect.
2. Click Disaster recovery, and then click Create recovery server.
3. Select the number of virtual cores and the size of RAM.

Note
You can see the compute points for every option. The number of compute points reflects the
cost of running the recovery server per hour. For more information, see "Compute points" (p.
702).

4. Specify the cloud network to which the server will be connected.

5. Select the DHCP option.

DHCP option Description

Provided by Default setting. The IP address of the server will be provided by an

cloud site automatically configured DHCP server in the cloud.

Custom The IP address of the server will be provided by your own DHCP server in
the cloud.

6. [Optional] Specify the MAC address.

The MAC address is a unique identifier that is assigned to the network adapter of the server. If
you use custom DHCP, you can configure it to always assign a specific IP adresses to a specific
MAC address. In that way you will ensure that the recovery server always gets the same
IP address. You can run applications that have licenses that are registered with the MAC address.
7. Specify the IP address that the server will have in the production network. By default, the IP
address of the original machine is set.

Note
If you use a DHCP server, add this IP address to the server exclusion list in order to avoid IP
address conflicts.
If you use a custom DHCP server, you must specify the same IP address in IP address in
production network as the one configured in the DHCP server. Otherwise, test failover will not
work properly, and the server will not be reachable via a public IP address.

8. [Optional] Select the Test IP address check box, and then specify the IP address.
This will give you the capability to test a failover in the isolated test network and to connect to
the recovery server via RDP or SSH during a test failover. In the test failover mode, the VPN
gateway will replace the test IP address with the production IP address by using the NAT
protocol.
If you leave the check box cleared, the console will be the only way to access the server during a
test failover.

743 © Acronis International GmbH, 2003-2024

 Note
If you use a DHCP server, add this IP address to the server exclusion list, in order to avoid IP
address conflicts.

You can select one of the proposed IP addresses or type in a different one.
9. [Optional] Select the Internet access check box.
This will enable the recovery server to access the Internet during a real or test failover. By
default, the TCP port 25 is open for outbound connections to public IP addresses.
10. [Optional] Set the RPO threshold.
The RPO threshold defines the maximum time interval allowed between the last suitable
recovery point for a failover and the current time. The value can be set within 15 – 60 minutes, 1
– 24 hours, 1 – 14 days.
11. [Optional] Select the Use public IP address check box.
Having a public IP address makes the recovery server available from the Internet during a
failover or test failover. If you leave the check box cleared, the server will be available only in
your production network.
The Use public IP address option requires the Internet access option to be enabled.
The public IP address will be shown after you complete the configuration. By default, TCP port
443 is open for inbound connections to public IP addresses.

Note
If you clear the Use Public IP address check box or delete the recovery server, its public IP
address will not be reserved.

12. [Optional] [If the backups for the selected machine are encrypted by using encryption as a
machine property], specify the password that will be automatically used when creating a virtual
machine for the recovery server from the encrypted backup.
a. Click Specify, and then enter the password for the encrypted backup and define a name for
the credentials.
By default, you will see the most recent backup in the list.
b. [Optional] To view all the backups, select Show all backups.
c. Click Done.

Note
Although the password that you specify will be stored in a secure credentials store, saving
passwords might be against your compliance obligations.

13. [Optional] Change the recovery server name.

14. [Optional] Type a description for the recovery server.
15. [Optional] Click the Cloud firewall rules tab to edit the default firewall rules. For more
information, see "Setting firewall rules for cloud servers" (p. 769).
16. Click Create.

744 © Acronis International GmbH, 2003-2024

The recovery server appears in the Disaster Recovery > Servers > Recovery servers tab of the
Cyber Protect console. You can view its settings by selecting the original machine and clicking
Disaster recovery.

How failover works

Production failover

Note
The availability of this feature depends on the service quotas that are enabled for your account.

When a recovery server is created, it stays in the Standby state. The corresponding virtual machine
does not exist until you start a failover. Before starting a failover process, you must create at least
one disk image backup (with bootable volume) of the original machine.

When starting the failover process, you select the recovery point (backup) of the original machine
from which a virtual machine with the predefined parameters will be created. The failover operation
uses the "run VM from a backup" functionality. The recovery server gets the transition state
Finalization. This process implies transferring the server's virtual disks from the backup storage
('cold' storage) to the disaster recovery storage ('hot' storage).

Note
During the Finalization, the server is accessible and operable, although the performance is lower
than normal. You can open the server console by clicking the Console is ready link. The link is
available in the VM State column on the Disaster Recovery > Servers screen, and in the server's
Details view.

When the Finalization is completed, the server performance reaches its normal value. The server
state changes to Failover. The workload is now switched from the original machine to the recovery
server in the cloud site.

745 © Acronis International GmbH, 2003-2024

If the recovery server has a protection agent inside, the agent service is stopped in order to avoid
interference (such as starting a backup or reporting outdated statuses to the backup component).

On the diagram below, you can see both the failover and failback processes.

Test failover
During a test failover, the virtual machine is not finalized. This means that the agent reads the
virtual disks' content directly from the backup, performing random access to different parts of the
backup, so its performance might be slower than the normal performance. For more information
about the test failover process, see "Performing a test failover" (p. 746).

Automated test failover

When automated test failover is configured, it is performed once a month without any manual
interaction. For more information, see "Automated test failover" (p. 748) and "Configuring
automated test failover" (p. 749).

Performing a test failover

Performing a test failover means starting a recovery server in a test VLAN that is isolated from your
production network. You can test several recovery servers at a time and check their interaction. In
the test network, the servers communicate using their production IP addresses, but they cannot
initiate TCP or UDP connections to the workloads in your local network.

During test failover, the virtual machine (recovery server) is not finalized. The agent reads the
content of the virtual disks directly from the backup and randomly accesses different parts of the
backup. This might make the performance of the recovery server in the test failover state slower
than its normal performance.

746 © Acronis International GmbH, 2003-2024

Though performing a test failover is optional, we recommend that you make it a regular process
with a frequency that you find adequate in terms of cost and safety. A good practice is creating a
runbook – a set of instructions describing how to spin up the production environment in the cloud.

Important
You must create a recovery server in advance to protect your devices from a disaster.

You can perform failover only from recovery points that were created after the recovery server of
the device was created.

At least one recovery point must be created before failing over to a recovery server. The maximum
number of recovery points that is supported is 100.

To perform a test failover

1. Select the original machine or select the recovery server that you want to test.
2. Click Disaster Recovery.
The description of the recovery server opens.
3. Click Failover.
4. Select the failover type Test failover.
5. Select the recovery point (backup), and then click Start.
6. If the backup that you selected is encrypted by using encryption as a machine property:
a. Enter the encryption password for the backup set.

Note
The password will only be saved temporarily and will be used only for the current test
failover operation. The password is automatically deleted from the credentials store if the
test failover is stopped, or after the test failover completes.

b. [Optional] To save the password for the backup set and use it in subsequent failover
operations, select the Store the password in a secure credentials store... check box and
then, in the Credentials name field, enter a name for the credentials.

Important
The password will be stored in a secured credentials store and will be applied automatically
in subsequent failover operations. However, saving passwords might conflict with your
compliance obligations.

c. Click Done.
When the recovery server starts, its state changes to Testing failover.

747 © Acronis International GmbH, 2003-2024

7. Test the recovery server by using any of the following methods:
l In Disaster Recovery > Servers, select the recovery server, and then click Console.
l Connect to the recovery server by using RDP or SSH, and the test IP address that you specified
when creating the recovery server. Try the connection from both inside and outside the
production network (as described in "Point-to-site connection").
l Run a script within the recovery server.
The script may check the login screen, whether applications are started, the Internet
connection, and the ability of other machines to connect to the recovery server.
l If the recovery server has access to the Internet and a public IP address, you may want to use
TeamViewer.
8. When the test is complete, click Stop testing.
The recovery server is stopped. All changes made to the recovery server during the test failover
are not preserved.

Note
The Start server and Stop server actions are not applicable for test failover operations, both in
runbooks and when starting a test failover manually. If you try executing such an action, it will fail
with the following error message:
Failed: The action is not applicable to the current server state.

Automated test failover

With automated test failover, the recovery server is tested automatically once a month without any
manual interaction.

The automated test failover process consists of the following parts:

1. creating a virtual machine from the last recovery point

2. taking a screenshot of the virtual machine

748 © Acronis International GmbH, 2003-2024

3. analyzing if the operating system of the virtual machine starts successfully
4. notifying you about the test failover status

Note
Automated test failover consumes compute points.

You can configure the automated test failover in the recovery server's settings. For more
information, see "Configuring automated test failover" (p. 749).

Note that, in very rare cases, automated test failover might be skipped and might not be performed
at the scheduled time. This is because production failover has higher priority than automated test
failover, so the hardware resources (CPU and RAM) allocated for automated test failover might be
temporarily limited to ensure that there are enough resources for a concurrent production failover.

If automated test failover is skipped for some reason, an alert will be raised.

Note
Automated test failover will fail if the backups of the original machine are encrypted by using
encryption as a machine property, and the encryption password is not specified when creating the
recovery server. For more information about specifying the encryption password, see "Creating a
recovery server" (p. 742).

Configuring automated test failover

By configuring automated test failover, you can test your recovery server every month without
performing any manual actions.

To configure automated test failover

1. In the console, go to Disaster recovery > Servers > Recovery servers, and then select the
recovery server.
2. Click Edit.
3. In the Automated test failover section, in the Schedule field, select Monthly.
4. [Optional] In Screenshot timeout, change the default value of the maximum time period (in
minutes) for the system to try performing automated test failover.
5. [Optional] If you want to save the Screenshot timeout value as the default and have it
populated automatically when you enable automated test failover for the other recovery servers,
select Set as default timeout.
6. Click Save.

Viewing the automated test failover status

You can view the details of a completed automated test failover, such as status, start time, end time,
duration, and the screenshot of the virtual machine.

To view the automated test failover status of a recovery server

749 © Acronis International GmbH, 2003-2024

1. In the console, go to Disaster recovery > Servers > Recovery servers and then select the
recovery server.
2. In the Automated test failover section, check the details of the last automated test failover.
3. [Optional] Click Show screenshot to view the screenshot of the virtual machine.

Disabling automated test failover

You can disable automated test failover if you want to save resources or you do not need
automated test failover to be performed for a certain recovery server.

To disable automated test failover

1. In the console, go to Disaster recovery > Servers > Recovery servers, and then select the
recovery server.
2. Click Edit.
3. In the Automated test failover section, in the Schedule field, select Never.
4. Click Save.

Performing a failover

Note
The availability of this feature depends on the service quotas that are enabled for your account.

A failover is a process of moving a workload from your premises to the cloud, and also the state
when the workload remains in the cloud.

When you start a failover, the recovery server starts in the production network. To avoid
interference and unwanted issues, ensure that the original workload is not online and cannot be
accessed via VPN.

To avoid a backup interference into the same cloud archive, manually revoke the protection plan
from the workload that is currently in Failover state. For more information about revoking plans,
see Revoking a protection plan.

Important
You must create a recovery server in advance to protect your devices from a disaster.

You can perform failover only from recovery points that were created after the recovery server of
the device was created.

At least one recovery point must be created before failing over to a recovery server. The maximum
number of recovery points that is supported is 100.

You can follow the instructions below or watch the video tutorial.

To perform a failover

750 © Acronis International GmbH, 2003-2024

1. Ensure that the original machine is not available on the network.
2. In the Cyber Protect console, go to Disaster recovery > Servers > Recovery servers and select
the recovery server.
3. Click Failover.
4. Select the type of failover Production failover.
5. Select the recovery point (backup), and then click Start.
6. [If the backup that you selected is encrypted by using encryption as a machine property]
a. Enter the encryption password for the backup set.

Note
The password will only be saved temporarily and will be used only for the current failover
operation. The password is automatically deleted from the credentials store after the failover
operation completes and the server returns to the Standby state.

b. [Optional] To save the password for the backup set and use it in subsequent failover
operations, select the Store the password in a secure credentials store... check box and
then, in the Credentials name field, enter a name for the credentials.

Important
The password will be stored in a secured credentials store and will be applied automatically
in subsequent failover operations. However, saving passwords might conflict with your
compliance obligations.

c. Click Done.
When the recovery server starts, its state changes to Finalization, and after some time to
Failover.

Important
It is critical to understand that the server is available in both the Finalization and Failover
states. During the Finalization state, you can access the server console by clicking the Console
is ready link. The link is available in the VM State column on the Disaster Recovery > Servers
screen, and in the server's Details view. For details, see "How failover works" (p. 745).

751 © Acronis International GmbH, 2003-2024

7. Ensure that the recovery server is started by viewing its console. Click Disaster Recovery >
Servers, select the recovery server, and then click Console.
8. Ensure that the recovery server can be accessed using the production IP address that you
specified when creating the recovery server.

Once the recovery server is finalized, a new protection plan is automatically created and applied to
it. This protection plan is based on the protection plan that was used for creating the recovery
server, with certain limitations. In this plan, you can change only the schedule and retention rules.
For more information, refer to "Backing up the cloud servers".

If you want to cancel failover, select the recovery server and click Cancel failover. All changes
starting from the failover moment - except the recovery server backups - will be lost. The recovery
server will return back to the Standby state.

If you want to perform failback, select the recovery server and click Failback.

How to perform failover of servers using local DNS

If you use DNS servers on the local site for resolving machine names, then after a failover the
recovery servers, corresponding to the machines relying on the DNS, will fail to communicate
because the DNS servers used in the cloud are different. By default, the DNS servers of the cloud
site are used for the newly created cloud servers. If you need to apply custom DNS settings, contact
the support team.

How to perform failover of a DHCP server

Your local infrastructure may have the DHCP server located on a Windows or Linux host. When such
a host is failed over to the cloud site, the DHCP server duplication issue occurs because the VPN
gateway in the cloud also performs the DHCP role. To resolve this issue, do one of the following:

l If only the DHCP host was failed over to the cloud, while the rest local servers are still on the local
site, then you must log in to the DHCP host in the cloud and turn off the DHCP server on it. Thus,
there will be no conflicts and only the VPN gateway will work as the DHCP server.

752 © Acronis International GmbH, 2003-2024

l If your cloud servers already got the IP addresses from the DHCP host, then you must log in to
the DHCP host in the cloud and turn off the DHCP server on it. You must also log in to the cloud
servers and renew the DHCP lease to assign new IP addresses allocated from the correct DHCP
server (hosted on the VPN gateway).

Note
The instructions are not valid when your cloud DHCP server is configured with the Custom DHCP
option, and some of the recovery or primary servers get their IP address from this DHCP server.

How failback works

Note
The availability of this feature depends on the service quotas that are enabled for your account.

A failback is a process of moving the workload from the cloud back to a physical or virtual machine
on your local site. You can perform a failback on a recovery server in Failover state, and continue
using the server on your local site.

You can perform automated failover to a virtual or physical target machine on your local site. During
the failback, you can transfer the backup data to your local site while the virtual machine in the
cloud continues to run. This technology helps you to achieve a very short downtime period, which is
estimated and displayed in the Cyber Protect console. You can view it and use this information to
plan your activities and, if necessary, warn your clients about an upcoming downtime period.

The failback processes to target virtual machines and target physical machines are slightly different.
For more information about the phases of the failback process, see "Failback to a target virtual
machine" (p. 753) and "Failback to a target physical machine" (p. 758).

In specific cases when you cannot use the automated failback procedure, you can perform a manual
failback. For more information, see "Manual failback" (p. 762).

Note
Runbook operations support the failback in manual mode only. This means that if you start the
failback process by executing a runbook that includes a Failback server step, the procedure will
require a manual interaction: you must manually recover the machine, and confirm or cancel the
failback process from the Disaster Recovery > Servers tab.

Failback to a target virtual machine

Note
The availability of this feature depends on the service quotas that are enabled for your account.

The failback process to a target virtual machine consists of four phases.

753 © Acronis International GmbH, 2003-2024

1. Planning. During this phase, you restore the IT infrastructure at your local site (such as the hosts
and the network configurations), configure the failback parameters, and plan when to start the
data transfer.

Note
To minimize the total time for the failback process, we recommend that you start the data
transfer phase immediately after you set up your local servers, and then continue with the
configuration of the network and the rest of the local infrastructure during the data transfer
phase.

2. Data transfer. During this phase, the data is transferred from the cloud site to the local site
while the virtual machine in the cloud continues to run. You can start the next phase - switchover
- at any time during the data transfer phase, but you should consider the following relations.
The longer you remain in the data transfer phase,
l the longer the virtual machine in the cloud continues to run.
l the more data will be transferred to your local site.
l the higher the cost you will pay (you spend more compute points).
l the shorter the downtime period that you will experience during the switchover phase.
If you want to minimize the downtime, start the switchover phase after more than 90% of the
data is transferred to the local site.

754 © Acronis International GmbH, 2003-2024

 If you can afford to experience a longer downtime period, and do not want to spend more
compute points for running the virtual machine in the cloud, you can start the switchover phase
earlier.
If you cancel the failback process during the data transfer phase, the transferred data will not be
deleted from the local site. To avoid potential issues, manually delete the transferred data before
you start a new failback process. The following data transfer process will start from the
beginning.
3. Switchover. During this phase, the virtual machine in the cloud is turned off, and the remaining
data - including the last backup increment - is transferred to the local site. If no backup plan is
applied on the recovery server, a backup will be performed automatically during the switchover
phase, which will slow down the process.
You can view the estimated time to finish (downtime period) of this phase in the Cyber Protect
console. When all the data is transferred to the local site (there is no data loss, and the virtual
machine on the local site is an exact copy of the virtual machine in the cloud), the switchover
phase completes. The virtual machine on the local site is recovered, and the validation phase
starts automatically.
4. Validation. During this phase, the virtual machine on the local site is ready and automatically
started. You can verify if the virtual machine is working correctly, and:
l If everything is working as expected, confirm the failback. After the failback confirmation, the
virtual machine in the cloud is deleted, and the recovery server returns to the Standby state.
This is the end of the failback process.
l If something is wrong, you can cancel the switchover and return to the data transfer phase.

Performing failback to a virtual machine

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can perform failback to a target virtual machine on your local site.

Prerequisites
l The agent that you will use to perform failback is online and is not currently used for another
failback operation.
l Your Internet connection is stable.
l There is at least one full backup of the virtual machine in the cloud.

To perform a failback to a virtual machine

1. In the Cyber Protect console, go to Disaster recovery > Servers.

2. Select the recovery server that is in the Failover state.
3. Click the Failback tab.
4. In the Failback parameters section, select Virtual machine as a Target, and configure the
other parameters.

755 © Acronis International GmbH, 2003-2024

 Note that by default, some of the Failback parameters are populated automatically with
suggested values, but you can change them.
The following table provides more information about the Failback parameters.

Parameter Description

Backup size Amount of data that will be transferred to your local site during the
failback process.
After you start the failback process to a target virtual machine, the
Backup size will be increasing during the data transfer phase, because
the virtual machine in the cloud will continue to run and generate new
data.
To calculate the estimated downtime period during the failback process to
a target virtual machine, take 10% of the Backup size value (as we
recommend that you start the switchover phase after 90% of the data is
transferred to your local site), and divide it by the value of your Internet
speed.

Note
The value of the Internet speed will decrease when you perform several
failback processes at the same time.

Target Type of workload on your local site to which you will recover the cloud
server: Virtual machine or Physical machine.

Target Failback location: a VMware ESXi host or a Microsoft Hyper-V host.

machine You can select from all the hosts that have an agent which is registered
location with the Cyber Protection service.

Agent Agent which will perform the failback operation.

You can use one agent to perform one failback operation at the same
time.
You can select an agent that is online and is not currently used for
another failback process, has a version which supports the failback
functionality, and has rights to access the backup.
Note that you can install several agents on VMware ESXi hosts, and start a
separate failback process using each of them. These failback processes
can be performed at the same time.

Target Virtual machine settings:

machine l Virtual processors. Select the number of virtual processors.
settings l Memory. Select how much memory the virtual machine will have.
l Units. Select the units for the memory.
l [Optional] Network adapters. To add a network adapter, click Add,
and select a network in the Network field.
When you are ready with the changes, click Done.

Path (For Microsoft Hyper-V hosts) Folder on the host where your machine will

756 © Acronis International GmbH, 2003-2024

 Parameter Description

be stored.
Ensure that there is enough free memory space on the host for the
machine.

Datastore (For VMware ESXi hosts) Datastore on the host where your machine will
be stored.
Ensure that there is enough free memory space on the host for the
machine.

Provisioning Method of allocation of the virtual disk.

mode For Microsoft Hyper-V hosts:
l Dynamically expanding (default value).
l Fixed size.
For Microsoft Hyper-V hosts:
l Thin (default value).
l Thick.

Target Name of the target machine. By default, the target machine name is the
machine same as the recovery server name.
name The target machine name must be unique on the selected Target
machine location.

5. Click Start data transfer, and then in the confirmation window, click Start.

Note
If there is no backup of the virtual machine in the cloud, the system will perform a backup
automatically before the data transfer phase.

The Data transfer phase starts. The console displays the following information:

Field Description

Progress This parameter shows how much data is already transferred to the local
site, and the total amount of data that must be transferred.
The total amount of data includes the data from the last backup before the
data transfer phase was started, and the backups of the newly generated
data (backup increments), as the virtual machine continues to run during
the data transfer phase. For this reason, both values of the Progress
parameter increase with time.

Downtime This parameter shows how much time the virtual machine in the cloud will
estimation be unavailable if you start the switchover phase now. The value is
calculated based on the values of the Progress parameter, and decreases
with time.

6. Click Switchover and then, in the confirmation window, click Switchover again.
The switchover phase starts. The console displays the following information:

757 © Acronis International GmbH, 2003-2024

 Field Description

Progress This parameter shows the progress of restoring the machine on the local
site.

Estimated This parameter shows the approximate time when the switchover phase will
time to be completed and you will be able to start the machine on the local site.
finish

Note
If no backup plan is applied to the virtual machine in the cloud, a backup will be performed
automatically during the switchover phase, which will cause a longer downtime.

7. After the Switchover phase completes and the virtual machine at your local site is started
automatically, validate that it is working as expected.
8. Click Confirm failback, and then in the confirmation window, click Confirm to finalize the
process.
The virtual machine in the cloud is deleted, and the recovery server returns to the Standby state.

Note
Applying a protection plan on the recovered server is not part of the failback process. After the
failback process completes, apply a protection plan on the recovered server to ensure that it is
protected again. You may apply the same protection plan that was applied on the original
server, or a new protection plan that has the Disaster Recovery module enabled.

Failback to a target physical machine

Note
The availability of this feature depends on the service quotas that are enabled for your account.

The automatic failback process to a target physical machine consists of the following phases:

1. Planning. During this phase, you restore the IT infrastructure at your local site (such as the hosts
and the network configurations), configure the failback parameters, and plan when to start the
data transfer.
2. Data transfer. During this phase, the data is transferred from the cloud site to the local site
while the virtual machine in the cloud continues to run. You can start the next phase - switchover
- at any time during the data transfer phase, but you should consider the following relations.
The longer you remain in the data transfer phase,
l the longer the virtual machine in the cloud continues to run.
l the more data will be transferred to your local site.
l the higher the cost you will pay (you spend more compute points).
l the shorter the downtime period that you will experience during the switchover phase.

758 © Acronis International GmbH, 2003-2024

 If you want to minimize the downtime, start the switchover phase after more than 90% of the
data is transferred to the local site.
If you can afford to experience a longer downtime period, and do not want to spend more
compute points for running the virtual machine in the cloud, you can start the switchover phase
earlier.

Note
The data transfer process uses a flashback technology. This technology compares the data that
is available on the target machine to the data of the virtual machine in the cloud. If part of the
data is already available on the target machine, it will not be transferred again. This technology
makes the data transfer phase faster.
For this reason, we recommend that you restore the server to the original machine on your local
site.

3. Switchover. During this phase, the virtual machine in the cloud is turned off, and the remaining
data - including the last backup increment - is transferred to the local site. If no backup plan is
applied on the recovery server, a backup will be performed automatically during the switchover
phase, which will slow down the process.
4. Validation. During this phase, the physical machine on the local site is ready, and you can
reboot it using a Linux-based bootable media. You can verify if the virtual machine is working
correctly, and:
l If everything is working as expected, confirm the failback. After the failback confirmation, the
virtual machine in the cloud is deleted, and the recovery server returns to the Standby state.
This is the end of the failback process.
l If something is wrong, you can cancel the failover and return to the planning phase.

Note
After the bootable media has been rebooted, you will not be able to use it again. If, at the
validation phase, you discover something wrong, you must register a new bootable media and
start the failback process again.
However, as flashback technology will be used, the data that is already on the local site will not
be transferred again, and the failback process will be much faster.

Performing failback to a physical machine

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can perform automatic failback to a target physical machine on your local site.

759 © Acronis International GmbH, 2003-2024

Note
The data transfer process uses a flashback technology. This technology compares the data that is
available on the target machine to the data of the virtual machine in the cloud. If part of the data is
already available on the target machine, it will not be transferred again. This technology makes the
data transfer phase faster.

For this reason, we recommend that you restore the server to the original machine on your local
site.

Prerequisites
l The agent that you will use to perform failback is online and is not currently used for another
failback operation.
l Your Internet connection is stable.
l A registered bootable media is available. For more information, see "Creating bootable media to
recover operating systems" in the Cyber Protection User Guide.
l The target physical machine is the original machine on your local site, or has the same firmware
as the original machine.
l There is at least one full backup of the virtual machine in the cloud.

To perform a failback to a physical machine

1. In the Cyber Protect console, go to Disaster recovery > Servers.

2. Select the recovery server that is in the Failover state.
3. Click the Failback tab.
4. In the Target field, select Physical machine.
5. In the Target bootable media field, click Specify, select the bootable media, and then click
Done.

Note
We recommend that you use ready-made bootable media as it is already configured. For more
information, see "Creating bootable media to recover operating systems" in the Cyber
Protection User Guide.

6. [Optional] To change the default disk mapping, in the Disk mapping field, click Specify, map the
disks of the backup to the disks of the target machine, and then click Done.
7. Click Start data transfer and then, in the confirmation window, click Start.

Note
If there is no backup of the virtual machine in the cloud, the system will perform a backup
automatically before the data transfer phase.

The data transfer phase starts. The console displays the following information:

760 © Acronis International GmbH, 2003-2024

 Field Description

Progress This parameter shows how much data is already transferred to the local
site, and the total amount of data that must be transferred.
The total amount of data includes the data from the last backup before the
data transfer phase was started, and the backups of the newly generated
data (backup increments), as the virtual machine continues to run during
the data transfer phase. For this reason, the Progress values increase with
time.
As the system uses a flashback technology during the data transfer and
does not transfer the data that is already available on the target machine,
the progress might be faster than what is initially calculated by the console.

Downtime This parameter shows how much time the virtual machine in the cloud will
estimation be unavailable if you start the switchover phase now. The value is
calculated based on the values of the Progress parameter, and decreases
with time.
As the system uses a flashback technology during the data transfer and
does not transfer the data that is already available on the target machine,
the downtime might be much shorter than the value that is initially
displayed in the console.

8. Click Switchover and then, in the confirmation window, click Switchover again.
The switchover phase starts. The console displays the following information:

Field Description

Progress This parameter shows the progress of restoring the machine on the local
site.

Estimated This parameter shows the approximate time when the switchover phase will
time to be completed and you will be able to start the machine on the local site.
finish

Note
If no backup plan is applied to the virtual machine in the cloud, a backup will be performed
automatically during the switchover phase, which will cause a longer downtime.

9. After the Switchover phase completes, reboot the bootable media, and then verify that the
physical machine on your local site is working as expected.
For more information, see "Recovering disks using bootable media" in the Cyber Protection User
Guide.
10. Click Confirm failback and then, in the confirmation window, click Confirm to finalize the
process.
The virtual machine in the cloud is deleted, and the recovery server returns to the Standby state.

761 © Acronis International GmbH, 2003-2024

 Note
Applying a protection plan on the recovered server is not part of the failback process. After the
failback process completes, apply a protection plan on the recovered server to ensure that it is
protected again. You may apply the same protection plan that was applied on the original
server, or a new protection plan that has the Disaster Recovery module enabled.

Manual failback

Note
We recommend that you use the failback process in a manual mode only when you are advised to
do so by the Support team.

You can also start a failback process in a manual mode. In this case, the data transfer from the
backup in the cloud to the local site will not be done automatically. It must be done manually after
the virtual machine in the cloud is powered off. This makes the failback process in a manual mode
much slower, and you should expect a longer downtime period.

The failback process in a manual mode consists of the following phases:

1. Planning. During this phase, you restore the IT infrastructure at your local site (such as the hosts
and the network configurations), configure the failback parameters, and plan when to start the
data transfer.
2. Switchover. During this phase, the virtual machine in the cloud is turned off, and the newly
generated data is backed up. If no backup plan is applied on the recovery server, a backup will be
performed automatically during the switchover phase, which will slow down the process. When
the backup is complete, you recover the machine to the local site manually. You can either
recover the disk by using bootable media, or recover the entire machine from the cloud backup
storage.
3. Validation. During this phase, you verify that the physical or virtual machine at the local site is
working correctly, and confirm the failback. After the confirmation, the virtual machine on the
cloud site is deleted, and the recovery server returns to the Standby state.

Performing manual failback

Note
The availability of this feature depends on the service quotas that are enabled for your account.

You can perform a manual failback to a target physical or virtual machine on your local site.

To perform a manual failback

1. In the Cyber Protect console, go to Disaster recovery > Servers.

2. Select the recovery server that is in the Failover state.
3. Click the Failback tab.

762 © Acronis International GmbH, 2003-2024

 4. In the Target field, select Physical machine.
5. Click the gear icon, and then enable the Use manual mode switch.
6. [Optional] Calculate the estimated downtime period during the failback process, by dividing the
Backup size value by the value of your Internet speed.

Note
The value of the Internet speed will decrease when you perform several failback processes at
the same time.

7. Click Switchover, and then in the confirmation window, click Switchover again.
The virtual machine on the cloud site is turned off.

Note
If no backup plan is applied to the virtual machine in the cloud, a backup will be performed
automatically during the switchover phase, which will cause a longer downtime.

8. Recover the server from the cloud backup to the physical or virtual machine on your local site.
For more information, see "Recovering a machine" in the Cyber Protection User Guide.
9. Ensure that the recovery is completed and the recovered machine works properly, and click
Machine is restored.
10. If everything is working as expected, click Confirm failback, and then in the confirmation
window, click Confirm again.
The recovery server and recovery points become ready for the next failover. To create new
recovery points, apply a protection plan to the new local server.

Note
Applying a protection plan on the recovered server is not part of the failback process. After the
failback process completes, apply a protection plan on the recovered server to ensure that it is
protected again. You may apply the same protection plan that was applied on the original
server, or a new protection plan that has the Disaster Recovery module enabled.

Working with encrypted backups

You can create recovery servers from the encrypted backups. For your convenience, you can set up
an automatic password application to an encrypted backup during the failover to a recovery server.

When creating a recovery server, you can specify the password to be used for automatic disaster
recovery operations. It will be saved to the Credentials store, a secure storage of credentials that
can be found in Settings > Credentials section.

One credential can be linked to several backups.

To manage the saved passwords in the Credentials store

763 © Acronis International GmbH, 2003-2024

1. Go to Settings > Credentials.
2. To manage a specific credential, click the icon in the last column. You can view the items linked to
this credential.
l To unlink the backup from the selected credential, click the recycle bin icon near the backup.
As a result, you will have to specify the password manually during the failover to the recovery
server.
l To edit the credential, click Edit, and then specify the name or password.
l To delete the credential, click Delete. Note that you will have to specify the password
manually during the failover to the recovery server.

Operations with Microsoft Azure virtual machines

Note
Some features might require additional licensing, depending on the applied licensing model.

You can perform failover of Microsoft Azure virtual machines to Acronis Cyber Protect Cloud. For
more information, see "Performing a failover" (p. 750).

After that, you can perform failback from Acronis Cyber Protect Cloud back to Azure virtual
machines. The failback process is same as the failback process to a physical machine. For more
information, see "Prerequisites" (p. 760).

Note
To register a new Azure virtual machine for failing back, you can use the Acronis Backup VM
extension that is available in Azure.

You can configure a Multisite IPsec VPN connectivity between Acronis Cyber Protect Cloud and the
Azure VPN gateway. For more information, see "Configuring Multi-site IPsec VPN" (p. 720).

Setting up primary servers

This section describes how to create and manage your primary servers.

Creating a primary server

Prerequisites
l One of the connectivity types to the cloud site must be set.

To create a primary server

1. Go to Disaster Recovery > Servers > Primary servers tab.

2. Click Create.
3. Select a template for the new virtual machine.

764 © Acronis International GmbH, 2003-2024

4. Select the flavor of the configuration (number of virtual cores and the size of RAM). The following
table shows the maximum total amount of disk space (GB) for each flavor.

Type vCPU RAM (GB) Maximum total amount of disk space (GB)

F1 1 2 500

F2 1 4 1000

F3 2 8 2000

F4 4 16 4000

F5 8 32 8000

F6 16 64 16000

F7 16 128 32000

F8 16 256 64000

Note
You can see the compute points for every option. The number of compute points reflects the
cost of running the primary server per hour. For more information, see "Compute points" (p.
702).

5. [Optional] Change the virtual disk size. If you need more than one hard disk, click Add disk, and
then specify the new disk size. Currently, you can add no more than 10 disks for a primary
server.
6. Specify the cloud network in which the primary server will be included.
7. Select the DHCP option.

DHCP option Description

Provided by Default setting. The IP address of the server will be provided by an

cloud site automatically configured DHCP server in the cloud.

Custom The IP address of the server will be provided by your own DHCP server in
the cloud.

8. [Optional] Specify the MAC address.

The MAC address is a unique identifier that is assigned to the network adapter of the server. If
you use custom DHCP, you can configure it to always assign a specific IP adresses to a specific
MAC address. This ensures that the primary server always gets the same IP address. You can run
applications that have licenses that are registered with the MAC address.
9. Specify the IP address that the server will have in the production network. By default, the first
free IP address from your production network is set.

765 © Acronis International GmbH, 2003-2024

 Note
If you use a DHCP server, add this IP address to the server exclusion list in order to avoid IP
address conflicts.
If you use a custom DHCP server, you must specify the same IP address in IP address in
production network as the one configured in the DHCP server. Otherwise, test failover will not
work properly, and the server will not be reachable via a public IP address.

10. [Optional] Select the Internet access check box.

This will enable the primary server to access the Internet. By default, TCP port 25 is open for
outbound connections to public IP addresses.
11. [Optional] Select the Use public IP address check box.
Having a public IP address makes the primary server available from the Internet. If you leave the
check box cleared, the server will be available only in your production network.
The public IP address will be shown after you complete the configuration. By default, TCP port
443 is open for inbound connections to public IP addresses.

Note
If you clear the Use Public IP address check box or delete the recovery server, its public IP
address will not be reserved.

12. [Optional] Select Set RPO threshold.

RPO threshold defines the maximum allowable time interval between the last recovery point and
the current time. The value can be set within 15 – 60 minutes, 1 – 24 hours, 1 – 14 days.
13. Define the primary server name.
14. [Optional] Specify a description for the primary server.
15. [Optional] Click the Cloud firewall rules tab to edit the default firewall rules. For more
information, see "Setting firewall rules for cloud servers" (p. 769).
16. Click Create.

The primary server becomes available in the production network. You can manage the server by
using its console, RDP, SSH, or TeamViewer.

766 © Acronis International GmbH, 2003-2024

Operations with a primary server
The primary server appears in the Disaster Recovery > Servers > Primary servers tab in the Cyber
Protect console.

To start or stop the server, click Power on or Power off on the primary server panel.

To edit the primary server settings, stop the server, and then click Edit.

To apply a protection plan to the primary server, select it and on the Plan tab click Create. You will
see a predefined protection plan where you can change only the schedule and retention rules. For
more information, refer to "Backing up the cloud servers".

Managing the cloud servers

To manage the cloud servers, go to Disaster Recovery > Servers. There are two tabs there:
Recovery servers and Primary servers. To show all optional columns in the table, click the gear
icon.

You can find the following information about each cloud server by selecting it.

Column Description
name

Name A cloud server name defined by you

Status The status reflecting the most severe issue with a cloud server (based on the active
alerts)

State A cloud server state

VM state The power state of a virtual machine associated with a cloud server

Active The location where a cloud server is hosted. For example, Cloud.

767 © Acronis International GmbH, 2003-2024

 location

RPO The maximum time interval allowed between the last suitable recovery point for failover
threshold and the current time. The value can be set within 15-60 minutes, 1-24 hours, 1-14 days.

RPO The RPO compliance is the ratio between the actual RPO and RPO threshold. The RPO
compliance compliance is shown if the RPO threshold is defined.

It is calculated as follows:

RPO compliance = Actual RPO / RPO threshold

where

Actual RPO = current time – last recovery point time

RPO compliance statuses

Depending on the value of the ratio between the actual RPO and RPO threshold, the
following statuses are used:

l Compliant. The RPO compliance < 1x. A server meets the RPO threshold.
l Exceeded. The RPO compliance <= 2x. A server violates the RPO threshold.
l Severely exceeded. The RPO compliance <= 4x. A server violates the RPO threshold
more than 2x times.
l Critically exceeded. The RPO compliance > 4x. A server violates the RPO threshold
more than 4x times.
l Pending (no backups). The server is protected with the protection plan but the
backup is being created and not completed yet.

Actual RPO The time passed since the last recovery point creation

Last recovery The date and time when the last recovery point was created
point

Firewall rules for cloud servers

You can configure firewall rules to control the inbound and outbound traffic of the primary and
recovery servers on your cloud site.

You can configure inbound rules after you provision a public IP address for the cloud server. By
default, TCP port 443 is allowed, and all other inbound connections are denied. You can change the
default firewall rules, and add or remove Inbound exceptions. If a public IP is not provisioned, you
can only view the inbound rules, but cannot configure them.

You can configure outbound rules after when you provision Internet access for the cloud server. By
default, TCP port 25 is denied, and all other outbound connections are allowed. You can change the
default firewall rules, and add or remove outbound exceptions. If Internet access is not provisioned,
you can only view the outbound rules, but cannot configure them.

768 © Acronis International GmbH, 2003-2024

Note
For security reasons, there are predefined firewall rules that you cannot change.

For inbound and outbound connections:

l Permit ping: ICMP echo-request (type 8, code 0) and ICMP echo-reply (type 0, code 0)
l Permit ICMP need-to-frag (type 3, code 4)
l Permit TTL exceeded (type 11, code 0)

For inbound connections only:

l Non-configurable part: Deny all

For outbound connections only:

l Non-configurable part: Reject all

Setting firewall rules for cloud servers

You can edit the default firewall rules for the primary and recovery servers in the cloud.

To edit the firewall rules of a server on your cloud site

1. In the Cyber Protect console, go to Disaster Recovery> Servers.

2. If you want to edit the firewall rules of a recovery server, click the Recovery servers tab.
Alternatively, if you want to edit the firewall rules of a primary server, click the Primary servers
tab.
3. Click the server, and then click Edit.
4. Click the Cloud firewall rules tab.
5. If you want to change the default action for the inbound connections:
a. In the Inbound drop-down field, select the default action.

Action Description

Deny all Denies any inbound traffic.

You can add exceptions and allow traffic from specific IP addresses,
protocols, and ports.

Allow Allows all inbound TCP and UDP traffic.

all You can add exceptions and deny traffic from specific IP addresses,
protocols, and ports.

Note
Changing the default action invalidates and removes the configuration of existing inbound
rules.

b. [Optional] If you want to save the existing exceptions, in the confirmation window, select

769 © Acronis International GmbH, 2003-2024

 Save filled-in exceptions.
c. Click Confirm.
6. If you want to add an exception:
a. Click Add exception.
b. Specify the firewall parameters.

Firewall Description
parameter

Protocol Select the protocol for the connection. The following options are
supported:
l TCP
l UDP
l TCP+UDP

Server port Select the ports to which the rule applies. You can specify the
following:
l a specific port number (for example, 2298)
l a range of port numbers (for example, 6000-6700)
l any port number. Use * if you want the rule to apply to any port
number.

Client IP Select the IP addresses to which the rule applies. You can specify the
address following:
l a specific IP address (for example, 192.168.0.0)
l a range of IP addresses using the CIDR notation (for example,
192.168.0.0/24)
l any IP address. Use * if you want the rule to apply to any
IP address.

7. If you want to remove an existing inbound exception, click the bin icon next to it.
8. If you want to change the default action for the outbound connections:
a. In the Outbound drop-down field, select the default action.

Action Description

Deny all Denies any outbound traffic.

You can add exceptions and allow traffic to specific IP addresses, protocols,
and ports.

Allow Allows all outbound traffic.

all You can add exceptions and deny traffic from specific IP addresses,
protocols, and ports.

Note
Changing the default action invalidates and removes the configuration of existing outbound
rules.

770 © Acronis International GmbH, 2003-2024

 b. [Optional] If you want to save the existing exceptions, in the confirmation window, select
Save filled-in exceptions.
c. Click Confirm.
9. If you want to add an exception:
a. Click Add exception.
b. Specify the firewall parameters.

Firewall Description
parameter

Protocol Select the protocol for the connection. The following options are
supported:
l TCP
l UDP
l TCP+UDP

Server port Select the ports to which the rule applies. You can specify the
following:
l a specific port number (for example, 2298)
l a range of port numbers (for example, 6000-6700)
l any port number. Use * if you want the rule to apply to any port
number.

Client IP Select the IP addresses to which the rule applies. You can specify the
address following:
l a specific IP address (for example, 192.168.0.0)
l a range of IP addresses using the CIDR notation (for example,
192.168.0.0/24)
l any IP address. Use * if you want the rule to apply to any
IP address.

10. If you want to remove an existing outbound exception, click the bin icon next to it.
11. Click Save.

Checking the cloud firewall activities

After an update of the configuration of the firewall rules of a cloud server, a log of the update
activity becomes available in the Cyber Protect console. You can view the log and check the
following information:

l user name of the user who updated the configuration

l date and time of the update
l firewall settings for inbound and outbound connections

771 © Acronis International GmbH, 2003-2024

l the default actions for inbound and outbound connections
l the protocols, ports and IP addresses of the exceptions for inbound and outbound connections

To view the details about a cloud firewall rules configuration change

1. In the Cyber Protect console, click Monitoring > Activities.

2. Click the corresponding activity, and click All Properties.
The description of the activity should be Updating cloud server configuration.
3. In the context field, inspect the information that you are interested in.

Backing up the cloud servers

Primary and recovery servers are backed up agentless on the cloud site. These backups have the
following restrictions.

l The only possible backup location is the cloud storage. Primary servers are backed up to the
Primary servers backup storage.

Note
Microsoft Azure backup locations are not supported.

l A backup plan cannot be applied to multiple servers. Each server must have its own backup plan,
even if all of the backup plans have the same settings.
l Only one backup plan can be applied to a server.
l Application-aware backup is not supported.
l Encryption is not available.
l Backup options are not available.

When you delete a primary server, its backups are also deleted.

A recovery server is backed up only in the failover state. Its backups continue the backup sequence
of the original server. When a failback is performed, the original server can continue this backup
sequence. So, the backups of the recovery server can only be deleted manually or as a result of
applying the retention rules. When a recovery server is deleted, its backups are always kept.

Note
The backup plans for cloud servers are performed according to UTC time.

Orchestration (runbooks)
Note
Some features might require additional licensing, depending on the applied licensing model.

A runbook is a set of instructions describing how to spin up the production environment in the
cloud. You can create runbooks in the Cyber Protect console. To access the Runbooks screen, select
Disaster recovery > Runbooks.

772 © Acronis International GmbH, 2003-2024

Why use runbooks?
With runbooks, you can:

l Automate a failover of one or multiple servers

l Automatically check the failover result by pinging the server IP address and checking the
connection to the port you specify
l Set the sequence of operations for servers running distributed applications
l Include manual operations in the workflow
l Verify the integrity of your disaster recovery solution, by executing runbooks in the test mode.

Creating a runbook
A runbook consists of steps that are executed consecutively. A step consists of actions that start
simultaneously.

You can follow the instruction below or watch the video tutorial.

To create a runbook

1. In the Cyber Protection console, go to Disaster recovery > Runbooks.

2. Click Create runbook.
3. Click Add step.
4. Click Add action, and then select the action that you want to add to the step.

Action Description

Failover server Performs a failover of a cloud server. To define this action, you must select a
cloud server and configure the runbook parameters that are available for this
action. For more information about these parameters, see "Runbook parameters"
(p. 775).

Note
If the backup of the server that you select is encrypted by using encryption as a
machine property, the Failover server action will be paused and will be changed
automatically to Interaction required. To proceed with the execution of the
runbook, you will have to provide the password for the encrypted backup.

Failback server Performs a failback of a cloud server. To define this action, you must select a
cloud server and configure the runbook parameters that are available for this
action. For more information about these settings, see "Runbook parameters" (p.
775).

773 © Acronis International GmbH, 2003-2024

 Action Description

Note
Runbook operations support the failback in manual mode only. This means that
if you start the failback process by executing a runbook that includes a Failback
server step, the procedure will require a manual interaction: you must manually
recover the machine, and confirm or cancel the failback process from the
Disaster Recovery > Servers tab.

Start server Starts a cloud server. To define this action, you must select a cloud server and
configure the runbook parameters that are available for this action. For more
information about these settings, see "Runbook parameters" (p. 775).

Note
The Start server action is not applicable for test failover operations in runbooks.
If you try executing such an action, it will fail with the following error message:
Failed: The action is not applicable to the current server state.

Stop server Stops a cloud server. To define this action, you must select a cloud server and
configure the runbook parameters that are available for this action. For more
information about these settings, see "Runbook parameters" (p. 775).

Note
The Stop server action is not applicable for test failover operations in runbooks.
If you try executing such an action, it will fail with the following error message:
Failed: The action is not applicable to the current server state.

Manual A manual operation requires an interaction from a user. To define this action, you
operation must enter a description.
When a runbook sequence reaches a manual operation, the runbook will be
paused and will not proceed until a user performs the required manual
operation, such as clicking the confirmation button.

Execute runbook Executes another runbook. To define this action, you must choose a runbook.
A runbook can include only one execution of a given runbook. For example, if you
added the action "execute Runbook A", you can add the action "execute Runbook
B", but cannot add another action "execute Runbook A".

5. Define the runbook parameters for the action. For more information about these parameters,
see "Runbook parameters" (p. 775).
6. [Optional] To add a description of the step:
a. Click the ellipsis icon, and then click Description.
b. Enter a description of the step.
c. Click Done.
7. Repeat steps 3-6 until you create the desired sequence of steps and actions.
8. [Optional] To change the default name of the runbook:

774 © Acronis International GmbH, 2003-2024

 a. Click the ellipsis icon.
b. Enter the name of the runbook.
c. Enter a description of the runbook.
d. Click Done.
9. Click Save.
10. Click Close.

Runbook parameters
Runbook parameters are specific settings that you must configure to define a runbook action. There
are two categories of runbook parameters - action parameters and completion check parameters.

Action parameters define the runbook behavior depending on the action initial state or result.

Completion check parameters ensure that the server is available and provides the necessary
services. If a completion check fails, the action is considered failed.

The following table describes the configurable runbook parameters for each action.

Runbook Category Available for Description

parameter action

Continue if Action parameter l Failover server This parameter defines the runbook
already done l Start server behavior when the required action is
l Stop server already done (for example, a failover has
l Failback server already been performed or a server is
already running). When enabled, the

775 © Acronis International GmbH, 2003-2024

 Runbook Category Available for Description
parameter action

runbook issues a warning and proceeds.

When disabled, the action fails, and then
the runbook fails too.

By default, this parameter is enabled.

Continue if Action parameter l Failover server This parameter defines the runbook
failed l Start server behavior when the required action fails.
l Stop server When enabled, the runbook issues a
l Failback server warning and proceeds. When disabled, the
action fails, and then the runbook fails too.

By default, this parameter is disabled.

Ping IP address Completion check l Start server The software will ping the production IP
address of the cloud server until the server
replies or the timeout expires, whichever
comes first.

Connect to port Completion check l Failover server The software will try to connect to the cloud
(443 by default) l Start server server by using its production IP address
and the port you specify, until the
connection is established or the timeout
expires, whichever comes first. This way,
you can check if the application that listens
on the specified port is running.

Timeout in Completion check l Failover server The default timeout is 10 minutes.

minutes l Start server

Operations with runbooks

Note
The availability of this feature depends on the service quotas that are enabled for your account.

To access the list of operations, hover on a runbook and click the ellipsis icon. When a runbook is
not running, the following operations are available:

l Execute
l Edit
l Clone
l Delete

776 © Acronis International GmbH, 2003-2024

Executing a runbook
Every time you click Execute, you are prompted for the execution parameters. These parameters
apply to all failover and failback operations included in the runbook. The runbooks specified in the
Execute runbook operations inherit these parameters from the main runbook.

l Failover and failback mode

Choose whether you want to run a test failover (by default) or a real (production) failover. The
failback mode will correspond to the chosen failover mode.
l Failover recovery point
Choose the most recent recovery point (by default) or select a point in time in the past. If the
latter is the case, the recovery points closest before the specified date and time will be selected
for each server.

Stopping a runbook execution

During a runbook execution, you can select Stop in the list of operations. The software will complete
all of the already started actions except for those that require user interaction.

Viewing the execution history

When you select a runbook on the Runbooks tab, the software displays the runbook details and
execution history. Click the line corresponding to a specific execution to view the execution log.

777 © Acronis International GmbH, 2003-2024

Configuring your antivirus and antimalware
protection
Note
On Windows machines, the antimalware protection feature requires the installation of Agent for
Antimalware protection, and the URL filtering feature requires the installation of Agent for URL
filtering. These agents are installed automatically for protected workloads if the Antivirus &
Antimalware protection and/or the URL filtering modules are enabled in their protection plans.

Antimalware protection in Cyber Protection provides you with the following benefits:

l Top protection on all the stages: proactive, active, and reactive.

l Four different antimalware technologies inside to provide the best of the breed multi-layered
protection.
l Management of Microsoft Security Essentials and Microsoft Defender Antivirus.

Note
The availability of this feature depends on the service quotas that are enabled for your account.

Important
EICAR test file is detected only when the Advanced Antimalware option is enabled in the
protection plan. However, not detecting the EICAR file does not affect the antimalware capabilities
of Cyber Protection.

Supported platforms
Active protection, antivirus and antimalware features are supported on the following platforms.

Operating system Version/Distribution

Windows Windows 7 Service Pack 1 and later

Windows Server 2008 R2 Service Pack 1 and later

Note
For Windows 7, you must install the following updates from Microsoft
before installing the protection agent.

l Windows 7 Extended Security Updates (ESU)

l KB4474419
l KB4490628

For more information on the required updates, refer to this knowledge

base article.

Linux Red Hat Linux 7.x, 8.x, 9.x

778 © Acronis International GmbH, 2003-2024

 Operating system Version/Distribution

CloudLinux 6.10, 7.x, 8.x

CentOS 6.5 and later 6.x versions, 7.x, 8.x

Ubuntu 16.04, 18.04, 20.04, 22.04, 22.10

Debian 8.x, 9.x, 10,x, 11.x

Oracle Linux 7.x, 8.x, 9.x

SUSE Enterprise Linux 15.x

openSUSE Leap 15.x

macOS macOS 10.13.x and later

Supported features per platform

Note
Antimalware protection for Linux and macOS is available with the Advanced Antimalware pack.

Feature set Windows Linux macOS

Antivirus and Antimalware protection

Fully-integrated Active Protection functionality Yes No No

Real-time antimalware protection Yes, with the Yes, with the

Advanced Advanced
Yes
Antimalware Antimalware
pack pack

Advanced real-time antimalware protection with

Yes Yes Yes
local signature-based detection

Static analysis for portable executable files Yes No Yes*

On-demand antimalware scanning Yes Yes** Yes

Network folder protection Yes Yes No

Server-side protection Yes No No

Scan of archive files Yes No Yes

Scan of removable drives Yes No Yes

Scan of new and changed files only Yes No Yes

779 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Antivirus and Antimalware protection

File/folder exclusions Yes Yes Yes***

Processes exclusions Yes No Yes

Behavioral analysis engine Yes No Yes

Exploit prevention Yes No No

Quarantine Yes Yes Yes

Quarantine auto clean-up Yes Yes Yes

URL filtering (http/https) Yes No No

Corporate-wide whitelist Yes No Yes

Firewall management**** Yes No No

Microsoft Defender Antivirus

Yes No No
management*****

Microsoft Security Essentials management Yes No No

Registering and managing Antivirus and

Antimalware protection via Windows Security Yes No No
Center

For more information about the supported operating systems and their versions, see "Supported
platforms" (p. 778).

* Static analysis for portable executable files is supported only for scheduled scans on macOS.

** Start conditions are not supported for on-demand scanning on Linux.

*** File/folder exclusions are only supported for the case when you specify files and folders that will
not be scanned by real-time protection or scheduled scans on macOS.

**** Firewall management is supported on Windows 8 and later. Windows Server is not supported.

***** Microsoft Defender Antivirus management is supported on Windows 8.1 and later.

Feature set Windows Linux macOS

Active Protection

Process Injects detection Yes No No

Automatic recovery of affected files from the local

Yes Yes Yes
cache

780 © Acronis International GmbH, 2003-2024

 Feature set Windows Linux macOS

Active Protection

Self-defense for Acronis backup files Yes No No

Self-defense for Acronis software Yes

(Only Active
Yes No Protection and
antimalware
components)

Trusted/blocked process management Yes No Yes

Processes/folders exclusions Yes Yes Yes

Ransomware detection based on a process behavior

Yes Yes Yes
(AI-based)

Cryptomining process detection based on process

Yes No No
behavior

External drives protection (HDD, flash drives, SD

Yes No Yes
cards)

Network folder protection Yes Yes Yes

Server-side protection Yes No No

Zoom, Cisco Webex, Citrix Workspace, and Microsoft

Yes No No
Teams protection

For more information about the supported operating systems and their versions, see "Supported
platforms" (p. 778).

Antivirus and antimalware protection

Note
Some features might require additional licensing, depending on the applied licensing model.

The Antivirus & Antimalware module protects your Windows, Linux, and macOS machines from
all recent malware threats. See the full list of supported antimalware features in "Supported
platforms" (p. 778).

Antivirus & Antimalware protection is supported and registered in Windows Security Center.

781 © Acronis International GmbH, 2003-2024

Antimalware features
l Detection of malware in files in the real-time protection and on-demand modes
l Detection of malicious behavior in processes (for Windows)
l Blocking access to malicious URLs (for Windows)
l Placing dangerous files to the quarantine
l Adding trusted corporate applications to the allowlist

Scanning types
You can configure antivirus and antimalware protection to run constantly in the background or on
demand.

Real-time protection

Note
The availability of this feature depends on the service quotas that are enabled for your account.

Real-time protection checks all files that are being executed or opened on a machine to prevent
malware threats.

To prevent potential compatibility and performance issues, real-time protection cannot work in
parallel with other antivirus solutions that also use real-time protection features. The statuses of
other installed antivirus solutions are determined through Windows Security Center. If the Windows
machine is already protected by another antivirus solution, real-time protection is automatically
turned off.

To enable real-time protection, disable or uninstall the other antivirus solution. Real-time protection
can replace Microsoft Defender real-time protection automatically.

Note
On machines running Windows Server operating systems, Microsoft Defender will not be turned off
automatically when real-time protection is enabled. An administrator must turn off the Microsoft
Defender manually to avoid potential compatibility issues.

You can choose one of the following scan modes:

l Smart on-access detection means that the antimalware program runs in the background and
actively and constantly scans your machine system for viruses and other malicious threats for the
entire duration that your system is powered on. Malware will be detected in both cases when a
file is being executed and during various operations with the file such as opening it for reading or
editing.
l On-execution detection means that only executable files will be scanned at the moment they are
run to ensure they are clean and will not cause any damage to your machine or data. Copying of
an infected file will remain unnoticed.

782 © Acronis International GmbH, 2003-2024

Scheduled scan
Antimalware scanning is performed according to a schedule.

You can choose one of the following scan modes.

l Quick scan—Checks only workload system files.

l Full scan—Checks all files on your workload.
l Custom scan—Checks files/folders that were added by the administrator to the Protection plan.

After antimalware scanning completes, you can see details about the workloads that were affected
by threats in the Monitoring > Overview > Recently affected widget.

Antivirus and antimalware protection settings

This section describes the features that you can configure in the Antivirus & Antimalware
protection module in a protection plan. To learn how to create a protection plan, see "Creating a
protection plan" (p. 206).

The following features can be configured in the Antivirus & Antimalware protection module for a
protection plan:

l "Active Protection" (p. 783)

l "Advanced Antimalware" (p. 784)
l "Network folder protection" (p. 785)
l "Server-side protection" (p. 785)
l "Self-protection" (p. 786)
l "Cryptomining process detection" (p. 787)
l "Quarantine" (p. 788)
l "Behavior-engine" (p. 788)
l "Exploit prevention" (p. 789)
l "Real-time protection" (p. 790)
l "Schedule scan" (p. 791)
l "Protection exclusions" (p. 795)

Note
Not all the operating systems support the Antivirus & Antimalware protection features. For more
information about the supported operating systems and features, see "Supported platforms" (p.
778). Some features require a certain license to be available in your protection plan.

Active Protection
Active Protection protects your system from malicious software known as ransomware that
encrypts files and demands a ransom for the encryption key.

Default setting: Enabled.

783 © Acronis International GmbH, 2003-2024

Note
A protection agent must be installed on the protected machine. For more information about the
supported operating systems and features, see "Supported platforms" (p. 778).

To configure Active Protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Active Protection.
3. In the Action on detection section, select one of the available options:
Default setting: Revert using cache

l Notify only—The software generates an alert about the process suspected of ransomware
activity.
l Stop the process—The software generates an alert and stops the process suspected of
ransomware activity.
l Revert using cache—The software generates an alert, stops the process, and reverts the file
changes by using the service cache.
4. Click Done to apply the selected options to your protection plan.

Advanced Antimalware
This engine uses an enhanced database of virus signatures to improve the efficiency of antimalware
detection in both quick and full scans.

Important
This feature is available only if you have the Advanced Security protection pack enabled. For more
information, see https://www.acronis.com/en-us/products/cloud/cyber-protect/security/

Note
The availability of this feature depends on the service quotas that are enabled for your account.

To configure Advanced Antimalware

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. In the Advanced Antimalware section, use the toggle to enable the local signature-based
engine.

Note
Antivirus and Antimalware protection for macOS and Linux also requires the local signature-based
engine. For Windows, Antivirus and Antimalware protection is available with or without this engine.

784 © Acronis International GmbH, 2003-2024

Network folder protection
The Network folder protection feature defines whether Antivirus & Antimalware protection
protects network folders that are mapped as local drives. The protection applies to folders shared
via SMB or NFS protocols.

To configure Network folder protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Network folder protection.
3. Add the files where you want to backup the network folders:
l For example, If your workload is Windows, in the Windows field, enter the path for the
Windows file where you want to backup the network folders. Default value:
C:\ProgramData\Acronis\Restored Network Files.
l For example, If your workload is macOS, in the macOS field, enter the path for the macOS files
where you want to backup the network folders. Default value: /Library/Application
Support/Acronis/Restored Network Files/.

Note
Enter the path of a local folder. Network folders, including folders on mapped drives, are not
supported as backup destinations for the network folders.

4. Click Done to apply the selected options to your protection plan.

Server-side protection

This feature defines whether Active protection protects network folders that are shared by you from
the external incoming connections from other servers in the network that may potentially bring
threats.

Default setting: Off.

Note
Server-side protection is not supported for Linux.

To set trusted connections

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Server-side protection.
3. Use the Server-side protection toggle to enable it.
4. Select the Trusted tab.
5. In the Trusted connections field, click Add to define connections that will be allowed to modify
data.

785 © Acronis International GmbH, 2003-2024

6. In the ComputerName/Account field, type the name of the computer and the account of the
machine where the protection agent is installed. For example, MyComputer\TestUser.
7. In the Host name field, type the host name of the machine that is allowed to connect to the
machine using the protection agent.
8. Click the check mark to the right to save the connection definition.
9. Click Done.

To set blocked connections

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Server-side protection.
3. Use the Server-side protection toggle to enable it.
4. Select the Blocked tab.
5. In the Blocked connections field, click Add to define connections that will not be allowed to
modify data.
6. In the ComputerName/Account field, type the name of the computer and the account of the
machine where the protection agent is installed. For example, MyComputer\TestUser.
7. In the Host name field, type the host name of the machine that is allowed to connect to the
machine using the protection agent.
8. Select the check box to the right to save the connection definition.
9. Click Done.

Self-protection
Self-protection prevents unauthorized changes to the software's own processes, registry records,
executable and configuration files, and backups located in your local folders.

Administrators can enable Self-protection, without enabling Active Protection.

Default setting: On.

Note
Self-protection is not supported for Linux.

To enable Self-protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Self-protection.
3. Use the Self-protection toggle to enable it.

To enable Password protection

786 © Acronis International GmbH, 2003-2024

1. Once the Self-protection feature is enabled, you can enable the Password protection feature
by using the toggle.
2. Click Generate new password to generate a password to modify or delete local agents.
3. Click Copy, and then paste it in a safe place because this will be requested when you want to
modify the components list locally.

Important
The password will not be available after you close the window. To get this password applied to
devices, the protection plan settings must be saved.

4. Click Close.

Password protection prevents unauthorized users or software from uninstalling Agent for
Windows or modifying its components. These actions are only possible with a password that an
administrator can provide.

A password is never required for the following actions:

l Updating the installation by running the setup program locally

l Updating the installation by using the Cyber Protect console
l Repairing the installation

Default setting: Disabled

For more information about how to enable Password protection, refer to Preventing unauthorized
uninstallation or modification of agents.

Cryptomining process detection

Cryptomining malware degrades the performance of useful applications, increases electricity bills,
and may cause system crashes and even hardware damage due to abuse. The Cryptomining
process detection feature protects your devices against cryptomining malware to prevent
unsanctioned using of computer resources.

Administrators can enable Cryptomining process detection, without enabling Active Protection.
Default setting: Enabled.

Note
Cryptomining process detection is not supported for Linux.

To configure network folder protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Cryptomining process detection.
3. Use the Detect cryptomining processes toggle to enable or disable the feature.
4. Select what to do with processes suspected of cryptomining activities:

787 © Acronis International GmbH, 2003-2024

 Default setting: Stop the process

l Notify only—The software generates an alert.

l Stop the process — The software generates an alert and stops the process.
5. Click Done to apply the selected options to your protection plan.

Quarantine
Quarantine is a folder used to isolate suspicious (probably infected) or potentially dangerous files.

To configure Quarantine

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Quarantine.
3. In the Remove quarantined files after field, you can define the period in days after which the
quarantined files will be removed.
Default setting: 30 days

4. Click Done.

For more information about this feature, refer to Quarantine.

Behavior-engine
The Behavior engine feature protects a system from malware by using behavioral heuristic to
identify malicious processes.

Default setting: Enabled.

Note
Behavior engine is not supported for Linux.

To configure Network folder protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Behavior engine.
3. Use the Behavior engine toggle to enable or disable the feature.
4. In the Action on detection section select the action that the software will perform when a
malware activity is detected:
Default setting: Quarantine

l Notify only—The software generates an alert about the process suspected of malware
activity.
l Stop the process—The software generates an alert and stops the process suspected of
malware activity.

788 © Acronis International GmbH, 2003-2024

 l Quarantine—The software generates an alert, stops the process, and moves the executable
files to the quarantine folder.
5. Click Done to apply the selected options to your protection plan.

Exploit prevention

Important
This feature is available only if you have the Advanced Security protection pack enabled. For more
information, see https://www.acronis.com/en-us/products/cloud/cyber-protect/security/

Note
The availability of this feature depends on the service quotas that are enabled for your account.

Exploit prevention detects and prevents infected processes from spreading and exploiting the
software vulnerabilities on a systems. When an exploit is detected, the software can generate an
alert and stop the process suspected of exploit activities.

Exploit prevention is available only with agent versions 12.5.23130 (21.08, released in August 2020)
or later.

Default setting: Enabled for newly created protection plans, and Disabled for existing protection
plans, created with previous agent versions.

Note
Exploit prevention is not supported for Linux.

You can select what should the program do when an exploit is detected, and which exploit
prevention methods are applied by the program.

To configure Exploit prevention

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Exploit prevention.
3. In the Action on detection section, select one of the available options:
Default setting: Stop the process

l Notify only
The software will generate an alert about the process suspected of exploit activities.
l Stop the process
The software will generate an alert and stop the process suspected of exploit activities.
4. In the Enabled exploit prevention techniques section, select from the available options that
you want to be applied:
Default setting: All methods are enabled

789 © Acronis International GmbH, 2003-2024

 l Memory protection
Detects and prevents suspicious modifications of the execution rights on memory pages.
Malicious processes apply such modifications to page properties, to enable the execution of
shell codes from non-executable memory areas like stack and heaps.
l Return-oriented programming (ROP) protection
Detects and prevents attempts for use of the ROP exploit technique.
l Privilege escalation protection
Detects and prevents attempts for elevation of privileges made by an unauthorized code or
application. Privilege escalation is used by malicious code to gain full access of the attacked
machine, and then perform critical and sensitive tasks. Unauthorized code is not allowed to
access critical system resources or modify system settings.
l Code injection protection
Detects and prevents malicious code injection into remote processes. Code injection is used
to hide malicious intent of an application behind clean or benign processes, to evade
detection by antimalware products.
5. Click Done to apply the selected options to your protection plan.

Note
Processes that are listed as trusted processes in the Exclusions list will not be scanned for exploits.

Allowing processes to modify backups

The Allow specific processes to modify backups setting is only available when the Self-
protection setting is enabled.

It applies to files that have extensions .tibx, .tib, .tia, and are located in local folders.

This setting lets you specify the processes that are allowed to modify the backup files, even though
these files are protected by self-protection. This is useful, for example, if you remove backup files or
move them to a different location by using a script.

If this setting is disabled, the backup files can be modified only by processes signed by the backup
software vendor. This allows the software to apply retention rules and to remove backups when a
user requests this from the web interface. Other processes, no matter suspicious or not, cannot
modify the backups.

If this setting is enabled, you can allow other processes to modify the backups. Specify the full path
to the process executable, starting with the drive letter.

Default setting: Disabled.

Real-time protection

Note
The availability of this feature depends on the service quotas that are enabled for your account.

790 © Acronis International GmbH, 2003-2024

Real-time protection constantly checks your computer system for viruses and other malicious
threats for the entire time that your system is powered on unless paused by the computer user.

Default setting: Enabled.

Important
This feature is available only if you have the Advanced Security protection pack enabled. For more
information, see https://www.acronis.com/en-us/products/cloud/cyber-protect/security/

To configure Real-time protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Real-time protection.
3. In the Action on detection drop-down, select one of the available options:
Default setting: Quarantine

l Notify only
The software generates an alert about the process suspected of ransomware activity.

l Block and notify

The software blocks the process and generates an alert about the process suspected of malware
activities.

l Quarantine
4. The software generates an alert, stops the process, and moves the executable file to the
quarantine folder.
5. In the Scan mode section, select the action that the software will perform when a virus or other
malicious threat is detected:
Default setting: Smart on-access

l Smart on-access—Monitors all system activities and automatically scans files when they are
accessed for reading or writing, or whenever a program is launched.
l On-execution—Automatically scans only executable files when they are launched to ensure
that they are clean and will not cause any damage to your computer or data.
6. Click Done.

Schedule scan
On-demand scanning checks your computer system for viruses according to the specified schedule.
A full scan checks all the files on your machine, while a quick scan checks only the machine system
files.

To configure Schedule scan

Default settings:

791 © Acronis International GmbH, 2003-2024

l Custom scan is disabled.
l Quick and Full scan are scheduled.

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Schedule scan.
3. Use the toggle to enable the type of scan that you want to apply for your machine.

Available types of scan:

l Full — takes much longer to finish in comparison to the quick scan because every file will be
checked.
l Quick — only scans the common areas where malware normally resides on the machine.
l Custom — Checks the files/folders that were selected by the administrator of the Protection
plan.

Note
You can schedule all three scans - Quick, Full, and Custom - in one protection plan.

To configure custom scan

l Use the Custom scan toggle to enable or disable this type of scan.

l In the Action on detection drop-down list, select one of the available options:

Default setting: Quarantine

Quarantine

The software generates an alert and moves the executable file to the quarantine folder.

Notify only

The software generates an alert about the process that is suspected to be malware.

Field Description

Schedule the This setting defines when the task will run.
task run using
The following values are available:
the following
events l Schedule by time – This is the default setting. The task will run
according to the specified time.
l When user logs in to the system – By default, a login of any user will
trigger the task. You can modify this setting so that only a specific user
account can trigger the task.
l When user logs off the system – By default, a logoff of any user will
trigger the task. You can modify this setting so that only a specific user
account can trigger the task.

792 © Acronis International GmbH, 2003-2024

 Field Description

Note
The task will not run at system shutdown. Shutting down and logging
off are different events in the scheduling configuration.

l On the system startup – The task will run when the operating system
starts.
l On the system shutdown – The task will run when the operating
system shuts down.

Schedule type The field appears if in Schedule the task run using the following
events you have selected Schedule by time.

The following values are available:

l Monthly – Select the months and the weeks or days of the month
when the task will run.
l Daily – This is the default setting. Select the days of the week when the
task will run.
l Hourly – Select the days of the week, repetition number, and the time
interval in which the task will run.

Start at The field appears if in Schedule the task run using the following
events you have selected Schedule by time

Select the exact time when the task will run.

Run within a The field appears if, in Schedule the task run using the following
date range events, you have selected Schedule by time.

Set a range in which the configured schedule will be effective.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs in to the system.
login to the
The following values are available:
operating
system will l Any user - Use this option if you want the login of any user to trigger
initiate a task the task.
l The following user - Use this option if you want only the login of a
specific user account to trigger the task.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs off the system.
logout from the
The following values are available:
operating
system will l Any user - Use this option if you want the logout of any user to trigger
initiate a task the task.
l The following user - Use this option if you want only the logout of a
specific user account to trigger the task.

793 © Acronis International GmbH, 2003-2024

 Field Description

Start conditions Defines all conditions that must be met simultaneously for the task to
run.

Start conditions for antimalware scans are similar to the start conditions
for the Backup module that are described in "Start conditions".

You can define the following additional start conditions:

l Distribute task start time within a time window – This option

allows you to set the time frame for the task in order to avoid network
bottlenecks. You can specify the delay in hours or minutes. For
example, if the default start time is 10:00 AM and the delay is 60
minutes, then the task will start between 10:00 AM and 11:00 AM.
l If the machine is turned off, run missed tasks at the machine
startup
l Prevent the sleep or hibernate mode during task running – This
option is effective only for machines running Windows.
l If start conditions are not met, run the task anyway after –
Specify the period after which the task will run, regardless of the other
start conditions.

Note
Start conditions are not supported for Linux.

l Select the Scan only new and changed files check box if you want to scan only newly created
and modified files.

Default setting: Enabled

l Two additional options displayed for Custom scan for Full scan only:

1. Scan archive files

Default setting: Enabled.

Max recursion depth

Default setting: 16

How many levels of embedded archives can be scanned. For example, MIME document > ZIP
archive > Office archive > document content.

Max size

Default setting: 100

Maximum size of an archive file to be scanned.

2. Scan removable drives

Default setting: Disabled

794 © Acronis International GmbH, 2003-2024

l Mapped (remote) network drives
l USB storage devices (such as pens and external hard drives)
l CDs/DVDs

Note
Scan removable drives is not supported for Linux.

Protection exclusions
Protection exclusions enable you to eliminate false positives when a trusted program is considered
ransomware or malware. You can define trusted and blocked items by adding them to the
protection exclusions list.

In the trusted items list, you can add files, processes and folders to consider them as safe in the
system, and to prevent any future detections for these.

In the blocked items list, you can add processes and hashes. This option guarantees that those
processes will be blocked, and your workload will be safe.

Protection Blocked Trusted

exclusion
item

Hash When a hash is added to the blocked When a hash is added to the trusted
list, the system will stop the process, list, the system will know what
based on the provided hash. processes have to be ignored by
monitoring, based on the provided
For example, when you add this MD5
hash.
hash,
938c2cc0dcc05f2b68c4287040cfcf71, For example, when you add this MD5
the process associated with this hash hash,
will be blocked. 938c2cc0dcc05f2b68c4287040cfcf71,
the process associated with this hash
will be trusted and excluded from
monitoring.

Process When a process is added to the When a process is added to the trusted
blocked list, the system will know that list, the system will know that those
those processes must to be monitored, processes have to be excluded from
and the processes will always be monitoring.
blocked.
Note
For example, if you add this path
Processes signed by Microsoft are
C:\Users\user1\application\nppInstalle
always trusted.
r.exe to the blocked list, this specific
process will be blocked, and when you For example, if you add this path
will try to open it, it will not be allowed C:\Users\user1\application\nppInstaller
to start. .exe, this specific process will be
excluded from monitoring, and

795 © Acronis International GmbH, 2003-2024

 Protection Blocked Trusted
exclusion
item

antivirus will not interfere with this

process.

File/folder When a file or a folder is added to the

trusted list, the system will know that
those files or folders should always be
considered safe, and there is no need
for those to be scanned/monitored.

To specify the items that will always be trusted

1. Open the protection plan.

2. Expand the Antivirus and Antimalware protection module.
3. Select the Exclusions option.
The Protection exclusions window opens.
4. In the Trusted items section, click Add to select from the available options:
l To trust files, folders, or processes, select the File/folder/process option. The Add
file/folder/process window opens.
o In the File/process/folder field, enter the path for each process, folder, or file on a new
line. In the Description section, enter a short description so that you can recognize your
change in the list of trusted items.
o Select the Add as file/folder checkbox to trust the file/folder.
Examples of folder description: D:\folder\, /home/Folder/folder2, F:\
o Select the Add as process checkbox to trust a process. The selected processes will be
excluded from monitoring.

Note
Specify the full path to the process executable, starting with the drive letter. For example,
C:\Windows\Temp\er76s7sdkh.exe.

Note
Local network paths are supported. e.g: \\localhost\folderpath\file.exe

l Select the Hash option to add MD5 hashes to the list of trusted items. The Add hash window
opens.
o Here you can insert MD5 hashes on separate lines to be included as trusted in the
Protection exclusions list. Based on these hashes, Cyber Protection will exclude the
processes described by the MD5 hashes from being monitored.

Default setting: No exclusions are defined by default.

To specify the items that will always be blocked

796 © Acronis International GmbH, 2003-2024

1. Open the protection plan.
2. Expand the Antivirus and Antimalware protection module.
3. Select the Protection exclusions option. The Protection exclusions window opens.
In the Blocked items section, click Add to select from the available options:
l To block processes, select the Process option. The Add process window opens.
o In the Process field, enter the path for each process on a new line. In the Description field,
enter a short description so that you can recognize your change in the list of blocked items.

Note
These processes will not be able to start as long as Active Protection is enabled on the
machine.

l To block hashes, select the Hash option. The Add hash window is displayed.
o In the Hash field, enter the hash for each process on a new line. In the Description field,
enter a short description so that you can recognize your change in the list of blocked items.

Default setting: No exclusions are defined by default.

Wildcards
For specifying folders, you can use the wildcard characters * and ?. The asterisk (*) substitutes for
zero or more characters. The question mark (?) substitutes for exactly one character. Environment
variables, such as %AppData%, cannot be used.

You can use a wildcard (*) to add items to the exclusion lists.

l Wildcards can be used in the middle or the end of a description.

Examples of accepted wildcards in descriptions:

C:\*.pdf

D:\folders\file.*

C:\Users\*\AppData\Roaming

l Wildcards cannot be used at the beginning of a description.

Examples of unaccepted wildcards in descriptions:

*.docx

*:\folder\

Variables
You can also use variables to add items to the Protection exclusions list, with the following
limitations:

l For Windows, only SYSTEM variables are supported. User specific variables, for example,
%USERNAME%, %APPDATA% are not supported. Variables with {username} are not supported.

797 © Acronis International GmbH, 2003-2024

 For more information, see https://ss64.com/nt/syntax-variables.html.
l For macOS, environment variables are not supported.
l For Linux, environment variables are not supported.

Examples of supported formats:

l %WINDIR%\Media
l %public%
l %CommonProgramFiles%\Acronis\

Description
You can use the Description field to make notes on the exclusions that you added in the protection
exclusions list. Some suggestions on the notes you may make:

l Reasons and purposes for the exclusion.

l Actual file name of a hash exclusion.
l Time stamps.

If there are multiple items added in a single entry, there can only be 1 comment captured for the
multiple items.

Active Protection in the Cyber Backup Standard edition

In Cyber Backup Standard edition, Active Protection is a separate module in the protection plan.
Thus, it can be configured separately and applied to different devices or group of devices.

In all other editions of the Cyber Protection service, Active Protection is part of the Antivirus &
Antimalware module of the protection plan.

Default setting: Enabled.

Note
A protection agent must be installed on the protected machine. For more information about the
supported operating systems and features, see "Supported platforms" (p. 778).

How it works
Active Protection monitors processes running on the protected machine. When a third-party
process tries to encrypt files or mine cryptocurrency, Active Protection generates an alert and
performs additional actions, as specified in the protection plan.

In addition, Active Protection prevents unauthorized changes to the backup software's own
processes, registry records, executable and configuration files, and backups located in local folders.

To identify malicious processes, Active Protection uses behavioral heuristics. Active Protection
compares the chain of actions performed by a process with the chains of events recorded in the
database of malicious behavior patterns. This approach enables Active Protection to detect new
malware by its typical behavior.

798 © Acronis International GmbH, 2003-2024

Active Protection settings in Cyber Backup Standard
In the Cyber Backup Standard edition, you can configure the following Active Protection features:

l Action on detection
l Self-protection
l Network folder protection
l Server-side protection
l Cryptomining process detection
l Exclusions

Note
Active Protection for Linux supports the following settings: Action on detection, Network folder
protection, and Exclusions. Network folder protection is always on and not configurable.

Action on detection
In the Action on detection section, select one of the available options:

l Notify only
The software will generate an alert about the process suspected of ransomware activity.
l Stop the process
The software will generate an alert and stop the process suspected of ransomware activity.
l Revert using cache
The software will generate an alert, stop the process, and revert the file changes by using the
service cache.

Default setting: Revert using cache.

Self-protection prevents unauthorized changes to the software's own processes, registry records,
executable and configuration files, and backups located in your local folders.

Administrators can enable Self-protection, without enabling Active Protection.

Default setting: On.

Note
Self-protection is not supported for Linux.

To enable Self-protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Self-protection.
3. Use the Self-protection toggle to enable it.

To enable Password protection

799 © Acronis International GmbH, 2003-2024

1. Once the Self-protection feature is enabled, you can enable the Password protection feature
by using the toggle.
2. Click Generate new password to generate a password to modify or delete local agents.
3. Click Copy, and then paste it in a safe place because this will be requested when you want to
modify the components list locally.

Important
The password will not be available after you close the window. To get this password applied to
devices, the protection plan settings must be saved.

4. Click Close.

Password protection prevents unauthorized users or software from uninstalling Agent for
Windows or modifying its components. These actions are only possible with a password that an
administrator can provide.

A password is never required for the following actions:

l Updating the installation by running the setup program locally

l Updating the installation by using the Cyber Protect console
l Repairing the installation

Default setting: Disabled

For more information about how to enable Password protection, refer to Preventing unauthorized
uninstallation or modification of agents.

Network folder protection

The Protect network folders mapped as local drives setting defines whether Active protection
protects from local malicious processes network folders that are mapped as local drives.

This setting applies to folders shared via SMB or NFS protocols.

If a file was originally located on a mapped drive, it cannot be saved to the original location when
extracted from the cache by the Revert using cache action. Instead, it will be saved to the folder
specified in this setting. The default folder is C:\ProgramData\Acronis\Restored Network Files for
Windows, and Library/Application Support/Acronis/Restored Network Files/ for macOS. If this
folder does not exist, it will be created. If you want to change this path, specify a local folder.
Network folders, including folders on mapped drives, are not supported.

Default setting: On.

This feature defines whether Active protection protects network folders that are shared by you from
the external incoming connections from other servers in the network that may potentially bring
threats.

Default setting: Off.

800 © Acronis International GmbH, 2003-2024

Note
Server-side protection is not supported for Linux.

To set trusted connections

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Server-side protection.
3. Use the Server-side protection toggle to enable it.
4. Select the Trusted tab.
5. In the Trusted connections field, click Add to define connections that will be allowed to modify
data.
6. In the ComputerName/Account field, type the name of the computer and the account of the
machine where the protection agent is installed. For example, MyComputer\TestUser.
7. In the Host name field, type the host name of the machine that is allowed to connect to the
machine using the protection agent.
8. Click the check mark to the right to save the connection definition.
9. Click Done.

To set blocked connections

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Server-side protection.
3. Use the Server-side protection toggle to enable it.
4. Select the Blocked tab.
5. In the Blocked connections field, click Add to define connections that will not be allowed to
modify data.
6. In the ComputerName/Account field, type the name of the computer and the account of the
machine where the protection agent is installed. For example, MyComputer\TestUser.
7. In the Host name field, type the host name of the machine that is allowed to connect to the
machine using the protection agent.
8. Select the check box to the right to save the connection definition.
9. Click Done.

Cryptomining malware degrades the performance of useful applications, increases electricity bills,
and may cause system crashes and even hardware damage due to abuse. The Cryptomining
process detection feature protects your devices against cryptomining malware to prevent
unsanctioned using of computer resources.

801 © Acronis International GmbH, 2003-2024

Administrators can enable Cryptomining process detection, without enabling Active Protection.
Default setting: Enabled.

Note
Cryptomining process detection is not supported for Linux.

To configure network folder protection

1. In the Create protection plan window, expand the Antivirus & Antimalware protection
module.
2. Click Cryptomining process detection.
3. Use the Detect cryptomining processes toggle to enable or disable the feature.
4. Select what to do with processes suspected of cryptomining activities:
Default setting: Stop the process

l Notify only—The software generates an alert.

l Stop the process — The software generates an alert and stops the process.
5. Click Done to apply the selected options to your protection plan.

Protection exclusions enable you to eliminate false positives when a trusted program is considered
ransomware or malware. You can define trusted and blocked items by adding them to the
protection exclusions list.

In the trusted items list, you can add files, processes and folders to consider them as safe in the
system, and to prevent any future detections for these.

In the blocked items list, you can add processes and hashes. This option guarantees that those
processes will be blocked, and your workload will be safe.

Protection Blocked Trusted

exclusion
item

Hash When a hash is added to the blocked When a hash is added to the trusted
list, the system will stop the process, list, the system will know what
based on the provided hash. processes have to be ignored by
monitoring, based on the provided
For example, when you add this MD5
hash.
hash,
938c2cc0dcc05f2b68c4287040cfcf71, For example, when you add this MD5
the process associated with this hash hash,
will be blocked. 938c2cc0dcc05f2b68c4287040cfcf71,
the process associated with this hash
will be trusted and excluded from
monitoring.

Process When a process is added to the When a process is added to the trusted
blocked list, the system will know that list, the system will know that those

802 © Acronis International GmbH, 2003-2024

 Protection Blocked Trusted
exclusion
item

those processes must to be monitored, processes have to be excluded from

and the processes will always be monitoring.
blocked.
Note
For example, if you add this path
Processes signed by Microsoft are
C:\Users\user1\application\nppInstalle
always trusted.
r.exe to the blocked list, this specific
process will be blocked, and when you For example, if you add this path
will try to open it, it will not be allowed C:\Users\user1\application\nppInstaller
to start. .exe, this specific process will be
excluded from monitoring, and
antivirus will not interfere with this
process.

File/folder When a file or a folder is added to the

trusted list, the system will know that
those files or folders should always be
considered safe, and there is no need
for those to be scanned/monitored.

To specify the items that will always be trusted

1. Open the protection plan.

2. Expand the Antivirus and Antimalware protection module.
3. Select the Exclusions option.
The Protection exclusions window opens.
4. In the Trusted items section, click Add to select from the available options:
l To trust files, folders, or processes, select the File/folder/process option. The Add
file/folder/process window opens.
o In the File/process/folder field, enter the path for each process, folder, or file on a new
line. In the Description section, enter a short description so that you can recognize your
change in the list of trusted items.
o Select the Add as file/folder checkbox to trust the file/folder.
Examples of folder description: D:\folder\, /home/Folder/folder2, F:\
o Select the Add as process checkbox to trust a process. The selected processes will be
excluded from monitoring.

Note
Specify the full path to the process executable, starting with the drive letter. For example,
C:\Windows\Temp\er76s7sdkh.exe.

Note
Local network paths are supported. e.g: \\localhost\folderpath\file.exe

803 © Acronis International GmbH, 2003-2024

 l Select the Hash option to add MD5 hashes to the list of trusted items. The Add hash window
opens.
o Here you can insert MD5 hashes on separate lines to be included as trusted in the
Protection exclusions list. Based on these hashes, Cyber Protection will exclude the
processes described by the MD5 hashes from being monitored.

Default setting: No exclusions are defined by default.

To specify the items that will always be blocked

1. Open the protection plan.

2. Expand the Antivirus and Antimalware protection module.
3. Select the Protection exclusions option. The Protection exclusions window opens.
In the Blocked items section, click Add to select from the available options:
l To block processes, select the Process option. The Add process window opens.
o In the Process field, enter the path for each process on a new line. In the Description field,
enter a short description so that you can recognize your change in the list of blocked items.

Note
These processes will not be able to start as long as Active Protection is enabled on the
machine.

l To block hashes, select the Hash option. The Add hash window is displayed.
o In the Hash field, enter the hash for each process on a new line. In the Description field,
enter a short description so that you can recognize your change in the list of blocked items.

Default setting: No exclusions are defined by default.

Wildcards
For specifying folders, you can use the wildcard characters * and ?. The asterisk (*) substitutes for
zero or more characters. The question mark (?) substitutes for exactly one character. Environment
variables, such as %AppData%, cannot be used.

You can use a wildcard (*) to add items to the exclusion lists.

l Wildcards can be used in the middle or the end of a description.

Examples of accepted wildcards in descriptions:

C:\*.pdf

D:\folders\file.*

C:\Users\*\AppData\Roaming

l Wildcards cannot be used at the beginning of a description.

Examples of unaccepted wildcards in descriptions:

*.docx

804 © Acronis International GmbH, 2003-2024

*:\folder\

Variables
You can also use variables to add items to the Protection exclusions list, with the following
limitations:

l For Windows, only SYSTEM variables are supported. User specific variables, for example,
%USERNAME%, %APPDATA% are not supported. Variables with {username} are not supported.
For more information, see https://ss64.com/nt/syntax-variables.html.
l For macOS, environment variables are not supported.
l For Linux, environment variables are not supported.

Examples of supported formats:

l %WINDIR%\Media
l %public%
l %CommonProgramFiles%\Acronis\

Description
You can use the Description field to make notes on the exclusions that you added in the protection
exclusions list. Some suggestions on the notes you may make:

l Reasons and purposes for the exclusion.

l Actual file name of a hash exclusion.
l Time stamps.

If there are multiple items added in a single entry, there can only be 1 comment captured for the
multiple items.

URL filtering
Note
The availability of this feature depends on the service quotas that are enabled for your account.

Malware is often distributed by malicious or infected sites and uses the so called Drive-by download
method of infection.

The URL filtering functionality allows you to protect machines from threats like malware and
phishing coming from the Internet. You can protect your organization by blocking user access to the
websites that may have malicious content.

The URL filtering also allows you to control web usage to comply with the external regulations and
internal company policies. You can configure access to the websites depending on the category they
relate to. The URL filtering supports currently 44 website categories and allows to manage access to
them.

805 © Acronis International GmbH, 2003-2024

Currently, the HTTP/HTTPS connections on Windows machines will be checked by the protection
agent.

The URL filtering feature requires an internet connection to function.

Note
To prevent possible compatibility issues with protection agent builds 15.0.26692 (release C21.03
HF1) and earlier, the URL filtering functionality will be automatically disabled if another antivirus
solution is detected, or if the Windows Security Center service is not present on the system.
In later protection agents, the compatibility issues are resolved so URL filtering is always enabled
according to the policy.

How it works
A user enters a URL link in a browser. The Interceptor gets the link and sends in to the protection
agent. The agent gets the URL, parses it, and then checks the verdict. The Interceptor redirects a
user to the page with the message with available actions to manually proceed to the requested
page.

806 © Acronis International GmbH, 2003-2024

807 © Acronis International GmbH, 2003-2024
URL filtering configuration workflow
Generally, the URL filtering configuration consists of the following steps:

1. You create a protection plan with the enabled URL filtering module.
2. Specify the URL filtering settings (see below).
3. Assign the protection plan to the machines.

To check which URLs have been blocked, go to Monitoring> Alerts.

URL filtering settings

The following settings can be specified for the URL filtering module.

Malicious website access

Specify which action will be performed when a user opens a malicious website:

l Notify only—the software generates an alert about the process suspected of ransomware
activity.
l Block —blocks the access to the malicious website. A user will not be able to access the website
and a warning alert will be generated.
l Always ask user—asks the user whether to proceed to the website anyway or return back.

Categories to filter
There are 44 website categories for which you can configure access:

l Allow – allow access to websites related to the selected category.

l Deny – deny access to websites related to the selected category.

By default all categories are allowed.

Show all notifications for blocked URLs by categories – if enabled, you will get all notifications
shown in the tray for blocked URLs by categories. If a website has several sub-domains, then the
system also generates notifications for them, therefore the number of notifications may be big.

808 © Acronis International GmbH, 2003-2024

In the table below, you can find category descriptions:

Website category Description

1 Advertising This category covers domains whose main purpose is to serve

advertisements.

2 Message boards This category covers forums, discussion boards, and question-answer
type websites. This category does not cover the specific sections on
company websites where customers ask questions.

3 Personal websites This category covers personal websites, as well as all types of blogs:
individual, group, and even company ones. A blog is a journal published
on the World Wide Web. It consists of entries (“posts”), typically displayed
in reverse chronological order so that the most recent post appears first.

4 Corporate/business This is a broad category that covers corporate websites that typically do
websites not belong to any other category.

5 Computer software This category covers websites offering computer software, typically either
open-source, freeware, or shareware. It may also cover some online
software stores.

6 Medical drugs This category covers websites related to medicine/alcohol/cigars that

have discussions on the use or selling of (legal) medical drugs or
paraphernalia, alcohol, or tobacco products.

Note that illegal drugs are covered in the Narcotics category.

7 Education This category covers websites belonging to official educational

institutions, including those that are outside of the .edu domain. It also
includes educational websites, such as an encyclopedia.

8 Entertainment This category covers websites that provide information related to artistic
activities and museums, as well as websites that review or rate content
such as movies, music, or art.

9 File sharing This category covers file-sharing websites where a user can upload files
and share them with others. It also covers torrent-sharing websites and
torrent trackers.

10 Finance This category covers websites belonging to all banks around the world
that provide online access. Some credit unions and other financial
institutions are covered as well. However, some local banks may be left
uncovered.

11 Gambling This category covers gambling websites. These are the “online casino” or
“online lottery” type website, which typically requires payment before a
user can gamble for money in online roulette, poker, blackjack, or similar
games. Some of them are legitimate, meaning there is a chance to win;
and some are fraudulent, meaning that there is no chance to win. It also
detects “beating tips and cheats” websites that describe the ways to

809 © Acronis International GmbH, 2003-2024

 make money on gambling and online lottery websites.

12 Games This category covers websites that provide online games, typically based
on Adobe Flash or Java applets. It does not matter for detection whether
the game is free or requires a subscription, however, casino-style
websites are detected in the Gambling category.

This category does not cover:

l Official websites of companies that develop video games (unless they

produce online games)
l Discussion websites where games are discussed
l Websites where non-online games can be downloaded (some of them
are covered in the Illegal category)
l Games that require a user to download and run an executable, like
World of Warcraft; those can be prevented by different means like a
firewall

13 Government This category covers government websites, including government

institutions, embassies, and office websites.

14 Hacking This category covers websites that provide the hacking tools, articles, and
discussion platforms for hackers. It also covers websites offering exploits
for common platforms that facilitate Facebook or Gmail account hacking.

15 Illegal activities This category is a broad category related to hate, violence and racism,
and it is intended to block the following categories of websites:

l Websites belonging to terrorist organizations

l Websites with racist or xenophobic content
l Websites discussing aggressive sports, and/or promoting violence

16 Health and fitness This category covers websites associated with medical institutions,
websites related to disease prevention and treatment, websites that offer
information or products about weight loss, diets, steroids, anabolic or
HGH products, as well as websites providing information on plastic
surgery.

17 Hobbies This category covers websites that present resources related to activities
typically performed during an individual’s free time, such as collecting,
arts and crafts, and cycling.

18 Web hosting This category covers free and commercial website hosting services that
allow private users and organizations to create and publish web pages.

19 Illegal downloads This category covers websites related to software piracy, including:

l Peer-to-peer (BitTorrent, emule, DC++) tracker websites that are

known in helping to distribute copyrighted content without the
copyright holder's consent
l Warez (pirated commercial software) websites and discussion boards

810 © Acronis International GmbH, 2003-2024

 l Websites providing users with cracks, key generators, and serial
numbers to facilitate the use of software illegally

Some of these websites may also be detected as pornography or

alcohol/cigars, since they often use porn or alcohol advertisements to
earn money.

20 Instant messaging This category covers instant messaging and chat websites that allow
users to chat in real-time. It will also detect yahoo.com and
gmail.com since they both contain an embedded instant messenger
service.

21 Jobs/employment This category covers websites presenting job boards, job-related

classified advertisements, and career opportunities, as well as
aggregators of such services. It does not cover recruiting agencies or the
“jobs” pages on regular company websites.

22 Mature content This category covers the content that was labeled by a website creator as
requiring a mature audience. It covers a wide range of websites from the
Kama Sutra book and sex education websites, to hardcore pornography.

23 Narcotics This category covers websites sharing information about recreational and
illegal drugs. This category also covers websites covering development or
growing drugs.

24 News This category covers news websites that provide text and video news. It
strives to cover both global and local news websites; however, some
small local news websites may not be covered.

25 Online dating This category covers online dating websites – paid and free - where users
can search for other people by using some criteria. They may also post
their profiles to let others search them. This category includes both free
and paid online dating websites.

Because most of the popular social networks can be used as online

dating websites, some popular websites like Facebook are also detected
in this category. We recommend that you use this category with the
Social networks category.

26 Online payments This category covers websites offering online payments or money
transfers. It detects popular payment websites like PayPal or
Moneybookers. It also heuristically detects the webpages on the regular
websites that ask for the credit card information, allowing detection of
hidden, unknown, or illegal online stores.

27 Photo sharing This category covers photo-sharing websites whose primary purpose is to
let users upload and share photos.

28 Online stores This category covers known online stores. A website is considered an
online store if it sells goods or services online.

811 © Acronis International GmbH, 2003-2024

29 Pornography This category covers websites containing erotic content and
pornography. It includes both paid and free websites. It covers websites
that provide pictures, stories, and videos, and it will also detect
pornographic content on mixed-content websites.

30 Portals This category covers websites that aggregate information from multiple
sources and various domains, and that usually offer features such as
search engines, e-mail, news, and entertainment information.

31 Radio This category covers websites that offer Internet music streaming
services, from online radio stations to websites that provide on-demand
(free or paid) audio content.

32 Religion This category covers websites promoting religion or a sect. It also covers
the discussion forums related to one or multiple religions.

33 Search engines This category covers search engine websites, such as Google, Yahoo, and
Bing.

34 Social networks This category covers social network websites. This includes
MySpace.com, Facebook.com, Bebo.com, etc. However, specialized social
networks, like YouTube.com, will be listed in the Video/Photo category.

35 Sport This category covers websites that offer sports information, news, and
tutorials.

36 Suicide This category covers websites promoting, offering, or advocating suicide.

It does not cover suicide prevention clinics.

37 Tabloids This category is mainly designed for soft pornography and celebrity
gossip websites. A lot of the tabloid-style news websites may have
subcategories listed here. Detection for this category is also based on
heuristics.

38 Waste of time This category covers websites where individuals tend to spend a lot of
time. This can include websites from other categories such as social
networks or entertainment.

39 Traveling This category covers websites that present travel offers and travel
equipment, as well as travel destination reviews and ratings.

40 Videos This category covers websites that host various videos or photos, either
uploaded by users or provided by various content providers. This
includes websites like YouTube, Metacafe, Google Video, and photo
websites like Picasa or Flickr. It will also detect videos embedded in other
websites or blogs.

41 Violent cartoons This category covers websites discussing, sharing, and offering violent
cartoons or manga that may be inappropriate for minors due to violence,
explicit language, or sexual content.

This category doesn't cover the websites that offer mainstream cartoons

812 © Acronis International GmbH, 2003-2024

 such as “Tom and Jerry”.

42 Weapons This category covers websites offering weapons for sale or exchange,
manufacture, or usage. It also covers the hunting resources and the
usage of air and BB guns, as well as melee weapons.

43 Email This category covers websites that provide email functionality as a web
application.

44 Web proxy This category covers websites that provide web proxy services. This is a
“browser inside a browser” type website when a user opens a web page,
enters the requested URL into a form, and clicks “Submit”. The web proxy
site downloads the actual page and shows it inside the user browser.

These are the following reasons this type is detected (and might need to
be blocked):

l For anonymous browsing. Since requests to the destination web

server are made from the proxy web server, only its IP address is
visible and if the server administrators trace the user, the trace will
end on web proxy – which may or may not keep logs necessary to
locate the original user.
l For location spoofing. User IP addresses are often used for profiling
the service by the source location (some national government
websites may only be available from local IP addresses), and using
those services might help the user to spoof their true location.
l For accessing prohibited content. If a simple URL filter is used, it will
only see the web proxy URLs and not the actual servers that the user
visits.
l For avoiding company monitoring. A business policy might require
monitoring employee Internet usage. By accessing everything through
a web proxy, a user might escape monitoring that will not provide
correct information.

Since the SDK analyzes the HTML page (if provided), and not just URLs,
for some categories the SDK will still be able to detect the content. Other
reasons, however, cannot be avoided just by using the SDK.

URL exclusions
URLs that are known as safe can be added to the list of the trusted domain. URLs that represent a
threat can be added to the list of the blocked domain.

To specify the URLs that will always be trusted or blocked

1. In the URL filtering module of a protection plan, click URL exclusions.

The URL exclusions window opens.
The following options are displayed:

Trusted items—Click Add to select from the available options:

813 © Acronis International GmbH, 2003-2024

l Domain—When you select this option, the Add domain window opens.
o In the Domain field, enter each domain on a new line. In the Description field, enter a short
description so that you can recognize your change in the list of trusted items.
l Process—When you select this option, the Add process window is displayed.
o In the Process field, enter the path for each process on a new line. In the Description section,
enter a short description so that you can recognize your change in the list of trusted items.

Blocked items—Click Add. The Add domain window is displayed.

In the Domain field, enter each domain on a new line. In the Description field, enter a short
description so that you can recognize your change in the list of blocked items.

Note
Local network paths are supported. For example, \\localhost\folderpath\file.exe.

Description
You can use the Description field to make notes on the exclusions that you added in the URL
exclusions list. Some suggestions on the notes you may make:

l Reasons and purposes for the exclusion.

l Time stamps.

If there are multiple items added in a single entry, there can only be 1 comment captured for the
multiple items.

Microsoft Defender Antivirus and Microsoft Security

Essentials
Note
The availability of this feature depends on the service quotas that are enabled for your account.

Microsoft Defender Antivirus

Microsoft Defender Antivirus is a built-in antimalware component of Microsoft Windows that is
delivered starting from Windows 8.

The Microsoft Defender Antivirus (WDA) module allows you to configure Microsoft Defender
Antivirus security policy and track its status via the Cyber Protect console.

This module is applicable for the workloads on which Microsoft Defender Antivirus is installed.

Microsoft Security Essentials

Microsoft Security Essentials is a built-in antimalware component of Microsoft Windows that is
delivered with Windows versions earlier than 8.

814 © Acronis International GmbH, 2003-2024

The Microsoft Security Essentials module allows you to configure Microsoft Security Essentials
security policy and track its status via the Cyber Protect console.

This module is applicable for the workloads on which Microsoft Security Essentials is installed.

The settings for Microsoft Security Essentials are similar to the settings for Microsoft Defender
Antivirus, but you cannot configure real-time protection, and cannot define exclusions via the Cyber
Protect console.

Schedule scan
Specify the schedule for scheduled scanning.

Scan mode:

l Full – a full check of all files and folders additionally to the items scanned in the quick scan. It
required more machine resources for execution compared to the quick scan.
l Quick – a quick check of the in-memory processes and folders where malware is typically found.
It required less machine resources for execution.

Define the time and day of week when the scan will be performed.

Daily quick scan – define the time for the daily quick scan.

You can set the following options depending on your needs:

Start the scheduled scan when the machine is on but not in use

Check for the latest virus and spyware definitions before running a scheduled scan

Limit CPU usage during the scan to

For more details about the setting for Microsoft Defender Antivirus, refer to
https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-
policies#scheduled-scans-settings

Default actions
Define the default actions to be performed for the detected threats of different severity levels:

l Clean – clean up the detected malware on a workload.

l Quarantine – put the detected malware in the quarantine folder but do not remove it.
l Remove – remove the detected malware from a workload.
l Allow – do not remove or quarantine the detected malware.
l User defined – a user will be prompted to specify the action to be performed with the detected
malware.
l No action – no actions will be taken.
l Block – block the detected malware.

815 © Acronis International GmbH, 2003-2024

For more details about the default actions settings for Microsoft Defender Antivirus, refer to
https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#default-
actions-settings

Real-time protection
Enable Real-time protection to detect and stop malware from installing or running on workloads.

Scan all downloads – if selected, scanning is performed for all downloaded files and attachments.

Enable behavior monitoring – if selected, behavior monitoring will be enabled.

Scan network files – if selected, network files will be scanned.

Allow full scan on mapped network drives – if selected, mapped network drives will be fully
scanned.

Allow email scanning – if enabled, the engine will parse the mailbox and mail files, according to
their specific format, in order to analyze the mail bodies and attachments.

For more details about the real-time protection settings for Microsoft Defender Antivirus, refer to
https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#real-
time-protection-settings

Advanced
Specify the advanced scan settings:

l Scan archive files – include archived files such as .zip or .rar files into scanning.
l Scan removable drives – scan removable drives during full scans.
l Create a system restore point – in some cases an important file or registry entry could be
removed as "false positive", then you will be able to recover from a restore point.
l Remove quarantined files after – define the period after which the quarantined files will be
removed.
l Send file samples automatically when a further analysis is required:
o Always prompt – you will be asked for confirmation before file sending.
o Send safe samples automatically – most samples will be sent automatically except files that
may contain personal information. Such files will require additional confirmation.
o Send all samples automatically – all samples will be sent automatically.
l Disable Windows Defender Antivirus GUI – if selected, the WDA user interface will not be
available to a user. You can manage the WDA policies via Cyber Protect console.
l MAPS (Microsoft Active Protection Service) – online community that helps you choose how to
respond to potential threats.
o I don't want to join MAPS – no information will be sent to Microsoft about the software that
was detected.
o Basic membership – basic information will be sent to Microsoft about the software that was
detected.

816 © Acronis International GmbH, 2003-2024

 o Advanced membership – more detailed information will be sent to Microsoft about the
software that was detected.
For more details, refer to https://www.microsoft.com/security/blog/2015/01/14/maps-in-the-
cloud-how-can-it-help-your-enterprise/

For more details about the advanced settings for Microsoft Defender Antivirus, refer to
https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-
policies#advanced-settings

Exclusions
You can define the following files and folders to be excluded from scanning:

l Processes – any file that the defined process reads from or writes to will be excluded from
scanning. You need to define a full path to the executable file of the process.
l Files and folders – the specified files and folders will be excluded from scanning. You need to
define a full path to a folder or file, or define the file extension.

For more details about the exclusion settings for Microsoft Defender Antivirus, refer to
https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-
policies#exclusion-settings

Firewall management
Note
The availability of this feature depends on the service quotas that are enabled for your account.

Firewall management allows you to easily configure firewall settings on protected workloads.

This functionality in Cyber Protect is provided through a built-in Microsoft Defender Firewall
component of Microsoft Windows. Microsoft Defender Firewall blocks unauthorized network traffic
flowing into or out of your workloads.

Firewall management is applicable for the workloads on which Microsoft Defender Firewall is
installed.

Supported Windows operating systems

The following Windows operating systems are supported for the firewall management:

Windows

l Windows 8
l Windows 8.1
l Windows 10
l Windows 11

Windows Server is not supported.

817 © Acronis International GmbH, 2003-2024

Enabling and disabling firewall management
You can enable firewall management when creating a protection plan. You can change an existing
protection plan to enable or disable firewall management.

To enable or disable firewall management

1. In the Cyber Protect console, go to Devices > All devices.

2. Do one of the following to open the protection plan panel:
l If you are going to create a new protection plan, select a machine to protect, click Protect, and
then click Create plan.
l If you are going to change an existing protection plan, select a protected machine, click
Protect, click the ellipsis (...) next to the name of the protection plan, and then click Edit.
3. In the protection plan panel, navigate to the Firewall management area, and enable or disable
Firewall management.
4. Do one of the following to apply your changes:
l If creating a protection plan, click Create.
l If editing a protection plan, click Save.

Microsoft Defender Firewall status in the Firewall management area of the protection plan
panel is displayed as On or Off, depending on whether you enabled or disabled the firewall
management.

You might also access the protection plan panel from the Management tab. However, this capability
is not available in all editions of the Cyber Protection service.

Quarantine
Quarantine is a special isolated folder on a machine's hard disk where the suspicious files detected
by Antivirus and Antimalware protection are placed to prevent further spread of threats.

Quarantine allows you to review suspicious and potentially dangerous files from all machines and
decide whether they should be removed or restored. The quarantined files are automatically
removed if the machine is removed from the system.

How do files get into the quarantine folder?

1. You configure the protection plan and define the default action for infected files – to place in
Quarantine.
2. The system during the scheduled or on-access scanning detects malicious files, places them in
the secure folder - Quarantine.
3. The system updates the quarantine list on machines.
4. Files are automatically cleaned up from the quarantine folder after the time period defined in
the Remove quarantined files after setting in the protection plan.

818 © Acronis International GmbH, 2003-2024

Managing quarantined files
To manage the quarantined files, go to Antimalware protection > Quarantine. You will see a list
with quarantined files from all machines.

Name Description

File The file name.

Date quarantined The date and time when the file was placed in Quarantine.

Device The device on which the infected file was found.

Threat name The threat name.

Protection plan The protection plan according to which the suspicious file was placed in Quarantine.

You have two possible actions with quarantined files:

l Delete – permanently remove a quarantined file from all machines. You can delete all files with
the same file hash. You can restore all files with the same file hash. Group the files by hash, select
needed files and then delete them.
l Restore – restore a quarantined file to the original location without any modifications. If
currently there is a file with the same name in the original location, then it will be overwritten with
the restored file. Note that the restored file will be added to the allowlist and skipped during
further antimalware scans.

Quarantine location on machines

The default location for quarantined files is:

l For a Windows machine: %programdata%\Acronis\NGMP\quarantine

l For a Mac machine: /Library/Application Support/Acronis/NGMP/quarantine
l For a Linux machine: /var/lib/Acronis/NGMP/quarantine

The quarantine storage is under the service provider's self-defense protection.

Self-service custom folder on-demand

You can select custom folders on the workload and scan them directly from the context menu.

819 © Acronis International GmbH, 2003-2024

To access the Scan with Cyber Protect option in the context menu

For workloads with Antivirus and Antimalware enabled in the protection plan, right-click the
files/folders on which you want to scan.

Note
This option is available only to administrators of the workload.

Corporate whitelist
An antivirus solution might identify legitimate corporate-specific applications as suspicious. To
prevent these false positives detections, the trusted applications are manually added to a whitelist,
which is time consuming.

Note
Corporate whitelist does not affect antimalware scans of backups.

Cyber Protection can automate this process: backups are scanned by the Antivirus and Antimalware
protection module and the scanned data are analyzed, so that such applications are moved to the
whitelist, and false positive detections are prevented. Also, the company-wide whitelist improves the
further antimalware scanning performance.

The whitelist is created for each customer, and is based only on this customer's data.

The whitelist can be enabled and disabled. When it is disabled, the files added to it are temporarily
hidden.

Note
Only accounts with the administrator role (for example, Cyber Protection administrator; company
administrator; partner administrator who acts on behalf of a company administrator; unit
administrator) can configure and manage the whitelist. This functionality is not available for a read-
only administrator account or a user account.

Automatic adding to the whitelist

1. Run a cloud scanning of backups on at least two machines. You can do this by using the backup
scanning plans.
2. In the whitelist settings, enable the Automatic generation of whitelist switch.

Manual adding to the whitelist

Even when the Automatic generation of whitelist switch is disabled, you can add files to the
whitelist manually.

1. In the Cyber Protect console, go to Antimalware protection > Whitelist.

2. Click Add file.
3. Specify the path to the file, and then click Add.

820 © Acronis International GmbH, 2003-2024

Adding quarantined files to the whitelist
You can add files that are quarantined to the whitelist.

1. In the Cyber Protect console, go to Antimalware protection > Quarantine.

2. Select a quarantined file, and then click Add to whitelist.

Whitelist settings
When you enable the Automatic generation of whitelist switch, you must specify one of the
following levels of heuristic protection:

l Low
Corporate applications will be added to the whitelist only after a significant amount of time and
checks. Such applications are more trusted. However, this approach increases the possibility of
false positive detections. The criteria to consider a file as clean and trusted are high.
l Default
Corporate applications will be added to the whitelist according to the recommended protection
level, to reduce possible false positive detections. The criteria to consider a file as clean and
trusted are medium.
l High
Corporate applications will be added to the whitelist faster, to reduce possible false positive
detections. However, this does not guarantee that the software is clean, and it might later be
recognized as suspicious or malware. The criteria to consider a file as clean and trusted are low.

Viewing details about items in the whitelist

You can click an item in the whitelist to view more information about it and to analyze it online.

If you are unsure about an item that you added, you can check it in the VirtusTotal analyzer. When
you click Check on VirusTotal, the site analyzes suspicious files and URLs to detect types of
malware by using the file hash of the item that you added. You can view the hash in the File hash
(MD5) string.

The Machines value represents the number of machines where such hash was found during
backup scanning. This value is populated only if an item came from Backup scanning or Quarantine.
This field remains empty if the file has been added manually to the whitelist.

Antimalware scan of backups

With an antimalware scan of backups, you can prevent recovery of infected files by checking
whether your backups are free of malware. Antimalware scans are performed by a cloud agent that
resides in the Cyber Protection data center and no local computing resources are used.

Note
The availability of this feature depends on the service quotas that are enabled for your account.

821 © Acronis International GmbH, 2003-2024

To perform an antimalware scan, you need to configure a backup scanning plan. For more
information about how to do this, refer to "Backup scanning plans" (p. 189).

Every backup scanning plan creates a scanning task for the cloud agent and adds this task to a
queue, which is one per data center. Scanning tasks are processed according to their order in the
queue. Also, the scanning time depends on the backup size. That is why there is a delay between
creating a backup scanning plan and completing the scan.

The backups that you selected for scanning can be in one of the following states:

l Not scanned
l No malware
l Malware detected

You can check the results of a backup scan in the Backup scanning details (threats) widget. You
can find it in the Cyber Protect console, on the Monitoring > Overview tab.

Limitations
l Antimalware scan is supported for Entire machine or Disks/volumes backups of the following
workloads:
o Windows machines on which a protection agent is installed.
o Windows virtual machines that are backed up at the hypervisor level (agentless backup) by
Agent for Hyper-V and Agent for VMware (Windows).
Antimalware scan is not supported for backups created by virtual appliances, such as Agent for
VMware (Virtual appliance), Agent for Virtuozzo, Agent for Scale Computing HC3.
l Only volumes with the NTFS file system, and GPT or MBR partitioning are scanned.

822 © Acronis International GmbH, 2003-2024

l Only the default cloud storage is supported as backup location. Local storages and partner-
owned cloud storages are not supported.
l When you select backups to scan, you can select backup sets that include a Continuous data
protection (CDP) backup. However, only non-CDP backups in these backup sets will be scanned.
For more information about the CDP backups, refer to "Continuous data protection (CDP)" (p.
389).
l When you perform safe recovery of an entire machine, you can select a backup set that includes
a CDP backup. However, this recovery operation will not use the data in the CDP backup. To
recover the CDP data, run an additional Files/folders recovery operation.

823 © Acronis International GmbH, 2003-2024

Working with Advanced protection features
By default, Cyber Protect includes features that cover most of the cyber security threats. You can
use these features without an additional fee. In addition, you can enable advanced features to boost
the protection of your workloads.

l If an Advanced protection feature is available for you to use, it appears in the protection plan

marked with the Advanced feature icon .

l If an Advanced protection feature is not available for you, contact your administrator to enable
the required Advanced protection pack.
l If the administrator enabled you to buy extra security packs, you can select to enable the
Advanced features. A message will prompt you to a screen to inform you that extra billing
applies.

Note
If at least one feature is enabled, you will have to purchase the corresponding Advanced protection
pack.

Note
If all the Advanced features are disabled on your protection plan, the corresponding Advanced
protection pack will be disabled.

Advanced Advanced protection features

protection
pack

Advanced Protects your workloads continuously and ensures that even last-minute changes of
Backup your work will not be lost. Features include:

l One-click recovery
l Continuous data protection
l Backup support for Microsoft SQL Server clusters and Microsoft Exchange clusters –
Always On Availability Groups (AAG) and Database Availability Groups (DAG)
l Backup support for MariaDB, MySQL, Oracle DB, and SAP HANA
l Data protection map and compliance reporting
l Off-host data processing
l Backup frequency for Microsoft 365 and Google Workspace workloads
l Remote operations with bootable media
l Direct backup to Microsoft Azure public cloud storage

Advanced Protects your workloads continuously from all malware threats. Features include:
Security + EDR
l Manage incidents in a centralized Incident page
l Visualize the scope and impact of incidents
l Recommendations and remediation steps
l Check for publicly disclosed attacks on your workloads using Threat feeds

824 © Acronis International GmbH, 2003-2024

 l Store security events for 180 days

l Antivirus and antimalware protection with local signature-based detection (with real-
time protection)
l Exploit prevention
l URL filtering
l Endpoint firewall management
l Forensic backup, scan backups for malware, safe recovery, corporate allowlist
l Smart protection plans (integration with CPOC alerts)
l Centralized backup scanning for malware
l Remote wipe
l Microsoft Defender Antivirus
l Microsoft Security Essentials

Advanced Allows you to patch vulnerabilities on the protected workloads. Features include:
Management
l Patch management
l Disk health
l Software inventory
l Fail-safe patching
l Cyber Scripting
l Remote assistance
l File transfer and sharing
l Selecting a session to connect
l Observing workloads in multi-view
l Connection modes: control, view-only, and curtain
l Connection via the Quick Assist application
l Remote connection protocols: NEAR and Apple Screen Sharing
l Session recording for NEAR connections
l Screenshot transmission
l Session history report
l 24 monitors
l Threshold-based monitoring
l Anomaly-based monitoring

Advanced Data Prevents leakage of sensitive information from the protected workloads. Features
Loss include:
Prevention
l Content-aware prevention of data loss from workloads via peripheral devices and
network communication
l Pre-built automatic detection of personally identifiable information (PII), protected
health information (PHI), and Payment Card Industry Data Security Standard (PCI
DSS) data, as well as documents in the “Marked as Confidential” category
l Automatic data loss prevention policy creation with optional end user assistance
l Adaptive data loss prevention enforcement with automatic learning-based policy
adjustment
l Cloud-based centralized audit logging, alerting, and end user notifications

825 © Acronis International GmbH, 2003-2024

Advanced Data Loss Prevention
The Advanced Data Loss Prevention module analyzes the content and context of data transfers on
protected workloads and prevents leakage of sensitive data trough peripheral devices or network
transfers within and outside the company network based on data flow policy.

Advanced Data Loss Prevention features can be included in any protection plan for a customer
tenant if the Protection service and the Advanced Data Loss Prevention pack are enabled for this
customer.

Before you start using the Advanced Data Loss Prevention module, verify that you read and
understand the basic concepts and logic of Advanced DLP management that are described in the
Fundamentals guide.

You might also want to review the Technical Specifications document.

Creating the data flow policy and policy rules

The key principle of data loss prevention demands that users of a corporate IT system should be
allowed to handle sensitive data only to the extent necessary to perform their job duties. Any other
sensitive data transfers - irrelevant to the business processes - should be blocked. Therefore it is
crucial to distinguish between business-related and rogue data transfers, or flows.

The data flow policy contains rules that specify which data flows are allowed and which are
prohibited, thus preventing unauthorized transfers of sensitive information when the Data Loss
Prevention module is enabled in a protection plan and running in Enforcement mode.

Each sensitivity category in the policy contains one default rule, marked with an asterisk (*) and one
or more explicit (non-default) rules that define the data flows for specific users or groups. Read
more about the types of policy rules in the Fundamentals guide.

The data flow policy is usually created automatically while Advanced Data Loss Prevention is running
in observation mode. The time required for building a representative data flow policy is
approximately one month, but it could differ, depending on the business processes in your
organization. The data flow policy can also be created, configured, or edited manually by a company
or unit administrator.

To start the automatic creation of data flow policy

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Management > Protection plans.
3. Click Create plan.
4. Expand the Data Loss Prevention section and click the Mode row.

826 © Acronis International GmbH, 2003-2024

5. In the Mode dialog, select Observation mode, and select how to process data transfers:
Option Description

Allow all All transfers of sensitive data from user workloads are treated as necessary for the
business process and safe. A new rule is created for every detected data flow that does
not match an already defined rule in the policy.

Justify All transfers of sensitive data from user workloads are treated as necessary for the
all business process, but risky. Therefore, for every intercepted transfer of sensitive data to
any recipient or destination both inside and outside the organization that does not match
a previously created data flow rule, the user must provide a one-time business
justification. When the justification is submitted, a new data flow rule is created in the data
flow policy.

Mixed The Allow all logic is applied for all internal sensitive data flows, and the Justify all logic is
applied for all external data flows.

Note
For more information about internal and external data see Automated detection of
destination

6. Save the protection plan and apply it to the workloads from which you want to collect data to
build the policy.

Note
Data leakage is not prevented during observation mode.

To configure the data flow policy manually

1. In the Cyber Protect console, navigate to Protection > Data flow policy.
2. Click New data flow rule.
The New data flow rule pane expands on the right.
3. Select a sensitivity category, add a sender and a recipient, and define the permission for data
transfers for the selected category, sender, and recipient.
Option Description

Allow Allow this sender to transfer data of this sensitivity category to this recipient.

Exception Do not allow this sender to transfer data of this sensitivity category to this recipient,
but allow the sender to submit an exception to the rule for a specific transfer.
When this sender tries to transfer data of this sensitivity category to this recipient,
block the transfer and ask the sender to submit an exception to allow this transfer.
When the exception is submitted, the data transfer is allowed to proceed.

Important
All subsequent data transfers between this sender and recipient for this sensitivity
category will be allowed for five minutes after the exception is submitted.

827 © Acronis International GmbH, 2003-2024

 Option Description

Deny Do not allow this sender to transfer data of this sensitivity category to this recipient,
and do not allow the sender to request an exception to the rule.

4. (Optional) Select an action that should be executed when the rule is triggered.
Action Description

Write in log Store an event record in the audit log when the rule is triggered. We
recommend to select this action for rules with Exception permission.

Generate an alert Generate an alert in the Cyber Protect Alerts tab when the rule is triggered.
If notifications are enabled for the administrator, an email notification will
be sent as well.

Notify the end user Notify the user in real time with an on-screen warning when they trigger the
when a data transfer rule.
is denied

5. Click Save.
6. Repeat steps 2 to 5 to create multiple rules of different sensitivity categories and options, and
verify that the resulting rules correspond to the options that you selected.

Data flow policy structure

In the Data flow policy view, policy rules are grouped according to the category of sensitive data
that they control. The sensitivity category identifier is displayed right above the group of policy rules.

l Sensitive
o Protected Health Information (PHI)
o Personally Identifiable Information (PII)
o Payment Card Industry Data Security Standard (PCI DSS),
o Marked as Confidential
l Non-sensitive

For more information on the data flow policy concept and features, see the Fundamentals guide.

Rule structure
Each policy rule consists of the following elements.

l Sensitivity Category
o Protected Health Information (PHI)
o Personally Identifiable Information (PII)
o Payment Card Industry Data Security Standard (PCI DSS)
o Marked as Confidential
See "Sensitive data definitions" (p. 838)

828 © Acronis International GmbH, 2003-2024

l Sender - specifies the initiator of a data transfer controlled by this rule. It may be a single user, a
list of users, or user group.
o Any internal - a user group that includes all internal users of the organization.
o Contact / From organization - a Windows account in the organization, recognized by
Advanced Data Loss Prevention, as well as all other accounts (including those used by third-
party communication applications) that a given Windows account has used earlier.
o Contact / Custom identity - identifier of an internal user specified in one of the following
formats: email, Skype ID, ICQ identifier, IRC identifier, Jabber e-mail, Mail.ru Agent e-mail, Viber
phone number, Zoom e-mail.
The following wild cards can be used for specifying a group of contacts:
n * - any number of symbols
n ? - any single symbol
l Recipient - specifies the destination of a data transfer controlled by this rule. It may be a single
user, a list of users, or user group, as well as other types of destinations specified below.
o Any - any of the recipient types supported by Advanced DLP.
o Contact / Any contact - any internal or external contact.
o Contact / Any internal contact - any contact of an internal user (see "Automated detection of
destination" (p. 838)).
o Contact / Any external contact - any contact of an external person or entity.
o Contact / From organization - the same principle as described in the Sender field.
o Contact / Custom identity - the same principle as described in the Sender field.
o File sharing services - the identifier of a controlled file sharing service.
o Social network - the identifier of a controlled social network.
o Host / Any host - any computer recognized by Advanced DLP as internal or external.
o Host / Any internal host - any computer recognized by Advanced DLP as internal.
o Host / Any external host - any computer recognized by Advanced DLP as external.
o Host / Specific host - a computer identifier specified as a host name (e.q. FQDN) or IP address
(IPv4 or IPv6).
o Device / Any device - any peripheral device connected to the workload.
o Device / External storage - a removable storage or redirected mapped drive connected to
the workload.
o Device / Encrypted removable - a removable storage device encrypted with BitLocker To Go.
o Device / Redirected clipboard - a redirected clipboard connected to the workload.
o Printers - any local or network printer connected to the workload.
l Permission - a preventive control enforced over a data transfer controlled by this rule. Described
in more detail in topic Permissions in data flow policy rules.
l Action - a non-preventive action performed when this rule is triggered. By default this field is set
to "No action". The options are:
o Write in log - store an event record in the audit log when the rule is triggered.
o Notify the end user when a data transfer is denied - notify user with a real-time onscreen

829 © Acronis International GmbH, 2003-2024

 warning when they trigger the rule.
o Generate an alert - alert the administrator when the rule is triggered.

Warning!
When No action is selected and the rule is triggered:
l no event record is added to the audit log;
l no alert is sent to the administrator;
l no onscreen notification is displayed to the end user.

What triggers a policy rule?

A data transfer matches a data flow policy rule if all of the following conditions are true:

l All senders of this data transfer are listed or belong to a user group specified in the Sender field
of the rule.
l All recipients of this data transfer are listed or belong to a user group specified in the Recipient
field of the rule.
l The data being transferred matches the Sensitivity category of the rule.

Adjusting the permissions in data flow policy rules

Advanced Data Loss Prevention supports three types of permissions in data flow policy rules. The
permissions are configured individually in each rule of the policy.

Allow Data transfers that match the combination of sensitivity category, sender, and recipient
(permissive) defined in the rule are allowed.

Exception Data transfers that match the combination of sensitivity category, sender, and recipient
(prohibitive) defined in the rule are not allowed, but the sender can submit an exception to the rule to
allow a specific transfer.

Important
All subsequent data transfers between this sender and recipient for this sensitivity
category will be allowed for five minutes after the exception is submitted.

Deny Data transfers that match the combination of sensitivity category, sender, and recipient
(prohibitive) defined in the rule are not allowed, and the sender does not have the option to submit an
exception.

In addition, a priority flag can be assigned to the Allow and Exception permissions to increase the
policy management flexibility. With this setting, you can override the permissions set for specific
groups in other data flow rules in the policy. You can use it to apply a group data flow rule only to
some of its members. To achieve this, you must create a data flow rule for specific users that you
want to exclude from the group rules, and then prioritize their permissions over the data flow
restrictions configured in the rules for the group to which these users belong. For information on
permission priorities when combining rules, see "Combining data flow policy rules" (p. 831).

830 © Acronis International GmbH, 2003-2024

Important
Before switching a company or unit policy from Observation to Enforcement mode, it is crucial to
adjust the default rules for each sensitive data category from the permissive to a prohibitive state.
Default rules are marked with an asterisk (*) in the Data flow policy view. Read more about the
types of policy rules in the Fundamentals guide.

To edit permissions in policy rules

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Protection > Data flow policy.
3. Select the policy rule that you wish to edit and click Edit above the rules list.
The Edit data flow rule window opens.
4. In the Permission section, select Allow, Exception, or Deny.
5. (Optional) To prioritize the Allow or Exception permission of this rule over the permissions in
other rules, select the Prioritize check box.
You do not need to use this check box to prioritize a data flow rule over the default Any > Other
rule, because it has the lowest priority in the policy by default.
For information on permission priorities when combining rules, see "Combining data flow policy
rules" (p. 831).
6. (Optional) Select an action to be executed when the rule is triggered.
7. Save the changes to the policy rule.

Combining data flow policy rules

When a data transfer matches more than one rule, the permissions and actions configured for all
rules are combined and applied as follows.

Permissions
If а data transfer matches more than one rule and these rules have different permissions for the
same data category, the overriding rule is the one with higher priority permission, according to the
following permission priority list (in descending order):

1. Exception with the Prioritized flag

2. Allow with the Prioritized flag
3. Deny
4. Exception
5. Allow

If а data transfer matches more than one rule and these rules have different permissions for
different data categories, the following logic is applied for the override:

1. The most restrictive rule permission is defined for each of the sensitivity categories that the data
transfer matches.
2. The most restrictive of the rule permissions defined in point 1 is enforced.

831 © Acronis International GmbH, 2003-2024

Example

A file transfer matches three rules in different sensitivity categories as follows:

Sensitivity category Permission

PII Allow - Prioritized

PHI Exception - Prioritized

PCI Deny

The permission that will be applied is Deny.

Actions
If a data transfer matches more than one rule and these rules have different options configured in
the Action field, all configured actions in all triggered rules are performed.

Policy review and management

Before the automatically created baseline data flow policy is enforced, it has to be reviewed,
validated, and approved by the client, because it is the client who inherently knows all the specifics
of their business processes and can assess whether they are consistently interpreted in the baseline
policy. Also, the client can identify inaccuracies, which are then fixed by the partner administrator.

During the policy review, the partner administrator presents the baseline data flow policy to the
client, who reviews each data flow in the policy and validates its consistency with their business
processes. The validation does not require any technical skills, because the representation of policy
rules in the Cyber Protect console is intuitively clear: each rule describes who are the sender and the
recipient of a sensitive data flow.

Based on client’s instructions, the partner administrator manually adjusts the baseline policy by
editing, deleting, and creating data flow policy rules. After client’s approval, the reviewed policy is
enforced on protected workloads by switching the protection plan applied to these workloads to the
Enforcement mode.

Before enforcing a reviewed policy, it is important to change the Allow permission in all
automatically created default policy rules for sensitive data categories to Deny or Exception. The
Deny permission cannot be overriden by users, while the Exception permission blocks a transfer
matching the rule but allows users to override the block in an emergency situation by submitting a
business-related exception.

Data flow policy renewal

When the business process of the company or its unit is considerably changed, their DLP policies
have to be renewed in order to make them consistent with the changes in sensitive data flows of the
updated business process. A policy renewal is also required if an employee’s job role is changed – in
this case, the part of the unit policy used to protect employee workload has also to be renewed.

832 © Acronis International GmbH, 2003-2024

The Advanced DLP policy management workflow allows administrators to automate policy renewals
for the entire company, a unit, a user, or a part of users in a unit.

Renewing the policy for a company or unit

All options of the Observation mode can be used to renew the company or unit-wide policy, as well
a part of a unit policy for one or more users in the unit.

To renew the policy for a company or unit

The renewal process consists of the following steps that must be performed by a Company
administrator or a Partner who manages the company workloads.

1. Delete all non-default rules in the enforced policy.

2. To start the renewal, switch the protection plan with Advanced DLP applied to the company or
unit to one of the observation mode options, depending on which one is the optimal for this
particular company or unit, and then apply the plan to all workloads in the company or the unit.
3. When the renewal period ends, review the new company or unit policy with the client, adjust if
necessary, and get an approval by the client.
4. Switch the protection plan applied to the company or unit workloads to an appropriate
enforcement mode option, which the client considers as optimal for preventing data leakage
from the unit's workloads.

Renewing the policy for one or more users in the company or unit
User-level policies can be renewed by using any option of the Observation mode, as well as the
adaptive enforcement mode.

Using the Observation mode for renewing a user policy

Using the observation mode for renewing a policy for a user or a part of users in the company (or
unit) has the following specifics: the data flow policy enforced for the entire company (or unit) is not
enforced over user's data transfers during the renewal period. As a result, new individual rules for
the user can be created during the renewal that could contradict with or match existing group rules
in the enforced policy for the company (or unit). After the renewal is completed and the policy is re-
enforced over the user's data transfers, whether these new individual rules created for the user will
be actually applied or not to the user's data transfers depends on their priorities in comparison with
other rules in the policy that these data transfers match.

To renew the policy for a user through Observation mode

The renewal process consists of the following steps that must be performed by a Company
administrator or a Partner who manages the company workloads.

1. Delete all non-default rules in the policy enforced for the company (or unit) that have the user as
their single sender.
2. Remove the user from the sender lists of all non-default data flow rules in the enforced policy.

833 © Acronis International GmbH, 2003-2024

3. Create a new protection plan with Advanced DLP in observation mode and apply it to the user's
workload to start the renewal (observation) period.
The duration of the renewal period depends on how long it could take for the user to have
performed all or 90-95% of their regular business activities that involve transferring sensitive
data from their workloads.
4. When the renewal period ends, review the new rules related to this user that have been added
to the enforced policy, adjust them if necessary, and get them approved by the client.
5. Switch the protection plan applied to the user's workload to the Strict enforcement mode or
the Adaptive enforcement mode - depending on which option the client considers as optimal
for preventing data leakage from the user's workload.
Alternatively, you can re-apply to the user's workload the protection plan applied to the company
(or unit).

Using the Adaptive enforcement mode for renewing a user policy

Policy renewal for a single user or a part of all users in the company (or unit) can be performed by
using the Adaptive enforcement mode of a protection plan with Advanced DLP applied to the user's
workload.

Note
This policy renewal method has the following specifics: the enforced company (unit) policy rules for
sender groups with the user's membership (i.e. Any internal) are also enforced over data transfers
from this user during the renewal. As a result, the renewal will not create new individual rules for
the user that would contradict with or match these already existing policy rules for sender groups.
Which of these two methods is more effective for user policy renewals for a particular client
depends on its specific IT security requirements

To renew the policy for a user through Adaptive enforcement mode

The renewal process consists of the following steps that must be performed by a Company
administrator or a Partner who manages the company workloads.

1. Delete all non-default rules in the policy enforced for the company (unit) that have the user as
their single sender.
2. Remove the user from the sender lists of all non-default data flow rules in the enforced policy.
3. For all default rules in the policy enforced for the company (or unit), set their permission to
Exception, and select the Write in log action in the Action field.
4. If the protection plan currently applied to the user's workload is set to the Strict enforcement
mode, create a new protection plan with Advanced DLP and apply it to the user's workload in the
Adaptive enforcement mode to start the renewal period.
The duration of the renewal period depends on how long it could take for the user to have
performed all or 90-95% of their regular business activities that involve transferring sensitive
data from their workloads.
5. When the renewal period ends, review the new rules related to this user that have been added
to the enforced policy, adjust them if necessary, and get them approved by the client.

834 © Acronis International GmbH, 2003-2024

6. Switch the protection plan applied to the user's workload to the Strict enforcement mode or
leave it in the Adaptive enforcement mode - depending on which option the client considers as
optimal for preventing data leakage from the user's workload.
Alternatively, you can re-apply to the user's workload the protection plan applied to the company
(or unit).

Enabling Advanced Data Loss Prevention in protection plans

Advanced Data Loss Prevention features can be included in any protection plan for a customer
tenant if the Protection service and the Advanced Data Loss Prevention pack are enabled for this
customer.

Advanced DLP is the advanced module of the Data loss prevention feature group. The Advanced
DLP features and Device control can be used independently or together (in a single protection plan,
or in two plans protecting the same workload). If used together, their functional capabilities are
coordinated as follows.

l Device control stops controlling user access to those local channels in which Advanced DLP
inspects the content of transferred data. However, Device control retains the control over the
following device types if they are configured to Read-only or Denied access:
o Removable
o Encrypted removable
o Mapped drive
For example, if you have both Device control and Advanced DLP enabled in a single protection
plan or in two plans protecting the same workload, and you have the Read-only access configured
for USB devices in Device control, the Read-only access will be applied to all USB devices, except
for the ones in the allowlist, regardless of the access settings in the Advanced DLP module. If the
default, Enable access is configured in Device control, the access setting in Advanced DLP will be
applied.
l User access to the following local channels and peripherals in the allowlist is enforced by Device
Control:
o Optical drives
o Floppy drives
o MTP-connected mobile devices
o Bluetooth adapters
o Windows clipboard
o Screenshot captures
o USB devices and device types (except for Removable storage and Encrypted)

To create a protection plan with Advanced DLP

1. Navigate to Management > Protection plans.

2. Click Create plan.
3. Expand the Data Loss Prevention section and click the Mode row.
The Mode dialog opens.

835 © Acronis International GmbH, 2003-2024

 l To start the creation or renewal of the data flow policy, select Observation mode and then
select how to process data transfers:
Option Description

Allow all All transfers of sensitive data from user workloads are treated as necessary for the
business process and safe. A new rule is created for every detected data flow that does
not match an already defined rule in the policy.

Justify All transfers of sensitive data from user workloads are treated as necessary for the
all business process, but risky. Therefore, for every intercepted transfer of sensitive data
to any recipient or destination both inside and outside the organization that does not
match a previously created data flow rule, the user must provide a one-time business
justification. When the justification is submitted, a new data flow rule is created in the
data flow policy.

Mixed The Allow all logic is applied for all internal transfers of sensitive data, and the Justify all
logic is applied for all external transfers of sensitive data.
For definition of internal destinations, see "Automated detection of destination" (p. 838)

Warning!
o Select Observation mode only if you do not have a data flow policy created before or if
you are renewing the policy. Before you start the policy renewal, see "Data flow policy
renewal" (p. 832).
o Data leakage is not prevented in the Observation mode. See Observation mode in the
Fundamentals guide.

l To enforce the existing data flow policy, select Enforcement mode, and then select how
strictly to enforce the data flow policy rules:
Option Description

Strict The data flow policy is enforced as is and will not be extended with new
enforcement permissive policy rules when previously unobserved sensitive data flows are
detected. See Strict enforcement in the Fundamentals guide.

Adaptive The enforced policy continues its automatic adaptation to those business
enforcement operations that were not performed during the observation period or to
(Enforcement changes in business processes. This mode allows the enforced data flow policy
with learning) to expand based on newly learned data flows detected on the workloads. See
Adaptive enforcement in the Fundamentals guide.

Important
Before switching a company or unit policy from Observation to Enforcement mode, it is
crucial to adjust the default rules for each sensitive data category from the permissive to a
prohibitive state. Default rules are marked with an asterisk (*) in the Data flow policy view.
Read more about the types of policy rules in the Fundamentals guide.

4. Click Done to close the Mode dialog.

836 © Acronis International GmbH, 2003-2024

5. (Optional) To configure optical character recognition, allowlists, and more protection options,
click Advanced Settings.
For information on available options, see "Advanced settings" (p. 837).
6. Save the protection plan and apply it to the workloads that you want to protect.

Advanced settings
You can use the advanced settings in protection plans with Advanced Data Loss Prevention to
increase the quality of data content inspection in channels controlled by Advanced Data Loss
Prevention, as well as exclude from any preventive controls data transfers to peripheral device
types in the allowlist, categories of network communications, destination hosts, as well as data
transfers initiated by applications in the allowlist. You can configure the following advanced settings:

l Optical character recognition

This setting turns on or off optical character recognition (OCR) in order to extract pieces of text in
31 language for further content inspection from graphical files and images in documents,
messages, scans, screenshots, and other objects.
l Transfer of password-protected data
The content of password-protected archives and documents cannot be inspected. With this
setting, Advanced DLP allows the administrator to select whether outgoing transfers of password-
protected data are to be allowed or blocked.
l Prevent data transfer on errors
Sometimes, the analysis of content that is being sent might fail or another control error might
occur in DLP agent operations. If this option is enabled, the transfer will be blocked. If the option
is disabled, the transfer will be allowed despite the error.
l Allowlist for device types and network communications
Data transfers to the types of peripheral devices and in network communications checked in this
list are allowed regardless of their data sensitivity and the enforced data flow policy.

Warning!
This option is used if issues with a specific Device type or Protocol occur. Do not enable it unless
advised by a Support representative.

l Allowlist for remote hosts

Data transfers to destination hosts specified in this list are allowed regardless of their data
sensitivity and the enforced data flow policy.
l Allowlist for applications
Data transfers performed by applications specified in this list are allowed regardless of their data
sensitivity and the enforced data flow policy.

The Security level indicator of Advanced settings displayed in the Create protection plan view
and in the "Details" view of a protection plan has the following logic of level indication:

837 © Acronis International GmbH, 2003-2024

l Basic indicates that none of the advanced settings is turned on.
l Moderate indicates that one or more settings are turned on, but the combination of OCR,
Transfer of password-protected data, and Prevent data transfer on errors is not activated.
l Strict indicates that at least the combination of OCR, Transfer of password-protected data,
and Prevent data transfer on errors settings is activated.

Automated detection of destination

In Mixed Observation mode, Advanced Data Loss Prevention applies different rules depending on
the destination of the detected data transfer - internal or external. The logic for determining a
destination as internal is described below. All other destinations are considered external.

For each intercepted data transfer, Advanced Data Loss Prevention detects automatically if the
destination HTTP, FTP, or SMB server is internal by performing a DNS request and comparing the
FQDN names of the machine where the Data Loss Prevention agent runs and the remote server. If
the DNS request fails, it also checks if the protected workload and the remote server are in the same
network. Servers that have the same domain name (or are in the same subnetwork) as the machine
where the Data Loss Prevention agent runs are considered internal.

For email communication, Advanced Data Loss Prevention treats as internal transfers all emails sent
from a corporate email address by using the corporate mail server if the recipient email is on the
same domain as the sender email, and the recipient mail server name is the same.

Non-corporate emails are treated as external communication unless the recipient account is known.
Known email addresses are updated as Data Loss Prevention monitors the user activity on the
network and updates the database at the back end with data for email addresses associated with
the user.

Communications via messengers are treated as external communications unless the recipient
account is known. Known accounts are updated as Data Loss Prevention monitors the user activity
on the network and updates the database at the back end with data for accounts associated with
the user.

Sensitive data definitions

This topic describes the logic of identifying sensitive data during content analysis.

To reduce the number of false positives, identical matches are counted as one match for all groups
of the described logical expressions.

Important
The logical expressions used for content identification are provided for information only and do not
describe the solution in full detail.

838 © Acronis International GmbH, 2003-2024

Protected Health Information (PHI)

Supported languages
l US, UK, English-International
l Finnish
l Italian
l French
l Polish
l Russian
l Hungarian
l Norwegian
l Spanish

Data considered Protected Health Information

The following data is considered protected health information.

l First names and last names

l Address (street, city, county, precinct, zip code, and their equivalent geocodes)
l Phone numbers
l Email addresses
l Social security numbers
l Health plan beneficiary numbers
l Bank account numbers
l URLs
l IP address numbers
l ICD-10-CM codes
l ICD-10-PCS-and-GEMs
l HIPAA
l Other health-care related
l Credit card numbers

Logical expression used for content detection

The logical expression consists of the following strings that are joined by the logical operator OR.
The OR operator is used to join different data groups in the list above if the AND logical operator is
not specified explicitly. The numbers in brackets represent the number of detected instances that
would return a positive detection result.

l Social Security Numbers (5)

l (First names and Last names (3) OR Address (3) OR Phone Numbers (3) OR Email Address
(3) OR Bank Account Numbers (3) OR Credit Card Numbers (3)) AND (Social security numbers

839 © Acronis International GmbH, 2003-2024

 (3) OR Health plan beneficiary numbers (3) * OR ICD-10-CM codes (3) OR ICD-10-PCS-and-GEMs
(3) OR HIPAA (3) OR * Other Health-care related (3))

Personally Identifiable Information (PII)

Supported languages
l US, UK, English-International
l Bulgarian
l Chinese
l Czech
l Danish
l Dutch
l Finnish
l French
l German
l Hungarian
l Indonesian
l Italian
l Korean
l Malay
l Norwegian
l Polish
l Portuguese (Brazil)
l Portuguese (Portugal)
l Romanian
l Russian
l Serbian
l Singapore
l Spanish
l Swedish
l Taiwan
l Turkish
l Thai
l Japanese

Data considered Personally Identifiable Information (PII)

l First names and last names
l Address (street, city, county, zip code)
l Bank account numbers

840 © Acronis International GmbH, 2003-2024

l Personal and fiscal ID numbers
l Passport numbers
l Social security numbers
l Phone numbers
l Car plate numbers
l Driving license numbers
l Identifiers and serial numbers
l IP addresses
l Email addresses
l Credit card numbers

Logical expression used for content detection

Logical expression for all supported languages except Japanese

The logical expression consists of the following strings joined by the logical operator OR or AND. The
numbers in brackets represent the number of detected instances that would return a positive
detection result.

l Personal and fiscal ID numbers (5)

l First names and Last names (3) AND (Credit Card Number (3) OR Social Security Number (3) OR
Bank Account Number (3) OR Personal and fiscal ID numbers (3) OR Driving license numbers (3)
OR Passport Numbers (3) OR Social security numbers (3) OR IP Addresses (3) OR Car plate
numbers (3) OR Identifiers and serial numbers)
l Phone Numbers (3) AND (Credit Card Number (3) OR Social Security Number (3) OR Bank Account
Number (3) OR Address (3) OR Personal and fiscal ID numbers (3) OR Driving license numbers (3)
OR Passport Numbers (3) OR Social security numbers (3) OR Car plate numbers (3) OR Identifiers
and serial numbers (3))
l (First names and Last names (30) OR Address (30)) AND (Email Addresses (30) OR Phone
Numbers (30) OR IP Addresses (30))
l Email Addresses (3) AND (Credit Card Number (3) OR Social Security Number (3) OR Bank Account
Number (3) OR Personal and fiscal ID numbers (3) OR Driving license numbers (3) OR Passport
Numbers (3) OR Social security numbers (3) OR Car plate numbers (3) OR Identifiers and serial
numbers (3))
l Email Address (30) AND (Address (30) OR Phone Numbers (30))
l First names and Last names (30) AND Address (30)
l Phone Numbers (30) AND Address (30)
l First names and Last names (3) AND Bank Account Numbers (3)
l Phone Numbers (3) AND (Credit Card Number (3) OR Bank Account Number (3) OR Social security
numbers (3) OR Personal and fiscal ID numbers (3) OR Driving license numbers (3) OR Passport
Numbers (3))

841 © Acronis International GmbH, 2003-2024

Logical expression for Japanese

Note
Only unique matches are counted by content detection.

The logical expression consists of the following strings joined by the logical operator OR. The
operator OR is used to join different groups if logical operator AND is not explicitly specified.

l Social security numbers (5)

l First names and Last names (3) AND (Credit Card Number (3) OR Bank Account Number (3) OR
Driving license numbers (3) OR Passport Numbers (3) OR Social security numbers (3))
l First names and Last names (30) AND (Email Addresses (30) OR Phone Numbers (30) OR IP
Addresses (30) OR Address (30))
l Address (3) AND (Credit Card Number (3) OR Bank Account Number (3) OR Driving license
numbers (3) OR Passport Numbers (3) OR Social security numbers (3))
l Email Address (3) AND (Credit Card Number (3) OR Bank Account Number (3) OR Social security
numbers (3) OR Driving license numbers (3))
l Address (5) AND (Email Address (5) OR First names and Last names (5) OR Phone Numbers (5) OR
IP Addresses (5))
l First names and Last names (3) AND Bank Account Numbers (3)
l Phone Numbers (3) AND (Credit Card Number (3) OR Bank Account Number (3) OR Address (3)
OR Social security numbers (3) OR Driving license numbers (3))

Payment Card Industry Data Security Standard (PCI DSS)

Supported languages
This sensitivity group is language - independent. Тhe PCI DSS data is in English in all countries.

Data considered PCI DSS

l Cardholder data
o Primary Account Number (PAN)
o Cardholder Name
o Expiration date
o Service code
l Sensitive Authentication Data
o Full track data (magnetic-stripe data or equivalent on a chip)
o CAV2/CVC2/CVV2/CID
o PINs/PIN blocks

842 © Acronis International GmbH, 2003-2024

Logical expression used for content detection
The logical expression consists of the following strings joined by the logical operator OR. The
numbers in brackets represent the number of detected instances that would return a positive
detection result.

l Credit Card Number (5)

l Credit Card Number (3) AND (American Name (Ex) (3) OR American Name (3) OR PCI DSS
Keywords (3) OR Date (month/year) (3))
l Credit Card Dump (5)

Marked as Confidential
Data marked as confidential is detected through keywords group.

The Match condition is weight-based, and every word has weight == 1. The content detection is
considered positive when Match if weight > 3.

Supported languages
l English
l Bulgarian
l Chinese Simplified
l Chinese Traditional
l Czech
l Danish
l Dutch
l Finnish
l French
l German
l Hungarian
l Indonesian
l Italian
l Japanese
l Korean
l Malay
l Norwegian
l Polish
l Portuguese - Brazil
l Portuguese - Portugal
l Russian
l Serbian
l Spanish

843 © Acronis International GmbH, 2003-2024

l Swedish
l Turkish

Keyword groups
The keyword group for each language contains the country-specific equivalents of the following
keywords that are used for the English language (case-insensitive).

l confidential
l internal distribution
l not for distribution
l do not distribute
l not for public
l not for external distribution
l for internal use only
l highly qualified documentation
l private
l privileged information
l for internal use only
l for official use only

Data Loss Prevention events

Advanced Data Loss prevention generates events in the DLP events view as follows.

l During observation mode, events are generated for all justified data transfers.
l During enforcement mode, events are generated based on the Write in log action configured for
each policy rule that is triggered.

To view the events for a rule in the data flow policy

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Protection > Data flow policy.
3. Locate the rule for which you want to view the events and click the ellipsis at the end of the rule
line.
4. Select View events.

To view details about an event in the DLP events view

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Protection > DLP events.
3. Click an event in the list to view more details about it.
The Event details pane expands to the right.

844 © Acronis International GmbH, 2003-2024

4. Scroll down and up in the Event details pane to view the available information.
The details that are displayed in the pane depend on the type of rule and rule settings that
triggered the event.

To filter events in the DLP events list

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Protection > DLP events.
3. In the upper left, click Filter.
4. Select sensitivity category, workload, action type, user, and channel from the drop-down menus.
You can select more than one item in the drop-down menus. Filtering applies the logical
operator OR between items in the same menu, but the logical operator AND is used between
items from different menus.
For example, if you select PHI and PII sensitivity category, the result will return all events that
contain PHI or PII, or both. If you select sensitivity category PHI and action Write access, only
events that match both categories will appear in the filtered result.
5. Click Apply.
6. To view all events again, click Filter, then Reset to default, and finally click Apply.

To search for events in the DLP events list

1. Repeat steps 1-2 from the procedure above.

2. From the drop-down list to the right of Filter, select a category in which you want to search:
Sender, Destination, Process, Message subject, or Reason.
3. In the text box, enter the phrase you are interested in and confirm by pressing Enter on the
keyboard.
Only events matching the phrase you entered appear in the list.
4. To reset the list of events, click the X sign in the search text box and press Enter.

To view the list of events related to specific rules in the data flow policy

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Protection > Data flow policy.
3. Select the check box in front of the name of the policy rule you are interested in.
You can select multiple policy rules if needed.
4. Click View events.
The view switches to Protection > DLP events and the events that are related to the policy rules
that you selected appear in the list.

Advanced Data Loss Prevention widgets on the Overview dashboard

The Overview dashboard provides a number of customizable widgets that give an overview of
operations related to the Cyber Protection service, including Advanced Data loss Prevention. You
can find the following Advanced Data Loss Prevention widgets on the Overview dashboard under
Monitoring.

845 © Acronis International GmbH, 2003-2024

l Sensitive data transfers - shows a total number of sensitive data transfer operations to internal
and external recipients. The chart is divided by the type of permission: allowed, justified or
blocked. You can customize this widget by selecting the desired time range (1 day, 7 days, 30
days, or this month).
l Outbound sensitive data categories - shows a total number of sensitive data transfers to
external recipients. The chart is divided by sensitive categories: Protected Health Information
(PHI), Personally Identifiable Information (PII), PCI DSS and Marked as Confidential (Confidential).
l Top senders of outbound sensitive data - shows a total number of sensitive data transfers
from the organization to external recipients and a list of the top five users with the largest
number of transfers (along with these numbers). This statistic includes both allowed and justified
transfers. You can customize this widget by selecting the desired time range (1 day, 7 days, 30
days, or this month).
l Top senders of blocked sensitive data transfers - shows a total number of blocked sensitive
data transfers and a list of the top five users with the largest number of attempted transfers
(along with these numbers). You can customize this widget by selecting the desired time range (1
day, 7 days, 30 days, or this month).
l Recent DLP events - shows details of recent Data loss prevention events for the selected time
range. You can customize this widget using the following options:
o Range (date posted) (1 day, 7 days, 30 days, or this month).
o Name of the workload
o Operation status (allowed, justified, or blocked)
o Sensitivity (PHI, PII, Confidential, PCI DSS)
o Destination type (external, internal)
o Grouping (workload, user, channel, destination type)

The widgets are updated every five minutes. The widgets have clickable elements that enable you to
investigate and troubleshoot issues. You can download the current state of the dashboard or send it
via email in the .pdf or/and .xlsx format.

Custom sensitivity categories

Custom sensitive data categories may help an organization to protect intellectual property and
confidential data specific for that organization by expanding Advanced DLP built-in catalog of
compliance regulatory-related content definitions.

To create custom sensitive category

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Protection > Data Loss Prevention > Data classifiers.
3. Select Sensitivity category.
4. You will see a list of sensitivities, both built-in (such as Protected health information or Personally
Identifiable Information) and custom ones.
5. Click Create Sensitivity in the top right corner of the window.
6. Enter its name in the next window.

846 © Acronis International GmbH, 2003-2024

 7. New custom sensitivities are always disabled by default. You can enable them once you
configure all their parameters.
8. After creating new sensitivity, you will need to set up its content detectors. Click an arrow to
expand the contents of your new sensitivity and select Add content detector.
9. In the next window you can either use any of the existing content detectors (by clicking the
checkmark next to their name and then clicking Add in the lower right corner) or define a new
one.
10. Instead of creating a new sensitivity from scratch you can also reuse existing one (either built-in
or existing custom sensitivity) by cloning it and adjusting its parameters.
l To clone an existing sensitivity, click a checkmark next to its name and then select Clone from
the Action drop down menu (indicated by an ellipsis) in the top left corner. You can select
multiple items at a time to clone more than one sensitivity.
l In the next window you can select which parameters of the existing sensitivity you wish to
retain by clicking the checkmarks next to each parameter.

Note
Copying of built-in sensitivities inside one tenant will create a new sensitivity that consists of
same detectors (they become Custom once copied)

To create new content detector

1. Log in to the Cyber Protect console as an administrator.

2. Navigate to Protection > Data Loss Prevention > Data classifiers.
3. Select Content detectors.
4. You will see a list of content detectors, both built-in and custom ones.
5. Click Create content detector in the top right corner of the window.
6. A drop-down menu will open, where you can select the type of detector you want to create – at
this point only File type content detector is available, more to come in the future updates.
7. In the following window you can configure the content detector.
Type of Description
content
detector

File type a. There are two lists: Supported file types and Selected file types. By clicking a
content “plus” icon to the right of the supported file type you will move it to the Selected file
detector types list. You can also select multiple supported file types by clicking on the
checkmarks next to their names and then using Add selected button in the top
right corner.
b. To remove a file type from the Selected file types list, click on a trashcan icon to the
right of its name. You can also remove multiple file types at once using checkmarks
and Remove selected button.

Keywords a. When creating new keywords content detector, you will need to import keywords
content from a file. After successful importing you can either merge new keywords with the

847 © Acronis International GmbH, 2003-2024

 Type of Description
content
detector

detector list of existing ones or replace the existing ones with imported keywords.
b. You also need to determine if you want the content detector to match all keywords
from the list, any keyword from the list or a custom number of keywords.

8. Instead of creating a new content detector from scratch you can also reuse an existing one
(either built-in or existing custom sensitivity) by cloning it and adjusting its parameters.
l To clone an existing content detector, click a checkmark next to its name and then select
Clone from the Action drop down menu (indicated by an ellipsis) in the top left corner. You
can select multiple items at a time to clone more than one content detector.

Note
Copying of built-in content detector causes the detector to become custom.

Organization map

Note
This functionality is accessible only to Company Administrator users.

The organization map is a databse that contains data for users and all their accounts used to
transfer data through instant messaging, email, or any other means, that have been intercepted by
Advanced DLP.

The organization map provides means to create and manage user groups in Advanced DLP, and to
manage users and accounts associated to users in Advanced DLP. User groups can then be used for
group-based DLP policy management.

To locate the Organization map

l In the Cyber Protect Cloud console, navigate to Protection > Data loss prevention >
Organization map.

How does it work?

Note
The organization map is populated while the Advanced DLP module operates in Observation mode.

For every data transfer intercepted by the DLP Agent, the following attributes are collected in the
back end.

848 © Acronis International GmbH, 2003-2024

 Attribute Description Label in
the UI

Organization A manually created group. The Organization unit can have one or more Group
Unit nested Organization Units. name, as
defined

Security ID A unique security identifier. On the user

details page
> SID

A user-friendly display name derived from the account names for the Name
user. This name is not always available in Organization map.

PC\UserName The name of the user of the endpoint (workload). User name
A user name can be assigned to only one Organization Unit.

Device The name of the endpoint (workload). Workload

(Workload)

Account Accounts that were used by a user for communication via instant Accounts
messaging and email, and have been intercepted by the DLP Agent. For
example, if the agent detects that username 'PC\John' uses
[email protected] to send an email - this account is linked to PC\John
user name.

In the organization map, you can view and search accounts, users, and groups, and create, edit, and
delete groups.

To search for specific accounts

As part of incident investigation, Administrator users might need to find the owner of a specific
account that was involved in a potential data breach.

1. In the Cyber Protect Cloud console, navigate to Protection > Data loss prevention >
Organization map.
2. In the Search text box above the users list, start typing or paste the account.
The list is filtered as you type.

To search for a specific user name

1. In the Cyber Protect Cloud console, navigate to Protection > Data loss prevention >
Organization map.
2. To search in a specific group, click the group name in the list.
3. In the Search text box above the users list, start typing or paste a user name.
The list is filtered as you type.

To view the accounts used by a particular user name

1. Locate the user in the users list.

2. Click the three dots at the end of the user row and select View.

849 © Acronis International GmbH, 2003-2024

3. In the user details dialog, locate the Associated accounts section.
4. You can add comments in the Description text box.

To create a user group

1. In the Cyber Protect Cloud console, navigate to Protection > Data loss prevention >
Organization map.
2. In the lower left section of the groups list, click Create group.
The Create organizational unit dialog opens.

3. From the Parent drop-down menu, select the context for the new group.

Note
You cannot change the parent later. The group will remain nested in this context.

4. Enter a group name and click Save.

To add a user to a group

1. In the Cyber Protect Cloud console, navigate to Protection > Data loss prevention >
Organization map.
2. In the users list, locate the user that you want to add and select the check box in the beginning of
the user row.
The Move selected and Delete selected buttons appear above the users list.

3. Click Move selected.

The Move user dialog opens.
4. Select a new parent for the selectet user and click Save.

Note
A user can belong to only one group.

To delete an account associated to a user

850 © Acronis International GmbH, 2003-2024

1. Locate the user in the users list.
2. Click the three dots at the end of the user row and select View.
3. In the user details dialog, locate the Associated accounts section.
4. Locate the account that you want to delete and click the three dots next to it.
5. From the drop-down list, select Delete.

To rename a user group

1. In the Cyber Protect Cloud console, navigate to Protection > Data loss prevention >
Organization map.
2. Click the three dots next to the name of the group and click Rename.

To delete a user group

1. In the Cyber Protect Cloud console, navigate to Protection > Data loss prevention >
Organization map.
2. Click the three dots next to the name of the group and click Delete.
All users from the goup are moved to the parent entity.

Known issues and limitations

l [DEVLOCK-4028] There is no control for the group chats in the Zoom desktop agent.
l [DEVLOCK-4016] Friendly name and sender ID doesn't captured for GMX Web Mail and Web.de
Mail in case of draft creation.
l [DEVLOCK-4447] There is no Justification dialog for naver.com WebMail in case of draft creation.
l [DEVLOCK-1033] DeviceLockDriver: potential bugcheck DRIVER_POWER_STATE_FAILURE caused
by a deadlock during IRP_MN_QUERY_DEVICE_RELATIONS processing.

Endpoint Detection and Response (EDR)

Note
This functionality is part of the Advanced Security + EDR protection pack, which in turn is part of the
Cyber Protection service. Note that when you add EDR functionality to a protection plan, you may
be subject to additional charges.

EDR detects suspicious activity on the workload, including attacks that have gone unnoticed. EDR
then generates incidents, which provide a step-by-step overview of each attack, helping you
understand how an attack happened and how to prevent it from happening again. With easy-to-
understand interpretations of each stage in the attack, the time spent on investigating attacks can
be reduced to a matter of minutes.

Why you need Endpoint Detection and Response (EDR)

In today's ever-expanding world of cyber threats and malicious attacks, prevention no longer
guarantees 100% protection. Some attacks will always make it through prevention layers and

851 © Acronis International GmbH, 2003-2024

successfully penetrate the network. Conventional solutions can’t see when this happens, leaving
attackers free to dwell in your environment for days, weeks, or months.

Existing EDR solutions do help prevent these "silent failures" by finding and removing attackers
quickly. However, they typically require a high level of security expertise or expensive Security
Operation Center (SOC) analysts, and analysis of incidents can be extremely time-consuming.

The Acronis Advanced Security + EDR functionality overcomes these limitations by detecting attacks
that have gone unnoticed, and helping you understand how an attack happened and how to
prevent it from happening again. In turn, this reduces the time spent on investigating attacks.

Here's why you need EDR:

l Full visibility: Understand what happened and how it happened, even for attacks that have gone
unnoticed. The evolution of each attack is also visually mapped out, step-by-step (from the initial
point of entry to viewing the data that was targeted and/or exfiltrated), enabling you to quickly
understand the scope and impact of an incident. For more information, see "How to investigate
incidents in the cyber kill chain" (p. 864).
l Minimize investigation time: Reduce incident investigation time from hours to just a matter of
minutes. EDR details each step of the attack in clear, easy-to-understand human language, in turn
helping reduce the need for expensive experts or additional headcount. For more information,
see "Investigating incidents" (p. 863)
l Check for known threats on your workloads: You can automatically search your workloads for
threats from malware, vulnerabilities, and other types of global events that may affect your data
protection. These threats are referred to as Incidents of Compromise (IOCs), and are based on
threat data received from the Cyber Protection Operations Center (CPOC). For more information,
see "Check for indicators of compromise (IOCs) from publicly known attacks on your workloads"
(p. 874).
l Respond faster to incidents: With access to all post-breach activities and a breakdown of each
step of the kill chain, you can perform a number of actions to remediate each attack point.
Among other things, you can investigate using remote control and forensic backup (this feature is
not available in the Early Access version), quarantine workloads, and kill malware processes. You
can also recover business operations using Cyber Disaster Recovery Cloud. For more information,
see "Remediating incidents" (p. 877).
l Report on your security posture with confidence: With EDR enabled, you can eliminate much
of the insecurity and fear of the impact cyber attacks can have on your business. In addition,
incident-related information is stored for 180 days, which can be used for auditing purposes.

Features
Endpoint Detection and Response (EDR) includes the following features:

l Receive alert notifications when a breach happens

l Manage your incidents in the Incident page

852 © Acronis International GmbH, 2003-2024

l Easy to understand visualization of the attack storyline
l Recommendations and remediation steps
l Check for publicly disclosed attacks on your workloads using threat feeds
l Quick glance overview in the dashboard
l Store security events for 180 days

Receive alert notifications when a breach happens

EDR provides alert notifications whenever an incident occurs. These alerts are highlighted in the
main menu of the Cyber Protect console. You can then investigate an alert by clicking the
Investigate incident button, which redirects you to the incident investigation screen (otherwise
known as the cyber kill chain).

For more information, see "Reviewing incidents" (p. 856).

Manage your incidents in the Incident page

EDR enables you to manage all your incidents in the Incidents page (accessed from the Protection
menu in the Cyber Protect console). The Incidents page, which can be filtered according to your
requirements, ensures you can quickly and easily understand the current status of your incidents,
including their severity, workload affected, and positivity level. You can also navigate directly to the
cyber kill chain to view the attack storyline, node-by-node.

For more information about the Incidents page, see "Reviewing incidents" (p. 856).

Easy to understand visualization of the attack storyline

EDR provides a visual representation of an attack in an easy readable format. This ensures that even
non-security personnel can digest the objectives and severity of any attack. There's really no need
for a Security Operation Center (SOC) service or to hire security experts; EDR details how exactly an
attack happened, including:

l How the attacker got in

l How the attacker hid their tracks
l What harm was caused
l How the attack spread

For more information, see "How to investigate incidents in the cyber kill chain" (p. 864).

Recommendations and remediation steps

EDR provides clear and easy to implement recommendations for resolving attacks on a workload.
To resolve an attack quickly, click the Remediate entire incident button to view and follow
recommended steps for mitigating the incident. These recommended steps enable you to rapidly
resume operations affected by an attack. However, if you want to take more granule remediation
steps, you can navigate to each node and remediate it with the relevant action.

For more information, see "Remediating incidents" (p. 877).

853 © Acronis International GmbH, 2003-2024

Check for publicly disclosed attacks on your workloads using threat feeds
EDR includes the ability to review existing, known attacks in threat feeds against your workloads.
These threat feeds are automatically generated based on threat data received from the Cyber
Protection Operations Center (CPOC); EDR enables you to verify whether or not a threat is impacting
your workload, and then take the necessary steps to nullify the threat.

For more information, see "Check for indicators of compromise (IOCs) from publicly known attacks
on your workloads" (p. 874).

Quick glance overview in the dashboard

EDR provides a range of statistics within the Cyber Protect console dashboard. You can view:

l The current threat status, including the number of incidents that need to be investigated.
l The evolution of attacks by severity, indicating possible attack campaigns.
l The efficiency rate of closing down incidents.
l The most targeted tactics used to attack your customers.
l The network status of the workload, meaning whether it is isolated or connected.

Store security events for 180 days

EDR collects workload and application events and stores them for 180 days. Events that pre-date the
180-day period are deleted (event deletion is based on age and not according to storage space).
Note that even when EDR is switched off, all previously collected events for a workload are retained,
and will be available for incident investigation.

Software requirements
Endpoint Detection and Response (EDR) supports the following operating systems:

l Microsoft Windows 7 Service Pack 1 and later

l Microsoft Windows Server 2008 R2 and later

Enabling Endpoint Detection and Response (EDR) functionality

You can enable EDR in any protection plan.

To enable EDR

1. In the Cyber Protect console, go to Management > Protection plans.

2. Select the relevant protection plan from the displayed list, and in the right sidebar, click Edit.
Alternatively, you can create a new protection plan and continue to the next step. For further
information about working with protection plans, see "Protection plans and modules" (p. 205).
3. In the protection plan sidebar, enable the Endpoint Detection and Response (EDR) module by
clicking the switch next to the module name.

854 © Acronis International GmbH, 2003-2024

4. In the displayed dialog, click Enable. Note that when EDR is enabled, other protection modules
are also enabled, as shown in the displayed dialog.

Note
If any one of Active protection, Behavior engine, Exploit prevention, or URL filtering are
switched Off, Endpoint Detection and Response (EDR) is also switched Off.

5. The Advanced Security + EDR pack icon, as shown below, is added to the list of protection
packs required for the implementation of the protection plan, depending on additional packs
you select.

855 © Acronis International GmbH, 2003-2024

How to use Endpoint Detection and Response (EDR)
EDR enables you to detect attacks that have gone unnoticed, while helping you understand how an
attack happened and how to prevent it from happening again. With easy-to-understand
interpretations of each stage in the attack, the time spent on investigating attacks can be reduced to
a matter of minutes.

The table below describes the general workflow when working with EDR. Initially, you will review and
prioritize any new incidents, investigate them further in the cyber kill chain, and then take the
relevant remediation actions.

Step How to use EDR

STEP 1: Review In the EDR incident list:

incidents
l Understand the security posture of an organization: how many incidents need to
be investigated?
l Understand which are the most critical incidents, and prioritize their investigation
according to their severity.
l Understand which incidents are new or ongoing.

STEP 2: In the EDR cyber kill chain:

Investigate
l Understand the objectives of the attacker and view the attack techniques used.
incidents
l Verify how likely any incident is a true malicious attack.
l Verify whether or not a threat feed is impacting your workload.
l See what response actions have already been applied to an incident.

STEP 3: In the relevant EDR remediation sections:

Remediate
l Quickly and easily remediate an entire incident by applying global response
incidents
actions.
l Remediate individual attack points within an incident.
l Apply actions to prevent the attack (or future attacks) from spreading or affecting
workloads that have not yet been targeted by the attacker.

Reviewing incidents
Endpoint Detection and Response (EDR) provides an incident list that includes both prevention (or
malware) and suspicious detections on a workload. The incident list gives you a quick-glance
overview of any attacks or threats that are affecting your workloads, including threats that are yet to
be mitigated.

From the incident list, you can quickly determine:

l The security posture of an organization: how many incidents need to be investigated?

l Which are the most critical incidents, and prioritize their investigation according to their severity.

856 © Acronis International GmbH, 2003-2024

l Which incidents are new or ongoing.

Note
When logged in as a partner administrator, you can view all EDR incidents in a single screen that
consolidates incidents from all your customers, without the need to access each customer's
individual incident view. An additional Customers column is displayed, which includes the customer
name each incident belongs to. In addition, the widgets shown on the Overview dashboard display
metrics data aggregated across all customers.

The incident list, as shown below, is accessed from the Protection menu in the Cyber Protect
console. For further information about reviewing the incidents in the incident list, see "Viewing
which incidents are currently not mitigated" (p. 859) To learn more about when an incident is
created, see What exactly are incidents?.

Note
If Managed Detection and Response (MDR) is enabled on your workloads, an additional MDR ticket
column is displayed. This column display the ticket number provided by the MDR vendor.

Note
The Cyber Protect console must be open in order for you to receive incident notifications.

What exactly are incidents?

Incidents, or security incidents, can be thought of as containers of at least one prevention or
suspicious detection point (or a mix), and include all the related events and detections of a single
attack. These security incidents can also include additional benign events that give further context
into what happened.

This enables you to view attack events together in one single incident, and understand the logical
steps that the attacker performed. In addition, it helps speed up the investigation time for an attack.

When EDR is enabled in the protection plan, security incidents are created when:

857 © Acronis International GmbH, 2003-2024

l A prevention layer stops something: These incidents are automatically closed by the system,
according to the protection plan settings. However, you can investigate what exactly the malware
did before it was stopped. For example, ransomware is stopped when it starts to encrypt files, but
prior to that it could have stolen credentials or installed a service.
l Suspicious activity is detected by EDR: These are detections that should be investigated and
remediated. By reviewing the visually enhanced cyber kill chain (for more information, see "How
to investigate incidents in the cyber kill chain" (p. 864)), you can easily apply the relevant
remediation actions.

Prioritize which incidents need immediate attention

The Cyber Protect console incident list can be accessed at any time from the Protection menu in
the Cyber Protect console. The incident list gives you a quick-glance overview of any attacks or
threats, enabling you to prioritize incidents that require attention.

Important
To ensure your workloads remain secure, always analyze and prioritize the incidents that are
ongoing or not mitigated.

How to analyze which security incidents need immediate attention

The incident list enables you to analyze and prioritize the listed incidents that require attention. You
can:

l View which incidents are currently not mitigated: Quickly understand from the incident list if any
attacks are currently in progress. Any incidents that are not mitigated, as indicated in the Threat
status column, should be looked at immediately (by default, the incident list is filtered to display
these incidents).
l Understand the scope and impact of incidents: Based on your filtering of newly opened or
ongoing attacks, understand the severity for the filtered incidents as well as the impact on your
business.

Once you have a refined list of the most important incidents, you can then analyze incident details
to get a better understanding of a specific incident , as well as the techniques used by the attacker
to achieve their objective. For more information, see "Analyze incident details" (p. 861).

858 © Acronis International GmbH, 2003-2024

Note
By default, the incident list is sorted according to the Updated column, which details the date and
time the incident was last updated with new detections recorded inside the incident. Note that any
existing incident can be updated at any time, even if the incident was previously closed. You can
also filter the list to show newly opened or ongoing attacks according to your requirements, as
described in the procedure below.

To filter the incident list

1. At the top of the Incident list, click Filter to filter the displayed list of incidents. For example, if
you select a start and end date in the Created field, the incident list and widgets display the
relevant incidents created during the defined time period.

2. When done, click Apply.

Viewing which incidents are currently not mitigated

You can view the current threat status for incidents in the Threat status column, which shows if the
incident is Mitigated or Not mitigated. The threat status is automatically defined by EDR; any
incident that is not mitigated should be investigated as soon as possible.

You can then refine the displayed incident list further by applying filters. For example, if you want to
filter the list according to threat status and a specific level of severity, select the relevant filter

859 © Acronis International GmbH, 2003-2024

options. Once you have filtered the incidents that are of interest to you, you can then investigate
them, as described in "Investigating incidents" (p. 863).

You can also use the Threat status widget, as shown below, for a quick glance overview of the
current threat status. Note that the data displayed in this widget reflects the filters you applied; see
"To filter the incident list" (p. 859).

Understanding the scope and impact of incidents

You can quickly understand the scope and impact of incidents by reviewing the Severity, Attack
info, and Positivity level columns. As mentioned above, after you have determined which incidents
are currently in progress you can then filter these additional columns to do the following:

l Review which incidents are more critical in the Severity column. The severity of an incident can
be one of Critical, High, or Medium.
o Critical: There is a severe risk of malicious cyber activity with the risk of compromising critical
hosts in your environment.
o High: There is a high risk of malicious cyber activity with the risk of severe damage in your
environment.
o Medium: There is an increased risk of malicious cyber activity.

Note
When determining the severity, the EDR algorithm takes into consideration the workload type
as well as the scope of each step of the attack. For example, an incident which includes steps
related to credential theft is set to Critical.

l Understand why an incident was created in the Incident type column. The incident type can
include any one or more of the following:
o Ransomware detected
o Malware detected
o Suspicious process detected
o Malicious process detected
o Suspicious URL blocked
o Malicious URL blocked

860 © Acronis International GmbH, 2003-2024

l Determine which attack techniques are in use in the Attack info column, and understand if there
is a common theme or pattern to the attacks.
l Confirm how likely an incident is a true malicious attack; the Positivity level column includes a
score of between 1-10 (the higher the score, the more likely the attack is a true malicious attack).

After you have found the incidents that need immediate attention, you can then investigate them,
as described in "Investigating incidents" (p. 863)

You can also use the Severity history and Detection by tactics widgets for a quick glance
overview of the severity and attack techniques.

The Detection by tactics widget displays the various attack techniques used, with values in green
or red indicating the increase or decrease over the previous specified time range. This widget
provides an aggregated view of all the objectives in the filtered incidents, giving you a quick
overview of the impact on your customers.

Analyze incident details

During the incident review stage, you can also analyze the details of each incident from the Endpoint
Detection and Response (EDR) incident list. These details enable you to drill-down into the entire

861 © Acronis International GmbH, 2003-2024

incident and understand how and when it occurred. In addition, you can assign an incident to
specific users for investigation, and set the investigation status.

To analyze incident details

1. In the Cyber Protect console, go to Protection > Incidents. The Incident list is displayed.
2. Click on the incident you want to review. The details for the selected incident are displayed.
3. In the displayed Overview tab, you can review the incident and workload details, including the
current threat status and severity. You can also define the Investigation state (select from one
of Investigating, Not started (the default state), False positive, or Closed), and select a user to
assign the incident to (in the Assignee drop-down list, select the relevant user).

4. Click the Attack Info tab to review details of the attack and the techniques used in the attack.
Click the link next to each listed attack technique to review further information about the
technique on MITRE.org.
5. Click the Activities tab to review any action taken in the cyber kill chain to mitigate an incident.
For more information, see "How to investigate incidents in the cyber kill chain" (p. 864).
For example, if a patch was run on the workload, you can see who initiated the patch, how long it
took, and any errors that occurred during the implementation of the patch.

862 © Acronis International GmbH, 2003-2024

6. Click Investigate incident to access the cyber kill chain where you can investigate the incident
node-by-node. For more information, see "How to investigate incidents in the cyber kill chain" (p.
864).

Investigating incidents
Endpoint Detection and Response (EDR) enables you to investigate an entire incident, including all of
the attack stages and objects (processes, registries, scheduled tasks, and domains) impacted by an
attack. These objects are represented by nodes in the easy-to-understand cyber kill chain, as shown
below. Use the cyber kill chain to quickly understand what exactly happened, and when it
happened.

Each and every step of an attack is viewed in the cyber kill chain, which provides you with a detailed
interpretation of how and why the incident happened. The cyber kill chain uses easy to understand
sentences and graphs that help explain each step of the attack, in turn helping to minimize
investigation time.

You can quickly understand the scope and impact of an incident, with the attack evolution mapped
to the MITRE framework. This enables you to analyze what happened in each step of an attack,
including:

l The initial point of entry

l How the attack was executed
l Any escalations of privileges
l Avoidance detection techniques
l Lateral movements to other workloads
l Credential theft
l Exfiltration attempts

863 © Acronis International GmbH, 2003-2024

Note
Each object impacted in the attack, whether it is a process, registry, scheduled task or domain, is
represented by a node in the cyber kill chain.

How to investigate incidents in the cyber kill chain

You can investigate each and every step of an attack in the cyber kill chain. Follow the cyber kill
chain's easy to comprehend sentences and graphs to understand each step of the attack, which in
turn help you to minimize investigation time.

To begin an investigation in the cyber kill chain

1. In the Cyber Protect console, go to Protection > Incidents.

2. In the displayed list of incidents, click in the far right column of the incident you want to
investigate. The cyber kill chain for the selected incident is displayed.

3. View a summary of the incident in the threat status bar at the top of the page. The threat status
bar includes the following information:
l Current threat status: The threat status is automatically defined by the system. Any incident
that is Not mitigated should be investigated as soon as possible.

864 © Acronis International GmbH, 2003-2024

 Important
An incident is set to Mitigated when a restore from backup has been successfully completed
or when all detections have been successfully remediated by a stop process, quarantine, or
rollback action.

An incident is set to Not mitigated when a restore from backup has not been successfully
completed or when at least one detection has not been successfully remediated by a stop
process, quarantine, or rollback action.

You can also manually set the threat status to Mitigated or Not mitigated. When selecting
either status, you are prompted to enter a comment. This comment is saved as part of the
investigation activities, and can be viewed in the Activities tab. Note that EDR can still revert
the threat status to Mitigated or Not mitigated if new detections were discovered for the
incident or response actions were run and were completed successfully.

l Incident severity: Critical, High, or Medium. For more information, see "Reviewing incidents"
(p. 856).
l Current investigation state: One of Investigating, Not started (the default state), False
positive, or Closed. You should change the state when you start investigating the incident so
that other colleagues are aware of any changes to the incident.
l Positivity level: Indicates how likely an incident is a true malicious attack, between a range of
1-10. For more information, see "Reviewing incidents" (p. 856).
l Incident type: One or more of Ransomware detected, Malware detected, Suspicious
process detected, Malicious process detected, Suspicious URL blocked, and Malicious
URL blocked.
l If Managed Detection and Response (MDR) is enabled on the workload, an MDR ticket field is
displayed. You can view details of the MDR ticket created for the incident, and the MDR
security analyst assigned to the incident.

l When the incident was created and updated: Date and time the incident was detected, or
when the incident was last updated with new detections recorded inside the incident.

865 © Acronis International GmbH, 2003-2024

4. Click the Legend tab to view the various nodes that make up the kill chain graph, and define
which nodes to view. For further information, see "Understanding and customizing the cyber kill
chain view" (p. 866).
5. Investigate and remediate the incident by performing the following steps. Note that this is the
typical workflow for investigating and remediating an incident, but may vary according to each
incident and your own requirements.
a. Investigate each stage of the attack in the Attack stages tab. For further information, see
"How to navigate attack stages" (p. 869).
b. Click Remediate entire incident to apply remediation actions. For further information, see
"Remediate an entire incident" (p. 877).
You can also remediate individual nodes in the cyber kill chain, as described in "Response
actions for individual cyber kill chain nodes" (p. 882).
c. Review actions taken to mitigate the incident in the Activities tab. For further information,
see "Understand the actions taken to mitigate an incident" (p. 872).

Understanding and customizing the cyber kill chain view

To understand the nodes impacted in the cyber kill chain, access the legend. The legend displays all
of the nodes involved in an incident, enabling you to understand how the various nodes have been
impacted by the attacker. You can also define the nodes you want to hide or display in the cyber kill
chain.

To access the legend

1. Click the arrow icon to the right of the Legend section.

The Legend section expands, as shown below.

866 © Acronis International GmbH, 2003-2024

2. There are four main colors used in the legend, which enable you to quickly understand what
happened to each node in the cyber kill chain, as shown below. These color-coded nodes are
also included in the attack stages, as described in "How to navigate attack stages" (p. 869).

To hide or display nodes in the cyber kill chain

1. In the expanded Legend section, ensure is displayed next to the nodes you want to display in
the cyber kill chain. If the displayed icon is , click the icon to change it to .
2. To hide a node in the cyber kill chain, click . The icon changes to and the node is not
displayed in the cyber kill chain.

Investigate the attack stages of an incident

The attack stages of an incident provide easy to understand interpretations of every incident.

Each attack stage summarizes what exactly happened, and what were the objects (referred to as
nodes in the cyber kill chain) targeted. For example, if a downloaded file was masquerading as
something else, the attack stage will indicate this, and include links to the relevant node in the cyber
kill chain which you can investigate, and to the relevant MITRE ATT&CK technique.

867 © Acronis International GmbH, 2003-2024

Each stage of the attack provides you with the information you need to resolve three crucial
questions:

l What was the attacker's objective?

l How did the attacker achieve this objective?
l Which nodes were targeted?

More importantly, the interpretation provided ensures the time spent on investigating an incident is
greatly reduced, as you no longer need to go through each security event from a timeline or graph
node and then try to create an interpretation of the attack.

The attack stages also include information about compromised files that contain sensitive
information, such as credit card numbers and social security numbers, as shown in the Collection
stage in the example below.

For more information, see "What information is included in an attack stage?" (p. 869).

868 © Acronis International GmbH, 2003-2024

How to navigate attack stages
Attack stages are listed in chronological order. Scroll down to see the complete list of attack stages
for the incident.

To investigate a specific attack stage further, click anywhere in the attack stage to navigate to the
relevant node in the cyber kill chain graph. For more information about navigating the cyber kill
chain graph and specific nodes, see "Investigate individual nodes in the cyber kill chain" (p. 870).

What information is included in an attack stage?

Each attack stage provides an easy to understand interpretation of the attack, in easily readable
human language. This interpretation is composed of a number of elements, as shown below and
described in the following table.

Attack stage element Description

Header Describes what the attacker tried to do, and

their objective (in the example above,
Credential Access), with a link to a known
MITRE ATT&CK technique. Click the link to
learn more on the MITRE ATT&CK website.

Note
If an attack stage is not a known MITRE
ATT&CK technique, the header text won't be
linked. This is relevant for generic
techniques such as files detected in a
random folder.

Timestamp The time the attack stage occurred.

Technique How the attacker technically achieved their

objective, and what objects (registry entries,
files, or scheduled tasks) were affected.

Included in the text description of the attack

869 © Acronis International GmbH, 2003-2024

 Attack stage element Description

technique are color-coded links to each

affected node in the cyber kill chain, as
shown in the example above. These color-
coded links enable you to navigate quickly to
the affected node and to investigate what
exactly happened. The colors used in an
attack stage indicate the following:

Looking at the above legend, we can see that

the Credential Access example attack stage
has a link to a malware node
and a suspicious file node (click on the
links to jump to the corresponding node in
the cyber kill chain). For more information
about navigating these nodes and the
actions available, see "Investigate individual
nodes in the cyber kill chain" (p. 870).

Note that attack stages also include links to

file nodes that have information about
compromised files which contain sensitive
information, such as protected health
information (PHI), credit card numbers and
social security numbers.

Note
Each attack stage is a single detection event. The content listed in each stage (header, timestamp,
technique) is generated according to specific parameters in the detection event, and which are
based on attack stage templates stored by Endpoint Detection and Response (EDR).

Investigate individual nodes in the cyber kill chain

In addition to reviewing the attack stages, you can also navigate through each of the attack nodes in
the cyber kill chain. This enables you to drill-down to specific nodes in the cyber kill chain and to
investigate and remediate each node as required.

For example, you can determine how likely an incident is a true malicious attack. Based on your
investigation, you can also apply a number of response actions to the node, including isolate a
workload or quarantine a suspicious file.

To investigate individual nodes in the cyber kill chain

870 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Protection > Incidents.

2. In the displayed list of incidents, click in the far right column of the incident you want to
investigate. The cyber kill chain for the selected incident is displayed.
3. Navigate to the relevant node, and click it to display the sidebar for the node.

Note
Click the node to expand it and display associated nodes.

For example. clicking the powershell.exe node in the example below opens the sidebar for the
node. You can also click the arrow icon next to the node to view the associated nodes, including
files and registry values, that may be affected by the powershell.exe node. In turn, you can click
on these associated nodes to investigate further.

4. Investigate the information included in the sidebar tabs:

l Overview: Includes two main sections that provide a security summary of the attacked node.
o Security analysis: Provides an analysis of the attacked node, including the EDR verdict on
the threat (such as suspicious activity), the objective of the attack according to MITRE attack
techniques (click on the link to go to the MITRE website), the reason for detection, and the
number of workloads that may be affected by the attack (click the n Workloads link to view
the affected workloads).

Note
The n Workloads link means that the specific malicious or suspicious object has been
found on other workloads. It does not mean that the attack is happening on these other
workloads, but that there is an indicator of compromise on these other workloads. The
attack may have already happened (and created another incident), or the attacker is
preparing to hit these other workloads using their attack "toolkit".

o Details: Includes details about the node, including its type, name and current state, path to
the node, and any file hashes and digital signatures (such as MD5 and certificate serial
numbers).
l Scripting Activities: Includes details of any scripts invoked or loaded in the attack. Click to
copy the script to your clipboard for further investigation.

871 © Acronis International GmbH, 2003-2024

 Note
The Scripting Activities tab is only displayed for process nodes that run commands or
scripts (such as cmd or PowerShell commands).

l Response Actions: Includes a number of sections that provide additional investigation,

remediation and prevention actions, depending on the node type.
For example, for workload nodes, you can define a number of responses that include a
forensic backup and a restore from backup. Alternatively, for malicious or suspicious nodes,
you can stop or quarantine the node, rollback changes made by the attack, and add it to a
protection plan allowlist or blocklist.
For more information about applying response actions to specific nodes, see "Response
actions for individual cyber kill chain nodes" (p. 882).
l Activities: Displays the actions applied to the incident in chronological order. For more
information, see "Understand the actions taken to mitigate an incident" (p. 872).

Understand the actions taken to mitigate an incident

After you have reviewed an incident and investigated how the attack occurred, you will typically
apply response actions. Once you have applied response actions, these actions can be viewed in a
number of places to get a better understanding of what steps have been taken to mitigate the
incident.

Note
Incidents created by prevention layers automatically apply the actions configured in the protection
plan. For detection points, you need to define the relevant response actions to mitigate each attack
scenario.

To understand the response actions taken, you can view all the response actions applied to an
entire incident, or view the actions applied to a specific node in the incident cyber kill chain.

To view all response actions applied to an incident

1. In the Cyber Protect console, go to Protection > Incidents.

2. In the displayed list of incidents, click in the far right column of the incident you want to
investigate. The cyber kill chain for the selected incident is displayed.
3. Click the Activities tab.
The list of response actions already applied to the incident is displayed.

872 © Acronis International GmbH, 2003-2024

4. You can perform a number of actions on the displayed list:
l Click on an activity type row to display more information about the selected activity. The
information is displayed in a sidebar, as shown in Step 3, and includes details on who initiated
the action, its status, file path, and any comments added by the initiator.
l Use the Search box to search for a specific action.
l Click Filter to apply filters to the list.
l Select the Group by impacted entity check box to group relevant actions according to entity.

l
Click to show / hide the list of completed actions.
Ensure is displayed next to the actions you want to display. If you want to hide an action
from the displayed list, click again to change it to .

To view response actions applied to a specific node

873 © Acronis International GmbH, 2003-2024

1. In the cyber kill chain, click on a node to view the sidebar for that node.
2. Click the Activities tab.

3. To get a complete understanding of what actions were applied and why, you may need to scroll
through the applied response actions for the node. For example, for remote desktop connection
actions, you can view who started the action and when, the duration of the action, and its overall
status (if it succeeded, failed, or succeeded with errors).

Check for indicators of compromise (IOCs) from publicly known attacks on your
workloads
Endpoint Detection and Response (EDR) includes the ability to review existing, known attacks in
threat feeds against your workloads. These threat feeds are automatically generated based on
threat data received from the Cyber Protection Operations Center (CPOC); EDR enables you to verify
whether or not a threat is impacting your workload, and then take the necessary steps to nullify the
threat.

You can access threat feeds from the Monitoring menu in the Cyber Protect console. For more
information, see "Threat feed" (p. 288).

To review specific threat details and confirm if they impact your workloads, click on a threat feed.
You can view the number of IOCs detected and workloads affected, and drilldown to workloads that
contain unmitigated IOCs.

Note
If the protection plan does not have EDR enabled, this additional threat feed functionality, as shown
below, is not displayed.

874 © Acronis International GmbH, 2003-2024

Define threat feed settings
You can define a number of threat feed settings to automatically locate and mitigate any known
threats.

To define threat feed settings

1. In the Cyber Protect console, go to Monitoring > Threat feed.

2. On the displayed Threat feed page, click Settings.
3. In the displayed dialog, select any of the following options:
Option Description

Search for indicators of compromise Click the switch to enable the automatic search for IOCs on
(IOCs) your workloads.
When this option is enabled, the Action on detection and
Generate alert options are also displayed.

Action on detection From the dropdown list, select the action to be taken on the
relevant files when a threat is discovered on a workload:
l No action
l Quarantine
l Delete
l Isolate workloads

Generate alert Select the checkbox to generate an alert if an IOC is found on

a workload. The alert will be displayed in the Alerts page.

4. Click Apply.

Review and mitigate IOCs on affected workloads

When Endpoint Detection and Response (EDR) is enabled in a protection plan, you can view any
known threats that are affecting workloads in the protection plan. You can also mitigate any

875 © Acronis International GmbH, 2003-2024

remaining indicators of compromise (IOCs) that were not automatically mitigated. For information
on how to automatically mitigate IOCs, see "Define threat feed settings" (p. 875).

To review and mitigate affected workloads

1. In the Cyber Protect console, go to Monitoring > Threat feed.

2. Click on a thread to display the details for that threat.
3. In the Indicators of compromise (IOCs) prevalence section, click the n workloads link to view
the workloads with unmitigated IOCs.

4. In the displayed Workloads page, click on the relevant workload and review its details. You can
run specific functionality on the workload, including defining additional URLs to filter (see "URL
filtering" (p. 805)), and blocking malicious processes (refer to the Exclusions section in "Antivirus
and antimalware protection settings" (p. 783)).
For example, if a threat feed indicates that a workload has been affected by an IOC, first locate
and analyze the IOC, as described in "Review and analyze discovered IOCs" (p. 876). Then go to
the protection plan for the workload and define additional protection, such as blocking malicious
file hashes or processes.

Review and analyze discovered IOCs

In addition to reviewing any workloads affected by known threats, you can also review and analyze
specific indicators of compromise (IOCs). This enables you to view the individual workloads that are
affected by an IOC, and mitigate the IOC.

To review and analyze IOCs

1. In the Cyber Protect console, go to Monitoring > Threat feed.

2. Click on a thread to display the details for that threat.
3. In the Indicators of compromise (IOCs) prevalence section, click the Total IOCs found link.
The Found indicators page is displayed.

876 © Acronis International GmbH, 2003-2024

4. (Optional) Use the Filter option to filter the list of IOCs according to their status. You can also use
the Search option to search for specific IOCs.
5. To view the workload affected by an IOC, click the link in the Workload column. You can then
perform a variety of actions on the workload, such as run patch management, or modify a
protection plan.
6. (Optional) In the File hash column, click Show to display the file hashes found for a specific IOC.
In the displayed dialog, click to copy the file hash of the IOC to a text editor.

Remediating incidents
Endpoint Detection and Response (EDR) enables you to remediate entire incidents, or the individual
attack points of an incident.

By remediating an entire incident, you can choose the remediation(s) that you want to execute
globally on the incident. If you need to manage the incident in more granular detail, you can
remediate individual attack points as required. For example, you may want to isolate the network of
a workload to stop lateral movement or command and control (C&C) activities; this ensures that
even though the workload is isolated, all Acronis Cyber Protect technologies are still functional and
an investigation can be launched.

EDR ensures effective remediation by:

l Mitigating - to ensure the threat is stopped.

l Recovering - to ensure services are back online immediately.
l Preventing - to ensure techniques used in an attack are prevented in future attacks.

Remediate an entire incident

By remediating an entire incident, you can quickly and easily choose the remediation(s) that you
want to execute globally on the incident. Endpoint Detection and Response (EDR) guides you
through the remediation process, step by step.

877 © Acronis International GmbH, 2003-2024

If you need to manage your network and the incident in more granular detail, see "Response actions
for individual cyber kill chain nodes" (p. 882).

To remediate an entire incident

1. In the Cyber Protect console, go to Protection > Incidents.

2. In the displayed list of incidents, click in the far right column of the incident you want to
investigate. The cyber kill chain for the selected incident is displayed.
3. Click Remediate entire incident. The Remediate entire incident dialog is displayed.

4. In the Analyst verdict section, based on your investigation of the incident, select one of the
following:

878 © Acronis International GmbH, 2003-2024

 l True positive: Select if you are sure the attack is a legitimate attack. Once selected, you then
add remediation and prevention actions, as described in the following steps.
l False positive: Select if you are sure the attack is not a genuine attack. In this mode, you can
define how to prevent this from happening again, such as by adding the incident to a
protection plan allowlist.

Note
After selecting False positive, you can only define prevention actions. For more information,
see "Remediate a false positive incident" (p. 881).

5. In the Remediation actions section, perform the following remediation steps. Note that they
must be performed in sequential order; for example, you cannot select Step 2 before Step 1 is
completed.
a. Step 1 - Stop threats: Select the check box to stop all processes related to the threat.
b. Step 2 - Quarantine threats: Once the threat is stopped, select the check box to quarantine
all malicious and suspicious processes and files.
c. Step 3 - Rollback changes: After threats have been quarantined, select the check box to
delete any new registry entries, scheduled tasks or files created by the threat (and any of its
children threats). The rollback process then reverts any modifications made by the threat (or
its children) to the registry, scheduled tasks and/or files existing on the workload prior to the
attack. To optimize speed, the rollback process tries to recover items from the local cache.
Items that fail to be recovered will be recovered by the system from backup images.

Note
The rollback process recovers from items in the local cache only. Rollback from backup
archives will be available in future releases.

Select the Allow this response action to access encrypted backups using your stored
credentials check box if access to the relevant backups is encrypted. EDR accesses the
stored user credentials to decrypt the encrypted archives and search for the relevant files.
You can also click Affected items to view all items (files, registry, or scheduled tasks) affected
by the rollback, the actions applied (Delete, Recover, or None), and if the items are being
restored from the local cache or backup images.

879 © Acronis International GmbH, 2003-2024

 d. Recover workload: Select the check box to recover a workload if any of the above
remediation steps fail, whether completely or partially.

Select one of the following recovery options:

l Recover workload from backup: Enables you to recover a workload from a specific
recovery point. Click the recovery point edit icon to select from a list of recovery backups.
l Disaster recovery failover: Enables you to run disaster recovery, if you have this
functionality enabled in your protection plan. We recommend that you use this option for
critical workloads, such as AD servers, or database servers. For more information, see
"Implementing disaster recovery" (p. 698).
6. In the Prevention actions section, select the relevant remediation steps:
l Add to blocklist: Select the check box and from the displayed protection plan list, select the
relevant protection plans. This prevention action ensures all detections of the incident will be
blocked from being executed for the selected protection plans.
l Patch workload: Select the check box to patch any vulnerable software and prevent attackers
from gaining access to the workload. You can then select the relevant action to perform once
the patch is complete (Do not restart, Restart, or Restart only if required), depending if the
user is logged in or not.
You can also select the Do not restart while backup is in progress check box to ensure the
workload is not restarted during backup.

880 © Acronis International GmbH, 2003-2024

7. Select the Change investigation state of the incident to: Closed check box. If not selected,
the investigation state remains in its previous state.
8. Click Remediate. The remediation actions you selected are executed, step by step, with the
progress of each remediation step shown in the Remediate entire incident dialog.
Once clicked, the button displays Go to activities. Click Go to activities to review all response
actions applied to the incident. For more information, see "Understand the actions taken to
mitigate an incident" (p. 872).

Remediate a false positive incident

If you are sure an attack is not a genuine attack, in other words a false positive, you can define how
to prevent the incident from happening again. For example, you can add the incident to a protection
plan allowlist.

To remediate a false positive incident

1. In the cyber kill chain for the selected incident, click Remediate entire incident. The Remediate
entire incident dialog is displayed.

881 © Acronis International GmbH, 2003-2024

2. In the Analyst verdict section, select False positive.

3. In the Prevention actions section, select the Add to allowlist check box. From the displayed
protection plan list, select the relevant protection plans.
This prevention action ensures all detections of the incident will be prevented from being
detected for the selected protection plans.
4. Select the Change investigation state of the incident to: False positive check box.
5. Click Remediate.
Once clicked, the button displays Go to activities. Click Go to activities to review the response
actions applied to the incident. For more information, see "Understand the actions taken to
mitigate an incident" (p. 872).

Response actions for individual cyber kill chain nodes

If you need to manage the incident in more granular detail, you can apply various response actions
to individual cyber kill chain nodes. These response actions enable you to quickly and easily
remediate any node.

Note
To apply global response actions to an entire incident, see "Remediate an entire incident" (p. 877).

Response actions are divided into the following categories, although not all nodes include all of the
following categories:

882 © Acronis International GmbH, 2003-2024

l Remediate: Actions in this category enable you to apply an immediate response to the attack,
and include managing network isolation for a workload, and the deletion and quarantining of
files, processes, and registry values.
l Investigate: Actions in this category (applicable to workloads only) enable you to run a Forensic
backup, or remote desktop connection for a more in-depth investigation.
l Investigate: Actions in this category (applicable to workloads only) enable you to run a remote
desktop connection for a more in-depth investigation.
l Recovery: Actions in this category (applicable to workloads only) enable you to respond to
intensive attacks by running a recovery from backup, or Disaster Recovery failover.
l Prevent: Actions in this category enable you to prevent future threats or false positives by adding
them to a protection plan allowlist or blocklist.

Note
If an incident is closed, you cannot apply a response action to a node. However, you can reopen a
closed incident by changing its investigation state to Investigating. When reopened, you can then
apply response actions.

The following table describes each of the node types in the cyber kill chain, the applicable categories
for each node, and the response actions available.

Node Category Response

Actions

Workload Remediate l Manage

network
isolation
l Restart
workload

Investigate l Forensic
backup
l Remote
desktop
connection

Investigate l Remote
desktop
connection

Recovery l Recovery
from backup
l Disaster
Recovery
failover

Prevent l Patch

883 © Acronis International GmbH, 2003-2024

 Node Category Response
Actions

Process Remediate l Stop process

l Quarantine

Prevent l Add to
allowlist
l Add to
blocklist

File Remediate l Delete

l Quarantine

Prevent l Add to
allowlist
l Add to
blocklist

Registry Remediate l Delete

Network Prevent l Add to

allowlist
l Add to
blocklist

Define response actions for an affected workload

As part of your response to an attack, you can apply the following actions to affected workloads:

l Manage network isolation: Enables you to manage the network isolation of a workload to stop
lateral movement or Command and Control (C&C) activities. For more information, see "Manage
the network isolation of a workload" (p. 885).
l Patch: Enables you to patch a workload to prevent future vulnerability exploitations in future
potential attacks. For more information, see "Patch a workload" (p. 888).
l Restart workload: Enables you to immediately restart a workload, or restart the workload
according to a predefined timeout period. For more information, see "Restart a workload" (p.
889).
l Forensic backup: Enables you to do an on-demand forensic backup for audit or further
investigation purposes. For more information, see "Run an on-demand forensic backup on a
workload" (p. 890).
l Remote desktop connection: Enables you to remotely access the workload under investigation.
For more information, see "Remote connection to a workload" (p. 891).
l Recovery from backup: Enables you to recover your entire machine from backup or specific files
or folders. For more information, see "Recovery from backup" (p. 892).

884 © Acronis International GmbH, 2003-2024

l Disaster Recovery failover: Enables you to run "Implementing disaster recovery" (p. 698). Note
that your workload must have a subscription for Advanced Disaster Recovery. For more
information, see "Disaster Recovery failover" (p. 893).

Manage the network isolation of a workload

EDR enables you to manage the network isolation of a workload to stop lateral movement or
Command and Control (C&C) activities. There are a number of isolation options to choose from,
according to your requirements. Note that all Acronis Cyber Protect technologies are functional
even if a workload is isolated, ensuring that an investigation can be fully carried out.

To isolate a workload from the network

1. In the cyber kill chain, click the workload node you want to remediate.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Remediate section, click Manage network isolation.

Note
The Network Status value indicates if the workload is currently connected or not. If the value
displays Isolated, you can reconnect the isolated workload to the network, as described in the
procedure below. If the workload is offline you can still isolate the workload; when the workload
goes back online it is automatically put into the Isolated state.

4. In the Immediate action after isolation drop-down list, select from one of:
l Isolate only
l Isolate and backup workload
l Isolate and backup workload with forensic data
l Isolate and power off workload

885 © Acronis International GmbH, 2003-2024

 For more information about defining where to backup the workload and encryption options, see
"Managing the backup and recovery of workloads and files" (p. 378).
5. [Optional] In the Message to display field, add a message to display to end users when they
access the isolated workload. For example, you can inform users that the workload is now
isolated and that network access in and out of the workload is currently not available. Note that
this message is also displayed as a tray monitor notification, and remains displayed until the
user dismisses the message.
6. [Optional] In the Comment field, add a comment. This comment is visible in the Activities tab
(for a single node or the entire incident), and can help you (or your colleagues) recall why you
took the action when you revisit the incident.
7. Click Manage network exclusions to add ports, URLs, host names, and IP addresses that will
have access to the workload during the isolation. For more information, see how to manage
network exclusions.
8. Click Isolate.
The workload is isolated. This action can also be viewed in the Activities tabs of both the
individual node and the entire incident. For more information, see "Understand the actions
taken to mitigate an incident" (p. 872).

Note
The workload is also shown as Isolated under the Workloads menu in the Cyber Protect
console. You can also isolate single or multiple workloads from the Workloads > Workloads
with agents menu; select the relevant workload(s) and in the right sidebar select Manage
network isolation. In the displayed dialog, you can manage network exclusions and click
Isolate or Isolate all to isolate the selected workload(s).

To connect an isolated workload back to the network

1. In the cyber kill chain, click the workload node you want to reconnect.

Note
If the isolated workload is currently offline you can still reconnect it back to the network; when
the workload goes back online it is automatically put into the Connected state.

2. In the displayed sidebar, click the Response Actions tab.

3. In the Remediate section, click Manage network isolation.
4. Select from one of the following:
l Connect to network immediately: The workload is reconnected to the network.
l Recover workload from backup before connecting to network: Select a recovery point
from which to recover the workload.
a. In the Recovery point field, click Select.
b. In the displayed sidebar, select the relevant recovery point.
c. Click Recover > Entire workload to recover all the files and folders on the workload.
Or

886 © Acronis International GmbH, 2003-2024

 Click Recover > Files/folders to recover specific files and folders on the workload. You are
then prompted to select the relevant files or folders. Once selected, you can view the list of
items by clicking the relevant value in the Items to be recovered field.

Note
If the recovery point you select is encrypted, you will be prompted for the password.

5. [Optional] Select the Automatically restart the workload if required check box. This option is
relevant only if you selected Recover > Entire workload in Step 4.
6. [Optional] In the Message to display field, add a message to display to end users when they
access the connected workload. For example, you can inform users that a backup was restored
to the workload and that network access in and out of the workload is resumed.
7. [Optional] In the Comment field, add a comment. This comment is visible in the Activities tab
(for a single node or the entire incident), and can help you (or your colleagues) recall why you
took the action when you revisit the incident.
8. Click Connect if you selected Connect to network immediately in Step 4.
Or
Click Recover and connect if you selected Recover workload from backup before
connecting to network in Step 4.
The workload is reconnected to the network and all network access to the workload is no longer
restricted.

887 © Acronis International GmbH, 2003-2024

 Note
You can also connect single or multiple isolated workloads from the Workloads > Workloads
with agents menu in the Cyber Protect console; select the relevant workload(s) and in the right
sidebar select Manage network isolation. In the displayed dialog, click Connect or Connect all
to reconnect the selected workload(s) to the network.

To manage network exclusions

Note
Even if all Acronis Cyber Protect technologies are working when the workload is in isolation, there
may be scenarios in which you need additional network connections to be established (for example,
you may need to upload a file from the workload to a shared directory). In these scenarios, you can
add a network exclusion, but make sure any threats are removed before you add the exclusion.

1. In the Remediate section of the Response actions tab, click Manage network exclusions.
2. In the Network exclusions sidebar, add the relevant exclusions. For each of the options available
(Ports, URL address, and Hostname / IP address), do the following:
a. Click Add and then enter the relevant port(s), URL addresses, or Hostname / IP addresses.
b. In the Traffic direction drop-down list, select one of Incoming and outgoing connections,
Incoming connections only, or Outgoing connections only.
c. Click Add.
3. Click Save.

Patch a workload
EDR automatically detects if a workload requires a patch, and enables you to patch the workload to
prevent vulnerability exploitations in future potential attacks. Note that this feature is available only
if the partner's workload has a subscription for Advanced Management.

To patch a workload

1. In the cyber kill chain, click the workload node you want to patch.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Remediate section, click Patch.
4. In the Patches to install field, click Select. In the displayed dialog, select the relevant patches
and then click Select.
5. In the Post-installation options field, click the displayed link. The Post-installation options
dialog is displayed.

888 © Acronis International GmbH, 2003-2024

6. Select the action to perform after the patch is installed:
l If user is logged out: Select one of Do not restart, Restart, or Restart only if required.
l If user is logged in: Select one of Do not restart, Restart, or Restart only if required.
When you select Restart, you can also define the following:
o Schedule the restart.
o Allow snoozing, including the defined intervals between snoozes.
7. [Optional] Select the Do not restart while backup is in progress check box to ensure the
workload is not restarted if a backup is currently in progress.
8. Click Save.
9. In the Response Actions tab, click Patch.
The selected patch is run. This action can also be viewed in the Activities tabs of both the
individual node and the entire incident. For more information, see "Understand the actions
taken to mitigate an incident" (p. 872).

Restart a workload
As part of your remediation response to an attack, EDR enables you to immediately restart a
workload, or restart the workload according to a predefined timeout period.

To restart a workload

1. In the cyber kill chain, click the workload node you want to set a restart schedule for.
2. In the displayed sidebar, click the Response Actions tab.

889 © Acronis International GmbH, 2003-2024

3. In the Remediate section, click Restart workload.

4. In the Restart timeout field, click the displayed link, and then select one of the following:
l Set timeout: In the Restart timeout dialog, set the restart period for the workload, and then
click Save.
l Restart immediately: Select to restart the workload immediately.
5. [Optional] Select the Fail if end-user is logged in check box to ensure the workload is not
restarted if the user is logged in.
6. In the Message to display field, add a message to display to users when they access the isolated
workload.
7. [Optional] In the Comment field, add a comment. This comment is visible in the Activities tab
(for a single node or the entire incident), and can help you (or your colleagues) recall why you
took the action when you revisit the incident.
8. Click Restart.
The workload is set to restart according to the schedule defined. This action can also be viewed
in the Activities tabs of both the individual node and the entire incident. For more information,
see "Understand the actions taken to mitigate an incident" (p. 872).

Run an on-demand forensic backup on a workload

As part of your investigation into an attack, EDR enables you to run an on-demand forensic backup
for audit or further investigation purposes. Note that this feature is available only if the partner's
workload has a subscription for Advanced Backup.

To run a forensic backup

890 © Acronis International GmbH, 2003-2024

1. In the cyber kill chain, click the workload node you want to run a forensic backup on.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Investigate section, click Forensic backup.

4. [Optional] In the Backup name field, click the edit icon to edit the backup name.
5. In the Forensic options field, click the displayed link. In the displayed Forensic options dialog,
select one of the following:
l Collect raw memory dump
l Collect kernel memory dump
You can also select the Snapshot of running processes check box to add information about the
processes running at the moment the backup starts. This information is stored in a backup
image.
Click Save to close the Forensic options dialog.
6. In the Where to back up field, click the displayed link to define a location for the backup.
7. [Optional] Click the Encryption option to enable encryption. In the displayed dialog, enter the
password for the encrypted backup and select the relevant encryption algorithm.
8. [Optional] In the Comment field, add a comment. This comment is visible in the Activities tab
(for a single node or the entire incident), and can help you (or your colleagues) recall why you
took the action when you revisit the incident.
9. Click Run.
The forensic backup is started. This action can also be viewed in the Activities tabs of both the
individual node and the entire incident. For more information, see "Understand the actions
taken to mitigate an incident" (p. 872).

Remote connection to a workload

As part of your investigation into an attack, EDR enables you to remotely access the workload under
investigation.

To remotely connect to a workload

891 © Acronis International GmbH, 2003-2024

1. In the cyber kill chain, click the workload node you want to remotely connect to.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Investigate section, click Remote desktop connection.

4. Select one of the following remote connection methods:

l Connect via RDP client: This method will prompt you to download and install the Remote
Desktop Connection Client. You can then remotely connect to a workload from the Cyber
Protect console.
l Connect via Web client: This method does not require the installation of an RDP client on
your workload. You are redirected to the login screen where your credentials to the remote
machine have to be entered.
When the remote connection is started, this action can be viewed in the Activities tabs of both
the individual node and the entire incident. For more information, see "Understand the actions
taken to mitigate an incident" (p. 872).

Recovery from backup

As part of your recovery response to an attack, EDR enables you to recover your entire machine
from backup or specific files or folders.

To recover your workload from backup

1. In the cyber kill chain, click the workload node you want to recover.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Recovery section, click Recover from backup.

4. In the Recovery point field, click Select and then perform the following steps:
a. In the displayed sidebar, select the relevant recovery point.
b. Click Recover > Entire workload to recover all the files and folders on the workload.
Or

892 © Acronis International GmbH, 2003-2024

 Click Recover > Files/folders to recover specific files and folders on the workload. You are
then prompted to select the relevant files or folders. Once selected, you can view the items
selected for recovery by clicking the relevant value in the Items to be recovered field.

Note
If the recovery point you select is encrypted, you will be prompted for the password.

5. [Optional] Select the Automatically restart the workload check box. This option is relevant
only if you selected Recover > Entire workload in Step 4.
6. [Optional] In the Comment field, add a comment. This comment is visible in the Activities tab
(for a single node or the entire incident), and can help you (or your colleagues) recall why you
took the action when you revisit the incident.
7. Click Start recovery.
The process to recover the workload starts. The progress for this action can be viewed in the
Activities tabs of both the individual node and the entire incident. For more information, see
"Understand the actions taken to mitigate an incident" (p. 872).

Disaster Recovery failover

As part of your recovery response to an attack, EDR enables you to run "Implementing disaster
recovery" (p. 698), which allows you to switch the workload to the recovery server. Note that your
workload must have a subscription for Advanced Disaster Recovery.

To run Disaster Recovery failover

1. In the cyber kill chain, click the workload node you want to recover.
2. In the displayed sidebar, click the Response Actions tab.

893 © Acronis International GmbH, 2003-2024

3. In the Recovery section, click Disaster Recovery failover.

4. In the Recovery point field, perform the following steps:

a. Click the current recovery point date to select a recovery point.
b. In the displayed sidebar, select the relevant recovery point.

Note
If you have an Advanced Disaster Recovery subscription, you can select the relevant recovery
server (the offline VM) created in Disaster Recovery. If you do not have a subscription, you will be
prompted to configure Disaster Recovery.

5. [Optional] In the Comment field, add a comment. This comment is visible in the Activities tab
(for a single node or the entire incident), and can help you (or your colleagues) recall why you
took the action when you revisit the incident.
6. Click Failover.
The workload is switched to the recovery server. This action can be viewed in the Activities tabs
of both the individual node and the entire incident. For more information, see "Understand the
actions taken to mitigate an incident" (p. 872).

Define response actions for a suspicious process

As part of your remediation response to an attack, you can apply the following actions to suspicious
processes:

l Stop a process (see below)

l Quarantine a process (see below)
l Roll back changes made by a process (see below)

894 © Acronis International GmbH, 2003-2024

l Add the process to a protection plan allowlist or blocklist (see "Add or remove a process, file or
network in the protection plan blocklist or allowlist" (p. 900))

To stop a suspicious process

1. In the cyber kill chain, click the process node you want to remediate.

Note
Windows critical processes or non-running processes cannot be stopped and are disabled in the
cyber kill chain.

2. In the displayed sidebar, click the Response Actions tab.

3. In the Remediate section, click Stop process.

4. Select one of the following:

l Stop process (stops the specific process)
l Stop process tree (stops the specific process and all child processes)
5. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.
6. Click Stop.The process is stopped.

Note
The related application is closed and any unsaved data will be lost.

This action can also be viewed in the Activities tabs of both the individual node and the entire
incident. For more information, see "Understand the actions taken to mitigate an incident" (p.
872).

To quarantine a suspicious process

1. In the cyber kill chain, click the process node you want to quarantine.

Note
Windows critical processes cannot be quarantined and are disabled in the cyber kill chain.

895 © Acronis International GmbH, 2003-2024

2. In the displayed sidebar, click the Response Actions tab.
3. In the Remediate section, click Quarantine.

4. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.
5. Click Quarantine.The process is stopped and then quarantined.

Note
The process is added to and managed in the quarantine section available under antimalware
protection.

This action can also be viewed in the Activities tabs of both the individual node and the entire
incident. For more information, see "Understand the actions taken to mitigate an incident" (p.
872).

To rollback changes

1. In the cyber kill chain, click the process node you want to rollback changes for.

Note
This action is available for detection nodes (shown as red or yellow nodes) only.

2. In the displayed sidebar, click the Response Actions tab.

896 © Acronis International GmbH, 2003-2024

3. In the Remediate section, click Rollback changes.

Note
The rollback process recovers from items in the local cache only. Rollback from backup archives
will be available in future releases.

4. To view the items affected by the rollback changes, click the Affected items link. The displayed
dialog shows all items (files, registry, scheduled tasks) that the rollback will revert and with what
action (Delete, Recover, or None). In addition, you can see whether the restored items will be
recovered from the local cache or backup recovery points.

897 © Acronis International GmbH, 2003-2024

5. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.
6. Click Rollback. The rollback functionality reverts any registry, file or scheduled task changes
made by the process in the following steps:
a. Any new entries (registry, scheduled tasks, files) created by the threat (and its child threats)
are deleted.
b. Any modifications that the threat (and its child threats) made to the registry, scheduled tasks
and/or files existing on the workload prior to the attack are reverted.
c. Rollback tries to recover items from the local cache. For items that cannot be recovered, EDR
will automatically recover them from clean backup images.
The rollback action can also be viewed in the Activities tabs of both the individual node and the
entire incident. For more information, see "Understand the actions taken to mitigate an incident"
(p. 872).

Define response actions for a suspicious file

As part of your remediation response to an attack, you can apply the following actions to suspicious
files:

l Delete a file (see below)

l Quarantine a file (see below)
l Add the file to a protection plan allowlist or blocklist (see "Add or remove a process, file or
network in the protection plan blocklist or allowlist" (p. 900))

To delete a suspicious file

1. In the cyber kill chain, click the file node you want to remediate.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Remediate section, click Delete.

4. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.

898 © Acronis International GmbH, 2003-2024

5. Click Delete.
The file is deleted. This action can also be viewed in the Activities tabs of both the individual
node and the entire incident. For more information, see "Understand the actions taken to
mitigate an incident" (p. 872).

To quarantine a suspicious file

1. In the cyber kill chain, click the file node you want to remediate.
2. In the displayed sidebar, go to Response Actions.
3. In the Remediate section, click Quarantine.

4. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.
5. Click Quarantine.
The file is quarantined. This action can also be viewed in the Activities tabs of both the
individual node and the entire incident. For more information, see "Understand the actions
taken to mitigate an incident" (p. 872).

Define response actions for a suspicious registry entry

As part of your remediation response to an attack, you can delete suspicious registry entries.

This option is available for registry cyber kill chain nodes.

To delete a suspicious registry entry

1. In the cyber kill chain, click the node you want to remediate.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Remediate section, click Delete.

899 © Acronis International GmbH, 2003-2024

4. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.
5. Click Delete.
The registry entry is deleted. This action can also be viewed in the Activities tabs of both the
individual node and the entire incident. For more information, see "Understand the actions
taken to mitigate an incident" (p. 872).

Add or remove a process, file or network in the protection plan blocklist or allowlist
As part of your prevention response to an attack, you can add a node to your protection plan
allowlist or blocklist.

You can add a node to an allowlist if you consider the node safe and want to prevent any future
detections for it. Add a node to a blocklist to stop the node from running in the future.

You can also remove a node from the allowlist or blocklist to allow or prevent any future access to
the node.

This option is available for the following cyber kill chain nodes:

l Process
l File
l Network

To add or remove a process, file or network in the protection plan blocklist

1. In the cyber kill chain, click the process, file, or network node you want to remediate.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Prevent section, click the arrow icon next to Blocklist.

4. Select the relevant protection plan(s) you want to apply this action to.

900 © Acronis International GmbH, 2003-2024

5. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.
6. Click Add.
The action is implemented, and the process, file, or network will be prevented from launching in
the future.
Alternatively, if the process, file, or network was previously added to the blocklist and you now
want to remove it from the blocklist, click Remove. This will allow future access to the node.
The add or remove action can also be viewed in the Activities tabs of both the individual node
and the entire incident. For more information, see "Understand the actions taken to mitigate an
incident" (p. 872).

To add or remove a process, file or network in the protection plan allowlist

1. In the cyber kill chain, click the process, file, or network node you want to remediate.
2. In the displayed sidebar, click the Response Actions tab.
3. In the Prevent section, click the arrow icon next to Allowlist.

4. Select the relevant protection plan(s) you want to apply this action to.
5. [Optional] Add a comment. This comment is visible in the Activities tab (for a single node or the
entire incident), and can help you (or your colleagues) recall why you took the action when you
revisit the incident.
6. Click Add.
The action is implemented and the process, file, or network will be prevented from detection in
the future.
Alternatively, if the process, file, or network was previously added to the allowlist and you now
want to remove it from the allowlist, click Remove. This will prevent any future access to the
node.

901 © Acronis International GmbH, 2003-2024

 The add or remove action can also be viewed in the Activities tabs of both the individual node
and the entire incident. For more information, see "Understand the actions taken to mitigate an
incident" (p. 872).

Enabling monitoring mode for Endpoint Detection and Response

(EDR)
The monitoring mode in Cyber Protection enables you to use EDR in a production environment. In
turn, this enables you to check for any false positives, and make necessary exclusions before fully
deploying EDR.

In monitoring mode, nothing is blocked or stopped, and incidents are created, but no responses are
initiated.

To enable the monitoring mode for EDR

1. In the relevant protection plan, ensure that EDR is enabled. For more information, see "Enabling
Endpoint Detection and Response (EDR) functionality" (p. 854).
2. Expand the Antivirus & Antimalware protection module, and then define the following:
l Click Active protection, and in the Action on detection section, select Notify only. Then
click Done. For more information, see "Active Protection" (p. 783).

l Click Behavior engine, and in the Action on detection section, select Notify only. Then click
Done. For more information, see "Behavior-engine" (p. 788).
l Click Exploit prevention, and in the Action on detection section, select Notify only. Then
click Done. For more information, see "Exploit prevention" (p. 789).

902 © Acronis International GmbH, 2003-2024

 l Click Real-time protection, and in the Action on detection section, select Notify only. Then
click Done. For more information, see "Real-time protection" (p. 790).
l Click Schedule scan, and in the Action on detection section, select Notify only. Then click
Done. For more information, see "Schedule scan" (p. 791).
3. Expand the URL filtering module, and in the Access to malicious website drop-down list,
select Notify only. Then click Done. For more information, see "URL filtering" (p. 805).

How to test if Endpoint Detection and Response (EDR) is working

correctly
To ensure EDR is deployed and working, you can run a number of commands that trigger EDR
detections.

Note
When EDR is deployed, you should see incidents immediately if any suspicious activity occurs. The
steps below enable you to check if EDR is working if no new incidents were triggered for several
days.

To test if EDR is deployed and working correctly

1. Login to the relevant domain-joined Active Directory user account.

2. Run the following two commands in Windows PowerShell:
l net group "Domain Computers" /domain
l net user administrator /domain
3. In the Cyber Protect console, go to Protection > Incidents to view the generated incident.
You can also click on the triggered Medium severity type incident to display it in the EDR cyber
kill chain and confirm the PowerShell commands you executed in the previous step, as shown in
the example below.

903 © Acronis International GmbH, 2003-2024

4. Run the following commands in Windows PowerShell:
l c:\>whoami
l c:\>net localgroup
l c:\>net localgroup administrators
l c:\>powershell -command start-process cmd -verb runas
l c:\WINDOWS\system32>net user administrator /active:yes
l c:\>powershell -command Get-Hotfix
5. In the EDR cyber kill chain, click on the executable nodes (for example, net.exe or whoami.exe)
to display the exact PowerShell commands executed on the command line. These commands
are shown in the Details section of the Overview tab in the example below.

6. After you have confirmed that an EDR incident was generated, manually set the Threat status
for the incident to Mitigated and the Investigation state to Closed. For more information, see
"How to investigate incidents in the cyber kill chain" (p. 864). You can also enter a comment for
the incident to indicate that this was a test incident.

904 © Acronis International GmbH, 2003-2024

Assessing vulnerabilities and managing patches
Vulnerability assessment (VA) is a process of identifying, quantifying, and prioritizing
vulnerabilities found in the system. In the vulnerability assessment module, you can scan your
machines for vulnerabilities, and check if the operating systems and installed applications are up to
date and working properly.

Vulnerability assessment scanning is supported for machines with the following operating systems:

l Windows. For more information, see "Supported Microsoft and third-party products" (p. 905).
l macOS. For more information, see "Supported Apple and third-party products" (p. 907).
l Linux (CentOS 7/Virtuozzo/Acronis Cyber Infrastructure) machines. For more information, see
"Supported Linux products" (p. 908).

Use the Patch management (PM) functionality to manage patches (updates) for applications and
operating systems installed on your machines, and keep your systems up to date. In the patch
management module, you can automatically or manually approve update installations on your
machines.

Patch management is supported for machines with the Windows operating systems. For more
information, see "Supported Microsoft and third-party products" (p. 905).

Vulnerability assessment
The vulnerability assessment process consists of the following steps:

1. You create a protection plan with the enabled vulnerability assessment module, specify the
Vulnerability assessment settings, and assign the plan to machines.
2. The system, by schedule or on demand, sends a command to run the vulnerability assessment
scanning to the protection agents installed on machines.
3. The agents get the command, start scanning machines for vulnerabilities, and generate the
scanning activity.
4. After the vulnerability assessment scanning is completed, the agents generate the results and
send them to the monitoring service.
5. The monitoring service processes the data from the agents and shows the results in the
vulnerability assessment widgets and list of found vulnerabilities.
6. When you get a list of found vulnerabilities, you can process it and decide which of the found
vulnerabilities must be fixed.

You can monitor the results of the vulnerability assessment scanning in Monitoring> Overview >
Vulnerabilities / Existing vulnerabilities widgets.

Supported Microsoft and third-party products

The following Microsoft products and third-party products for Windows operating systems are
supported for vulnerability assessment and patch management:

905 © Acronis International GmbH, 2003-2024

Supported Microsoft products
Windows OS

l Windows 7 (Enterprise, Professional, Ultimate)

l Windows 8
l Windows 8.1
l Windows 10
l Windows 11

Windows Server OS

l Windows Server 2022

l Windows Server 2019
l Windows Server 2016
l Windows Server 2012 R2
l Windows Server 2012
l Windows Server 2008 R2

Microsoft Office and related components

l Microsoft Office 2019 (x64, x86)

l Microsoft Office 2016 (x64, x86)
l Microsoft Office 2013 (x64, x86)
l Microsoft Office 2010 (x64, x86)

Windows OS related components

l Internet Explorer
l Microsoft EDGE
l Windows Media Player
l .NET Framework
l Visual Studio and Applications
l Components of operating system

Server applications

l Microsoft SQL Server 2008 R2

l Microsoft SQL Server 2012
l Microsoft SQL Server 2014
l Microsoft SQL Server 2016
l Microsoft SQL Server 2017
l Microsoft SQL Server 2019
l Microsoft Exchange Server 2013
l Microsoft Exchange Server 2016

906 © Acronis International GmbH, 2003-2024

l Microsoft Exchange Server 2019
l Microsoft SharePoint Server 2016
l Microsoft SharePoint Server 2019

Supported third-party products for Windows OS

Remote work becomes more and more wide-spread across the world, therefore collaboration and
communication tools, VPN clients are now important to be always up-to-date and checked on
possible vulnerabilities. The Cyber Protection service supports the vulnerability assessment and
patch management for such applications.

Collaboration and communication tools, VPN clients

l Microsoft Teams
l Zoom
l Skype
l Slack
l Webex
l NordVPN
l TeamViewer

For more information about the supported third-party products for Windows OS, refer to List of
third-party products supported by Patch Management (62853).

Supported Apple and third-party products

The following Apple products and third-party products for macOS are supported for vulnerability
assessment:

Supported Apple products

macOS

l macOS 10.13.x and later

macOS built-in applications

l Safari, iTunes, and others.

Supported third-party products for macOS

l Microsoft Office (Word, Excel, PowerPoint, Outlook, OneNote)
l Adobe Acrobat Reader
l Google Chrome
l Firefox
l Opera
l Zoom

907 © Acronis International GmbH, 2003-2024

l Skype
l Thunderbird
l VLC media player

Supported Linux products

The following Linux distributions and versions are supported for VA:

l Virtuozzo 7.x
l CentOS 7.x
l CentOS 8.x

Vulnerability assessment settings

To learn how to create a protection plan with the Vulnerability assessment module, refer to
"Creating a protection plan". You can perform VA scanning by schedule or on demand (by using the
Run now action in a protection plan).

You can specify the following settings in the Vulnerability assessment module.

What to scan
Define which software products you want to scan for vulnerabilities:

l Windows machines:
o Microsoft products
o Windows third-party products (for more information about the supported third-party
products for Windows OS, refer to List of third-party products supported by Patch
Management (62853))
l macOS machines:
o Apple products
o macOS third-party products
l Linux machines:
o Scan Linux packages

Schedule
Define the schedule according to which to perform the vulnerability assessment scan on the
selected machines:

Field Description

Schedule the This setting defines when the task will run.
task run using
The following values are available:
the following
events l Schedule by time – This is the default setting. The task will run
according to the specified time.

908 © Acronis International GmbH, 2003-2024

 Field Description

l When user logs in to the system – By default, a login of any user will
trigger the task. You can modify this setting so that only a specific user
account can trigger the task.
l When user logs off the system – By default, a logoff of any user will
trigger the task. You can modify this setting so that only a specific user
account can trigger the task.

Note
The task will not run at system shutdown. Shutting down and logging
off are different events in the scheduling configuration.

l On the system startup – The task will run when the operating system
starts.
l On the system shutdown – The task will run when the operating
system shuts down.

Schedule type The field appears if in Schedule the task run using the following
events you have selected Schedule by time.

The following values are available:

l Monthly – Select the months and the weeks or days of the month
when the task will run.
l Daily – This is the default setting. Select the days of the week when the
task will run.
l Hourly – Select the days of the week, repetition number, and the time
interval in which the task will run.

Start at The field appears if in Schedule the task run using the following
events you have selected Schedule by time

Select the exact time when the task will run.

Run within a The field appears if, in Schedule the task run using the following
date range events, you have selected Schedule by time.

Set a range in which the configured schedule will be effective.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs in to the system.
login to the
The following values are available:
operating
system will l Any user - Use this option if you want the login of any user to trigger
initiate a task the task.
l The following user - Use this option if you want only the login of a
specific user account to trigger the task.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs off the system.

909 © Acronis International GmbH, 2003-2024

 Field Description

logout from the The following values are available:

operating
l Any user - Use this option if you want the logout of any user to trigger
system will
the task.
initiate a task
l The following user - Use this option if you want only the logout of a
specific user account to trigger the task.

Start conditions Defines all conditions that must be met simultaneously for the task to
run.

Start conditions for antimalware scans are similar to the start conditions
for the Backup module that are described in "Start conditions".

You can define the following additional start conditions:

l Distribute task start time within a time window – This option

allows you to set the time frame for the task in order to avoid network
bottlenecks. You can specify the delay in hours or minutes. For
example, if the default start time is 10:00 AM and the delay is 60
minutes, then the task will start between 10:00 AM and 11:00 AM.
l If the machine is turned off, run missed tasks at the machine
startup
l Prevent the sleep or hibernate mode during task running – This
option is effective only for machines running Windows.
l If start conditions are not met, run the task anyway after –
Specify the period after which the task will run, regardless of the other
start conditions.

Note
Start conditions are not supported for Linux.

Vulnerability assessment for Windows machines

You can scan Windows machines and third-party products for Windows for vulnerabilities.

To configure the vulnerability assessment for Windows machines

1. In the Cyber Protect console, create a protection plan and enable the Vulnerability assessment
module.
2. Specify the vulnerability assessment settings:
l What to scan – select Microsoft products, Windows third-party products, or both.
l Schedule – define the schedule for performing the vulnerability assessment.
For more information about the Schedule options, see "Vulnerability assessment settings" (p.
908).
3. Assign the plan to the Windows machines.

910 © Acronis International GmbH, 2003-2024

After a vulnerability assessment scan, you can see a list of found vulnerabilities. You can process the
information and decide which of the found vulnerabilities must be fixed.

To monitor the results of the vulnerability assessment, see the Monitoring > Overview >
Vulnerabilities / Existing vulnerabilities widgets.

Vulnerability assessment for Linux machines

You can scan Linux machines for application-level and kernel-level vulnerabilities.

To configure the vulnerability assessment for Linux machines

1. In the Cyber Protect console, create a protection plan and enable the Vulnerability assessment
module.
2. Specify the vulnerability assessment settings:
l What to scan – select Scan Linux packages.
l Schedule – define the schedule for performing the vulnerability assessment.
For more information about the Schedule options, see "Vulnerability assessment settings" (p.
908).
3. Assign the plan to the Linux machines.

After a vulnerability assessment scan, you can see a list of found vulnerabilities. You can process the
information and decide which of the found vulnerabilities must be fixed.

To monitor the results of the vulnerability assessment, see the Monitoring > Overview >
Vulnerabilities / Existing vulnerabilities widgets.

Vulnerability assessment for macOS devices

You can scan macOS devices for operating system-level and application-level vulnerabilities.

To configure the vulnerability assessment for macOS devices

1. In the Cyber Protect console, create a protection plan and enable the Vulnerability assessment
module.
2. Specify the vulnerability assessment settings:
l What to scan – select Apple products, macOS third-party products, or both.
l Schedule – define the schedule for performing the vulnerability assessment.
For more information about the Schedule options, see "Vulnerability assessment settings" (p.
908).
3. Assign the plan to the macOS devices.

After a vulnerability assessment scan, you can see a list of found vulnerabilities. You can process the
information and decide which of the found vulnerabilities must be fixed.

To monitor the results of the vulnerability assessment, see the Monitoring > Overview >
Vulnerabilities / Existing vulnerabilities widgets.

911 © Acronis International GmbH, 2003-2024

Managing found vulnerabilities
If the vulnerability assessment was performed at least once and some vulnerabilities were found,
you can see them in Software management > Vulnerabilities. The list of vulnerabilities shows
both vulnerabilities that have patches to be installed, and those that do not have suggested patches.
You can use the filter to show only vulnerabilities with patches.

Name Description

Name The name of vulnerability.

Affected Software products for which the vulnerabilities were found.

products

Machines The number of affected machines.

Severity The severity of found vulnerability. The following levels can be assigned according to the
Common Vulnerability Scoring System (CVSS):

l Critical: 9 - 10 CVSS
l High: 7 - 9 CVSS
l Medium: 3 - 7 CVSS
l Low: 0 - 3 CVSS
l None

Patches The number of appropriate patches.

Published The date and time when the vulnerability was published in Common Vulnerabilities and
Exposures (CVE).

Detected The first date when an existing vulnerability was detected on machines.

You can find the description of found vulnerability by clicking its name in the list.

To start the vulnerability remediation process

912 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Software management > Vulnerabilities.
2. Select the vulnerability in the list, and then click Install patches. The vulnerability remediation
wizard will open.
3. Select the patches to be installed on the selected machines, and then click Next.
4. Select the machines on which you want to install the patches.
5. Select the reboot options.
a. Select if you want the machine to be rebooted after the patches are installed.

Option Description

No The machines will not be rebooted automatically after the patches are
installed.

If required The machines will be rebooted only if it is required for applying the
patches.

Yes The machines will be rebooted automatically after the patches are
installed. You can also specify a reboot delay.

b. [Optional] If you want to delay the machine reboot while a backup of the machine is in
progress, select Do not reboot until backup is finished.
6. Click Install patches.

As a result, the selected patches are installed on the selected machines.

Patch management
Note
The availability of this feature depends on the service quotas that are enabled for your account.

For more information about the supported third-party products for Windows OS, refer to List of
third-party products supported by Patch Management (62853).

Use the patch management functionality to:

l install OS-level and application-level updates

l approve patches manually or automatically
l install patches on-demand or according to a schedule
l precisely define which patches to install by different criteria: severity, category, and approval
status
l perform pre-update backup to prevent possible unsuccessful updates
l define the reboot action after patch installation

Note
To work with Windows updates, the patch management feature requires that Windows updates are
enabled on the workload.

913 © Acronis International GmbH, 2003-2024

Cyber Protection introduces peer-to-peer technology to minimize network bandwidth traffic. You
can choose one or more dedicated agents that will download updates from the Internet and
distribute them among other agents in the network. All agents will also share updates with each
other as peer-to-peer agents.

The patch management workflow

The patch management workflow includes steps for configuring and applying a protection plan,
running a vulnerability assessment scan, configuring patch settings, approving patches and finally,
installing patches that are approved. The exact steps of the workflow are as follows.

1. Configure a protection plan that has the Vulnerability assessment and Patch management
modules enabled.
2. Configure the vulnerability assessment settings. For more information about these settings, see
"Vulnerability assessment settings" (p. 908).
3. Configure the patch management settings. For more information about these settings, see
"Patch management settings in the protection plan" (p. 914)
4. Apply the protection plan to one or several machines.
5. Wait for a vulnerability assessment scan to be completed. The scan will start automatically,
according to the schedule that is configured in the protection plan. Alternatively, you can
manually start the scan on demand by clicking the Run now icon in the Vulnerability
assessment module in the protection plan.
6. Approve the patches. You can define settings for automatic patch approval, which include an
automatic installation of the patches on test machines. For more information, see "Automatic
patch approval" (p. 921). Alternatively, you can manually approve patches by setting their
approval status to Approved. For more information, see "Approving patches manually" (p. 926).
7. Install the patches. The approved patches can be installed automatically, according to the
schedule that is configured in the protection plan. Alternatively, you can manually install patches
on demand. For more information, see "Installing patches on demand" (p. 926).

You can monitor the results of the patch installation in Monitoring> Overview > Patch
installation history widget.

Patch management settings in the protection plan

In the Patch management module of the protection plan, you can configure the following patch
management settings:

l What updates to install for Microsoft and third-party products for Windows OS.
l When to run the automatic patch installation.
l Whether to run a pre-update backup.

For more information about creating a protection plan and enabling the Patch management
module, see "Creating a protection plan" (p. 206).

914 © Acronis International GmbH, 2003-2024

Note
The availability of this feature depends on the service quotas that are enabled for your account.

Microsoft products
To install the Microsoft updates on the selected machines, enable the Update Microsoft products
option.

Select the installation option:

Option Description

All updates Use this option if you want to install all approved updates.

Only Security and Critical Use this option if you want to install all approved security
updates and critical updates.

Updates of specific products Use this option if you want to define custom settings for
(Automatic patch approval different products.
and testing)
If you want to update specific products, for each product
you can define which updates to install by category, severity,
or approval status.

If you want to configure automatic test approval and testing

of the patches, select this option.

For Microsoft products, patch distribution uses the Windows API service. Patches and updates are
not downloaded or stored internally or on distribution agents. Instead, they are downloaded from
Microsoft CDN. Thus, even with the Updater role assigned, the agent cannot download and
distribute patches.

Windows third-party products

To install the third-party updates for Windows OS on the selected machines, enable the Windows
third-party products option.

915 © Acronis International GmbH, 2003-2024

Select the installation options:

Option Description

All updates Use this option if you want to install all approved updates.
*

Only major updates Use this option if you want to install all approved major
updates.

Only minor updates Use this option if you want to install approved minor
updates.

Updates of specific products Use this option if you want to define custom settings for
(Automatic patch approval different products.
and testing)
If you want to update specific products then, for each
product, you can define which updates to install by
category, severity, or approval status.

If you want to configure automatic test approval and

testing of the patches, select this option.

Install the latest versions only Select this check box if you want to install the latest
for applications with detected updates only for applications that have detected
vulnerabilities vulnerabilities. *

* This option requires Cyber Protect agent version 23.11.36772 or later.

For Windows third-party products, patches are distributed directly to the managed workloads from
an internal Acronis database. In case the Updater role is assigned to an agent, this agent will be
used to download and distribute patches.

916 © Acronis International GmbH, 2003-2024

Schedule
Define the schedule and conditions according to which the updates will be installed on the selected
machines.

Field Description

Schedule the This setting defines when the task will be run.
task run using
The following values are available:
the following
events l Schedule by time – This is the default setting. The task will run
according to the specified time.
l When user logs in to the system – By default, a login of any user will
start the task. You can modify this setting so that only a specific user
account can trigger the task.
l When user logs off the system – By default, a logoff of any user will
start the task. You can modify this setting so that only a specific user
account can trigger the task.

Note
The task will not run at system shutdown. Shutting down and logging
off are different events in the scheduling configuration.

l On the system startup – The task will run when the operating system
starts.
l On the system shutdown – The task will run when the operating
system shuts down.

Schedule type The field appears if, in Schedule the task run using the following
events, you have selected Schedule by time.

The following values are available:

l Monthly – Select the months and the weeks or days of the month
when the task will run.
l Daily – This is the default setting. Select the days of the week when the
task will run.
l Hourly – Select the days of the week, repetition number, and the time
interval in which the task will run.

Start at The field appears if, in Schedule the task run using the following
events, you have selected Schedule by time

Select the exact time when the task will run.

Configure The field appears if, in Schedule the task run using the following
maintenance events, you have selected Schedule by time.
window for
Select this setting if you want the patch installation to run only during the
patches
time interval that you will specify. If the patch installation process has not

917 © Acronis International GmbH, 2003-2024

 Field Description

completed by the end time defined by the maintenance window for

patches, it will be stopped automatically.

Run within a The field appears if, in Schedule the task run using the following
date range events, you have selected Schedule by time.

Set a range in which the configured schedule will be effective.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs in to the system.
login to the
The following values are available:
operating
system will l Any user - Use this option if you want the login of any user to trigger
initiate a task the task.
l The following user - Use this option if you want only the login of a
specific user account to trigger the task.

Specify a user The field appears if, in Schedule the task run using the following
account whose events, you have selected When user logs off the system.
logout from the
The following values are available:
operating
system will l Any user - Use this option if you want the logout of any user to trigger
initiate a task the task.
l The following user - Use this option if you want only the logout of a
specific user account to trigger the task.

Start conditions Defines all conditions that must be met simultaneously for the task to
run.

Start conditions for antimalware scans are similar to the start conditions
for the Backup module that are described in "Start conditions".

You can define the following additional start conditions:

l Distribute task start time within a time window – This option

allows you to set the time frame for the task in order to avoid network
bottlenecks. You can specify the delay in hours or minutes. For
example, if the default start time is 10:00 AM and the delay is 60
minutes, then the task will start between 10:00 AM and 11:00 AM.
l If the machine is turned off, run missed tasks at the machine
startup
l Prevent the sleep or hibernate mode during task running – This
option is effective only for machines running Windows.
l If start conditions are not met, run the task anyway after –
Specify the period after which the task will run, regardless of the other
start conditions.

918 © Acronis International GmbH, 2003-2024

 Field Description

Note
Start conditions are not supported for Linux.

Reboot after Define whether to reboot the machine automatically after the installation
update of the updates completes.

The following values are available:

l Never – A reboot will never be initiated after the updates.

l If required – A reboot will be initiated only if it is required for applying
the updates.
l Always – A reboot will be always initiated after the updates. You can
specify a reboot delay.

Do not reboot If you select this option, if a backup process is running, the reboot of the
until backup is machine will be delayed until the backup is completed.
finished

Pre-update backup
Run backup before installing software updates – the system will create an incremental backup
of machine before installing any updates on it. If there were no backups created earlier, then a full
backup of machine will be created. It allows you to prevent such cases when the installation of
updates was unsuccessful and you need to get back to the previous state. For the Pre-update
backup option to work, the corresponding machines must have both the patch management and
the backup module enabled in a protection plan and the items to back up – entire machine or
boot+system volumes. If you select inappropriate items to back up, then the system will not allow
you to enable the Pre-update backup option.

Viewing the list of available patches

After a vulnerability assessment scan completes, you can view information about the available
patches in Software management > Patches.

To view details about a specific patch, in the list of patches, click the corresponding patch.

The following table describes the information for the patch that you can view on the screen.

Field Description

Approval status The approval status is mainly needed for automatic approval scenarios.

You can define one of the following statuses for a patch:

l Approved – the patch was installed on at least one machine and validated as ok
l Declined – the patch is not safe and may corrupt a machine system
l Pending approval – the patch status is unclear and should be validated

919 © Acronis International GmbH, 2003-2024

License l Agreed
agreement l Disagreed. If you disagree with the license agreement, then the patch status
becomes Declined and it will not be installed

Severity The severity of the patch:

l Critical
l High
l Medium
l Low
l None

Vendor The vendor of the patch

Affected Product for which the patch is applicable

product

Installed Product versions that are already installed

versions

Version Version of the patch

Category The category to which the patch belongs:

l Critical update – broadly released fixes for specific problems addressing critical,
non-security related bugs.
l Security update – broadly released fixes for specific products addressing security
issues.
l Definition update – updates to virus or other definition files.
l Update rollup – cumulative set of hotfixes, security updates, critical updates, and
updates packaged together for easy deployment. A rollup generally targets a
specific area, such as security, or a specific component, such as Internet
Information Services (IIS).
l Service pack – cumulative sets of all hotfixes, security updates, critical updates,
and updates created since the release of the product. Service packs might also
contain a limited number of customer-requested design changes or features.
l Tool – utilities or features that aid in accomplishing a task or set of tasks.
l Feature pack – new feature releases, usually rolled into products at the next
release.
l Update – broadly released fixes for specific problems addressing non-critical, non-
security related bugs.
l Application – patches for an application.

Release date The date when the patch was released

Last reported The date of the last time when the patch was reported

First installed The date of the first successful installation of the patch on a machine

Microsoft KB If the patch is for a Microsoft product, the field shows the KB article ID

920 © Acronis International GmbH, 2003-2024

 Machines Number of affected machines

Vulnerabilities The number of vulnerabilities. If you click on it, you will be redirected to the list of
vulnerabilities.

Size The average size of the patch

Language The language which is supported by the patch

Vendor site The official site of the vendor

Configuring the patch lifetime in the list

You can keep the list of patches up to date by configuring the patch lifetime in the list on the
Patches screen. This setting defines how long the detected available patch will be visible in the list
of patches. The patch will be removed from the list after it is successfully installed on all the
machines on which it was indicated as missing, or after the lifetime in the list passes.

To configure the patch lifetime in the list

1. In the Cyber Protect console, go to Software management > Patches.

2. Click Settings.
3. In Lifetime in list, select the appropriate option.

Option Description

Forever The patch will always stay in the list.

7 days The patch will be removed from the list seven days after its first installation.
For example, let us assume that you have two machines on which patches
must be installed. One of them is online, and the other one is offline. The patch
was installed on the first machine. After 7 days, the patch will be removed from
the list of patches, even if it is not installed on the second machine (because it
was offline).

30 days The patch is removed from the list 30 days after its first installation.

Automatic patch approval

Automatic patch approval makes the process of installing updates on machines easier. With
automatic patch approval, the installation of patches is not delayed by the manual patch approval
process. Important updates and fixes are installed faster, which increases the reliability of your
system.

You can use automatic patch approval in test scenarios for automatic installation of patches. If the
patches are installed successfully on the test machines, the patches will be automatically installed
on the production machines, too. For more information about this scenario, see "Use case for
automatic patch approval and testing" (p. 922).

921 © Acronis International GmbH, 2003-2024

You can also use automatic patch approval in scenarios for automatic installation of patches in your
production environment, skipping the testing phase. For more information about this scenario, see
"Use case for automatic patch approval without testing" (p. 925).

Configuring automatic patch approval

You can configure automatic patch approval and ensure that the installation of patches is not
delayed by the manual patch approval process.

To configure automatic patch approval

1. In the Cyber Protect console, go to Software management > Patches.

2. Click Settings.
3. Enable Automatic patch approval.
4. Configure the settings for automatic patch approval.
a. Select the automatic patch approval option.

Option Description

Automatic The approval status of the patch will change to Approved when the
patch selected number of days passes after a successful installation of the
approval patch. We recommend that you use this setting if you want to test the
and testing patches by installing them on a test machine first, ensure that everything
is working as expected, and then install the patches in your production
environment.

Automatic The approval status of the patch will change to Approved when the
patch selected number of days passes after the patch was found.
approval
without
testing

b. Select the number of days that must pass after the condition from the automatic patch
approval option is met. After this period, the approval status of the patches will automatically
change from Pending approval to Approved.
5. Select Automatically accept the license agreements.
6. Click Apply.

Use case for automatic patch approval and testing

If you want to test the new patches on a test machine before installing them on your production
machines, you can configure two protection plans - a plan for installation of patches for test
purposes, and a plan for installation of tested patches on production machines. Thus, you will
ensure that the patches that you install in your production environment are safe and your
production machines work correctly after the patch installation.

The use case consists of the following stages:

922 © Acronis International GmbH, 2003-2024

1. Configure the settings for Automatic patch approval. Select the Automatic patch approval and
testing option. For more information, see "Configuring automatic patch approval" (p. 922).
2. Configure a protection plan for test purposes (for example, 'Test patching') with the enabled
Patch management module and apply it to the machines in the test environment. Specify the
following condition of patch installation: the patch approval status must be Pending approval.
This step is needed to validate the patches and check if the machines work properly after patch
installation. For more information, see "Configuring the Test patching protection plan" (p. 923).
3. Configure a protection plan for the production environment (for example, 'Production patching')
with the enabled Patch management module and apply it to the machines in the production
environment. Specify the following condition of patch installation: the patch status must be
Approved. For more information, see "Configuring the Production patching protection plan" (p.
924).
4. Run the Test patching plan and check the results. Leave the approval status of the machines that
have no issues as Pending approval, but change the approval status of the machines working
incorrectly to Declined. According to the number of days set in the Automatic patch approval
setting, the status of the patches will automatically change from Pending approval to
Approved. When you run the Production patching plan, only the Approved patches will be
installed on the production machines. For more information, see "Running the Test patching
protection plan and decline unsafe patches" (p. 925).
5. Run the Production patching plan.

Configuring the Test patching protection plan

You can configure a protection plan with patch installation settings for your machines in the test
environment.

To configure the Test patching protection plan

1. In the Cyber Protect console, go to Management > Protection plans.

2. Click Create plan.
3. Enable the Patch management module.
4. Define which updates to install for Microsoft and third-party products, schedule, and pre-update
backup. For more details about these settings, see "Patch management settings in the protection
plan" (p. 914).

Important
For all the products to be updated, select the Pending approval approval status. Thus, the
agent will install only Pending approval patches on the selected machines in the test
environment.

923 © Acronis International GmbH, 2003-2024

Configuring the Production patching protection plan
You can configure a protection plan with patch installation settings for your machines in the
production environment.

To configure the Production patching protection plan

1. In the Cyber Protect console, go to Management > Protection plans.

2. Click Create plan.
3. Enable the Patch management module.
4. Define which updates to install for Microsoft and third-party products, schedule, and pre-update
backup. For more details about these settings, see "Patch management settings in the protection
plan" (p. 914).

Important
For all the products to be updated, set the Approval status to Approved. Thus, the agent will
install only Approved patches on the selected machines in the production environment.

924 © Acronis International GmbH, 2003-2024

Running the Test patching protection plan and decline unsafe patches
After patches are installed on the machines in your test environment, you can check if everything is
working as expected. You can leave the approval status of the machines that have no issues as
Pending approval, but change the approval status of the machines working incorrectly to
Declined.

To run the Test patching protection plan and decline the patches that are not safe

1. Run the Test patching protection plan (by schedule or manually).

2. Depending on the result, see which of the installed patches are safe.
3. Go to Software management > Patches and set the Approval status to Declined for the
patches that are not safe.

Use case for automatic patch approval without testing

If you want to automatically install new patches on your production machines as soon as possible,
without installing them on test machines first, you can configure only one protection plan.

The use case consists of the following stages:

1. Configure the settings for Automatic patch approval. Select the Automatic patch approval
without testing option. For more information, see "Configuring automatic patch approval" (p.
922).
2. Configure a protection plan for the production environment (for example, 'Production patching')
with the enabled Patch management module and apply it to the machines in the production
environment. Specify the following condition of patch installation: the patch status must be
Approved. For more information, see "Configuring the Production patching protection plan" (p.

925 © Acronis International GmbH, 2003-2024

 924).
3. Run the Production patching plan.

Approving patches manually

You can manually approve a patch and speed up its installation by skipping the testing phase.

Prerequisites
l A protection plan that has the Patch management module enabled is applied to at least one
Windows machine.
l There are patches that are still not installed on the machine or machines on which the protection
plan is applied.

To manually approve patches

1. In the Cyber Protect console, go to Software management > Patches.

2. Select the patches that you want to install, and then accept their license agreements.
3. Set the Approval status of the patches to Approved.
The approval status of the patches is set to Approved. The patches will be automatically installed
on the machines based on the schedule defined in the protection plan. If you want to install the
patches immediately, follow the procedure that is described in "Installing patches on demand"
(p. 926).

Installing patches on demand

You can manually install patches on demand when you do not want to wait for the scheduled
installation time.

You can start the manual patch installation from three screens: Patches, Vulnerabilities, and All
devices.

To manually install a patch

From Patches

1. In the Cyber Protect console, go to Software management > Patches.

2. Accept the license agreements for the patches that you want to install.
3. In the Install patches wizard, select the patches that you want to install, and then click Install.
4. Select the machines on which you want to install the patches.
5. Select the reboot options.

926 © Acronis International GmbH, 2003-2024

 a. Select if you want the machine to be rebooted after the patches are installed.

Option Description

No The machines will not be rebooted automatically after the patches are
installed.

If required The machines will be rebooted only if it is required for applying the
patches.

Yes The machines will be rebooted automatically after the patches are
installed. You can also specify a reboot delay.

b. [Optional] If you want to delay the machine reboot while a backup of the machine is in
progress, select Do not reboot until backup is finished.
6. Click Install patches.

From Vulnerabilities

1. In the Cyber Protect console, go to Software management > Vulnerabilities.

2. Perform the remediation process, as described in "Managing found vulnerabilities" (p. 912).

From All devices

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the machine on which you want to install the patches.
3. Click Patch.
4. Select the patches that you want to install, and then click Next.
5. Select the reboot options.
a. Select if you want the machine to be rebooted after the patches are installed.

Option Description

No The machines will not be rebooted automatically after the patches are
installed.

If required The machines will be rebooted only if it is required for applying the
patches.

Yes The machines will be rebooted automatically after the patches are
installed. You can also specify a reboot delay.

b. [Optional] If you want to delay the machine reboot while a backup of the machine is in
progress, select Do not reboot until backup is finished.
6. Click Install patches.

927 © Acronis International GmbH, 2003-2024

Managing your software and hardware
inventory

Software inventory
The software inventory feature is available for devices on which the Advanced pack is enabled, or
which have the (Legacy) Cyber Protect license. The feature enables you to view all the software
applications that are installed on all Windows and macOS devices.

To obtain the software inventory data, you can run automatic or manual scans on the devices.

You can use the software inventory data to:

l browse and compare the information about all applications that are installed on the company
devices
l determine if an application needs to be updated
l determine if an unused application needs to be removed
l ensure that the software version on multiple company devices is the same
l monitor changes in the software status between consecutive scans.

Enabling the software inventory scanning

When software inventory scanning is enabled on the devies, the system automatically collects the
software data every 12 hours.

The Software inventory scanning feature is enabled by default for all devices that have the required
license, but you can change the setting when necessary.

Note
Customer tenants can enable or disable the software inventory scanning. Unit tenants can only view
the software inventory scanning settings, but cannot change them.

To enable the software inventory scanning

1. In the Cyber Protect console, go to Settings.

2. Click Protection.
3. Click Inventory scanning.
4. Enable the Software inventory scanning module by clicking the switch next to the module
name.

To disable the software inventory scanning

1. In the Cyber Protect console, go to Settings.

2. Click Protection.
3. Click Inventory scanning.

928 © Acronis International GmbH, 2003-2024

4. Disable the Software inventory scanning module by clicking the switch next to the module
name.

Running a software inventory scan manually

You can manually run a software inventory scan from the Software inventory screen, or from the
Software tab in the Inventory screen.

Prerequisites
l The device uses Windows or macOS operating system.
l The device has the required (Legacy) Cyber Protect license or has the Advanced Management
pack activated.

To run a software inventory scan from the Software inventory screen

1. In the Cyber Protect console, go to Software management.

2. Click Software inventory.
3. In the Group by: drop-down field, select Devices.
4. Find the device which you want to scan, and click Scan now.

To run a software inventory scan from the Software tab in the Inventory screen

1. In the Cyber Protect console, go to Devices.

2. Click the device which you want to scan, and click Inventory.
3. In the Software tab, click Scan now.

Browsing the software inventory

You can view and browse the data for all software applications that are available on all company
devices.

Prerequisites
l The devices use Windows or macOS operating system.
l The devices have the required (Legacy) Cyber Protect license or have the Advanced Management
pack activated.
l Software inventory scan on the devices has finished successfully.

To view all software applications that are available on all Windows and macOS company devices

1. In the Cyber Protect console, go to Software Management.

2. Click Software inventory.
By default, the data is grouped by device. The following table describes the data that is visible in
the Software inventory screen.

929 © Acronis International GmbH, 2003-2024

 Column Description

Name Name of the application.

Version Version of the application.

Status Status of the application.

l New.
l Updated.
l Removed.
l No Change.

Vendor Vendor of the application.

Date Date and time when the application was installed.

installed

Last run For macOS devices only. Date and time when the application was last
active.

Location Directory where the application is installed.

User User who installed the application.

System type For Windows devices only. Bit type of the application.
l X86 for 32-bit applications.
l X64 for 64-bit applications.

3. To group the data by application, in the Group by: drop-down field, select Applications.
4. To narrow the information displayed on the screen, use one or a combination of the filters.
a. Click Filter.
b. Select one or a combination of several filters.
The following table describes the filters in the Software inventory screen.

Filter Description

Device Name Device name. Multiple selection is possible. Use this

filter if you want to compare the software on specific
devices.

Application Application name. Multiple selection is possible. Use this

filter if you want to compare the data for a specific
application on specific devices or on all devices.

Vendor Vendor of the application. Multiple selection is possible.

Use this filter if you want to view all applications from a
specific vendor on specific devices or on all devices.

Status Application status. Multiple selection is possible. Use this

filter if you want to view all applications in the selected

930 © Acronis International GmbH, 2003-2024

 Filter Description

status on specific devices or on all devices.

Date installed Date when the application is installed. Use this filter if
you want to view all applications that are installed on a
specific date on specific devices or on all devices.

Scan date Date of the software inventory scan. Use this filter if you
want to view the information about the software on
specific devices or on all devices that are scanned on
that date.

c. Click Apply.
5. To browse through the whole software inventory list, use the pagination in the lower left part of
the screen.

l Click the number of the page you want to open.

l In the drop-down field, select the page number of the page you want to open.

Viewing the software inventory of a single device

You can view a list of all the software applications that are installed on a single device, as well as
detailed information about the applications, such as status, version, vendor, installation date, last
run, and location.

Prerequisites
l The device uses Windows or macOS operating system.
l The device has the required (Legacy) Cyber Protect license or has the Advanced Management
pack activated.
l Software inventory scan on the device has finished successfully.

To view the software inventory of a single device from the Software Inventory screen

1. In the Cyber Protect console, go to Software management.

2. Click Software inventory.
3. In the Group by: drop-down field, select Devices.
4. Find the device you want to inspect using one of the following options.
l Find the device using the Filter:
a. Click Filter.
b. In the Device name field, select the name of the device you want to view.
c. Click Apply.
l Find the device using the dynamic Search:
a. Click Search.
b. Type the full device name or part of the device name.

To view the software inventory of a single device from Devices screen

931 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Devices.
2. Click the device which you want to view, and click Inventory.
3. Click the Software tab.

Hardware inventory
The hardware inventory feature enables you to view all the hardware components that are available
on:

l physical Windows and macOS devices with a license that supports the Hardware inventory
feature.
l virtual Windows and macOS machines running on the following virtualization platforms: VMware,
Hyper-V, Citrix, Parallels, Oracle, Nutanix, Virtuozzo, and Virtuozzo Hybrid Infrastructure. For
more information about the supported versions of the virtualization platforms, see "Supported
virtualization platforms" (p. 31).

Note
The Hardware inventory feature for virtual machines is not supported in the Cyber Protect legacy
editions.

The hardware inventory feature is supported only for devices on which a protection agent is
installed.

To obtain the hardware inventory data, you can run automatic or manual scans on the devices.

You can use the hardware inventory data to:

l discover all hardware assets of the organization

l browse through the hardware inventory of all devices in your organization
l compare the hardware components on multiple company devices
l view detailed information about a hardware component.

Enabling the hardware inventory scanning

When hardware inventory scanning is enabled on physical devices and virtual machines, the system
automatically collects the hardware data every 12 hours.

The hardware inventory scanning feature is enabled by default, but you can change the setting
when necessary.

Note
Customer tenants can enable or disable the hardware inventory scanning. Unit tenants can only
view the hardware inventory scanning settings, but cannot change them.

To enable the hardware inventory scanning

932 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Settings.
2. Click Protection.
3. Click Inventory scanning.
4. Enable the Hardware inventory scanning module by clicking the switch next to the module
name.

To disable the hardware inventory scanning

1. In the Cyber Protect console, go to Settings.

2. Click Protection.
3. Click Inventory scanning.
4. Disable the Hardware inventory scanning module by clicking the switch next to the module
name.

Running a hardware inventory scan manually

You can manually run a hardware inventory scan for a single device, and view the current data for
the hardware components of the device.

Note
Hardware inventory scanning of virtual machines is supported only when the current date and time
of the virtual machine corresponds to the current date and time in UTC. To ensure that the virtual
machine uses the correct time settings, disable the Time synchronization option of the virtual
machine, set the current date, time, and time zone, and then restart Acronis Agent Core Service
and Acronis Managed Machine Service.

Prerequisites
l (For all devices) The device uses a Windows or macOS operating system.
l (For all devices) The devices have a license that supports the Hardware inventory feature. Note
that the Hardware inventory feature for virtual machines is not supported in the (Legacy) Cyber
Protect editions.
l (For all devices) A protection agent is installed on the device.
l (For virtual machines) The machine runs on one of the supported virtualization platforms. For
more information, see "Hardware inventory" (p. 932).

To run a hardware inventory scan on a single device

1. In the Cyber Protect console, go to Devices.

2. Click the device which you want to scan, and click Inventory.
3. In the Hardware tab, click Scan now.

Browsing the hardware inventory

You can view and browse the data for all hardware components that are available on all company
devices.

933 © Acronis International GmbH, 2003-2024

Prerequisites
l (For all devices) The devices use Windows or macOS operating system.
l (For all devices) The devices have a license that supports the Hardware inventory feature. Note
that the Hardware inventory feature for virtual machines is not supported in the Cyber Protect
legacy editions.
l (For all devices) A protection agent is installed on the device.
l (For all devices) Hardware inventory scan on the devices has finished successfully.
l (For virtual machines) The machine runs on one of the supported virtualization platforms. For
more information, see "Hardware inventory" (p. 932).

To view all hardware components that are available on the Windows and macOS company
devices

1. In the Cyber Protect console, go to Devices.

2. In the View: drop-down field, select Hardware.

Note
The view is a set of columns which determines what data is visible in the screen. The predefined
views are Standard and Hardware. You can create and save custom views which include
different sets of columns, and are more convenient for your needs.

The following table describes the data that is visible in the Hardware view.

Column Description

Name Device name.

Hardware scan status Status of the hardware scan.

l Completed.
l Not started.
l Not supported. status is shown for workloads
for which hardware inventory functionality is
not supported, i.e. virtual machines, mobile
devices, Linux devices.
l Update agent. shown in case the outdated
version of agent is installed on the device.
Clicking on this action will redirect to Settings >
Agents page, where admin can perform the
agent update.
l Upgrade quota. Clicking on it will open a
dialog where admin can switch the current
license to one of other available for tenant
licenses

Processor Models of all processors of the device.

934 © Acronis International GmbH, 2003-2024

 Column Description

Processor cores Number of cores of all processors of the device.

Disk storage Used storage, and total storage of all the disks of
the device.

Memory Total RAM capacity of the device.

Scan date Date and time of the last hardware inventory

scan.

Motherboard Motherboard of the device.

Motherboard serial number Serial number of the motherboard.

BIOS version Version of the BIOS of the system.

Organization Organization to which the device belongs.

Owner Owner of the device.

Domain Domain of the device.

Operating system Operating system of the device.

Operating system build Build of the operating system of the device.

3. To add columns in the table, click the column options icon, and select the columns that you want
to be visible in the table.
4. To narrow the information displayed on the screen, use one or more filters.
a. Click Search.
b. Click the arrow, and then click Hardware.
c. Select one or a combination of several filters.
The following table describes the Hardware filters.

Filter Description

Processor Multiple selection is possible. Use this filter if you want to view the
model hardware data of the devices which have the specified processor model.

Processor Use this filter if you want to view the hardware data of the devices which
cores have the specified number of processor cores.

Disk total Use this filter if you want to view the hardware data of the devices which
size have the specified total storage size.

Memory Use this filter if you want to view the hardware data of the devices which
capacity have the specified RAM capacity.

d. Click Apply.
5. To sort the data in an ascending order, click a column name.

935 © Acronis International GmbH, 2003-2024

Viewing the hardware of a single device
You can view detailed information about the motherboard, processors, memory, graphics, storage
drives, network, and system of a specific device.

Prerequisites
l (For all devices) The device uses Windows or macOS operating system.
l (For all devices) The devices have a license that supports the Hardware inventory feature. Note
that the Hardware inventory feature for virtual machines is not supported in the Cyber Protect
legacy editions.
l (For all devices) A protection agent is installed on the device.
l (For all devices) Hardware inventory scan on the device has finished successfully.
l (For virtual machines) The machine runs on one of the supported virtualization platforms. For
more information, see "Hardware inventory" (p. 932).

To view the detailed information about the hardware of a specific device

1. In the Cyber Protect console, go to Devices->All Devices.

2. In the View: drop-down field, select Hardware.
3. Find the device you want to inspect using one of the methods described below.
l Find the device using the Filter:
a. Click Filter.
b. Select one or a combination of several filter parameters to find the device.
c. Click Apply.
l Find the device using the Search:
a. Click Search.
b. Type the full device name or part of the device name, and click Enter.
4. Click the row listing the device, and click Inventory.
5. Click the Hardware tab.
The following hardware data is available.

Hardware component Information displayed

Motherboard Name, manufacturer, model, and serial

number of the motherboard of the device.

Processors Manufacturer, model, max clock speed, and

number of cores of each processor of the
device.

Memory Capacity, manufacturer, and serial number of

the memory of the device.

Graphics Manufacturer and model of the GPUs of the

936 © Acronis International GmbH, 2003-2024

 Hardware component Information displayed

device.

Storage drives Model, media type, available space and size of

the storage drives of the device.

Network Mac address, IP address, and type of the

network adapters of the device.

System Product ID, original install date, system boot

time, system manufacturer, system model,
BIOS version, boot device, system locale, and
time zone of the system.

937 © Acronis International GmbH, 2003-2024

Connecting to workloads for remote desktop or
remote assistance
The remote desktop and assistance functionality is a convenient way to connect to the workloads in
your organization for remote control or remote assistance. Starting from December 2022, the
functionality supports the NEAR, RDP, and Apple Screen Sharing protocols. For more information,
see "Remote connection protocols" (p. 943).

You can use the remote desktop functionality to perform the following tasks.

l Connect to remote Windows, macOS, and Linux workloads by using NEAR in view-only mode.
l Connect to remote Windows workloads by using RDP.
l Connect to remote macOS workloads by using Apple Screen Sharing in view-only or curtain
mode.
l Connect to managed workloads and remotely control them by using cloud remote connections.
l Connect to unmanaged workloads and remotely control them by using direct remote
connections.
l Connect to unmanaged remote workloads by using Acronis Quick Assist.
l Connect to remote workloads by using different authentication methods: with remote workload
credentials, by asking for permission to observe or control, or with an access code (for Quick
Assist).
l Observe multiple monitors at the same time in multi-view.
l Record remote sessions (when connected via NEAR).
l View the session history report.

For more information about the features that are part of the Standard and Advanced Management
packs, see "Supported remote desktop and assistance features" (p. 939).

You can use the remote assistance functionality to perform the following tasks.

l Connect to remote Windows, macOS, and Linux workloads by using NEAR in control mode.
l Connect to remote macOS workloads by using Apple Screen Sharing in control mode.
l Provide remote assistance to workloads by using cloud remote connections.
l Transfer files between the local and remote workloads.
l Perform basic management actions on the remote workload: restart, shut down, sleep, empty
recycle bin, and log out the remote user.
l Monitor the remote workload by periodically taking screenshots of its desktop.

For more information about the features that are part of the Standard protection and Advanced
Management, see "Supported remote desktop and assistance features" (p. 939).

938 © Acronis International GmbH, 2003-2024

Important
To activate the complete remote desktop and assistance functionality for a managed workload, you
must configure and apply a remote management plan to the workload. Although you can apply only
one remote management plan on a workload, depending on your needs, you can configure
different remote management plans and apply them to different workloads.

For example, you can create a remote management plan that has only the RDP protocol enabled
and apply it to some workloads. In that way, you will be able to remotely connect to these
workloads without activating the Advanced Management license per workload, and without paying
any additional fees.

On the other hand, you can create another remote management plan that has the NEAR and Apple
Screen Sharing protocols enabled. In this case, the Advanced Management license per workload will
be activated, and you will be charged for each workload to which this remote management plan is
applied.

For more information about remote management plans and working with them, see "Remote
management plans" (p. 946).

Note
The remote desktop and assistance functionality requires:

l a one-time installation of Connect Client on the managing (host) workload. The system will
suggest you to download the client when you attempt performing a remote action (remote
control or remote assistance) on a target workload for the first time. Alternatively, you can
download Connect Client from the Downloads window in the Protection console. For more
information about the settings that you can configure, see "Configuring the Connect Client
settings" (p. 975).
l installation of Connect Agent on the managed workloads. The Connect Agent is a module that is
part of the Protection agent, starting from version 15.0.31266.
l for macOS remote workloads, the required system permissions should be granted to the
Connect Agent. For more information, see "Installing protection agents in macOS" (p. 78).
l running the Acronis Quick Assist application on the unmanaged workloads. You can download
Acronis Quick Assist from the website.

For more information about the supported platforms by each remote desktop and assistance
component, see "Supported platforms" (p. 942).

Supported remote desktop and assistance features

The following table provides more information about the changes of the supported features of the
remote desktop and assistance functionalitythat were introduced in December 2022.

939 © Acronis International GmbH, 2003-2024

 Feature Standard Advanced Standard Advanced
protection Management protection Management

before Dec before Dec after Dec after Dec 2022

2022 2022 2022

Remote assistance via Yes No No No

RDP for Windows

Share a remote No Yes No No

connection with users

Remote connections

Remote actions No No Yes Yes

Selecting a session for No No No Yes

Windows/macOS/Linux to
connect

Direct connect via RDP No No No Yes

and Apple Screen Sharing

Multi-window control No No No Yes

Connection modes: No No No Yes

Control/View-only/Curtain

Common credentials No No Yes Yes

support for remote
connections

Concurrent connections per technician

via RDP Yes Yes Yes Yes

via NEAR No No No Yes

Files transfer and sharing

from Windows to No No No Yes

Windows/macOS/Linux

from macOS to No No No Yes

Windows/macOS/Linux

from Linux to No No No Yes

Windows/macOS/Linux

Connecting via Quick Assist application

from Windows to No No No Yes

940 © Acronis International GmbH, 2003-2024

 Feature Standard Advanced Standard Advanced
protection Management protection Management

before Dec before Dec after Dec after Dec 2022

2022 2022 2022

Windows/macOS/Linux

from macOS to No No No Yes

Windows/macOS/Linux

from Linux to No No No Yes

Windows/macOS/Linux

Remote connections via protocols

Remote connection via NEAR

from Windows to No No No Yes

Windows/macOS/Linux

from macOS to No No No Yes

Windows/macOS/Linux

from Linux to No No No Yes

Windows/macOS/Linux

Remote connection via RDP (desktop client)

from Windows to Yes Yes Yes Yes

Windows

from macOS to Windows Yes Yes Yes Yes

from Linux to Windows No No Yes Yes

Remote connection via RDP (web client)

from Windows to Yes Yes Yes Yes

Windows

from macOS to Windows Yes Yes Yes Yes

from Linux to Windows No No Yes Yes

Remote connection via Apple Screen Sharing

from No No No Yes
Windows/macOS/Linux to
macOS

Session management

Session recording No No No Yes

941 © Acronis International GmbH, 2003-2024

 Feature Standard Advanced Standard Advanced
protection Management protection Management

before Dec before Dec after Dec after Dec 2022

2022 2022 2022

Reporting and monitoring

Session history and No No No Yes

search

Screenshot transmission No No No Yes

Supported platforms
The following table lists the supported operating systems by each of component of the remote
desktop and assistance functionality.

Remote desktop component Supported platforms

Connect Client l Windows 7 or later

l macOS 10.13 or later
l Linux:
openSUSE 8
Debian 9, 10
Ubuntu 18.0-20.10
Red Hat Enterprise Linux 8
CentOS 8
Fedora 31-33
SUSE Linux Enterprise Server 15 SP2
Linux Mint 20
Manjaro 20

Connect Agent l Windows 7 or later

l Windows Server 2008 R2 or later
l macOS 10.13 or later
l Linux:
Red Hat Enterprise Linux 8, 8.1
Fedora 30
Ubuntu 18.4 LTS (Bionic Beaver) -19.04 (Disco Dingo)
Debian 9, 10
CentOS 8
openSUSE 15.1

Acronis Quick Assist l Windows 7 or later

l Windows Server 2008 R2 or later
l macOS 10.13 or later

942 © Acronis International GmbH, 2003-2024

 Remote desktop component Supported platforms

l Linux:
Red Hat Enterprise Linux 8, 8.1
Fedora 30
Ubuntu 18.4 LTS (Bionic Beaver) -19.04 (Disco Dingo)
Debian 9, 10
CentOS 8
openSUSE 15.1

Remote connection protocols

The remote desktop functionality uses the following protocols for remote connections.

NEAR
NEAR is a highly secure protocol developed by Acronis that has the following characteristics.

l
H.264
NEAR implements three quality modes: Smooth, Balanced and Sharp. In Smooth mode, NEAR
uses hardware H.264 encoding on macOS and Windows to encode the desktop picture, and
falling back to software encoder if hardware encoder is not available. The picture size is currently
limited to Full HD resolution (1920x1080).

l
Adaptive codec
In Balanced and Sharp quality modes, NEAR uses Adaptive codec, which provides full picture
quality in 32 bit, compared to the 'video' mode used by H.264.
In Balanced mode, the picture quality is automatically adjusted according to your current
network conditions and retains the current framerate.
In Sharp mode, the picture is full quality, but it might be with a reduced framerate, if your
network, processor, or video card are overloaded.
Adaptive codec is using OpenCL on Windows and macOS when it is available in their graphics
drivers.

l
Sound transfer
NEAR is capable of capturing the remote computer sound and transfer that to host. For more
information about enabling remote sound redirection on Windows, macOS, and Linux, see
"Remote sound redirection" (p. 944).

l
Different login options
You can use the following methods to log in to the remote workload.

943 © Acronis International GmbH, 2003-2024

 Access code: the user who is logged in to the remote workload runs Quick Assist and tells you
the access code. With this method, you always connect to the session of the currently logged in
user.
Workload credentials: log in to the remote workload using administrator credentials that are
registered in the workload.
Ask for permission to observe or control: the user who is logged in to the remote workload
will be asked to allow or deny the connection.

l
Security
Your data is always two-way encrypted with AES encryption in NEAR.

RDP
Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft that enables
connecting to the remote Windows computer over a network connection.

Apple Screen Sharing

Apple Screen Sharing is a VNC client by Apple included as part of macOS version 10.5 and later.

Remote sound redirection

Connect Client supports audio streaming via the NEAR connection protocol. For more information
about NEAR, see "Remote connection protocols" (p. 943).

Redirecting sound from a remote Windows workload

For Windows workloads, the remote sound should be transmitted automatically. Ensure that there
are sound output devices (speakers or headphones) connected to the remote workload.

Redirecting sound from a remote macOS workload

To enable sound redirection from a macOS workload, ensure that:

l The workload has the Protection agent installed.

l The workload has a sound capture driver installed.
l The workload uses the NEAR protocol for remote connections.

Note
For macOS 10.15 Catalina, the Microphone permission must be granted to the Connect Agent. For
more information about granting the Microphone permission to the Connect Agent, see "Granting
the required system permissions to the Connect Agent" (p. 79).

The agent works with the following sound capture drivers: Soundflower or Blackhole.

944 © Acronis International GmbH, 2003-2024

The installation process on the newest versions is described on the Blackhole wiki page:
https://github.com/ExistentialAudio/BlackHole/wiki/Installation.

Note
Connect Client currently supports only the 2-channel version of Blackhole.

Alternatively, if Homebrew is installed on the workload, you can install Blackhole by running the
following command:

brew install --cask blackhole-2ch

Note
While the sound of a remote macOS workload is redirected, the user who is logged in to the remote
workload will not hear the sound.

Redirecting sound from a remote Linux workload

The remote sound redirection should work automatically with most Linux distributions. If the
remote sound redirection is not working by default, install PulseAudio driver by running the
following command:

sudo apt-get install pulseaudio

Connections to remote workloads for remote desktop or

remote assistance
The remote desktop and assistance functionality provides several ways to establish remote direct or
cloud connections to your workloads.

Direct connections are established via TCP/IP in the local area network (LAN) between Connect
Client and the remote workload that does not have an agent installed. They do not require Internet
access.

Cloud connections are established between Connect Client and the agent or Quick Assist on the
workload via Acronis Cloud.

The following table provides more info about the cloud connection options.

Cloud Cloud connection option View Supported Available for

connection mode remote action

via NEAR from Connect Client to Control Remote desktop managed

Connect Agent workloads
View-only Remote assistance
from Connect Client to
Quick Assist

via RDP from Connect Client to Control Remote desktop managed

945 © Acronis International GmbH, 2003-2024

 Cloud Cloud connection option View Supported Available for
connection mode remote action

Connect Agent workloads

from web client to

Connect Agent

via Apple Screen from Connect Client to Control Remote desktop managed
Sharing Connect Agent workloads
View-only Remote assistance

Curtain

The following table provides more info about the direct connection options.

Direct Direct connection option Supported Available for

connection remote action

via RDP from Connect Client to RDP server Remote desktop unmanaged
workloads

via Apple Screen from Connect Client to Apple Screen Remote desktop unmanaged
Sharing Sharing server workloads
Remote assistance

Remote management plans

Remote management plans are plans that you apply on the Protection agent to enable and
configure the remote desktop and assistance functionality on your managed workloads.

If no remote management plan is applied on a workload, the remote desktop and assistance
functionality will be limited to remote actions (restart, shut down, sleep, empty recycle bin, and log
out remote user).

Note
The availability of the settings that you can configure in the remote management plan depends on
the service pack that is applied on the tenant. To access all settings, activate the Advanced
Management pack. For more information about the features that are part of the Standard and
Advanced Management packs, see "Supported remote desktop and assistance features" (p. 939).

Creating a remote management plan

You can create a remote management plan, and then assign it to a workload to configure the
remote desktop and assistance functionality on the managed workload.

946 © Acronis International GmbH, 2003-2024

Note
The availability of the remote management plan's settings depends on the service quota that is
assigned to the tenant. If you are using the standard functionality, you can only configure
connections via RDP.

Prerequisites
2FA is enabled for your user account.

To create a remote management plan

From Remote management plans

1. In the Cyber Protect console, go to Management > Remote management plans.

2. Create a remote management plan by using one of the two options.
l If there are no remote management plans in the list, click Create.
l If there are remote management plans in the list, click Create plan.
3. [Optional] To change the default name of the plan, click the pencil icon, enter the name of the
plan, and then click Proceed.
4. Click Connection protocols, and enable the protocols that you want to be available in this
remote management plan for remote connections - NEAR, RDP, or Apple Screen Sharing.
5. [Optional] For the NEAR protocol, in the Security settings section, select or clear the check
boxes to enable or disable the corresponding setting, and then click Done.

Setting Description Available for

Lock the workload when If you select this setting, the Windows, macOS
the user disconnects from remote workload will be
the console session locked when you disconnect
from the console session.

Allow only one user at a If you select this setting, Windows, macOS, Linux
time to connect using connections using NEAR and
NEAR or to transfer files file transfers will not be
possible while there is an
active remote connection to
the workload.

Allow the workload's If you select this setting, the Windows, macOS
administrator to connect administrator will be allowed
to any non-admin user to connect to any standard
session user session on the
workload.
If both Allow the
workload's administrator
to connect to any non-

947 © Acronis International GmbH, 2003-2024

 Setting Description Available for

admin user session and

Allow system session
creation are clear, you will
only be able to connect to
active administrator sessions
on the remote macOS
workloads.

Allow system session If you select this setting, macOS

creation when establishing remote
connections, the
administrator will connect in
a new session, instead of one
of the existing active
sessions.

Allow clipboard If you select this setting, you Windows, macOS, Linux
synchronization will be able to transfer data
between your clipboard and
the clipboard of the remote
workload. For example, you
will be able to copy some
text from a file on the
remote workload and paste
it in a file on your workload,
and the opposite.

6. Click Security settings, select or clear the check boxes to enable or disable the corresponding
setting, and then click Done.

Setting Description

Show if the workload is controlled If you select this setting, a notification will be
remotely displayed on the desktop of the remote
workload when there is an active remote
desktop connection to the workload.

Ask for the user's permission to take If you select this setting, the user of the
screenshots of the workload remote workload will be notified when the
administrator requests screenshot
transmission from the workload.

7. Click Workload management, select the features that you want to be available on the remote
workloads, and then click Done.

948 © Acronis International GmbH, 2003-2024

 Setting Description Available on

File transfer Enables the file transfers Windows, macOS, Linux

between local and remote
workloads.

Screenshot transmission Enables the transmission of Windows, macOS, Linux

screenshots of the desktop
of the remote workload to
the Cyber Protect console.

8. Click Display settings, select or clear the check boxes to enable or disable the corresponding
setting, and then click Done.

Note
The Display settings are only available for connections via NEAR.

Setting Description Available on

Use Desktop Desktop duplication is one of Windows

Deduplication for desktop the screen capture methods
capturing on Windows. In some
environments, it might be
unstable. If you do not use
Desktop deduplication, you
will use the basic method
(BitBlt) instead- it is much
slower, but more stable.

Use OpenCL acceleration OpenCL acceleration can Linux

speed up the Adaptive codec,
which is responsible for the
Balanced quality mode, by
running some computations
on the graphics processing
unit (GPU). This requires an
installation of an OpenCL
driver on the remote Linux.
Adaptive Codec is using
OpenCL on macOS and
Windows, if it is available in
your graphics drivers.

Use hardware H.264 NEAR supports three quality Windows, macOS

encoding modes: Smooth, Balanced,
and Sharp.
Smooth mode uses

949 © Acronis International GmbH, 2003-2024

 Setting Description Available on

hardware H.264 encoding to

encode the desktop picture.
Balanced mode uses
Adaptive codec, which
provides full picture quality
in 32 bit, compared to the
'video' mode used by H.264.
The picture quality is
automatically adjusted
according to your current
network conditions and
retains the current
framerate.
Sharp mode uses Adaptive
codec, which provides full
picture quality in 32 bit,
compared to the 'video'
mode used by H.264. The
picture quality is always full,
but it might be with reduced
frames per seconds, if your
network or processor/video
card are overloaded.

9. If you want the information about the users who last logged in to the workloads to be visible in
the workload's details, click Toolbox, select Show last logged-in users, and then click Done.
For more information about the last logged-in users, see "Find the last logged in user" (p. 376).
10. [Optional] To add workloads to the plan:
a. Click Add workloads.
b. Select the workloads, and then click Add.
c. If there are compatibility issues that you want to resolve, follow the procedure as described in
"Resolving compatibility issues with remote management plans" (p. 958).
11. Click Create.

From All devices

1. In the Cyber Protect console, go to Devices > All devices.

2. Click the workload to which you want to apply a remote management plan.
3. Click Protect, and then click Add plan.
4. Click Create plan, and select Remote management.
5. [Optional] To change the default name of the plan, click the pencil icon, enter the name of the
plan, and then click Proceed.

950 © Acronis International GmbH, 2003-2024

6. Click Connection protocols, and enable the protocols that you want to be available in this
remote management plan for remote connections - NEAR, RDP, or Apple Screen Sharing.
7. [Optional] For the NEAR protocol, in the Security settings section, select or clear the check
boxes to enable or disable the corresponding setting, and then click Done.

Setting Description Available for

Lock the workload when If you select this setting, the Windows, macOS
the user disconnects from remote workload will be
the console session locked when you disconnect
from the console session.

Allow only one user at a If you select this setting, Windows, macOS, Linux
time to connect using connections using NEAR and
NEAR or to transfer files file transfers will not be
possible while there is an
active remote connection to
the workload.

Allow the workload's If you select this setting, the Windows, macOS
administrator to connect administrator will be allowed
to any non-admin user to connect to any standard
session user session on the
workload.
If both Allow the
workload's administrator
to connect to any non-
admin user session and
Allow system session
creation are clear, you will
only be able to connect to
active administrator sessions
on the remote macOS
workloads.

Allow system session If you select this setting, macOS

creation when establishing remote
connections, the
administrator will connect in
a new session, instead of one
of the existing active
sessions.

Allow clipboard If you select this setting, you Windows, macOS, Linux
synchronization will be able to transfer data
between your clipboard and
the clipboard of the remote
workload. For example, you

951 © Acronis International GmbH, 2003-2024

 Setting Description Available for

will be able to copy some

text from a file on the
remote workload and paste
it in a file on your workload,
and the opposite.

8. Click Security settings, select or clear the check boxes to enable or disable the corresponding
setting, and then click Done.

Setting Description

Show if the workload is controlled If you select this setting, a notification will be
remotely displayed on the desktop of the remote
workload when there is an active remote
desktop connection to the workload.

Ask for the user's permission to take If you select this setting, the user of the
screenshots of the workload remote workload will be notified when the
administrator requests screenshot
transmission from the workload.

9. Click Workload management, select the features that you want to be available on the remote
workloads, and then click Done.

Setting Description Available on

File transfer Enables the file transfers Windows, macOS, Linux

between local and remote
workloads.

Screenshot transmission Enables the transmission of Windows, macOS, Linux

screenshots of the desktop
of the remote workload to
the Cyber Protect console.

10. Click Display settings, select or clear the check boxes to enable or disable the corresponding
setting, and then click Done.

Note
The Display settings are only available for connections via NEAR.

Setting Description Available on

Use Desktop Desktop duplication is one of Windows

Deduplication for desktop the screen capture methods
capturing on Windows. In some
environments, it might be

952 © Acronis International GmbH, 2003-2024

 Setting Description Available on

unstable. If you do not use

Desktop deduplication, you
will use the basic method
(BitBlt) instead- it is much
slower, but more stable.

Use OpenCL acceleration OpenCL acceleration can Linux

speed up the Adaptive codec,
which is responsible for the
Balanced quality mode, by
running some computations
on the graphics processing
unit (GPU). This requires an
installation of an OpenCL
driver on the remote Linux.
The Adaptive Codec is using
OpenCL on macOS and
Windows, if it is available in
your graphics drivers.

Use hardware H.264 NEAR supports three quality Windows, macOS

encoding modes: Smooth, Balanced,
and Sharp.
Smooth mode uses
hardware H.264 encoding to
encode the desktop picture.
Balanced mode uses
Adaptive codec, which
provides full picture quality
in 32 bit, compared to the
'video' mode used by H.264.
The picture quality is
automatically adjusted
according to your current
network conditions and
retains the current
framerate.
Sharp mode uses Adaptive
codec, which provides full
picture quality in 32 bit,
compared to the 'video'
mode used by H.264. The
picture quality is always full,
but it might be with reduced
frames per seconds, if your

953 © Acronis International GmbH, 2003-2024

 Setting Description Available on

network or processor/video
card are overloaded.

11. If you want the information about the users who last logged in to the workloads to be visible in
the workload's details, click Toolbox, select Show last logged-in users, and then click Done.
For more information about the last logged-in users, see "Find the last logged in user" (p. 376).
12. Click Create.

Adding a workload to a remote management plan

Depending on your needs, you can add workloads to a remote management plan after the plan was
created.

Prerequisites
2FA is enabled for your user account.

To add a workload to a remote management plan

From Remote management plans

1. In the Cyber Protect console, go to Management > Remote management plans.

2. Click the remote management plan.
3. Depending on whether or not the plan was already applied to any workload, do the following:
l Click Add workloads, if the plan was not applied to any workloads yet.
l Click Manage workloads, if the plan was applied to any workloads.
4. Select a workload from the list, and then click Add.
5. Click Save.
6. Click Confirm to apply the required service quota to the workload.

From All devices

1. In the Cyber Protect console, go to Devices > All devices.

2. Click the workload to which you want to apply a remote management plan.
3. Click Protect, and then click Add plan.
4. In Select a plan from the list below, select Remote management to view only the remote
management plans.
5. Click Apply.
6. Click Confirm to apply the required service quota to the workload.

Removing workloads from a remote management plan

Depending on your needs, you can remove workloads from a remote management plan.

954 © Acronis International GmbH, 2003-2024

Prerequisites
2FA is enabled for your user account.

To remove workloads from a remote management plan

1. In the Cyber Protect console, go to Management > Remote management plans.

2. Click the remote management plan.
3. Click Manage workloads.
4. Select one or several workloads that you want to remove from the remote management plan,
and then click Remove.
5. Click Done.
6. Click Save.

Additional operations with existing remote management plans

From the Remote management plans screen, you can perform the following additional operations
with remote management plans: view details, edit, view the activities, view the alerts, rename,
enable, disable, clone, export, and delete.

View details

Prerequisites
2FA is enabled for your user account.

To view the details of a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click View details.

Edit

Prerequisites
2FA is enabled for your user account.

To edit a plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Edit.

Activities

To view the activities related to a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.

955 © Acronis International GmbH, 2003-2024

2. Click Activities.
3. Click an activity to view more details about it.

Alerts

To view the alerts

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Alerts.

Rename

Prerequisites
2FA is enabled for your user account.

To rename a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Rename.
3. Enter the new name of the plan, and then click Proceed.

Enable

Prerequisites
2FA is enabled for your user account.

To enable a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Enable.

Disable

Prerequisites
2FA is enabled for your user account.

To disable a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Disable.

Clone

Prerequisites
2FA is enabled for your user account.

956 © Acronis International GmbH, 2003-2024

To clone a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Clone.
3. Click Create.

Export

Prerequisites
2FA is enabled for your user account.

To export a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Export.
The plan configuration is exported in a JSON format to the local machine.

Delete

Prerequisites
2FA is enabled for your user account.

To delete a remote management plan

1. In the Remote management plans screen, click the More actions icon of the remote
management plan.
2. Click Delete.
3. Select I confirm, and then click Delete.

Compatibility issues with remote management plans

In some cases, applying a remote management plan on a workload might cause compatibility
issues. You might observe the following compatibility issues:

l Conflicting plans - this issue appears when another remote management plan is already applied
on the workload, as only one remote management plan can be applied on a workload.
l Incompatible operating system- this issue appears when the workload's operating system is not
supported.
l Unsupported agent - this issue appears when the version of the protection agent on the
workload is outdated and does not support the remote desktop functionality.
l Insufficient quota - this issue appears when there is not enough service quota in the tenant to
assign to the selected workloads.

If the remote management plan is applied to up to 150 individually selected workloads, you will be
prompted to resolve the existing conflicts before saving the plan. To resolve a conflict, remove the

957 © Acronis International GmbH, 2003-2024

root cause for it or remove the affected workloads from the plan. For more information, see
"Resolving compatibility issues with remote management plans" (p. 958). If you save the plan
without resolving the conflicts, it will be automatically disabled for the incompatible workloads, and
alerts will be shown.

If the remote management plan is applied to more than 150 workloads or to device groups, first it
will be saved, and then checked for compatibility. The plan will be automatically disabled for the
incompatible workloads, and alerts will be shown.

Resolving compatibility issues with remote management plans

Depending on the cause of the compatibility issues, you can perform different actions to resolve the
compatibility issues as a part of the process of creating a new remote management plan.

Note
When resolving a compatibility issue by removing workloads from a plan, you cannot remove
workloads that are part of a device group.

To resolve the compatibility issues

1. Click Review issues.

2. [To resolve compatibility issues with existing remote management plans by removing workloads
from the new plan]
a. On the Conflicting plans tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
3. [To resolve compatibility issues with remote management plans by disabling the plans that are
already applied on the workloads]
a. Click Disable applied plans.
b. Click Disable, and then click Close.
4. [To resolve compatibility issues with incompatible operating systems]
a. On the Incompatible operating system tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
5. [To resolve compatibility issues with unsupported agents by removing workloads from the plan]
a. On the Unsupported agents tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
6. [To resolve compatibility issues with unsupported agents by updating the agent version] Click Go
to the Agents list.

Note
This option is available only for customer administrators.

958 © Acronis International GmbH, 2003-2024

7. [To resolve compatibility issues with insufficient quota by removing workloads from the plan]
a. On the Insufficient quota tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
8. [To resolve compatibility issues with insufficient quota by increasing the quota of the tenant]

Note
This option is available only for partner administrators.

a. On the Insufficient quota tab, click Go to the Management portal.

b. Increase the service quota for the customer.

Workload credentials
You can add administrator or non-administrator credentials of the remote workloads (username
and password, or VNC password), save them in the cloud credentials store, and then use them for
automatic authentication when connecting to the workloads that you manage. In that way, instead
of entering these credentials manually every time during the authentication step of the connection,
you can save them in the credentials store once, assign them to multiple workloads, and then the
Connect Client will use these credentials every time you want to connect to the workloads remotely.

Note
The credentials that are stored in the credentials store are not shared between different tenant
levels. They are shared only on the same tenant level for the same customer tenant or partner
tenant.

This means that if a customer tenant has several administrators, they will see and share the
credentials in the credentials store, while any other partner administrators, or customer
administrators of other tenants will not be able to view or use these credentials.

Adding credentials
You can add credentials and then use them for remote connections to multiple workloads.

To add credentials to a workload and save them in the Credentials store

1. In the Cyber Protect console, go to Devices > All devices.

2. Click the workload for which you want to add credentials.
3. Access the Settings menu in one of the following ways:
l Click Remote desktop, and then click Settings.
l Click Manage, and then click Settings.
4. Click Add credentials.
5. In the Credentials store, click Add credentials.

959 © Acronis International GmbH, 2003-2024

6. Enter the credentials.

Field Description

Credentials Identifier of the credentials that will be visible in the credentials store.
name

Username Username that will be used for remote connections to the target
workload.

Password Password that will be used for remote connections to the target
workload.

VNC password This field is available for Apple Screen Sharing only.

7. Click Save.

Assigning credentials to a workload

After you add credentials, you can use them to authenticate automatically when you connect to a
workload that you manage.

To assign saved credentials for automatic authentication to a workload

1. In the Cyber Protect console, go to Devices > All devices.

2. Access the Settings menu in one of the following ways:
l Click Remote desktop, and then click Settings.
l Click Manage, and then click Settings.
3. On the tab of the supported protocol (NEAR, RDP, or Apple Screen Sharing), click Add
credentials.
4. In the Credentials store, select the credentials from the list, and then click Select credentials.

Deleting credentials
You can delete credentials that are not needed anymore.

To delete credentials from the Credentials store

1. In the Cyber Protect console, go to Devices > All devices.

2. Access the Settings menu in one of the following ways:
l Click Remote desktop, and then click Settings.
l Click Manage, and then click Settings.
3. On the tab of the supported protocol (NEAR, RDP, or Apple Screen Sharing), click Delete.
4. In the confirmation window, click Delete.

Unassigning credentials from a workload

You can unassign credentials from a workload, but still keep them in the Credentials store.

960 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Devices > All devices.
2. Access the Settings menu in one of the following ways:
l Click Remote desktop, and then click Settings.
l Click Manage, and then click Settings.
3. On the tab of the supported protocol (NEAR, RDP, or Apple Screen Sharing), click Unassign.
4. In the confirmation window, click Unassign.

Working with managed workloads

Managed workloads are workloads on which the Protection agent is installed.

You can perform the following actions on the remote managed workloads:

l connect for remote assistance or remote desktop by using NEAR in control or view-only mode
l connect for remote desktop by using RDP in control mode
l connect for remote assistance or remote desktop by using Apple Screen Sharing in control, view-
only, or curtain mode
l connect for remote desktop via a web client
l restart, shut down, sleep, empty recycle bin, log out remote user from the remote workloads
l transfer files between your workload and the remote workloads
l monitor them by taking screenshots

Note
The remote desktop connections to managed workloads require installing a Protection agent and
applying a remote management plan on the workload.

Configuring RDP settings

You can configure the settings that will be applied automatically for remote control RDP connections
to the managed workload.

To configure the RDP settings of a workload

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. Access the Settings menu in one of the following ways:
l Click Remote desktop, and then click Settings.
l Click Manage, and then click Settings.

961 © Acronis International GmbH, 2003-2024

3. On the RDP tab, configure the settings.

Setting Description

Audio This setting enables or disables the redirection of the remote workload
playback sound on your local workload.

Audio This setting determines whether audio recording (speaking to the

recording microphone) will be transferred to the remote workload.

Redirect If you select this setting, the printers from your workload will be available on
printers the remote workload.

Redirect This setting defines whether files from your local workload will be shared to
files remote workload.

Color This setting determines the number of colors in the picture that RDP will
depth transfer. Higher value requires higher bandwidth.
High color: 16 bit
True color:
l 24 bit for RDP connections via the web client
l 32 bit for RDP connections via Connect Client

4. Click the close button.

Connecting to managed workloads for remote desktop or remote

assistance

Note
The availability of the connection protocols that you can use for remote connections depends on
the remote management plan configuration and on the remote workload's operating system.

Prerequisites
l A remote management plan with the corresponding connection protocol enabled is applied on
the managed workload.
l The required service quota is assigned to workload. (The service quota is automatically acquired
when you apply a remote management plan to workload.)
l [For Apple Screen Sharing connections] Apple Screen Sharing is enabled on the macOS workload.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.

To remotely connect to a managed workload for remote desktop or remote assistance

1. In the Cyber Protect console , go to Devices > Machines with agents.

2. Click the workload to which you want to connect.
3. Click Remote desktop.
By default, NEAR is selected as a connection protocol.

962 © Acronis International GmbH, 2003-2024

4. [Optional] In the Connection protocol drop-down list, select the connection protocol that you
want to use.
5. Click the view mode that you want to use.

Protocol Remote View mode Supported

connections remote
to action

NEAR Windows Control- In this mode, you will be able to Remote

Linux observe and perform operations on the desktop
macOS remote workload. Remote
View-only- In this mode, you will be only assistance
able to observe the remote workload.

RDP Windows Control- In this mode, you will be able to Remote

view and perform operations on the remote desktop
workload.

Note
If RDP is disabled in the OS settings of the
workload, a pop-up window will appear. Use
this window to enable RDP for the workload
for the current session or in general:
l If you want to enable RDP for this
workload only for the current session,
select Disable it after the session is
over, and then click Allow.
l If you want to enable RDP for this
workload, click Allow.

Apple macOS Control- In this mode, you will be able to Remote

Screen observe and perform operations on the desktop
Sharing remote workload. Remote
View-only- In this mode, you will be only assistance
able to observe the remote workload.
Curtain - available only for macOS
workloads. If you connect to the remote
workload in curtain mode, the display of the
remote workload will be dimmed, and the
remote user will not be able to see your
actions on the workload.

6. Depending on whether or not Connect Client is installed on your workload, do one of the
following:
l If Connect Client is not installed, download it, install it, and then in the confirmation pop-up
that appears, select Allow.

963 © Acronis International GmbH, 2003-2024

 l If Connect Client is already installed, in the confirmation pop-up that appears, click Open
Connect Client.
7. In the Authentication window, select an authentication option, and then provide the required
credentials.

Note
If you have assigned credentials to the workload, authentication will be done automatically and
this step will be skipped. For more information, see "Assigning credentials to a workload" (p.
960).

Authentication Description
option

With remote You will be allowed to establish the remote connection after you
workload provide username and password of an administrator user of the
credentials remote workload.
This option is available for NEAR, RDP, and Apple Screen Sharing.
You can use this option to authenticate for remote desktop and
remote assistance.

Ask for You will be allowed to establish the remote connection in observe
permission to mode after the user who is logged in on the remote workload allows it.
observe This option is available for NEAR and Apple Screen Sharing.
You can use this option to authenticate for remote assistance.

Ask for You will be allowed to establish the remote connection in control mode
permission to after the user who is logged in on the remote workload allows it.
control This option is available for NEAR and Apple Screen Sharing.
You can use this option to authenticate for remote assistance.

8. Click Connect, and then click the session to display (if more than one user session is available on
the workload).
Connect Client will open a new viewer window on which you will be able to see the remote
workload's desktop. The viewer has a toolbar with additional actions that you can perform on
the remote workload after the remote connection is established. For more information, see
"Using the toolbar in the Viewer window" (p. 972).

Connecting to a managed workload via a web client

You can establish a remote desktop connection to a managed workload via a web client.

Prerequisites
l Standard service quota is assigned to the workload.
l A remote management plan that has RDP enabled is applied to the managed workload.
l RDP is enabled on the managed workload.

964 © Acronis International GmbH, 2003-2024

l Your browser supports HTML5.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.

To remotely connect to a workload via a web client

1. In the Cyber Protect console, go to Devices > All devices.

2. Click the workload which you want to connect remotely, and then click Remote
desktop>Connect via web client.
3. Enter the login and password to access the workload, and then click Connect.

Note
If you have assigned credentials to the workload, authentication will be done automatically and
this step will be skipped. For more information, see "Assigning credentials to a workload" (p.
960).

Transferring files
You can easily transfer files between the local workload and a managed workload.

Prerequisites
l A remote management plan that has the NEAR protocol and File transfer enabled is applied on
the workload.
l Advanced Management quota is applied on the workload.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.

To remotely transfer files between your workload and a managed workload

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. Click the workload with which you want to transfer files.
3. Click Manage, and then Transfer files.
4. Depending on whether or not Connect Client is installed on your workload, do one of the
following:
l If Connect Client is not installed, download it, install it, and then in the confirmation pop-up
that appears, click Allow.
l If Connect Client is already installed, in the confirmation pop-up that appears, click Open
Connect Client.
5. In the Authentication window, select an authentication option, and then provide the required
credentials.

Authentication Description
option

With remote You will be allowed to establish the remote connection after you
workload provide username and password of an administrator user of the
credentials remote workload.

965 © Acronis International GmbH, 2003-2024

 Authentication Description
option

Ask for You will be allowed to transfer files after the user who is logged in on
permission to the remote workload allows it.
transfer files

6. In the File transfer window, browse files and drag and drop them to the desired destination.

Note
The files of the local workload are listed in the left pane, and the files of the remote workload are
listed in the right pane.
When a file transfer begins, it is listed in the Tasks pane.

7. [Optional] If you want to remove the completed tasks from the Tasks pane, click Clear finished.
8. When all transfers complete, close the window.

Performing control actions on managed workloads

You can manage a remote workload by performing the following basic control actions on it: empty
recycle bin, sleep, restart, shut down, and log out remote user.

Prerequisites
l Standard service quota is applied to the workload.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.

Empty recycle bin

To empty the recycle bin on the remote workload

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. Click the workload on which you want to perform this action.
3. Click Manage, and then click Empty recycle bin.
4. Select the user session for which you want to perform this action, and then click Empty recycle
bin.

Sleep

To put a remote workload to sleep

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. Click the workload on which you want to perform this action.
3. Click Manage, and then click Sleep.

Restart

To restart a remote workload

966 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Devices > Machines with agents.
2. Click the workload on which you want to perform this action.
3. Click Manage, and then click Restart.
l For Windows workloads, select if you want to allow the user who is currently logged in locally
to the workload to save the changes before the workload is restarted, select the user, and
then click Restart again.
l For macOS workloads, select if you want to allow the user who is currently logged in locally to
the workload to save the changes before the workload is restarted, and then click Restart
again.
l For Linux workloads, click Restart.

Shut down

To shut down a remote workload

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. Click the workload on which you want to perform this action.
3. Click Manage, and then click Shut down.
l For Windows workloads, select if you want to allow the user who is currently logged in locally
to the workload to save the changes before the workload is shut down, select the user, and
then click Shut down again.
l For macOS workloads, select if you want to allow the user who is currently logged in locally to
the workload to save the changes before the workload is shut down, and then click Shut
down again.
l For Linux workloads, click Shut down again.

Log out remote user

To log out the user of a remote workload

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. Click the workload on which you want to perform this action.
3. Click Manage, and then click Log out remote user.
4. Select the user that you want to log out, and then click Log out.

Monitoring workloads via screenshot transmission

You can monitor the status of a workload by using the Screenshot transmission feature.

Prerequisites
l A remote management plan with the Screenshot transmission feature enabled is applied on the
workload.
l The Protection agent version is up-to-date and supports the Screenshot transmission feature.
l Advanced Management service quota is applied on the workload.

967 © Acronis International GmbH, 2003-2024

l The workload is online.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.

Monitoring a workload via Screenshot transmission

To monitor a workload via Screenshot transmission

1. In the Cyber Protect console, go to Devices>Screenshot transmission.

2. Click the workload that you want to monitor.
3. Select the user session.
4. Select the display.
5. Select refresh rate at which to take a new screenshot of the desktop.
6. Select the image quality.
7. To download the screenshot, click the download icon.

Taking a screenshot of a workload

To take a screenshot of a managed workload

1. In the Cyber Protect console, go to Devices > Machines with agents.

2. Click the workload from which you want to take a screenshot.
3. Click Manage, and then click Take desktop screenshot.
The Screenshot transmission screen will open, with the workload preselected. Depending on
the settings of the remote management plan that is applied on the workload, you will see the
screenshot or you will see the screenshot after the user of the remote workload approves the
request.

Observing multiple managed workloads simultaneously

You can observe the desktops of multiple remote workloads simultaneously in a single window.

Note
The number of desktops that you can see simultaneously in the window depends on the size of
your monitor.

Prerequisites
l NEAR / Apple Screen Sharing is enabled in the remote management plans that are applied to the
workloads.
l Advanced Management service quota is applied on the workload.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.

To observe multiple workloads simultaneously

1. In the Cyber Protect console, go to Devices > All devices.

2. Select the workloads which you want to observe.
3. Click Multi view.

968 © Acronis International GmbH, 2003-2024

4. Depending on whether or not Connect Client is installed on your workload, do one of the
following:
l If Connect Client is not installed, download it, install it, and then in the confirmation pop-up
that appears, select Allow.
l If Connect Client is already installed, in the confirmation pop-up that appears, click Open
Connect Client.
5. In the Authentication window, select an authentication option, and then provide the required
credentials.

Authentication Description
option

With remote You will be allowed to establish the remote connection after you
workload provide username and password of an administrator user on the
credentials remote workload.

Ask for You will be allowed to establish the remote connection in observe
permission to mode after the user who is logged in on the remote workload allows it.
observe

6. If you want to use the same authentication method and credentials when connecting to all the
remote workloads that you selected in step 2, select Use on other computers.
7. Click Connect.
In toolbar of the multi-view window, you can select a view mode in which to connect to a
workload. This action will open a separate Viewer window for that workload.

Note
If any of the selected workloads is offline, or has an outdated version of the agent installed, it will
not be shown in the multi-view window.
All multi-view connections to remote workloads are in View-only mode.

Working with unmanaged workloads

Unmanaged workloads are workloads on which the Protection agent is not installed.

You can perform the following actions on the unmanaged remote workloads:

l connect for remote assistance by using Acronis Quick Assist

l connect for remote desktop or remote assistance by using an IP address
l transfer files between your workload and the remote workload by using Quick Assist

Note
The remotely connect to unmanaged workloads by using Quick Assist, ensure that:

l The Advanced Management pack is activated for your customer tenant.

l The Quick Assist application is running on the remote workload to which you want to connect.

969 © Acronis International GmbH, 2003-2024

Connecting to unmanaged workloads via Acronis Quick Assist
You can use the Quick assist feature to connect remotely on demand to unmanaged workloads and
provide one-time assistance.

Prerequisites
l The Advanced Management pack is assigned to your customer tenant.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.
l The remote user has provided the workload ID and access code from Quick Assist.
l The remote user has downloaded and run Acronis Quick Assist.

To connect to a workload for remote assistance by using Quick Assist

1. In the Cyber Protect console, go to Devices > All devices.

2. Click Quick Assist.
3. In the Quick Assist window, enter the workload ID that the end user gave you, and then select
Connect.
4. Click Connect.
5. Depending on whether or not Connect Client is installed on your workload, do one of the
following:
l If Connect Client is not installed, download it, install it, and then in the confirmation pop-up
that appears, select Allow.
l If Connect Client is already installed, in the confirmation pop-up that appears, click Open
Connect Client.
6. In the Authentication window, enter the access code.
7. Connect Client will open a new viewer window on which you will be able to see the remote
workload's desktop. The viewer has a toolbar with additional actions that you can perform on
the remote workload after the remote connection is established. For more information, see
"Using the toolbar in the Viewer window" (p. 972).

Connecting to unmanaged workloads via IP address

If an unmanaged workload is in your LAN, you can connect to it for remote control or remote
assistance by using its IP address. This connection does not require Internet access.

Prerequisites
l The Advanced Management pack is assigned to your customer tenant.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.

To connect to a workload for remote desktop or remote assistance by using its IP address

1. In the Cyber Protect console, go to All devices.

2. Click Quick Assist.

970 © Acronis International GmbH, 2003-2024

3. Click the Via IP address tab.
4. Enter the workload's IP address and port.
5. Select a connection protocol - RDP (Windows workloads) or Apple Screen Sharing (for macOS
workloads), depending on the remote workload's operating system.

Note
Connections via RDP support the remote desktop action, and connections via Apple Screen
Sharing support both the remote desktop and remote assistance actions.

6. Click Connect.
7. In the Authentication window, provide the required credentials.

For Apple Screen Sharing connections, Connect Client will open a new viewer window on which you
will be able to see the remote workload's desktop. The viewer has a toolbar with additional actions
that you can perform on the remote workload after the remote connection is established. For more
information, see "Using the toolbar in the Viewer window" (p. 972).

Transferring files via Acronis Quick Assist

You can use the Quick assist feature to transfer files between your workload and unmanaged
workloads.

Prerequisites
l The Advanced Management pack is assigned to your customer tenant.
l 2FA is enabled for your user account in Acronis Cyber Protect Cloud.
l The remote user has downloaded and run Acronis Quick Assist.
l The remote user has provided the computer ID and access code from Quick Assist.

To transfer files to a workload by using Quick Assist

1. In the Cyber Protect console, go to Devices > All devices.

2. Click Quick assist.
3. In the Quick assist window, enter the workload ID that the end user gave you, and then select
File Transfer.
4. Click Connect.
5. Depending on whether or not Connect Client is installed on your workload, do one of the
following:
l If Connect Client is not installed, download it, install it, and then in the confirmation pop-up
that appears, select Allow.
l If Connect Client is already installed, in the confirmation pop-up that appears, click Open
Connect Client.
6. In the Authentication window, enter the access code.
7. In the File transfer window, browse files and drag and drop them to the desired destination.

971 © Acronis International GmbH, 2003-2024

 Note
The files of the local workload are listed in the left pane, and the files of the remote workload are
listed in the right pane.
When a file transfer begins, it is listed in the Tasks pane.

8. [Optional] If you want to remove the completed tasks from the Tasks pane, click Clear finished.
9. When all transfers complete, close the window.

Using the toolbar in the Viewer window

After you connect to a remote workload, you can use the toolbar of the viewer window to quickly
perform the different actions.

Icon Description

Actual size

Scales the remote workload's desktop so that one pixel of the remote
desktop corresponds to one pixel on the viewer window.

Zoom to fit

Scales the remote workload desktop to fit the viewer window.

Lock and Unlock screen

Shows a placeholder on the remote workload's display so that the

remote user will not see your actions.

Take screenshot

Save the remote server's desktop image to a local file.

Select display

Select the remote workload display that you want to view and the
desired resolution.

Available for Apple Screen Sharing connections to macOS, and NEAR

connections to any operating system.

Image quality

Adjusts the remote screen image quality from black and white to the
highest possible on Apple Screen Sharing connections.

NEAR image quality

Adjusts the quality/performance ratio on NEAR connections. The left

side of the slider (Smooth) prioritizes performance over image
quality, the right one (Sharp) means the best quality of remote
desktop screen, but probably worse performance.

972 © Acronis International GmbH, 2003-2024

 Icon Description

Send Ctrl+Alt+Del

Sends a Ctrl + Alt + Delete sequence to the remote workload.

Available for Windows and Linux workloads.

File Transfer

Opens the File Manager window to exchange files between remote

and local workload. Available for NEAR connections.

Pin toolbar

Turns off automatic hiding of viewer toolbar.

Available for Windows workloads.

Full screen

Switches to the full screen mode and scales the remote workload to
completely fill your local screen.

Available for Windows workloads.

Close

Closes the Viewer window and ends the remote control session.

Available for Windows workloads.

Depending on connection type, additional options might be available when you click the Other icon.

Option Description

Start recording / Record the current remote desktop session.

Stop recording
Session recordings are saved as .crec files on the local workload. You
can open .crec files with Acronis Connect Client.

Available for NEAR connections

Clipboard auto sync When this option is on, the client will automatically synchronize your
local clipboard and the clipboard of the remote computer.

Available for NEAR and Apple Screen Sharing connections

Send clipboard Send Clipboard replaces the remote computer clipboard contents
with the contents of the local clipboard.
Get clipboard
Get Clipboard transfers the contents of the remote computer
clipboard to the local clipboard.

Smart keyboard / Changes the keyboard input mode for the current connection.
Raw keys / Raw keys
Smart keyboard- the client transmits Unicode codes of the locally
with all shortcuts
typed symbols to the remote computer

973 © Acronis International GmbH, 2003-2024

 Option Description

Raw keys- the client uses the raw codes of the keyboard buttons you
press.

Raw keys with all shortcuts- the client disables local system
shortcuts so that they are also transmitted to the remote operating
system.

Keyboard focus on When enabled, the client only captures the keyboard input while your
mouse hover local mouse cursor is placed over the Viewer window.

When disabled, the client captures your keyboard whenever its

window is active.

Show connection When Show connection info is selected, a small information panel
info / Hide will appear over the remote desktop screen, showing the most
connection info essential information about current connection.

Remote sound Enables the client to redirect the sound from the remote computer to
the local one.

Available for NEAR connections

Preferences Configure the settings of Connect Client. For more information, see
"Configuring the Connect Client settings" (p. 975).

Recording and playing remote sessions

You can record a remote session via NEAR in Acronis Connect Client.

To record a remote session

1. On the Viewer toolbar in Connect Client, click Other, and select Start Recording.
2. Select a name and location for the record.
By default, the file will be named with the current date and time and located in the Documents
folder in the current user home directory. While the recording is active, in the Viewer toolbar
you will see a flashing red circle over the top right corner of the remote screen and the recording
timer.
3. To stop the recording, click Other, and then click Stop Recording. On a Mac, you can also click
Stop on the toolbar.
All .crec files made by Acronis Connect Client will be opened with Acronis Connect Client by
default.

To play a recording

1. Locate a recording file.

2. Open it.

974 © Acronis International GmbH, 2003-2024

 The recording player of Acronis Connect Client opens. Note that it is not possible to navigate
through the recording. To find a certain moment in the recording, wait until the player reaches it.

3. [Optional] To adjust playback speed, use the << and >> icons in the playback controls section.
The recording is stored as a sequence of events that have been transmitted to and from the
remote server during a connection. This ensures the best quality of the recording at the
minimum file size. However, this also means that it is not possible to navigate through the
recording. At the moment it is also not possible to convert the recordings to a video format.

Configuring the Connect Client settings

After you install Connect Client on your workload, you can configure its settings according to your
preferences.

To configure the settings of Connect Client

1. In the start menu, find Connect Client, and start it.

2. Configure the settings on the General tab.

Option Description

Write Select this option to allow Connect Client to write verbose logs. If disabled, the
verbose client will only write general information to the log file.
logs

Proxy Select whether to use the default System proxy, or configure a Custom
settings SOCKSS proxy.

3. Configure the settings on the Viewer tab.

Option Description

Ask for Select this option if you want Connect Client to display a confirmation
confirmation message when you attempt closing the Viewer window in order to
when closing a prevent accidental closing.
viewer

When minimized Select whether to suspend the Viewer activity when minimized, in
order to reduce the CPU load.

When maximized Select whether to enable the full screen mode when maximized.

Clipboard Enable showing the Clipboard transfer indicator in the Viewer window
transfer whenever you copy or paste text and images.

Keyboard Mode Enable showing the Input mode indicator in the Viewer window title
whenever mouse and keyboard events are being sent to the remote
machine.

Clipboard Select Automatically synchronize clipboard to enable automatic

975 © Acronis International GmbH, 2003-2024

 Option Description

clipboard synchronization, when available.

Send keyboard Choose whether to grab your local keyboard input whenever the
events Connect Client window is active or only when your local mouse
pointer is over it.

Viewer Change the Viewer window background color.

background color

Reconnect Select Enable to reconnect automatically, if you want Connect

automatically Client to automatically re-establish the connection if it has been
interrupted.

H.264 You can disable hardware decoders.

Close when idle Select the time interval of being idle after which to close the Viewer
window.

4. Configure the settings on the Keyboard tab.

Option Description

Modifier Change the behavior of modifier keys with a pop-up menu. These settings
mappings are stored separately for NEAR, Apple Screen Sharing, and RDP connections.

Input mode For each type of connection (selected in the header of pane), select the
default keyboard input mode.

5. Click OK.

The remote desktop notifiers

The Connect Agent displays action dialogs (notifiers) on the remote workload's desktop in the
following cases:

l when you try to connect to the workload remotely by asking for permission to observe. The user
who is logged in to the remote workload locally can allow or deny the request.

l when you try to connect to the workload remotely by asking for permission to control. The user
who is logged in to the remote workload locally can allow or deny the request.

976 © Acronis International GmbH, 2003-2024

l when you try to exchange files between your workload and the remote workload by asking for
permission to transfer files. The user who is logged in to the remote workload locally can allow or
deny the request.

When you establish a remote desktop connection to a workload, the user who is logged in to the
workload will view a different connection notifier that contains the following information:

l name of the user who is connected remotely

l connection protocol that is used to establish the remote connection
l duration of the remote connection

The user who is logged in to the remote workload locally can end the connection at any time by
clicking the Disconnect icon or the Close icon.

977 © Acronis International GmbH, 2003-2024

Monitoring the health and performance of
workloads
You can monitor the system parameters and the health of the workloads in your organization. If a
parameter is out of norm, you will be notified immediately and will be able to quickly resolve the
issue. You can also configure custom alerts and automatic response actions. These are actions that
will be performed automatically to resolve anomalies in workload behavior.

Note
The monitoring functionality requires an installation of Protection agent version 15.0.35324 or later
on the workloads.

Monitoring plans
To start monitoring the performance, hardware, software, system, and security parameters of your
managed workloads, apply a monitoring plan to them. The monitoring plans consist of different
monitors that you can enable and configure. Some monitors support the anomaly-based
monitoring type. For more information about monitoring plans, see "Monitoring plans" (p. 1010).
For more information about the available monitors that you can configure in the monitoring plans,
see "Configurable monitors" (p. 979).

If the agent cannot collect data from a workload for some reason, the system will generate an alert.

Monitoring types
You must configure the monitoring type for each monitor that you enable in the plan. The
monitoring type determines the algorithm that the monitor will use to estimate the normal behavior
and deviation of the workload. There are two monitoring types: threshold-based and anomaly-
based. Some monitors support only the threshold-based monitoring type.

Threshold-based monitoring tracks if the values of the parameters are above or below a threshold
value that you configure. With this monitoring type, you are responsible for defining the correct
threshold values for the workloads. The system determines the normal behavior based on these
static threshold values and without considering other specific conditions that might cause the
behavior. For this reason, threshold-based monitoring might be less accurate as compared to
anomaly-based monitoring.

Anomaly-based monitoring uses machine learning to create the normal behavior patterns for a
workload and to detect abnormal behavior. For more information, see "Anomaly-based monitoring"
(p. 978).

Anomaly-based monitoring
Anomaly-based monitoring uses machine learning models to create the normal behavior patterns
for a workload and to detect anomalies (unexpected spikes in the time-series data) in the workload's

978 © Acronis International GmbH, 2003-2024

behavior. When you activate this monitoring type, the system creates a model and starts training
itself and adjusting the model for the specific workload based on the data that it collects from the
workload. This means that at the beginning of the training period, the data might not be fully
accurate. Creating a reliable model requires at least three weeks of training of the model. As the
system collects more data and analyzes historical data sets, it gradually refines the model and
creates the dynamic upper and lower thresholds for each metric of the workload. This monitoring
type is more flexible as compared to the threshold-based monitoring because the system monitors
the values of the parameters and their context. For example, it might be normal for a specific
workload to have bigger load in certain hours of the day. A threshold-based monitoring type would
falsely interpret this as an abnormal behavior and would trigger an alert.

You can reset the machine learning models of a workload. In this case, the system will delete all data
and models for the monitors that are applied to the workload. For more information, see "Resetting
the machine learning models" (p. 1019).

Supported platforms for monitoring

The monitoring functionality is supported for the following operating systems.

Supported Windows versions Supported macOS versions

l Windows 7 SP1 l macOS 10.14 (Mojave)

l Windows 8, 8.1 l macOS 10.15 (Catalina)
l Windows 10 l macOS 11.x (Big Sur)
l Windows 11 l macOS 12.x (Monterey)
l Windows Server 2008 R2 l macOS 13.x (Ventura)
l Windows Server 2012
l Windows Server 2012 R2
l Windows Server 2016
l Windows Server 2019
l Windows Server 2022

Configurable monitors
The monitoring functionality supports the following monitors, divided into six categories: Hardware,
Performance, Software, System, Security, and Custom.

Monitor Description Supported Frequency Support of Availability in

operating of data anomaly- Standard
systems collection based protection or
monitoring Advanced
Management

Hardware

Disk space Monitors the Windows 1 minute Yes Standard

979 © Acronis International GmbH, 2003-2024

 Monitor Description Supported Frequency Support of Availability in
operating of data anomaly- Standard
systems collection based protection or
monitoring Advanced
Management

free space on macOS protection

a specific
drive of the
workload.

CPU Monitors the Windows 30 sec Yes Advanced

temperature CPU Management
macOS
temperature.

GPU Monitors the Windows 30 sec Yes Advanced

temperature GPU Management
macOS
temperature.

Hardware Monitors the Windows 24 hours No Standard

changes hardware protection
macOS
changes, such
as adding,
removing, or
replacing
hardware on a
workload

Performance

CPU usage Monitors the Windows 30 sec Yes Advanced

overall CPU Management
macOS
usage (by all
CPUs on the
workload).

Memory Monitors the Windows 30 sec Yes Advanced

usage overall Management
macOS
memory
usage (by all
memory slots
on the
workload).

Disk transfer Monitors the Windows 30 sec Yes Advanced

rate read and write Management
macOS
speed of each
physical disk
on the
workload.

980 © Acronis International GmbH, 2003-2024

 Monitor Description Supported Frequency Support of Availability in
operating of data anomaly- Standard
systems collection based protection or
monitoring Advanced
Management

Network Monitors the Windows 30 sec Yes Advanced

usage incoming and Management
macOS
outgoing
traffic for each
network
adapter of the
workload.

CPU usage by Monitors the Windows 30 sec No Advanced

process CPU usage by Management
macOS
certain
process.

Memory Monitors the Windows 30 sec No Advanced

usage by memory Management
macOS
process usage by the
selected
process.

Disk transfer Monitors the Windows 30 sec No Advanced

rate by read and write Management
macOS
process speed of the
selected
process.

Network Monitors the Windows 30 sec No Advanced

usage by incoming and Management
macOS
process outgoing
traffic of the
selected
process.

Software

Windows Monitors the Windows 30 sec No Advanced

service status status of the Management
selected
Windows
service
(Running or
Stopped).

Process Monitors the Windows 30 sec No Advanced

status status of the Management

981 © Acronis International GmbH, 2003-2024

 Monitor Description Supported Frequency Support of Availability in
operating of data anomaly- Standard
systems collection based protection or
monitoring Advanced
Management

selected macOS
process
(Running or
Stopped).

Installed Monitors the Windows 24 hours No Advanced

software installation, Management
macOS
update, or
deletion of
software
applications.

System

Last system Monitors Windows 1 hour No Standard

restart when the protection
macOS
workload was
restarted.

Windows Monitors Windows 10 min No Advanced

event log specific Management
business-
critical events
in the
Windows
event logs.

Files and Monitors the Windows 10 min No Standard

folders size total size of protection
macOS
the selected
files or
folders.

Security

Windows Monitors the Windows 15 min No Advanced

Update Windows Management
status Update status
of the
workload and
whether the
latest updates
are installed.

982 © Acronis International GmbH, 2003-2024

 Monitor Description Supported Frequency Support of Availability in
operating of data anomaly- Standard
systems collection based protection or
monitoring Advanced
Management

Firewall Monitors the Windows 5 min No Advanced

status status of the Management
macOS
built-in or
third-party
firewall that is
installed on
the workload.

Antimalware Monitors the Windows 5 min No Advanced

software status of the Management
macOS
status built-in or
third-party
antimalware
software that
is installed on
the workload.

Failed logins Monitors Windows 1 hour No Advanced

unsuccessful Management
login attempts
on the
workload.

AutoRun Monitors if Windows 1 hour No Advanced

status the AutoRun Management
feature for
removable
storage media
is enabled.

Custom

Custom Monitors Windows custom No Advanced

custom Management
macOS
objects via
running
scripts.

Settings of the Disk space monitor

Disk space monitors the free space on a specific drive of the workload.

983 © Acronis International GmbH, 2003-2024

Note
When calculating the space, the monitor uses binary bytes (1024 bytes per KB, 1024 KB per MB, and
1024 MB per GB) for both Windows and macOS workloads.

You can configure the following settings for the monitor.

Setting Description

Threshold-based monitoring

Drive The drive that you want to monitor.

The following values are available.

l System drive —This is the default value.

l Any drive

Operator The operator is a conditional function that defines how to measure the
performance on the metric.

The following values are available.

l Less than —This is the default value.

l Less than or equal to

Disk free The threshold value and the Operator value determine the normal
space performance of the monitored metric. When the value of the monitored metric
threshold is out of the norm, the system generates an alert.

Enter an integer value in the range 1-100 (%). The default value is 20.

Include This setting is available if the Drive value is Any drive.

removable
Select this setting if you want to add removable drives, like USB flash drives, for
drives
monitoring. By default, the setting is disabled.

Time period The system will generate an alert for a detected issue only if the metric value is
out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 30.

Anomaly-based monitoring

Drive The drive that you want to monitor.

The following values are available.

l System drive —This is the default value.

l Any drive

Model The period during which the system will train the machine learning models
training based on the data that is collected from the agents, and will then create the
period normal behavior pattern of the workload. The longer the model training
period, the more precise the long-term behavior pattern that the system will

984 © Acronis International GmbH, 2003-2024

 Setting Description

create. We recommend that the minimum model training period is twenty-one

days.

Enter an integer value (days). The default value is 21.

Receive If you select this setting, you will receive alerts about anomalies during the
anomaly model training period. These alerts might be false, because the models are still
alerts being trained and might not be accurate enough.
during the
By default, the setting is selected.
training
period

Sensitivity The sensitivity level acts as a preliminary filter for anomalies if their values are
level within a specific range. This filter operates independently from the anomaly
detection algorithm. Its purpose is to stop the anomalies that are in the
specified range from being processed by the anomaly detection algorithm.

During the training period:

1. The algorithm is trained using the data that is collected during the training.
2. The algorithm performs anomaly detection on the training data.
3. A filtering process based on mean and standard deviation is applied.
4. Any anomalies that are in the specified interval are filtered.
5. From the remaining anomalous data points, the anomaly with the lowest
anomaly level is selected. This level (a float number between 0 and 1) is
recorded in the model.

During the prediction:

1. The algorithm predicts anomalies on the inference data.

2. The predicted anomalies are filtered based on the mean and standard
deviation, according to the sensitivity level.
3. The remaining anomalies are further filtered based on the following
principle: values above the threshold level are considered an anomaly,
while values below the threshold level are considered normal behavior.

The following values are available.

l Low — The low level equals the mean value and the standard deviation
value.
l Normal — This is the default value. The normal level equals the mean value
and two times the standard deviation value.
l High — The high level equals the mean value and three times the standard
deviation value.

Anomaly The system will generate an alert for a detected anomaly only if the abnormal
duration behavior persists for the specified period.

The default value is 30 minutes.

985 © Acronis International GmbH, 2003-2024

Settings of the CPU temperature monitor
CPU temperature monitors the CPU temperature of the workload.

You can configure the following settings for the monitor.

Setting Description

Threshold-based monitoring

CPU temperature has The maximum value of the monitored metric. If the value is
exceeded (C°) exceeded, the system generates an alert.

Enter an integer value (C°). The default value is 80.

Time period The system will generate an alert for a detected issue only if the
metric value is out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value
is 5.

Anomaly-based monitoring

Model training period The period during which the system will train the machine
learning models based on the data that is collected from the
agents, and will then create the normal behavior pattern of the
workload. The longer the model training period, the more
precise the long-term behavior pattern that the system will
create. We recommend that the minimum model training period
is twenty-one days.

Enter an integer value (days). The default value is 21.

Sensitivity level The sensitivity level acts as a preliminary filter for anomalies if
their values are within a specific range. This filter operates
independently from the anomaly detection algorithm. Its
purpose is to stop the anomalies that are in the specified range
from being processed by the anomaly detection algorithm.

During the training period:

1. The algorithm is trained using the data that is collected

during the training.
2. The algorithm performs anomaly detection on the training
data.
3. A filtering process based on mean and standard deviation is
applied.
4. Any anomalies that are in the specified interval are filtered.
5. From the remaining anomalous data points, the anomaly
with the lowest anomaly level is selected. This level (a float
number between 0 and 1) is recorded in the model.

986 © Acronis International GmbH, 2003-2024

 Setting Description

During the prediction:

1. The algorithm predicts anomalies on the inference data.

2. The predicted anomalies are filtered based on the mean and
standard deviation, according to the sensitivity level.
3. The remaining anomalies are further filtered based on the
following principle: values above the threshold level are
considered an anomaly, while values below the threshold
level are considered normal behavior.

The following values are available.

l Low — The low level equals the mean value and the standard
deviation value.
l Normal — This is the default value. The normal level equals
the mean value and two times the standard deviation value.
l High — The high level equals the mean value and three times
the standard deviation value.

Anomaly duration The system will generate an alert for a detected anomaly only if
the abnormal behavior persists for the specified period.

Enter an integer value in the range 1-60 (min). The default value
is 15.

Settings of the GPU temperature monitor

GPU temperature monitors the GPU temperature of the workload.

You can configure the following settings for the monitor.

Setting Description

Threshold-based monitoring

GPU The maximum value of the monitored metric. If the value is exceeded, the
temperature system detects an anomaly.
has exceeded
Enter an integer value (C°). The default value is 80.

Time period The system will generate an alert for a detected issue only if the metric value
is out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Anomaly-based monitoring

Model training The period during which the system will train the machine learning models
period based on the data that is collected from the agents, and will then create the
normal behavior pattern of the workload. The longer the model training

987 © Acronis International GmbH, 2003-2024

 Setting Description

period, the more precise the long-term behavior pattern that the system will
create. We recommend that the minimum model training period is twenty-
one days.

Enter an integer value (days). The default value is 21.

Sensitivity The sensitivity level acts as a preliminary filter for anomalies if their values
level are within a specific range. This filter operates independently from the
anomaly detection algorithm. Its purpose is to stop the anomalies that are in
the specified range from being processed by the anomaly detection
algorithm.

During the training period:

1. The algorithm is trained using the data that is collected during the
training.
2. The algorithm performs anomaly detection on the training data.
3. A filtering process based on mean and standard deviation is applied.
4. Any anomalies that are in the specified interval are filtered.
5. From the remaining anomalous data points, the anomaly with the lowest
anomaly level is selected. This level (a float number between 0 and 1) is
recorded in the model.

During the prediction:

1. The algorithm predicts anomalies on the inference data.

2. The predicted anomalies are filtered based on the mean and standard
deviation, according to the sensitivity level.
3. The remaining anomalies are further filtered based on the following
principle: values above the threshold level are considered an anomaly,
while values below the threshold level are considered normal behavior.

The following values are available.

l Low — The low level equals the mean value and the standard deviation
value.
l Normal — This is the default value. The normal level equals the mean
value and two times the standard deviation value.
l High — The high level equals the mean value and three times the
standard deviation value.

Anomaly The system will generate an alert for a detected anomaly only if the
duration abnormal behavior persists for the specified period.

Enter an integer value in the range 1-60 (min). The default value is 15.

988 © Acronis International GmbH, 2003-2024

Settings of the Hardware changes monitor
Hardware changes monitors the hardware changes, such as adding, removing, or replacing
hardware on a workload.

You can configure the following settings for the monitor.

Setting Description

Hardware Select one or multiple hardware components that you want to monitor for
components changes.

The following values are available.

l All — This is the default value.

l Motherboard
l CPU
l RAM
l Disk
l GPU
l Network adapter

What to Specify the changes for which you want to monitor the selected hardware
monitor components. You can select multiple items from the list.

The following values are available.

l Any change —This is the default value.

l Newly added components
l Replaced components
l Removed components

Settings of the CPU usage monitor

CPU usage monitors the total CPU usage (processor utilization) of the workload. If the workload has
multiple CPUs, the total CPU usage will be the sum of the CPU usage of each CPU.

You can configure the following settings for the monitor.

Setting Description

Threshold-based monitoring

Operator The operator is a conditional function that defines how to measure the
performance on the metric.

The following values are available.

l More than —This is the default value.

l More than or equal to

989 © Acronis International GmbH, 2003-2024

 Setting Description

l Less than
l Less than or equal to

CPU usage The threshold value and the Operator value determine the normal
threshold performance of the monitored metric. When the value of the monitored metric
is out of the norm, the system generates an alert.

Enter an integer value in the range 1-100 (%). The default value is 90.

Time period The system will generate an alert for a detected issue only if the metric value is
out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Anomaly-based monitoring

Model The period during which the system will train the machine learning models
training based on the data that is collected from the agents, and will then create the
period normal behavior pattern of the workload. The longer the model training period,
the more precise the long-term behavior pattern that the system will create.
We recommend that the minimum model training period is twenty-one days.

Enter an integer value (days). The default value is 21.

Receive If you select this setting, you will receive alerts about anomalies during the
anomaly model training period. These alerts might be false, because the models are still
alerts being trained and might not be accurate enough.
during the
By default, the setting is selected.
training
period

Sensitivity The sensitivity level acts as a preliminary filter for anomalies if their values are
level within a specific range. This filter operates independently from the anomaly
detection algorithm. Its purpose is to stop the anomalies that are in the
specified range from being processed by the anomaly detection algorithm.

During the training period:

1. The algorithm is trained using the data that is collected during the training.
2. The algorithm performs anomaly detection on the training data.
3. A filtering process based on mean and standard deviation is applied.
4. Any anomalies that are in the specified interval are filtered.
5. From the remaining anomalous data points, the anomaly with the lowest
anomaly level is selected. This level (a float number between 0 and 1) is
recorded in the model.

During the prediction:

1. The algorithm predicts anomalies on the inference data.

2. The predicted anomalies are filtered based on the mean and standard

990 © Acronis International GmbH, 2003-2024

 Setting Description

deviation, according to the sensitivity level.

3. The remaining anomalies are further filtered based on the following
principle: values above the threshold level are considered an anomaly,
while values below the threshold level are considered normal behavior.

The following values are available.

l Low — The low level equals the mean value and the standard deviation
value.
l Normal — This is the default value. The normal level equals the mean value
and two times the standard deviation value.
l High — The high level equals the mean value and three times the standard
deviation value.

Anomaly The system will generate an alert for a detected anomaly only if the abnormal
duration behavior persists for the specified period.
Enter an integer value in the range 1-60 (min). The default value is 15.

Settings of the Memory usage monitor

Memory usage monitors the total memory usage by all memory modules of the workload.

You can configure the following settings for the monitor.

Setting Description

Threshold-based monitoring

Operator The operator is a conditional function that defines how to measure the
performance on the metric.

The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Memory The threshold value and the Operator value determine the normal
usage performance of the monitored metric. When the value of the monitored metric
threshold is out of the norm, the system generates an alert.

Enter an integer value in the range 1-100 (%). The default value is 90.

Time period The system will generate an alert for a detected issue only if the metric value is
out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Anomaly-based monitoring

991 © Acronis International GmbH, 2003-2024

 Setting Description

Model The period during which the system will train the machine learning models
training based on the data that is collected from the agents, and will then create the
period normal behavior pattern of the workload. The longer the model training period,
the more precise the long-term behavior pattern that the system will create.
We recommend that the minimum model training period is twenty-one days.

Enter an integer value (days). The default value is 21.

Receive If you select this setting, you will receive alerts about anomalies during the
anomaly model training period. These alerts might be false, because the models are still
alerts being trained and might not be accurate enough.
during the
By default, the setting is selected.
training
period

Sensitivity The sensitivity level acts as a preliminary filter for anomalies if their values are
level within a specific range. This filter operates independently from the anomaly
detection algorithm. Its purpose is to stop the anomalies that are in the
specified range from being processed by the anomaly detection algorithm.

During the training period:

1. The algorithm is trained using the data that is collected during the training.
2. The algorithm performs anomaly detection on the training data.
3. A filtering process based on mean and standard deviation is applied.
4. Any anomalies that are in the specified interval are filtered.
5. From the remaining anomalous data points, the anomaly with the lowest
anomaly level is selected. This level (a float number between 0 and 1) is
recorded in the model.

During the prediction:

1. The algorithm predicts anomalies on the inference data.

2. The predicted anomalies are filtered based on the mean and standard
deviation, according to the sensitivity level.
3. The remaining anomalies are further filtered based on the following
principle: values above the threshold level are considered an anomaly,
while values below the threshold level are considered normal behavior.

The following values are available.

l Low — The low level equals the mean value and the standard deviation
value.
l Normal — This is the default value. The normal level equals the mean value
and two times the standard deviation value.
l High — The high level equals the mean value and three times the standard
deviation value.

Anomaly The system will generate an alert for a detected anomaly only if the abnormal

992 © Acronis International GmbH, 2003-2024

 Setting Description

duration behavior persists for the specified period.

Enter an integer value in the range 1-60 (min). The default value it 30 minutes.

Settings of the Disk transfer rate monitor

Disk transfer rate monitors the read and write speed of each physical disk on the workload.

You can configure the following settings for the monitor.

Setting Description

Threshold-based monitoring

What to Select the speed that you want to monitor.

monitor
The following values are available.

l Read speed and Write speed. This is the default value.

l Read speed
l Write speed

Read speed The operator is a conditional function that defines how to measure the
operator performance on the metric.

The following values are available.

l More than. This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Read speed The threshold value and the Operator value determine the normal
threshold performance of the monitored metric. When the value of the monitored metric
is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Read speed The system will generate an alert for a detected issue only if the metric value is
time period out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Write speed The operator is a conditional function that defines how to measure the
operator performance on the metric.

The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

993 © Acronis International GmbH, 2003-2024

 Setting Description

Write speed The threshold value and the Operator value determine the normal
threshold performance of the monitored metric. When the value of the monitored metric
is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Write speed The system will generate an alert for a detected issue only if the metric value is
time period out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Anomaly-based monitoring

Model The period during which the system will train the machine learning models
training based on the data that is collected from the agents, and will then create the
period normal behavior pattern of the workload. The longer the model training period,
the more precise the long-term behavior pattern that the system will create.
We recommend that the minimum model training period is twenty-one days.

Enter an integer value (days). The default value is 21.

Receive If you select this setting, you will receive alerts about anomalies during the
anomaly model training period. These alerts might be false, because the models are still
alerts being trained and might not be accurate enough.
during the
By default, the setting is selected.
training
period

What to Select the speed that you want to monitor.

monitor
The following values are available.

l Read speed and Write speed. This is the default value.

l Read speed
l Write speed

Sensitivity The sensitivity level acts as a preliminary filter for anomalies if their values are
level within a specific range. This filter operates independently from the anomaly
detection algorithm. Its purpose is to stop the anomalies that are in the
specified range from being processed by the anomaly detection algorithm.

During the training period:

1. The algorithm is trained using the data that is collected during the training.
2. The algorithm performs anomaly detection on the training data.
3. A filtering process based on mean and standard deviation is applied.
4. Any anomalies that are in the specified interval are filtered.
5. From the remaining anomalous data points, the anomaly with the lowest
anomaly level is selected. This level (a float number between 0 and 1) is
recorded in the model.

994 © Acronis International GmbH, 2003-2024

 Setting Description

During the prediction:

1. The algorithm predicts anomalies on the inference data.

2. The predicted anomalies are filtered based on the mean and standard
deviation, according to the sensitivity level.
3. The remaining anomalies are further filtered based on the following
principle: values above the threshold level are considered an anomaly,
while values below the threshold level are considered normal behavior.

The following values are available.

l Low — The low level equals the mean value and the standard deviation
value.
l Normal — This is the default value. The normal level equals the mean value
and two times the standard deviation value.
l High — The high level equals the mean value and three times the standard
deviation value.

Anomaly The system will generate an alert for a detected anomaly only if the abnormal
duration behavior persists for the specified period.
(Read
Enter an integer value in the range 1--60 (min).
speed)
The default value it 25.

Anomaly The system will generate an alert for a detected anomaly only if the abnormal
duration behavior persists for the specified period.
(Write
Enter an integer value in the range 1--60 (min).
speed)
The default value it 25.

Settings of the Network usage monitor

Network usage monitors the incoming and outgoing traffic for each network adapter of the
workload.

You can configure the following settings for the monitor.

Setting Description

Threshold-based monitoring

Traffic The traffic direction that you want to monitor.

direction
The following values are available.

l Incoming and Outgoing traffic. This is the default value.

l Incoming traffic
l Outgoing traffic

995 © Acronis International GmbH, 2003-2024

 Setting Description

Incoming The operator is a conditional function that defines how to measure the
traffic performance on the metric.
operator
The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Incoming The threshold value and the Operator value determine the normal
traffic performance of the monitored metric. When the value of the monitored metric
threshold is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Incoming The system will generate an alert for a detected issue only if the metric value is
traffic time out of the norm during the specified period.
period
Enter an integer value in the range 1-60 (min). The default value is 5.

Outgoing The operator is a conditional function that defines how to measure the
traffic performance on the metric.
operator
The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Outgoing The threshold value and the Operator value determine the normal
traffic performance of the monitored metric. When the value of the monitored metric
threshold is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Outgoing The threshold value and the Operator value determine the normal
traffic time performance of the monitored metric. When the value of the monitored metric
period is out of the norm, the system generates an alert.

Enter an integer value in the range 1-60 (min). The default value is 5.

Anomaly-based monitoring

Model The period during which the system will train the machine learning models
training based on the data that is collected from the agents, and will then create the
period normal behavior pattern of the workload. The longer the model training
period, the more precise the long-term behavior pattern that the system will
create. We recommend that the minimum model training period is twenty-one
days.

996 © Acronis International GmbH, 2003-2024

 Setting Description

Enter an integer value (days). The default value is 21.

Receive If you select this setting, you will receive alerts about anomalies during the
anomaly model training period. These alerts might be false, because the models are still
alerts being trained and might not be accurate enough.
during the
By default, the setting is selected.
training
period

Traffic l Incoming and Outgoing traffic. This is the default value.

direction l Incoming traffic
l Outgoing traffic

Sensitivity The sensitivity level acts as a preliminary filter for anomalies if their values are
level within a specific range. This filter operates independently from the anomaly
detection algorithm. Its purpose is to stop the anomalies that are in the
specified range from being processed by the anomaly detection algorithm.

During the training period:

1. The algorithm is trained using the data that is collected during the training.
2. The algorithm performs anomaly detection on the training data.
3. A filtering process based on mean and standard deviation is applied.
4. Any anomalies that are in the specified interval are filtered.
5. From the remaining anomalous data points, the anomaly with the lowest
anomaly level is selected. This level (a float number between 0 and 1) is
recorded in the model.

During the prediction:

1. The algorithm predicts anomalies on the inference data.

2. The predicted anomalies are filtered based on the mean and standard
deviation, according to the sensitivity level.
3. The remaining anomalies are further filtered based on the following
principle: values above the threshold level are considered an anomaly,
while values below the threshold level are considered normal behavior.

The following values are available.

l Low — The low level equals the mean value and the standard deviation
value.
l Normal — This is the default value. The normal level equals the mean value
and two times the standard deviation value.
l High — The high level equals the mean value and three times the standard
deviation value.

Anomaly The system will generate an alert for a detected anomaly only if the abnormal
duration behavior persists for the specified period.
(Incoming)

997 © Acronis International GmbH, 2003-2024

 Setting Description

Enter an integer value in the range 1--60 (min).

The default value it 25.

Anomaly The system will generate an alert for a detected anomaly only if the abnormal
duration behavior persists for the specified period.
(Outgoing)
Enter an integer value in the range 1--60 (min).

The default value it 25.

Settings of the CPU usage by process monitor

CPU usage by process monitors the CPU usage of the selected process. If there are multiple
instances of the same process, the system will monitor the total usage by all process instances and
will generate an alert when the conditions are met.

You can configure the following settings for the monitor.

Setting Description

Process Name of the process that you want to monitor. Enter the process name without
name the extension.

Operator The operator is a conditional function that defines how to measure the
performance on the metric.

The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Threshold The threshold value and the Operator value determine the normal
performance of the monitored metric. When the value of the monitored metric
is out of the norm, the system generates an alert.

Enter an integer value in the range 1-100 (%). The default value is 90.

Time period The system will generate an alert for a detected issue only if the metric value is
out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Settings of the Memory usage by process monitor

Memory usage by process monitors the memory usage of the selected process. If there are
multiple instances of the same process, the system will monitor the total usage by all process
instances and will generate an alert when the conditions are met.

998 © Acronis International GmbH, 2003-2024

Note
The agents use the total process working set (private and shared) to estimate the size of the
memory usage by process. That is why the size that the widget shows might be different from the
size of the memory usage that is shown in Windows Task Manager (private working set).

You can configure the following settings for the monitor.

Setting Description

Process Name of the process that you want to monitor. Enter the process name without
name the extension.

Operator The operator is a conditional function that defines how to measure the
performance on the metric.

The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Threshold The threshold value and the Operator value determine the normal
performance of the monitored metric. When the value of the monitored metric
is out of the norm, the system generates an alert.

Enter an integer value (kb). The default value is 1.

Time period The system will generate an alert for a detected issue only if the metric value is
out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Settings of the Disk transfer rate by process monitor

Disk transfer rate by process monitors the read and write speed of the selected process. If there
are multiple instances of the same process, the system will monitor the total usage by all process
instances and will generate an alert when the conditions are met.

You can configure the following settings for the monitor.

Setting Description

Process The name of the process that you want to monitor. Enter the process name
name without the extension.

What to The speed that you want to monitor.

monitor
The following values are available.

l Read speed and Write speed. This is the default value.

999 © Acronis International GmbH, 2003-2024

 Setting Description

l Read speed
l Write speed

Read speed The operator is a conditional function that defines how to measure the
operator performance on the metric.

The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Read speed The threshold value and the Operator value determine the normal
threshold performance of the monitored metric. When the value of the monitored metric
is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Read speed The system will generate an alert for a detected issue only if the metric value is
time period out of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 5.

Write The operator is a conditional function that defines how to measure the
speed performance on the metric.
operator
The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Write The threshold value and the Operator value determine the normal
speed performance of the monitored metric. When the value of the monitored metric
threshold is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Write The system will generate an alert for a detected issue only if the metric value is
speed time out of the norm during the specified period.
period
Enter an integer value in the range 1-60 (min). The default value is 5.

Settings of the Network usage by process monitor

Network usage by process monitors the incoming and outgoing traffic of the selected process. If
there are multiple instances of the same process, the system will monitor the total usage by all
process instances and will generates an alert when the conditions are met for all instances.

You can configure the following settings for the monitor.

1000 © Acronis International GmbH, 2003-2024

 Setting Description

Process Name of the process that you want to monitor. Enter the process name without
name the extension.

Traffic The traffic direction that you want to monitor.

direction
The following values are available.

l Incoming traffic and Outgoing traffic. This is the default value.

l Incoming traffic
l Outgoing traffic

Incoming The operator is a conditional function that defines how to measure the
traffic performance on the metric.
operator
The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Incoming The threshold value and the Operator value determine the normal
traffic performance of the monitored metric. When the value of the monitored metric
threshold is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Incoming The system will generate an alert for a detected issue only if the metric value is
traffic time out of the norm during the specified period.
period
Enter an integer value in the range 1-60 (min). The default value is 5.

Outgoing The operator is a conditional function that defines how to measure the
traffic performance on the metric.
operator
The following values are available.

l More than —This is the default value.

l More than or equal to
l Less than
l Less than or equal to

Outgoing The threshold value and the Operator value determine the normal
traffic performance of the monitored metric. When the value of the monitored metric
threshold is out of the norm, the system generates an alert.

Enter an integer value (kb/s). The default value is 0 kb/s.

Outgoing The system will generate an alert for a detected issue only if the metric value is
traffic time out of the norm during the specified period.
period
Enter an integer value in the range 1-60 (min). The default value is 5.

1001 © Acronis International GmbH, 2003-2024

Settings of the Windows service status monitor
Windows service status monitors whether the selected Windows service is running or stopped.

You can configure the following settings for the monitor.

Setting Description

Service The name of the Windows service that you want to monitor.
name
You can select a service name from the list of Windows services. The list is
populated by all agents of the tenant after software inventory scan completes
successfully on the workloads. You can also add a service name that is not in the
list. This is the only available option if software inventory scan was not performed
on the workloads.

Service If the service is in the selected status, the system will generate an event.
status
The following values are available.

l Running
l Stopped—This is the default value.

Time The system will generate an alert for a detected issue only if the metric value is out
period of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 1.

Settings of the Process status monitor

Process status monitors whether the selected process is running or stopped. If there are multiple
instances of the same process, the system will monitor each instance of the process and will
generate the alert when the conditions are met for all instances of the process.

You can configure the following settings for the monitor.

Setting Description

Process The name of the process that you want to monitor. Enter the name of the
name executable file without the extension.

Process If the process is in the selected status, the system will generate an event.
status
The following values are available.

l Running
l Stopped—This is the default value.

Time The system will generate an alert for a detected issue only if the metric value is out
period of the norm during the specified period.

Enter an integer value in the range 1-60 (min). The default value is 1.

1002 © Acronis International GmbH, 2003-2024

Settings of the Installed software monitor
Installed software monitors the installation, updates, or deletion of software applications on the
workload.

You can configure the following settings for the monitor.

Setting Description

What Specify the software that you want to monitor.

software to
The following values are available.
monitor
l Any software —This is the default value.
l Specific software

Software This setting becomes available if you select the Specific software value for
names What software to monitor.

Enter the name of one or several software applications.

You can select a software application name from the list of Windows services.
The list is populated by all agents of the tenant after software inventory scan
completes successfully on the workloads. You can also add a software
application name that is not in the list. This is the only available option if
software inventory scan was not performed on the workloads.

Installation Specify if you want to monitor installed, not installed, or updated software.
status
The following values are available.

l Installed - This is the default value. If you select this value, the monitor will
generate an alert when a new software application is installed on the
workload.
l Updated - If you select this value, the monitor will generate an alert when a
software application is updated.
l Not installed - If you select this value, the monitor will generate an alert
when a software application is uninstalled or not available on the workload.

Settings of the Last system restart monitor

Last system restart when the workload was last restarted.

You can configure the following setting for the monitor.

Setting Description

The workload The period (number of days) since the last restart of the workload. If the
has not been workload has not been restarted for a longer period than the period you
restarted for specify, the system will generate an alert.

Enter an integer value in the range 1-180 (days). The default value is 30.

1003 © Acronis International GmbH, 2003-2024

Settings of the Windows event log monitor
Windows event log monitors specific business-critical events in the Windows event logs.

You can configure the following settings for the monitor.

Setting Description

Event log Select a certain event log from a list of Windows event logs that are available
name in Windows Event Viewer.

The following values are available.

l Any —This is the default value.

l Application
l Security
l System

Event source Event source name

You can select the value from a list of event sources that are collected from
all agents of the tenant or enter a new source name manually.

If the software inventory scan is disabled for the tenant, the event source list
will be empty.

Matching In this field, you can specify whether to connect the Event IDs, Event type,
mode and Event description settings by using the Any or the All operator.

The following values are available.

l Any —This is the default value. An alert will be generated only if any of the
selected criteria is matched.
l All — An alert will be generated if all the selected criteria are matched.

Event IDs Enter one or multiple event IDs separated by comma. If the system finds in
the event log any of the event codes that you entered in this field, it
generates an alert.

Event type Select one or multiple event types that you want to monitor.

The following values are available.

l Any —This is the default value.

l Error
l Warning
l Information
l Success-audit
l Failure-audit

Event Specific keywords or phrases in the event description for which you want to
description search. Each keyword or phrase that you enter must be enclosed in quotation

1004 © Acronis International GmbH, 2003-2024

 Setting Description

marks and must be separated by comma. If the system finds any of the
keywords or phrases that you entered, it will generate an alert.

Number of The minimum number of occurrences in the log that an event must have
occurrences during the time period for the system to generate an alert.

Enter an integer value in the range 1-1000.

Time period The system will generate an alert for a detected issue only if the metric value
is out of the norm during the specified period.

Enter an integer value and then select the unit: minutes or hours. The default
value is 60 minutes.

Settings of the Files and folders size monitor

Files and folders size monitors the total size of the selected files and folders.

You can configure the following settings for the monitor.

Setting Description

Files or The paths to the files or folders that you want to monitor. You can also specify
folders to files or folders that you want to exclude from monitoring.
monitor
You can use the following wildcard characters.

l * — for zero or more characters in a file or folder name

l ? — for exactly one character in a file or folder name

For Windows workloads:

l The full path should start from the drive letter followed by the :\ separator.
l You can use slash or backslash as a path separator character.
l The file or folder name must not end with a space or a period.

For macOS workloads:

l The full path should start from the root directory.

l You can use slash as a path separator character.
l The file or folder name must not end with a space or a period.

Specifying a specific location is not mandatory for exclusion filters. The files
entered without a specific location will be excluded in the monitored folders.

Operator The operator is a conditional function that defines how to measure the
performance on the metric.

The following values are available.

l More than —This is the default value.

l Less than

1005 © Acronis International GmbH, 2003-2024

 Setting Description

Threshold The threshold value and the Operator value determine the normal
value performance of the monitored metric. When the value of the monitored metric
is out of the norm, the system generates an alert.

Enter an integer value (MB).

Time period The system will generate an alert for a detected issue only if the metric value is
out of the norm during the specified period.

Enter an integer value in the range 10-60 (min). The default value is 10.

Settings of the Windows Update status monitor

Windows Update status monitors the Windows Update status of the workload and whether the
latest updates are installed.

If you enable this monitor, the system will generate an alert in the following cases.

l Windows Update is disabled on the workload.

l Windows Update is enabled on the workload, but the latest updates are not installed.

Settings of the Firewall status monitor

Firewall status monitors the built-in or third-party firewall that is installed on the workload.

If you enable this monitor, the system will generate an alert in the following cases.

l The built-in OS firewall (Windows Defender Firewall or macOS firewall) is disabled and no third-
party firewall is running.
l Windows Defender Firewall is disabled for public networks.
l Windows Defender Firewall is disabled for private networks.
l Windows Defender Firewall is disabled for domain networks.

Settings of the Failed logins monitor

Failed logins monitors the unsuccessful login attempts on the workload.

You can configure the following settings for the monitor.

Setting Description

Failed login The threshold value determines the boundaries for the normal performance
attempts of the monitored metric. When the threshold value is exceeded, the value is
threshold out of norm.

Enter an integer value. The default value is 60.

Time period The system will generate an alert for a detected issue only if the metric value
is out of the norm during the specified period.

1006 © Acronis International GmbH, 2003-2024

 Setting Description

Enter an integer value in the range 1-24 and select a unit: hours or days. The
default value is 12.

Settings of the Antimalware software status monitor

Antimalware software status monitors the built-in or third-party antimalware software that is
installed on the workload.

If you enable this monitor, the system will generate an alert when it identifies one of the following
conditions.

l Antimalware software is not installed on the workload.

l Antimalware software is installed, but not running.
l Antimalware software is installed and running, but the malware definitions are not up to date.

Note
This condition is checked for Windows and Windows Server operating systems.

Operating Supported antimalware software

system

Windows l Acronis Cyber Protect

l Windows Defender
l Symantec Endpoint Security
l Norton 360
l Norton antivirus
l SentinelOne
l Trend Micro Endpoint Security with Apex One
l Trend Micro Worry-Free Business
l McAfee Endpoint Security
l McAfee Endpoint Protection for SMB
l FireEye Endpoint Security
l F-Secure SAFE
l F-Secure Client Security
l CrowdStrike Falcon
l Kaspersky Endpoint Security Cloud
l BitDefender Antivirus
l Sophos Intercept X Endpoint
l Avast Business Antivirus
l AVG Antivirus Business Edition
l AVG Internet Security Business Edition
l Panda Endpoint Protection
l Tencent PC Manager

1007 © Acronis International GmbH, 2003-2024

 Operating Supported antimalware software
system

l Webroot Business Endpoint Protection

l ESET Endpoint Security
l Avira Antivirus
l Comodo Internet Security
l Comodo Business Antivirus
l K7 Business Security
l K7 Total Security
l Vipre Endpoint Protection
l Total AV

Windows Server l Acronis Cyber Protect

l Windows Defender
l ESET Endpoint Security

Note
The monitor might work with other antimalware applications, but this is not
guaranteed.

macOS l Acronis Cyber Protect

l F-Secure Safe
l BitDefender Anti-virus for Mac
l Sophos Home
l Sophos Endpoint Protection
l Avast Security for Mac
l AVG AntiVirus for Mac
l Webroot SecureAnywhere
l ESET Cybersecurity
l Avira Antivirus for Mac
l Comodo Antivirus for Mac
l K7 Antivirus for Mac
l Vipre Advanced Security
l Total AV for Mac

Note
The monitor might work with other antimalware applications, but this is not
guaranteed.

Settings of the AutoRun feature status monitor

AutoRun feature status monitors if the AutoRun feature for removable media is enabled.

For security reasons, we recommend that you disable the AutoRun feature for removable media on
the workload. If the feature is enabled, the system will generate an alert.

1008 © Acronis International GmbH, 2003-2024

Settings of the Custom monitor
Custom monitors custom objects via running a script.

You can configure the following settings for the monitor.

Setting Description

Script to run List of predefined scripts from the script repository.

Schedule The time when the script is run and, optionally, additional conditions that
should be met to run the script.

The following values are available.

l Schedule by time — The script will run in the exact time, days, weeks, or
months that you specify. This is the default value.
Schedule type — Hourly, Daily, or Monthly
Run within a date range — A time range in which to run the script.
l When user logs in to the system — The script will run when a user logs in
to the workload.
l When user logs off the system — The script will run when a user logs out
of the workload.
l On the system startup — The script will run when the operating system of
the workload starts.
l When system is shut down — The script will run when the workload is
shut down.
l When system goes online — The script will run when the workload
becomes available online.

Start conditions — The task will be performed at a specified time or event

only if the condition is met. With multiple conditions are selectedl, all of them
must be met simultaneously to start the task.

By default, the Prevent the sleep or hibernate mode to start a scheduled

task condition is selected.

If start conditions are not met, run the task anyway after — By default,
this condition is enabled. The default value is 1 hour.

Account to The account on which the script will be run.

execute the
The following values are available.
script
l System account — This is the default value.
l Currently logged in account

Maximum The maximum period during which the script can run on the workload.
duration
If the script does not complete during this period, the operation will fail.

Enter an integer value in the range 1-1440 (minutes). The default value is 3

1009 © Acronis International GmbH, 2003-2024

 Setting Description

minutes.

PowerShell The PowerShell execution policy.

execution
The following values are available.
policy
l Undefined
l AllSigned
l Bypass — This is the default value.
l RemoteSigned
l Restricted
l Unrestricted

For more information about these values, see the Microsoft documentation.

Monitoring plans
Monitoring plans are plans that you apply on your managed workloads to enable and configure the
monitoring functionality.

If no monitoring plan is applied on a workload, the monitoring features will not be available for the
workload.

Note
The availability of the settings that you can configure in the monitoring plan depends on the service
pack that is applied on the tenant. To access all settings, activate the Advanced Management pack.

Creating a monitoring plan

You can create a monitoring plan, and then add workloads to it to configure the monitoring
functionality on the managed workloads.

Prerequisites
The version of the agent that is installed on the workload supports the monitoring functionality.

To create a monitoring plan

From Monitoring plans

1. In the Protection console, go to Management > Monitoring plans.

2. Create a monitoring plan by using one of the two options.
l If there are no monitoring plans in the list, click Create.
l If there are monitoring plans in the list, click Create plan.
3. In the Create monitoring plan window, depending on whether the Advanced Management
pack is enabled for your tenant, do the following:

1010 © Acronis International GmbH, 2003-2024

 l If your tenant is using Standard protection, the following four monitors are automatically
added to the monitoring plan: Disk space, Hardware changes, Last system restart, and Files
and folders size.
l If the Advanced Management pack is enabled for your tenant, select one of the template
options, and then click Next.

Option Description

Recommended Select this option to create a monitoring plan with the default
monitoring configuration.

Custom Use this option to create a monitoring plan from scratch.

4. [Optional] To change the default name of the plan, click the pencil icon, enter the name of the
plan, and then click OK.
5. [Optional] To add a monitor to the plan, click Add monitor, click the monitor in the list, and then
click Add.

Note
The settings of the monitor will be populated automatically with the default values.
You can add maximum three monitors of the same type and up to 30 monitors in total to a
monitoring plan.

6. [Optional] In the monitor parameters screen, change the default settings of the monitor and
alerts, and then click Done.

Note
You can configure different settings for each monitor. For more information, see "Configurable
monitors" (p. 979) and "Configuring monitoring alerts" (p. 1020).

7. [Optional] To delete a monitor, click the bin icon, and then click Delete.
8. [Optional] To add workloads to the plan:
a. Click Add workloads.
b. Select the workloads, and then click Add.
c. If there are compatibility issues that you want to resolve, follow the procedure as described in
"Resolving compatibility issues with monitoring plans" (p. 1018).
9. Click Create.

From All devices

1. In the Protection console, go to Devices > All devices.

2. Click the workload to which you want to apply a monitoring plan.
3. Click Protect.
4. Depending on whether a monitoring plan is applied to the workload, do the following:
l If a monitoring plan is already applied on the workload, click Create plan, and then select
Monitoring.

1011 © Acronis International GmbH, 2003-2024

 l If no monitoring plan is applied on the workload, click Add plan, and then Create plan, and
select Monitoring.
5. In the Create monitoring plan window, select one of the template options, and then click Next.

Option Description

Recommended Select this option to create a monitoring plan with the default
monitoring configuration.

Custom Use this option to create a monitoring plan from scratch.

6. [Optional] To change the default name of the plan, click the pencil icon, enter the name of the
plan, and then click OK.
7. [Optional] If you want to change the default settings of the monitor and alerts, configure the new
values , and then click Done.

Note
You can add maximum three monitors of the same type and up to 30 monitors in total to a
monitoring plan.

8. [Optional] In the monitor parameters screen, change the default settings of the monitor and
alerts, and then click Done.

Note
You can configure different settings for each monitor. For more information, see "Configurable
monitors" (p. 979) and "Configuring monitoring alerts" (p. 1020).

9. [Optional] To delete a monitor, click the bin icon, and then click Delete.
10. Click Create.

Adding workloads to monitoring plans

Depending on your needs, you can add workloads to a monitoring plan after the plan was created.

Prerequisites
l 2FA is enabled for your user account.
l The version of the agent that is installed on the workload supports the monitoring functionality.
l At least one monitoring plan is available.

To add a workload to a monitoring plan

From Monitoring plans

1. In the Protection console, go to Management > Monitoring plans.

2. Click the monitoring plan.
3. Depending on whether the plan was already applied to any workload, do the following:

1012 © Acronis International GmbH, 2003-2024

 l Click Add workloads, if the plan was not applied to any workloads yet.
l Click Manage workloads, if the plan was applied to any workload.
4. Select a workload from the list, and then click Add.
5. Click Save.
6. If necessary, click Confirm to apply the required service quota to the workload.

From All devices

1. In the Protection console, go to Devices > All devices.

2. Click the workload to which you want to apply a monitoring plan.
3. Click Protect.
4. Find the monitoring plan to which you want to add the workload, and click Apply.
5. If necessary, click Confirm to apply the required service quota to the workload.

Revoking monitoring plans

You can revoke a monitoring plan from a workload to which the plan was applied.

Prerequisites
At least one monitoring plan is applied to the workload.

To revoke a monitoring plan

1. In the Protection console, go to Devices > All devices.

2. Click the workload, and then click Protect.
3. Click the More actions icon of the monitoring plan that you want to revoke, and then click
Revoke.

Configuring automatic response actions

Automatic response actions on the alerted events are predefined actions or measures that are
triggered automatically in response to detected events or incidents. These actions are designed to
mitigate potential threats and to minimize damage.

You can configure one or several automatic response actions on the alerted events. The maximum
number of automatic response actions per monitor can be 20.

To configure automatic response actions

1. In the Protection console, go to Management > Monitoring plans.

2. Select the monitoring plan for which you want to configure automatic response actions.
3. Select the monitor, to which you want to configure automatic response actions, or, if you have
not added monitors yet, click Add monitor, click the monitor in the list, click Add, and then
select the monitor.
4. Click the link next to Automatic response actions.

1013 © Acronis International GmbH, 2003-2024

5. In the Automatic response actions window, add one or several response actions that will be
performed automatically when an alert is triggered.
6. Configure each response action. For example, if you have added the response action Start a
Windows service, do the following:
a. Next to Windows service, click Specify.
b. In the Service field, select a service to start as a response action.
c. Click Done.
7. In the list of all added response actions use the up and down arrows or drag and drop to set the
sequence of the response actions.
8. Configure how to handle successive response actions if a previous response action fails. Select
one of the following:
a. Continue with the next response action.
b. Do not continue with the next response action.
9. Click Done.
You will see the number of configured actions next to the Automatic response actions setting
of your monitoring plan. You can edit or delete these actions, as well as add the new ones at any
time later.

The following table lists and describes all the automatic response actions available in the monitor
settings.

Automatic response action Description Supported

OS

Run a script If you add this action, you can: Windows,

macOS
1. Select a certain script to run on the
workload.
2. Specify the account under which you want
to execute the script.
3. Specify maximum duration of the
operation.
4. Specify PowerShell execution policy.
5. Run a script.

To perform this action, you need an Advanced

Management pack license for the workload (if
not assigned yet).

The system will run the selected remote script

with specified parameters when the
conditions are met.

Restart the workload If you add this action, the system will restart Windows,
the workload remotely when the conditions macOS
are met.

1014 © Acronis International GmbH, 2003-2024

 Automatic response action Description Supported
OS

Stop the process If you add this action, you can specify the Windows,
process to stop via manual input of process macOS
name.

The system will stop the process when the

conditions are met.

Start the Windows service If you add this action, you can select which Windows
Windows service to start from the dynamic list
of services populated from the agents.

The system will start the service when the

conditions are met.

Stop the Windows service If you add this action, you can select which Windows
Windows service to stop from the dynamic list
of services populated from the agents.

The system will stop the service when the

conditions are met.

Enable Windows Update If you add this action, the system will enable Windows
Windows Update when the conditions are
met.
This action is available only for Windows
Update status monitor.

Disable AutoRun on If you add this action, the system will disable Windows
removable drives the AutoRun feature on removable storage
media for the workload when the conditions
are met.
This action is available only for Autorun
feature status monitor.

Additional operations with monitoring plans

From the Monitoring plans screen, you can perform the following additional operations with
monitoring plans: view details, edit, view the activities, view the alerts, rename, enable, disable,
clone, export, and delete.

View details

To view the details of a monitoring plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click View details.
3. [Optional] If you want to view the details of a monitor that is enabled in the plan, click the
monitor name.

1015 © Acronis International GmbH, 2003-2024

Edit

Prerequisites
2FA is enabled for your user account.

To edit a plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Edit.
3. [Optional] To delete a monitor from the plan, click the recycle bin icon that is situated to the right
of the monitor name.
4. [Optional] To enable or disable a monitor in the plan, use the toggle next to the monitor name.
5. [Optional] To edit the monitor parameters, do the following.
a. Click the monitor name.
b. Click the overview of the monitor parameters.
c. In the Monitor parameters screen, configure the parameters, and then click Done.

Note
You can configure different settings for each monitor. For more information, see
"Configurable monitors" (p. 979) and "Configuring monitoring alerts" (p. 1020).

d. Close the screen and confirm the changes.

6. [Optional] To add a monitor, click Add monitor, and then, if necessary, edit the parameters as
explained in the previous step.
7. Click Save.

Activities

To view the activities related to a monitoring plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Activities.
3. Click an activity to view more details about it.

Alerts

To view the alerts

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Alerts.

Rename

Prerequisites
2FA is enabled for your user account.

To rename a monitoring plan

1016 © Acronis International GmbH, 2003-2024

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Rename.
3. Enter the new name of the plan, and then click OK.

Enable

Prerequisites
l 2FA is enabled for your user account.
l The monitoring plan is applied to at least one workload.

To enable a monitoring plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Enable.

Disable

Prerequisites
2FA is enabled for your user account.

To disable a monitoring plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Disable.

Clone

Prerequisites
2FA is enabled for your user account.

To clone a monitoring plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Clone.
3. Click Create.

Export

Prerequisites
2FA is enabled for your user account.

To export a monitoring plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Export.
The plan configuration is exported in a JSON format to the local machine.

Delete

1017 © Acronis International GmbH, 2003-2024

Prerequisites
2FA is enabled for your user account.

To delete a monitoring plan

1. In the Monitoring plans screen, click the More actions icon of the monitoring plan.
2. Click Delete.
3. Select I confirm, and then click Delete.

Compatibility issues with monitoring plans

In some cases, applying a monitoring plan on a workload might cause compatibility issues. You
might observe the following compatibility issues:

l Incompatible operating system- this issue appears when the workload's operating system is not
supported.
l Unsupported agent - this issue appears when the version of the protection agent on the
workload is outdated and does not support the monitoring functionality.
l Insufficient quota - this issue appears when there is not enough service quota in the tenant to
assign to the selected workloads.

If the monitoring plan is applied to up to 150 individually selected workloads, you will be prompted
to resolve the existing conflicts before saving the plan. To resolve a conflict, remove the root cause
for it or remove the affected workloads from the plan. For more information, see "Resolving
compatibility issues with monitoring plans" (p. 1018). If you save the plan without resolving the
conflicts, it will be automatically disabled for the incompatible workloads, and alerts will be shown.

If the monitoring plan is applied to more than 150 workloads or to device groups, first it will be
saved, and then checked for compatibility. The plan will be automatically disabled for the
incompatible workloads, and alerts will be shown.

Resolving compatibility issues with monitoring plans

Depending on the cause of the compatibility issues, you can perform different actions to resolve the
compatibility issues as part of the process of creating a new monitoring plan.

To resolve the compatibility issues

1. Click Review issues.

2. [Optional] To resolve compatibility issues with incompatible operating systems by removing
workloads from the plan:
a. On the Incompatible operating system tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.

1018 © Acronis International GmbH, 2003-2024

3. [Optional] To resolve compatibility issues with incompatible operating systems by disabling a
monitor in the plan:
a. On the Incompatible operating system tab, select the monitors that you want to remove.
b. Click Disable monitor.
c. Click Disable, and then click Close.
4. [Optional] To resolve compatibility issues with unsupported agents by removing workloads from
the plan:
a. On the Unsupported agents tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
5. [Optional] To resolve compatibility issues with unsupported agents by updating the agent
version, click Go to Agents list.

Note
This option is available only for customer administrators.

6. [Optional] To resolve compatibility issues with insufficient quota by removing workloads from
the plan:
a. On the Insufficient quota tab, select the workloads that you want to remove.
b. Click Remove workloads from plan.
c. Click Remove, and then click Close.
7. [Optional] To resolve compatibility issues with insufficient quota by increasing the quota of the
tenant:
a. On the Insufficient quota tab, click Go to Management portal.
b. Increase the service quota for the customer.

Note
This option is available only for partner administrators.

Resetting the machine learning models

You can reset the models of a workload when they become outdated or invalid for some reason.
This action will delete the created models and the data that was collected for the workload by the
monitors with anomaly-based monitoring type, and then will start training the machine learning
models for the workload from scratch.

To reset the machine learning models for a workload

1. In the Protection console, go to Devices > All devices.

2. Click a workload from the list, and then click the Details tab.
3. In the Reset machine learning models section, click Reset.
4. In the confirmation window, click Reset again.

1019 © Acronis International GmbH, 2003-2024

Monitoring alerts
Monitoring alerts are displayed in the Protection console and are sent via email when the monitored
behavior of workloads is out of norm. The alerts ensure that the stakeholders are informed as soon
as possible when there are any issues in the IT environment of the organization.

Note
To enable monitoring alerts via email, you must configure at least one email notification policy for
the corresponding alert type. For more information, see "Configuring email notification policies" (p.
1027).

Configuring monitoring alerts

You can configure the monitor's alert settings when you add a monitor to a monitoring plan, or
when you edit a monitor that is already available in a monitoring plan.

To configure monitoring alerts

1. In the Monitor parameters window, go to the Generate alerts section.

2. In Alert severity, select the severity that corresponds to the priority of the alert.

Option Description

Critical These alerts have the highest priority and are related to issues that are
critical for the operation of the workload. Resolve these issues as soon
as possible.

Error An error alert is less severe and indicates that something is wrong or is
not behaving normally. Resolve the issues on time to prevent them
causing more severe issues.

Warning A warning alert indicates that there is some condition of which you
should be aware, but it might not be causing a problem yet. Resolve
these issues after you fix the issues that are causing critical and error
alerts.
This is the default value.

Informational These alerts have the lowest priority. The Informational severity does
not indicate a problem. Such alerts provide information about actions
that are related to a monitored object.

3. In Alert frequency, select how often the system should generate an alert when the condition is
met.

Option Description

Once until the The system will generate an alert one time until the check
check passes completes successfully.

1020 © Acronis International GmbH, 2003-2024

 Option Description

This is the default value.

After X consecutive The system will generate an alert after X consecutive failed checks,
failures where X is an integer value.

4. In Alert message, click the pencil icon to edit the default alert message that will be used when
the system generates an alert. You can specify a custom alert message that contains variables.
For more information about the variables that you can use, see "Monitoring alert variables" (p.
1021).

Note
You can configure more than one alert message for some of the monitors.

5. Enable Alert auto-resolution, if you want the system to automatically resolve the alert when the
monitored metric returns to normal state and the behavior is normal again. By default, the
setting is enabled.

Monitoring alert variables

You can configure different alert variables for different monitors. To use a variable, it must be
enclosed in {{}}.

The following table provides more information about the available variables.

Variable Description Available for

monitor

plan_name The name of the policy All monitors

monitor_name The name of the sub policy in the monitoring plan All monitors

workload_ The name of the workload All monitors

name

threshold_ Specific monitoring conditions or thresholds for All monitors that

value generating an alert support threshold-
based monitoring.

threshold_unit The unit that is associated with the threshold value. All monitors that
For example, %, MB, or mb/s. support threshold-
based monitoring.

time_period The system will generate an alert for a detected All monitors that
issue only if the metric value is out of the norm support threshold-
during the specified period. based monitoring.

time_unit The unit that will be associated with the time period All monitors that
(sec/min/hours/day). support threshold-

1021 © Acronis International GmbH, 2003-2024

 Variable Description Available for
monitor

based monitoring.

anomaly_value The anomaly value All monitors that

support anomaly-
based monitoring.

anomaly_unit The unit that will be associated with the anomaly All monitors that
value support anomaly-
based monitoring.

deviation_value The deviation value All monitors that

support anomaly-
based monitoring.

deviation_unit The unit that will be associated with the deviation All monitors that
value support anomaly-
based monitoring.

drive_name The drive for Windows, or partition for macOS Disk space,

CPU_model The model of the monitored CPU CPU temperature

GPU_model The model of the monitored GPU GPU temperature

hardware_ The model of the monitored component Hardware changes

model

hardware_ The type of monitored hardware Hardware changes

component

hardware_ The model of the monitored component that was Hardware changes
model_old replaced

hardware_ The model of the new monitored component that Hardware changes
model_new was added

disk_model The model of the disk Disk transfer rate

network_ The model of the network adapter Network usage

adapter_model

process_name The name of the process CPU usage by process

Memory usage by
process

Disk transfer rate by

process

Network usage by
process

1022 © Acronis International GmbH, 2003-2024

 Variable Description Available for
monitor

Process status

service_name The name of the service Windows service

status

software_name The name of the software application Installed software

software_ The version of the software application Installed software

version

software_ The version of the software application before the Installed software
version_old update

software_ The version of the new or updated software Installed software

version_new application

number_of_ The number of times an event appears in the log Windows event log
occurrences

event_types The type of the event Windows event log

event_source The source of the event Windows event log

event_log_ The name of the event Windows event log

name

firewall_ The name of the firewall software Firewall status

software_name

antimalware_ The name of the antimalware software Antimalware software

software_name status

user_name The name of the user AutoRun feature

status

script_name The name of the script Custom

Manual response actions

When you see an alert, you can select a response action that you want to perform on the alerted
events.

To perform a manual response action

1. In the Protection console, go to Alerts.

2. Open the alert that you want to view.
3. Click Response action, and then select a response action from the drop-down list.

1023 © Acronis International GmbH, 2003-2024

The list of response actions available for a particular alert depends on the alert type, availability of
features for a particular tenant and the workload operating system.

The following table lists and describes all the manual response actions for your reference.

Manual response action Description Supported

OS

Browse disk space usage Opens a window with Disk space usage Windows,
trend graph, where you can: macOS

l Browse how the disk space usage changed

over time (for the last 1 day / 7 days / 1
month).
l Browse the delta for disk space usage in
relative value (%) for the selected period.

Browse files size growth Opens a window with File size growth graph, Windows,
trend where you can: macOS

l Browse how the total size of the

monitored files and folders changed over
time (for the last 1 day / 7 days / 1 month).
l Browse the delta for total size of files in
relative value (%) for the selected period.

Run a script Opens a window, where you can: Windows,

macOS
1. Select a certain script to run on the
workload.
2. Specify the account under which you want
to execute the script.
3. Specify maximum duration of the
operation.
4. Specify PowerShell execution policy.
5. Run a script.

To perform this action, you need Advanced

Management Pack license for the workload (if
not assigned yet).

Connect via NEAR Acronis Connect Client establishes a remote Windows,

connection. macOS

Connect via RDP Acronis Connect Client establishes a remote Windows

connection.

Open hardware inventory You are redirected to Hardware inventory Windows,

tab for the current workload. macOS

Browse top 10 processes Opens a window with top 10 processes that Windows,
that loaded CPU have loaded the CPU and may have caused macOS

1024 © Acronis International GmbH, 2003-2024

 Manual response action Description Supported
OS

its overheating (The system snapshot at the

moment of alert generation).

Browse top 10 processes Opens a window with top 10 processes that Windows,
that loaded GPU have loaded the GPU and may have caused macOS
its overheating (The system snapshot at the
moment of alert generation).

Browse top 10 processes Opens a window with top 10 processes that Windows,
that loaded memory have loaded the memory (The system macOS
snapshot at the moment of alert generation).

Browse top 10 processes Opens a window with top 10 processes that Windows,
that loaded disk have loaded the disk (The system snapshot at macOS
the moment of alert generation).

Browse top 10 processes Opens a window with top 10 processes that Windows,
that loaded network have loaded the network interface adapter macOS
(The system snapshot at the moment of alert
generation).

Browse resource usage by Opens a window with detailed information Windows,

process about the usage of hardware resources by macOS
the related process: CPU usage, memory
usage, disk I/O, network usage.

Restart workload Opens a confirmation window. Restarts the Windows,

workload after the confirmation. macOS

Start Windows service Opens a confirmation window. Starts the Windows

Windows service after the confirmation.

Stop Windows service Opens a confirmation window. Stops the Windows

Windows service after the confirmation.

Stop process Opens a confirmation window. Stops the Windows,

process to which the alert refers to after the macOS
confirmation.

Enable Windows Update Opens a confirmation window. Enables Windows

Windows Update after the confirmation.

Disable AutoRun feature on Opens a confirmation window. Disables Windows

removable drives AutoRun feature on the system level of the
workload after the confirmation.

1025 © Acronis International GmbH, 2003-2024

Important
For security reasons, two-factor authentication is required to perform the following manual
response actions:

l Run a script
l Connect via NEAR
l Connect via RDP
l Restart workload
l Start Windows service
l Stop Windows service
l Stop process
l Enable Windows Update
l Disable AutoRun feature on removable drives

Viewing the monitoring alerts for a workload

On the Alerts tab, you can view the monitoring alerts of a specific workload and perform different
alert actions.

To view the monitoring alerts for a workload

1. In the Protection console, go to All devices.

2. Click a workload, and then select the Alerts tab.
3. [Optional] In the monitoring alert pane, perform one of the following actions:
l To clear the alert, click Clear.
l To take a response action, click Response action, and then click the action.
l To contact the Support team, click Get support.
4. [Optional] To clear all monitoring alerts for the workload, click Clear all.

Viewing the alert log of monitoring alerts

You can see all events that are related to a monitoring alert in a chronological order: the response
actions (both automatic or manual) that were performed, and the email notifications that were sent.

To view the audit log of a monitoring alert

1. In the Protection console, go to Alerts.

2. Open the Table view.
3. In the list of alerts, click the monitoring alert that you want to view.
4. Click Details, and then click Alert log.

1026 © Acronis International GmbH, 2003-2024

Configuring email notification policies
Email notification policies specify which users will receive email notifications from different
monitors.

From the Email notifications screen, you can perform the following actions with email notification
policies: add, edit, enable, disable, and delete.

Add

To add a new email notification policy

1. In the Protection console, go to Settings > Email notifications.

2. Click Add policy.
3. Click Select recipients.
4. In the Select recipients screen, select the users that you want to receive email alerts, and then
click Select.
5. In Alert types, select the monitors for which you want the system to send email alerts.
6. Click Add.

Edit

To edit an email notification policy

1. In the Protection console, go to Settings > Email notifications.

2. Click the ellipsis icon of the notification policy, and then click Edit.
3. [Optional] To change the recipients, click Edit recipients, add or remove users from the list, and
then click Select.
4. [Optional] In Alert types, select the types of monitoring alerts that you want to be sent to the
selected recipients.
5. Click Save.

Enable

To enable an email notification policy

1. In the Protection console, go to Settings > Email notifications.

2. In the Email notifications screen, click the ... icon of the email notification policy.
3. Click Enable.

Disable

To disable an email notification policy

1. In the Protection console, go to Settings > Email notifications.

2. In the Email notifications screen, click the ... icon of the email notification policy.
3. Click Disable.

Delete

1027 © Acronis International GmbH, 2003-2024

To delete an email notification policy

1. In the Protection console, go to Settings > Email notifications.

2. In the Email notifications screen, click the ... icon of the email notification policy.
3. Click Delete, and then click Confirm.

Viewing monitor data

For each workload, you can view the list of applied monitors, the current status of the monitors, and
the historical performance details in a graphical view. You can use this information to analyze the
state of the workload and how the state changed in time.

Prerequisites
l A monitoring plan is applied on the workload.
l The workload is online and has data for the corresponding monitor.
l The version of the agent that is installed on the workload supports the monitoring plans.

To view the monitors that are applied to a workload and the monitor data

1. In the Protection console, go to Devices > All devices.

2. Click a workload, and then click the Monitoring tab.
The Monitoring tab displays a widget for each monitor that is enabled for the workload. Each
widget displays the following information.

Displayed Description
information

Monitor The monitor name

name

Last result The latest value of the monitored metric or the latest state of the event

Last check The date and time when the monitor collected the last data

Alerts The number of alerts that were generated by the monitor and are still
unresolved.
If there is at least one unresolved alert generated by this monitor, clicking
the number will open the Alerts tab. The alerts will be filtered, and only
the alerts for this monitor will be listed.

Note
The widgets become visible on the tab 15 minutes (or the minimum monitor frequency that is
set for a monitor) after you apply a monitoring plan to the workload.

3. [Optional] To view more details about the monitor, and if applicable, the historical data that was
collected for the monitored metric, in the monitor's widget, click the ellipsis icon, and then click
Details.

1028 © Acronis International GmbH, 2003-2024

 For more information about the monitor details that you can see in the widgets, see "Monitor
widgets" (p. 1029).

Monitor widgets
In the monitor widget, you can see the following details about the monitor.

Detail Description

Monitoring The name of the monitoring plan that contains the monitor. The name of the
plan monitoring plan is a link that opens the monitoring plan in view mode.

Monitor The time interval at which the monitor collects data from the workload
frequency

Last result The latest value of the monitored metric or the latest state of the event

Last check The date and time when the monitor collected the last data

Last alert The date and time when the last alert was generated. The field is displayed
only if at least one alert has been generated for the monitor.

Historical For monitors that collect time-series data, the widget displays historical data
graph for a selected period (1 hour, 6 hours, 12 hours, 1 day, 1 week, or 1 month) in a
graphical view.

The graph displays the actual values of the metrics during a period that you
select. If for some reason the agent did not send the collected data to the
cloud, the missing values are displayed as a dotted line that connects the data
points with actual values that precede and follow the missing value.

For monitors that are using Anomaly-based monitoring, the graph displays
the baselines area, a line that shows the actual values of the metric, and the
anomalies. The anomalies are the spikes or values that are out of the
baselines and are displayed as red dots on the graph.

If you hover the mouse over the graph, you can see the actual value and the
threshold values for a specific time.

1029 © Acronis International GmbH, 2003-2024

 Detail Description

Note
The data on the graphs is displayed in the time zone of the local system. That
is the time zone of the browser of the workload from which you access the
Protection console.

1030 © Acronis International GmbH, 2003-2024

Additional Cyber Protection tools

Compliance mode
The Compliance mode is designed for clients with higher security demands. This mode requires
mandatory encryption for all backups and allows only locally set encryption passwords.

With the Compliance mode, all backups created in a customer tenant and its units are automatically
encrypted with the AES algorithm and a 256-bit key. Users can set the encryption passwords only on
the protected devices, and cannot set them in the protection plans.

Important
The Compliance mode cannot be disabled.

Limitations
l The Compliance mode is compatible only with agents version 15.0.26390 or higher.
l The Compliance mode is not available for devices running Red Hat Enterprise Linux 4.x or 5.x,
and their derivatives.
l Cloud services cannot access encryption passwords. Due to this limitation, some features are not
available for tenants in the Compliance mode.

Unsupported features
The following features are not available for tenants in the Compliance mode:

l Recovery through the Cyber Protect console

l File-level browsing of backups through the Cyber Protect console
l Cloud-to-cloud backup
l Website backup
l Application backup
l Backup of mobile devices
l Antimalware scan of backups
l Safe recovery
l Automatic creation of corporate whitelists
l Data protection map
l Disaster recovery
l Reports and dashboards related to the unavailable features

Setting the encryption password

You must set the encryption password locally, on the protected device. You cannot set the
encryption password in the protection plan. Without a password, creating backups will fail.

1031 © Acronis International GmbH, 2003-2024

Warning!
There is no way to recover encrypted backups if you lose or forget the password.

You can set the encryption password in the following ways:

1. During the installation of a protection agent (for Windows, macOS, and Linux).
2. By using the command line (for Windows and Linux).
This is the only way to set an encryption password on a virtual appliance.
For more information on how to set an encryption password with the Acropsh tool, refer to
"Encryption" (p. 420).
3. In the Cyber Protect Monitor (for Windows and macOS).

To set the encryption password in the Cyber Protect Monitor

1. On the protected device, log on as an administrator.

2. Click the Cyber Protect Monitor icon in the notification area (in Windows) or the menu bar (in
macOS).
3. Click the gear icon.
4. Click Encryption.
5. Set the encryption password.
6. Click OK.

Changing the encryption password

You can change the encryption password before a protection plan creates any backups.

We recommend that you do not change the encryption password after backups are created,
because subsequent backups will fail. To continue protecting the same machine, you must create a
new protection plan for it. Changing both the encryption password and the protection plan will
result in creating new backups that are encrypted with the changed password. The backups that
were created before these changes will not be affected.

Alternatively, you can keep the applied protection plan, and change only the backup file name in it.
This will also result in creating new backups that are encrypted with the changed password. To learn
more about the backup file name, refer to "Backup file name" (p. 428).

You can change the encryption password in the following ways:

1. In the Cyber Protect Monitor (for Windows and macOS).

2. By using the command line (for Windows and Linux).
For more information on how to set an encryption password with the Acropsh tool, refer to
"Encryption" (p. 420).

Recovering backups for tenants in the Compliance mode

With the Compliance mode, you cannot recover backups in the Cyber Protect console.

1032 © Acronis International GmbH, 2003-2024

The following options are available:

l Recovering an entire machine, its disks, or files, by using a bootable media.

l Extracting files from local backups of Windows machines with installed agent, by using Windows
File Explorer.

Immutable storage
With immutable storage, you can access deleted backups during a specified retention period. You
can recover content from these backups, but you cannot change, move, or delete them. When the
retention period ends, the deleted backups are permanently deleted.

The immutable storage contains the following backups:

l Backups that are deleted manually.

l Backups that are deleted automatically, according to the settings in the How long to keep
section in a protection plan or the Retention rules section in a cleanup plan.

Deleted backups in the immutable storage still use storage space and are charged accordingly.

Deleted tenants are not charged for any storage, including immutable storage.

Immutable storage modes

For customer tenants, immutable storage is available in the following modes:

Immutable storage is available in the following modes:

l Governance mode
You can disable and re-enable the immutable storage. You can change the retention period or
switch to Compliance mode.
l Compliance mode

Warning!
Selecting Compliance mode is irreversible.

You cannot disable the immutable storage. You cannot change the retention period and cannot
switch back to Governance mode.

Supported storages and agents

l Immutable storage is supported only on the cloud storage.
Immutable storage is available for Acronis-hosted and partner-hosted cloud storages that use
Acronis Cyber Infrastructure version 4.7.1 or later.
All storages that can be used with Acronis Cyber Infrastructure Backup Gateway are supported.
For example, Acronis Cyber Infrastructure storage, Amazon S3 and EC2 storages, and Microsoft
Azure storage.

1033 © Acronis International GmbH, 2003-2024

 Immutable storage requires that TCP port 40440 is open for the Backup Gateway service in
Acronis Cyber Infrastructure. In version 4.7.1 and later, TCP port 40440 is automatically opened
with the Backup (ABGW) public traffic type. For more information about the traffic types, see
Acronis Cyber Infrastructure documentation.
l Immutable storage requires a protection agent version 21.12 (build 15.0.28532) or later.
l Only TIBX (Version 12) backups are supported.

Enabling immutable storage

You can configure the immutable storage settings in the Cyber Protect console or in the
management portal. They both provide access to the same settings. The procedure below uses the
Cyber Protect console. To learn how to configure the immutable storage settings in the
management portal, see Configuring immutable storage in the administrator guide.

Configuring the immutable storage settings requires two-factor authentication in the tenant to
which the administrator account belongs.

To enable immutable storage

1. Log in to the Cyber Protect console as an administrator.

2. Go to Settings > System settings.
3. Scroll through the list of default backups options, and then click Immutable storage.
4. Enable the Immutable storage switch.
5. Specify a retention period between 14 and 3650 days.
The default retention period is 14 days. A longer retention period will result in increased storage
usage.
6. Select the immutable storage mode, and then confirm your choice, if prompted.
In the Governance mode, you can enable or disable immutable storage, and change the
retention period. You can switch from Governance mode to Compliance mode.

Warning!
Switching to Compliance mode is irreversible. After you select Compliance mode, you cannot
disable the immutable storage, or change its mode or retention period.

7. Click Save.
8. To make an existing archive support the immutable storage, create a new backup in that archive.
To create a new backup, run the protection plan manually or on a schedule.

Warning!
If you delete a backup before making the archive support the immutable storage, the backup is
deleted permanently.

1034 © Acronis International GmbH, 2003-2024

Disabling immutable storage

Note
You can disable the immutable storage only in the Governance mode.

To disable immutable storage

1. Log in to the Cyber Protect console as an administrator.

2. In the navigation menu, click Settings > System settings.
3. Scroll through the list of default backups options, and then click Immutable storage.
4. Disable the Immutable storage switch.
5. Confirm your choice by clicking Disable.

Warning!
Disabling the immutable storage does not come into effect immediately. During a grace period of
14 days, the immutable storage is still active and you can access the deleted backups according to
their original retention period. When the grace period ends, all backups in the immutable storage
are permanently deleted.

Accessing deleted backups in immutable storage

During the retention period, you can access deleted backups and recover data from them.

Note
To allow access to deleted backups, port 40440 on the backup storage should be enabled for
incoming connections.

To access a deleted backup

1. On the Backup storage tab, select the cloud storage that contains the deleted backup.
2. [Only for deleted archives] To see the deleted archives, click Show deleted.
3. Select the archive that contains the backup that you want to recover.
4. Click Show backups, and then click Show deleted.
5. Select the backup that you want to recover.
6. Proceed with the recovery operation, as described in "Recovery" (p. 472).

Geo-redundant storage
Geo-redundant storage ensures data durability by asynchronously copying it to a secondary
location that is geographically distant to the primary location. With geo-redundancy, your data is
accessible even if the primary location is unavailable.

1035 © Acronis International GmbH, 2003-2024

Important
The replicated data takes up the same storage space as the original data.

Enabling and disabling geo-redundant storage

Prerequisites

l The geo-redundant storage becomes available in the Cyber Protect console only after a partner
administrator enables in the Management portal or via API.
l Only administrators can enable or disable the geo-redundant storage in the Cyber Protect
console. Make sure you have the administrator rights.

To enable geo-redundant storage

1. [Only if the geo-redundant storage was enabled via API] In the alert on the top "Geo-redundancy
is available for all your data in the cloud", click Enable Geo-redundant Cloud Storage.
2. In the Cyber Protect console, go to Settings > System settings.
3. Scroll through the list of default backups options, and then click Geo-redundant Cloud Storage.
4. Enable the Geo-redundant Cloud Storage switch.
5. Click Save.
Now, your data will be replicated to a secondary location and will stay available even if the
primary location fails.

To disable geo-redundant storage

Warning!
The replicated data is deleted within one day after you disable the geo-redundancy.

1. In the Cyber Protect console, go to Settings > System settings.

2. Scroll through the list of backups options, and then click Geo-redundant Cloud Storage.
3. Disable the Geo-redundant Cloud Storage switch.
4. Confirm your choice by typing Disable, and then click Disable.

Geo-replication status
Geo-redundancy implies that data is replicated to a secondary location. Geo-replication status
shows the stages of this process. The following statuses are possible:

l In sync—The data has been replicated to the secondary location.

l Syncing—The data is being replicated to the secondary location. The duration of this operation
depends on the size of the data.
l On hold—Data replication is temporarily suspended.
l Disabled—Data replication is disabled.

To check the replication status in the Cyber Protect console

1036 © Acronis International GmbH, 2003-2024

1. In the Cyber Protect console, go to Backup storage.
2. Select the location and the backup set.
3. Click Details, and then check the status in Geo-replication status.

Limitations
l Currently, secondary locations for replicated data are only available in the United States and
Canada.
l For information about the Disaster Recovery service limitations when using geo-redundancy, see
the Disaster Recovery documentation.

1037 © Acronis International GmbH, 2003-2024

Glossary
B D
Backup set Data loss prevention (formerly, data leak
A group of backups to which an individual prevention)
retention rule can be applied. For the Custom A system of integrated technologies and
backup scheme, the backup sets correspond to organizational measures aimed at detecting
the backup methods (Full, Differential, and and preventing accidental or intentional
Incremental). In all other cases, the backup sets disclosure / access to confidential, protected, or
are Monthly, Daily, Weekly, and Hourly. A sensitive data by unauthorized entities outside
monthly backup is the first backup created or inside the organization, or the transfer of
after a month starts. A weekly backup is the such data to untrusted environments.
first backup created on the day of the week
selected in the Weekly backup option (click the
Data loss prevention agent
gear icon, then Backup options > Weekly
backup). If a weekly backup is the first backup A data loss prevention system’s client
created after a month starts, this backup is component that protects its host computer
considered monthly. In this case, a weekly from unauthorized use, transmission, and
backup will be created on the selected day of storage of confidential, protected, or sensitive
the next week. A daily backup is the first data by applying a combination of context and
backup created after a day starts, unless this content analysis techniques and enforcing
backup falls within the definition of a monthly centrally managed data loss prevention
or weekly backup. An hourly backup is the first policies. Cyber Protection provides a fully
backup created after an hour starts, unless this featured data loss prevention agent. However,
backup falls within the definition of a monthly, the functionality of the agent on a protected
weekly, or daily backup. computer is limited to the set of data loss
prevention features available for licensing in
Cyber Protection, and depends upon the
C protection plan applied to that computer.
Cloud server
Device control module
[Disaster Recovery] General reference to a
recovery or a primary server. As part of a protection plan, the device control
module leverages a functional subset of the
Cloud site (or DR site) data loss prevention agent on each protected
computer to detect and prevent unauthorized
[Disaster Recovery] Remote site hosted in the
access and transmission of data over local
cloud and used for running recovery
computer channels. These include user access
infrastructure, in case of a disaster.
to peripheral devices and ports, document
printing, clipboard copy/paste operations,
media format and eject operations, as well as
synchronizations with locally connected mobile

1038 © Acronis International GmbH, 2003-2024

devices. The device control module provides
granular, contextual control over the types of
I
devices and ports that users are allowed to Incremental backup
access on the protected computer and the
A backup that stores changes to the data
actions that users can take on those devices.
against the latest backup. You need access to
other backups to recover data from an
Differential backup
incremental backup.
A differential backup stores changes to the
data against the latest full backup. You need L
access to the corresponding full backup to
recover the data from a differential backup. Local site

[Disaster Recovery] The local infrastructure

F deployed on your company's premises.

Failback
M
Switching a workload from a spare server (such
as a virtual machine replica or a recovery Module
server running in the cloud) back to the
Module is a part of protection plan providing a
production server.
particular data protection functionality, for
example, the backup module, the Antivirus &
Failover Antimalware protection module, and so on.

Switching a workload from a production server

to a spare server (such as a virtual machine O
replica or a recovery server running in the
Orphaned backup
cloud).
An orphaned backup is a backup that is not
Finalization associated to a protection plan anymore.

The operation that makes a temporary virtual

machine that is running from a backup into a P
permanent virtual machine. Physically, this
Physical machine
means recovering all of the virtual machine
disks, along with the changes that occurred A machine that is backed up by an agent
while the machine was running, to the installed in the operating system.
datastore that stores these changes.
Point-to-site (P2S) connection
Full backup [Disaster Recovery] A secure VPN connection
A self- sufficient backup containing all data from outside to the cloud and local sites by
chosen for backup. You do not need access to using your endpoint devices (such as a
any other backup to recover the data from a computer or laptop).
full backup.

1039 © Acronis International GmbH, 2003-2024

 threshold defines the maximum time interval
Primary server
allowed between the last suitable recovery
[Disaster Recovery] A virtual machine that does point for a failover and the current time.
not have a linked machine on the local site
(such as a recovery server). Primary servers are Recovery server
used for protecting an application or running
various auxiliary services (such as a web [Disaster Recovery] A VM replica of the original

server). machine, based on the protected server

backups stored in the cloud. Recovery servers
are used for switching workloads from the
Production network
original servers, in case of a disaster.
[Disaster Recovery] The internal network
extended by means of a VPN tunneling and Runbook
covering both local and cloud sites. Local
servers and cloud servers can communicate [Disaster Recovery] Planned scenario

with each other in the production network. consisting of configurable steps that automate
disaster recovery actions.

Protection agent
S
Protection agent is the agent to be installed on
machines for data protection. Single-file backup format

A backup format, in which the initial full and

Protection plan subsequent incremental backups are saved to
Protection plan is a plan that combines the a single .tibx file. This format leverages the
data protection modules including Backup, speed of the incremental backup method,
Antivirus & Antimalware protection, URL while avoiding its main disadvantage– difficult
filtering, Windows Defender Antivirus, deletion of outdated backups. The software
Microsoft Security Essentials, Vulnerability marks the blocks used by outdated backups as
assessment, Patch management, Data "free" and writes new backups to these blocks.
protection map, Device control. This results in extremely fast cleanup, with
minimal resource consumption. The single-file
backup format is not available when backing
Public IP address
up to locations that do not support random-
[Disaster Recovery] An IP address that is access reads and writes.
needed to make cloud servers available from
the Internet.
Site-to-site (S2S) connection

[Disaster Recovery] Connection extending the

R local network to the cloud, via a secure VPN
Recovery point objective (RPO) tunnel.

[Disaster Recovery] Amount of data lost from

outage, measured as the amount of time from
a planned outage or disaster event. RPO

1040 © Acronis International GmbH, 2003-2024

 virtual machine with an agent inside is treated
T as physical from the backup standpoint.
Test IP address
VPN appliance
[Disaster Recovery] An IP address that is
needed in case of a test failover, to prevent [Disaster Recovery] A special virtual machine
duplication of the production IP address. that enables connection between the local
network and the cloud site via a secure VPN
Test network tunnel. The VPN appliance is deployed on the
local site.
[Disaster Recovery] Isolated virtual network
that is used to test the failover process.
VPN gateway (formerly, VPN server or
connectivity gateway)
U
[Disaster Recovery] A special virtual machine
USB devices database providing a connection between the local site
and the cloud site networks via a secure VPN
[Device control] The device control module
tunnel. The VPN gateway is deployed on the
maintains a database of USB devices from
cloud site.
which they can be added to the list of
exclusions from device access control. The
database registers USB devices by device ID,
which can be entered by hand or selected from
known devices in the Cyber Protect console.

V
Validation

An operation that checks the possibility of data

recovery from a backup. Validation of a file
backup imitates recovery of all files from the
backup to a dummy destination. Validation of a
disk backup calculates a checksum for every
data block saved in the backup. Both
procedures are resource- intensive. While the
successful validation means a high probability
of successful recovery, it does not check all
factors that influence the recovery process.

Virtual machine

A virtual machine that is backed up at a

hypervisor level by an external agent such as
Agent for VMware or Agent for Hyper- V. A

1041 © Acronis International GmbH, 2003-2024

Index
Active Directory Domain Controller for L3 IPsec
# VPN connectivity 725

#CyberFit Score by machine 275 Active point-to-site connections 736

#CyberFit Score for machines 218 Active Protection 783

#CyberFit scoring mechanism 219 Active Protection in the Cyber Backup Standard
edition 798
3
Active Protection settings in Cyber Backup
32-bit or 64-bit? 678 Standard 799

Activities tab 307

A
Adaptive codec 943
About Cyber Disaster Recovery Cloud 698
Add or remove a process, file or network in the
About Secure Zone 395 protection plan blocklist or allowlist 900

About the backup schedule 614 Add or remove USB devices from the
database 354
About the Physical Data Shipping service 460
Adding a Google Workspace organization 614
Access keys 524, 528
Adding a Microsoft 365 organization 578, 582
Access requirements needed to backup to
public cloud storage 521 Adding a workload to a remote management
plan 954
Access settings 356
Adding access to a Microsoft Azure
Accessing a virtual appliance via an SSH
subscription 529
client 168
Adding access to a public cloud connection 532
Accessing deleted backups in immutable
storage 1035 Adding credentials 959

Accessing the Cyber Protection service 22 Adding quarantined files to the whitelist 821

Action field values 369 Adding VLANs 691

Action on detection 799 Adding workloads to a static group 327

Actions 832 Adding workloads to monitoring plans 1012

Actions with protection plans 207 Adding workloads to the Cyber Protect
console 315
Activating Startup Recovery Manager 696
Additional Cyber Protection tools 1031
Activating the account 19
Additional operations with existing remote
Active Directory Domain Controller for L2 Open
management plans 955
VPN connectivity 725

1042 © Acronis International GmbH, 2003-2024

Additional operations with monitoring Agent for oVirt 29
plans 1015
Agent for oVirt – required roles and ports 153
Additional options 402
Agent for Scale Computing HC3 29
Additional parameters 104
Agent for Scale Computing HC3 – required
Additional requirement for virtual roles 139
machines 547
Agent for SQL, Agent for Active Directory, Agent
Additional requirements for application-aware for Exchange (for database backup and
backups 538 application-aware backup) 24

Additional requirements for machines running Agent for Synology 29

Windows 547
Agent for Virtuozzo 28
Additional scheduling options 413
Agent for Virtuozzo Hybrid Infrastructure 28
Adjusting the permissions in data flow policy
Agent for VMware - LAN-free backup 657
rules 830
Agent for VMware – necessary privileges 666
Administering Microsoft 365 organizations
added on different levels 583 Agent for VMware (Virtual Appliance) 28

Advanced 816 Agent for VMware (Windows) 28

Advanced Antimalware 784 Agent for Windows 23

Advanced Data Loss Prevention 826 Aggregated workloads 373

Advanced Data Loss Prevention widgets on the Alert types 251

Overview dashboard 845 Alert widgets 269
Advanced settings 837 Alerts 427
Advanced storage option 394 Alerts tab 307
Agent-based and agentless backup 62 Allowing DHCP traffic over L2 VPN 735
Agent for Advanced Data Loss Prevention 25 Amazon 40
Agent for Data Loss Prevention 24 Analyze incident details 861
Agent for Exchange (for mailbox backup) 25 Anomaly-based monitoring 978
Agent for File Sync & Share 25 Antimalware features 782
Agent for Hyper-V 28 Antimalware protection alerts 261
Agent for Linux 26 Antimalware scan of backups 821
Agent for Mac 27 Antivirus and antimalware protection 781
Agent for Microsoft 365 25 Antivirus and antimalware protection
Agent for MySQL/MariaDB 26 settings 783

Agent for Oracle 26 Apple Screen Sharing 944

1043 © Acronis International GmbH, 2003-2024

Application-aware backup 545 Backing up workloads to public clouds 513

Applying a default protection plan 217 Backup 54, 378

Applying a plan to a group 345 Backup alerts 251

Applying a protection plan to a workload 208 Backup consolidation 428

Approving patches manually 926 Backup file name 428

Are the required packages already Backup format 433

installed? 66
Backup format and backup files 433
Assessing vulnerabilities and managing
Backup format compatibility across different
patches 905
product versions 434
Assigning credentials to a workload 960
Backup options 425
Attaching SQL Server databases 556
Backup plans for cloud applications 189
Autodiscovery of machines 120
Backup replication 191
Automated detection of destination 838
Backup scanning details 284
Automated test failover 746, 748
Backup scanning plans 189
Automatic adding to the whitelist 820
Backup schedule 398
Automatic deletion of unused customer
Backup schemes 398
environments on the cloud site 717
Backup types 400
Automatic driver search 485
Backup validation 434, 496
Automatic patch approval 921
Backup window 457
Automatic updates for components 176
Basic parameters 102
Availability of the backup options 425
Before you start 131, 135, 140, 148, 153
Availability of the recovery options 494
Behavior-engine 788

B Boot mode 496

Backing up a website 644 Bootable Media Builder 678

Backing up clustered Hyper-V machines 669 Browsing the hardware inventory 933

Backing up databases included in an AAG 542 Browsing the software inventory 929

Backing up the cloud servers 772 Bucket settings 524, 528

Backing up the Exchange cluster data 544 Built-in groups 324

Backing up to Amazon S3 521 Built-in groups and custom groups 324

Backing up to Microsoft Azure 521

Backing up to Wasabi 525

1044 © Acronis International GmbH, 2003-2024

 Checking the validation status of a backup 200
C Checksum verification 197

Cache storage 177 Citrix 36

calculate hash 448 Cleanup 200

Capturing network packets 739 Cloning a script 233

Categories to filter 808 Cloud-only mode 708, 728

Changed block tracking (CBT) 435 Cloud-to-cloud groups and non-cloud-to-cloud

groups 325
Changed Block Tracking (CBT) 655
Cloud agent and local agent 573
Changing the backup format to version 12
(TIBX) 433 Cloud applications 285

Changing the encryption password 1032 Cloud network infrastructure 706

Changing the logon account on Windows Cluster-aware backup 543

machines 80
Cluster backup mode 435
Changing the Microsoft 365 access
Combining data flow policy rules 831
credentials 580
Common backup rule 41
Changing the ports used by the protection
agent 58 Common installation rule 41

Changing the registration of a workload 120 Common requirements 537

Changing the script status 235 Comparing script versions 236

Changing the service quota of machines 178 Comparison of the default protection
plans 212
Changing the SQL Server or Exchange Server
access credentials 565 Compatibility issues with monitoring
plans 1018
Changing the timeout for VM heartbeat and
screenshot validation 198 Compatibility issues with remote management
plans 957
Check access to the drivers in bootable
environment 485 Compatibility issues with scripting plans 244

Check device IP address 412 Compatibility with Dell EMC Data Domain
storages 42
Check for indicators of compromise (IOCs)
from publicly known attacks on your Compatibility with encryption software 40
workloads 874
Compliance mode 1031
Check for publicly disclosed attacks on your
Components for unattended installation
workloads using threat feeds 854
(EXE) 90
Checking the cloud firewall activities 771
Components for unattended installation
Checking the size of a search index 634 (MSI) 98

1045 © Acronis International GmbH, 2003-2024

Compression level 436 Configuring the Multi-site IPsec VPN
settings 720
Compute points 702
Configuring the number of retries in case of an
Configurable monitors 979
error 199
Configuring a CDP backup 392
Configuring the patch lifetime in the list 921
Configuring a Site-to-site Open VPN
Configuring the Production patching protection
connection 718
plan 924
Configuring an application-aware backup 638
Configuring the Test patching protection
Configuring automated test failover 749 plan 923

Configuring automatic patch approval 922 Configuring the virtual appliance 132, 136, 144,

Configuring automatic response actions 1013 150

Configuring Cloud-only mode 718 Configuring user accounts in Virtuozzo Hybrid

Infrastructure 141
Configuring custom DNS servers 733
Configuring your antivirus and antimalware
Configuring email notification policies 1027 protection 778
Configuring encryption as a machine Conflict between a new and existing plan 211
property 421
Conflict between an individual and group
Configuring encryption in the protection plan 211
plan 421
Connecting to a machine booted from bootable
Configuring local routing 734 media 691
Configuring monitoring alerts 1020 Connecting to a managed workload via a web
Configuring Multi-site IPsec VPN 720 client 964

Configuring network settings 691 Connecting to managed workloads for remote

desktop or remote assistance 962
Configuring networks in Virtuozzo Hybrid
Infrastructure 141 Connecting to unmanaged workloads via
Acronis Quick Assist 970
Configuring Point-to-site remote VPN
access 725 Connecting to unmanaged workloads via IP
address 970
Configuring proxy server settings 69
Connecting to workloads for remote desktop or
Configuring proxy server settings in Cyber
remote assistance 938
Protect Monitor 297
Connections to remote workloads for remote
Configuring RDP settings 961
desktop or remote assistance 945
Configuring retention rules 418
Continuous data protection (CDP) 389
Configuring Site-to-site Open VPN 718
Control type 684
Configuring the Connect Client settings 975
Conversion to a virtual machine 201

1046 © Acronis International GmbH, 2003-2024

Copying Microsoft Exchange Server Creating WinPE or WinRE bootable media 687
libraries 565
Cross-platform recovery 473
Corporate whitelist 820
Cryptomining process detection 787
CPU priority 458
Custom groups 324
Create a disaster recovery protection plan 704
Custom or ready-made bootable media? 676
Creating a backup replication plan 191
Custom scripts 682
Creating a dynamic device group on the
Custom sensitivity categories 846
partner level 309
Customer tenant level 306
Creating a dynamic group 328
Cyber Disaster Recovery Cloud trial
Creating a monitoring plan 1010
version 701
Creating a personal Google Cloud project 615
Cyber Protect Monitor 29, 296
Creating a primary server 764
Cyber Protection 270
Creating a protection plan 206
Cyber Protection services installed in your
Creating a recovery server 742 environment 179

Creating a remote management plan 946 Cyber Scripting 225

Creating a replication plan 653 CyberApp workloads 373

Creating a runbook 773

D
Creating a script 229
Data considered PCI DSS 842
Creating a script by using AI 231
Data considered Personally Identifiable
Creating a scripting plan 238
Information (PII) 840
Creating a static device group on the partner
Data considered Protected Health
level 308
Information 839
Creating a static group 326
Data Deduplication 54
Creating a validation plan 195
Data flow policy renewal 832
Creating backups in an existing backup
Data flow policy structure 828
archive 432
Data Loss Prevention events 844
Creating bootable media to recover operating
systems 675 Data protection map 280, 292

Creating physical bootable media 677 Data protection map settings 293

Creating the data flow policy and policy Database backup 539
rules 826
Date and time for files 497
Creating the transform file and extracting the
Deactivating Startup Recovery Manager 697
installation packages 165

1047 © Acronis International GmbH, 2003-2024

Default actions 815 Deploying Agent for Virtuozzo Hybrid
Infrastructure (Virtual Appliance) 140
Default backup file name 430
Deploying Agent for VMware (Virtual
Default backup options 424
Appliance) 131
Default protection plans 212
Deploying agents through Group Policy 162
Define response actions for a suspicious
Deploying the OVA template 149
file 898
Deploying the OVF template 131
Define response actions for a suspicious
process 894 Deploying the QCOW2 template 136, 144

Define response actions for a suspicious Description 814

registry entry 899
Detection by tactics 274
Define response actions for an affected
Device control alerts 368
workload 884
Device Control alerts 267
Define threat feed settings 875
Device groups 324
Defining a backup location in Amazon S3 515
Device types allowlist 361
Defining a backup location in Microsoft
Azure 513 Devices tab 308

Defining a backup location in Wasabi 518 Different login options 943

Defining how and what to protect 188 Disable automatic DRS for the agent 131

Deleting a group 345 Disabling automated test failover 750

Deleting a Microsoft 365 organization 583 Disabling automatic assignment for an

agent 663
Deleting a protection plan 211
Disabling full-text search for Gmail
Deleting all alerts 292
backups 636
Deleting backups 507
Disabling immutable storage 1035
Deleting backups outside the Cyber Protect
Disabling One-click recovery 454
console 508
Disaster recovery alerts 255
Deleting credentials 960
Disaster Recovery compatibility with encryption
Deleting custom DNS servers 734
software 702
Deleting the machine 650
Disaster Recovery failover 893
Deploying Agent for oVirt (Virtual
Discovered machines 271
Appliance) 148
Disk health monitoring 276
Deploying Agent for Scale Computing HC3
(Virtual Appliance) 135 Disk health status alerts 280

Deploying Agent for Synology 153 Disk health widgets 277

1048 © Acronis International GmbH, 2003-2024

Disk provisioning 656 Enable or disable device control 350

Distribution algorithm 661 Enable or disable OS notification and service

alerts 353
Do not show messages and dialogs while
processing (silent mode) 437, 497 Enable VSS full backup 469

Do not start when connected to the following Enabling Advanced Data Loss Prevention in
Wi-Fi networks 411 protection plans 835

Do not start when on metered connection 410 Enabling and disabling firewall
management 818
Download configuration for OpenVPN 736
Enabling and disabling geo-redundant
Downloading data for recently affected
storage 1036
workloads 285
Enabling and disabling the Site-to-site
Downloading files from the cloud storage 488
connection 731
Downloading protection agents 73
Enabling Endpoint Detection and Response
Downloading the IPsec VPN log files 741 (EDR) functionality 854

Downloading the logs of the VPN Enabling enhanced search in encrypted

appliance 738 backups 635

Downloading the logs of the VPN gateway 738 Enabling immutable storage 1034

Downloading the output of a scripting Enabling monitoring mode for Endpoint

operation 236 Detection and Response (EDR) 902

Downloading the setup program 155 Enabling One-click recovery 452

Dynamic groups 325 Enabling or disabling a protection plan 210

Dynamic installation and uninstallation of Enabling or disabling enhanced search in

components 82 existing plans 636

Enabling the hardware inventory scanning 932

E
Enabling the software inventory scanning 928
Easy to understand visualization of the attack
Enabling the use of the device control module
storyline 853
on macOS 350
Editing a default protection plan 218
Encryption 420
Editing a dynamic group 344
Endpoint Detection and Response (EDR) 851
Editing a protection plan 209
Endpoint Detection and Response (EDR)
Editing or deleting a script 234 widgets 271
Editing the Recovery server default Error handling 437, 497, 656
parameters 705
Event parameters 406
EDR alerts 267
Example 85, 94, 107, 142-143, 408, 409-412,

1049 © Acronis International GmbH, 2003-2024

 417 File filters (Inclusions/Exclusions) 438

Emergency backup in case of bad blocks on Files of a script 682

the hard disk 406
Filter criteria 439
Installing the packages manually in Fedora
Finalization of machines running from cloud
14 68
backups 651
Examples 83, 85, 93-94, 105
Finalization vs. regular recovery 651
Exchange Server clusters overview 543
Finalizing the machine 650
Exclude device subclasses from access
Find the last logged in user 376
control 353
Firewall management 817
Exclude individual USB devices from access
control 353 Firewall rules for cloud servers 768

Excluding processes from access control 366 Fits the time interval 409

Exclusions 817 Flashback 498

Executing a runbook 777 Forensic backup process 442

Existing vulnerabilities 282 Forensic data 441

Exploit prevention 789 Full-text search 633

Exporting backups 506 Full path recovery 499

Extensions and exception rules 295

G
Extracting files from local backups 492
General recommendations for local sites 722
Extracting the MSI, MST, and CAB files 91
Generating a registration token 162

F Geo-redundant storage 1035

Failback options 656 Geo-replication status 1036

Failback to a target physical machine 758 get content 447

Failback to a target virtual machine 753 Getting started with Cyber Protection 19

Failing back 655 Getting the certificate for backups with forensic
data 444
Failing over to a replica 654
Granting the required system permissions to
Fast incremental/differential backup 438
the Connect Agent 79
Features 852

File-level backup snapshot 440 H

File-level security 498 H.264 943

File exclusions 498 Hardware inventory 932

1050 © Acronis International GmbH, 2003-2024

Hardware inventory widgets 287 How to recover data to a mobile device 568

High Availability of a recovered machine 669 How to reduce bottlenecks 510

How autodiscovery works 121 How to review data via the Cyber Protect
console 568
How creating Secure Zone transforms the
disk 396 How to start backing up your data 567

How do files get into the quarantine How to test if Endpoint Detection and
folder? 818 Response (EDR) is working correctly 903

How does it work? 848 How to use Endpoint Detection and Response
(EDR) 856
How failback works 753
How to use notarization 424, 631
How failover works 745

How it works 219, 277, 289, 292, 390, 424, 444,

I
632, 798, 806
If you choose to create the virtual machine on a
How many agents are required for cluster-
virtualization server 204
aware backup and recovery? 544
If you choose to save the virtual machine as a
How many agents are required for cluster data
set of files 204
backup and recovery? 542
Ignore bad sectors 437
How many agents do I need? 131, 135, 140,
148 Ignore failed VSS writers 469

How remote installation of agents works 123 Immutable storage 1033

How routing works 708, 711, 716 Immutable storage modes 1033

How the regular conversion to a virtual Implementing disaster recovery 698

machine works 204
Important tips 415
How to analyze which security incidents need
In 576
immediate attention 858
In-archive deduplication 434
How to assign the user rights 81
In Cyber Protection 613
How to create Secure Zone 396
In Google Workspace 613
How to delete Secure Zone 397
In Microsoft 365 576
How to get forensic data from a backup? 442
Incident severity history 273
How to investigate incidents in the cyber kill
chain 864 Inclusion and exclusion filters 439

How to navigate attack stages 869 Individual protection plans for hosting control
panel integrations 218
How to perform failover of a DHCP server 752
Information for partner administrators 319
How to perform failover of servers using local
DNS 752 Information parameters 104

1051 © Acronis International GmbH, 2003-2024

Initial connectivity configuration 718 Keyword groups 844

Installation 76 Known issues 638

Installation parameters 102 Known issues and limitations 851

Installing Agent for Synology 155

L
Installing agents and components (MSI and
MST combination) 92 License issue 212

Installing and deploying Cyber Protection License management for on-premises

agents 56 management servers 187

Installing and uninstalling agents and Licensing alerts 265

components (EXE) 83
Limitations 32, 34, 36-40, 141, 149, 154, 203,
Installing and uninstalling agents and 225, 276, 382-383, 387, 389, 395, 475,
components (MSI and direct 488, 497, 577, 595, 599, 603, 614, 621,
selection) 92 624, 628, 638, 644, 652, 658, 696, 700,
822, 1031
Installing patches on demand 926
Limitations and known issues 612
Installing protection agents 73
Limitations for backup file names 430
Installing protection agents in Linux 75
Limitations for recovering files in the Cyber
Installing protection agents in macOS 78
Protect console 492
Installing protection agents in Windows 73
Limitations when using Geo-redundant Cloud
Installing the packages from the repository 67 Storage 701

Installing the packages manually 68 Limiting the total number of simultaneously

backed-up virtual machines 670
Integrations for DirectAdmin, cPanel, and
Plesk 647 Linking workloads to specific users 375

Interaction with other backup options 463 Linux 384

Intermediate snapshots 205 Linux-based 676

Investigate individual nodes in the cyber kill Linux-based bootable media 678
chain 870
Linux-based or WinPE/WinRE-based bootable
Investigate the attack stages of an incident 867 media? 676

Investigating incidents 863 Linux packages 65

IP address reconfiguration 728 list backups 446

IPsec/IKE security settings 722 list content 446

List of USB devices on a computer 366

K
Local connection 691
Kernel parameters 679
Local operations with bootable media 692

1052 © Acronis International GmbH, 2003-2024

Log truncation 449 Managing virtualization environments 665

Logical expression for all supported languages Managing workloads in the Cyber Protect
except Japanese 841 console 304

Logical expression for Japanese 842 Managing your software and hardware
inventory 928
Logical expression used for content
detection 839, 841, 843 Manual adding to the whitelist 820

LVM snapshotting 450 Manual binding 662

Manual failback 762

M
Manual response actions 1023
Mac 384
Marked as Confidential 843
Machine migration 671
Mass storage drivers to install anyway 485
Mailbox backup 547
McAfee Endpoint Encryption and PGP Whole
Malicious website access 808 Disk Encryption 41

Manage the network isolation of a Microsoft 33

workload 885
Microsoft 365 seats licensing report 577
Manage your incidents in the Incident
Microsoft Azure 40
page 853
Microsoft Azure and Amazon EC2 virtual
Managing access to Microsoft Azure
machines 675
subscriptions 528
Microsoft BitLocker Drive Encryption 41
Managing access to other public cloud storage
services 532 Microsoft Defender Antivirus 814

Managing discovered machines 129 Microsoft Defender Antivirus and Microsoft

Security Essentials 814
Managing found vulnerabilities 912
Microsoft Exchange Server 436
Managing networks 726
Microsoft products 915
Managing point-to-site connection settings 735
Microsoft Security Essentials 814
Managing public cloud account access 520
Microsoft SQL Server 435
Managing quarantined files 819
Migration via a bootable media 675
Managing the backup and recovery of
workloads and files 378 Missing updates by categories 283

Managing the cloud servers 767 Monitor widgets 1029

Managing the detected unprotected files 292 Monitoring 248

Managing the target workloads for a plan 242 Monitoring alert variables 1021

Managing the VPN appliance settings 730 Monitoring alerts 1020

1053 © Acronis International GmbH, 2003-2024

Monitoring plans 978, 1010

Monitoring the health and performance of O

workloads 978
Observing multiple managed workloads
Monitoring types 978 simultaneously 968

Monitoring workloads via screenshot Obtaining application ID and application

transmission 967 secret 578

Mount points 450, 499 Off-host data processing 190

Mounting Exchange Server databases 559 On what workloads, agents, and backup
locations are bottlenecks shown? 512
Mounting volumes from a backup 504
On Windows Event Log event 405
Multi-site IPsec VPN connection 715
One-click recovery 451
Multi-site IPSec VPN log files 742
Operations with a primary server 767
Multi-volume snapshot 451
Operations with backups 502
Multitenancy support 313
Operations with Microsoft Azure virtual
N machines 764

Operations with runbooks 776

Names without variables 431
Options description 448
NEAR 943
Oracle 38
Network folder protection 785
Orchestration (runbooks) 772
Network management 726
Organization map 848
Network requirements for the Agent for
Virtuozzo Hybrid Infrastructure (Virtual OS notification and service alerts 360
Appliance) 141
Output speed during backup 459
Network settings 690
Overview of the physical data shipping
Networking concepts 707 process 460

No successful backups for a specified number oVirt/Red Hat Virtualization 4.2 and 4.3/Oracle
of consecutive days 427 Virtualization Manager 4.3 153

Notarization 423, 631 oVirt/Red Hat Virtualization 4.4, 4.5 153

Notarization of backups with forensic data 443

P
Note for Mac users 474
Parallels 37
Nutanix 38
Parameters 679

Parameters for legacy features 105

1054 © Acronis International GmbH, 2003-2024

Parameters for unattended installation Performing manual failback 762
(EXE) 85
Permissions 831
Parameters for unattended installation
Personally Identifiable Information (PII) 840
(MSI) 95
Physical Data Shipping 460
Partner tenant (All customers) level 306
Physical machine to virtual 478
Partner tenant level in the Cyber Protect
console 307 Plan statuses 188

Password requirements 19 Plans on different administration levels 243

Passwords with special characters or blank Point-to-site remote VPN access 716
spaces 119 Policy permissions 521, 525
Patch a workload 888 Policy review and management 832
Patch installation history 283 Policy rules for disks and volumes 385
Patch installation status 282 Policy rules for files and folders 387
Patch installation summary 283 Ports 718
Patch installation widgets 282 Ports required by the Downloader
Patch management 913 component 58

Patch management settings in the protection Post-backup command 463

plan 914 Post-data capture command 465
Payment Card Industry Data Security Standard Post-recovery command 501
(PCI DSS) 842
Power off target virtual machines when starting
Performance 499, 656 recovery 501
Performance and backup window 456 Power on the target virtual machine when
Performing a failover 750 recovery is complete 502

Performing a permanent failover 655 Pre-backup command 462

Performing a test failover 746 Pre-data capture command 464

Performing autodiscovery and manual Pre-recovery command 500

discovery 123 Pre-update backup 919
Performing autodiscovery of machines at the Pre/Post commands 461, 499, 656
partner tenant level 309
Pre/Post data capture commands 463
Performing control actions on managed
workloads 966 Preconfiguring multiple network
connections 690
Performing failback to a physical machine 759
Predefined scripts 681
Performing failback to a virtual machine 755

1055 © Acronis International GmbH, 2003-2024

Preparation 56, 75, 484 Protecting Microsoft 365 collaboration app
seats 612
WinPE 2.x and 3.x 688
Protecting Microsoft 365 data 573
WinPE 4.0 and later 689
Protecting Microsoft 365 Teams 603
Prepare drivers 484
Protecting Microsoft applications 536
Preparing a machine for remote
installation 126 Protecting Microsoft SharePoint 536

Prerequisites 121, 155, 158, 160-162, 168-169, Protecting Microsoft SQL Server and Microsoft
225, 306, 309, 374-375, 389, 454, 492, Exchange Server 536
537, 638, 648, 663, 720, 725, 730, 733-
Protecting mobile devices 566
734, 741-742, 755, 760, 764, 926, 929,
931, 933-934, 936, 947, 954-957, 962, Protecting MySQL and MariaDB data 637
964-968, 970-971, 1010, 1012-1013, Protecting OneDrive files 595
1016-1018, 1028
Protecting OneNote notebooks 611
Prerequistes 235
Protecting Oracle Database 637
Preventing unauthorized uninstallation or
modification of agents 173 Protecting SAP HANA 637

Primary servers 714 Protecting Shared drive files 628

Prioritize which incidents need immediate Protecting SharePoint Online sites 599

attention 858 Protecting web hosting servers 646

Privacy settings 21 Protecting websites 643

Privileges required for the logon account 81 Protecting websites and hosting servers 643

Production failover 745 Protection exclusions 795

Protected Health Information (PHI) 839 Protection of collaboration and communication

Protecting a domain controller 536 applications 247

Protecting Always On Availability Groups Protection plan cheat sheet 380

(AAG) 541 Protection plans 189

Protecting Database Availability Groups Protection plans and modules 205

(DAG) 543
Protection settings 176
Protecting Exchange Online data 585
Protection status 270
Protecting Exchange Online mailboxes 580
Public and test IP address 712
Protecting Gmail data 620

Protecting Google Drive files 624 Q

Protecting Google Workspace data 613 Quarantine 788, 818

Protecting Hosted Exchange data 569 Quarantine location on machines 819

1056 © Acronis International GmbH, 2003-2024

Quick glance overview in the dashboard 854 Recovering backed-up OneNote
notebooks 611
Quotas 646
Recovering backups for tenants in the
R Compliance mode 1032

Recovering data from an application-aware

RDP 944
backup 639
Re-attempt, if an error occurs 437, 497
Recovering databases 641
Re-attempt, if an error occurs during VM
Recovering disks by using bootable media 482
snapshot creation 438
Recovering email messages and meetings 609
Re-generate configuration 736
Recovering entire mailboxes to PST data
Real-time protection 782, 790, 816
files 590
Reassigning IP addresses 732
Recovering ESXi configuration 493
Receive alert notifications when a breach
Recovering Exchange databases 557
happens 853
Recovering Exchange mailboxes and mailbox
Recently affected 284
items 559
Recommendations 497
Recovering files 487
Recommendations and remediation steps 853
Recovering files by using bootable media 491
Recommendations for the Active Directory
Recovering files in the Cyber Protect
Domain Services availability 725
console 487
Recording and playing remote sessions 974
Recovering Google Drive and Google Drive
Recovering a machine 475 files 625
Recovering a machine with One-click Recovering Google Drive files 626
recovery 454
Recovering instances 640
Recovering a team mailbox 607
Recovering mailbox items 562, 571, 581, 588,
Recovering a team site or specific items of a 622
site 610
Recovering mailbox items to PST files 591
Recovering a virtual machine 480
Recovering mailboxes 561, 571, 581, 587, 621
Recovering a website 645
Recovering mailboxes and mailbox items 571,
Recovering an entire Google Drive 625 581, 587, 621
Recovering an entire OneDrive 596 Recovering OneDrive and OneDrive files 596
Recovering an entire Shared drive 629 Recovering OneDrive files 597
Recovering an entire team 604 Recovering physical machines 475
Recovering applications 537 Recovering public folders and folder items 593

1057 © Acronis International GmbH, 2003-2024

Recovering Shared drive and Shared drive Recovery with restart 476
files 629
Red Hat and Linux 36
Recovering Shared drive files 630
Redirecting sound from a remote Linux
Recovering SharePoint Online data 601 workload 945

Recovering SQL databases 549 Redirecting sound from a remote macOS

workload 944
Recovering SQL databases as files 553
Redirecting sound from a remote Windows
Recovering SQL databases to a non-original
workload 944
machine 551
Redistribution 662
Recovering SQL databases to the original
machine 549 Registering and unregistering workloads
manually 115
Recovering stored routines 643
Registering the bootable media 689
Recovering system databases 556
Registration parameters 103
Recovering system state 493
Regular conversion to virtual machine vs.
Recovering tables 642
running a virtual machine from a
Recovering team channels or files in team backup 204
channels 605
Reinstalling the VPN gateway 730
Recovering team mailbox items to PST
Remediate a false positive incident 881
files 608
Remediate an entire incident 877
Recovering the entire server 640
Remediating incidents 877
Recovering the Exchange cluster data 544
Remote connection protocols 943
Recovering the master database 556
Remote connection to a workload 891
Recovery 55, 472
Remote management plans 946
Recovery cheat sheet 472
Remote operations with bootable media 693
Recovery from a network share 682
Remote sessions widget 288
Recovery from backup 892
Remote sound redirection 944
Recovery from the cloud storage 681
Removing access to a Microsoft Azure
Recovery of databases included in an AAG 542
subscription 531
Recovery options 494
Removing access to a public cloud
Recovery servers 712 connection 535

Recovery to Virtuozzo containters or Virtuozzo Removing workloads from a remote

virtual machines 493 management plan 954

Recovery with bootable media on- Removing workloads from the Cyber Protect
premises 692 console 320

1058 © Acronis International GmbH, 2003-2024

Renewing access to a Microsoft Azure Resolving compatibility issues with scripting
subscription 530 plans 245

Renewing access to a public cloud Resolving plan conflicts 211

connection 534
Response actions for individual cyber kill chain
Renewing the policy for a company or unit 833 nodes 882

Renewing the policy for one or more users in Restart a workload 889
the company or unit 833
Retention rules 414
Replication 419
Retention rules according to the backup
Replication of virtual machines 651 scheme 415

Replication options 655 Reverting to the original initial RAM disk 486

Replication vs. backing up 652 Review and analyze discovered IOCs 876

Reported data according to widget type 301 Review and mitigate IOCs on affected
workloads 875
Reports 298
Reviewing incidents 856
Required permissions for unattended
installation in macOS 107 Revoking a plan from a group 346

Required ports 153 Revoking a protection plan 209

Required roles 153 Revoking monitoring plans 1013

Required user rights 549, 576, 613 Rule structure 828

Required user rights for application-aware Run an on-demand forensic backup on a

backups 546 workload 890

Requirements 492, 504 Run as virtual machine 197

Requirements for ESXi virtual machines 538 Runbook parameters 775

Requirements for Hyper-V virtual Running a #CyberFit Score scan 223

machines 539
Running a backup manually 413
Requirements for the VPN appliance 718
Running a backup on a schedule 400
Requirements on User Account Control
Running a hardware inventory scan
(UAC) 127
manually 933
Requirements on user accounts 560
Running a software inventory scan
Resetting the machine learning models 1019 manually 929

Resolving compatibility issues with monitoring Running a virtual machine from a backup
plans 1018 (Instant Restore) 647

Resolving compatibility issues with remote Running cloud-to-cloud backups manually 189
management plans 958
Running pre‐freeze and post‐thaw scripts

1059 © Acronis International GmbH, 2003-2024

 automatically 663 Search indexes 634

Running the machine 648 Search operators 342

Running the Test patching protection plan and Sector-by-sector backup 466
decline unsafe patches 925
Security 944

Security incident burndown 274

S
Security incident MTTR 273
Safe recovery 474
Seeding an initial replica 656
Save battery power 410
Select the snapshot provider 469
Save system information if a recovery with
reboot fails 498 Selecting a destination 393

Saving an agent log file 180 Selecting a tenant level 306

Scale Computing 35 Selecting components for installation 128

Scanning types 782 Selecting data to back up 382

Schedule 240, 293, 908, 917 Selecting disks or volumes 383

Schedule and start conditions 240 Selecting entire machine 382

Schedule by events 403 Selecting ESXi configuration 388

Schedule by time 401 Selecting Exchange Online mailboxes 570

Schedule scan 791, 815 Selecting Exchange Server data 540

Scheduled scan 783 Selecting Exchange Server mailboxes 548

Scheduling 466 Selecting files or folders 386

Screenshot validation 198 Selecting Gmail mailboxes 621

Script quick run 246 Selecting Google Drive files 625

Script repository 237 Selecting mailboxes 586

Script versions 234 Selecting Microsoft 365 mailboxes 580

Scripting plans 237 Selecting OneDrive files 595

Scripts 228 Selecting public folders 587

Scripts in bootable media 681 Selecting Shared drive files 628

Search attributes for cloud-to-cloud Selecting SharePoint Online data 600

workloads 330
Selecting SQL databases 540
Search attributes for non-cloud-to-cloud
Selecting system state 388
workloads 331
Selecting teams 604
Search in cloud-to-cloud backups 632
Self-protection 786

1060 © Acronis International GmbH, 2003-2024

Self-service custom folder on-demand 819 Settings of the Failed logins monitor 1006

Sensitive data definitions 838 Settings of the Files and folders size
monitor 1005
Server-side protection 785
Settings of the Firewall status monitor 1006
Services installed in macOS 180
Settings of the GPU temperature monitor 987
Services installed in Windows 179
Settings of the Hardware changes monitor 989
Setting firewall rules for cloud servers 769
Settings of the Installed software monitor 1003
Setting the encryption password 1031
Settings of the Last system restart
Setting the frequency of Google Workspace
monitor 1003
backups 619
Settings of the Memory usage by process
Setting the frequency of Microsoft 365
monitor 998
backups 585
Settings of the Memory usage monitor 991
Setting the root password on a virtual
appliance 167 Settings of the Network usage by process
monitor 1000
Setting up a display mode 692
Settings of the Network usage monitor 995
Setting up connectivity 707
Settings of the Process status monitor 1002
Setting up primary servers 764
Settings of the Windows event log
Setting up recovery servers 742
monitor 1004
Setting up the disaster recovery
Settings of the Windows service status
functionality 703
monitor 1002
Setting up the Group Policy object 166
Settings of the Windows Update status
Settings of the Antimalware software status monitor 1006
monitor 1007
SID changing 501
Settings of the AutoRun feature status
Signing a file with ASign 490
monitor 1008
Site-to-site Open VPN - Additional
Settings of the CPU temperature monitor 986
information 180
Settings of the CPU usage by process
Site-to-site Open VPN connection 709, 726
monitor 998
Skip the task execution 468
Settings of the CPU usage monitor 989
Smart protection 288
Settings of the Custom monitor 1009
Software-specific recovery procedures 41
Settings of the Disk space monitor 983
Software inventory 928
Settings of the Disk transfer rate by process
monitor 999 Software inventory widgets 286

Settings of the Disk transfer rate monitor 993 Software management tab 308

1061 © Acronis International GmbH, 2003-2024

Software requirements 23, 699, 854 Supported Linux products 908

Sound transfer 943 Supported locations 193-194, 200, 419

Special operations with virtual machines 647 Supported MariaDB versions 31

Splitting 467 Supported Microsoft and third-party

products 905
SQL Server high-availability solutions
overview 541 Supported Microsoft Exchange Server
versions 29
SSH connections to a virtual appliance 167
Supported Microsoft products 906
Start conditions 241, 407
Supported Microsoft SharePoint versions 30
Starting the Secure Shell daemon 167
Supported Microsoft SQL Server versions 29
Startup Recovery Manager 696
Supported mobile devices 566
Static groups 325
Supported MySQL versions 30
Static groups and dynamic groups 325
Supported operating systems 699
Step 1 56
Supported operating systems and
Step 2 56
environments 23
Step 3 56
Supported operating systems and versions 43
Step 4 56
Supported operations with logical volumes 54
Step 5 57
Supported Oracle Database versions 30
Step 6 58
Supported plans for device groups 326
Stopping a runbook execution 777
Supported platforms 225, 778, 942
Stopping failover 654
Supported platforms for monitoring 979
Store security events for 180 days 854
Supported protection features by operating
Structure of autostart.json 683 system 43

Support for virtual machine migration 664 Supported remote desktop and assistance

Supported features per platform 779 features 939

Supported Apple and third-party products 907 Supported SAP HANA versions 30

Supported Apple products 907 Supported storage classes 521

Supported cluster configurations 542-543 Supported third-party products for macOS 907

Supported data sources 391 Supported third-party products for Windows

OS 907
Supported destinations 392
Supported versions 611
Supported file systems 51
Supported virtual machine types 202
Supported languages 839-840, 842-843

1062 © Acronis International GmbH, 2003-2024

Supported virtualization platforms 31, 699 Threat feed 288

Supported web browsers 23 Threat status 272

Supported Windows operating systems 817 Top-level object 683

Switching the Site-to-site connection type 731 Top incident distribution per workload 272

System alerts 269 Transferring files 965

System requirements 718 Transferring files via Acronis Quick Assist 971

System requirements for agents 63 Troubleshooting 129

System requirements for the agent 131, 135, Troubleshooting IPsec VPN configuration
140, 148 issues 739

Troubleshooting the IPsec VPN

T configuration 739

Task failure handling 467 Two-factor authentication 19

Task start conditions 468

U
TCP ports required for backup and replication
of VMware virtual machines 57 Unassigning credentials from a workload 960

Tenants in the Compliance mode 492 Unattended installation and uninstallation in

macOS 106
Test failover 746
Unattended installation and uninstallation with
Testing a replica 653
an EXE file 83
The Activities dashboard 249
Unattended installation and uninstallation with
The Activities tab 295 an MSI file 91

The Alerts dashboard 250 Unattended installation or uninstallation 82

The backup location's host is available 408 Unattended installation or uninstallation in

The Backup storage tab 502 Linux 100

The Cyber Protect console 304 Unattended installation or uninstallation in

Windows 82
The key functionality 698
Unattended installation or uninstallation
The Management tab 188 parameters 101
The Overview dashboard 248 Understand the actions taken to mitigate an
The patch management workflow 914 incident 872

The remote desktop notifiers 976 Understanding and customizing the cyber kill
chain view 866
The tool "tibxread" for getting the backed-up
data 445 Understanding the detection of
bottlenecks 509
The way of using Secure Zone 41

1063 © Acronis International GmbH, 2003-2024

Understanding the scope and impact of Use case for automatic patch approval and
incidents 860 testing 922

Understanding your current level of Use case for automatic patch approval without
protection 248 testing 925

Uninstallation parameters 105 Useful tips 582, 615

Uninstalling agents 174 User is idle 408

Universal Restore in Linux 486 User roles and Cyber Scripting rights 226

Universal Restore in Windows 484 Users logged off 409

Universal Restore process 486 Using a locally attached storage 660

Universal Restore settings 485 Using device control 349

Unsupported features 1031 Using the Adaptive enforcement mode for

renewing a user policy 834
Updating Agent for Synology 159
Using the cloud Agent for Microsoft 365 582
Updating agents 168
Using the Cyber Protect console as a partner
Updating agents automatically 171
administrator 306
Updating agents manually 169
Using the locally installed Agent for Office
Updating agents on BitLocker-protected 365 578
workloads 173
Using the Observation mode for renewing a
Updating the Cyber Protection definitions by user policy 833
schedule 177
Using the toolbar in the Viewer window 972
Updating the Cyber Protection definitions on-
Using Universal Restore 484
demand 177
Using variables 431
Updating, rebuilding, or deleting indexes 634

URL exclusions 813

V
URL filtering 805
Validating backups 506
URL Filtering alerts 266
Validation 193
URL filtering configuration workflow 808
Validation methods 197
URL filtering settings 808
Validation status 194
Usage examples 419, 647, 652, 663
Variable object 683
Usage scenarios 504
Verifying file authenticity with Notary
USB devices allowlist 362 Service 489, 632

USB devices database 363 View device control alerts 356

USB devices database management page 364 View or change access settings 352

1064 © Acronis International GmbH, 2003-2024

Viewing and updating public cloud backup VPN access to local site 736
locations 519
VPN appliance 711
Viewing backup status in vSphere Client 666
VPN gateway 711, 716
Viewing bottleneck details 511
VPN gateway network configuration 711
Viewing details about items in the whitelist 821
Vulnerability assessment 905
Viewing monitor data 1028
Vulnerability assessment for Linux
Viewing the alert log of monitoring alerts 1026 machines 911

Viewing the automated test failover status 749 Vulnerability assessment for macOS
devices 911
Viewing the distribution result 662
Vulnerability assessment for Windows
Viewing the execution history 777
machines 910
Viewing the hardware of a single device 936
Vulnerability assessment settings 908
Viewing the list of available patches 919
Vulnerability assessment widgets 281
Viewing the monitoring alerts for a
Vulnerable machines 281
workload 1026

Viewing the software inventory of a single

W
device 931
Wait until the conditions from the schedule are
Viewing the workloads of specific
met 468
customers 308
Weekly backup 471
Viewing which incidents are currently not
mitigated 859 What's new in the Cyber Protect console 305

Viewing workloads managed by RMM What do I need to back up a website? 643

integrations 372
What do I need to use application-aware
Virtual machine binding 661 backup? 545

Virtuozzo 39 What does a disk or volume backup store? 384

Vituozzo Hybrid Infrastructure 39 What does Google Workspace protection

mean? 613
VM heartbeat 198
What exactly are incidents? 857
VM power management 501, 656
What information is included in an attack
VMware 31
stage? 869
Volume Shadow Copy Service (VSS) 468
What is a backup file? 429
Volume Shadow Copy Service (VSS) for virtual
What is a bottleneck? 509
machines 470
What items can be backed up? 569, 580, 585,
Volume Shadow Copy Service VSS for virtual
595, 599, 603, 620, 624, 628, 643
machines 656

1065 © Acronis International GmbH, 2003-2024

What items can be recovered? 570, 580, 586, WinPE/WinRE-based 676
595, 600, 603, 620, 624, 628
WinRE images 686
What items cannot be recovered? 600
Wiping data from a managed workload 371
What to do next 705
Working in VMware vSphere 651
What to replicate 192
Working with Advanced protection
What to scan 908 features 824

What triggers a policy rule? 830 Working with aggregated workloads 374

What you can back up 566 Working with CyberApp workloads 374

What you can do with a replica 652 Working with encrypted backups 763

What you need to know 566 Working with logs 737

What you need to know about conversion 202 Working with managed workloads 961

What you need to know about finalization 651 Working with the Device control module 347

Where can I see backup file names? 429 Working with unmanaged workloads 969

Where to get the Cyber Protect app 567 Workload credentials 959

Which agent do I need? 58 Workload network status 275

Which backup type do I need? 62 Workloads 314

Whitelist settings 821

Why are there monthly backups with an hourly

scheme? 416

Why back up Microsoft 365 data? 573

Why use application-aware backup? 545

Why use Bootable Media Builder? 678

Why use runbooks? 773

Why use Secure Zone? 395

Why you need Endpoint Detection and

Response (EDR) 851

Windows 384

Windows event log 472, 502

Windows third-party products 915

WinPE-based and WinRE-based bootable

media 686

WinPE images 687

1066 © Acronis International GmbH, 2003-2024