Backup Exec Agents And Options
The bottom line is that IT administration is not as simple as it was a few years ago. In fact, keeping your business data for critical applications protected is pretty tricky. Backing up, that’s not the tricky bit, is it? Backing stuff up, on the face of it, is really easy. You can back up most data pretty easily with most backup technology, but it is the restoring it that is troubling.
The whole point of agents and options is to improve, extend and enhance the backing up and restoration of critical data. As I’ve said in a previous blog, backing up Active Directory is pretty easy – restoring it can be a nightmare if you are not using Backup Exec AD Agent. So BE has a number of pretty critical agents and options to help organisations to expand the effectiveness of their backup strategy and specifically deal with the idiosyncrasies of specific application backup nightmares.
The BE 12.5 Media Server and Agent of Windows Systems licenses include: Advanced Open File Option (AOFO) and Intelligent Disaster Recovery Option (IDRO). Advanced Open File Option (AOFO) and Intelligent Disaster Recovery Option (IDRO). These are included with each core license and with each Agent for Windows Systems.
Be 12.5 has a number of new and enhanced agents Backup Exec 12.5 for Windows Servers which include the new agent for VMware Virtual Infrastructures and Microsoft Virtual Servers, both of which deliver one agent delivering optimised data protection to an unlimited number of either VMware or Microsoft virtual systems through a single management console; granular file folder recovery from a single backup; comprehensive backup for virtual systems and legacy physical systems supporting both disk and tape storage environments.
The new Backup Exec 12.5 Remote Media Agent for Linux Server gives organisations the ability to directly attach a storage device to a remote Linux servers for added flexibility and reduced bandwidth requirements for backup jobs on remote Linux servers. Each Remote Media Agent for Linux Servers includes a Remote Agent for Linux Servers and all backup and recovery job configurations are centrally managed through the primary Windows media server console.
The Backup Exec NDMP Option supports the backup and restore of Network Data Management Protocol (NDMP) greatly expanding the number of disk targets that can be selected for disk-based data protection. The option enables NAS device storage configurations with tape devices attached and protects NDMP devices residing in remote locations including in a Storage Area Network (SAN) configurations.
In early April BE management was enhanced with BEIM(Backup Exec Infrastructure Management Option), adding functionality that enhances CASO (BE Central Admin Server Option). Built on the Altiris technology, the infrastructure manager enables inventory for an entire Backup Exec environment including current and older versions of Backup Exec; discover, locate, and manage existing/new server resources in a Backup Exec environment as well as locate unprotected servers; define and deploy the correct patch levels to BE and BESR servers, applications and databases across an environment or upgrade, deploy, configure and manage from BE version 9.1 to 12.5.
So, it’s probably worth taking another look at the agents and options that could enhance your backup.
(For a complete list of agents and options, please see the Backup Exec 12.5 License and Support Services guide, available at www.symantec.com .)
The Backup & Archiving Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Backup & Archiving community. Any authenticated Connect member can contribute to this blog.
Comments
Backup Exec 12.5 Remote Media Agent for Linux Server
Backup Exec 12.5 Remote agent for linux server works mainly on which linux distros and is it packaged or as .RPM and .deb can it be downloaded via yum and apt or is it a one script fits all.
Backup Exec 12.5 Remote Media Agent for Linux Server
repeted post IE / Internet connection missbehavior
Backup Exec 12.5 Remote Media Agent for Linux Server
repeted post IE / Internet connection missbehavior
Backup Exec Remote Media Agent for Linux Servers (RMALS)
According to the Backup Exec 12.5 Software Compatibility List (ftp://exftpp.symantec.com/pub/support/products/Backup_Exec_for_WindowsNT/307063.pdf), the Backup Exec Remote Media Agent for Linux Servers (RMALS) supports the following versions of Linux (on 32-bit x86 and 64-bit x64 platforms only):
Also note that the only filesystems that are supported on SUSE Linux Enterprise Server are Ext2, Ext3, ReiserFS, JFS, and VxFS.
Also note that RMALS is not designed to be a full disaster recovery agent. You will still need some other method to restore the operating system to the Linux server in the event of a full system crash.
You cannot install RMALS via an online installation process such as "apt" or "yum", nor can you install it via the Red Hat "rpm" command. To install RMALS, you put the Backup Exec installation CD into the CD-ROM drive of the Linux server, log in as root, and execute the "installrmal" script from the root directory of the CD-ROM.
One More Question
Great job :) Your post really helped a lot.
I am trying to verify that the backupexec (/opt/VRTSralus/bin/beremote) is set to start up in the appropriate run levels. However I can't seem to get chkconfig to add it correctly. I get this error.
chkconfig --add /opt/VRTSralus/bin/beremote
error reading information on service /opt/VRTSralus/bin/beremote: No such file or directory
I have also tried using the /etc/ini.d/VRTSralus.init script with the chkconfig command and get this error
chkconfig --add VRTSralus.init
service VRTSralus.init does not support chkconfig
Regards,
Winn Johnston
From "man
From "man chkconfig":
RUNLEVEL FILES
Each service which should be manageable by chkconfig needs two or more
commented lines added to its init.d script. The first line tells chk-
config what runlevels the service should be started in by default, as
well as the start and stop priority levels. If the service should not,
by default, be started in any runlevels, a - should be used in place
of the runlevels list. The second line contains a description for the
service, and may be extended across multiple lines with backslash con-
tinuation.
For example, random.init has these three lines:
# chkconfig: 2345 20 80
# description: Saves and restores system entropy pool for \
# higher quality random number generation.
This says that the random script should be started in levels 2, 3, 4,
and 5, that its start priority should be 20, and that its stop prior-
ity should be 80. You should be able to figure out what the descrip-
tion says; the \ causes the line to be continued. The extra space in
front of the line is ignored.
So, what you need to do is edit /etc/init.d/VRTSralus.init and add those two lines:
[root@myhost ~]# vi /etc/init.d/VRTSralus.init
<snip>
#!/bin/sh
# chkconfig: 2345 20 80
# description: Symantec Backup Exec Remote Agent for Linux and UNIX Servers
if [ ! -d /opt/VRTSralus ]
then
<snip>
... then run:
[root@myhost ~]# chkconfig --add VRTSralus.init
[root@myhost ~]# chkconfig --list | grep VRTS
VRTSralus.init 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@myhost ~]# service VRTSralus.init start
You'll also need to ensure you have libstdc++.so.5 installed:
[root@myhost ~]# ls -l /usr/lib/libstdc++.so.5
ls: /usr/lib/libstdc++.so.5: No such file or directory
If you're using yum, use this command to install it:
[root@myhost ~]# yum install compat-libstdc++-33
...
[root@myhost ~]# ls -l /usr/lib/libstdc++.so.5
lrwxrwxrwx 1 root root 18 Sep 16 02:02 /usr/lib/libstdc++.so.5 -> libstdc++.so.5.0.7
re-installation
I am rebuilding a new server to replace an existing one and want to re-install BE12.5. Where can I find a download of the programme as I do not have the media any more.
Would you like to reply?
Login or Register to post your comment.