Help Center
About File Auditing About Endpoint DLP About File Analysis About Data risk assessment Release NotesQuick Start
- System requirements
- Minimum privileges required
- Default port configuration
- Installing DataSecurity Plus
- Uninstalling DataSecurity Plus
- Starting DataSecurity Plus
- Launching DataSecurity Plus
- Configuring your solution
Setting up File Audit
- Domain configuration
- File server configuration
- Failover cluster configuration
- Workgroup configuration
Dashboard
Reports
Alerts
Configuration
Storage Configuration
Setting up Endpoint DLP
Reports
Alerts
Configuration
Setting up File Analysis
Dashboard
Reports
Alerts
Configuration
Setting up Data risk assessment
Dashboard
Reports
Alerts
Configuration
About DataSecurity Plus
How-To
- How to Migrate/Move DataSecurity Plus
- How to apply SSL certificate
- How to automate DataSecurity Plus database backup
Troubleshooting
Quick Start File Auditing Endpoint DLP Data Risk Assessment File Analysis About DataSecurity Plus Release notes Contact usContact us
2019
2018
2017
2016
2015
Administrative settings
- Technician configuration
- Email configuration
- Notification filters
- Manage agent
- SIEM integration
- Business hours configuration
General settings
Migration guide
Follow the guidelines in this article to:
- Move DataSecurity Plus from one server or drive to another.
- Migrate DataSecurity Plus from 32-bit to 64-bit architecture.
or
Moving DataSecurity Plus from one server or drive to another.
- Stop the DataSecurity Plus server(Start > Run > type services.msc > Stop ManageEngine DataSecurity Plus).
- Stop the DB.
- Open Command Prompt as an administrator
- Navigate to <installation dir>\ManageEngine\DataSecurity Plus\bin
- Execute StopDB.bat
- Remove the DataSecurity Plus service.
- Open Command Prompt as an administrator
- Navigate to <installation dir>\ManageEngine\DataSecurity Plus\bin
- Execute the command wrapper.exe -r ..\conf\wrapper.conf
- Copy the entire DataSecurity Plus folder to the new server or drive.
- Ensure both folder sizes are the same.
- Open Command Prompt with administrative privileges. Navigate to \ManageEngine\DataSecurity Plus\bin and execute InstallNTService.bat.
- If you want to start the product as a service, go to:
Services.msc > ManageEngine DataSecurity Plus Service. Right click on Properties, click Log on select This Account and provide the appropriate credentials.
Permissions needed on the target folder while moving the installation folder
Ensure that the following permissions are assigned to the target folder while changing the installation location:
- To another drive or another folder (except Program Files and Program Files(x86)).
- To Program Files or the Program Files(x86) folder:
By default, the required permissions (Read & execute and Write) will be pre-set by Windows. Ensure that the permissions assigned for Authenticated Users are not removed, as DataSecurity Plus can't operate without these permissions.
As the permissions needed for Authenticated Users will not be pre-set, we'll have to assign them explicitly. Provide Authenticated Users with Modify and Read & execute permissions on the data folder (inside the pgsql folder). Another option is to run the initpgsql.bat file inside \ManageEngine\DataSecurity Plus\bin.
Migrating DataSecurity Plus from 32-bit to 64-bit architecture
- Check the product build number. If it's not the latest build, upgrade your 32-bit version of DataSecurity Plus to the latest build using the appropriate service pack from the below link. https://www.manageengine.com/data-security/service-pack.html
- Install the latest 64-bit version of DataSecurity Plus in a different computer. Do not start the product.
- Stop the 32-bit installation.
- Provide a different name for the below folders in your 32-bit installation.
- lib
- jre
- bin
- Now copy the following folders from the 64-bit build installation folder and save it in the 32-bit installation folder.
- lib
- jre
- bin
- Go to the \ManageEngine\DataSecurity Plus\conf folder in the 32-bit installation.
- Open product.confusing Wordpad.
- Change product.processor_architecture to 64.
- Start the 32-bit installation and reapply the license file.