Veritas Backup Exec Agent Download

[Jule Kue]

Iwas just wondering if anybody had any similar experience with the latest version of Backup Exec (version 21 and up), running on Server 2008R2, with a Windows Server 2003 Enterprise server being backed up.

Thanks! The 2003 Enterprise server is an old FTP box and there is a plan to migrate this to a Server 2019 machine but it will be a while before this happens, until then we still have daily backups tp worry about.

I think it is a worth-while exercise to upgrade BE to current version and see if you can make the agents work properly on the old servers. The best scenario would be a new installation of BE v21 on a different server, preferably 2012 or newer, and verify functionality. This way you are able to quickly fail back to your current BE v20 media server. The biggest change would be removing the old agent from your 2003 server and installing the new one for testing.

I have installed the trial on a different server in the same backup network, but am having difficulty pushing out the Windows agent to any machines. I am getting the error "Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled and is not blocked by a firewall. 2147944122"

I have tried copying the RAWSx64 and VCredist and MSXML to the C: drive and running setup however I get an error saying it cannot run because it failed the checksum requirements. ( I copied those files from the ISO image file).

Firstly, I went to my media server (The one with the backup exec installed on it), I then went to the install agents tab. Here is where you can list the servers that you want to "push" install. I clicked on add > and then I found our server. Once the server was added it asks you to provide credentials and the domain.

After this, the push install will attempt to validate your server (this could take a couple of minutes). After it verifies it will prompt you to continue with the install. Follow the remaining steps and it should work. IF it doens't, ensure that you have set permission for the media server to connect and overwrite files on the affected server.

I did not have the affected server open in a different RDC window. I only had the media server opened. (I have no idea if this really helped it, but after dealing with this issue for 3 weeks now I like to think it did).

This should hopefully work for you. If it does not, try local installing on the server or machine but be sure that you grab the RAWS folder from the C:/programfiles/symantec/backupexec/agents/ folder as well as the VCredist folder from the BackupExec account. Then log in to the affected serve using the backupexec account (be sure it has administrative permissions).

We have backup exec Version 20.4 Rev. 1188 installed on a Windows Server 2012 R2 server. Our primary file server is a QNAP TVS-EC2470U-SAS-RP.

Currently, we use NFS shares for the company to be able to access the files. We would like to be able to backup the data on the QNAP with backup exec, but I can't seem to find a way to do so. When I tried to run the backup, I got the following error:

After several months of dealing with a feature that should work and talking to tech support and listening to them attempt trail and error on a variation of this procedure and then realizing that maintaining my backup server is a manual process that requires finding solutions that Symantec can't figure out, Try this:

Basically, you would expect when you upgrade your BE12.x installation, the install process would check this folder and make sure the proper updates are in this folder and remove any updates (.msp files) that arent needed.

If you check the version of the remote agent on the remote server by going into the Backup tab on the media server, selecting a server and then selecting properties. If the version says anything other than x.x.x.158 then stop and restart the agent on the remote server, hit F5 in your Backup source selections and check the version properties again.

(ie, I see version 12.5.2213.158 after all is said and done)

A colleague swears that several years ago, before I came onboard with the company, that they use to be able to do agentless backups with Backup Exec. I have worked with the product for several years and have never heard of such a thing. Why purchase agents if you can run backups without an agent?! Has anyone heard of this functionality in Backup Exec 2010 and if so, how would I go about configuring such a backup?

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 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.

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 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.

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.

3a8082e126