How about adding Linux VMs Servers to Backup Exec 2014? Don't know how can I add Centos 5.x and 6.x to Backup Exec 2014 V-Ray edition. Backup Exec gives error every time I try to add the Linux VM. The server was unable to complete the requested operation Any ideas how to create friendship between backup Exec 2014 and the Linux VMs? Many Thanks Syed Mazhar

BE 2014 doors not support any version of CentOS. See the SCL below. http://www.symantec.com/docs/TECH217478 In fact, CentOS is never supported by any version of BE

After creatign firewall rule on CentOS to accept traffic from BE2014 server, I managed to install the agent on CentOS release 5.11 (Final) , BE 2014 is backing up CentOS with following execption error: Click an exception below to locate it in the job log Backup- centos-vm The remote computer is running a previous version of the Backup Exec Agent for Windows. You must upgrade the agent for Windows to enable secure communication between the agent and Backup Exec servers. Backup- \\centos-vm\[ROOT]Unable to open the item \\centos-vm\[ROOT]/var/lib/mysql/ibdata1 - skipped. Unable to open the item \\centos-vm\[ROOT]/var/lib/mysql/ib_logfile1 - skipped. Unable to open the item \\centos-vm\[ROOT]/var/lib/mysql/ib_logfile0 - skipped. Unable to open the item \\centos-vm\[ROOT]/var/log/nagios/nagios.pid - skipped. Unable to open the item \\centos-vm\[ROOT]/var/run/sendmail.pid - skipped. Unable to open the item \\centos-vm\[ROOT]/var/run/iscsiuio.pid - skipped. Unable to open the item \\centos-vm\[ROOT]/var/run/atd.pid - skipped. Unable to open the item \\centos-vm\[ROOT]/var/run/sm-client.pid - skipped. Unable to open the item \\centos-vm\[ROOT]/var/run/iscsid.pid - skipped. Any solution for this? Many Thanks Syed Mazhar

Yes...it is unsupported as per pkh's comment. If you log a call with Symantec you'd probably get little, or no support. You'd need to install a version of Linux compatible with BE 2014, or perhaps look at Netbackup or another product (assuming NBU also supports CentOS). Thanks!

Unsupported means that BE is not tested with the product, so you are on your own.

Hi, What a stumbling Block, BTW who said Veeam isn't right choice for VMWare Backup? I am running Veeam on a side trial copy and it is perfectly copying all the VMs including CentOS without any hicc ups. Would I still be able to restore the Linux / CentoS VM, regardless of those few files? Thanks for all your help top guns. Syed Mazhar

Try disabling OFO on the Linux client machine. Edit ralus.cfg on the client and set Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\RALUS\DisableOFO=1 Restart the RALUS service and the exceptions may stop from appearing. Would I still be able to restore the Linux / CentoS VM, regardless of those few files? Honestly, the best way to confirm this would be to run an actual restore. Though, per the exception, looks like you are backing up the CentOS VM as a physical machine (using the RALUS agent) and not through the vCenter/ESX host.

Adding Linux VMs

19 Replies

pkh
Moderator
10 years ago
BE 2014 doors not support any version of CentOS. See the SCL below. http://www.symantec.com/docs/TECH217478 In fact, CentOS is never supported by any version of BE
Syed_Mazhar
Level 3
10 years ago
After creatign firewall rule on CentOS to accept traffic from BE2014 server, I managed to install the agent on CentOS release 5.11 (Final) , BE 2014 is backing up CentOS with following execption error:

Click an exception below to locate it in the job log

Backup- centos-vm

The remote computer is running a previous version of the Backup Exec Agent for Windows. You must upgrade the agent for Windows to enable secure communication between the agent and Backup Exec servers.

Backup- \\centos-vm\[ROOT]Unable to open the item \\centos-vm\[ROOT]/var/lib/mysql/ibdata1 - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/lib/mysql/ib_logfile1 - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/lib/mysql/ib_logfile0 - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/log/nagios/nagios.pid - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/run/sendmail.pid - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/run/iscsiuio.pid - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/run/atd.pid - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/run/sm-client.pid - skipped.

Unable to open the item \\centos-vm\[ROOT]/var/run/iscsid.pid - skipped.

Any solution for this?

Many Thanks

Syed Mazhar
CraigV
Moderator
10 years ago
Yes...it is unsupported as per pkh's comment. If you log a call with Symantec you'd probably get little, or no support.

You'd need to install a version of Linux compatible with BE 2014, or perhaps look at Netbackup or another product (assuming NBU also supports CentOS).

Thanks!
pkh
Moderator
10 years ago
Unsupported means that BE is not tested with the product, so you are on your own.
Syed_Mazhar
Level 3
10 years ago
Hi,

What a stumbling Block, BTW who said Veeam isn't right choice for VMWare Backup? I am running Veeam on a side trial copy and it is perfectly copying all the VMs including CentOS without any hicc ups.

Would I still be able to restore the Linux / CentoS VM, regardless of those few files?

Thanks for all your help top guns.

Syed Mazhar
VJware
Level 6
10 years ago
Try disabling OFO on the Linux client machine. Edit ralus.cfg on the client and set Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\RALUS\DisableOFO=1

Restart the RALUS service and the exceptions may stop from appearing.

Would I still be able to restore the Linux / CentoS VM, regardless of those few files?

Honestly, the best way to confirm this would be to run an actual restore. Though, per the exception, looks like you are backing up the CentOS VM as a physical machine (using the RALUS agent) and not through the vCenter/ESX host.
LegAEI
Level 5
10 years ago

From the previous thread:

For plain VM backups, you don't need to install the agent, just create a new NON-GRT backup job for that VM host and do an offline/full backup.

If you want to do a GRT-enabled backup, you will have to install the VM tools for the virtualization platform, then get agent for linux installed on the VM itself.
mgmasterv2
Level 6
10 years ago
Backup youre linux VM's using aget for vmware & Hyper-v -create Backup Job From Esxi or Vcenter .

in my case its always work for centos.
Artegic
Level 6
10 years ago
CentOS is functionally identical to RHEL of the same release number. It is true (although incomprehensible) that Symantec refuses to support it, but that should not be a reason for us as a community to follow their bad example.
CraigV
Moderator
10 years ago
...since when is this a bad example? A lot of other vendors also don't support various applications and vendors.

However, pointing this out to the OP covers them too...telling them to simply follow through isn't sound advice. They're currently having issues with this now, and Symantec wouldn't be obliged to help them with a solution.

Putting it in as an Idea would be the only recourse...

Thanks!