General Migration Notes
- Before migrating to a new server, we recommend upgrading to the latest version of the MediaCP.
- A valid license is required to complete the restoration process.
- Transferring of files can often take hours to complete, be sure to leave enough time before terminating your old server.
- Before completing a migration, you should request that both old and new server IP addresses be added to your software license.
- The restoration process will prompt you for a custom media content path if you wish to relocate your media files to another disk during the migration
Wowza Streaming Engine Notes
- If you have custom Wowza Streaming Engine configurations, such as multiple VHosts configured, you are required to migrate these configurations manually to the new server once the MediaCP is deployed on the new server.
- If you have configured a custom Ondemand Directory from Admin -> System Config -> Plugins -> Wowza Streaming Engine, then you must manually copy this directory to the new server and specify the new path after migration.
1. Prepare DNS records
It is highly recommend to lower the Time To Live (TTL) of your DNS records to 300 before migration.
2. Create Linux compatible backup file
- Download and save the latest version of the installation software:
http://install.mediacp.net/MediaCP-Install.exe - Run MediaCP-Install.exe
- Select option [4] Linux Migration
3. Transfer backup to new server
The easiest way to transfer the backup to the new server is directly via SSH connection using a utility such as WinSCP.
- Install WinSCP on your Windows Server
- Open WinSCP and connect to your new Linux Server
- Upload (drag and drop) the backup file from C:/ drive into /root/
4. Restore the MediaCP
- Install MediaCP
- Install Wowza Streaming Engine (if supported by license)
- Restoration will then automatically replace MediaCP files, database and media content with the backup from your windows server
- Attempt to start all your media services
cd /root;rm -f init;wget http://install.mediacp.net/scripts/init;chmod +x init;./init restore
a) You will be prompted for your license key and the path to the backup file.
b) You will also be prompted to specify a location for your media content files. If you wish to leave this as default, simply press return. If you wish to install the media files to a different location, you may do so here and a symlink will be created automatically from /usr/local/mediacp/content to the new location.
The path to the backup file should be similar to /root/mediacp_201911180000.tar
(be sure to replace mediacp_201911180000.tar with the name of your backup file).
5. Check new server is running appropriately
We recommend thoroughly testing your panel before switching DNS records.
Firstly, on your new server in SSH open /etc/hosts (nano /etc/hosts) and ensure your domain name is mapped to the loopback address 127.0.0.1. See the below image example
You can do this by updating your systems hosts file to point your domain name at the new server, so only you can see the new server and your customers will still access the original server.
Open your systems hosts file:
- Navigate to C:\Windows\System32\drivers\etc
- Right click hosts file and Open with “Wordpad”
- Add a new line containing your new servers IP Address and your domain name, separated by a single space. It should look like the below.
- Close all instances of your web browser then start it again and you should be accessing the new server.
6. Update DNS Records
- Login to wowza.com Portal
- Select the StreamLock tab
- Scroll down and select the Change link next to your stream lock certificate
- Input your new servers IP Address and press save
b. MediaCP Domain Name
Update your DNS record to point to the new server.
