Endpoint Protection

 View Only
  • 1.  SQL Server Replication best practice

    Posted Apr 06, 2010 02:06 PM

    I have been tasked to set up out new Infrastructure  for Sep 11.0.5002.333  MR5. I read the install guide and admin guide and so far so good.
    He are some basics about the way I set everything up. Server one has the management console while server 2 has our SQL database. I am going to set up another management console on server 3 and place another sql database on server 4 for the server 3 management console. I want to set up replication between the two SQL databases. The question I have is can both databases being on different servers have the same name our database team who configured the first one needs to know this info. I don't see this info in either guide can someone please help?
    This setup will cover over 10,000 users in several countries so I did not think using 2 SQL databases was overkill. Coming from SAV 10x I did not want to run into the same performance issues I saw with that system. I also have 6 gups working great in 4 different states.



  • 2.  RE: SQL Server Replication best practice
    Best Answer

    Posted Apr 06, 2010 02:38 PM
    Yes you can have 2 database on diffrent server and SEPM's on different servers and still replicate..
    Just make sure to mention the right Database server name ( 2nd Server with SQL ) and Management server name ( 2nd server with SEPM ) and Remote Database server (1st SQL) and Management server( 1st sepm) while installing the 2nd SEPM as replication partner. 


  • 3.  RE: SQL Server Replication best practice

    Posted Apr 06, 2010 09:07 PM

    You really don't need 2 databases for only 10,000 users!
    What is the requirement of having 2?

    If it is just for redundancy then you are better off having the SQL clustered.
    If it is for disaster recovery you can just keep a backup and recover very quickly from complete failure to a new SQL server.

    It is not critical to keep the DB available as the clients will continue functioning without the SEPM and DB.
    They just wont get definitions from the SEPM and you wont be able to do reporting or policy changes.
    So you have this sliding window of risk where the clients becoming more and more out of date.

    If you know what you are doing and have practised your DR process you can can recover the SEPM in 30-60 minutes with a DB backup.
    Even if you don't have a DB and need to generate and drop new sylink,xml files you could fully recover your fleet of 10,000 in a day.

    Adding additional databases should be avoided unless there is a very specific requirement.

    Check the following:

    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/c68d849449ab97328825733e0069a691?OpenDocument




  • 4.  RE: SQL Server Replication best practice



  • 5.  RE: SQL Server Replication best practice

    Posted Apr 07, 2010 10:05 AM
    Hey guys thanks for all the great information, I do have a good reason for 2 databases I work for one company but sometimes they act like 2 separate companies and we cover many countries and many states in the U.S. Thanks again for all the help.