Pre-Upgrade Preparation and Upgrade Notes
Explore this Page
Overview
This section outlines key preparation steps and important notes to ensure a smooth DataCore SANsymphony upgrade. It covers verifying access, backing up configurations, meeting prerequisites, and enabling necessary services. It also highlights critical cautions to avoid upgrade issues and maintain system stability.
Pre-Upgrade Steps
The DcsAdmin account and password must be known before proceeding.
- Refer to DataCore FAQ 1277 (Known Issues: Third Party Hardware and Software) before upgrading.
- Read and understand the Upgrade Notes and the Installation and Upgrading from Previous DataCore SANsymphony Versions sections (see Known Issues).
- Ensure that all hardware and software requirements are met before installing or upgrading DataCore SANsymphony.
- Ensure all mirrored virtual disks (vDisks) are healthy and all replication streams are fully initialized before performing the upgrade.
- Ensure that the "Windows Modules Installer" service is not disabled. By default, this service should be set to "Manual", and will be automatically started and stopped as required.
- Back up the configuration. Refer to Backing Up and Restoring Configuration Files in the DataCore SANsymphony Help for directions that includes stopping the DataCore Server before doing the backup. A backup folder will be created automatically if the location has not been previously set in the DataCore Server Details>Settings Tab.
- If DataCore Technical Support has previously requested that the DataCore.Executive.CorePMFdll.config file be customized because of a specific hardware configuration, copy this file to a safe location, as it must be restored after the upgrade, replacing the newly installed file.
- Close all DataCore windows on all DataCore Servers being upgraded before proceeding with the upgrade instructions below.
- Enable firewall rules on all servers. In Server Manager->Configuration->Windows Firewall with Advanced Security, select Inbound Rules, and enable the following:
- Windows Management Instrumentation (WMI-In)
- Windows Management Instrumentation (ASync-In)
- Windows Management Instrumentation (DCOM-In)
- Remote Volume Management (RPC-EPMAP)
- Remote Volume Management - Virtual Disk Service (RPC)
- Remote Volume Management - Virtual Disk Service Loader (RPC)
- File and Printer Sharing (Echo Request - ICMPv4-In)
- Next, select Outbound Rules and enable the following: Windows Management Instrumentation (WMI Out).
- Open local TCP port 445 (File Sharing/RPC) for incoming connections from remote hosts.
Upgrade Notes
- During the upgrade procedure, do not modify the existing configuration until the entire upgrade is complete. This includes making changes to replication when server groups are on different versions of DataCore SANsymphony software. If issues are experienced during the upgrade, such as mirrors not recovering, contact DataCore Technical Support.
- It is assumed that DataCore Servers always have the most up-to-date “Root Certificates” (used for verifying signed drivers). If DataCore Servers have unknown or expired ca-certificates, download and install the most recent “DigiCert Assured ID Root CA” from here: https://www.digicert.com/kb/digicert-root-certificates.htm.
- After upgrading the first DataCore Server and restarting it, do not open the DataCore Management Console on any other DataCore Servers until they are upgraded. To monitor the upgrade, use the DataCore Management Console on the newly upgraded DataCore Server. Alternatively, for DataCore Servers without the DataCore Management Console component installed, next upgrade the stand-alone DataCore Management Console server to monitor the status during the upgrade.
- After upgrading a DataCore Server and completing the reboot required by the installer, do not stop that DataCore Server or reboot it again until all other DataCore Servers in the same server group have been upgraded.
- When upgrading DataCoreDataCore SANsymphony installations on Windows Hyper-V servers where a dependency has been set up between the Hyper-V Virtual Machine Management Properties (VMMS) service and the DataCore Executive Service will require that the VMMS service is manually stopped before the server is upgraded.
- When upgrading, DataCore Deployment Wizard uses the hostname to connect to the target systems. Hence, DataCore Deployment Wizard validates the hostname of the machine being connected to against the hostname of the machine to which the DataCore Deployment Wizard is connected. An error is displayed if a mismatch is found. In the event, DataCore Deployment Wizard prompts a false mismatch issue, bypass this validation by adding the Wizard-flags.xml file to DataCore Deployment Wizard's installation directory C:\Program Files\DataCore\DataCoreDeployment\SDW.
- The physical disks with Capacity Optimization enabled will be displayed under the Capacity Optimization option in the DataCore Servers panel of the DataCore Management Console, only after all the servers in the configuration are upgraded to SANsymphony 10.0 PSP18 or later. For more information, see here.
- Prior to SANsymphony 10.0 PSP16, SANsymphony used Microsoft SQL Server 2012 Express LocalDB to store the local performance recordings. Now while upgrading to SANsymphony 10.0 PSP16, Microsoft SQL Server 2022 LocalDB will be installed and configured. However, the previously installed LocalDB version 2012 will not be removed. This will ensure that no other client applications depending on Microsoft SQL Server 2012 Express LocalDB are impacted. To uninstall "Microsoft SQL Server 2012 Express LocalDB" safely, ensure that no other applications are using it.
- If any Commvault Agent software is installed on any SANsymphony servers, do not upgrade the servers to DataCore SANsymphony 10.0 PSP17 or higher. Contact DataCore Technical Support for more information.
Users must be logged in as local administrator or must be a member of the local Administrators group to uninstall "Microsoft SQL Server 2012 Express LocalDB".
Learn More