I will be migrating PRTG to a new server. I know this will take a while so I need to know if there is anyway to get alerts from the sensors while migration is happening.
during migration, the PRTG probe service is down so sensors are not working, also the core service is down and cannot send out notification.
Many parts of the migration can be done in parallel (like installing PRTG on the new server) meaning the actual downtime can usually be kept short.
Thanks for the reply. What else can be done in parallel? What can be done to keep downtime as short as possible?
you could also copy most of the data (except for the current day) from "C:\ProgramData\Paessler\PRTG Network Monitor\Monitoring Database" to the new server before stopping the services. Please review the official migration guide to see which steps are necessary to migrate. Anything which is not changed (historic data except for the current day, and the file "PRTG Configuraiton.dat") can be copied before stopping PRTG on the old server.
I really appreciate the quick replies. How long would migration take then? Your official guide says it would take "a while". I can't have the alerts down for more than a couple of hours.
the downtime can usually be kept below an hour. You can prepare the new server by configuring the web interface settings and copying the bulk of the data-folder content. Then stop the PRTG services on both server.
Now copy the rest, the "PRTG Configuration.dat" file and the current-date subfolder of the "Monitoring Database" folder.
When the core service is restarted after the migration, that first start-up takes more time because PRTG computes the graph data cache for the last three days (and does the rest via a background task.) A machine powerful enough to run PRTG might need 5 to 20 minutes for that.
I have two folders called Monitoring Database. One has newer dates and the other has older dates. Do both of them need to be copied to the new server?
Never mind. This was from someone else's previous attempts of migration. Disregard.
PRTG only uses one of such folders. That means, the current PRTG will not show the content of both. In order to keep the current status, only the newer "Monitoring Database" has to be copied. You can try to merge the content into one "Monitoring Database" folder but it is not clear what would happen, as the history of the older "Monitoring Database" is not known. The best way seems to copy only the newer folder, while making a backup of the old, just in case.
Earlier response:"Anything which is not changed (historic data except for the current day, and the file "PRTG Configuraiton.dat") can be copied before stopping PRTG on the old server."
Does this mean all folders can be moved before stopping the core services?
except for the files in the base folder "C:\ProgramData\Paessler\PRTG Network Monitor\". and the most recent subfolder in "Monitoring Database", yes.