We have 2 servers with 2 DPA installations and 2 repositories, one of them internally and the other one in an Azure server. We want to migrate the internal one to the Azure server and we want to be able to monitor all of DBs (over 20) from the same DPA installation that is already in the Azure server.
I have moved DPA repositories before, but I'm not sure if we can join 2 DPA repositories. If we can't join the 2 DBs, then we would lose the monitoring history from either most of the DBs or the most important DB, which would be a big loss. Is there any way to either join both repositories or export the history of the DBs that we will move so we can import it again?
Solved! Go to Solution.
I'm not sure of merging the data and how complicated it might be (e.g., export only a subset of repo tables and whether assigned ids, etc. may have to be massaged to match the Azure).
A couple of alternatives you might want to consider:
Thanks for the options!
Regarding DPA Central, can it be done by still moving the on-premise DPA to Azure but have 2 separate Azure repositories? I read that DPA central uses the server information to connect so I dont know if we can have the 2 DPA instances in one server and connect them through DPA Central.
I confirmed that merging will be difficult because of DPA Server generated names, ids that would likely conflict between the two DPA Server databases. Doing so will require a lot of manual, custom work to resolve and maintain data integrity.
You'll need two DPA Servers, one for each repository (new Azure and moved). As far as running both DPA Servers simultaneously on the same OS, I wouldn't suggest it. The overhead of the second server in terms of resource conflicts will likely impact the scalability (i.e., how many DB instances you can monitor) of the actively monitoring one. I don't know if others have run two servers simultaneously on the same OS and if so, what adjustments or configurations (such as using different ports for each) would be required.
My suggestion would be to isolate the second DPA Server into its own VM to avoid same OS resource conflicts and also make it very easy to start/stop when you need it, move it elsewhere, provision resources, avoid difficulties in upgrades, or delete the second server via VM management interfaces.
Awesome! Thank you for all the information. I think we are really tending to DPA Central, just need to confirm resourcing in general.
The idea now is that since we are going to continue to grow, instead of just using the "moved" instance as history, we would keep both active and be able to just keep growing.
You can have 2 DPA servers running on one OS in Azure, but make sure the OS is Linux. Could potentially use Windows, but it is much more difficult especially on upgrades. Overall, I would still recommend separate VMs to avoid some of the problems mentioned in my earlier response.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.