- #SYMANTEC BACKUP EXEC 2010 R3 LINUX AGENT INSTALL#
- #SYMANTEC BACKUP EXEC 2010 R3 LINUX AGENT PATCH#
- #SYMANTEC BACKUP EXEC 2010 R3 LINUX AGENT CODE#
This removes the need for transporting the data through the backup server itself, thus enhancing speed and removing load from the backup server. NDMP, or Network Data Management Protocol, is a protocol invented by NetApp and EMC, meant to transport data between NAS devices and backup devices. Incase you are unfamiliar with NDMP here is the quick low down.
#SYMANTEC BACKUP EXEC 2010 R3 LINUX AGENT INSTALL#
For my latest test I used 2010 R3… Now since the VNXe does not utilize an operating system where third party vendors can install agents into, we are going to be utilizing the NDMP protocol. Here they are: CA BrightStor ARCserve, Commvault Galaxy, EMC Avamar, EMC Networker, Symantec NetBackup, and Symantec Backup Exec which we are about to explore.Īs of this writing the VNXe Operating Environment v2.0 is fully supported by Backup Exec 2010 R2 or newer. To start off I just want to say that there are a number of Backup Applications that can do what I am about to describe, and just to be fair I will list a couple of the popular ones and If I have enough time in the future I will break down the process with each one. Typically I would use a couple different combinations of these three technologies depending on the business need and data risk, but today I am only going to go into detail with backing up the VNXe using Backup Exec as it is the most popular choice for small and medium businesses which is fitting for the VNXe. There are a number of ways to protect the VNXe including snapshots, replication and NDMP backups. From that line they also produced a more affordable “VNXe” model for small business and remote offices. I try to suppress it but it's hard, and I am not a native English speaker.EMC recently launched their new VNX storage line which is a unified storage platform with one management framework supporting file, block, and object optimized for virtual applications. PS: Please forgive any sarcasm that may have leaked into the lines above. (CentOS isn't supported by Symantec anyway even when running the distribution kernel because it isn't called Red Hat Enterprise, so it doesn't make any difference in that respect.) (Of course it'll kill your Symantec support, too.) Although I cannot say I like that solution, we are currently using it out of necessity on a CentOS 6 system running a self-compiled 3.1 kernel, and it doesn't seem to have caused any trouble so far. Patching /opt/VRTSralus/bin/libbesocket.so as described in does work (if done intelligently ) and allows you to back up Linux systems running on a 3.x kernel. (It'll just kill your support from Symantec.)
#SYMANTEC BACKUP EXEC 2010 R3 LINUX AGENT PATCH#
Even for these two, Symantec does not support the latest patch levels, but as Red Hat stays with the same kernel release during the live of a major version, updating will not actually break Backup Exec on these systems. Its Linux support is limited to a few specific distributions still based on kernel release 2.6, of which the only still supported ones are Red Hat Enterprise Linux 5 and 6. To my knowledge Backup Exec is the only Symantec solution coming close.
#SYMANTEC BACKUP EXEC 2010 R3 LINUX AGENT CODE#
It just reinstates RALUS' papering over the issue by changing the error code returned by ioctl from the documented value for this case back to what RALUS expects.