Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

syslog server backup and restore

Hi,

I am in the process of moving kiwi syslog server v9 from one system to other system. want to check if there is a simple process to migrate all settings instead of reconfiguring.

Thanks,

Sridhar

Find more posts tagged with

Accepted answers

All comments

Aforsythe

Sridhar,

Yes there is a simple process... But there may be some cleanup that needs to happen afterwards, or at least there was in my case. It still beat configuring from the ground up.

First thing you need to do is export your settings to an INI file. There is an option on the file-menu in the kiwi service manager.

Then you need to save that ini file and ALL scripts that you are using. You'll want to move them over to the new server where you can "Import Settings" from the File menu on the new server.

Clean-up:

1. I did have to re-create all of the databases and custom tables in SQL Server and you will have to as well if you do not intend on doing a DB Backup and restore on the new server (I didn't need the data so I did not move it) and I had scripted the structure so the only manual process for me here was to run the script to create the databases and tables.

2. I did have to go through and re-establish database connection strings in all of my rules that log to the database because the server/instancce name had changed and so had the logon credentials.

3. I had to change script locations because the drive the scripts were on had changed. I only had about 40-50 rules and a few dozen scripts so this wasn't so bad, but hind-sight I would have just written a script to parse through the INI and change C:\ to G:\ where applicable.

4. The default Editor path incase you use something besides notepad for script editing needs to be the same as it was on the previous server. I know there is a place to change this information somewhere but I haven't looked. I usually have Edit Pad Pro up and running on the server and browsing the scripts folder anyway, so the "Edit Script" button not working doesn't inconvenience me any.

That is all of the clean-up that I had to go through, but if you are logging to files and archiving and rotating files etc... you may need to change the relevant paths associated to those actions as well.

Hope this helps,

Acy

chvgms

Thanks for the details and quick response.