Chapter 3 Pure Storage Non Disruptive M20 TO M50 Upgrade Demo
welcome to the final episode of the pier storage non-disruptive everything video series in episode 3 we will demonstrate a non-disruptive upgrade from the flasher a
m22 a flasher a m50 and add capacity to the system in this video we will show an in generation upgrade from a flasher 8m to another flasher am no disruption no data migration no rebuy of hardware and software as the series discusses this is all a new and unique ownership experience that pier storage is delivering to its customers with evergreen storage before we dive in episode 3 let's recap episode 2 quickly in episode 2 we show the non-disruptive hardware upgrade from the FA 400 series 2 the new flasher AM series the upgrade was performed with a variety of different application workloads such as Microsoft Exchange Jets tres 2013 sequel server 2014 both OLTP and DSS workloads along with oracle 11g DSS workload in episode 3 the same workloads continue to run on the flash ray so we can show the next non-disruptive upgrade of hardware let's get started before beginning the hardware upgrade we can check the view of the flash ray web management interface to see that our application workloads are still running without interruption we can also take a quick view of the two sequel server instances via the sequel server Activity Monitor sequel 1 and sequel two are showing an OLTP and DSS workload respectively the sequel one instance shows that the database io is approximately 765 megabytes per second and the sequel to instance is driving 185 megabytes per second to start the hardware upgrade process we first check the mode of the currently connected controller using Pierre DB list mode this indicates we are on the primary controller we set an alert flag using peer alert tag timeout of 240 minutes specifying maintenance this indicates we were performing a maintenance operation on the system the first controller that will be replaced in the system is CT 0 which is secondary to ensure we are working on the correct controller we set a hardware attribute to identify ct0 you the pure hardware set attribute identify on ct0 this operation shows an indication on the front of the controller to verify the identity as part of the peer storage platform customers flash arrays use the pure one phone home feature for continual monitoring of the systems for this upgrade we are sending today's phone home logs before starting any of the physical work on the system we issue pure a phone homes send today to start the task and we can issue a watch command to see when the task has completed with the phone home task complete and the controller identified ct0 we can begin the hardware removal process there is no shutdown process for the flasher a.
m.
except to simply remove cables and then the controller the next sequence of events are to remove mini SAS connections fiber channel cables Ethernet and finally unscrewing the secure screw which keeps the controller in place the trickiest part of the upgrade is making sure the cables are not in your way switching over to the management interface you'll notice a new alerts ct0 cable failures and ct0 failure these are because we remove the ct0 controller and all of its associated cables you will notice that the ct0 controller goes from green to red and the ct1 controller changes from yellow to green now ct1 is servicing all io to the flash array during this process it's important to point out that we have no disruption in a ops latency or bandwidth the next step is to add the new flash array m50 controller in the ct0 slot and reconnect all the cables we connect many SAS cables fibre channel and last Ethernet switching over to the flasher a web management interface we see both controllers are now online opening up a CLI session we run the hardware config – M to show the model of the ct0 controller notice that it isn't an M 50 this is the control that was just added to the system with the new flasher a M 50 controller installed we begin the software portion of the upgrade we start by running pure setup replace from controller f a.
m.
20 this will start the purity setup wizard and check SAS cabling and controller links are ok we set the time zone confirm that change and purity is restarted once purity restarts we receive a confirmation that pure storage is online and the secondary controller is ready for use the FA m20 CSG ndu c t1 is still the primary controller switching over the web management interface we can see that both controllers are online which is indicated by the green lights on the controllers a quick view of the sequel server instances shows that database IO is still running now it is time to replace the remaining F a.
m.
20 controller c t1 we connect to the controller and verify identity for safety using pure hardware set attribute identify on c t1 checking the front of the controller will visually identify it as c t1 once again we send the phone home logs from today using pure a phone home send today now we remove the remaining F a.
m.
20 c t1 controller and add the second fa m50 controller again we remove mini SAS cables fibre channel and Ethernet along with unscrewing the security screw as previously mentioned the tricky part is ensuring the cables are out of the way when you slide in the new F a.
m.
50 controller now reconnect the many SAS cables fibre channel and Ethernet to bring the system online we connect our remote console to the new c t1 controller to perform the peer setup replace from controller f a.
m.
20 this again starts the purity setup wizard and check SAS cabling and controller links are ok we choose to change the time zone confirm that change impurity is restarted once purity restarts we receive a confirmation that pure storage is online and the secondary controller is ready for use we check both of the controllers using pure a-list controller to ensure both controllers are m50 and have a status of ready the next step in the process is to add capacity to the system by adding drive packs to the flasher em-50 chassis this will provide additional capacity in addition to the already existing external shelves we remove the flasher 8mm faceplate and then remove the blank drives that are in the chassis once these are removed we add the additional drives to the first set of drive bays switching over the web management interface we can see the newly inserted drive show up as yellow this is an indication that the system has recognized the drives and are adding them into the system as the drives are recognized they go online as indicated by the green status of each individual Drive notice that as the drives come online the total capacity of the system increases after the first drive pack has been added we perform the same steps by removing the blanks and adding another drive pack again the drives were recognized as shown in the web management interface and the capacity of the system continues to increase we now have a fully populated flasher em-50 chassis with two external shelves all without disruption to the running workloads in conclusion of the video series we showed non-disruptive upgrades of the following pure D operating environment software upgrade generational hardware upgrade from the fa 422 the fa m 20 model in generation hardware upgrade from the fa m 22 the fa m 50 model and finally adding capacity into the system all of these actions were performed with active workloads and did not cause any disruption this concludes the pure storage non-disruptive everything video series and we hope the three videos explained just how easy it is to upgrade our system and to see the value of evergreen storage.
Nhận xét
Đăng nhận xét