Brightstor Backup Agent for Linux on ESX 3.0

[petzold]

Hello

I upgradet my ESX Server to 3.0. Nolw i have the Problem that i can't use the Brightstor 11.1 Backup anymore. When the i try to connect to the server and browse the the tree i can't log in. Login is denied even for root.

Any Ideas what i could do.

Thank your and regards

Paul

[vreihen]

Sounds like you need to open the ESX firewall port for ArghServe's daemon...

[petzold]

Hi Jive

Thank your for your reply. Yes i think it could ber that. But wher can i set the firewall arcserve daemon. Under VI Configuratiuon Security Profile Firewall Settings there is no Arcserve or Brightstor Daemon. Only Symantec. For Test i opend all of the available ports. How an wher can i add ports.

Regards Paul

[Quotient · Accepted solution]

Use the esxcfg-firewall command which is well documented in Chapter 12 of the Sever Config Guide.

I strongly recommend reading Chapter 10 & Chapter 12.

http://www.vmware.com/pdf/vi3_server_config.pdf

I believe CA BrightStor uses tcp / udp port 6050 by default. But there may be more...

Presuming it is port 6050 and only port 6050, issue the following in an ssh session:

esxcfg-firewall --openPort 6050,tcp,out,BrightStorAgent

esxcfg-firewall --openPort 6050,udp,out,BrightStorAgent[/b]

If that didn't work try these too, testing between each one:

esxcfg-firewall --openPort 6050,tcp,in,BrightStorAgent

esxcfg-firewall --openPort 6050,udp,in,BrightStorAgent[/b]

You could also try adding the service to the end of the /etc/vmware/firewall/services.xml file...

I'm not certain what this will achieve:

Perhaps it will configure the firewall appropriately...

Perhaps it will even show up in the VI Client dialog...?!?!?!

It will probably take a service firewall restart[/b]and a service mgmt-vmware restart[/b]to test this mod - which may not be supported... who knows?

EDIT: Looks like you can: http://www.vmware.com/community/thread.jspa?threadID=48002&tstart=0

Hope this helps.

Ben

[Noyzyboy]

Hi,

I've been struggling with this today and it would appear all that is necessary to get this working is to run the following:

esxcfg-firewall --openPort 6051,tcp,out,BrightStorAgent

esxcfg-firewall --openPort 6051,udp,out,BrightStorAgent

esxcfg-firewall --openPort 6051,tcp,in,BrightStorAgent

esxcfg-firewall --openPort 6051,udp,in,BrightStorAgent

No firewall restart is necessary. It certainly worked for me. Thanks for the initial nudge in the right direction.

Cheers,

Rich

[bellopao]

If you want control firewall using Virtual Center Client you can modify the file services.xml

nano -w /etc/vmware/firewall/services.xml[/b]

and add this lines (MODIFY ID 0026 BASED ON YOUR LAST ID)

and then type this command: service mgmt-vmware restart[/b]

restart your Virtual Center Client then select your ESX host, Configuration, Security Profile, Properties...

and chech the new firewall rule

And in order to make the /vmfs directory visible u need to modify the file /etc/mtab

and add this line

/vmfs /vmfs vmfs rw 0 0[/i]

and restart agent

caagent stop

caagent start[/b]

[om8000]

I had the same problem.

I was able to select directories for backup, but job returned an error when started. So I read the 100 last lines inside file:

/opt/CA/BABcmagent/logs/caagentd.log

where software incompatibility was reported.

I overlook for the server and client versions and I had 11.1 server but 11.5 client. Client downgrade to 11.1 was very very helpfull ;).

Considering ArcServe and EXS support - it is only 11.5 that supports vmfs partitions without troubles. But you will also need to upgrade ArcServe server to the same version .

[mixolydian]

Hello,

I would like to know if you successfully installed the 11.5 Linux agent from BrightStor. I am trying to use that now and cannot install it in the console. I execute "./install" and get permission denied.

I was very happy with the 11.1 agent on 2.x but now need the VMFS3 compatibility

I am logged in a root.

Regards,

Brian

Message was edited by: Brian - The file permissions were not set for correct execution levels because installation package was zipped from CD using a WINDOZE machine and the attribs were missing - created a tarball from a linux machine and everything seems to be fine.

mixolydian

[RPingarron]

Hi,

I successfully installed and got VMCB with BAB11.5 in ESX3.

What you need is BAB11.5 SP3 (either as BackupServer under Windows2003SP2 and either in the linux agent).

When you install the BAB11.5-SP3 linux agent, the "install" script does not run as you said. All you need is to do a manual install :

1 - Install CA-LIC with "rpm -ivh ca-lic-xxxx.i386.rpm --force"

2 - Install CMagt with "rpm -ivh babcmagt.rpm --force"

3 - Install the linux agent with "rpm -ivh babagtux.rpm --force"

4 - Run the Universal Agent Configuration Utility to register the agent, so just issue a "/opt/CA/BABuagent/uagentsetup

Regards,

Raul

[TimBee]

Hi Raul,

Many thanks for your manual install instructions! They worked like a charm!

One problem though: When you restart the ESX host the CA Agent will not be strated during bootup, which meanse that you have to manually start the service from the console after complete bootup. I do that now by issuing the last command in your quick-guide: Step 4 -> uagentsetup. The will the generate this output in the terminal:

-

---

UAGENT is registered already!

Do you want to register it again? (default n) : y

BrightStor ARCserve Backup Client Agent is enabled and running

-

---

After this I can connect to the Agent.

Is there a way to automatically start up the BrightStor ARCserve Backup Client Agent duriong ESX bootup time?

Thanks and Best Regards,

Tim.

[TimBee]

I've found a solution to my problem, and I would like to share it with you :

You have to copy BrightStor startup script (bab_agent) to the script folder:

/etc/init.d (make sure you chmod "bab_agent" to 755)

The you need to configure the runlevels by entering these commands:

ln -s /etc/init.d/bab_agent /etc/rc.d/rc0.d/K00bab_agent

ln -s /etc/init.d/bab_agent /etc/rc.d/rc1.d/K00bab_agent

ln -s /etc/init.d/bab_agent /etc/rc.d/rc4.d/K00bab_agent

ln -s /etc/init.d/bab_agent /etc/rc.d/rc6.d/K00bab_agent

ln -s /etc/init.d/bab_agent /etc/rc.d/rc2.d/S99bab_agent

ln -s /etc/init.d/bab_agent /etc/rc.d/rc3.d/S99bab_agent

ln -s /etc/init.d/bab_agent /etc/rc.d/rc5.d/S99bab_agent

...and now it should work.

Best Regards,

Tim.