Before you upgrade the PlateSpin Server software to PlateSpin Protect 11.2 SP1, ensure that you prepare your PlateSpin Servers and workload environments to meet the following prerequisites:
(Conditional) Ensure that your VM containers are running a supported version of VMware ESXi and that you have a paid license for them. For more information, see Supported VM Containers
in the PlateSpin Protect User Guide.
Pause the replication schedules for all protected workloads, and ensure that no replications are running. See Section 2.1.1, Pausing the Replication Schedule.
Make a record of any customized .config parameters controlling the server’s default behavior. You will need to restore these settings after the upgrade.
Back up your database files. See Section 2.1.2, Backing Up Your Database Files.
Back up your custom Linux blkwatch drivers. You will need to upload these drivers again after the upgrade. See Section 2.1.3, Backing Up Your Custom Linux blkwatch Drivers Before Upgrade.
Upgrade .NET Framework 4.5 to .NET Framework 4.5.2.
Before you attempt to upgrade PlateSpin Protect, use the following procedure to pause the replication schedules for the workloads protected by the PlateSpin Server and ensure that there are no running replications. You can wait for the in-progress replications to complete gracefully, or abort them.
From the PlateSpin Protect Web Interface, click Workloads.
On the Workloads page, click Select All, click Pause Schedule, and then click Execute to initiate a pause for all scheduled replications.
On the Workloads page, ensure that the Schedule state of protected workloads is Paused.
On the Workloads page, ensure that the Replication Status of each of the protected workloads is Idle. Wait for any replications that are underway to complete, or abort the running operations.
If you do not perform this task before the upgrade, the upgrade software will automatically detect the running jobs before it executes the software upgrade, and will prompt you to perform the task before you continue. You can proceed with the upgrade process only when each workload’s Replication Status is Idle.
Use the following procedure to manually back up the Microsoft SQL Server database file that resides on the same server as PlateSpin Protect. You can use the backup file if you need to roll back.
On your server host, stop Microsoft SQL services:
On the Start menu, click Run, type services.msc, then click OK.
In the Services window, right-click the SQL Server items, then select Stop.
Copy all *.mdf and *.ldf files to a location outside the product installation directory. The default location of these files is:
\Program Files\PlateSpin Protect Server\Database
Restart MS SQL services that you stopped in Step 1.
NOTE:This procedure assumes that your Protect database is installed on the same server with your PlateSpin Protect Server. Steps for backing up an external SQL server are similar, although the paths to the *.mdf and *.ldf files are specific to your SQL server.
During the upgrade, the PlateSpin Protect installation program will overwrite custom Linux blkwatch drivers that you previously added to PlateSpin Protect. Consider saving a copy of your custom Linux blkwatch drivers prior to the upgrade.
Log in to the PlateSpin Server host machine as the Administrator user.
Navigate to the PlateSpin application's installation directory, such as C:\Program Files\PlateSpin Protect Server\.
Open the .\Packages\9D470BFF-E30F-4015-83D8-4D308A8C8B1B\ folder and copy the 1.package file out of this folder to a temporary directory.
Rename 1.package with the .zip file extension (1.zip), then extract the contents of the file to this temporary directory.
Save your CustomKernel* content to another temporary location.
Proceed with the upgrade, as detailed in Upgrade Procedure.
After the upgrade, you should upload again any custom Linux blkwatch drivers you need for future migrations. See KB Article 7005873.