Skip to main content

Palomar Pomerado Health goes virtual with IBM



Its time to make the customers the heros! They go through a lot after listening to nusts like us all the time, so they deserve to also share some limelight when they go virtual.

PPH choose IBM's SAN virtualized storage.

Why did PPH go through this migration and embrace virtualized storage?

PPH knew it needed to go much further into digital hospital management. Paper-based file and record and booking systems just couldn't cope. It was going to add another hospital and move to fully digitised medical records for its patients. A $496 million bond issue had provided the finance for this.

It also wanted to introduce a new and customized computerized physician order entry (CPOE) program, a digital physician bedside care system, in 2009. To do that it needed a better IT infrastructure than the inflexible one it currently had. It needed a storage system which would allow it to migrate files from one storage array to another without shutting down major parts of its IT infrastructure.

Cerner Corporation, an IBM business partner and software supplier to PPH, suggested that it move to more powerful servers and add two tiers of storage alongside the ageing ESS array, and, in a crucial move, virtualise these three pieces of storage into one logical pool behind IBM's SVC. This would both increase the utilization of storage capacity and provide appropriate levels of storage service and cost to different types of data, and also enable files to be moved from one array to another, or from one storage tier to another, without interrupting users' and applications' storage service at all.



Link
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more