Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-2277325.1
Update Date:2018-03-13
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  2277325.1 :   Platinum ZFS Storage Appliance Racked System and Backup Appliance Remote Patch Deployment  


Related Items
  • Oracle ZFS Backup Appliance ZS5-4
  •  
  • Oracle ZFS Storage Appliance Racked System ZS5-4
  •  
  • Oracle ZFS Backup Appliance
  •  
  • Oracle ZFS Backup Appliance ZS5-2
  •  
  • Oracle ZFS Storage Appliance Racked System ZS5-2
  •  
  • Oracle ZFS Storage Appliance Racked System ZS4-4
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
  •  




In this Document
Purpose
Details
References


Applies to:

Oracle ZFS Backup Appliance ZS5-2 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS4-4 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS5-2 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS5-4 - Version All Versions and later
Oracle ZFS Backup Appliance - Version All Versions and later
7000 Appliance OS (Fishworks)

Purpose

Remote Patch Deployment is a deliverable of Oracle Platinum Services, which provides patching of customer’s Platinum-certified components up to four (4) times per year.  This note provides the customer a high-level overview of the patching process.

Remote Patch Deployment comprises of software updates for Oracle ZFS Storage Appliances and provides additional features, bug fixes, and occasionally security updates, thus allowing your storage environment to run at peak efficiency.

A software update is a binary file, which is the same for all supported platforms, that contains new management software as well as new hardware firmware for your storage controllers and disk shelves.

 

To receive remote patch installation services you must be a current Oracle Platinum Services customer. Remote patch installation services are subject to the Oracle Platinum Services Technical Support Policy.

The programs patched and the scope of the remote patching installations are available at http://www.oracle.com/us/support/library/remote-quarterly-patching-scope-1652890.pdf

 

Details

 

Remote Patch Deployment Process Timetable

The patch process will begin a month prior to the scheduled patch upgrade date and will consist of the following timetable:

 

Event

Owner

Activity

Timeframe

Open Patch Event SR

Patch Coordinator or
Customer

Initiate Request for Patch Update

4+ Weeks

Proposed Date/Time

Patch Coordinator Patch Engineer & Customer

Agree to Patch Event Date

4+ Weeks

Patch Assessment

Patch Engineer

Verify Gateway Passwords, Review Installed Patch Level
& Configuration Check

3+ Weeks

Patch Plan & Update SR

Patch Engineer

Recommended Patch Level, Communicate to Patch Coordinator & Customer

3+ Weeks

Patch Review

Patch Coordinator & Customer

Review Scope of Remote Patch Deployment and Completed Patch Assessment

2+ Weeks

Date Confirmation

Patch Coordinator & Customer

Confirm Date/Time for Patch Event

1+ Week

Patch Pre-Check

Patch Engineer

Health Check

1 – 2 Days

Patch Event Confirmation

Patch Engineer & Customer

Confirm Patch Event with Customer

1 Hour

Patch Event

Patch Engineer

Upgrade System

Patch Date/Time

Patch Event SR Closure

Patch Coordinator & Customer

Confirm Complete and Approval for SR Closure

Upon Completion

 

Patch Process

The patch process is based upon the standard upgrade for clustered systems as documented in the Sun Storage 7000 Unified Storage System: How to upgrade a clustered system in Oracle Knowledge Doc ID 1447284.1.

 

Estimated Patch Upgrade Time

Following are the expected times to complete the patch upgrade*:

Activity

Variable

Time

Pre-Upgrade Checklist

 

10 Minutes

Setup Patch Files

 

30 Minutes

Upgrade BIOS

 

10 Minutes

Upgrade First Node

 

30 Minutes

BIOS Delay Update

Dependent on Current Code

10 Minutes

Upgrade Second Node

 

30 Minutes

Failback

 

10 Minutes

Disk Firmware Push

Dependent on # Trays

10 Minutes

Post Upgrade Check

 

10 Minutes

Total Estimate for Upgrade

 

2 1/2 Hours

*These timings represent actual averages; however, these may not represent timings you will experience. Customers should allow ample time for upgrades and expect variations by system, configurations, sizing and performance.

 

Latest Release

Release Name Date Released Version String Applicable Systems Release Notes and CR's Fixed Important MOS Notes Security Patch Number Download Link
OS8.7.14
(2013.1.7.14)
01/09/2018 ak-2013.06.05.7.14 Oracle ZFS Backup Appliance,
Oracle ZFS Storage Appliance Racked System ZS4-4,
Oracle ZFS Backup Appliance ZS5-2,
Oracle ZFS Storage Appliance Racked System ZS5-2,
Oracle ZFS Backup Appliance ZS5-4,
Oracle ZFS Storage Appliance Racked System ZS5-4
Release Notes Replication Compatibility(Doc ID 1958039.1)
Interoperability - 2013.1.7.0 (Doc ID 2221946.1)
No 27357887 download

Additional information is available in the Oracle Support Document 2021771.1 (Oracle ZFS Storage Appliance: Software Updates)

 

Cluster Upgrade

In a clustered system, as is the case with the ZS Racked System and Backup Appliance Platinum Serviced Products, a rolling upgrade can be performed, eliminating downtime while the upgrade is completed. The upgrade procedure is described in the Oracle® ZFS Storage Appliance Customer Service Manual in the Release OS8.7.x Documentation Library. To describe the rolling upgrade procedure, this document refers to the two clustered storage controllers as A and B, where A is the controller that will be updated first, and B is the controller that will be updated second. A key best practice in rolling upgrades is that each controller should be upgraded at a time when it is not providing service to clients. The procedure described meets this requirement and it is the customers responsibility to ensure best practices and proper configuration of client services for a successful upgrade.

 

Conclusion

At the conclusion of the patch event, the corresponding Service Request (SR) will be updated and the customer notified.  Customers should test the system to make sure all components are online and available.

All communication will be documented in the patch event Service Request. When significant updates happen in the SR, an email will be sent to the contact persons listed in the SR.

Telephone or chat contact can be established with the customer at any time during the patching process.

Customers can contact their local Oracle Support center and enter their Service Request number if there are any concerns.

 

 

References

<NOTE:2277291.1> - Platinum ZFS Storage Appliance Racked System and Backup Appliance Patch Assessment

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback