LogoLogo
www.mikopbx.comTelegram communityForum
English
English
  • MikoPBX Manual
    • Quick start
    • Getting to know MikoPBX
    • System requirements
  • Installation
    • Standalone Computer
    • Virtual Machine
      • VMware ESXi
      • VMware Fusion
      • VirtualBOX
      • VMware Workstation Pro
      • Hyper-V
      • Proxmox
    • Cloud
      • AWS
        • AWS deployment guide
        • AWS Marketplace
      • Microsoft Azure
      • Google Cloud
        • Google Cloud deployment guide
        • Google Cloud Marketplace
      • Hetzner cloud (In dev)
      • Digital Ocean
      • Alibaba Cloud
      • Vultr
    • Docker container
      • Docker installation and creating a user and directories
      • Running MikoPBX in a container
      • Running MikoPBX using docker compose
  • User manual
    • Telephony
      • Extensions
      • Call queues
      • IVR Menu
      • Conferences
      • Sound files
      • Call detail records (CDR)
    • Call Routing
      • Telephony providers
      • Incoming routing
      • Outbound routing
      • Night and Holiday Switch
    • Modules
      • Registration in the modules marketplace
      • Module management
      • Application dialplans
    • Maintenance
      • PBX update
        • Updating from the web interface
        • Updating from the MikoPBX console
        • Updating the docker
      • System log entries
      • Reboot
    • Network and Firewall
      • Network interface
      • Firewall
      • Anti brute force
    • System
      • General settings
      • Time Settings
      • Mail settings
        • Setting up E-mail notifications for the Gmail mail service
      • Asterisk Manager Interface(AMI)
      • System files customisation
  • FAQ
    • Setup
      • Installation on MDADM RAID1
      • Fine-tuning the firewall
      • Migrating MikoPBX to Another Server
        • Transfer Using Backup
        • Transfer using scheduled backup (SFTP)
        • Transfer using rsync
      • Reset to factory settings
      • Monitoring Providers on MikoPBX
    • Management
      • Change the login name
      • The extra disk space has run out, the disk size has increased
      • Storing Recordings in a Shared Windows Folder
      • Resetting WEB Interface Credentials
      • Backup Internet and Provider Re-Registration
    • Troubleshooting
      • Connecting to the PBX using SSH
        • Connecting to PBX using SSH client (Putty)
        • Connecting via SSH (Windows)
        • Connecting via SSH (Linux/MacOS)
      • Connecting to a PBX using WinSCP
      • Getting logs using the tcpdump application
      • Capturing Logs from PBX using Wireshark
      • Traffic Analysis Using Sngrep
      • Adjusting the volume
      • Troubleshooting sound problems
      • Jitter Configuration
    • Incoming Routing
      • Choosing a provider when redirecting to a mobile
      • Notification of Employment, Call Waiting
      • Black and white lists
      • Allow additional dialing of the internal number in the queue
      • Output of information about the did number
      • Setting individual non-working hours for a provider account
      • An example of the implementation of a typical route of incoming calls
      • Routing by DID Number
      • Normalization of incoming phone number
      • Basic IVR example
    • Outbound routing
      • Add P-Preferred-Identity and Remote-Party-ID header
      • Conference with a regular external subscriber
      • Outgoing with internal number dialing
      • Remove all special characters from the dialed number
      • Prohibiting calls via a backup route
      • Calls to emergency numbers
      • Number Templates
        • Uniform distribution of outgoing
        • Sample template: calls to another country
        • How to prohibit the replacement of "+" with 00
        • Changing the number prefix from "+345" to "347"
        • Changing the number prefix from "345, 347" to "+345"
        • Removing the area code from the number
        • Adding the prefix "1" to the number
      • Making Calls Through a Specific Provider
    • Scenarios and cases
      • Generate extensions by REST API
      • Missed Call Telegram Notifications
      • Call the company from your mobile and dial an extension to call a third-party company
      • Sending an incoming fax to email
      • Customer's assessment of the quality of service
      • Simulation of external calls
      • Disabling "off-hours" for VIP numbers
      • Registering multiple accounts from one provider
      • Setting up individual non-working hours for several providers on one host
      • Disable forwarding to mobile for internal calls
      • Unique background music for the queue
      • Pause for Queue agent
      • Dynamic Queue Agents
      • Setting up the "Paging" function
      • Limit the number of authorizations per SIP account
      • Call Monitoring (ChanSpy)
      • Conversion of Call History FreePBX -> MikoPBX
      • SSL Certificate for MikoPBX Web Interface from OPNSense
      • Hiding the Caller’s Number from Employees
    • Interconnections
      • Merging two MikoPBX
      • Integration of MikoPBX and Grandstream UCM6202
      • MikoPBX and FreePBX (PJSIP)
      • MikoPBX and FreePBX (IAX)
    • VoIP providers
      • Mango
      • Zadarma
    • Softphones
      • Bria Solo
      • Sessiontalk
      • MicroSIP
      • Groundwire
      • Zoiper
      • Jitsi
      • PhonerLite
      • Linphone (MacOS)
      • Telephone(MacOS)
      • Configuring webRTC client SIMPL5
      • Softphone.pro
      • 3CX Softphone
      • PortSIP
    • IP telefones
      • Snom D120
      • Yealink T19
    • VoIP gateways
      • GoIP4
      • Grandstream HT503
      • Using a Huawei E173 USB Modem for Calls (chan_dongle)
  • Modules
    • MIKO modules
      • for 1C:Enterprise
        • Панель телефонии 4.0 для 1С
        • Панель телефонии 1.0 для 1С
        • Модуль умной маршрутизации
      • Users groups
      • CRM Bitrix24 integration
      • Autoprovision
      • Let's Encrypt
      • Access control management
      • Module auto dialer
      • Backup
      • Synchronization with LDAP/AD
      • Callback module
  • other
    • Changelog
      • MikoPBX 2024.1
      • MikoPBX 2023.2
      • MikoPBX 2023.1.223
Powered by GitBook
On this page
  • Creating a Backup
  • Managing Backup Files
  • Restore from Backup
  • Scheduled Backups

Was this helpful?

Edit on GitHub
Export as PDF
  1. Modules
  2. MIKO modules

Backup

Last updated 7 months ago

Was this helpful?

Note: In version 2020.2.XXX, the backup functionality has been moved to a separate module and is not included in the core package. The module can be installed via the Module Management section.

Creating a Backup

  1. Go to the "Modules" -> "Marketplace of modules section" tab.

Make sure that the Backup Module is installed and enabled.

  1. Go to the module settings.

  1. Click on "Create backup copy".

  1. Select the data that should be included in the backup:

  • PBX Settings - all configuration settings of MikoPBX made in the web interface.

  • Call History - saves the cdr.db database (location: /storage/usbdisk1/mikopbx/astlogs/asterisk/cdr.db). This setting does not save actual call recordings, only the information on the Telephony → Call History (Documentation) tab without playback/download functionality.

  • Call Recording Files - saves all call recordings in *.mp3 format.

  • Sound Files - saves sound files uploaded to the PBX in the Telephony → Sound Files (Documentation) section.

  1. Click on "Create a backup".

Once the process is complete, the backup will appear in the list of backups:

Managing Backup Files

In the backup list, you can perform the following actions:

  • Restore from a backup.

  • Download the backup archive.

  • Delete the backup.

Restore from Backup

The process of upgrading from Askozia 4, 5 ME to MikoPBX is described in this guide.

  1. In the list of backups, select the desired one and click "Restore from backup".

  1. Select the categories of data to restore.

  1. Click on "Restore from a backup".

The restoration process will start, and once completed, the PBX will be rebooted.

The progress of data restoration will be displayed on the current page.

We recommend restoring the data in two stages:

  1. Restore Sound Files, PBX Settings, and Call History.

  2. Restore Call Recording Files - this is the longest stage.

Scheduled Backups

  • FTP Mode - creates a ZIP archive. For this mode, an FTP server is required.

  • SFTP Mode - creates an IMG container. This mode only requires MikoPBX.

  • WebDav Mode - creates an IMG container.

The fastest backup options are SFTP and WebDav. FTP is outdated, and the ability to use this protocol will eventually be removed from the backup module.

  1. Click the "Backup schedule" button to configure automatic backups.

  1. To enable scheduled backups, activate the switch "Scheduled Backup."

  1. Fill in the required information:

  • Server Address - IP address of MikoPBX or the address of the SFTP \ FTP server.

  • Port - for SFTP mode, the port is 22. Disabling the "SFTP Mode" switch activates FTP mode with port 21.

  • Username - the username for server authentication.

  • Password - the password for server authentication.

  • Server Path - the directory where the backups will be saved. Recommended directory on MikoPBX: /storage/usbdisk1/mikopbx/backup/.

When using WebDav, the directory in the "Server Path" field must be created manually in advance.

  • Schedule - specify the day and time for the backup operation.

  • Keep Last X Versions - specify how many backup versions should be retained.

  • PBX Settings - all configuration settings of MikoPBX made in the web interface.

  • Call History - saves the cdr.db database (location: /storage/usbdisk1/mikopbx/astlogs/asterisk/cdr.db). This does not save actual call recordings, only the information on the Telephony → Call History tab without playback/download functionality.

  • Call Recording Files - saves all call recordings in *.mp3 format.

  • Sound Files - saves sound files uploaded to the PBX in the Telephony → Sound Files section.

  1. Click "Save."

Marketplace of modules section
Module settings
"Create backup copy" button
Created copy
Options
"Restore from a backup" button
"Backup schedule" button