You want to know how to move the Symantec Endpoint Protection Manager (SEPM) database to a new SQL server, possibly due to decommissioning your existing hardware.
You can perform a SQL backup of sem5 and restore this to a new SQL server or instance using the following procedure:
Back up and restore the database
- Right-click the sem5 database and choose Tasks > Back Up.
You can choose to use the existing backup file, or for a smaller backup file, you can remove that path and designate a new path and filename.
- Copy the backup file to the new SQL server and restore the database as sem5.
- Once the database is restored to the new SQL server or instance, the sem5 database user must be deleted, and a new sem5 login must be created. This is because there is no sem5 login, and you cannot create a login for a database if that database user already exists.
Delete the sem5 database user
- Open the sem5 database
- Click Security > Users.
- Locate and delete the sem5 user.
Create a new login for sem5
- From the top of the hierarchy, open Security > Logins.
- Right-click Logins and choose New Login.
- Use the login name:
- Enter a password.
- Use the default database:
- On the left, click User Mapping, and then check sem5.
- In Database role membership for sem5, check dbowner (public should already be checked).
- Click OK.
Connect the SEPM to the database
At this stage you have either installed a new SEPM, or plan to use the same SEPM as before. In either case, the SEPM needs to be pointed to the new database location.
Run the Management Server Configuration Wizard to point the SEPM to the new database.
- If SEPM is already installed: Choose the option to Reconfigure the Management server. When prompted, enter the credentials for the sem5 user created in the steps above.
- If SEPM is a new installation, the wizard will launch after the setup is complete. Choose the option to add an additional manager to an existing site. When prompted, enter server name(\instance name) of the new SQL server, and the credentials for the sem5 user created in the steps above.
- If you are installing a new SEPM, you must use the same version of SEPM as the original SEPM. If you install a newer version of SEPM, you will get an error that the schema is not compatible.
- This solution works for all versions of SEP, as well as SQL 2005, SQL 2008 and SQL 2012.