Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
fwconsole backup --restore /home/20200109-110433-1578548073-14.0.13.23-818337824.tgz --restorelegacycdr
Transaction ID is: 76bbbff3-c47f-4b5f-b5ca-e922e230cba9
Determining backup file type...type is legacy
Legacy CDR Restore Option: 1
Starting restore job with file: /home/20200109-110433-1578548073-14.0.13.23-818337824.tgz
Extracting backup...


Restore Legacy Backup using in-file-db(sqlite) instead of in-memory via command line (--useinfiledb)

This recommended only for Legacy Heavy backup which can cause memory issue shown below And this option (--useinfiledb) will make the restore process very  slow

Code Block
proc_open(): fork failed - Cannot allocate memory on line 523 of file /var/www/html/admin/libraries/BMO/GPG.class.php
#0 [internal function]: Whoops\Run->handleError(2, 'proc_open(): fo...', '/var/www/html/a...', 523, Array)
#1 /var/www/html/admin/libraries/BMO/GPG.class.php(523): proc_open('/usr/bin/gpg2 -...', Array, NULL, '/tmp', Array)


 This kind restore is possible only via command line , And the option you need to pass is --useinfiledb

Code Block
fwconsole backup --restore /home/20200109-110433-1578548073-14.0.13.23-818337824.tgz --useinfiledb
Transaction ID is: 76bbbff3-c47f-4b5f-b5ca-e922e230cba9
Determining backup file type...type is legacy
Starting restore job with file: /home/20200109-110433-1578548073-14.0.13.23-818337824.tgz
Extracting backup...
Legacy Restore is using file based sqlite
Loading manifest to memory
Loading astdb to memory
Utilizing file based sqlite at /tmp/76bbbff3-c47f-4b5f-b5ca-e922e230cba9.db, This is SLOW


Core

Convert Legacy chan_sip extensions to chan_pjsip

...