Video Screencast Help

out of disk space for SEPM - move SEPM to another drive

Created: 26 Mar 2012 • Updated: 10 Apr 2012 | 5 comments
ThaveshinP's picture
This issue has been solved. See solution.

I have 2 SEPM's running SEP 11RU7Mp1. On SEPM 1 that does AD synchronization, I am running out of disk space. SEPM 2 is fine.

What is the easiest way to move the SEPM 1 to another drive on the same server with more than enough space and keep the AD synch or would I have to move the AD synch to SEPM 2?

Comments 5 CommentsJump to latest comment

VIVEK.R's picture

Soln 1.

Soln 2.

Soln 3.Moving the Symantec Endpoint Protection Manager to another drive or server is not an overly complicated process, but there are a few simple steps that you will have to adhere to in order to make sure that the SEPM will communicate with the clients once it has been moved to the new location. 

*NOTE: If using this method to move to a new server, make sure that the Server Name and IP Address are the same on both the old and new servers.


(1)  Use the Symantec Endpoint Protection “Database Back Up and Restore” utility to take a backup of the SEPM environment including the Log Files. This will do a couple of things:

a. Create a backup of the database which will be stored at C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\backup\*.zip

b. Create 2 backup files that contain the Private Key for the server.  These files will be labeled “keystore_’date & version of backup here’.jks” and “server_’date & version of backup here’.xml”.  These files will be located at C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Server Private Key Backup\

(2 )  All of these files should be copied to a location that is easily accessible at a later time.

(3)  Uninstall Symantec Endpoint Protection Manager from the Server.

(4)  Restart the server.

(5)  Install the Symantec Endpoint Protection Manager on the desired Drive, using the same installation media version that you just uninstalled from the C: Drive.

(6)  When the Configuration Wizard launches at the end of the Installation, accept most of the standard settings. If your old installation used a SQL DB, make sure that you configure the DB setting to connect to the original database.  This will of course remove your old configuration from the DB, but that’s why we have a back-up.

(7)  Copy the database backup file to <Install Drive>:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\backup\.

(8)  Stop the Service titled “Symantec Endpoint Protection Manager”

(10)  Launch the “Database Back Up and Restore” utility, except this time select “restore” from the main menu; when asked which version to restore, select the one that was just copied to the new SEPM installation path.

(11) Once the restore is complete rename and copy the 2 key backup files to :

server_’date & version of backup here’.xml” – <Install Drive>:\Program Files\Symantec\ Symantec Endpoint Protection Manager\tomcat\conf\server.xml

keystore_’date & version of backup here’.jks” – <Install Drive>:\Program Files\Symantec\ Symantec Endpoint Protection Manager\tomcat\etc\keystore.jks

(12)  Run the “Management Server Configuration Wizard” to ‘Reconfigure’ the database, making sure to point it to the same database as was used previously.

(13)  After the reconfiguration is complete, the SEPM Console will launch automatically. You should now be able to log in as you have always done using your security accounts. The Console should indicate that it is communicating and managing the clients that were being managed prior to the SEPM Move.

Mithun Sanghavi's picture


In your case, you would have to check what folder of SEPM is using the Largest Diskspace, accordingly we could guide you..

However, In your case you could try checking these Articles below:

Issue Related to Low disk space.
Again, here are few important articles for you:
How to use a new Drive/Partition to host the Symantec Endpoint Protection content directory without reinstalling
How to move Inetpub or content folder without reinstalling Symantec Endpoint Protection Manager
Symantec Endpoint Protection Manager: Moving from the Sybase Embedded Database to Microsoft SQL Server
Hope that helps!!

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Chetan Savade's picture

Hi ThaveshinP,


There are two methods to move Symantec Endpoint Protection Manager (SEPM) from one machine to another:

Method 1: if the SEPM server keeps the same IP and host name, you can refer to "Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager"

Method 2: if the new SEPM server has a different IP and host name, there are two alternatives:

1. Use replication to install a new SEPM and keep the policy the same with old SEPM. See "How to move Symantec Endpoint Protection Manager from one machine to another"

Replication is an option, but its better not to go for that. Beacuse if you do replication and remove the old server that is the Primary SEPM , in future if you want to do replication you will not be able to do so.

2. Install a new SEPM, then use the Sylink file to establish communication between the new SEPM and the existing SEP client through sylink replacer tool.

Note : Sylink replacer tool is most commonly used option because it's easy to use.

Please go through following thread for more details:

Link for more information :

I hope it will help you.

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

Sonday's picture

Backup the database, Server private key backup, Ip & host name.

Uninstall & reinstall the new drive, then restore the database & update the server privete key.

Reconfigure the Management configure wizard.