How it Works
Acronis
Loading...
B
C
D
E
F
H
Loading...
Loading...
Backup Recovery Server for Linux - 11.0
Installation Manual
11 pgs515.3 Kb0
User Guide
179 pgs2.66 Mb0

Acronis Backup Recovery Server for Linux - 11.0 User Guide

Acronis Backup & Recovery 11 Server for Linux
Update 0
User Guide
Copyright © Acronis, Inc., 2000-2011. All rights reserved.
“Acronis” and “Acronis Secure Zone” are registered trademarks of Acronis, Inc.
"Acronis Compute with Confidence", “Acronis Startup Recovery Manager”, “Acronis Active Restore”
and the Acronis logo are trademarks of Acronis, Inc.
Linux is a registered trademark of Linus Torvalds.
VMware and VMware Ready are trademarks and/or registered trademarks of VMware, Inc. in the United States and/or other jurisdictions.
Windows and MS-DOS are registered trademarks of Microsoft Corporation.
All other trademarks and copyrights referred to are the property of their respective owners.
Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.
Distribution of this work or derivative work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Third party code may be provided with the Software and/or Service. The license terms for such third-parties are detailed in the license.txt file located in the root installation directory. You can always find the latest up-to-date list of the third party code and the associated license terms used with the Software and/or Service at http://kb.acronis.com/content/7696
Table of contents
1 Introducing Acronis Backup & Recovery 11 ................................................................................ 7
1.1 What's new in Acronis Backup & Recovery 11 ....................................................................... 7
1.2 Acronis Backup & Recovery 11 components .......................................................................... 8
1.2.1 Agent for Linux.......................................................................................................................................... 8
1.2.2 Management Console .............................................................................................................................. 9
1.2.3 Bootable Media Builder ............................................................................................................................ 9
1.3 Supported file systems .......................................................................................................... 9
1.4 Technical Support ............................................................................................................... 10
2 Getting started ......................................................................................................................... 11
2.1 Using the management console .......................................................................................... 12
2.1.1 "Navigation" pane................................................................................................................................... 13
2.1.2 Main area, views and action pages......................................................................................................... 14
2.1.3 Console options ...................................................................................................................................... 17
3 Understanding Acronis Backup & Recovery 11 ......................................................................... 20
3.1 Owners and credentials ...................................................................................................... 20
3.2 User privileges on a managed machine ............................................................................... 21
3.3 Full, incremental and differential backups ........................................................................... 21
3.4 What does a disk or volume backup store? ......................................................................... 23
3.5 Backup and recovery of logical volumes and MD devices (Linux) ......................................... 23
3.5.1 Backing up logical volumes ..................................................................................................................... 23
3.5.2 Backing up MD devices ........................................................................................................................... 24
3.5.3 Backing up hardware RAID arrays (Linux) ............................................................................................... 25
3.5.4 Assembling MD devices for recovery (Linux) .......................................................................................... 25
3.5.5 Recovering MD devices and logical volumes .......................................................................................... 25
3.6 Support for SNMP ............................................................................................................... 29
4 Backup ...................................................................................................................................... 31
4.1 Back up now ....................................................................................................................... 31
4.2 Creating a backup plan........................................................................................................ 31
4.2.1 Selecting data to back up ........................................................................................................................ 33
4.2.2 Access credentials for source ................................................................................................................. 34
4.2.3 Source files exclusion .............................................................................................................................. 34
4.2.4 Access credentials for archive location ................................................................................................... 36
4.2.5 Backup schemes ..................................................................................................................................... 36
4.2.6 Backup location selection ....................................................................................................................... 46
4.2.7 Archive validation ................................................................................................................................... 48
4.2.8 Backup plan's credentials ....................................................................................................................... 48
4.2.9 Label (Preserving machine properties in a backup) ................................................................................ 49
4.2.10 Why is the program asking for the password? ....................................................................................... 50
4.3 Simplified naming of backup files ........................................................................................ 50
4.3.1 Usage examples ...................................................................................................................................... 51
4.3.2 The [DATE] variable ................................................................................................................................ 54
4.3.3 Backup splitting and simplified file naming ............................................................................................ 54
4.4 Scheduling .......................................................................................................................... 55
4.4.1 Daily schedule ......................................................................................................................................... 56
4.4.2 Weekly schedule ..................................................................................................................................... 58
4.4.3 Monthly schedule ................................................................................................................................... 60
4.4.4 Conditions ............................................................................................................................................... 62
4.5 Replication and retention of backups .................................................................................. 64
4.5.1 Supported locations ................................................................................................................................ 66
4.5.2 Setting up replication of backups ........................................................................................................... 66
4.5.3 Setting up retention of backups ............................................................................................................. 66
4.5.4 Retention rules for the Custom scheme ................................................................................................. 67
4.5.5 Replication/cleanup inactivity time ........................................................................................................ 69
4.5.6 Usage examples ...................................................................................................................................... 69
4.6 Default backup options ....................................................................................................... 70
4.6.1 Additional settings .................................................................................................................................. 72
4.6.2 Archive protection .................................................................................................................................. 73
4.6.3 Backup cataloging ................................................................................................................................... 74
4.6.4 Backup performance .............................................................................................................................. 74
4.6.5 Backup splitting....................................................................................................................................... 76
4.6.6 Compression level................................................................................................................................... 76
4.6.7 Disaster recovery plan (DRP) .................................................................................................................. 77
4.6.8 Error handling ......................................................................................................................................... 78
4.6.9 Event tracing ........................................................................................................................................... 79
4.6.10 Fast incremental/differential backup ..................................................................................................... 79
4.6.11 File-level backup snapshot...................................................................................................................... 80
4.6.12 LVM snapshotting ................................................................................................................................... 80
4.6.13 Media components................................................................................................................................. 81
4.6.14 Notifications............................................................................................................................................ 81
4.6.15 Pre/Post commands ............................................................................................................................... 83
4.6.16 Pre/Post data capture commands .......................................................................................................... 84
4.6.17 Replication/cleanup inactivity time ........................................................................................................ 86
4.6.18 Sector-by-sector backup ......................................................................................................................... 87
4.6.19 Task failure handling ............................................................................................................................... 87
4.6.20 Task start conditions ............................................................................................................................... 87
5 Recovery ................................................................................................................................... 89
5.1 Creating a recovery task ...................................................................................................... 89
5.1.1 What to recover ...................................................................................................................................... 90
5.1.2 Access credentials for location ............................................................................................................... 93
5.1.3 Access credentials for destination .......................................................................................................... 94
5.1.4 Where to recover.................................................................................................................................... 94
5.1.5 When to recover ................................................................................................................................... 101
5.1.6 Task credentials .................................................................................................................................... 101
5.2 Acronis Universal Restore ................................................................................................. 101
5.2.1 Getting Universal Restore ..................................................................................................................... 102
5.2.2 Using Universal Restore ........................................................................................................................ 102
5.3 Bootability troubleshooting .............................................................................................. 103
5.3.1 How to reactivate GRUB and change its configuration ........................................................................ 105
5.4 Default recovery options ................................................................................................... 106
5.4.1 Additional settings ................................................................................................................................ 108
5.4.2 Error handling ....................................................................................................................................... 109
5.4.3 Event tracing ......................................................................................................................................... 109
5.4.4 File-level security .................................................................................................................................. 110
5.4.5 Notifications.......................................................................................................................................... 110
5.4.6 Pre/Post commands ............................................................................................................................. 111
5.4.7 Recovery priority .................................................................................................................................. 113
6 Storing the backed up data..................................................................................................... 114
6.1 Vaults ............................................................................................................................... 114
6.1.1 Working with vaults .............................................................................................................................. 115
6.1.2 Personal vaults ...................................................................................................................................... 115
6.2 Acronis Secure Zone ......................................................................................................... 118
6.2.1 Creating Acronis Secure Zone ............................................................................................................... 118
6.2.2 Managing Acronis Secure Zone ............................................................................................................ 120
7 Operations with archives and backups ................................................................................... 122
7.1 Validating archives and backups........................................................................................ 122
7.1.1 Archive selection................................................................................................................................... 123
7.1.2 Backup selection ................................................................................................................................... 123
7.1.3 Vault selection ...................................................................................................................................... 123
7.1.4 Access credentials for source ............................................................................................................... 124
7.1.5 When to validate .................................................................................................................................. 124
7.1.6 Task credentials .................................................................................................................................... 125
7.2 Exporting archives and backups ........................................................................................ 125
7.2.1 Archive selection................................................................................................................................... 128
7.2.2 Backup selection ................................................................................................................................... 128
7.2.3 Access credentials for source ............................................................................................................... 128
7.2.4 Destination selection ............................................................................................................................ 129
7.2.5 Access credentials for destination ........................................................................................................ 130
7.3 Mounting an image ........................................................................................................... 130
7.3.1 Archive selection................................................................................................................................... 131
7.3.2 Backup selection ................................................................................................................................... 132
7.3.3 Access credentials ................................................................................................................................. 133
7.3.4 Volume selection .................................................................................................................................. 133
7.3.5 Managing mounted images .................................................................................................................. 133
7.4 Operations available in vaults ........................................................................................... 134
7.4.1 Operations with archives ...................................................................................................................... 134
7.4.2 Operations with backups ...................................................................................................................... 135
7.4.3 Converting a backup to full ................................................................................................................... 136
7.4.4 Deleting archives and backups ............................................................................................................. 136
8 Bootable media ...................................................................................................................... 138
8.1 Linux-based bootable media ............................................................................................. 139
8.1.1 Kernel parameters ................................................................................................................................ 139
8.1.2 Network settings................................................................................................................................... 141
8.1.3 Network port ........................................................................................................................................ 142
8.2 Connecting to a machine booted from media ................................................................... 142
8.3 Working under bootable media ........................................................................................ 142
8.3.1 Setting up a display mode..................................................................................................................... 143
8.3.2 Configuring iSCSI and NDAS devices ..................................................................................................... 143
8.4 List of commands and utilities available in Linux-based bootable media ............................ 144
8.5 Acronis Startup Recovery Manager ................................................................................... 145
9 Administering a managed machine ........................................................................................ 147
9.1 Backup plans and tasks ..................................................................................................... 147
9.1.1 Actions on backup plans and tasks ....................................................................................................... 147
9.1.2 States and statuses of backup plans and tasks ..................................................................................... 149
9.1.3 Export and import of backup plans ...................................................................................................... 152
9.1.4 Deploying backup plans as files ............................................................................................................ 155
9.1.5 Backup plan details ............................................................................................................................... 156
9.1.6 Task/activity details .............................................................................................................................. 157
9.2 Log.................................................................................................................................... 158
9.2.1 Actions on log entries ........................................................................................................................... 158
9.2.2 Log entry details ................................................................................................................................... 159
9.3 Alerts ................................................................................................................................ 159
9.4 Collecting system information........................................................................................... 160
9.5 Adjusting machine options ................................................................................................ 160
9.5.1 Customer Experience Program ............................................................................................................. 161
9.5.2 Alerts ..................................................................................................................................................... 161
9.5.3 E-mail notifications ............................................................................................................................... 162
9.5.4 Event tracing ......................................................................................................................................... 163
9.5.5 Log cleanup rules .................................................................................................................................. 165
10 Glossary .................................................................................................................................. 166
1 Introducing Acronis Backup & Recovery 11
1.1 What's new in Acronis Backup & Recovery 11
Acronis Backup & Recovery 11 builds on the success that Acronis Backup & Recovery 10 has established by bringing enterprise-class capabilities to the small business market at an affordable price in an easy-to-use package.
Acronis Backup & Recovery 11 continues the trend of expanding the backup and recovery capabilities in physical, virtual and cloud environments. The following is a summary of the product's new features and enhancements.
Simplified installation
The new installer makes the installation procedure simple and clear.
Improved usability
The redesigned product's UI lets you perform any operation easier, faster and more intuitively.
Advanced replication and retention of backups (p. 64)
Store a backup in multiple locations (possibly off-site) for redundancy. Move or copy backups to a cheaper or off-site storage automatically. Set a replication time window if you do not want copying or moving to occur during business hours.
Data view for vaults (p. 90)
Select data from a vault by browsing either the archives and backups (in the Archive view) or the backed up data (in the Data view).
Alert notifications (p. 159)
A new alert system has been introduced for both local and centralized management. Select the alerts you want to observe. Set up e-mail notifications about various types of alerts.
GPT support
Backup and recovery of disks whose partitioning scheme is GUID partition table (GPT).
4-KB drives support (p. 98)
When recovering disks or volumes, the software automatically eliminates volume misalignment – a situation that occurs when volume clusters are not aligned with disk sectors.
Partition (volume) alignment (p. 98)
Solid-State Drives (SSD) require a specific partition alignment for optimal performance. The required alignment is set automatically during recovery, but you can change it manually if required.
Automatic disk/volume mapping (p. 96)
When recovering disks or volumes, the software automatically maps the selected disk/volumes to the target disks in the optimal manner.
Applying Acronis Universal Restore without recovery (p. 102)
Using bootable media, you can apply Acronis Universal Restore to an operating system without performing the recovery.
Linux LVM support (p. 23)
LVM structure is saved in a backup and can be recovered.
Acronis Universal Restore for Linux systems (p. 103)
Recover Linux systems to dissimilar hardware.
Exporting and importing backup plans (p. 152)
Export a backup plan to an .xml file and import it to a different machine.
Deploying backup plans as files (p. 155)
Export a backup plan from one machine and deploy it as an .xml file to multiple machines.
Disaster Recovery Plan (p. 77)
The software can generate a disaster recovery plan and send it via e-mail right after a backup creation. The plan contains step-by-step instructions on how to recover.
Converting a backup to full (p. 136)
Convert an incremental or differential backup to a full one.
New command line
Provides backup and recovery automation. Includes remote management.
Automatic check for updates
The management console automatically checks for updates upon each start and provides notification once the newer version is available.
1.2 Acronis Backup & Recovery 11 components
This section contains a list of Acronis Backup & Recovery 11 components with a brief description of their functionality.
Components for a managed machine (agents)
These are applications that perform data backup, recovery and other operations on the machines managed with Acronis Backup & Recovery 11. Agents require a license to perform operations on each managed machine. Agents have multiple features, or add-ons, that enable additional functionality and so might require additional licenses.
Console
The console provides Graphical User Interface to the agents. Usage of the console is not licensed. In stand-alone editions of Acronis Backup & Recovery 11, the console is installed together with the agent and cannot be disconnected from it.
Bootable Media Builder
With Bootable Media Builder, you can create bootable media in order to use the agents and other rescue utilities in a rescue environment. In stand-alone editions of Acronis Backup & Recovery 11, Bootable Media Builder is installed together with the agent. All add-ons to the agent, if installed, will be available in a rescue environment.
1.2.1 Agent for Linux
This agent enables disk-level and file-level data protection under Linux.
Disk backup
Disk-level data protection is based on backing up either a disk or a volume file system as a whole, along with all information necessary for the operating system to boot; or all the disk sectors using the sector-by-sector approach (raw mode.) A backup that contains a copy of a disk or a volume in a
packaged form is called a disk (volume) backup or a disk (volume) image. It is possible to recover disks or volumes as a whole from such backup, as well as individual folders or files.
File backup
File-level data protection is based on backing up files and directories residing on the machine where the agent is installed or on a network share accessed using the smb or nfs protocol. Files can be recovered to their original location or to another place. It is possible to recover all files and directories that were backed up or select which of them to recover.
1.2.1.1 Universal Restore
The Universal Restore add-on enables you to use the restore to dissimilar hardware functionality on the machine where the agent is installed and create bootable media with this functionality. Universal Restore handles differences in devices that are critical for the operating system start-up, such as storage controllers, motherboard or chipset.
1.2.2 Management Console
Acronis Backup & Recovery 11 Management Console is an administrative tool for local access to Acronis Backup & Recovery 11 agent. Remote connection to the agent is not possible.
1.2.3 Bootable Media Builder
Acronis Bootable Media Builder is a dedicated tool for creating bootable media (p. 168). The media builder that installs on Linux creates bootable media based on Linux kernel.
The Universal Restore (p. 9) add-on enables you to create bootable media with the restore to dissimilar hardware functionality. Universal Restore handles differences in devices that are critical for the operating system start-up, such as storage controllers, motherboard or chipset.
1.3 Supported file systems
Acronis Backup & Recovery 11 can back up and recover the following file systems with the following limitations:
FAT16/32 NTFS Ext2/Ext3/Ext4 ReiserFS3 - particular files cannot be recovered from disk backups located on Acronis Backup &
Recovery 11 Storage Node
ReiserFS4 - volume recovery without the volume resize capability; particular files cannot be
recovered from disk backups located on Acronis Backup & Recovery 11 Storage Node
XFS - volume recovery without the volume resize capability; particular files cannot be recovered
from disk backups located on Acronis Backup & Recovery 11 Storage Node
JFS - particular files cannot be recovered from disk backups located on Acronis Backup &
Recovery 11 Storage Node
Linux SWAP
Acronis Backup & Recovery 11 can back up and recover corrupted or non-supported file systems using the sector-by-sector approach.
1.4 Technical Support
Maintenance and Support Program
If you need assistance with your Acronis product, please go to http://www.acronis.com/support/
Product Updates
You can download the latest updates for all your registered Acronis software products from our website at any time after logging into your Account (https://www.acronis.com/my) and registering the product. See Registering Acronis Products at the Website (http://kb.acronis.com/content/4834) and Acronis Website User Guide (http://kb.acronis.com/content/8128).
2 Getting started
1. Select Tools > Create bootable media in the menu.
2. Click Next in the welcome screen. Keep clicking Next until the list of components appears.
3. Proceed as described in "Linux-based bootable media" (p. 139).
Step 1. Installation
These brief installation instructions enable you to start using the product quickly. For the complete description of installation methods and procedures, please refer to the Installation documentation.
Before installation, make sure that:
Your hardware meets the system requirements. You have license keys for the edition of your choice. You have the setup program. You can download it from the Acronis Web site. Make sure that the RPM Package Manager (RPM) and the following Linux packages are installed:
gcc, kernel, kernel-headers, and kernel-devel. The names of these packages may vary depending on the Linux distribution.
To install Acronis Backup & Recovery 11
Run the AcronisBackupRecoveryServerLinux.i686 or the AcronisBackupRecoveryServerLinux.x86_64 installation file and follow the on-screen instructions.
Step 2. Running
Log in as root or log in as an ordinary user and then switch user as required. Start the console with the command
/usr/sbin/acronis_console
For understanding of the GUI elements see "Using the management console" (p. 12).
Step 3. Bootable media
To be able to recover an operating system that fails to start, or deploy it on bare metal, create bootable media.
Step 4. Backup
Back up now (p. 31)
Click Back up now to do a one-time backup in a few simple steps. The backup process will start immediately after you perform the required steps.
To save your machine to a file:
Under Where to back up, click Location, and select the location where the backup will be saved. Click OK to confirm your selection. Click OK at the bottom of the window to start the backup.
Tip. Using the bootable media, you can do off-line ("cold") backups in the same way as in the operating system.
Create backup plan (p. 31)
Create a backup plan if you need a long-term backup strategy including backup schemes, schedules and conditions, timely deleting of backups, or moving them to different locations.
Step 5. Recovery
Recover (p. 89)
To recover data, you need to select the backed up data and the destination the data will be recovered to. As a result, a recovery task will be created.
Recovery of a disk or volume over a volume locked by the operating system requires a reboot. After the recovery is completed, the recovered operating system goes online automatically.
If the machine fails to boot or if you need to recover a system to bare metal, boot the machine using the bootable media and configure the recovery operation in the same way as the recovery task.
Step 6. Management
The Navigation pane (at the left part of the console) enables you to navigate across the product views that are used for different administering purposes.
Use the Backup plans and tasks view to manage backup plans and tasks: run, edit, stop and
delete plans and tasks, view their states and progress.
Use the Alerts view to rapidly identify and solve the problems. Use the Log view to browse the operations log. The location where you store backup archives is called a vault (p. 179). Navigate to the
Vaults (p. 114) view to obtain information about your vaults. Navigate further to the specific vault to view backups and their contents. You can also select the data to recover and perform manual operations with backups (mounting, validating, deleting).
2.1 Using the management console
As soon as the console connects to a managed machine (p. 176) or to a management server (p. 176), the respective items appear across the console's workspace (in the menu, in the main area with the Welcome screen, or in the Navigation pane) enabling you to perform agent-specific or server-specific operations.
Acronis Backup & Recovery 11 Management Console - Welcome screen
Name
Description
Navigation pane
Contains the Navigation tree and the Shortcuts bar. Lets you navigate to the different views. For details, see Navigation pane (p. 13).
Main area
Here you configure and monitor backup, recovery and other operations. The main area displays views and action pages (p. 14) depending on the items selected in the menu or Navigation tree.
Menu bar
Appears across the top of the program window. Lets you perform most of operations available in Acronis Backup & Recovery 11. The menu items change dynamically depending on the item selected in the Navigation tree and the main area.
Key elements of the console workspace
2.1.1 "Navigation" pane
The navigation pane includes the Navigation tree and the Shortcuts bar.
Navigation tree
The Navigation tree enables you to navigate across the program views. You can choose between the Full list or the Short list of views. The Short list contains the most frequently used views from the Full list.
The Short list displays
[Machine name]. This is the root of the tree also called a Welcome screen. It displays the
name of the machine the console is currently connected to. Use this view for quick access to the main operations, available on the managed machine.
Backup plans and tasks. Use this view to manage backup plans and tasks on the
managed machine: run, edit, stop and delete plans and tasks, view their progress.
Vaults. Use this view to manage personal vaults and archives stored in there, add new
vaults, rename and delete the existing ones, validate vaults, explore backup content, perform operations on archives and backups, etc. If the machine is registered on the management server, you can browse the centralized vaults and perform operations on the archives for which you have the appropriate permissions.
Alerts. Use this view to examine warning messages for the managed machine.
The Full list additionally displays
Disk management. Use this view to perform operations on the machine's hard disk
drives.
Log. Use this view to examine information on operations performed by the program on
the managed machine.
Mounted images. This node is displayed if at least one volume is mounted. Use this view
to manage mounted images.
Shortcuts bar
The Shortcuts bar appears under the navigation tree. It offers you an easy and convenient way of connection to the machines in demand by adding them as shortcuts.
To add a shortcut to a machine
1. Connect the console to a managed machine.
2. In the navigation tree, right-click the machine's name (a root element of the navigation tree), and
then select Create shortcut. If the console and agent are installed on the same machine, the shortcut to this machine will be
added to the shortcuts bar automatically as Local machine [Machine name].
Operations with pane
How to expand/minimize panes
By default, the Navigation pane appears expanded. You might need to minimize the pane in order to free some additional workspace. To do this, click the chevron ( ). The pane will be minimized and the chevron changes its direction ( ). Click the chevron once again to expand the pane.
How to change the panes' borders
1. Point to the pane's border.
2. When the pointer becomes a double-headed arrow, drag the pointer to move the border.
2.1.2 Main area, views and action pages
The main area is a basic place where you work with the console. Here you create, edit and manage backup plans, recovery tasks and perform other operations. The main area displays different views and action pages according the items you select in the menu, or Navigation tree.
2.1.2.1 Views
To
Do the following
Sort items by any column
Click a column's header to sort items in ascending order.
Click it once again to sort items in descending order.
A view appears on the main area when clicking any item in the Navigation tree in the Navigation pane (p. 13).
"Log" view
Common way of working with views
Generally, every view contains a table of items, a table toolbar with buttons, and the Information panel.
Use filtering and sorting (p. 15) capabilities to search the table for the item in question. In the table, select the desired item. In the information panel (collapsed by default), view the item's details. To expand the panel, click
the arrow mark ( ).
Perform actions on the selected item. There are several ways of performing the same action on
selected items:
By clicking the buttons on the table toolbar. By selecting the items in the Actions menu. By right-clicking the item and selecting the operation in the context menu.
Sorting, filtering and configuring table items
The following is a guideline to sort, filter and configure table items in any view.
Filter items by predefined column value
In a field below the corresponding column's header, select the required value from the drop-down list.
Filter items by entered value
In a field below the corresponding column's header, type a value.
As a result you will see the list of values, fully or just partly coincide with the entered value.
Filter items by a predefined parameters
Depending on the view, you can filter a table items by some predefined parameters. To do this, click the respective buttons or links at the top of the table.
For example:
In the Log view, you can filter the event entries by clicking buttons
associated with the result: Succeeded, Succeeded with warnings, or Failed.
The Log view has the activity start time as the default parameter, and
three predefined settings for filtering activities by this parameter (All available, For last 3 months, or For custom period) are placed at the top
of the Log view.
Show or hide table columns
By default, any table has a fixed number of columns that are shown, others are hidden. If required, you can hide the shown columns and show the hidden ones.
To show or hide columns
1. Right-click any column header to open the context menu.
2. Click the items you want to be displayed/hidden.
2.1.2.2 Action pages
An action page appears in the main area when clicking any action item in the Actions menu. It contains steps you need to perform in order to create and launch any task or a backup plan.
Action page - Create backup plan
Using controls and specifying settings
Use active controls to specify a backup plan or recovery task settings and parameters. By default, such fields as credentials, options, comments, and some others are hidden. Most settings are configured by clicking the respective Show… links. Others are selected from the drop-down list, or typed manually in the page's fields.
Action page - Controls
Acronis Backup & Recovery 11 remembers the changes you made on the action pages. For example, if you started to create a backup plan, and then for any reason switched to another view without accomplishing the plan creation, you can click the Back navigation button on the menu. Or, if you have passed several steps forward, click the Down arrow and select the page where you started the plan creation from the list. Thus, you can perform the remaining steps and accomplish the backup plan creation.
Navigation buttons
2.1.3 Console options
The console options define the way information is represented in the Graphical User Interface of Acronis Backup & Recovery 11.
To access the console options, select Options > Console options from the top menu.
2.1.3.1 Alert display options
The option specifies which alerts to show and which to hide in the Alerts view.
The preset is: All alerts.
To show (hide) alerts, select (clear) the check boxes next to the respective alert types.
2.1.3.2 Credentials cache
The option specifies whether to store the credentials entered while using the management console.
The preset is: Disabled.
If the option is disabled, access credentials for various locations that you enter during a console session are stored only until the console is closed.
If the option is enabled, the credentials are saved for use during later sessions. In Windows, the credentials are stored in the Windows Credential Manager. In Linux, the credentials are stored in a special encrypted file.
2.1.3.3 Fonts
The option defines the fonts to be used in the Graphical User Interface of Acronis Backup & Recovery
11. The Menu font setting affects the drop-down and context menus. The Application font setting affects all other GUI elements.
The preset is: System Default font for both the menus and the application interface items.
To make a selection, choose the font from the respective combo-box and set the font's properties. You can preview the font's appearance by clicking Browse to the right.
2.1.3.4 Pop-up messages
These options are effective when the console is connected to a managed machine or to the management server.
The “Activities Need Interaction” dialog
This option defines whether to display a pop-up window when one or more activities require user interaction. This window enables you to specify your decision, such as to confirm reboot or to retry after freeing-up the disk space, on all the activities in the same place. Until at least one activity requires interaction, you can open this window at any time from the managed machine's welcome screen. Alternatively, you can review the task execution states in the Backup plans and tasks view and specify your decision on each task in the information panel.
The preset is: Enabled.
To make a selection, select or clear the The “Activities Need Interaction” dialog check box.
The “Feedback Confirmation” dialog
This option defines whether to display a pop-up window with the information about your system after an error occurs. You can send this information to Acronis technical support.
The preset is: Enabled.
To make a selection, select or clear the The “Feedback Confirmation” dialog check box.
Notify if bootable media is not created
This option defines whether to display a pop-up window when the management console is launched on a machine and no bootable media has been created on that machine.
The preset is: Enabled.
To make a selection, select or clear the Notify if bootable media is not created check box.
Notify when the management console is connected to a component of a different version
This option defines whether to display a pop-up window when a console is connected to an agent/management server and their versions differ.
The preset is: Enabled.
To make a selection, select or clear the Notify when the management console is connected to a
component of a different version check box.
About the task execution results
This option is effective only when the console is connected to a managed machine.
The option defines whether to display the pop-up messages about task run results: successful completion, failure or success with warnings. When the displaying of pop-up messages is disabled, you can review the task execution states and results in the Backup plans and tasks view.
The preset is: Enabled for all results.
To make a setting for each result (successful completion, failure or success with warnings) individually, select or clear the respective check box.
2.1.3.5 Startup page
This option defines whether to show the Welcome screen or the Dashboard view on the console connection to the management server.
The preset is: the Welcome screen.
To make a selection, select or clear the check box for Show the "Dashboard" view.
This option can also be set on the Welcome screen. If you select the check box for At startup, show the Dashboard instead of the current view on the Welcome screen, the setting mentioned above will be updated accordingly.
3 Understanding Acronis Backup & Recovery 11
This section attempts to give its readers a clear understanding of the product so that they can use the product in various circumstances without step-by-step instructions.
3.1 Owners and credentials
This section explains the concept of owner and the meaning of a backup plan's (or task's) credentials.
Plan (task) owner
A local backup plan owner is the user who created or last modified the plan.
A centralized backup plan owner is the management server administrator who created or last modified the centralized backup plan.
Tasks, belonging to a backup plan, either local or centralized, are owned by the backup plan owner.
Tasks that do not belong to a backup plan, such as the recovery task, are owned by the user who has created or last modified the task.
Managing a plan (task) owned by another user
Having Administrator privileges on the machine, a user can modify tasks and local backup plans owned by any user registered in the operating system.
When a user opens a plan or task for editing, which is owned by another user, all passwords set in the task are cleared. This prevents the "modify settings, leave passwords" trick. The program displays a warning each time you are trying to edit a plan (task) last modified by another user. On seeing the warning, you have two options:
Click Cancel and create your own plan or task. The original task will remain intact. Continue editing. You will have to enter all credentials required for the plan or task execution.
Archive owner
An archive owner is the user who saved the archive to the destination. To be more precise, this is the user whose account was specified when creating the backup plan in the Where to back up step. By default, the plan's credentials are used.
Plan's credentials and task credentials
Any task running on a machine runs on behalf of a user. When creating a plan or a task, you have the option to explicitly specify an account under which the plan or the task will run. Your choice depends on whether the plan or task is intended for manual start or for executing on schedule.
Manual start
You can skip the Plan's (Task) credentials step. Every time you start the task, the task will run under the credentials with which you are currently logged on. Any person that has administrative privileges on the machine can also start the task. The task will run under this person's credentials.
The task will always run under the same credentials, regardless of the user who actually starts the task, if you specify the task credentials explicitly. To do so, on the plan (task) creation page:
1. In the Plan parameters (or Task parameters) section, click Show plan's credentials, comments,
label (or Show task credentials).
2. Click Plan's (Task) credentials.
3. Enter the credentials under which the plan (task) will run. Scheduled or postponed start
The plan (task) credentials are mandatory. If you skip the credentials step, you will be asked for credentials after finishing the plan (task) creation.
Why does the program compel me to specify credentials?
A scheduled or postponed task has to run anyway, regardless if any user is logged on or not (for example, the system is at the Windows "Welcome" screen) or a user other than the task owner is logged on. It is sufficient that the machine be on (that is, not in standby or hibernate) at the scheduled task start time. That's why the Acronis scheduler needs the explicitly specified credentials to be able to start the task.
3.2 User privileges on a managed machine
When managing a machine running Linux, the user has or obtains the root privileges, and so can:
Back up and recover any data or the entire machine, having full control over all Acronis Backup &
Recovery 11 agent operations and log files on the machine.
Manage local backup plans and tasks owned by any user registered in the operating system.
To avoid routine logging on to the system as root, the root user can log on with the ordinary user credentials and then switch user as required.
3.3 Full, incremental and differential backups
Acronis Backup & Recovery 11 provides the capability to use popular backup schemes, such as Grandfather-Father-Son and Tower of Hanoi, as well as to create custom backup schemes. All backup schemes are based on full, incremental and differential backup methods. The term "scheme" in fact denotes the algorithm of applying these methods plus the algorithm of the archive cleanup.
Comparing backup methods with each other does not make much sense because the methods work as a team in a backup scheme. Each method should play its specific role according to its advantages. A competent backup scheme will benefit from the advantages of all backup methods and lessen the
influence of all the methods’ shortcomings. For example, weekly differential backup facilitates
archive cleanup because it can be easily deleted along with the weekly set of daily incremental backups depending on it.
Backing up with the full, incremental or differential backup method results in a backup (p. 167) of the corresponding type.
Full backup
A full backup stores all data selected for backup. A full backup underlies any archive and forms the base for incremental and differential backups. An archive can contain multiple full backups or consist of only full backups. A full backup is self-sufficient - you do not need access to any other backup to recover data from a full backup.
It is widely accepted that a full backup is the slowest to do but the fastest to restore. With Acronis
Parameter
Full backup
Differential backup
Incremental backup
technologies, recovery from an incremental backup may be not slower than recovery from a full one.
A full backup is most useful when:
you need to roll back the system to its initial state this initial state does not change often, so there is no need for regular backup.
Example: An Internet cafe, school or university lab where the administrator often undoes changes made by the students or guests but rarely updates the reference backup (in fact, after installing software updates only). The backup time is not crucial in this case and the recovery time will be minimal when recovering the systems from the full backup. The administrator can have several copies of the full backup for additional reliability.
Incremental backup
An incremental backup stores changes to the data against the latest backup. You need access to other backups from the same archive to recover data from an incremental backup.
An incremental backup is most useful when:
you need the possibility to roll back to any one of multiple saved states the data changes tend to be small as compared to the total data size.
It is widely accepted that incremental backups are less reliable than full ones because if one backup in the "chain" is corrupted, the next ones can no longer be used. However, storing multiple full backups is not an option when you need multiple prior versions of your data, because reliability of an oversized archive is even more questionable.
Example: Backing up a database transaction log.
Differential backup
A differential backup stores changes to the data against the latest full backup. You need access to the corresponding full backup to recover the data from a differential backup. A differential backup is most useful when:
you are interested in saving only the most recent data state the data changes tend to be small as compared to the total data size.
The typical conclusion is: "differential backups take longer to do and are faster to restore, while incremental ones are quicker to do and take longer to restore." In fact, there is no physical difference between an incremental backup appended to a full backup and a differential backup appended to the same full backup at the same point of time. The above mentioned difference implies creating a differential backup after (or instead of) creating multiple incremental backups.
An incremental or differential backup created after disk defragmentation might be considerably larger than usual because defragmentation changes file locations on the disk and the backup reflects these changes. It is recommended that you re-create a full backup after disk defragmentation.
The following table summarizes the advantages and shortcomings of each backup type as they appear based on common knowledge. In real life, these parameters depend on numerous factors such as the amount, speed and pattern of data changes; the nature of the data, the physical specifications of the devices, the backup/recovery options you set, to name a few. Practice is the best guide to selecting the optimal backup scheme.
Storage space
Maximal
Medium
Minimal
Creation time
Maximal
Medium
Minimal
Recovery time
Minimal
Medium
Maximal
3.4 What does a disk or volume backup store?
A disk or volume backup stores a disk or a volume file system as a whole, along with all the information necessary for the operating system to boot. It is possible to recover disks or volumes as a whole from such backup, as well as individual folders or files.
With the sector-by-sector (raw mode) option enabled, a disk backup stores all the disk sectors.
For supported file systems, with the sector-by-sector option turned off, a disk or volume backup stores only those sectors that contain data. This reduces the resulting backup size and speeds up the backup and recovery operations.
Windows
The swap file (pagefile.sys) and the file that keeps the RAM content when the machine goes into hibernation (hiberfil.sys) are not backed up. After recovery, the files will be re-created in the appropriate place with the zero size.
A volume backup stores all other 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). The boot code of GPT volumes is not backed up.
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.
Linux
A volume backup stores all files and folders 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.
3.5 Backup and recovery of logical volumes and MD
devices (Linux)
This section explains how you would back up and recover volumes managed by Linux Logical Volume Manager (LVM), called logical volumes; and multiple-disk (MD) devices, called Linux Software RAID.
To learn more about LVM please visit http://tldp.org/HOWTO/LVM-HOWTO/ or http://www.centos.org/docs/5/html/5.1/Deployment_Guide/ch-lvm.html.
3.5.1 Backing up logical volumes
Acronis Backup & Recovery 11 Agent for Linux can access, back up and recover logical volumes when running in Linux with 2.6.x kernel or a Linux-based bootable media.
Backup
In Acronis Backup & Recovery 11 GUI, logical volumes appear under Dynamic volumes at the end of the list of volumes available for backup. If you select logical volumes for backup, the logical volume
structure will be saved to the backup along with the volume contents. This structure can be automatically recreated when you recover these volumes under a Linux-based bootable media.
To back up all available disks, specify all logical volumes plus basic volumes not belonging to them. This is the default choice when you open the Create backup plan page.
Basic volumes included in logical volumes are shown in the list with None in the File system column. If you select such volumes, the program will back them up sector-by-sector. Normally this it is not required.
Recovery
When recovering logical volumes, you have two options:
Recovering volume contents only. The type or other properties of the target volume will not
change. This option is available both in the operating system and under bootable media. This option is useful in the following cases:
When some data on the volume was lost, but no hard disks were replaced. When recovering a logical volume over a basic disk or volume. You can resize the resulting
volume in this case.
A system, recovered from a logical volume backup to a basic disk, cannot boot because its kernel tries to mount the root file system at the logical volume. To boot the system, change the loader configuration and /etc/fstab so that LVM is not used and reactivate your boot loader (p. 105).
When recovering a basic or logical volume to a previously created logical volume. Such is the
case when you create the structure of logical volumes manually (p. 26) by using the lvm utility.
Recovering both the structure of logical volumes and their contents.
Such is the case when recovering on bare metal or on a machine with different volume structure. The structure of logical volumes can be automatically created at the time of recovery (p. 26).
This option is available only under bootable media.
For detailed instructions on how to recover logical volumes, see Recovering MD devices and logical volumes (p. 25).
3.5.2 Backing up MD devices
MD devices, known as Linux Software RAID, combine several volumes and make solid block devices (/dev/md0, /dev/md1, ..., /dev/md31). The information about MD devices is stored in /etc/raidtab or in dedicated areas of those volumes.
You can back up active (mounted) MD devices in the same way as logical volumes. The MD devices appear at the end of the list of volumes available for backup. If you select MD devices for backup, the structure of the MD devices will be backed up along with their contents.
Backing up volumes included in MD devices does not make sense when an MD device is mounted, as it won’t be possible to recover them.
When recovering MD devices under bootable media, the structure of MD devices can be recreated automatically. For detailed information about recovering MD devices under bootable media, see Recovering MD devices and logical volumes (p. 25).
For information about assembling MD devices when performing recovery in Linux, see Assembling MD devices for recovery (Linux) (p. 25).
3.5.3 Backing up hardware RAID arrays (Linux)
Hardware RAID arrays under Linux combine several physical drives to create a single partitionable disk. The special file related to a hardware RAID array is usually located in /dev/ataraid. You can back up hardware RAID arrays in the same way as ordinary hard disks.
Physical drives that are part of hardware RAID arrays may be listed alongside other disks as if they had a bad partition table or no partition table at all. Backing up such disks does not make sense as it won’t be possible to recover them.
3.5.4 Assembling MD devices for recovery (Linux)
In Linux, when performing recovery from a disk backup to an existing MD device (also called Linux Software RAID), make sure that this device is assembled at the time of recovery.
If the device is not assembled, assemble it by using the mdadm utility. Here are two examples:
Example 1. The following command assembles the device /dev/md0 combined from the volumes /dev/sdb1 and /dev/sdc1:
mdadm --assemble /dev/md0 -ayes /dev/sdb1 /sdc1
Example 2. The following command assembles the device /dev/md0 combined from the disks /dev/sdb and /dev/sdc:
mdadm --assemble /dev/md0 -ayes /dev/sdb /dev/sdc
If the recovery requires the machine to be rebooted (usually, when the volumes to recover include the boot partition), follow these guidelines:
If all parts of the MD device are volumes (a typical case, such as in the first example), make sure
that each volume type—called partition type or system ID—is Linux raid automount; the hexadecimal code of this partition type is 0xFD. This will guarantee that the device will be automatically assembled following the reboot. To view or change the partition type, use a disk partitioning utility such as fdisk.
Otherwise (such as in the second example), perform the recovery from bootable media. No
reboot will be required in that case. In bootable media, you may need to create the MD device manually or automatically, as described in Recovering MD devices and logical volumes (p. 25).
3.5.5 Recovering MD devices and logical volumes
Recovering MD devices and/or volumes created by Logical Volume Manager (logical volumes) assumes that the corresponding volume structure will be re-created.
In Linux-based bootable media, you can create the volume structure automatically (p. 26) when recovering the volumes from:
A backup created by Acronis Backup & Recovery 11. A backup created by Acronis Backup & Recovery 10, provided that the volume structure
information was saved in the backup. (It is saved by default.)
In other cases, before starting the recovery, you need to create the volume structure manually (p.
26) by using the mdadm and lvm utilities.
3.5.5.1 Creating the volume structure automatically
Use the following procedure to create the volume structure in a Linux-based bootable media.
Note: If you are recovering the volumes from a backup created by Acronis Backup & Recovery 10, this procedure works only if the volume structure information was saved in the backup. (It is saved by default.)
Caution: As a result of the following procedure, the current volume structure on the machine will be replaced with the one stored in the archive. This will destroy the data that is currently stored on some or all of the machine's hard disks.
If disk configuration has changed. An MD device or a logical volume resides on one or more disks, each of its own size. If you replaced any of these disks between backup and recovery (or if you are recovering the volumes to a different machine), make sure that the new disk configuration includes enough disks whose sizes are at least those of the original disks.
To create the volume structure automatically
1. Boot the machine from a Linux-based bootable media.
2. Click Acronis Bootable Agent. Then, click Run management console.
3. In the management console, click Recover.
Under the archive contents, Acronis Backup & Recovery 11 will display a message saying that it detected information about the volume structure.
4. Click Details in the area with that message.
5. Review the volume structure, and then click Apply RAID/LVM to create it.
3.5.5.2 Creating the volume structure manually
The following is a general procedure for recovering MD devices and logical volumes by using a Linux-based bootable media, and an example of such recovery. You can use a similar procedure in Linux.
To create the volume structure manually
1. Boot the machine from a Linux-based bootable media.
2. Click Acronis Backup & Recovery 11. Then, click Run management console.
3. On the toolbar, click Actions, and then click Start shell. Alternatively, you can press
CTRL+ALT+F2.
4. If necessary, examine the structure of volumes which are stored in the archive, by using the
acrocmd utility. Also, you can use this utility to mount one or more of these volumes as if they were regular volumes (see "Mounting backup volumes" later in this topic).
5. Create the volume structure according to that in the archive, by using the mdadm utility (for MD
devices), the lvm utility (for logical volumes), or both.
Note: Logical Volume Manager utilities such as pvcreate and vgcreate, which are normally available in Linux, are not included in the bootable media environment, so you need to use the lvm utility with a corresponding command. For example: lvm pvcreate, lvm vgcreate, and lvm lvcreate.
6. If you previously mounted the backup by using the acrocmd utility, use this utility again to
unmount the backup (see "Mounting backup volumes" later in this topic).
7. Return to the management console by pressing ALT+F1.
(Do not reboot the machine at this point. Otherwise, you will have to create the volume structure again.)
8. Click Recover, then specify the path to the archive and any other required parameters, and then
click OK.
Note: This procedure will not work if you connect to Acronis Backup & Recovery 11 Bootable Agent remotely, because the command shell is not available in this case.
Example
Suppose that you previously performed a disk-level backup of a machine with the following disk configuration:
The machine has two 1-gigabyte and two 2-gigabyte SCSI hard disks, mounted on /dev/sda,
/dev/sdb, /dev/sdc, and /dev/sdd, respectively.
The first and second pairs of hard disks are configured as two MD devices; both are in the RAID-1
configuration, and are mounted on /dev/md0 and /dev/md1, respectively.
A logical volume is based on the two MD devices and is mounted on
/dev/my_volgroup/my_logvol.
The following picture illustrates this configuration.
Do the following to recover data from this archive.
Step 1: Creating the volume structure
1. Boot the machine from a Linux-based bootable media.
2. In the management console, press CTRL+ALT+F2.
3. Run the following commands to create the MD devices:
mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[ab] mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[cd]
4. Run the following commands to create the logical volume group:
Caution: The pvcreate command destroys all data on the /dev/md0 and /dev/md1 devices.
lvm pvcreate /dev/md0 /dev/md1 lvm vgcreate my_volgroup /dev/md0 /dev/md1 lvm vgdisplay
The output of the lvm vgdisplay command will contain lines similar to the following:
--- Volume group --­VG Name my_volgroup ... VG Access read/write VG Status resizable ... VG Size 1.99 GB ... VG UUID 0qoQ4l-Vk7W-yDG3-uF1l-Q2AL-C0z0-vMeACu
5. Run the following command to create the logical volume; in the -L parameter, specify the size
given by VG Size:
lvm lvcreate -L1.99G --name my_logvol my_volgroup
6. Activate the volume group by running the following command:
lvm vgchange -a y my_volgroup
7. Press ALT+F1 to return to the management console.
Step 2: Starting the recovery
1. In the management console, click Recover.
2. In Archive, click Change and then specify the name of the archive.
3. In Backup, click Change and then select the backup from which you want to recover data.
4. In Data type, select Volumes.
5. In Items to recover, select the check box next to my_volgroup-my_logvol.
6. Under Where to recover, click Change, and then select the logical volume that you created in
Step 1. Click the chevron buttons to expand the list of disks.
7. Click OK to start the recovery. For a complete list of commands and utilities that you can use in the bootable media environment,
see List of commands and utilities available in Linux-based bootable media (p. 144). For detailed descriptions of the acrocmd utility, see the Acronis Backup & Recovery 11 command-line reference.
Mounting backup volumes
You may want to mount a volume stored in a disk backup, for example, to view some files in it before starting the recovery.
To mount a backup volume
1. Use the acrocmd list content command to list the disks and volumes that are stored in the
backup. For example, the following command lists the content of the latest backup of the linux_machine archive:
acrocmd list content --loc=\\server\backups --credentials=user,MyPassWd
--arc=linux_machine
The output will contain lines similar to the following:
type: disk Num Partition Flags Size Type GUID
---------- -------------------- ---------- ---------- ------------- ------
-­Dyn1 my_volgroup-my_lo... 4 GB Ext 3 Dyn2 md0 2.007 GB Ext 2 Disk 1 sda 16 GB DT_FIXED 1-1 sda1 Act,Pri 203.9 MB Ext 2 1-2 sda2 Pri 11.72 GB Reiser 1-3 sda3 Pri 1.004 GB Linux swap Disk 2 sdb 8 GB DT_FIXED 2-1 sdb1 Pri 2.007 GB Ext 2 2-2 sdb2 Pri 2.007 GB None Disk 3 sdc 1 GB DT_FIXED Disk 4 sdd 8 GB DT_FIXED 4-1 sdd1 Pri 2.007 GB Ext 2 4-2 sdd2 Pri 2.007 GB None
2. Use the acrocmd mount command, specifying the volume's name in the --volume parameter.
For example:
acrocmd mount --loc=\\server\backups --arc=linux_machine --mount_point=/mnt
--volume=DYN1
This command mounts the logical volume DYN1 on the mount point /mnt.
To unmount a backup volume
Use the acrocmd umount command, specifying the volume's mount point as a parameter. For
example:
acrocmd umount --mount_point=/mnt
3.6 Support for SNMP
SNMP objects
Acronis Backup & Recovery 11 provides the following Simple Network Management Protocol (SNMP) objects to SNMP management applications:
Type of event
Object identifier (OID): 1.3.6.1.4.1.24769.100.200.1.0 Syntax: OctetString The value may be "Information", "Warning", 'Error" and "Unknown". "Unknown" is sent only in
the test message.
Text description of the event
Object identifier (OID): 1.3.6.1.4.1.24769.100.200.2.0 Syntax: OctetString The value contains the text description of the event (it looks identical to messages published by
Acronis Backup & Recovery 11 in its log).
Example of varbind values:
1.3.6.1.4.1.24769.100.200.1.0:Information
1.3.6.1.4.1.24769.100.200.2.0:I0064000B
Supported operations
Acronis Backup & Recovery 11 supports only TRAP operations. It is not possible to manage Acronis Backup & Recovery 11 using GET- and SET- requests. This means that you need to use an SNMP Trap receiver to receive TRAP-messages.
About the management information base (MIB)
The MIB file acronis-abr.mib is located in the Acronis Backup & Recovery 11 installation directory. By default: %ProgramFiles%\Acronis\BackupAndRecovery in Windows and /usr/lib/Acronis/BackupAndRecovery in Linux.
This file can be read by a MIB browser or a simple text editor such as Notepad or vi.
About the test message
When configuring SNMP notifications, you can send a test message to check if your settings are correct.
The parameters of the test message are as follows:
Type of event
OID: 1.3.6.1.4.1.24769.100.200.1.0 Value: "Unknown"
Text description of the event
OID: 1.3.6.1.4.1.24769.100.200.2.0 Value: "?00000000"
Loading...
+ 149 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use