How To Backup And Import Account?

Backup and import single account

If you want to backup and import your account, please do as beblow:

  1. CAUTION: PLEASE BACKUP YOUR ACCOUNT’s MNEMONIC-PHRASE OF MASTER-KEY AT FIRST.

  2. Backup Account
    Using cli command dumpkeyfile to export your account information to backup file.

    $ ./mvs-cli dumpkeyfile account_name password last_word path_of_backup_keyfile

    last_word: The last word of your account’s mnemonic-phrase.
    path_of_backup_keyfile: The path of backup file.

  3. Import Account
    Using cli command importkeyfile to import your account information from backup file.
    NOTICE: you must use the same password as when using dumpkeyfile.

    $ ./mvs-cli importkeyfile account_name password path_of_backup_keyfile

    path_of_backup_keyfile: The path of backup file.

Backup and import accounts’ database file

Somehow, We have to backup/import database of accounts, we can do as below:

  1. Backup accounts database (without blocks)
    Copy and paste the below into the path search function on your device’s explorer:

    # Windows: Explorer
    %HOMEPATH%\AppData\Roaming\Metaverse

    # Mac-OSX: Finder => go to folder
    ~/Library/Application Support/Metaverse

    # Linux(unix-like):
    ~/.metaverse

    Copy and paste the account related tables in the sub-directory mainnet as a backup.
    All those tables’ name have prefix account_, include the followings:

    account_address_rows
    account_address_table
    account_asset_row
    account_asset_table
    account_table

  2. Import accounts’ database file
    Just copy the backuped tables in the above step back into the mainet sub-directory.
    NOTICE: when access your account, you must use the same username and password as in the backuped account tables.

Re-syncing blocks

If your database has some problem, please take one of the following solutions to re-syncing.

Solution 1 - re-syncing from height 0 (Linux) :

# backup old mainnet directory
$ mv ~/.metaverse/mainnet ~/.metaverse/mainnet.bak

# re-build new database
$ ./mvsd -i

# import accounts database(overwirte)
$ cp -f ~/.metaverse/mainnet.bak/account_* ~/.metaverse/mainnet/

# re-start mvsd in daemon mode:
$ ./mvsd -d

# waiting for syncing completed.
$ tail -f ~/.metaverse/debug.log

Solution 2 - re-syncing from height 1270000+:

Linux

# backup old mainnet directory
$ mv ~/.metaverse/mainnet ~/.metaverse/mainnet.bak

# re-build new database
# use mainnet-linux-height-1473277.tar.gz (md5sum is 54c996066d1249eca25e28babc3940b7)
$ cd ~/.metaverse
$ wget https://s3-us-west-1.amazonaws.com/wallet.mvs.org/download/mainnet-linux-height-1473277.tar.gz
$ tar -xzvf mainnet-linux-height-1473277.tar.gz

# import accounts database(overwirte)
$ cp -f ~/.metaverse/mainnet.bak/account_* ~/.metaverse/mainnet/

# re-start mvsd in daemon mode:
$ ./mvsd -d

# waiting for syncing completed.
$ tail -f ~/.metaverse/debug.log

Windows

  1. Stop wallet, upgrade to the lastest version
  2. Rename ‘C:\Users\%USER_NAME%\AppData\Roaming\Metaverse\mainnet’ to ‘C:\Users\%USER_NAME%\AppData\Roaming\Metaverse\mainnet_bak’
  3. Download block data mainnet-windows-height-1475846.zip and save to ‘C:\Users\%USER_NAME%\AppData\Roaming\Metaverse\mainnet-windows-height-1475846.zip’.
  4. Unzip ‘mainnet-windows-height-1475846.zip’ to where it is.
  5. Copy all files that start with ‘account_’ from folder ‘mainnet_bak’ to folder ‘mainnet’. Files that need to be copyed: ‘account_address_rows’, ‘account_address_table’, ‘account_asset_row’, ‘account_asset_table’ and ‘account_table’.
  6. Start wallet and wait for syncing block data to the lastest height.