Upgrading your WS_FTP Server Installation OS from Windows 2003 to 2008

These instructions explain how to migrate your present WS_FTP Server installation from a Windows 2003 to 2008 R2/2012 operating system, complete with your present accounts, configuration, and data:

1. If your current installation is a release prior to WS_FTP Server v7.5.1, upgrade your current installation to the 7.5.1 version. This step is necessary because the migrated database must be a version 7.5.1-compatible database.
2. Back up the “ws_ftp_server” and “ips_notifications” databases created by your current 2003 installation. (If your installation uses PostgreSQL for its database, use PostgreSQL’s pgAdminIII tool to back up these two databases. If your installation uses MS SQL Server, use the BACKUP DATABASE command, or the Backup Database option in Enterprise Manager. Refer to the appropriate Microsoft or PostgreSQL documentation for details.)
3. Install WS_FTP Server on the Windows 2008 R2/2012 server you want your WS_FTP Server installation to reside on. (See the section Installing WS_FTP Server.) Also install Server modules, as appropriate, such as the WS_FTP Server Web Transfer Client.
4. Copy the files for the databases (created in step 2 above) to the target Windows 2008 R2/2012 Server.
5. Stop all Ipswitch services on the target Windows 2008 R2/2012 server. You can do this by navigating to Server > Services, selecting the checkboxes next to each service, then clicking Stop.
6. Drop empty databases for both WS_FTP Server and IPS Notifications database on 2008 R2/2012 (“ws_ftp_server” and “ips_notification”). For SQL Server use the DROP DATABASE command, or drop the database in Enterprise Manager using the Drop Database task. For PostgreSQL, use the pgAdminIII tool.
7. Create new database and restore the database with the new files. With MS SQL, the command will be RESTORE DATABASE, or the Restore Database option in Enterprise Manager. With a PostgreSQL database, in the pgAdminIII tool, right click Databases, choose New Database, then use the following parameters:

   Name your new database “ws_ftp_server”

   Owner = IPS_admin

   Encoding = UTF8

   Template = template0

   Tablespace = pgdefault

   Ok

   After right clicking and creating a second New Database:

   Name your new database “ips_notifications”

   Owner = IPS_admin

   Encoding = UTF8

   Template = template0

   Tablespace = pgdefault

8. Restart the services stopped in Step 5. Verify that WS_FTP Server is in proper working order on the target 2008 R2/2012 machine by transferring a test file, logging into WS_FTP Server, and checking to see if data is correctly displayed under Users, Listeners, and Notifications.