Upgrade preparation
You must perform several steps to prepare for an upgrade.
To prepare for an upgrade
- Before you upgrade, back up the Application key, central configuration, databases, and any customized email templates. Use these backups to restore configuration information if the upgrade is unsuccessful.
Export the central configuration
On the web server, open Command Prompt as an administrator.
Go to the installation files folder:
cd "{ProgramFolder}\Install Files"
Run the following command to export the central configuration:
nsscmd.exe -getconfig
Save the command output in a secure location.
Back up databases and email templates
Back up both Self Service databases if database backup is part of your upgrade process.
If you customized email templates in version 11.1 or earlier, export the XML files from
Website\EmailTemplates, or record the customizations before the upgrade.After the upgrade, re-create the email templates in Settings > Email Templates, and then click Save. In version 11.2 or later, the email templates are stored in the database.
- Back up the databases
You should back up both Self Service databases before you start the upgrade. The default names for the databases are NetBackupSelfService and NetBackupSelfServiceNetBackupAdapter. Perform these steps in SQL Server Management Studio.
Make a note of the NetBackupSelfService database recovery model.
Set the database recovery model to Simple.
Back up the database.
Make a note of the NetBackupSelfServiceNetBackupAdapter database recovery model.
Set the database recovery model to Simple.
Back up the database.
- Take the portal offline.
Cohesity recommends that you prevent user logon and user activity while the upgrade is active. The best way to prevent user logon and user activity is to use Internet Information Services (IIS) Manager to stop the application pool for the portal website.
If a user attempts to connect to the website when the application pool is stopped, they receive an HTTP Error 503. The service is unavailable error in their web browser.
Do not stop the other application pools during the upgrade. If you stop the application pools with the suffix PublicWebServiceAppPool then the upgrade fails. The public web service is used for the upgrade.