Hi,
I wanted to know that if database server is rebooted what will be the risks? And how much time will it take approximately??
Regards,
Kiran Javed
The boot time varies depending on how large the DB server really is. As for risks I always have a backup ready and some server techs available in the event it dies but normally I just do a reboot and comes back on it's own. I think mine took only a few minutes to boot actually but I was just watching pings from command prompt.
It never hurt to stop the SolarWinds (or any other dependant) services before bouncing the DB server as well.
this will also largely depend on the system you are using. I have an old Sun X4600 and it takes about 10min to reboot. I reboot once every week on a schedule.
I'm working to migrate to a [actual] new system though and don't plan on doing that scheduled reboot.
if your DB server is separate from everything else, then your site will just give you an error saying can't talk to SQL. if on same system as primary NPM, then your site will go down hard as the primary web server will go down.
This really depends on how you have your environment set up.
If i stop the sql server before reboot, then after reboot and on starting sql server how much time will it take to come in proper working state???
9 minutes 57.26 seconds.
My opinion:
If the database server is separate from the Orion server, during the SQL reboot will be the polled data stored in MSMQ. After the reboot finishes, data from MSMQ will be transfered to the DB. Only DB depending services (e.g. website, alerting) won't be processing data while the DB is down. By default MSMQ size is not very large, but should cover the DB outage time in most cases (of course depends on number of polled elements, Orion modules, etc...). The must here is static IP address for both servers.
if you reboot the DB the website will be still up as long as you don't reboot the primary app server. You will simply not be collecting any data or view any data on the website untill DB is finished booting.
