StoreOnce Backup software revision (P9L ) release notes

Transcription

1 StoreOnce Backup software revision (P9L ) release notes Abstract This document describes the StoreOnce Backup software release, P9L rpm. This software is a mandatory upgrade for customers wishing to take advantage of the fixes. This release incorporates all features from the earlier 3.13.x releases. Part Number: BB Published: September 2016 Edition: 1

2 Description This document outlines the functional changes and defect fixes for HPE StoreOnce Backup software in the software release, P9L rpm. This software revision contains enhancements and fixes. Update recommendation Update recommendation: StoreOnce is valid for all HPE StoreOnce Backup systems in Product models. It is a MANDATORY upgrade for most users. IMPORTANT: New D6000 enclosure 7.12 firmware for StoreOnce 4900 and 6500 to support 12 Gbps SAS hard drives (MB4000JFEPB only): New 7.12 firmware provided in the StoreOnce software release for the D6000 enclosure enables support for the new 12 Gbps SAS hard drives that will be replacing the current 6 Gbps SAS hard drives. Supersedes information Supersedes: StoreOnce software. In order to upgrade to software you should first be running , , , or software or one of the two previous software versions: 3.12.x and 3.11.x. If you are running older software than 3.11.x, you must update to StoreOnce (or the latest available version of 3.11 software) first. For example, StoreOnce VSA users may not upgrade directly from StoreOnce VSA 3.7.x to 3.12.x or later; they must first upgrade to StoreOnce Product models The software release is applicable to the following product models: BB910A: HPE StoreOnce 2900 Backup BB896A: HPE StoreOnce 6500 Backup EJ022A: HPE StoreOnce B6200 Backup BB903A: HPE StoreOnce 4900 Backup BB877A: HPE StoreOnce 2700 Backup BB878A: HPE StoreOnce 4500 Backup BB879A: HPE StoreOnce 4700 Backup HPE StoreOnce 2610 iscsi Backup system BB852A: HPE StoreOnce 2620 iscsi Backup system BB853A: HPE StoreOnce 4210 iscsi Backup system BB854A: HPE StoreOnce 4210 FC Backup system BB855A: HPE StoreOnce 4220 Backup system BB856A: HPE StoreOnce 4420 Backup system BB857A: HPE StoreOnce 4430 Backup system TC458A/AAE: HPE StoreOnce VSA 10 TB 3 Year Software LTU/E-LTU D4T77A/AAE: HPE StoreOnce VSA 4 TB 3 Year Software LTU/E-LTU D4U47A/AAE: HPE StoreOnce VSA 50TB 3-year LTU/E-LTU 2 Description

3 D4U49A/AAE: HPE StoreOnce VSA 4TB 5-year LTU/E-LTU D4U62A/AAE: HPE StoreOnce VSA 10TB 5-year LTU/E-LTU D4U48A/AAE: HPE StoreOnce VSA 50TB 5-year LTU/E- LTU P9L02A/AAE: HPE StoreOnce VSA 4TB LTU/E-LTU P9L03A/AAE: HPE StoreOnce VSA 10TB LTU/E-LTU P9L04A/AAE: HPE StoreOnce VSA 20TB LTU/E-LTU P9L0?A/AAE: HPE StoreOnce VSA 32TB LTU/E-LTU P9L05A/AAE: HPE StoreOnce VSA 50TB LTU/E-LTU NOTE: The HPE StoreOnce 2610 iscsi Backup system is only available as a conversion from an existing HPE D2D2502 Backup system, so has no product number. Operating systems Languages This release is supported on: Cross operating system (BIOS, Firmware, Diagnostics, etc.) Languages supported for this release: English Japanese Chinese French German Brazilian Portuguese Russian Spanish Features and enhancements None Fixes with software There is new component firmware to resolve an issue that caused the 10GbE NIC ports to go offline after upgrading the 10GbE NC550/552 Ethernet Card to firmware. HDDs MB1000FCWDE/MB2000FCWDF/MB3000FCWDH/MB4000FCWDK models update to HPDA. NOTE: This is an important upgrade to improve reliability and reduce faults that may occur more frequently on HDDs running earlier firmware versions. There was a scenario, where a customer using Commvault with StoreOnce NAS CIFS shares failed to read files from the shares using Windows Explorer. This has been fixed. There is a new Fibre Channel driver with stability fixes. The new driver improves the robustness of Catalyst over Fibre channel connectivity in StoreOnce appliances. Filesystem stability fixes have been implemented. Operating systems 3

4 Improvements have been made to the handling and logging of failover on StoreOnce B6200 and StoreOnce 6500 appliances. There was an issue within the StoreOnce dedupe engine where, in some instances, backup jobs failed due to a write error. No data corruption occurred but the write session failed. This has been fixed. There is improvement on dedupe ratio when multiple replication seeding streams operation is performed on a new target store. A non-critical issue has been identified where the StoreOnce Event log may occasionally report NAS metadata CRC checksum errors related to a dormant feature that is not used by the StoreOnce system. These events are false positives and the issue is fixed in this StoreOnce software release. Known Issues and customer advisories To find the most current product advisories and bulletins: 1. Go to 2. Select HPE Servers, Storage and Networking under Product Support. 3. Enter your product name (StoreOnce) in the search box under Get drivers, manuals, parts & solutions. 4. Navigate to your specific product, if given additional product choices. 5. Select the Top Issues & Solutions tab. 6. Click Advisories, bulletins & notices in the right column. HPE recommends that you register your product for HPE Support Alerts at: e-updates. After registering, you will receive notification of product enhancements, new driver versions, firmware updates, and other product resources. Known issues Blackout and Bandwidth Limiting Windows Start and End of Restriction times are in UTC: An issue has been identified in the StoreOnce GUI pages for configuring StoreOnce Catalyst, Replication and Housekeeping Blackout and Bandwidth Limiting Windows where the Start and End of Restriction times are set and displayed in UTC instead of the locally selected timezone. This issue will be fixed in a future StoreOnce software release. Intermittent errors when using SMB Signing with NAS CIFS shares: A known issue exists where some customers using Signed SMB communication may experience loss of connection to the NAS CIFS share. This occurs for some unique configurations where the StoreOnce System incorrectly responds with a single unsigned packet during communication, forcing the client to terminate the session. Customers wishing to use SMB Signing should call HPE Support for assistance. This will be fixed in a future StoreOnce software release. NC550/NC552 10GbE Ethernet Card update to Firmware: On systems where VLAN subnets are configured on the 10GbE ports, the 10Gb NIC ports does not come back online after the firmware upgrade. Contact HPE Support. NOTE: HPE StoreOnce 6500 and B6200 Backup systems with five or more VLANs can experience this issue. IPv4 default gateway is not set up correctly on HPE StoreOnce 6500 and B6200 Backup systems: With StoreOnce software and later the default IPv4 gateway cannot be configured on a VLAN subnet for HPE StoreOnce 6500 and B6200 Backup systems. This will be addressed in a later software release and does not apply to single-node systems. Access to CIFS shares lost: In some rare corner cases CIFS shares could become inaccessible. To address this, restart the CIFS services on the node. 4 Known Issues and customer advisories

5 Recovery Manager Central (RMC) compatibility: The StoreOnce code is not compatible with RMC version 1.2 and below; use RMC version 1.21 or later. This will be resolved with future RMC releases. HP Autonomic Backup Restart IBM TSM VTLs fails after initiating service set failover: This may be a problem with the Tape driver. Please contact your HPE Account Representative for IBM Solution Documentation on supported HPE StoreOnce Configurations. HyperV RPM Update failed: ERROR User Events database is large: It is always recommended to check the Event Database size in the StoreOnce GUI on the Events page before upgrade. Upgrades may fail when the number of events is greater than 50,000. To reduce the number of events use the Delete button in the GUI to remove older events and reduce the number to less than 48,000. Static routing with StoreOnce 6500 and B6200: Do not use the static routing feature if you are using a data and management subnet on the same portset. Domain name resolution with StoreOnce Federated Catalyst: When configuring systems for StoreOnce Federated Catalyst HPE recommends using direct IP addresses rather than Fully Qualified Domain Names as some customers have experienced issues with name resolution. Problems with firmware update process after the network cards or the storage controllers firmware has been updated. This impacts all StoreOnce Backup models except Storeonce VSA. Shut down the system and leave it in this state for at least 1 minute. After this time has expired power back the system. Updating the P2000 MSA firmware TS240P001 to TS251P005 can fail due to a failed Compact Flash card. Contact HPE Support. warrantyserial command execution error when restoring from the config file: With StoreOnce software, the format for the StoreOnce CLI command has been changed to system set warrantyserial, and the command accepts only entitlement. With earlier software versions there were four valid parameters, server, storagemsa, driveenclosure, networkswitch. A config file, created using the config save devicescommand prior to software version , will contain the warranty serial information for these four components, and a warrantyserial command execution error will occur if the same config file is used for restore with StoreOnce software or later. Remote Support Entitlement: Both the StoreOnce CLI and GUI now display server warranty entitlement only. StoreOnce B6200: If the customer has previously entered the warranty serial number for the server only, the software will continue to use the same number for server, storage and switch attached to the server, if the customer has previously entered different warranty serial numbers for storage and switch, they will no longer be displayed. StoreOnce 6500: The software will either use the warranty serial number, if it can find it in the system, or the customer entered value. No data is lost if the customer entered value was the same for server, storage and switches. If the customer had entered different values for server, storage and switch, it was invalid and is no longer displayed. StoreOnce 2700, 2900 and 4500: The software upgrade is able to extract the correct warranty serial number from the system and uses that. If the customer had entered warranty details for storage, these are no longer displayed. StoreOnce 4700 and 4900: The software upgrade uses either the warranty serial number from the system, if available, or the customer-entered serial number. Any storage details are no longer displayed. Known Issues and customer advisories 5

6 IMPORTANT: No longer exposing the previously entered switch or storage information does not impact any functionality of the system; it is just simplifying the process from a customer perspective. The same entitlement will be provided. NOTE: Remote Support is not available for StoreOnce 2620, 4210, 4220, 4420, 4430 or VSA. StoreOnce Catalyst store items created with 3.11.x software require HPE Support assistance for Federated Store expansions in 3.12.x and later: An issue has been discovered with StoreOnce Catalyst store items created with 3.11.x where after upgrading to or and expanding to a larger Federated Catalyst store, the items created from 3.11.x will no longer be visible or accessible and HPE Support assistance will be required to correct. This issue only occurs for 3.11.x created items and only if the store is Federated Catalyst expanded in or As of checks are in place to detect affected items and prevent store expansions, however customers will still need to contact HPE Support to resolve the issue and enable Federated Catalyst expansions for affected stores. Unable to configure networking or show/update firmware after upgrading to 3.11.x or later on StoreOnce 6500 and B6200 systems: An issue has been discovered on StoreOnce 6500 and B6200 systems upgraded to 3.11.x, or where activating a new network configuration may fail or the firmware show/update commands may error with the message cannot execute this command. System is busy querying firmware version. Please try again later. These issues are due to a mismatch between the reported and expected numerical identifiers for the nodes, causing these dependent command operations to fail. As of the software upgrade process will detect and report the error and abort the upgrade if found. Customers with the issue should seek assistance from HPE Support to resolve. StoreOnce B6200 GUI and CLI report missing or failed IO cache modules after firmware updating or power cycling the P2000 Storage: An issue has been identified with some B6200 systems where the CompactFlash cards used in the P2000 storage may become disabled after power-cycling the controllers or performing a firmware update. When this issue occurs the P2000 storage will remain operational but with reduced performance. This issue is due to a specific model of CompactFlash card, which was discovered to have a fault, and may be present in some B6200 systems. Contact HPE Support, who will help to replace the CompactFlash card with HPE part number Reporting Central Reports may not generate using an end date equal to the current date: When using Reporting Central s custom range feature, selecting an end date equal to the current date can result in an error preventing the generation of the report. Reports using the pre-selected ranges will generate the current date values correctly and a fix for this issue will be available in a future software release. HPE StoreOnce 2900 Backup capacity reporting: Unlicensed capacity is reported incorrectly for the HPE StoreOnce 2900 Backup. This does not impact the capacity available after a successful license addition and storage expansion. Domain names with more than 4 characters cannot be used when configuring the server on the StoreOnce GUI: server domain names with top-level domains more than 4 characters long, such as ".local", will fail validation at the configuration screen and cannot be entered. A workaround can be used where the server IP address is entered instead. This behavior will be corrected in a future software release. Unable to add an external user to the AD domain (HPE 6500 and HPE B6200 only): When adding external users in User Management, ensure that all service sets in the cluster have been joined to the Active Directory domain in the NAS CIFS server settings. If all the service sets have not been joined to the Active Directory domain, addition of external users may fail or any previously added external users may not be available. 6 Known Issues and customer advisories

7 A "Please Wait" message displays when viewing Federated StoreOnce Catalyst stores: Following a failover, if the StoreOnce Catalyst stores page of the StoreOnce GUI is opened and there are Federated StoreOnce Catalyst stores configured, a pop up box with the message "Please Wait" may appear and never disappear unless the StoreOnce GUI times out or the browser is refreshed. This will be fixed in a future release. SNMP traps not sent to trap receiver: If the StoreOnce SNMP appliance is set up with SNMPv3 or with an IPv6-only network configuration, no traps may be sent to the trap receiver. This will be fixed in a future release. All items in the search list for host name lookup may not be checked for a host name match: If an HPE StoreOnce system is configured to obtain DHCPv6 addresses, any domains that have been statically defined by the user may be ignored in favor of the domains specified by the DHCPv6 server. It is strongly recommended that the domain name is specified even when configuring a DHCPv6 subnet. This will be fixed in a future release. Failure to acquire DNS and domain name information from DHCPv6 Server: (Single-node StoreOnce platforms only, not StoreOnce 6500 and B6200) DNS Server and domain name information will not be acquired in the following Subnet configuration: VLAN Tag Enabled Subnet configured, addressing mode set to DHCP with the expectation of acquiring IPv6 address details, and DHCPv6 Server is running on a Windows Server operating system. In this configuration it is possible to manually provide the DNS Server and domain name that should have been acquired via DHCPv6. StoreOnce Catalyst over Fibre Channel is currently not supported on SUSE Enterprise Linux 11 SP3. Only Service Pack 2 and lower are supported. Setting a quota in the replication wizard is not possible: When configuring VTL and NAS Replication mappings it is not currently possible to set a quota within the Replication wizard. Where quotas are required on a Replication target it is necessary to set the quota after the target VTL or NAS creation, or create the VTL or NAS targets before launching the Replication wizard. Quotas with StoreOnce Federated Catalyst: StoreOnce Federated Catalyst stores that reach their quota limit will fail a Catalyst backup as expected but the Federated Catalyst store will not be set to a Warning state within the StoreOnce GUI. This only affects StoreOnce Federated Catalyst stores. (52042) StoreOnce VSA and network link connection speed: The StoreOnce VSA GUI and the StoreOnce CLI command, net show status all, report the network link connection speed as 1GbE, although the physical link speed is 10GbE. This is a known issue in the reporting of the network status. StoreOnce VSA does support a 10GbE network link. Hardware component Unavailable with message Failed to get Hardware report object: Hardware report is invalid format : In the rare scenario where a hardware component contains a sub-component with a serial number with a non-printable Unicode character, the internal XML parser will fail to parse the hardware report and the hardware components will fail to display in either the GUI Hardware tree or the StoreOnce CLI commands, hardware show. The faulty hardware component must be identified and replaced by an HPE Support engineer. Manual offline firmware update required for StoreOnce B6200 storage hard drives: Due to a known issue with the P2000 G3 MSA whereby the required zero I/O to the hard drives is not guaranteed whilst connected nodes are online, it is necessary to use the manual process of updating the hard drive firmware over Ethernet connection to the P2000 G3 MSA with the nodes shutdown. This must be performed by a qualified HPE Support engineer. For more information see and StoreOnce B6200 storage Enclosure_IO_Mod firmware does not get upgraded when the Storage Controller firmware is up to date: The checks to run the Smart Component firmware upgrade package, which updates both the Storage Controller and the Enclosure IO Module in the P2000 controller shelf, only test the firmware status of the Storage Controller and not both. Known Issues and customer advisories 7

8 To overcome this issue, use the force option with the StoreOnce CLI command, hardware update firmware storagex force. NAS shares with over 25,000 files may take a long time to start after an ungraceful power off: After an ungraceful power off NAS shares containing over 25,000 files may take a noticeably long time to start whilst the StoreOnce Backup system re-initializes. This is because, after an ungraceful shutdown, the StoreOnce Backup system needs to rebuild its record of the content on the NAS share by reading each file. The time required is directly dependent on the number of files on the share; it has been seen to take approximately 2 hours to re-initialize a share containing 100,000 files. Performance considerations with Secure Erase: Secure Erase is intended to be used in scenarios where the user wishes to securely delete small amounts of highly sensitive data from the StoreOnce appliance. It is not recommended to keep Secure Erase turned on for an extended period of time or even permanently. Doing this can have a severe impact on the performance of the appliance. Securely Erasing an entire VTL, NAS share or Catalyst store can take several hours or even days depending on the amount of data stored in the device. Backup, recovery, copy or replication jobs may be impacted due to the increased I/O as a result of the Secure Erase. Minimum firmware K m required to upgrade B6200 switches from the StoreOnce CLI: Due to a known issue with B6200 switch firmware below K m where the SSH session may disconnect while copying the new firmware image to the switch, B6200 switches (HP ProCurve 6600) must be manually updated to minimum firmware K m. For information about downloading the latest K xxxx firmware refer to km/saw/view.do?docid=emr_na-c Minimum firmware required on 10GbE NICs before upgrading to or later: For StoreOnce 4420, 4430, 4500, 4700, 4900, B6200 and 6500 Backup systems, the 10GbE network cards must have minimum firmware before upgrading to StoreOnce software or later as the updated 10GbE drivers in and later will not work with firmware below , and the 10GbE interfaces will not be operational. To upgrade the 10GbE NIC firmware the OFFLINE Firmware image (.iso) for HP Emulex NC550/NC552 Network Adapters must be used. This can be obtained from Storage name incorrect or displays Uninitialized Name, HPE StoreOnce B6200 only: The new hardware reporting mechanism implemented in 3.11.x for the StoreOnce B6200 Backup system utilizes the System Name value set in the P2000 controllers for storage reporting. This value is normally set in manufacturing, however, if the controllers have been replaced after shipping, the values in the new controllers may not have been reset correctly. The StoreOnce 3.11.x software does not currently check or reset the System Name value in the P2000 controllers. This issue does not affect the functionality of the StoreOnce B6200 Backup system. Symantec NetBackup LSU spanning fails with HPE StoreOnce Catalyst stores and OST Plugin: The NetBackup LSU spanning feature is not supported or recommended with HPE StoreOnce Catalyst stores and OST Plugin. This is due to a lack of NetBackup support for asynchronous write operations, which are utilized by HPE StoreOnce Backup systems. Software upgrade 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: backup, restore, StoreOnce Catalyst Copy, Replication and housekeeping. 8 Software upgrade prerequisites

9 Considerations before upgrading The StoreOnce release contains the following HPE rebranding change that existing customers are advised to consider before upgrading: Remote Support Enterprise Server URL change: The connection from the StoreOnce to the HPE Secure Service Architecture has migrated from to This is an automatic change to the URL, but it may be necessary to modify your firewall to reflect the new URL. For details, see To complete the update (all models) (page 16). Maintenance window required To perform the StoreOnce software upgrade a maintenance window is required in which the unit will be unavailable for normal operations. When scheduling the maintenance window, please use the following as guidelines of a typical amount of time that the upgrade will take: For StoreOnce VSA products, the entire upgrade process is expected to take 30 minutes. For StoreOnce single-node products, the entire upgrade process is expected to take up to 2 hours, depending on your hardware configuration. The software upgrade is expected to take 40 minutes. A further minutes is required to perform necessary hardware firmware updates. For StoreOnce multi-node products, the entire upgrade process is expected to take between 3 hours and 10 hours, depending on your hardware configuration. The software upgrade is expected to take 50 minutes. A further 2 hours per couplet is required to perform necessary hardware firmware updates. NOTE: This assumes that the software currently on the StoreOnce product is the current latest available, and all previous firmware updates have been implemented. If you are upgrading from an earlier release, please add an additional 25% to the values above. Optional hardware and system status checks To protect Customer data, the upgrade utility will check the status of the Product Hardware and Service Set(s). If any elements are in a degraded or non-functional state, the upgrade utility will not carry out the requested software and\or firmware upgrade(s). For improved confidence that the update will be successful when run, the Product Hardware and Service Set(s) checks can be run manually before attempting the upgrade. Hardware status To check hardware status run the StoreOnce CLI command, hardware show problems. If any of the hardware, except HBA_Port, shows a status of removed, failure/failed, down/offline, the upgrade will be blocked. 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. If there are warnings or errors reported on any of the hardware the details can be found by running 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. Software upgrade prerequisites 9

10 NOTE: You can also check the Hardware page on the StoreOnce GUI and drill down to the failed item. Read the Diagnostic messages for the failed hardware and ensure the problem is rectified before attempting an upgrade. Service set status Pre-upgrade actions To check the service set status run the StoreOnce CLI command, serviceset show status. A typical example of the output of this command is shown below: # serviceset show status 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 / Running, upgrades will fail. Perform the following actions immediately before starting the software update process to ensure a smooth update process: 1. Reboot the system with the StoreOnce CLI command, system reboot. For StoreOnce 6500 and B6200 systems, disable failover first with the StoreOnce CLI command, system disable failover, and then perform system reboot. This ensures the system is in as clean and clear a state as is possible before the software upgrade. 2. Check the size of the Event database. To check the Events database size, look it up in the StoreOnce GUI on the Events page, where the count is displayed at the top. We have seen some upgrades fail when the number of events is greater than 50,000. This is not an exact figure and can be as low as 30,000 on some systems that have had a large number of warning or critical events, which contain more information and increases the Events database size. Customers experiencing failed upgrades due to the Events database size are advised to use the Export button to save an offline CSV copy of the All Events and then use the Delete button to remove older events to reduce the size of the Events database. NOTE: For security reasons, events of type "Audit" cannot be deleted as other event types can. They are managed through the retention period setting. 3. Collect a support ticket and save for future reference. IMPORTANT: upgrade. Please allow the full support ticket to be collected prior to initiating a software 4. For StoreOnce B6200, check the switch firmware using StoreOnce CLI command hardware show firmware switchx and, if required, please contact HPE Support to manually offline-upgrade to minimum version K m. 5. For StoreOnce 4420, 4430, 4500, 4700, 4900, B6200 or 6500, check all 10GbE network card firmware using StoreOnce CLI command hardware show firmware nodex and, if required, please contact HPE Support to manually offline-upgrade to minimum version Software upgrade prerequisites

11 6. Make sure that you are using one of the supported web browsers for accessing the StoreOnce Management GUI: Internet Explorer 9, 10 and 11 (note that Internet Explorer 8 is not supported and some StoreOnce features will not work with StoreOnce software version and later) Mozilla Firefox v23 and above, and Firefox ESR24 and above 7. Back up the system configuration and keystore, if Data At Rest encryption has been applied to stores. Use the StoreOnce CLI commands, config save devices and config save keystore. 8. If you are using StoreOnce Remote Support, disable remote event reporting during the upgrade process, using the StoreOnce CLI command, system enable remoteeventsuppression "reason". Software upgrade installation instructions (all products) Download and SFTP the upgrade package Download the upgrade package from the HPE Support web site, or from the HPE Software Depot To download the latest version of the StoreOnce software upgrade package, go to the Software Depot at and search for StoreOnce Backup System Software. To ensure the integrity of your download, HPE recommends verifying your results with this MD5 Checksum value: Checksum value fa2aff17fbaf19af05c1bd80b54aab1e Filename P9L rpm sftp the package to the software repository (all products) sftp the upgrade package P9L rpm to the software repository on the StoreOnce appliance. NOTE: In the following instructions, where the term Management IP address is used, this is the IP address that you normally use to log on to the StoreOnce GUI or CLI. Using Linux sftp Admin@<Management_IP Address> cd repository put P9L rpm exit sftp Using a Windows sftp client Ensure the File Protocol is set to SFTP, not SCP or FTP. Login to the Management IP address as Admin. Copy P9L rpm to repository. Software upgrade installation instructions (all products) 11

12 Update the software (all products) Software upgrade with HPE StoreOnce 6500 and B6200 Backup only: Run the StoreOnce CLI software update commands NOTE: If updating an HPE StoreOnce 4900, 4700, 4500, 2900 or 2700 Backup system, an HPE StoreOnce 4430/20, 4220/10 or 2620/10 Backup system or a StoreOnce VSA system, see the next section. To ensure smooth running of the software upgrade process, HPE recommends that the HPE 6500 or B6200 Backup system has service sets stopped and failover disabled prior to the upgrade. Once the software upgrade has completed successfully, failover should be manually turned back on. Service sets restart automatically. The status of failover can be checked using the StoreOnce CLI command: hardware show node status. The value shown in the HA (high availability) column indicates whether failover is on or off for the relevant node. Log in and enter the following StoreOnce CLI commands on the active node of the HPE 6500 or B6200 Backup system: 1. Log onto the physical IP of the node on which the update is to be run, do not use the Management VIF address. You cannot update software from the Management VIF address. If you are not logged on to the active node, the command will fail at step 7 as follows: # system update packages Cannot run 'system update packages' when logged in via the management VIF IP address. Please log in using the address X.X.X.X 2. Run system show repository which should list out the rpm file you copied over 3. Run system load package P9L rpm which, in the case of the HPE 6500 or B6200 Backup system, will distribute the package across all nodes it can communicate with and unpack them 4. Run system show packages which will show you the packages staged ready for update NOTE: The name of the package once it is loaded and unpacked is in the following format: Package Version State D2D_Master staged 5. Run serviceset stop all to stop service sets and ensure that no jobs are running. It may take several minutes for all service sets to stop. service show status to verify that all service sets have stopped. If they are still running, wait one minute and try again, until the status is Not Running. The following example is from a 2-node cluster. # service show status Service Set 1 Status Overall : Not Running Service Set 2 Status Overall : Not Running # 6. Run system disable failover to turn off failover (HA) Followed by hardware show node status to check that HA (failover) is reported as off for all nodes in the cluster 12 Software upgrade installation instructions (all products)

13 7. Run system update packages which will begin the process across all nodes to upgrade and reboot the nodes. Service sets will restart automatically at start up. NOTE: To protect Customer data, the upgrade utility will check the status of the Product Hardware, Service Set(s) and Event Database size. If any elements are in a degraded or non-functional state, the upgrade utility will not carry out the requested software and\or firmware upgrade(s). if this happens, please use the system with the old software and contact HPE Support for further help. 8. Once upgrade is in progress it will reboot the nodes. Wait for the upgrade to complete successfully, then run system enable failover to re-enable failover (HA) Followed by hardware show node status to check that HA (failover) is reported as turned on for all nodes in the cluster 9. Check that update was successful as described in To check that update is successful (all systems) (page 13). Software upgrade with HPE StoreOnce 4900, 4700, 4500, 2900 and 2700, HPE StoreOnce 4430/20, 4220/10 and 2620/10, and VSA Backup only: Run the StoreOnce CLI software update commands NOTE: If updating an HPE StoreOnce 6500 or B6200 Backup system, see the previous section. Enter the following CLI commands: 1. system show repository which should list out the rpm file you copied over 2. system load package P9L rpm to load and unpack the package: 3. system show packages which will show you the packages staged ready for update. NOTE: The name of the package once it is loaded and unpacked is in the following format: Package Version State D2D_Master staged 4. system update packages which will begin the process and upgrade and reboot the system 5. Check that update was successful as described in To check that update is successful (all systems) (page 13). To check that update is successful (all systems) Wait for the system to reboot. NOTE: Depending upon the updates, this could take could take 50 minutes or longer for HPE 6500 or B6200 products and 10 minutes or longer for all other products. Once access returns to the Management interface, check that the process has completed successfully, as follows: From the StoreOnce CLI: Use system show packages to check that all packages are now installed, as well as staged. The output should be in the following format: Package Version State D2D_Master installed D2D_Master staged From the GUI: Check the System Information details on the StoreOnce screen, to ensure that the software revision number has updated to the software version. From the GUI: Check the Event log for a confirmation message of the software upgrade: Update D2D_Master completed successfully. Software upgrade installation instructions (all products) 13

14 Run the firmware management tools (all products apart from VSA) It is important to check whether firmware updates should be applied after each software update. This is typically necessary for all StoreOnce hardware configurations. It is not necessary with, nor supported on, StoreOnce VSA. We have used the StoreOnce CLI in these release notes to illustrate the firmware upgrade process, but you can also use the StoreOnce GUI to carry out this task, if preferred. See the user guide for your product for information about using the StoreOnce GUI. NOTE: When using the StoreOnce GUI to run firmware management, please note that this tool does not work with the Internet Explorer 8 web browser; you must use a supported browser (Internet Explorer 9, 10 and 11, or Mozilla Firefox v22 and above and Firefox ESR24 and above). Refer to the user guide for your HPE StoreOnce Backup system for more details. Firmware update with HPE StoreOnce 6500 and B6200 Backup 1. Run the StoreOnce CLI command to show the current status of firmware # hardware show firmware <nodex storagex switchx> 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 step 6. Special instructions may apply. See step 6 for details. 3. Before upgrading firmware, stop service sets. serviceset stop all to stop service sets and ensure that no jobs are running. It may take several minutes for all service sets to stop. service show status to verify that all service sets have stopped. If they are still running, wait one minute and try again, until the status is Not Running. # service show status Service Set 1 Status Overall : Not Running Service Set 2 Status Overall : Not Running # NOTE: The above example is from a StoreOnce 6500 or B6200 Backup with 2 service sets. 4. Disable failover using the StoreOnce CLI command: system disable failover. IMPORTANT: You must disable failover using the StoreOnce GUI or CLI command before starting the upgrade process. 5. Use the hardware update firmware <nodex storagex switchx> force CLI command, as required. For example, 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. Specify the node, storage or switch and repeat the command for each node, storage and switch in your system. IMPORTANT: With the HPE StoreOnce 6500 or B6200 Backup you must 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 6500 and B6200 Systems. 14 Software upgrade installation instructions (all products)

15 NOTE: If using the StoreOnce GUI to upgrade firmware, be aware that Update All will only update all components of the selected node/service set. 6. After the firmware has updated, the StoreOnce Management Console (GUI or CLI) will report if components have been updated that require a cold reboot. Perform a cold reboot as follows: Power down the node(s) using the StoreOnce CLI command: system shutdown After the system has completely shut down, wait at least one minute before powering on using the Power On button on the server(s). NOTE: If a cold reboot is not required, it is acceptable to reboot the system using the StoreOnce CLI command: system reboot 7. Once the system has successfully rebooted, enable failover using the StoreOnce CLI command, system enable failover Firmware Update with HPE StoreOnce 4900, 4700, 4500, 2900 and 2700, HPE StoreOnce 4430/20, 4220/10 and 2620/10 IMPORTANT: For HPE StoreOnce 2620/42xx/44xx Backup, the Firmware Management Tool will not cover all of the required updates to bring all StoreOnce firmware components to the correct level. After performing a software upgrade and using the online firmware management tool, you must apply the firmware using the support pack that updates the firmware offline. Instructions on how to perform the offline update can be found in the support pack release notes. 1. Run the StoreOnce CLI command to show the current status of firmware # hardware show firmware 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 step 5. Special instructions may apply. See step 5 for details. 3. Before upgrading firmware, stop service sets. serviceset stop all to stop service sets and ensure that no jobs are running. It may take several minutes for all service sets to stop. service show status to verify that all service sets have stopped. If they are still running, wait one minute and try again, until the status is Not Running. # service show status Service Set 1 Status Overall : Not Running # 4. Use the hardware update firmware <node storage> force CLI command, as required. For example, 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. Specify the node, storage or switch and repeat the command for each node, storage and switch in your system. The command will be applied across all server components or across all storage components. Software upgrade installation instructions (all products) 15

16 5. After the firmware has updated, the StoreOnce Management Console (GUI or CLI) will report if components have been updated that require a cold reboot. Perform a cold reboot as follows: Power down the node(s) using the StoreOnce CLI command: system shutdown After the system has completely shut down, wait at least one minute before powering on using the Power On button on the server(s). NOTE: If a cold reboot is not required, it is acceptable to reboot the system using the StoreOnce CLI command: system reboot To get the VSA running (after upgrading a VSA 1.x to 2.x) IMPORTANT: This is a required step only if you are upgrading a StoreOnce VSA 1.x system running 3.7.x software first to 3.11.x and then to 3.13.x and have not completed this step with the 3.11.x upgrade. The 3.11.x software update process reboots the VSA, and also removes the existing 3 year support license. StoreOnce VSA users must get and apply a new license to re-enable features that they previously had. NOTE: If you completed this step with the StoreOnce 3.11.x upgrade continue to To complete the update (all models). After the services come up, log into the StoreOnce CLI and run the license add demo command. This command enables a 60 day all-in-one Instant-On license. This license enables all the advanced features and enhancements provided with VSA 2.0. However, after this 60 day period all backup targets will become read-only. During this 60 day period contact the HPE Licensing portal with the serial number of this VSA. You will be provided with a product license key which will enable the VSA for the remaining length of the 3 year license term. Use the StoreOnce CLI to apply the product license key. Continue to To complete the update (all models). To complete the update (all models) Clear the browser cache and reopen the browser. Pull a support ticket and save for future reference. Back up the system configuration using the StoreOnce CLI command, config save devices. If using encrypted VTL, NAS or StoreOnce Catalyst stores, back up the key configuration using the StoreOnce CLI command, config save keystore. If you are using StoreOnce Remote Support, the connection from the StoreOnce to the HPE Secure Service Architecture has migrated from to storage-support.glb.itcs.hpe.com. On the StoreOnce GUI page for Remote Support, manually 16 Software upgrade installation instructions (all products)

17 update the Enterprise Server URL to use the new URL. Additionally, it may be necessary to modify your firewall to reflect the new URL. Your DNS server should allow storage-support.glb.itcs.hpe.com (legacy) to be resolved to: storage-support1.itcs.hpe.com ( ) or storage-support2.itcs.hpe.com ( ). For Outbound Connectivity (File transfer from StoreOnce to HPE), Port 443 (https) should be opened (outbound) between the StoreOnce IP and the following IP addresses: storage-support1.itcs.hpe.com and storage-support2.itcs.hpe.com. If you are using StoreOnce Remote Support, 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 "reason" or wait 24 hours for it to be automatically re-enabled. Related software The following are available free of charge from the Software Depot: HPE StoreOnce Enterprise Manager (SEM): SEM is a standalone software application that provides basic management capabilities in a replication environment, and provides an easy way for customers to manage up to 400 StoreOnce devices that are being replicated across multiple sites. SEM also provides the ability to monitor disk usage and de-duplication ratios for devices allowing administrators the ability to identify devices that may need additional capacity. HPE StoreOnce OpenStorage Plug-ins (OST for NBU): This is a new version of the OST plug-in for use with StoreOnce 3.12 software and later. The plug-in is required by Symantec NetBackup (NBU) applications when using StoreOnce Catalyst and is installed on the host media server(s). HPE StoreOnce Catalyst plug-in for Oracle recovery manager (RMAN): This is a new version of the RMAN plug-in for use with StoreOnce 3.12 software and later. The plug-in is required by Oracle Recovery Manager when using StoreOnce Catalyst and is installed on the host media server(s). HPE StoreOnce Plug-in for Microsoft SQL Server (SQL): This plug-in is supported on StoreOnce 3.12 software and later. It provides functionality to backup and restore a database to different logical devices such as DISK, TAPE, or URL when using StoreOnce Catalyst and is installed on the Windows Server running Microsoft SQL server. HPE StoreOnce Recovery Manager Central (RMC): This product is supported on StoreOnce 3.12 software and later. HPE StoreOnce Recovery Manager Central software integrates HPE 3PAR StoreServ primary storage with HPE StoreOnce Backup systems to provide a converged availability and backup service that offers an alternative to traditional backup software. NOTE: StoreOnce code and later is not compatible with RMC version 1.2 and below. HPE StoreOnce Catalyst Plug-in for SAP HANA: This product is supported on StoreOnce 3.12 software and later. The HPE StoreOnce Catalyst Plug-in for SAP HANA enables optimized protection for SAP HANA databases. It enables the Database Administrator to backup/restore directly to/from a Catalyst Store on a StoreOnce Backup appliance. The HPE StoreOnce Catalyst Plug-in for SAP HANA must be installed using the SAP HANA operating system user, not the root user. The plug-in includes guided installation and configuration for fast setup. The latest software is available free with all StoreOnce Backup systems that have the corresponding Replication and StoreOnce Catalyst LTUs, as appropriate. The software, including release notes and documentation, can be downloaded from: index.do. Related software 17

18 Search for StoreOnce in the Search Software Depot search box. The search result includes the StoreOnce System Software for all products, VSA evaluation files, and QR images for all hardware platforms, plus a link to StoreOnce Free Software. Click on StoreOnce Free Software to access SEM and the other software listed above. 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. 18 Documentation feedback