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

DataBase copying

I am looking into creating a mirror of my production environment. The only difference is that the mirror polling will only do ICMP only, no SNMP. In our production we use 3 pollers and in the mirror we will use only one.
What I want to do is copy over the data base to the backup solution and then using the manage polling engines tool move all nodes to the one server. After the database is moved to keep the data base fresh and synced with production I want to copy over the production nodes table to the mirror location. I would create a job of some sort that would change all nodes to ICMP only, change the polling engine to the one server and change the polling intervals to what the server can handle. Would this be possible, or would in need to copy over more tables? I want to at all possible keep the amount of data used to backup as small as possible. Additional information, we have no need for historical data.

Has anyone done anything like this?

Find more posts tagged with

Accepted answers

All comments

FormerMember

problem i see with this is that you will have to copy your main database every (timeperiod you decide) then shut down the secondary system and run a script on the database to change all the pollers and fix the type of polling. Then restart the secondary system once the script is done having inserted the new copy of the database.

This is a very intense operation and will require manual intervention each time you do it.

once you perfect the script it will be manual to the point that you must stop Solarwinds on the secondary system until you insert the new database.

one other thing you might need to think about is frequency of polling. If you are combining all the devices from 3 pollers to one you will probably have to drop back on the polling to 3 times the normal poll cycle on you main system.

This really seems like a lot of work when you could just stand the box up as a spare solarwinds server and if the main fails just cut over to it.

aliendan

The stopping and starting of Orion should be the easy part. We will use a simple batch script. I think I will only need to copy the nodes table (but that is what I am looking into). In our BD this is only about 6.8 MB. That copy should be quick. About the polling cycles. The mirror system is only going to ping the nodes.

Fail over is not an option. We need an off site solution that will run if we loss the main site.