MSSQL Server migration
1. Stop the NetFlow Analyzer service.
2. Backup the old Netflow DB and restore on to the new DB server (Connect MSSQL client using SQL Server Management Studio and backup netflow database and restore it new server).
3. From the New MSSQL SERVER, copy the files bcp.exe and bcp.rll to NetFlow/bin/ folder.
4. Please make sure that "SQL browser" service is running in the new server.
5. Download the same version of MSSQL server Native client and install it on the NetFlow server. This is needed for NetFlow Analyzer Plugin to communicate remote database server. After installing the Native client, please restart the NetFlow Analyzer server.
Once installed the native client please follow the below steps and check if it works or not:
Open command prompt as Administrator and navigate to NetFlow_Home/bin
Execute bcp.exe and check if you get the option or any error. If you get the error, then check the error and install the package as mentioned in the error message and execute the bcp.exe again. You should get proper output.
4. Make sure that the database user for netflow has "sys admin" permission.
Open command prompt as Administrator and navigate to NetFlow_Home/bin
Execute bcp.exe and check if you get the option or any error. If you get the error, then check the error and install the package as mentioned in the error message and execute the bcp.exe again. You should get proper output.
4. Make sure that the database user for netflow has "sys admin" permission.
If using Windows Authentication for the MSSQL database follow the 5th set or skip.
5.
Stop Opmanager service. Right click on NetFlow Analyzer service name ->
Properties -> Log on -> This account -> Provide MSSQL server AD
account and save it.
6. Make sure that the database user for NetFlow has "sys admin" permission.
7. Open a cmd prompt as administrator, and navigate to /NetFlow/bin/.
8. Execute ChangeDBserver.bat -> Select MSSQL and Provide the New MSSQL server IP
9. Check if all the information is correct for new SQL server, click Test first and then Save the configuration.
10. In the MSSQL database server right click on the netflow db -> New Query and execute the below quries one by one:
OPEN MASTER KEY DECRYPTION BY PASSWORD = 'Password123'
ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY
alter master key regenerate WITH ENCRYPTION BY PASSWORD = 'Password123';
ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY
alter master key regenerate WITH ENCRYPTION BY PASSWORD = 'Password123';
10. Start the NetFlow analyzer service, wait for couple of hours and check the reports.
New to ADSelfService Plus?
Related Articles
MSSQL database migration in v12
Kindly follow the below steps to migrate the SQL DB, 1. Take a backup of "customer-config.xml" file from the location "ManageEngine\OpManager\conf". 2. Take a SQL backup of OpManagerDB from the old server via SQL Management Studio. 3. Create a new DB ...Netflow Analyzer migration (Links based on installation type)
Kindly refer the links below to migrate your Netflow Analyzer installation per your need - https://support.zoho.com/portal/manageengine/helpcenter/articles/mysql-32-bit-installation-to-64-bit-migration (For builds up to 9700) ...Migration of Database from MYSQL to MSSQL in the Firewall Analyzer
Please refer the below link for MYSQL to MSSQL migration. http://www.manageengine.co.in/products/firewall/help/appendix/migrating-data-mysql-mssql-database.html Note: I request to stop the Firewall Analyzer service and take the backup of complete ...PGSQL 32bit to 64 bit server to server migration (Postrgesql DB) for NetFlow Analyzer
NetFlow Analyzer installation can be migrated to a different server with old database and configuration provided both the installation are in same version and build number. Please follow the steps given below to migrate Netflow Analyzer to a ...MSSQL Database shrink.
To reduce the MSSQL database size, please follow the below steps. 1. Stop the NetFlow Analyzer service. 2.Open a command prompt as administrator(Right click and run as administrator) Navigate to <NetFlow_Home\troubleshooting\>. 3. Execute the ...