GBall Creator (Automated Server Backup)

[PhantosP2P]

I'd love to, but I am unsure of the correct thing to type. If I run gballexpander.jar from my command prompt (Windows 7), it opens the java front-end and asks me to select a file. What triggers do I use to tell it the first file?

Something like "c:\gball\gballexpander.jar -c:\gball\levels_0.arc" ?

It doesn't freeze or anything. It will create the folder as if starting, but then it simply disappears and nothing is extracted. I have 171 of these babies and it took over three days to compile :)

p.s. I love you.

[cbk1994]

Launch it with "java -jar c:\gball\gballexpander.jar", then try. When it stops working, look in the command prompt to see if there are any error messages.

[PhantosP2P]

Oh there we go!

[cbk1994]

Originally Posted by PhantosP2P

Oh there we go!

I'll try to fix that later. For now, you can run it with "java -Xmx1024m -jar c:\gball\gballexpander.jar" to increase the maximum memory it's allowed to use (if it happens again, increase '1024').

[PhantosP2P]

Thanks! This worked, but only after I grabbed the 64-bit version of Java so that I could tell it to grab 3GB instead of 1GB. The process is running now, and man is there a lot of stuff here.

Thank you again for making a viable backup option for us.

[ffcmike]

I decided to give this a shot at backing up Classic's account files, which was always likely to be problematic considering there are over 100,000 account files (would be nice if Stefan could help us out by comparing account text files with the actual accounts database, as there's a lot of junk that should be removed), which totalled about 110 mb after we wiped having been 380 mb before.

After setting this.maxlooplimit to 200,000 in order to not break the max loop limit it didn't take long during the file writing to receive an error related to flood alert, while using the default 4 mb at a time with a 6 minute delay, so it does look as if flood sensitivity isn't definite.
Setting it to a 10 minute delay writing just 2 mb at a time is working so far.

Edit: Now getting a flood error when attempting to write at 15%, 3% incrementation.

[cbk1994]

Yeah, I've had a lot of issues with the flood alert, and the times I've set are a bit generous here. Honestly, I'd consider trying gsync instead. It doesn't suffer from the the flood alert since it's not writing anything. The bottleneck would probably be how fast you can upload to a remote server, which should be pretty quick.

Granted, I have not tried it with a large number of small files, so it may need some adjustments (e.g. raising max loop limit).