How To Restore a database backup ?

[Phillip Weeks]

ok I have it starting up
Ill let you know how I make out
looks promising

[Phillip Weeks]

when I pick the database to restore there are two entries .zip and .zip.zip
which one is the correct selection??

[phildunlap]

.zip, the .zip.zip issue was recently fixed. If you'll look you're see .zip.zip is 0 bytes.

[Phillip Weeks]

do I restart the server immediately or wait a few mins while this unzips?

[phildunlap]

Shouldn't matter. As long as you do not kill -9 the process it will wait for the task to finish.

[Phillip Weeks]

I had no success restoring the backup db. I tried several times and also copied the zip to my laptop to see if I could restore it on that system but no either way it hangs on restart.. Is it possible for me to send you the zip file and you send me back a mah2 db that I can just put into that directory?

[phildunlap]

Can you describe what you mean 'hangs on restart' more fully?

Do you have an error when starting Mango that prevents Mango from starting?

[Phillip Weeks]

Okay I was able to get the db up on my laptop by starting it in SAFE mode (thank God) so its a memory issue on the laptop hanging. On the cloud server I have lots of memory. Can I now just copy this mah2.db and mah2.lock to my cloud server's database folder. and start cloud mango?

[phildunlap]

You don't need the lock file.

I don't feel like you've provided any of the information I've asked for at any stage. This will quickly disinterest me in this thread.

[Phillip Weeks]

Sorry I must apologize Phil, One month ago I thought mango's were delicious. So I have been learning much every day and you have provided me with much insightful help and instruction thus far. Joel's methodology worked for me to restore the backup db. It was more my misunderstanding about what was happening on my pc that was confusing me and I am not yet comfortable working in terminal window on linux so I try the stuff on the pc first. Anyhow, every issue we have been experiencing has been a result of running out of memory as the root issue. We get frozen out or it crashes. Growing pains. Tomorrow we shall have 8gb and 4 cpu's to play with and life should return to happy. A while ago you helped me with scripting the missing point interpolation and deleting outliers. Scripting is fine but I found that exporting specific data value ranges from watchlists and then importing back in through excel permits me the best control over deletion and adding points. Which was a brilliant suggestion you made to another user with same issue.
I have abandoned my scripting efforts on interpolating points. Thankfully you say :) lol
Anyway thanks again for your support and sorry for the disconnect..
Mango Rocks
I Love it :)

[phildunlap]

It is alright. I'm sure you can understand that to provide the best support I have to assess what information is probably relevant and available, and then get that information. I try to keep some eye to the long term for threads, and if our exchanges contain things like the text of the exact error the user encounters or simple descriptions of exact symptoms makes everything more searchable.

Best of luck on the new computer! I wonder, have you been setting a heap limit with an ext-enabled script?

[Phillip Weeks]

Ha ha you got it I was just messaging you back about the heap size and how I go about that . We have 8gb like this... What do you recommend and how to do it. Please and thanks. I'll start including some of the data from now on # top :)
I'm in a different time zone than our servers in case you were wondering.

This is from inside.. Our ES is much snappier than this system right now as its configured.

[Phillip Weeks]

Hard to see so

[phildunlap]

You can simply move a script for a correct size from Mango/bin/ext-avialable into Mango/bin/ext-enabled like memory-medium.sh, which sets a static heap of 5 Gb.

For 8 you could consider modifying it to 6 Gb, like,

#!/bin/bash
case "$1" in
    init)
        # Startup with Java Memory setup for Medium size installation
        # The heap is set to non-expanding for increased performance.  If memory use is a factor
        # set the Minimum heap size to a lower number and let the JVM adjust when necessary.
        JAVAOPTS="$JAVAOPTS -Xms6g -Xmx6g"
        ;;
esac

[Phillip Weeks]

That was easy .. Do I restart mango or the server to activate this configuration?

[phildunlap]

Yes, it won't take effect until the next startup, so that might mean restarting.

[Phillip Weeks]

OK thanks

[Phillip Weeks]

I restarted and JVM max memory is still about where it was at 1775mb before the change and the server says over 2 gb free does this look right for a 6gb heap?

[phildunlap]

Looks alright. If you do a ps $(pidof java) you can see if the command line options are set.

If you're getting the 1775Mb number from within Mango (i.e. internal metrics) know that Java is able to be more clever about its reporting, and even if it's allocated itself a minimum and maximum against the operating system it can expand and contract what's available for use in its own runtime.

[Phillip Weeks]

Its been a few days now since the server upgrade and here is what I have learned after tuning the system.. At first I modified the memory-medium.sh to 6gb heap as Phil suggested. This change did not take effect until Linux server was restarted because I restarted mango from inside mango no improvement or change in JVM. However once I rebooted the Linus server performance went up dramatically and UI became significantly faster, I then lowered it back to 5gb because JVM free memory was high. Unbenounced to me I had made an error in the sh file and JAVA consumed all the memory available so the heap was 8 and JVM was 3GB free memory!! At first I expected things to be great but soon experienced high degradation in performance and the system came to a crawl with constant Server Timeouts on every action. Linux could not keep up with limited memory I am guessing, So I shutdown and inspected the logs which had the script error on this sh config file. Fixed the error in memory-medium.sh file and uploaded the corrected file to the server, rebooted with 5gb heap. System came back up and leveled to about 15% above previous JVM levels but running perfectly now with few server timeouts and I set HI priority thread max to 2000 and 1000 for HI priority thread pool? Could anyone add significance to how and why mango responds to these changes?
This graph depicts how mango reconfigured memory through-out the changes made 2gb Heap to 5gb heap.

and this is current Mango stats after the process.

Linux Perspective: