2.2 Upgrade Procedure

During the upgrade process, the installation program automatically exports and then re-imports data from your previous installation.

To upgrade your PlateSpin Protect product:

  1. Before you begin the upgrade, prepare for the software upgrade by performing the tasks in Section 2.1, Before You Upgrade PlateSpin Protect.

  2. Log in to the PlateSpin Server host as an administrative user.

    If the server is in a domain, you must log in as a domain user who is a member of the Domain Admin group and the local Admin group.

    If you use Windows Authentication for the database server, you must log in as the domain user with SQL Admin rights. This user must have local administrator rights to the PlateSpin Server.

  3. Run the PlateSpin Protect Setup executable as the Administrator user, then follow the on-screen instructions.

    • Ensure that you select the Save data option when you are prompted during the server installation.

    NOTE:If replication jobs are still running, the validation might launch the Running Jobs Detected dialog. This prompt might also occur if some jobs were aborted and the condition is not correctly detected. You must wait for all operations to complete, or abort the running operations. After each workload’s Replication Status is Idle, in the installation dialog, select Yes - Proceed with installation, then click Next.

  4. When you are prompted to specify a database instance, point the installation program to your existing database instance and provide the appropriate authentication type and credentials.

    • For Windows Authentication to the database server, ensure that the logged in user has local administrator rights and has system administrator rights in the database server in order to upgrade the schema of the database. The user you specify as the Service User must also have local administrator rights.

    • For SQL Authentication to the SQL Server Express Edition database server, the SQL system administrator (sa) user and the default generated password (created when you installed SQL Server Express) is automatically completed for database administrator Login ID and Password. If you previously set a custom password for the sa user, type the custom password before you click Validate Credentials.

  5. Verify that the PlateSpin Protect software was upgraded to version 11.3:

    1. Log in to the PlateSpin Protect Web Interface.

      If you cannot access the log in, the upgrade might have failed. Verify that the PlateSpin Server host is up, the PlateSpin Server running, and the network connections are working, then try again to log in. If you still cannot access the login, the upgrade process failed. Jump to Step 7.

    2. Click About to view the version number. On the About page, the Software Version should be 11.3.0.xxxx, where xxxx represents the build number.

      If the version number displays the earlier version, it could be a browser cache issue. Clear the browser cache, close and restart the browser, then try again. If the version is still old, the upgrade failed. Jump to Step 7.

  6. Verify that the protected workload data was re-imported successfully after the upgrade. In the PlateSpin Web Interface, click Workloads, then visually confirm that the expected workloads are present.

    If the protected workloads are not present, part or all of the upgrade process failed.

    In some situations, the installation program might fail to automatically re-import data that it exports during the upgrade process. If this happens, use the ImportExportAll.bat utility to recover this data from the \ProgramData\PlateSpin directory on your server host. This folder is hidden by default.

    In order to import or export when you use Windows Authentication for database access, the following conditions must be met:

    • The user must be logged in as the domain user with SQL Admin rights to access the database. This user is specified during the installation. See Step 4 in Configuring Your Remote Microsoft SQL Server Database Server.

    • As is required by the installation, the domain user with SQL Admin rights to access the database must be a member of the local Administrators group.

    • The process that runs the ImportExportAll.bat utility must have elevated privileges. This is most easily accomplished by starting a command window using the Run as administrator context menu option.

  7. If the software upgrade failed according to the tests in Step 5, or if you were unable to re-import the data in Step 6, then try the upgrade again.

  8. After the upgrade has successfully completed, continue with Post-Upgrade Tasks.