Allow the Management Server Configuration Wizard to update the SEPM database.
Follow the rest of the prompts in the Management Server Configuration Wizard, providing the correct Microsoft SQL Server configuration and authentication information. Ensure the name in the Server name field matches what was entered for the existing server exactly, including all capitalization and punctuation marks. Browse to the recovery file you exported from the existing manager in step 1, and click Next. Check use a recovery file to restore communication with previously deployed clients. On the Welcome screen, select Install an additional management server to an existing Site. Perform the following steps in the Management Server Configuration Wizard:. Install SEPM to the new server, making sure to match the version of SEPM to the existing server. Note: You can configure the new SEPM with the same IP address as the existing SEPM. Ensure that the new SEPM has the same host name as the existing SEPM. Ensure that it is no longer able to connect to the Microsoft SQL server hosting the SEPM database. See Contents of the Endpoint Protection Manager disaster recovery file. Gather the recovery file from the existing SEPM. See Disaster recovery best practices for Endpoint Protection For Microsoft SQL server databases Make sure that you gather the database backup and recovery file(s) from your existing manager, and restore the database and recovery files to the new SEPM. For embedded databasesįollow the disaster recovery steps best practices for your SEPM version. The method used to replace the SEPM will vary depending on whether the SEPM is a member of a site using a Microsoft SQL Server database, or an embedded database site. 
PS : T oday (25 Dec 13), I’ve noticed that there was a related Symantec Technote here. I wish this saves a few hours of you SEP experts/admins. Now feel free to run a LiveUpdate session on SEPM console. * Set the “Restricted File Growth” value to let me say 40.000 MB (till next year 😉 ) * Select Files page and click on “… button” stated after the value located in “sem5_content” row and “Autogrowth” column * Right click sem5 database select Properties Until Symantec come up with, I have a manual solution. Symantec have to find a solution to this issue urgently. Consequently the older design of SEP database doesn’t meet today’s requirements. And these definitions’ sizes getting larger day by day. size limit of a database file of sem5 (SEP’s db) database.Īs you may know, definition revisions mainly stored in SEP Database. If you have encountered SEP virus-definition update problem on SEPM recently (late 2013) and if this is a large enterprise’s production system which keeps about 30 definition revisions, the reason is most probably the max.
0 kommentar(er)
