Backup Exec

Backup Exec
Original authorMaynard Electronics
DeveloperArctera
Release1980s
Stable release
22.2 / Oct, 2023
Written inC, C++, C#, .Net, Python
Operating systemWindows 2019, Windows 2016, Windows 2012 R2, Windows 2012, Windows 2008 R2, Windows 2008, Windows 2003 R2, Windows 10, Windows 8.1, Windows 7, Red Hat Enterprise Linux, SUSE Linux Enterprise Server
PlatformWindows Server, Linux, VMware vSphere, Microsoft Hyper-V
Size2.4 GB
Available inEnglish, French, German, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese, Spanish, Traditional Chinese
LicenseProprietary commercial software
Websitehttp://www.backupexec.com

Backup Exec is a commercial backup software product from Arctera originally released in the 1980s. It has been owned by several different companies, including Veritas, Symantec, and Seagate.

With its client/server design, Backup Exec provides backup and restore capabilities for servers, applications and workstations across the network. Backup Exec recovers data, applications, databases, or systems from an individual file, mailbox item, table object, or entire server. Current versions of the software support Microsoft, VMware, and Linux, among others. Backup Exec also provides integrated deduplication, replication, and disaster recovery capabilities and helps to manage multiple backup servers or multi-drive tape loaders. In addition, Backup Exec's family of agents and options offer features for scaling the Backup Exec environment and extending platform and feature support.

History

Within the "backup" portion of the data protection spectrum, one Arctera product, Backup Exec, has been in the market for more than two decades. Since the early days of Microsoft's journey to turn its Windows Server into the world's dominant client-server operating system, Backup Exec has been one of a handful of technologies to protect it. As the Windows Server grew to become a platform of choice for application enablement and user productivity, Backup Exec's media/platform support, application support, and internal operation evolved at a similar pace.

Backup Exec has a long history of successive owner-companies. Its earliest roots stretch back to the early 1980s when Maynard Electronics wrote a bundle of software drivers to help sell their tape-drive products.

Early product logo
product logo c.1994

Architecture

Core components

The core components that are contained in a basic Backup Exec architecture include the following:

  • A Backup Exec server is the heart of a Backup Exec installation. The Backup Exec server is a Windows server that:
    • Runs the Backup Exec software and services that control backup and restore operations
    • Is attached to and controls storage hardware
    • Maintains the Backup Exec database, media catalogs, and device catalogs
  • The Backup Exec Administration Console is the interface to control a Backup Exec server.
    • The Administration Console can be run directly on a Backup Exec server or from a remote system (using a Backup Exec Remote Administration Console).
  • Storage devices attached to the Backup Exec server contain the media on which backup data is written.
    • Backup Exec supports many different types of devices and media, including cloud, disk-based and tape-based. Backup Exec supports unlimited number of clients, NDMP-NAS systems, tape drives, and tape libraries.
  • Clients are the systems that contain the data which the Backup Exec server backs up.
    • Clients can include database servers, application servers, file servers, and individual workstations.
      An illustration of the Backup Exec platform

Add-on components

Backup Exec Agents and Options expand the features and functionality of core Backup Exec server to support the most common server applications, including Microsoft Exchange, SharePoint and SQL Server, Oracle, Windows and Linux clients, server operating systems, and the Hyper-V and VMware hypervisors. Not all agents are agents in the traditional sense. For example, the Agent for VMware and Hyper-V is not carrying out the backup process. The agent is simply collecting meta data (takes a few seconds) so that Backup Exec can perform granular recoveries directly from storage at a point in the future - no mounting required.

Here is a list of Backup Exec Agents and Options:

Agents Options
Agent for VMware and Hyper-V Deduplication Option
Agent for Applications and Databases Enterprise Server Option
Agent for Windows NDMP Option
Agent for Mac (no longer supported BE16) Library Expansion Option
Agent for Linux Virtual Tape Library (VTL) Unlimited Drive Option
Remote Media Agent for Linux (RMAL)

Tape format

When used with tape drives, Backup Exec uses the Microsoft Tape Format (MTF), which is also used by Windows NTBackup, backup utilities included in Microsoft SQL Server, and many other backup vendors and is compatible with BKF. Microsoft Tape Format (MTF) was originally Maynard's (Backup Exec's first authors) proprietary backup Tape Format (MTF) and was later licensed by Microsoft as Windows standard tape format. In addition, Microsoft also licensed and incorporated Backup Exec's backup engine into Windows NT, the server version of Windows.

Installation

Backup Exec and its options can be installed on a local computer, a remote computer, within a virtual environment, or on a public cloud "Infrastructure as a Service (IaaS)" virtualization platform. Backup Exec supports the Backup Exec server installation on 64-bit operating systems only. However, the Agent for Windows can be installed on 32-bit operating systems. Several methods are available for installing Backup Exec. An Environment Check runs automatically during installation to make sure that the installation process can complete. If Backup Exec finds any configuration issues that can be fixed during the installation, or that may prevent Installation, warnings appear.

Backup Exec can be installed using the following:

Additionally, Backup Exec installation media also has a Remote Administrator feature which can be installed on a remote computer or workstation to administer the Backup Exec server remotely.

Backup Exec may install the additional products:

Configuration

Backup Exec installations can have one or more Backup Exec servers, which are responsible for moving data from one or more locations to a storage medium, including cloud, disk, tape, and OST device. The data may be from the local system or from a remote system. There are two primary Backup Exec architectures:

Central Admin Server Option architecture

1. Standalone Backup Exec configuration (Two-Tier)

A single Backup Exec server is assigned the standalone Backup Exec server role. Each server runs the Backup Exec software and the services that control backup and restore operations of multiple clients. Each Backup Exec server maintains its own Backup Exec database, media catalogs, and device catalogs.

2. Central Admin Server Option (CASO) configuration (Three-Tier)

Large environments may contain multiple Backup Exec servers responsible for backing up many different client systems. Backup Exec servers in large environments can run independently of each other if each server is managed separately. Separate server management may not be an issue if there are only two or three Backup Exec servers, but it can become unwieldy as the environment grows. Backup Exec can centralize the management of multiple Backup Exec servers using an add-on option called the Backup Exec Central Admin Server Option (CASO). CASO ensures that everything throughout the network is protected by a single system that can be managed from one console and also balances the workload across all Backup Exec servers in the environment.

In a CASO environment, one Backup Exec server can be configured to be the Central Admin Server (CAS), while other Backup Execs become managed Backup Exec servers (MBESs) that are managed by the CAS. The CASO configuration simplifies the management and monitoring of enterprise-level environments.

Features and Capabilities

Backup Exec includes the following features and capabilities:

Multiplexing limitation

Backup Exec does not have support for sending data streams from multiple parallel backup jobs to a single tape drive, which Veritas refers to as multiplexing. Their NetBackup product does have this capability.

Multiplexing can reduce backup times when backing up data from non-solid state sources containing millions of small or highly fragmented files, which require very large amounts of head-seeking using traditional mechanical hard drives, and which significantly slow down the backup process.

When only a single job is running, and the source server is constantly seeking at a high rate, the tape drive slows down or may stop, waiting for its write cache to be filled. These delays accessing data can cause the backup availability window to be exceeded, when multiple servers with slow transfer rates are being backed up one after the other to the tape device.

A workaround to this is to install temporary disk storage in the backup server to use as a cache for the backup process. This storage is split into hundreds of small 1-5 gigabyte data blocks. Backups to the data blocks can be done in parallel, and each of the separate disk-based backup jobs are configured to duplicate and append to tape when completed.

Licensing

Backup Exec has the following licensing options:

Releases

Conner Backup Exec 2.1 DOS version
Symantec Backup Exec 2010 Administration Console

See also