Backup Exec Wikipedia. Veritas Backup Exec. Veritas_Backup_Exec_9.1.jpg/440px-Veritas_Backup_Exec_9.1.jpg' alt='Best Practices For Backup Exec 2012 Software Encryption Key' title='Best Practices For Backup Exec 2012 Software Encryption Key' />Backup Exec 15 and later stores sensitive information in the Backup Exec Database using encryption. A database encryption key is used to encrypt information such as. Symantec Enterprise Technical Support. Endpoint Encryption. ProxySG Software SGOS Web Security Service WSS PacketShaper. Original authorsMaynard Electronics. DevelopersVeritas Technologies LLCInitial release. Stable release. 16 November 7, 2. Development status. Publicly released. Written in. C, C, C,. Net, Python. Operating system. Windows 2. 01. 2 R2, Windows 2. Windows 2. 00. 8 R2, Windows 2. Windows 2. 00. 3 R2, Windows 1. BE15Deployment.png' alt='Best Practices For Backup Exec 2012 Software Encryption Key' title='Best Practices For Backup Exec 2012 Software Encryption Key' />Windows 8. Windows 7, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Windows 2. Platform. Windows Server, Linux, VMware v. Sphere, Microsoft Hyper VSize. GBAvailable in. English, French, German, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese, Spanish, Traditional Chinese. License. Proprietary commercial software. Websitehttp www. Veritas Backup Exec is a data protection software product designed for customers who have mixed physical and virtual environments, and who are moving to public cloud services. Supported platforms include VMware and Hyper V virtualization, Windows and Linux operating 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 recovery1 capabilities and helps to manage multiple backup servers or multi drive tape loaders. Backup Exec has an installation process that is well automated. Installing Backup Exec 1. Windows Server 2. R2 system takes around 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 VVMware virtual machines, applicationdatabase systems hosting Active Directory, Exchange, Oracle database, SQL, and other supported platforms. Best Practices For Backup Exec 2012 Software Encryption Key' title='Best Practices For Backup Exec 2012 Software Encryption Key' />How to manage encryption keys. With its clientserver 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, to an entire server. Current versions of the software support Microsoft, VMware, and Linux, among a longer list of supported hardware and software. 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 MTF5 was originally Maynards Backup Execs 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 Execs backup engine into Windows NT, the server version of Windows. In addition, Backup Execs family of agents and options offer features for scaling the Backup Exec environment and extending platform and feature support. Backup Exec 1. 6 is the latest version of Veritas backup and recovery software. HistoryeditWithin the backup portion of the data protection spectrum, one Veritas product, Backup Exec, has been in the market for more than two decades. Best Practices Backup and Recovery Strategies. Why You Lost Your Windows 10 Product Key. Data protection and backup needs. Using Encryption with Backup Exec. Backup Exec provide the Software Encryption. Any user of this installation of Backup Exec can use the key to back up and. Create a certificate or asymmetric Key to use for backup encryption. Recommended Practices. Create a backup of the encryption certificate and keys to a location. Secure with Confidence. Encryption is performed by the tape. BACKUP EXEC VERSION KEY FEATURES 15 2014 2012 2010 12. T10 encryption. How to manage encryption keys. Three ransomware backup best practices to. DXiSeries Configuration and Best Practices Guide. This document assumes that the reader has basic expertise with Veritas Backup Exec 2012 or. Since the early days of Microsofts journey to turn its Windows Server into the worlds dominant client server operating system, Backup Exec has been one of a handful of technologies to protect it. As the Win. Svr OS grew to become a platform of choice for application enablement and user productivity, Backup Execs mediaplatform 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 1. Maynard Electronics wrote a bundle of software drivers to help sell their tape drive products. Maynard Electronics started. Maynards software is known as Mayn. Stream. 1. 98. 9 Maynard is acquired by Archive Corp. Mayn. Stream is available for DOS, Windows, Macintosh, OS2, and Net. Ware. 1. 99. 1 Quest Development Corporation is independently formed to develop backup software under contract for Symantec. Conner Peripherals acquires Archive Corp. Backup Exec. 1. 99. Quest acquired rights to Fast. Back for Macintosh, and hired its principal author, Tom Chappell, from Fifth Generation Systems. One of the first iteration of Backup Exec Maynards Maynstream. Conner creates a subsidiary, Arcada Software, by acquiring Quest and merging it with their existing software division. Arcada acquires the Sy. Tron division from Rexon, including their OS2 backup software. Conner is acquired by Seagate Technology and Arcada is merged into its subsidiary Seagate Software. VERITAS Software acquires Seagate Softwares Network and Storage Management Group, which included Backup Exec. Symantec acquires VERITAS, including Backup Exec. Symantec announced they would be splitting off the Information Management Business which contains Backup Exec, into a new public company named Veritas Technologies Corporation. Veritas Technologies re launches as a newly independent company which contains Backup Exec. ArchitectureeditCore componentseditThe 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 componentseditBackup Exec Agents and Options expand the features and functionality of core Backup Exec server to support the most common server applications, including Microsoft Exchange, Share. Point and SQL Server, Oracle, Windows and Linux clients, server OSs, 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 1. Agents. Options. Agent for VMware and Hyper VDeduplication Option. Agent for Applications and Databases. Enterprise Server Option. Agent for Windows. NDMP Option. Agent for Mac. Library Expansion Option. Agent for Linux. Virtual Tape Library VTL Unlimited Drive Option. Remote Media Agent for Linux RMALInstallationeditBackup 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 Iaa. S virtualization platform. Backup Encryption Microsoft Docs. THIS TOPIC APPLIES TO SQL Server. Azure SQL Database. Azure SQL Data Warehouse Parallel Data Warehouse This topic provides an overview of the encryption options for SQL Server backups. It includes details of the usage, benefits, and recommended practices for encrypting during backup. Overview Starting in SQL Server 2. SQL Server has the ability to encrypt the data while creating a backup. By specifying the encryption algorithm and the encryptor a Certificate or Asymmetric Key when creating a backup, you can create an encrypted backup file. All storage destinations on premises and Window Azure storage are supported. In addition, encryption options can be configured for SQL Server Managed Backup to Microsoft Azure operations, a new feature introduced in SQL Server 2. To encrypt during backup, you must specify an encryption algorithm, and an encryptor to secure the encryption key. The following are the supported encryption options Encryption Algorithm The supported encryption algorithms are AES 1. AES 1. 92, AES 2. Triple DES Encryptor A certificate or asymmetric Key Caution It is very important to back up the certificate or asymmetric key, and preferably to a different location than the backup file it was used to encrypt. Without the certificate or asymmetric key, you cannot restore the backup, rendering the backup file unusable. Restoring the encrypted backup SQL Server restore does not require any encryption parameters to be specified during restores. It does require that the certificate or the asymmetric key used to encrypt the backup file be available on the instance that you are restoring to. The user account performing the restore must have VIEW DEFINITION permissions on the certificate or key. If you are restoring the encrypted backup to a different instance, you must make sure that the certificate is available on that instance. If you are restoring a backup from a TDE encrypted database, the TDE certificate should be available on the instance you are restoring to. Benefits. Encrypting the database backups helps secure the data SQL Server provides the option to encrypt the backup data while creating a backup. Encryption can also be used for databases that are encrypted using TDE. Encryption is supported for backups done by SQL Server Managed Backup to Microsoft Azure, which provides additional security for off site backups. This feature supports multiple encryption algorithms up to AES 2. This gives you the option to select an algorithm that aligns with your requirements. You can integrate encryption keys with Extended Key Management EKM providers. Prerequisites The following are prerequisites for encrypting a backup Create a Database Master Key for the master database The database master key is a symmetric key that is used to protect the private keys of certificates and asymmetric keys that are present in the database. For more information, see SQL Server and Database Encryption Keys Database Engine. Create a certificate or asymmetric Key to use for backup encryption. For more information on creating a certificate, see CREATE CERTIFICATE Transact SQL. For more information on creating an asymmetric key, see CREATE ASYMMETRIC KEY Transact SQL. Important Only asymmetric keys residing in an Extended Key Management EKM are supported. Restrictions The following are restrictions that apply to the encryption options If you are using asymmetric key to encrypt the backup data, only asymmetric keys residing in the EKM provider are supported. SQL Server Express and SQL Server Web do not support encryption during backup. However restoring from an encrypted backup to an instance of SQL Server Express or SQL Server Web is supported. Previous versions of SQL Server cannot read encrypted backups. Appending to an existing backup set option is not supported for encrypted backups. Permissions. To encrypt a backup or to restore from an encrypted backup VIEW DEFINITION permission on the certificate or asymmetric key that is used to encrypt the database backup. Note Access to the TDE certificate is not required to back up or restore a TDE protected database. Backup Encryption Methods The sections below provide a brief introduction to the steps to encrypting the data during backup. For a complete walkthrough of the different steps of encrypting your backup using Transact SQL, see Create an Encrypted Backup. Using SQL Server Management Studio You can encrypt a backup when creating the backup of a database in any of the following dialog boxes Back Up Database Backup Options Page On the Backup Options page, you can select Encryption, and specify the encryption algorithm and the certificate or asymmetric key to use for the encryption. Using Maintenance Plan Wizard When you select a backup task, on the Options tab of the Define Backup Task page, you can select Backup Encryption, and specify the encryption algorithm and the certificate or key to use for the encryption. Using Transact SQL Following is a sample Transact SQL statement to encrypt the backup file BACKUP DATABASE MYTest. DB. TO DISK NC Program FilesMicrosoft SQL ServerMSSQL1. MSSQLSERVERMSSQLBackupMy. Test. DB. bak. COMPRESSION. ENCRYPTION. ALGORITHM AES2. SERVER CERTIFICATE Backup. Encrypt. Cert. For the full Transact SQL statement syntax, see BACKUP Transact SQL. Using Power. Shell This example creates the encryption options and uses it as a parameter value in Backup Sql. Database cmdlet to create an encrypted backup. C PS encryption. Option New Sql. Backup. Encryption. Option Algorithm Aes. Encryptor. Type Server. Certificate Encryptor. Name Backup. Cert. Free Software Download Sites List on this page. C PS Backup Sql. Database Server. Instance. Database My. Test. DB Backup. File My. Test. DB. Compression. Option On Encryption. Option encryption. Option. Recommended Practices Create a backup of the encryption certificate and keys to a location other than your local machine where the instance is installed. To account for disaster recovery scenarios, consider storing a backup of the certificate or key to an off site location. You cannot restore an encrypted backup without the certificate used to encrypt the backup. To restore an encrypted backup, the original certificate used when the backup was taken with the matching thumbprint should be available on the instance you are restoring to. Therefore, the certificate should not be renewed on expiry or changed in any way. Renewal can result in updating the certificate triggering the change of the thumbprint, therefore making the certificate invalid for the backup file. The account performing the restore should have VIEW DEFINITION permissions on the certificate or the asymmetric key used to encrypt during backup. Availability Group database backups are typically performed on the preferred backup replica. If restoring a backup on a replica other than where the backup was taken from, ensure that the original certificate used for backup is available on the replica you are restoring to. If the database is TDE enabled, choose different certificates or asymmetric keys for encrypting the database and the backup to increase security. See Also. Backup Overview SQL Server.