Restore the VoipNow System

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:

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:

   $body

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.

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.