This page describes the ways in which you can restore the VoipNow system. |
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:
Please note that migration and backup restore are sensitive operations. We strongly recommend that you do not proceed unless you have experience with VoipNow. Otherwise, please open a support ticket. Also kindly note that errors or wrong actions during migration are not handled by the standard support packages. |
If your server already has VoipNow installed, run the following command:
The location of existing backups will be automatically queries and the following operations will be performed:
To restore the backup on a new server:
Run the following command:
vnrestore |
If the target server has a new IP (the backup was done on a machine with different IP), the |
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.
voipnow300_pbx/server/backup |