Video Screencast Help
Search Video Help Close Back
to help

Installing Symantec Endpoint Protection Manager/Client with Symantec Backup Exec

Created: 01 Sep 2010 | Updated: 26 Sep 2010 | 8 comments
Hafiz.mohammad's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hello,

I have a problem regarding this issue ;

1. Is there a problem when installing Symantec Endpoint Protection Manager with Symantec Backup Exec both co-allocated on the same physical server ?
2. Do I have to adjust the configuration for both of the clients of Symantec Endpoint Protection client and Backup Exec co-allocated together on the same physical client machine ?

Regards and Thanks..

Comments 8 CommentsJump to latest comment

VKalani's picture

Hi,

1. Is there a problem when installing Symantec Endpoint Protection Manager with Symantec Backup Exec both co-allocated on the same physical server ?

Answer:

There are no issues to have both of these on same  server. Both run perfectly fine with each other.

2. Do I have to adjust the configuration for both of the clients of Symantec Endpoint Protection client and Backup Exec co-allocated together on the same physical client machine ?

Answer:

See this:
Best settings for Symantec Endpoint Protection (SEP) client with Backup Exec for Windows Server version 12.x
http://clientui-kb.symantec.com/kb/index?page=content&id=TECH105418&actp=search&viewlocale=en_US&searchid=1283399436308

-VKalani

+1
Login to vote
  • Actions
P_K_'s picture

Backup Exec uses the following ports for communication 8443, 2638, and 8080.  For more information, read the following document:

"What TCP/UDP ports does Backup Exec 11d for Windows Servers (including CPS and DLO) and Backup Exec System Recovery use?" at:
http://seer.entsupport.symantec.com/docs/285830.htm

To install the Symantec Endpoint Protection Manager on to a server with Backup Exec,  install Symantec Endpoint Protection Manager to a custom site and port.   For more information, read the following document:

"Configuring the Symantec Endpoint Protection Manager to run with a custom HTTP port." at:
http://service1.symantec.com/SUPPORT/ent-security....

Symantec Endpoint Protection: Why and how is the port changed on an embedded database?
http://service1.symantec.com/SUPPORT/ent-security....

Prachand MCSE-2012 Symantec Technical Specialist (SCTS)

+2
Login to vote
  • Actions
VKalani's picture

Actually, with the latest version of Symantec endpoint  protection manger, it would automatically change the port 2638 to something else, if there is backup exec installed on the same server.

Also, by default, it will get installed on a custom HTTP port( 8014).

If, after installing  you are not able to log into the  Symantec Endpoint  protection manager, then you would have to change the  port 8443 to something else, like, 8444, or 8440.

To do this:

Go to C:/program files/Symantec/Symantec Endpoint  protection manager/Tomcat/Conf, and  open the file, server.XML with a notepad. Then Find " 8443", and replace it with 8440.
Save the  file, and  close  it.

Then, go to start-Programs-Symantec Endpoint  protection manager-Mgt.Server  configuration wizard.

While running this, change port 8443 to 8440, and  complete  the  wizard. Then you  should be able to log  into SEPM console, without  any  issues.

-VKalani

SOLUTION
+1
Login to vote
  • Actions
Hafiz.mohammad's picture

Ok,

Thanks for your replies.

However is this applicable for Backup Exec System Recovery too ?

Thanks.

0
Login to vote
  • Actions
Funaro's picture

The total Backup is 440GB which takes approximately 18hrs to backup.

I think it should take a lot less time. I imagine, in SEP, I should create exclusions for processes and directories which BackupExec uses.

Can you tell me on which executables should I exclude on the media server (which has BackupExec and SEP installed)?

In addition, on the servers which have the agents running, what exclusions should be added?

 

Thank you.

0
Login to vote
  • Actions
Hafiz.mohammad's picture

I`m sorry but I have not tried installing them together yet.

0
Login to vote
  • Actions