Veritas Backup Exec is a data protection software product designed for customers with mixed physical and virtual environments, and who are moving to public cloud services. Supported platforms include VMware and Hyper-V virtualization, Windows and Linuxoperating systems, Amazon S3, Microsoft Azure and Google Cloud Storage, among others. All management and configuration operations are performed with a single user interface. Backup Exec also provides integrated deduplication, replication, and disaster recovery[1] capabilities and helps to manage multiple backup servers or multi-drive tape loaders.
Backup Exec employs an automated installation process.[2] Installing Backup Exec 15 on a Windows Server 2012 R2 system takes around 30 minutes, according to reviews.[3] The installation wizard can be started from the Backup Exec Installation Media or the management console to push agents out to the physical servers, Hyper-V/VMware virtual machines, application/database systems hosting Active Directory, Exchange, Oracle database, SQL, and other supported platforms.
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.[4]
When used with tape drives, Backup Exec uses the Microsoft Tape Format (MTF),[5] 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)[5] 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.[6]
In addition, Backup Exec's family of agents and options offer features for scaling the Backup Exec environment and extending platform and feature support. Backup Exec 21.3 is the latest version of Veritas’ backup and recovery software, released on September 6, 2021.[7]
History
Within the “backup” portion of the data protection spectrum, one Veritas 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 WinSvr OS 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.[8]
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.
1982 – Maynard Electronics started. Maynard's software is known as "MaynStream."
2015 – Symantec announced they would be splitting off the Information Management Business which contains Backup Exec, into a new company named Veritas Technologies Corporation acquired by the Carlyle Group.[10]
2016 – Veritas Technologies re-launches as a newly independent company which contains Backup Exec.[11]
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).
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.[2] 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:[12]
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 [13])
Library Expansion Option
Agent for Linux
Virtual Tape Library (VTL) Unlimited Drive Option
Remote Media Agent for Linux (RMAL)
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.[14] Today 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.[15] 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.[15]
Backup Exec can be installed using the following:[16]
Installation wizard from the Backup Exec installation media, which guides through the installation process.
Push-install Backup Exec to remote computers through Terminal Services and the installation media is on a shared drive (network share).[17]
Command line, which is called silent mode installation. The silent mode installation uses the Setup.exe program on the Backup Exec installation media.
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:[18]
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.[19] There are two primary Backup Exec architectures:
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[2] 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:
Backup to disk, tape, or cloud regardless of location.[15]
Recovery Options:
Catalog-assisted granular recovery of objects, files, folders, applications, or VMs (including Exchange, SharePoint, SQL Server, and Active Directory) directly from storage, with no mounting or staging.
Restore to different targets or hardware (Dissimilar Hardware Recovery)
Restore to physical or virtual servers[20]
Simplified Disaster Recovery (SDR)
Guided Search and Restore: Built-in indexing and the ability to restore files through search.
True image restore
Cloud Support[22]
Free S3 Cloud Connector for Backup Exec to back up data to an S3-compatible cloud storage
Free Azure Cloud Connector for Backup Exec to write data to Microsoft Azure cloud storage
Cloud Connector can be deployed on-premises and in-the-cloud
Backup Exec UI has predefined templates for disk-to-disk-to-cloud and direct-to-cloud backups.
Fully integrated Physical-to-Virtual (P2V), which can be used for migrations or instant recovery[35]
Also supports - Backup to Virtual (B2V) and Point-in-time Conversion (PIT)[36]
Integrated Data Deduplication:[37]
Integrated block-level data deduplication[33]
Client, server-side, or OST appliance deduplication
Client deduplication supported for both Windows as well as Linux computers[38]
Optimized duplication (Opt Dup) supports backup "replication" from MMS/MBE to CAS/ CAS to MMS/MBE[39]
Security and Data Encryption:
Software encryption[40]
Hardware encryption (T10 encryption standard)[40]
Database Encryption Key (DEK)[41]
FIPS Version: OpenSSL FIPS 2.0.5[42]
Secure TLS protocol for its SSL control connection (over NDMP) between the Backup Exec Server and the Agent on a remote computer[43]
Management and Reporting:
Centralized administration:[44] Provides a single console for managing the entire Backup Exec environment, creates and delegates jobs to multiple Backup Exec servers, defines device and media sets.
Typical CASO configured Backup Exec environmentCentralized reporting:[44] Monitors all job activity dispatched by the CAS in real time, provides holistic reporting for the entire storage environment, centrally defines notification and alert settings
Operational resiliency: Automatically load-balances jobs across multiple Backup Exec servers, provides job failover from one Backup Exec server to another, centralizes or replicates catalogs for restores.
Management Plug-in for VMware vSphere[45]
Management pack for Microsoft System Center Operations Manager 2007 R2 & 2012 R2 (SCOM)[46]
Management Plug-In for Kaseya[47]
Localization/Language packs[48]
Command Line Interface (BEMCLI)[49]
Media Management:
Automatic robotic/tape drive configuration
Broad tape device support
Heterogeneous Support:
Broad platform support
Bare-metal restore, supports P2V as an option.Backup Exec Command Line Interface - BEMCLI
Support for leading networking topologies
Advanced VSS support
OpenStorage (OST) support
IPv4 & IPv6 support[50]
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.[51] Their NetBackup product does have this capability.[52]
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:[53]
Capacity Edition - Deploy an unlimited number of Backup Exec servers, Agents and Options (Licensed per TB)
Capacity Edition Lite - Includes protection for Windows and Linux operating systems, VMware and Hyper-V virtual environments, Microsoft applications, Oracle, and Enterprise Vault (Licensed per TB)
V-Ray Edition - Protects an unlimited number of guest machines per host including all of the applications and databases (Licensed per occupied processor socket on the virtual host)[54]
Traditional - Licensing per Backup Exec server with Agents and Options available based on need
Releases
Conner Backup Exec 2.1 DOS version
MaynStream for Windows 3.0, May, 1992[55]
Conner Backup Exec 2.1 DOS Version[56]
Conner Backup Exec for Windows NT 3.1, May, 1993
Barney, Doug (June 1994). "Arcada Backup Exec will be bundled with Chicago". InfoWorld. 16 (24): 26.
Arcada Software Backup Exec for Windows NT 6.0, April, 1995[57]
Seagate Software Backup Exec for Windows NT 7.0, August, 1997[58]
^"Symantec Backup Exec 2010 Deduplication And Archiving Suite - Essential Support - 1 Server". lifliycmww. Archived from the original on 2016-03-05. Retrieved 2016-02-25.
^Hacking; Security; Cybercrime; Vulnerability; Malware; hijackers, Cisco and Level 3 team up to squash brute force server; embarrassed, Cyber-crypto-criminal-cock-up Little money and (probably); easier, Bad news everyone: Cybercrime is getting even. "Symantec buys Veritas for $13.5bn stock". The Register. Retrieved 2016-02-19.{{cite web}}: CS1 maint: numeric names: authors list (link)
^"Symantec to split into security and storage software companies". Reuters. 2014-10-09. Retrieved 2016-02-19.
^"Newly Independent Veritas Re-Launches as Information Management Leader | Business Wire". www.businesswire.com. February 2016. Retrieved 2016-02-25.
^"Backup Exec TM 16 Agents and Options" (PDF). Veritas. Veritas Technologies LLC. 2016. Retrieved 14 January 2018.
^"Veritas Backup Exec 16 FAQ" (PDF). FAQ: Disaster and Recovery. Veritas Technologies LLC. October 2016. Retrieved 25 October 2019.
^"Support for Backup Exec in virtual and IaaS environments". www.veritas.com. Retrieved 2016-02-25.
^ abc"Backup Exec 16 Installation Best Practices". support.veritas.com. Veritas Technoloiges, LLC. Archived from the original on 2017-01-18. Retrieved 2016-02-25.
^"Lab Validation Symantec Backup Exec 2014" (PDF). Archived from the original (PDF) on August 17, 2014.
^"Reasons why the data throughput rate can be slower than the theoretical maximum when backing up to or restoring from tape media or disk (B2D) & how to troubleshoot or improve backup performance". www.veritas.com. Archived from the original on 2016-12-20. Retrieved 2016-02-23.
^ ab"9 Reasons to Take a Look at Backup Exec 15". Technically Speaking. Retrieved 2016-02-23.
^"Agent and Agentless VM Backup and Recovery – Unraveling the myths". www.veritas.com. 2012-09-28. Retrieved 2016-02-23.
^"Symantec adds P2V to latest Backup Exec". SearchServerVirtualization. Retrieved 2016-02-26.
^"Cosonok's IT Blog: Symantec Backup Exec 2012 SP1 Notes". www.cosonok.com. 4 July 2012. Retrieved 2016-02-26.
^"Symantec Shows Backup Exec a Little Dedupe Love; Lays out Source Side Deduplication Roadmap - DCIG". DCIG. 7 July 2009. Retrieved 2016-02-26.
^ "Deduplication methods for Backup Exec agents". www.veritas.com. Archived from the original on 2016-03-07. Retrieved 2016-02-26.
^"About using IPv4 and IPv6 in Backup Exec". www.veritas.com. Archived from the original on 2016-12-20. Retrieved 2016-02-23.
^Veritas tech note: What is the difference between multiplexing and multistreaming?, article #000004808, September 14, 2015, http://www.veritas.com/docs/000004808
^"About multiplexing". systemmanager.ru/nbadmin.en. Retrieved 22 June 2019.
^"So what exactly is in this Backup Exec V-Ray edition any way?". The Spiceworks Community. October 2012. Retrieved 2016-02-19.
^InfoWorld. InfoWorld Media Group, Inc. 1993-04-26. ISSN 0199-6649.
^"DANIELSAYS.COM - Daniel's Legacy Computer Collections - Screen Shot Gallery - DOS - Backup Exec 2.1(f) DOS Version". www.danielsays.com. Archived from the original on 2015-01-27. Retrieved 2016-02-19.
^Davis, Ziff (1996-02-20). PC Mag. Ziff Davis, Inc. ISSN 0888-8507.
^Software, Seagate. "Powerful New Seagate Backup Exec for Windows NT Sets the Standard for Windows NT Enterprise Storage Management". www.prnewswire.com. Retrieved 2016-02-19.
^Staff Writer (1999-06-24). "Veritas Software releases new version of Veritas Backup Exec Small Business Server Solution". ITWeb Technology News. Retrieved 2016-02-23.
^Corporation, VERITAS Software. "VERITAS Extends Data Protection Leadership With Backup Exec 9.0". www.prnewswire.com. Retrieved 2016-02-23.
^"Veritas Backup Exec 9.1 for Windows Servers Specs". CNET. Retrieved 2016-02-19.
^"VERITAS Partners Worldwide See Golden Opportunities in Backup Exec 10.0". Symantec. Archived from the original on March 1, 2016. Retrieved 2016-02-19.
^"Symantec Backup Exec 10d is "Designed for Disk" and Delivers Continuous Data Protection". Symantec. Archived from the original on March 1, 2016. Retrieved 2016-02-19.
^"Symantec Backup Exec 11d Review". ZDNet. Archived from the original on December 27, 2014. Retrieved 2016-02-19.
^"Symantec Busts Out SaaS with Backup Exec 12 | Network Computing". www.networkcomputing.com. 2008-02-19. Retrieved 2016-02-19.
^Ibm; Emc; Netapp; Seagate; Hp; them, Boring old Brocade just sits there making money Damn; products, Cisco strengthens its hardware-defined networking; continues, HP storage revenues declining as the dithering. "Symantec embraces server virtualization with Backup Exec". The Register. Retrieved 2016-02-19.
^"Backup Exec 2010 R3 revision 5204 Service Pack 2". www.veritas.com. Archived from the original on 2016-12-20. Retrieved 2016-02-23.
^ ab"ACME Communications – Backup Exec 2010 R3 SP3 and Backup Exec 2012 SP2 have been released!". Retrieved 2016-02-19.
^"Symantec NetBackup 7.5 and Backup Exec 2012 Global Availability Announced | StorageReview.com - Storage Reviews". www.storagereview.com. Retrieved 2016-02-19.
^"Announcing Backup Exec 2012 SP1 Available Now!". www.veritas.com. June 2012. Retrieved 2016-02-19.
^"Backup Exec 2012 Service Pack 3 with added VMware vSphere 5.5 support". Symantec. Retrieved 2016-02-19.[dead link]
^"Backup Exec 2012 Service Pack 4 is Available Now". www.veritas.com. 13 March 2014. Retrieved 2016-02-19.
^"Backup Exec 2014 is Now Available!". www.veritas.com. 2 June 2014. Retrieved 2016-02-23.
^"Backup Exec 2014 SP1 Now Available". www.veritas.com. 22 September 2014. Retrieved 2016-02-19.
^"Backup Exec™ 15 Delivers Performance and Simplicity for Hybrid Clouds". www.veritas.com. 6 April 2015. Retrieved 2016-02-19.
^"Feature Pack 1 for Backup Exec 15 delivers improved performance, intelligent backups and enhanced platform support". www.veritas.com. 8 July 2015. Retrieved 2016-02-19.
^"Backup Exec 15 Feature Pack 2 includes new Cloud Connector, platform support, enhanced user experience and more - Now Available!". www.veritas.com. 27 October 2015. Retrieved 2016-02-19.