Endpoint Protection

Sorry, again and again posting basics questions..

We have 1 primary server and 1 secondary server.  We have few queries.

If we made changes (creating a new group in primary server) how much time to take to reflect in secondary server?

We are using single database for both primary and secondary server, in this case and bandwidth issue occur due to using the single database?

We have enabled the truncate the database transactions logs and Rebuild index, in this scenario is there any data transfer between primary and secondary server?

If no change made in both the servers, what is frequent replication time between primary and secondary server?

...with both SEPMs sharing the same database, changes made from one SEPM will be reflected very quickly on the second.

The only time delay involved would be in the time it takes for SEPM1 to write the chanages to the database, and then for SEPM2 to read them back.  As per Symantec recommendations, the SEPMs should always be on the same local network as the SQL Server hosting the database, so normally there are no bandwidth problems.  As both SEPMs are using the same database, there is nothing to replicate between the SEPMs, in fact I think any communication between the two SEPMs if done via the database.

If we made changes (creating a new group in primary server) how much time to take to reflect in secondary server?

It depends on the replication interval setting you configured in SEPM. If Auto Replication is selected then replication may occur as frequently as every five minutes.

We are using single database for both primary and secondary server, in this case and bandwidth issue occur due to using the single database?

Bandwdith issue doesn't occur because of using the single database but again it is based on the replication setting.

For Secondary server where we need to set the replication interval setting in SEPM.. Please let me know the steps for both server and Database...

We have enabled the truncate the database transactions logs and Rebuild index, in this scenario is there any data transfer between primary and secondary server?

Truncate the database transaction logs and Rebuild Indexes are Database Maintenance Tasks so it will not cause any data transfer.

If no change made in both the servers, what is frequent replication time between primary and secondary server?
As said above if Auto replication is enabled its 5 mins.

Please check the below link to set the replication interval,

http://www.symantec.com/docs/HOWTO55469

Replication within SEP is only meant to happen between SEP Sites.  In a single database implementation, there can be only one SEP Site, meaning direct replication between the SEPMs should not occur.

You might need to check this

How changes are merged during replication
After replication occurs, the database on site 1 and the database on site 2 are the
same. Only computer identification information for the servers differs.
If administrators change settings on all sites on a site farm, conflicts can occur.
For example, administrators on site 1 and site 2 can both add a group with the
same name. If you want to resolve this conflict, both groups then exist after
replication. However, one of them is renamed with a tilde and the numeral 1 (~1).
If both sites added a group that is called Sales, after replication you can see two
groups at both sites. One group is called Sales and the other is called Sales 1. This
duplication occurs whenever a policy with the same name is added to the same
place at two sites.
If duplicate network adapters are created at different sites with the same name,
a tilde and the numeral 1 (~1) is added. The two symbols are added to one of the
names.
If different settings are changed at both sites, the changes are merged after
replication. For example, if you change Client Security Settings on site 1 and
Password Protection on site 2, both sets of changes appear after replication.
Whenever possible, changes are merged between the two sites.
If policies are added at both sites, new policies appear on both sites after
replication. Conflicts can occur when one policy is changed at two different sites.
If a policy is changed at multiple sites, the last update of any change is then
maintained after replication.
If you perform the following tasks with the replication that is scheduled to occur
every hour on the hour:
■ You edit the AvAsPolicy1 on site 1 at 2:00 P.M.
■ You edit the same policy on site 2 at 2:30 P.M.
Then only the changes that have been completed on site 2 appear after replication
is complete when replication occurs at 3:00 P.M.
Replicating data 373
About the impact of replication
If one of the replication partners is taken offline, the remote site may still indicate
the status as online.

Yes that is true.

THanks SMLatCST..

@Ariv.. you are talking about replication.. Just what to know the is it possible to set the time frequency between primary and secondary server.

If we enable the replication partners in that scenaron we can set the time frequency for replication.

And one more question.. Virus defs will copy from primary server to secondary server or live update action happens on both the serevrs?

Why is replication being discussed? The customer is using loadbalancing (2 SEPM's sharing one DB) not replication (2 SEPM's 2 DB's replicating data between the two).

The changes should happen almost instantly, as SMLatCST already touched on you want your SEPM's performing as few hops as possible when connecting to the DB as best practice.

Just what to know the is it possible to set the time frequency between primary and secondary server.

No.

If we enable the replication partners in that scenaron we can set the time frequency for replication

Yes.

Virus defs will copy from primary server to secondary server or live update action happens on both the serevrs?

Liveupdate should be configured on both the SEPM servers and they download individually.

Hi San

please, clarify:

do you have a single SQL Server DB where two SEPM consoles are connected, or two SEPMs in replication (one DB per each of them)?

As we mnetoned above we have 2 SEPM servers (Prinmary and secondary) both are using single database which installe din Primary server.

we are not enabled replication between these 2 SPEM serevrs.