Backup Exec Installation Guide
Abigael Ortyl
I have a media server, Windows Server 2008 SP2 running Backup Exec 2010 R2. The SQL and other Windows agents work but I cannot backup the Exchange 2010 server running Windows Server2008 R2. I have the correct license for the Exchange agent - installed on the media server, and I installed Exchange Management tools on the media server.
The 'Microsoft Exchange Database Availability Group' option is greyed out and if I select the server under a new backup job I can expand the 'Microsoft Information Store' option and see the mail database name but showing 0Kb.
When I try to back it up it gives an error displaying: The job failed with the following error: Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again.
Ben you were the closest, I got it working thanks to help from Gautam Khadse at Symantec. The user used by Backup Exec to do the backup job - in my case a user called backupexec - had to be placed explicitly as a local admin on the Exchange box, regardless of the fact that it had Domain Admin rights (which in my case automatically made this user a local administrator on the Exchange box).
All the other pre-requisites were also followed and the user also had the Exchange Organization Management role. The user's credentials also tested successfully in the new backup job dialogue box. This fix was not in the documentation, but worked for me.
My config is the same, remote agent on the exchange server and I am licensed for exchange. So when I create a new backup job I can drill down to the exchange server, drill down from there and select the "information store". Using brick level backup.
So I guess I am not really answering your question, but possibly asking another. Is there something else I need to be backing up? I have been getting good backups of the information store, and have done restores?
2. Verify Exchange Agent Installation:Check Exchange Agent is installed correctly on Backup Exec media server or if using remote agents, ensure that it is installed correctly on the Exchange server.
3. Ensure Correct Exchange Management Tools Installation:Check correct version of Exchange Management Tools is installed on the media server, also should match with Exchange server's version.
4. Update Selection List:Check if Correct mailbox databases are selected for backup. If the mailbox database is showing as 0KB,then Backup Exec is not able to properly recognize the Exchange database.
5. Check Database Availability Group (DAG) Configuration:If you're using a DAG configuration, ensure that DAG is correctly set up. All DAG members should properly visible to Backup Exec.
9. Review Event Logs:For getting more insights, Check the event logs on both the media server and the Exchange server for any relevant error messages or warnings. then you will get the clear idea about the issue.
You can back up your data to virtual tapes, archive the tapes, and manage your virtual tape library (VTL) devices by using Veritas Backup Exec. In this topic, you can find basic documentation needed to perform backup and restore operations using the following versions of Backup Exec:
The procedure for using these versions of Backup Exec with a Tape Gateway is the same. See the Veritas support website for detailed information about how to use Backup Exec, including how to create secure backups with Backup Exec, software and hardware compatibility lists, and administrator guides for Backup Exec.
After you have connected the virtual tape library (VTL) devices to the Windows client, you configure Backup Exec storage to recognize your devices. For information about how to connect VTL devices to the Windows client, see Connecting Your VTL Devices.
Tape Gateway provides 10 tape drives. However, your Backup Exec license agreement might require your backup application to work with fewer than 10 tape drives. In that case, you must deactivate tape drives in the Backup Exec robotic library to leave only the number of tape drives allowed by your license agreement actuvated. For instructions, see Deactivating a Tape Drive in Backup Exec .
Veritas Backup Exec software requires the Tape Gateway medium changer type. If the medium changer type listed under Robotic library is not Tape Gateway, you must change it before you configure storage in the backup application. For information about how to select a different medium changer type, see Selecting a Medium Changer After Gateway Activation.
When you import tapes into the robotic library, the tapes are stored in slots instead of tape drives. Therefore, the tape drives might have a message that indicates there is no media in the drives (No media). When you initiate a backup or restore job, the tapes are moved into the tape drives.
You write data to a Tape Gateway virtual tape by using the same procedure and backup policies you do with physical tapes. For detailed information, see the Backup Exec Administrative Guide in the documentation section in the Backup Exec software.
If your Tape Gateway restarts for any reason during an ongoing backup job, the backup job might fail. If the backup job fails, the tape status in Veritas Backup Exec changes to Not Appendable. You can archive the tape or continue to read data from it. To complete the failed backup job, you must resubmit it on a new tape.
In the Storage Gateway console, you can verify the status of the tape you are archiving. It might take some time to finish uploading data to AWS. During this time, the exported tape is listed in the Tape Gateway VTL with the status IN TRANSIT TO VTS. When the upload is completed and the archiving process begins, the status changes to ARCHIVING. When data archiving has completed, the exported tape is no longer listed in the VTL but is archived in S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive.
Use Backup Exec to restore the data. This process is the same as restoring data from physical tapes. For instructions, see the Backup Exec Administrative Guide in the documentation section in the Backup Exec software.
Recently I installed the latest version of Backup Exec R3 onto a clients site, after running many updates it required a reboot, however the client had had quite a bit of downtime so I needed to get Backup Exec working without having to reboot the server. Follow the steps below to start backup exec with out reboot.
When backup exec makes changes that require a reboot it puts a key in the registry that stops you launching backup exec. The trick is to locate this registry key and delete it. So first we need to run Regedit.
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 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 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]
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.
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 OSs, 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.
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]
c80f0f1006