HPE StoreOnce 3.16.x Software Upgrade Guide

Transcription

1 HPE StoreOnce 3.16.x Software Upgrade Guide Abstract This document describes the process for upgrading to StoreOnce 3.16.x from StoreOnce 3.14.x and later software. This document is intended for system administrators and system engineers who are familiar with installing StoreOnce software. Part Number: BB Published: January 2018 Edition: 4

2 Copyright 2017, 2018 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group.

3 Contents Overview... 5 StoreOnce software upgrade packages...5 Upgrading the StoreOnce system...5 Planning the software upgrade...6 Considerations before upgrading...6 Maintenance window guidelines... 7 Verifying hardware and system status... 8 Preparing for the software upgrade Upgrading StoreOnce software Copying the upgrade package to the StoreOnce server...12 Updating the StoreOnce software...13 Stopping service sets and disabling failover (6x00 systems only) Verifying that the software update was successful Applying firmware updates...16 Updating firmware from the StoreOnce GUI Updating firmware using the StoreOnce CLI...18 Completing the update...19 Verifying the DNS configuration when using Remote Support...19 Finding StoreOnce documents in the HPE Information Library...21 Troubleshooting the upgrade process...22 Package file is invalid error message You attempted to upgrade from 3.14.x or 3.15.x using the incorrect (OS conversion) RPM file...22 You attempted to upgrade 3.13.x to 3.14.x or later using a normal (non-os conversion) RPM You must be running or greater...24 Discovered GB to be added...24 Some support tickets are empty when downloaded Firmware update for FC HBA Updates not attempted StoreOnce websites...26 Support and other resources...27 Accessing Hewlett Packard Enterprise Support Accessing updates...27 Customer self repair...28 Remote support Contents 3

4 4 Contents Warranty information...28 Regulatory information...29 Documentation feedback... 29

5 Overview StoreOnce software upgrade packages The underlying operating system changed between the 13.x and 14.x releases. Select the package for the StoreOnce software version currently running on the system. Upgrading from 3.14.x or later The regular upgrade package, which is used for systems running or newer software. StoreOnce versions and later only support update from In this case, upgrade to and then to your target software version. Upgrading from 3.13.x To upgrade from 3.13.x to 3.16.x, you must first upgrade to using the OS conversion package P9L rpm. This upgrade package includes extra steps necessary to convert to the new underlying operating. All customer data is protected during the upgrade. NOTE: After updating from 3.13.x to you should not change the SMB version in the GUI until you have upgraded to or later. To use this upgrade package, the system must be running at least If the system is running or earlier software, upgrade the system to at least before upgrading with this upgrade package. IMPORTANT: See the release notes to determine which software upgrade package to use. StoreOnce software upgrade packages are delivered in RPM format. Upgrading the StoreOnce system 1. Plan the software upgrade These actions can be completed days to weeks ahead of time. 2. Prepare for the software upgrade Complete these actions immediately before updating the StoreOnce software. 3. Upgrade the StoreOnce software Overview 5

6 Planning the software upgrade Complete these planning steps and address any issues well before beginning the software upgrade process. 1. Download and review the software release notes. 2. Review the Considerations before upgrading. 3. Schedule a maintenance window. See Maintenance window guidelines. 4. Verify hardware and system status. If any hardware components or service sets are in a degraded or nonfunctional state, the software upgrade utility will not upgrade the StoreOnce software. You can verify the status and address any issues before starting the upgrade to minimize downtime during the software upgrade. Considerations before upgrading The StoreOnce 3.16.x releases contain changes and restrictions that existing customers are advised to consider before upgrading. Removal of TLS 1.0 support: TLS 1.0 support has been removed to comply with higher security standards required in various industries. Before using the StoreOnce GUI after on StoreOnce 3.16.x or later software, TLS 1.1 or 1.2 must be enabled in the web browser. TLS 1.1 is enabled by default with Internet Explorer 11, Mozilla Firefox v27 and above, and Firefox ESR 31 and above. For other supported browsers, TLS 1.1 or 1.2 is not enabled by default and must be enabled it in the browser settings. These browsers include: Internet Explorer 9 and 10, Mozilla Firefox 23 to 26, and Firefox ESR 24 to 26. Recovery Manager Central: RMC or later is recommended. If using RMC 1.2 or 2.x in a vcenter environment, newly installed StoreOnce Systems must be added through the RMC graphical user interface. StoreOnce Enterprise Manager: Minimum SEM version is required to add and manage StoreOnce Systems with and later software in SEM. Internet Explorer 8 no longer supported: ilo 4 firmware in 3.16.x removes support for IE8. Recommended browsers include IE 11 and the latest versions of Chrome and Firefox. NOTE: Any customers using SMB signing are advised to call HPE Support before upgrading. 6 Planning the software upgrade

7 Additional considerations when upgrading to The following issue exists in StoreOnce version and has been fixed in subsequent releases. CoFC with FC ports configured in LOOP mode If you are currently using Catalyst over Fibre Channel with FC ports configured in "loop" mode DO NOT UPGRADE to version There is a known issue where using loop Fibre Channel topology with CoFC will always result in backup/restore failures. If possible, connect the StoreOnce appliance with FC SAN switches or connect to Catalyst devices using Ethernet. This issue is fixed in later versions. Before upgrading to a newer software version, check the release notes to confirm that this issue is fixed. Additional considerations when upgrading from StoreOnce 3.13.x Warranty entitlement details: The warranty details, required for StoreOnce Remote Support, customers cannot modify the warranty details after the upgrade. Before upgrading, ensure that all warranty information is set and correct. After upgrading, you will need to contact HPE Support if changes are required. Active Directory support with IPv6: StoreOnce and later releases have a limitation in the automatic handling of mixed IPv4 and IPv6 environments. Before upgrading systems using Active Directory with IPv6, ensure that the StoreOnce System management interfaces are configured with both IPv4 and IPv6 addresses. Download old support tickets: The 3.13.x to 3.16.x OS conversion upgrade process only retains the latest three support tickets. Download all older support tickets before upgrading. StoreOnce Catalyst over Fibre Channel support for AIX: After upgrading, preapproved customers using StoreOnce Catalyst over Fibre Channel with AIX clients must reconfigure the FC port Host Emulations from "Default" to "AIX". Maintenance window guidelines The system will be unavailable for normal operations during the upgrade process. This upgrade takes slightly longer than previous software upgrades because it saves the configuration as part of the process. When scheduling the maintenance window, use the following as guidelines for a typical upgrade process: Allocate 30 to 60 minutes to perform preupgrade actions. For StoreOnce 6500 and 6600 products, the entire upgrade process takes approximately 4 hours, depending on the hardware configuration. Maintenance window guidelines 7

8 The software upgrade portion generally takes 60 to 90 minutes, but can, on very rare occasions, take longer. A further 3 hours is required to perform necessary hardware firmware updates after the successful software upgrade. For all other StoreOnce products, the entire upgrade process takes approximately 2 hours, depending on the hardware configuration. The software upgrade generally takes 60 minutes, but can, on very rare occasions, take longer. A further 20 to 80 minutes is required to perform necessary hardware firmware updates after the successful software upgrade. Verifying hardware and system status The software upgrade utility will not upgrade the StoreOnce software if these commands report errors. You can run these commands before starting the upgrade and then address any issues to minimize downtime during the software upgrade. 1. Verify that the appliance is in a healthy state by running the StoreOnce CLI commandsystem confidencechecker runtest all. If a test fails, follow the steps in the troubleshooting guide to address problems before continuing with the software upgrade. 2. Verify hardware status using the StoreOnce CLI command, hardware show problems. The upgrade will be blocked if any hardware, except HBA_Port, shows a status of removed, failure/failed, or down/offline. IMPORTANT: All configured network ports (NIC_port) must be properly connected otherwise they will be flagged as down/offline and the software upgrade will not proceed. a. Find details for reported warnings or errors using the CLI or from the GUI. Run the StoreOnce CLI command: hardware show status <dev-id of failed hw> detail, where <dev-id of failed hw> is the value shown in the dev-id of failed hw column of the output from the hardware show problems command. On the StoreOnce GUI, navigate to the Hardware and then drill down to the failed item. Read the Diagnostic messages for the failed hardware. b. Address any reported hardware failures before attempting a software upgrade. 3. Verify service set status using the StoreOnce CLI command, serviceset show status. A typical example of the output of this command: # serviceset show status 8 Verifying hardware and system status

9 Service Set 1 Status Overall : Running StoreOnce Subsystem : Running Virtual Tape : Running NAS : Running StoreOnce Catalyst : Running Replication : Running Housekeeping : Running If any of the service sets is in a state other than Not Started or Running, upgrades will fail. Planning the software upgrade 9

10 Preparing for the software upgrade Perform the following actions immediately before starting the software update process. Prerequisites IMPORTANT: The software and firmware update processes require service sets to stop and the system to reboot. These actions are disruptive to any I/O running on the system at the time, including: back up, restore, StoreOnce Catalyst Copy, Replication, and housekeeping. 1. Ensure that all hardware firmware is at a version supported by both the current and target StoreOnce software versions. a. For StoreOnce 6x00 systems, disable failover with the CLI command, system disable failover. b. Use the CLI command, hardware show firmware [nodex storagex switch] to display the current firmware version. c. If necessary, use the CLI command hardware update firmware [nodex storagex switch] to update the hardware firmware 2. Reboot the system so it is in a clean and clear state before the upgrade. a. For StoreOnce 6x00 systems, disable failover with the CLI command, system disable failover. b. Reboot the system with the CLI command, system reboot. 3. Reduce the size of a large Events database. The size of the Events database is displayed on the top of the StoreOnce GUI on the Events page. Most upgrades fail when the number of events is greater than 50,000. The number can be as low as 30,000 on systems with many warning or critical events, which contain more information, increasing the Events database size. If the system has failed upgrades due to the Events database size or you are concerned that the Events is getting too large, remove older events. NOTE: For security reasons, events of type "Audit" cannot be deleted as other event types can. They are managed through the retention period setting. a. Save an offline CSV copy, using the Events Export button. b. Remove older events with the Events button. 4. Collect at least one support ticket. 10 Preparing for the software upgrade

11 The three latest tickets will be preserved after the upgrade. Download any other support tickets that you wish to retain. IMPORTANT: Allow the full support ticket to be collected prior to initiating a software upgrade. 5. If Data At Rest encryption has been applied to stores, back up the system configuration and keystore. Use the StoreOnce CLI config save devices and config save keystore commands. 6. Verify that warranty entitlement details have been updated correctly. Use the StoreOnce CLI command, system set warrantyserial. Customers will not be able to modify warranty details for StoreOnce Remote Support after the upgrade and will need to contact HPE Support. 7. If the system is using StoreOnce Remote support, disable remote event reporting during the upgrade process. system enable remoteeventsuppression "software update started" 8. Download the StoreOnce software. Verify that the software package downloaded correctly by comparing the MD5 value of the package with the MD5 value in the release notes. Preparing for the software upgrade 11

12 Upgrading StoreOnce software IMPORTANT: The upgrade from version 3.13.x converts the StoreOnce operating system and cannot be reversed. Prerequisites Verify that all prerequisites have been met, as described in Planning the software upgrade and Preparing for the software upgrade. 1. Transfer the upgrade package to the StoreOnce appliance 2. Update the StoreOnce software with the CLI 3. Verify that the software update was successful 4. Apply firmware updates 5. Complete the upgrade process Copying the upgrade package to the StoreOnce server In the following instructions: <Management IP Address> is the IP address normally used to log on to the StoreOnce GUI or CLI. <Package RPM> is the file name of the upgrade package RPM file. Using Linux 1. sftp IP Address> 2. cd repository 3. put <Package RPM> 4. exit sftp Using a Windows sftp client 1. Ensure the File Protocol is set to SFTP, not SCP or FTP. 2. Log in to the Management IP address as Admin. 3. Copy <Package RPM> to repository. 12 Upgrading StoreOnce software

13 Updating the StoreOnce software Use the StoreOnce CLI to update the StoreOnce software and log in as an Admin user. On a StoreOnce 6x00 system, enter the commands on the active node. IMPORTANT: When upgrading from 3.13.x, you will run the system update packages command twice. Between the two instances of this command, there is an additional manual step that ensures the existing configuration is stored safely before the upgrade runs and the underlying operating system is converted. NOTE: If you encounter an error during the upgrade process, see Troubleshooting the upgrade process on page 22. Prerequisites Prerequisites for StoreOnce 6x00 systems: Service sets are stopped and failover is disabled. Once the software upgrade has completed successfully, failover can be enabled manually. Service sets restart automatically. You are connected to the StoreOnce 6x00 system through a physical IP address. The system update packages command will fail if you are connected through the VIF address and the error message will display the correct IP address for login. 1. Log in to the SSH as an Admin User and run system show repository to list the rpm file you copied over. Verify that it is the correct file. 2. Distribute the package across all nodes in the cluster and unpack them. system load package <Package RPM> <Package RPM> is the filename of the upgrade package and is found in the release notes. 3. Verify that the packages are staged and ready for update. system show packages NOTE: The name of the package once it is loaded and unpacked is in the following format: Package Version State D2D_Master 3.1x.x-xxxx.x staged 4. On StoreOnce 6x00 systems, stop service sets and disable failover. 5. On all StoreOnce Systems, run system update packages. Updating the StoreOnce software 13

14 NOTE: To protect customer data, the upgrade utility will check the status of the Product Hardware, Service Sets, and Event Database size. If any elements are in a degraded or nonfunctional state, the upgrade utility will not carry out the requested software and\or firmware upgrades. If the upgrade utility will not upgrade the software or firmware, continue using the system with the existing software and contact HPE Support for further help. When upgrading from 3.13.x, the first time that this command is run, it creates and saves a saved_config.tgz file to the saved_config directory on the node that is running Active Fusion Manager. The upgrade process will automatically use this file to rebuild your configuration and data stores after the operating system has been converted. The system displays a series of messages. Saving the system configuration. Can take 20 minutes to complete. System configuration successfully saved. 18 minutes elapsed. Cleaning up old packages The OS conversion is not yet complete. Do not use the system for any other purpose until the update is complete. The current system configuration has been saved and it is available at /saved_config/saved_config.tgz Please use sftp to copy this off the system, save it and then run system update packages again. Your CLI session has expired. Please exit the current session and login again. IMPORTANT: HPE Support will be able to restore your system using this file if you encounter any problems with the subsequent upgrade. 6. When upgrading from 3.13.x only, save a copy of the configuration file and then run system update packages again. NOTE: When upgrading from 3.14.x or later, system update packages is only run once. a. Copy the saved_config.tgz file and its hashsum file from the saved_config directory to a safe location. Use sftp to copy the file and then use the hashsum file to verify the contents of saved_config.tgz. If the file is not visible, refresh your FTP client. b. Log back in to SSH as Admin user. c. Run system update packages for a second time to begin the process to upgrade and reboot all the nodes in the cluster. Service sets will restart automatically at startup. Required services started successfully. Saving the system configuration. Can take 20 minutes to complete. System configuration successfully saved. 4 minutes elapsed. Start reboot of the system. Processing,,, Broadcast message from root (Mon Xxx 13 16:52:18 20xx): 14 Upgrading StoreOnce software

15 System rebooting to complete the update process. The system is going down for reboot NOW! Update will complete after rebooting. SSh connection will be lost. Allow minutes for reboot to complete before reconnecting. # Connection to closed by remote host. Connection to closed. The StoreOnce System reboots and initiates the OS conversion, which completes automatically. 7. Verify that the update was successful. 8. Apply firmware updates 9. On StoreOnce 6x00 Systems only, re-enable failover. a. Run the StoreOnce CLI command system enable failover. b. Run the StoreOnce CLI command hardware show node status and verify that HA (failover) is reported as turned on for all nodes in the cluster. Stopping service sets and disabling failover (6x00 systems only) Stop service sets and disable failover before running system update packages. 1. Stop service sets using the StoreOnce CLI command serviceset stop all It might take several minutes for all service sets to stop. 2. Verify that all service sets have stopped. If service sets are still running, wait one minute and try again, until the status is Not Running. service show status The following example is from a two-node cluster. # service show status Service Set 1 Status Overall : Not Running Service Set 2 Status Overall : Not Running # 3. Disable failover by running the StoreOnce CLI command system disable failover. 4. Verify that HA (failover) is reported off for all nodes in the cluster by running the StoreOnce CLI command hardware show node status. Stopping service sets and disabling failover (6x00 systems only) 15

16 Verifying that the software update was successful Once access returns to the Management interface, verify that the process has completed successfully. Prerequisites The system has rebooted. NOTE: The update process can take up to 30 minutes for StoreOnce 6x00 Systems and up to 15 minutes for all other products. 1. Use the StoreOnce CLI command system show packages to verify that all packages are now installed, as well as staged. The output is in the following format: Package Version State D2D_Master <version> installed NOTE: When upgrading from 3.13.x, only the installed version is displayed. 2. On the StoreOnce GUI, verify that the software reversion number reported in the System Information details has updated to the software version listed in the release notes. 3. On the StoreOnce GUI, verify that the Event log has a software upgrade confirmation message (Event Code: E ). Update D2D_Master <version> completed successfully Applying firmware updates HPE recommends updating system firmware when updating StoreOnce software. You can use the StoreOnce GUI or the StoreOnce CLI to carry out this task. See the user guide for your product for information about using the StoreOnce GUI. Prerequisites This procedure does not apply to VSA. Use a supported web browser when using the StoreOnce GUI to run firmware management. Firmware management does not work with the Internet Explorer 8 web browser. Supported browsers include: Internet Explorer 9, 10 and 11 Mozilla Firefox v23 and above Firefox ESR24 and above 16 Verifying that the software update was successful

17 Refer to the user guide for your StoreOnce System for more details. If the system is using StoreOnce Remote Support, disable remote event reporting during the upgrade process, using the StoreOnce CLI command system enable remoteeventssuppression "firmware update started". Before updating all other components in the system, the Storage_Ctlr firmware must be at version 2.50 or higher. On StoreOnce version and later, you can update the firmware for all of the storage controllers, run the CLI command hardware update firmware Storage_Ctlr. Updating firmware for a multi-node system requires a coordinated reboot. Once the system has rebooted, update the firmware for the remaining components as required. Updating firmware from the StoreOnce GUI 1. Select Firmware to view the firmware versions for hardware components, and to update firmware versions if required. The Firmware window appears with the following tabs: Server: Contains firmware details for all server components. Storage: Contains firmware details for all storage components. Switch: Contains firmware details for all switch components on StoreOnce 6600 and 6500 systems only. 2. Click Scan to perform a check on the currently installed firmware versions for all components. This will populate the firmware tabs and may take several minutes to run. NOTE: The scan will fail if a firmware update is already in progress. 3. After you have run a Scan, the Recommended Action field in the component list is updated to show whether individual components require an upgrade or a downgrade. Components requiring an upgrade are automatically selected. A downgrade takes longer to complete and is optional for some components, such as hard drives. If downgrades are identified, the user may either select them to be included or decide to carry them out separately, if required, after the upgrade has completed. NOTE: When the firmware updates are initiated, the backup devices will be taken offline. Before performing this step, check that there are no outstanding backup jobs pending. IMPORTANT: Do not shut down or reboot your system or any system component until the final step. Special instructions may apply. Updating firmware from the StoreOnce GUI 17

18 4. Click Update Selected or Update All. (Update All will attempt to update all components that are in the state where there is an update recommended; it will not try to update components that do not need an update.) 5. The Status field will show which components are being updated and which updates have been completed 6. In some cases, when firmware has been loaded, you will need to perform a reboot to complete the firmware update. A pop-up message will appear on your GUI screen after loading is completed, if a reboot is required. The message will also advise what type of reboot is required. If a software reboot is needed, you will see a message asking if you want to reboot your system now or later. If you click Yes, your system will be rebooted. A power cycle, or cold reboot, requires that the system must be shut down for at least 60 seconds before powering on using the Power-On buttons on the appliance. A coordinated reboot is a corner case with StoreOnce 6600 and 6500 Systems and requires assistance from HPE Support. Updating firmware using the StoreOnce CLI 1. Run the StoreOnce CLI command to show the current status of firmware. # hardware show firmware <nodex storagex switch all> NOTE: X is the number of the node or storage to which the command should be applied. You must run the command for each component separately, but for the switch (only applicable to StoreOnce 6600 and 6500 Systems), the command lists or upgrades the firmware versions for all network switch components. 2. Check the Action column to see if any firmware needs upgrading. IMPORTANT: Do not shutdown or reboot your system or any system component until the final step. Special instructions may apply. 3. Use the hardware update firmware command, as required. The command syntax is: hardware update firmware <nodex storagex switch all> The all parameter updates all firmware components in parallel, in the sequence: switch, node, storage. If you use one of the other parameters, be aware that you must repeat the command for each node and storage component in your system. All switches are updated concurrently. There may be instances where replacement hardware may need a firmware downgrade to bring it in line with the supported firmware version of the installed StoreOnce software on the system being maintained. Use the force parameter in the command to enable this, but be aware that the update will take longer to complete. 18 Updating firmware using the StoreOnce CLI

19 IMPORTANT: Update the firmware on all nodes, storage components and switches before shutting down or rebooting the system. Please refer to Customer Notice c for full details on performing firmware upgrades on StoreOnce Systems. 4. In some cases, when firmware has been loaded, you will need to perform a reboot to complete the firmware update. A message is displayed in the CLI output after successful completion, if a reboot is required. The message will also advise what type of reboot is required. Reboot the system using the StoreOnce CLI command: system reboot Power down the nodes using the StoreOnce CLI command: system shutdown After the system has completely shut down, wait at least 60 seconds before powering on using the Power-On buttons on the appliance. A coordinated reboot is a corner case with StoreOnce 6600 and 6500 Systems and requires assistance from HPE Support. 5. On StoreOnce 6600 and 6500 Systems only, enable failover using the StoreOnce CLI command, system enable failover Completing the update 1. Clear the browser cache, enable TLS 1.1 or 1.2 in settings, and reopen the browser. 2. Collect a support ticket and save for future reference. 3. Back up the system configuration using the StoreOnce CLI command, config save devices. 4. If using encrypted VTL, NAS or StoreOnce Catalyst stores, back up the key configuration using the StoreOnce CLI command, config save keystore. 5. On AIX systems, reconfigure the StoreOnce Catalyst over FC port Host Emulation from Default to AIX in the StoreOnce GUI. Verifying the DNS configuration when using Remote Support 1. Update the Enterprise Server URL and verify the DNS configuration. The connection from StoreOnce to the HPE Secure Service Architecture has migrated. From To Completing the update 19

20 a. On the StoreOnce GUI page for Remote Support, ensure that the Enterprise Server URL is set to the new URL. b. Verify that the DNS server allows storage-support.glb.itcs.hpe.com to resolve to one of the following: storage-support1.itcs.hpe.com storage-support2.itcs.hpe.com c. For Outbound Connectivity (File transfer from StoreOnce to HPE), verify that port 443 (https) is open (outbound) between the StoreOnce IP and the following IP addresses: storage-support1.itcs.hpe.com storage-support2.itcs.hpe.com 2. Optionally re-enable event reporting. Remote event reporting will be re-enabled on reboot. If the system has not been rebooted, you can use the StoreOnce CLI command, system disable remoteeventsuppression "firmware update complete", or wait 24 hours for it to be automatically re-enabled. 20 Upgrading StoreOnce software

21 Finding StoreOnce documents in the HPE Information Library The latest product documentation is available in the StoreOnce Backup section of the Hewlett Packard Enterprise Information Library: 1. Navigate to 2. In Products & Solutions, select StoreOnce Backup. 3. In Models / Subcategories, select your product. 4. To filter the entries, select the types of documents and your language. Finding StoreOnce documents in the HPE Information Library 21

22 Troubleshooting the upgrade process 1. Read the error message. Hardware errors: A hardware component might have failed, an Ethernet connection has been disconnected, or the system is unable to discover storage. Software errors: There is a problem with service sets, file system, or replication. Firmware upgrade errors: Failover has not been disabled on a StoreOnce 6x00 system or a service set is in an error state. 2. Fix the highlighted issue. 3. Rerun the software upgrade. Package file is invalid error message Symptom Error message: > # system load packages > Command Failed - com.ibrix.ias.model.businessexception: Package file is invalid. Verify checksum > of downloaded package file. Cause You attempted to upgrade software using an invalid file. Action 1. Verify that you are using the RPM file that supports update from your system's current firmware version. StoreOnce software is delivered in multiple formats to suit different uses. When upgrading from 3.13.x to a 3.15.x or later version, the system will need the RPM that includes the operating system migration. 2. Download the correct StoreOnce software upgrade RPM file from the HPE website to your system and re-run the system load package using the correct RPM file. You attempted to upgrade from 3.14.x or 3.15.x using the incorrect (OS conversion) RPM file Symptom When running system update packages, the system reports the following error: # system load package HPE_StoreOnce_Software_Update_3.16.0_OS_Conversion_for_3.13.x_P9L rpm # system update packages Initializing. Verifying staged package repository integrity. Package stage area verification successful. Updating from version '3.13.x ' to '3.16.x-1707.xrb'. 22 Troubleshooting the upgrade process

23 Reboot will occur after update completes. Installing update tool packages. Can take 5 minutes to complete. node 1 : Installing: D2D_UpdateTools node 2 : Installing: D2D_UpdateTools ERROR node 1 : Install failed node 1 : Install completed with errors ERROR node 2 : Install failed node 2 : Install completed with errors Update tool package installation failed. 0 minutes elapsed. Update encountered system error(s) before starting the update. Cause HPE provides two upgrade packages for most StoreOnce software releases: one for upgrading from 3.13.x and another for upgrading from 3.14.x and later versions. This error is reported when the 3.13.x upgrade package is used on a system running 3.14.x or later software. NOTE: Due to a limitation of the 3.14.x software, the incorrect use of the OS conversion RPM is not detected by the system load package command, as is normally the case. Instead, the error becomes evident when the system update packages command is run and fails. Once upgraded to 3.15.x, any further attempt to use the OS upgrade RPM will be correctly detected and flagged as an error by the system load package command. Action Download the correct StoreOnce software upgrade RPM file from the HPE website and rerun the system load package command using the correct RPM file. You attempted to upgrade 3.13.x to 3.14.x or later using a normal (non-os conversion) RPM. Symptom When running system load packages, the system reports the following error. > # system load packages > Command Failed - com.ibrix.ias.model.businessexception: Package file is invalid. Verify checksum > of downloaded package file. Cause HPE provides two upgrade packages for most StoreOnce software releases: one for upgrading from 3.13.x and another for upgrading from 3.14.x and later versions. This error is reported when the 3.14.x and later upgrade package is used on a system running 3.13.x software. Action Download the correct StoreOnce software upgrade RPM file from the HPE website and rerun the system load package using the correct RPM file. You attempted to upgrade 3.13.x to 3.14.x or later using a normal (non-os conversion) RPM. 23

24 When upgrading from 3.13.x to a release that does not have an OS conversion RPM, upgrade to an intermediate version first. You must be running or greater Symptom When running system update packages, the system reports the following error: > # system update packages Initializing. Verifying staged package repository integrity. Package stage area verification successful. Updating from version ' ' to ' rb'. Reboot will occur after update completes. Installing update tool packages. Can take 5 minutes to complete. node 1 : Installing: D2D_UpdateTools node 2 : Installing: D2D_UpdateTools node 1 : Install successful node 2 : Install successful Update tool package installation successful. 0 minutes elapsed. Updating from version ' ' to ' rb'. Reboot will occur after update completes. > ERROR You must be running or greater in order to update to Removing update tools packages. Update encountered system error(s) before starting the update. NOTE: The versions in the error message differ for each RPM. Cause The system is not running a software version supported by this RPM file. Action 1. Update the StoreOnce software to at least the minimum version specified in the error message. 2. Update the StoreOnce software to the current version. Discovered GB to be added Symptom After upgrading from 3.13.x, the output of the StoreOnce CLI command system show status shows a small amount of Discovered GB to be added. Cause The storage is reported incorrectly after the upgrade. 24 You must be running or greater

25 Action Run the StoreOnce CLI command hardware add storage to clear up this incorrect storage reporting. Some support tickets are empty when downloaded Symptom After upgrading from StoreOnce 3.13.x, support tickets older than the last three generated are empty, when downloaded. Cause Only the three most recent support tickets are retained by the upgrade process. Action Delete older tickets that are 0 KB in size and no longer contain any log data to download. Firmware update for FC HBA Updates not attempted Symptom Firmware update returns error Updates Not Attempted when the FC HBA component updates from version FW to FW Cause The firmware version currently installed on the FC HBA cannot be updated automatically. Action Using the StoreOnce CLI, run hardware update firmware FCHBA force. Some support tickets are empty when downloaded 25

26 StoreOnce websites Hewlett Packard Enterprise Information Library for StoreOnce products HPE Data Availability, Protection and Retention (DAPR) compatibility matrix HPE StoreOnce Systems QuickSpecs HPE StoreOnce Data Protection Backup Appliances information page General websites Storage white papers and analyst reports Enter "StoreOnce" into the keyword search box. For additional websites, see Support and other resources. 26 StoreOnce websites

27 Support and other resources Accessing Hewlett Packard Enterprise Support For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: Information to collect Technical support registration number (if applicable) Product name, model or version, and serial number Operating system name and version Firmware version Error messages Product-specific reports and logs Add-on products or components Third-party products or components Accessing updates Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method. To download product updates: Hewlett Packard Enterprise Support Center Hewlett Packard Enterprise Support Center: Software downloads Software Depot To subscribe to enewsletters and alerts: To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: Support and other resources 27

28 IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements. Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR. For more information about CSR, contact your local service provider or go to the CSR website: Remote support Remote support is available with supported devices as part of your warranty or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product's service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support. If your product includes additional remote support details, use search to locate that information. Remote support and Proactive Care information HPE Get Connected HPE Proactive Care services HPE Proactive Care service: Supported products list HPE Proactive Care advanced service: Supported products list Proactive Care customer information Proactive Care central Proactive Care service activation Warranty information To view the warranty for your product or to view the Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products reference document, go to the Enterprise Safety and Compliance website: 28 Customer self repair

29 Additional warranty information HPE ProLiant and x86 Servers and Options HPE Enterprise Servers HPE Storage Products HPE Networking Products Regulatory information To view the regulatory information for your product, view the Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center: Additional regulatory information Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our products as needed to comply with legal requirements such as REACH (Regulation EC No 1907/2006 of the European Parliament and the Council). A chemical information report for this product can be found at: For Hewlett Packard Enterprise product environmental and safety information and compliance data, including RoHS and REACH, see: For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see: Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page. Regulatory information 29