Migrating Appspace on-premises from Windows 2008 to Windows 2012 manually
This article provides the instructions for you to manually migrate your Appspace server running on a Windows 2008 operating system to a new server with Windows 2012.
- Backup Existing Appspace Databases
- Backup Appspace Folders
- Request for Appspace License
- Install Appspace on Windows 2012
- Restore Databases
- Restore Appspace Folders
- Activate Appspace
- Ensure your Windows 2008 server has been updated with the latest Microsoft updates.
- A new server preinstalled with Windows 2012 R2 and updated with the latest Microsoft updates.
- Administrator privileges for Windows Server 2008 and Windows Server 2012.
- Administrator privileges for the Appspace account.
- Identical license key(s) for the backup server.
- Contact Appspace Support to obtain the latest version of the Appspace Installer, and the migration tool.
- SSO configurations will not be copied over to the migrated server.
- Users whose invitations are pending must be deleted on this server, and re-invited again on the new server after migration.
Backup Existing Appspace Databases
Backup the existing Appspace databases from your windows 2008 server to a new location. You may choose to copy the folder to a location within the server, or to an external source such as a USB drive or a secure cloud storage service.
Stop the Internet Information Services (IIS) on the Appspace server, from the command prompt using this command: iisreset /stop
For more information, please refer to the instructions on the Microsoft website: https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/95826e7a-bac4-4e1f-bcb6-c52d49c9d7f4.mspx?mfr=true or https://technet.microsoft.com/en-us/library/cc732317(v=ws.10).aspx
Run the MySQL Workbench program from the Windows Start menu.
Click ‘Local instance MySQL’. The ‘Local instance MySQL’ tab will be displayed, with the Data Export and Data Import/Restore links shown on the Navigator sidebar.
You may need to enter the root password (if not already stored in the vault).
Select Data Export under Management in the Navigator pane, and in the Local Instance MySQL tab, select one database schema you would like to export, and ensure that all the tables are selected in the Schema Objects window on the right.
Ensure the following ‘Objects to Export’ checkboxes are checked:
- Dump Stored Procedures and Functions
- Dump Events
- Dump Triggers
Select the ‘Export to Self-Contained File’ option, and choose a location to store your .sql file (you may also customize the name of the file to your own preference). Click the Start Export button.
Allow some time for the export process. The progress bar will indicate the status of the task. The task will be completed once the Status indicates that the file has been exported. You may verify this by navigating to the location of the newly-generated .sql file in Windows Explorer.
Repeat Steps 3 to 5 for all the other database schemas by creating new self-contained .sql files. Ensure that only one database schema is selected at any one time, and that the ‘Export to Self-Contained File’ option is selected before exporting.
The following databases are required by Appspace for the backup process:
Note: Ensure all databases with the prefix “ext_” are copied.
Backup Appspace Folders
Backup the Appspace data and folders from your windows 2008 server to a new location. You may choose to copy the folder to a location within the server, or to an external source such as a USB drive or a secure cloud storage service.
From Windows Explorer, copy and paste the following Appspace installation folder to a desired backup location:
In Appspace versions prior to 5.1 (i.e. 5.0.x), the installation and content folders are located here:
- Installation Folder – C:\Nexus
- Content Folder – C:\NexusMediaNet\FTPFastNetV2
It is recommended that these old folders are restructured to match the current installation folder structure:
- Installation Folder – C:\Appspace
- Content Folder – C:\Appspace\Content
Repeat the process for other folders that host Appspace files (if any).
Request for Appspace License
Each new Appspace installation requires a new Appspace license. Please contact your respective Appspace sales representative to request for a new Appspace license that matches your previous installation.
Install Appspace on Windows 2012
Install Apspspace 6.2.x on your new Windows 2012 server. Please refer to the Installing Appspace on-premises article.
You must restore databases in MySQL by manually importing the self-contained SQL files backed up earlier to the Windows 2012 server.
Stop the Internet Information Services (IIS) on the server, by following the instructions on the Microsoft website: https://technet.microsoft.com/en-us/library/cc732778(v=ws.10).aspx
In MySQL Workbench, click Data Import/Restore, and select the ‘Import from Self-Contained File’ option. Locate the .sql file in your server and choose the appropriate Default Target Schema from the drop-down menu.
Click the Start Import button. The progress bar will indicate the status of the task.
Repeat the same procedure for the other database schemas (dsnmetrics, playoutmetrics, etc).
Restore Appspace Folders
Once the databases are restored, you may proceed to restore the installation folders and files from the previous Appspace server to the same location in the new Appspace server. By default the location is:
Repeat the process for other folders backed up earlier (if any).
Run Appspace Installer
Rerun the Appspace Installation Center (AIC) and select the Upgrade option. Please refer to the Upgrade Appspace section in the Upgrading an Appspace on-premises server article.
Start the Internet Information Services (IIS) on the server, by following the instructions on the Microsoft website: https://technet.microsoft.com/en-us/library/cc732778(v=ws.10).aspx
Proceed to activate the new license. Please refer to the Activating Appspace on-premises article.