4. Business and Technical Drivers - Availability Average Monthly Downtime Windows ISM Uptime In Hours In Minutes In Seconds 99.000% 7.3 99.500% 3.6 99.750% 1.8 99.900% 44.0 99.990% 4.4 99.999% 26 Business need
14. Operating System Challenges – Windows File Access CIFS C ommon I nternet F ile S ystem Dynamic CIFS share creation and mounting 41,000+ dynamic CIFS mounts in 3 months
15.
16. HP-UX Windows Caché is the bridge between HP-UX and Windows Operating System Challenges – Printing
17. Phase 1 (database tier) Migration - Data Transfer How do we move 3.5 Terabytes of Data within an ISM Window?
29. Partners Enterprise Caché UNIX Migration Walter Halvorsen Systems Programming Lead II [email_address]
Editor's Notes
I’m going to cover these 5 topics There were many steps in the migration process. I’m going to focus on the production migration events
We had to press the red button too often Availability was the primary business driver
Our monthly downtime for a Windows ISM did not meet our business need Rebooting our Production environment for monthly Windows security patches took between 1 and a half to two hours
Here’s how we’ve decreased the planned and unplanned downtime for the Caché production environment
Other business drivers were scalability and performance Our Caché 5.0 Windows environment <click> could no longer deliver the performance demanded by the LMR application
Over the past 5 years we’ve had a 7-fold increase in the number of monthly LMR transactions
During the same time, the entire platform had an even higher increase in database references
Here’s how we improved performance and increased scalability In a 32-bit O/S, we were limited to about 1.5 GB of global buffers, configured up to 30 GB on some application servers
This is a diagram of our production environment pre-migration There are 61 Windows app servers and 5 Windows database servers All infrastructure is in Needham except for 12 IIS servers and the SAN replication target Symmetrix
This project wasn’t just an operating system migration
We faced a number of challenges bringing HP-UX into the Partners environment
The solution was CIFS Our file IO utility automatically mounts CIFS shares and creates them, if necessary In production there have been more than 41,000 dynamic CIFS share mounts in three months
Another challenge was printing Printing to Windows print servers through CIFS would require maintaining hundreds of print queues on each HP-UX host We had to find a better way to do it
Here’s our solution to printing We use Cache as a bridge between HP-UX and Windows The Windows printer Daemon Queue is redundant for high-availability
We had to get the data from Windows to UNIX The solution to this is covered in upcoming slides
Here is the timeline for the phase 1 migration Phase 1 is the database tier migration The Caché version remained 5.0 The first 4 months consisted of Proof of Concept and benchmarking tests, followed by DEV, QA and 4 production database migration events So one part of the solution to the data transfer issue was to break it up into 4 events
I’m going to describe the process we used for each of the four migration events On the left are the 5 Windows database servers In the middle are the Windows InfoMover servers. Infomover is a san-based, host-assisted cross-platform file transfer utility. This is the other essential part of the solution to our file transfer problem On the right is the HP-UX database server cluster where Caché instances are already installed Note that the Windows servers are attached to the DMX-2 and the HP-UX server is attached to the DMX-3 To get enough throughput, I configured 4 InfoMover servers with 24 InfoMover processes among them writing to 24 filesystems on the HP-UX host First, we cloned the drives for the server, kept them in synch until the scheduled downtine, activated and terminated the clones Then we started the Infomover scripts to transfer the files and then Perform an Endian conversion. Afterward, we started a shadow process to keep the Windows database server up to date in case a back-out was required.
Here’s the final phase 1 configuration with the 5 Windows database servers replaced by 1 HP-UX Serviceguard cluster
This is the timeline for Phase 2 Phase 2 is the application tier migration to HP-UX and the Caché upgrade to 2008.1. It actually started before Phase 1 was completed We built two new Caché 2008.1 environments for the application testing and certification efforts In the Fall and early Winter we built the application tier Then we migrated DEV, QA and production
Now I’d like to walk you through the Phase 2 production migration process Note that green indicates Caché 5.0.20 and blue indicates Caché 2008.1 We start with Windows application servers and an HP-UX Serviceguard cluster all running Caché 5.0 instances We build the Ensemble and application server cluster on HP-UX Integrity blades and go live on Ensemble 2008.1 We build the remaining Integrity blades and install 2008.1 on Windows Proliant servers Install 5 2008.1 database instances Create routine datasets for 2008.1 Export 5.0 routines and classes and import them into the 2008.1 datasets Now we’re in the downtime window
Here is a diagram of production environment post-migration
Phase 3 is the build out of the remaining DR infrastructure we completed post-migration
I have 3 slides of accomplishments, so I’m just going to highlight a few Nagios First LAN-free
Here are all of the software upgrades in the migration in more detail
![[object Object],[object Object],[object Object],[object Object],[object Object]](https://image.slidesharecdn.com/partnersenterprisecachunixmigrationpublic-12514354490439-phpapp02/85/partners-enterprise-cach-unix-migration-public-1-320.jpg)
![In the next half hour… ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)