VoipNow Management

Page tree

Versions Compared

Old Version 3

changes.mady.by.user Wikid

Saved on

compared with

New Version 4

changes.mady.by.user Wikid

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated using 4PSA automated script
Excerpt

This page describes the ways in which you can restore the VoipNow system.

Table of Contents
maxLevel2

Overview

A VoipNow backup can be restored in-place (on the same server) or on a different server (target and source are different).

The following assumptions are made:

  • You have at least one database backup (a file having VN_DB_ in its name).
  • You have at least one full filesystem backup (a file having VN_FS_FULL_ in its name).
  • You have zero or more incremental filesystem backups (a file having VN_FS_INCR in its name).

Restore the same server

If your server already has VoipNow installed, run the following command:

Shell

The location of existing backups will be automatically queries and the following operations will be performed:

  1. Services are stopped.
  2. The latest database backup is restored.
  3. The latest full filesystem backup is extracted.
  4. The incremental backups following the last full filesystem backup are extracted.
  5. Services are started.

Restore to a different server

To restore the backup on a new server:

  1. Install VoipNow on the new server.
  2. Log in and configure the backup settings (only the backup folder is important at this stage).
  3. Copy the database backup, the full filesystem backup and (optionally) the incremental filesystem backups to the specified folder.

  4. Run the following command:

    Shell

  5. Services are stopped.
  6. The latest database backup is restored.
  7. The latest full filesystem backup is extracted.
  8. The incremental backups following the last full filesystem backup are extracted.
  9. Services are started.
Warning

If the target server has a new IP (the backup was done on a machine with different IP), the vnrestore script will log an error message due to VoipNow services being unable to start. This is normal - VoipNow components will not start properly until the database is updated (the old IP must be replaced with the new IP).

Debugging

Both the vnbackup and the vnrestore scripts read the DEBUG variable in backup.conf. If set to yes, additional debug information will be logged in the console.

Also, both vnbackup and vnrestore will create lock files under /var/lock/.vnbackup and /var/lock/.vnbackup. If their execution is not properly ended (meaning the script is stopped forcefully or an error is encountered), these lock files remain in place and will block further operations.

Please check the cause of the error by inspecting the log files, fix the error, and only then remove the corresponding lock file.

4psarelated
NameRelated Topics

Back up on a Remote System

Backup Directories and Preferences

Backup Operations

Hiddenlabel
voipnow300_pbx/server/backup

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.