Quote from: LoyceV on April 06, 2017, 02:16:18 PM

Quote from: CryptKeeper on April 05, 2017, 09:08:56 AM

I would advice to move to the light version of the wallet (you need to move your funds if you're currently using the full version) and then use the 'full backup' function. This backup can be compressed and encrypted and can be stored easily

I tried this, but ran into some problems. First, it ran out of memory the moment I clicked EXPORT, and crashed. After adding more memory (now 4.5 GB) to the VM, it crashes after a few minutes of "Exporting...| with this message: "uncaught exception rangeerror array buffer allocation failed".
I think it still runs out of memory, what is it doing that requires several gigabytes of memory?
With a bit more memory it works now

The final backup-file is 533 MB compressed. I assume this includes the full almost 2 GB byteball.sqlite.533 MB is a bit big for a wallet with 1 address and 0 transactions.
This also means I can't switch to the light version, right?

I'm not importing it into a light wallet, but after an hour it still says "Importing...". It's not doing much on network or CPU, it may be stuck. Very nice that the wallet allows for a chat that allows you to pay in chat, but the basic functions don't work the way it should.

^{I'm leaving this error messages here for search engines to pick up on it. I didn't find anything related to Byteball when I entered the errors in Google.}

You can only restore to the same type of wallet as your source wallet. That's why I wrote that you must move your funds using two devices: one with the original full wallet and one with the light wallet. Sorry if I wasnt clear enough on this.