The Backup Manager is your primary tool for backup and recovery. It specializes in enterprise-level data that cannot be handled with the help of mass-market solutions: databases, virtual machines and content management systems.

Supported features

Operating systems for backup and recovery

You can back up and restore data located on Windows OS, Mac OS X and GNU/Linux. Please see the table below for the full list of supported versions.

*For Windows Server 2016, only the features compatible with Windows Server 2012 R2 are supported.

** In addition to the major Linux distributions that are regularly tested in-house, it is possible to back up and restore data located on any GNU/Linux x86 and x86_64/amd64 distribution with glibc 2.4 or higher (with NPTL enabled). For the backup and restore of MySQL, glibc 2.5 or higher is required.

Data sources for backup and recovery

The Backup Manager handles individual files and directories as well as complex systems such as these:

• MS SQL


• VMware


• Hyper-V


• MS Exchange


• MS SharePoint


• Oracle


• MySQL

In addition, you can back up and recover the configuration of your operating system (the "System State" data source).

Please view the Data sources page for system compatibility details.

Backup-related features

"Yes" next to the name of an operating system means that the feature is available on all of the supported versions of that operating system.

Recovery-related features

"Yes" next to the name of an operating system means that the feature is available on all of the supported versions of that operating system.

All of the recovery-related features except for the bare metal recovery and the Standby Image backup are available in the Recovery Console (a multi-instance recovery tool for system administrators).

Common features

The rest of the features are available on all of the supported operating systems.

• Multi-lingual support. The Backup Manager can be used in any of these 7 languages: English, Dutch, Russian, German, Spanish, French, or Portuguese.


• Interface selection. You can operate the Backup Manager through the command line or use the graphic user interface.


• Custom branding. You can brand the Backup Manager for your end users removing references to the developer (this is done through the Cloud Management Console). Use a custom name, logo, color scheme, and icons.


• Remote management. You can install the Backup Manager remotely through the Cloud Management Console and send remote commands to the Backup Manager devices of your end users.


• Proxy connection. The Backup Manager can work from behind a proxy server.


• Email reports. Enable the delivery of email notifications on the statuses or recent backup and recovery sessions. This can be done by an end user in the Backup Manager or remotely by a service provider or a system administrator.


• Bandwidth usage control. Be sure your bandwidth usage will never exceed a specified limit.


• Updates.There are 2 ways to update the Backup Manager to the latest version: by downloading the latest version and installing it on top of the current one or by letting the app update itselt automatically.

Data processing technologies

Backup data is processed locally on the client side and then sent to remote storage. Data processing isn't platform-dependent so all users can benefit from advanced data processing technologies such as deep deduplication, delta slicing, directory hashing, compression, secure encryption, caching and so on.

Data sources

Practically any file located on a workstation or server can be protected against loss using the Backup Manager. Some files are not subject to backup – for example files from the Backup Manager installation folder and temporary files on Windows.

Complex systems such as databases, virtual machines and content management systems require specific approaches to keep backup data consistent (this guarantees that the system will continue working after recovery). That is why you will find different data sources in the Backup Manager (a separate data source for each type of data).

*To back up network shares on Mac OS X and Linux, you need to permanently connect the network resource to your desktop (it will be recognized as the Files and Folders data source after that).

Backup technology

Data backup in the Backup Manager is session-based. A session is a process during which a data selection on a client device is backed up to a remote server. Backup sessions result in the creation of virtual copies that can be retrieved at any time.

Because data tends to change, backup sessions usually run on a repeated basis (for instance, every day). You can start a new backup session manually or you can create a schedule for it.

1 data source = 1 backup session

There is a separate session for each data source. For example, if a backup selection has two data sources (Files and folders and System state), there will be two backup sessions.

Backup session structure

All backup sessions go through two stages: scanning and processing. The procedure varies slightly for initial sessions (performed on a device for the first time) and subsequent sessions (all other sessions after the initial one).

Structure of initial backup sessions

Stage 1: Scanning

At this stage, the Backup Manager makes a list of data to back up. In short, here is what it does:

• Performs a system scan to locate the data selected for backup.


• Puts the files in a queue.

Stage 2: Processing

The Backup Manager takes the queued files one by one in the order of priority (user-defined) and recentness (defined by change dates) and handles them in the following way:

• Cuts them into smaller fragments known as slices.


• Calculates a hash (a unique data fingerprint) for each slice. During subsequent backups, the hash will be used to detect changes.


• Compresses the slices to reduce their size (saves bandwidth and storage space).


• Encrypts the slices using the private security key set during Backup Manager installation (the data will be inaccessible without the key). One of the following encryption methods is used: AES-128 (default), AES-256, or Blowfish-448.


• Combines multiple slices into cabinets to utilize network and storage resources more efficiently.


• Transfers the cabinets to the Cloud. By default, two simultaneous connections are established. Their number can be customized within the range of 1 to 10 (view instructions). The higher the number of connections, the faster your data will reach the storage. However, a high number of connections consumes more bandwidth and memory resources.


• Registers all files and slices in a local database called the Backup Register and uploads the database to the Cloud.

When the backup session is complete, the data becomes available for recovery. You can see a new entry in the Session time list.

Structure of subsequent backup sessions (delta backup)

Stage 1: Scanning

The Backup Manager scans the system to find the data to back up and compares the results with those from the previous session. The comparison is drawn based on file attributes (names, change dates, size, access permissions and so on) stored in the Backup Register. If at least one attribute in a file has changed, the file is added to the queue for further processing.

Stage 2: Processing

The Backup Manager slices the files in the order of priority and recentness and calculates hashes for the slices. Then the hashes are compared to the hashes from the previous backup session. New slices whose hashes don't have matches in the storage undergo the standard procedure. They are compressed, encrypted, combined into cabinets and delivered to the storage. The Backup Register is updated with new records after that.

Sequence of backup sessions

Generally, backup sessions run successively. You can start the next backup session after the current one is complete (the Run backup button is unavailable while there is an active backup process). However, they can sometimes overlap. This can happen if they were scheduled shortly one after another or if one session had been started manually just before a scheduled session was due. In this case, the Backup Manager completes the scanning stages for all of the sessions (one after one) and then merges the queues created during scanning. Priority files and files with recent change dates are processed in the first place no matter which backup session they belong to.

Note that backup sessions involving data archiving are never interrupted. Other sessions can start only after they are completed.

The scheme applies to the following data sources: Files and Folders, Network shares, Oracle, and System State (on Windows XP and Windows Server 2003).

Overlapping backup sessions of the same data source

There cannot be two simultaneous backup sessions of the same data source if the data source is based on the Volume Shadow Copy technology or if the data source requires resource-consuming processing (MS SharePoint, MS Exchange, VMware, System State on Windows Vista and greater). However, these data sources can be backed up simultaneously with other data sources.

The session that has started first is completed normally. Subsequent sessions that started while it was in progress are skipped. If a user opens the Overview tab and chooses statistics for that day, there will be an error message similar to the one below.

Backup sessions vs. restore sessions

In addition to backup sessions, there are restore sessions that take place whenever a user starts a restore process. Restore sessions have a higher priority than backup sessions. So they are always processed in the first place.

Practical implications

1. Backup Manager users needn't make any preparations for backup: move the files to a separate folder, compress them or check for duplicates.


2. Data that is sent to storage is always unique in the sense that only changed blocks are transferred and only one copy of each change is submitted. This guarantees that bandwidth and storage space is used economically.


3. When the Backup Manager searches for changes, it compares file properties first. Only if a property has changed, a content analysis is made. This drastically reduces the amount of time and processing required for change detection, especially when it comes to large data sets.


4. Users who want to speed up their backup sessions can increase the number of simultaneous connections. It is best to do it gradually. This way the user can make sure the increased transfer activity isn't affecting computer performance and isn't clogging the Internet connection.


5. If it is necessary to restore something while a backup is in progress, the user can start a restore right away. All active backup sessions will be put on hold until the restore is completed.

Backup steps

1. Configure backup selection

Firstly, you should specify what you want to back up. This is done on the Backup tab in the Backup Manager.

To add a data source to your backup selection, click the Add button next to its name.

Then select the files, folders or components (such as databases, virtual disks and so on) that should be backed up. Here is an example for the "Files and Folders" data source.

You can let the Backup Manager help you choose data for backup. The feature is called Automatic File Selection.

To make sure all necessary data has been included into your backup selection, click on the name of the data source.

If you clear your backup selection afterwards, you'll be offered to remove all backup copies of these files from the Cloud. The action is irreversible.

2. Start backup

Option A: Start a one-time backup

A backup can be initiated manually at any time. Open the Backup tab and click Run backup.

Note that the Run backup button is unavailable until at least one data source is configured for backup.

The duration of the backup process depends on the size of your backup selection, the data transfer speed and the performance of your computer.

Option B (recommended): Enable regular backups

It is most convenient to set up a backup schedule and let backups run automatically without your interference. Note that your computer should be turned on during backups and shouldn't enter the sleep mode.

To create a backup schedule or edit existing schedules, go to Preferences > Schedule.

 

Backup options

There some options that you can consider for faster and efficient backups.

• Automatic file selection


• Backup filters


• Archiving


• Backup Accelerator


• Seed loading

Recovery steps

All data sources in the Backup Manager are recovered according to a general scheme. Please check if there are additional requirements and settings for the data sources you use.

Restore steps (general scheme)

1. Install the Backup Manager on the computer or virtual machine you want to recover the data to (if it isn't installed there yet).


2. Open the Restore module, and then select a data source from the vertical menu. The selection includes all data sources that have been backed up at least once on the current device.


3. From the Session time list, select the backup session you want to restore. The letter (A) next to the name of a session means that the session is archived (more on backup session archiving). (L) means that the session has been saved locally in the LocalSpeedVault and the data isn't synchronized with the Cloud yet.


4. Select the data you want to restore. For some data sources like Files and folders, VMware and Hyper-V, you can expand the file tree and select individual files or directories. For other data sources only the root folder can be selected.


5. Specify where to restore the selected data. Keep the Restore to field blank if you want to restore the data to the original location (in-place restore).


6. Click Restore and hold on till the restore process is completed. You can close the Backup Manager while the recovery is in progress (it will continue in background).

Common recovery options

File search

If you want to restore a particular file, enter a complete or partial name into the Search field in the upper-left corner.

Please note that the Search option does not accept wildcards or path names. The search isn't case sensitive. When viewing the search results, you can select the most recent version of a file or expand the list of prior versions.

Choice of target location

Two types of restores can be distinguished:

• In-place restores performed to the original location (the default option). This can be done if the original data is no longer there or if you want to overwrite it with a recovered version. If you choose this option, keep the Restore to field blank.


• Restores to a new location. Specify a path to the target directory in the Restore to field.

 

Note that the Backup Manager installation folder is not subject to the in-place restore. This helps prevent the loss of settings so you can be sure your backup data stays safe.

Generally, you can restore data to any of the following locations:

• Your hard drive.


• A removable storage drive mapped as a fixed drive.


• A network share (only for in-place restores). It must be available during the restore (it isn't possible to restore data if the target computer has entered the sleeping mode or got disconnected from the local network). Also your user account must have read and write access to the target folder.

Skip files that have not changed

You can let the Backup Manager skip content checks for files which properties haven't changed since the selected backup session. This helps optimize data processing operations and reduces restore times.

Additional recovery settings for data sources

Data source	Additional requirements	Pre-recovery settings	Additional recovery settings
Files and folders	No	No	No
System state	Yes	For domain controllers only	No
MS SQL databases	No	For master database recovery only	No
VMware machines	For individual file recovery only	Power off the virtual machine if it's going to be overwritten by the restore	Server access settings for restore to a new location
Hyper-V machines	For individual file recovery only	Power off the virtual machine if it's going to be overwritten by the restore	No
MS Exchange databases	The original data stores must be available (for in-place restores)	No	No
MS Exchange items (Granular Exchange restore)	Yes	Yes	Yes (optional)
Oracle databases	No	No	Post-recovery
MySQL databases	No	Stop the MySQL server (for in-place restores)	No

Please click on the name of your data source for details.

 

Recovery options

There are some additional recovery options that you can take advantage of.

• Stanby Image Backup


• Continuous restore

General options

• Enablining a local storage directory (LocalSpeedVault)


• Setting up pre- and post-backup scripts


• Command-line interface (ClientTool)


• Advanced settings (config file)

Advanced settings

When you install the Backup Manager, a special configuration file is created in its installation folder (config.ini). Advanced users can find it convenient to change some basic settings through this file and also to access advanced settings.

Config.ini location

The location of the config.ini file depends on your operating system.

Operating system	File path
Windows	C:/Program Files/Backup Manager/config.ini
Mac OS X	/Library/Application Support/MXB/Backup Manager/config.ini
GNU/Linux	/opt/MXB/etc/config.ini

Updating config.ini

1. Open the Backup Manager installation folder and find the config.ini file inside.


2. Edit the settings as needed, save the changes and close the file.


3. Restart the Backup FP (an internal process associated with the Backup Manager). This is necessary to apply the new settings.

To learn more about restarting the Backup FP, view this instruction.

Parameters supported by config.ini:

• Required parameters (default configuration)


• Proxy settings (optional)


• Automatic file selection settings (optional)


• Log settings (optional)


• Misc. optional settings

Logging

The Backup Manager automatically writes down its operations to a special file. The file is called an application log or Backup FP log. It contains non-personal data that lets system administrators and support engineers make sure all backup and recovery processes are set up correctly. If something goes wrong, the log is valuable for troubleshooting.

Versions of the application log

There are two versions of the application log: a local version and a server version. The local version is available on the hard drive where the Backup Manager is installed. The server version is stored in the Cloud and can be accessed from the Backup Manager.

The local version has more data while the server version displays the latest records. For detail, see the Application log settings section below.

How to view the application log (local and server versions)

Application log structure

Each log record is structured in the following way:

[timestamp] [type] [thread_id] [module]: [message]

The [module] component is optional.

For example:

[2015-01-14 10:30:22.083339] [D] [07200] [Periodic Task Thread]: "Profiler controller" is being executed...

Application log settings

As the size of the log file on the hard drive reaches 5 MB, the Backup Manager stops adding new entries to it and creates a new file instead. The file is saved to the same folder. If debug logging is on, the size limit is extended to 50 MB.

Generally, after the total size of all application log files on the user's computer reaches 50 MB (or 500 MB in case of debug logging), the oldest of them are cleared to free space for new files. These settings have proven to be comfortable for most users. However, sometimes (for example, when a tricky case is investigated), it may be necessary to customize the pre-defined size limits. This is done by adding parameters to the [Logging] section of the config file (learn more).