Move progress database from Solaris to AIX

The thought process has gone into the management of moving the production database from Solaris running on Oracle M8000 to IBM AIX. The initial cost of providing the clustered solution and the DR is coming to $2.5 million.

Oracle were taking us for a ride with the discounts on M8000. The 50% agressive discount offering on M8000 comes at the same cost of M8000 that we bought last year. Along with the Veritas storage foundation and the support cost, its too expensive as a solution.

We have the quotes from IBM for their p750, however we feel this is not an apples to apple comparison as the p750 lacks the RAS features. Th better would be the comparison with p595 or p785. We have to get the POC done and get the actual working configuration. Its a long way to go, since our aplication compatibility is yet to be established with AIX 6.1. Also, we are in the process of moving from 32 bit progress database to OpenEdge 64 bit. The dynamics will change with respect to cpu and memory utilization once we move to 64 bit OpenEdge.

Price to performance ratio is good with IBM, and we have to think in that direction as instructed from the management.

We received the p780 and p795 cost without discounts. p795 will be an overkill for our environment however if we have to plan for double the capacity, that is M9000 in our current environment we may go for p795.

If we have to size our DR for IBM server, we will go with either p780 for M8000 and p795 for M9000. This is to ensure that, we are doing apples to apples comparison. The CPU and the memory are not the only component we look for while comparing the Oracle with IBM servers. IBM p750 can comapre with M8000 just based on raw CPU power, but it does not have full RAS features. In an enterprise, RAS is the other half of coin.

Comments

Post a Comment

Popular posts from this blog

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

Recoverpoint replication reporting with vmax splitter

Guys, Have you ever thought of automating the RP replication status and send status via email or post it to any reporting platform. Since the splitter impacts the VMAX FA's and there is an overhead of 13% on the utilization its good idea to see if the replication is driving the utilization of vmax FA. There are ways of pulling iops/read/write using symstat but its utilization (Director CPU utilization etc) which plays a significant role. As it crosses 80% we start seeing the increase in device response time. However, to measure FA utilization we will have to go through SMAS UI then pull out the reports. Its manual effort. But there is a way to automate it through REST API. You can get the details what type of objects are supported by pointing to : https://smc server :8443/univmax/restapi Coming to the point, getting recoverpoint consistency group status fully automated doesn't seems to be tough. Lets get through the steps. 1. Hash your SSH keys of the unix host to ...
Read more

Weird problem post power maintenance, no Powerpath pseudo name for Luns

We had the scheduled power maintenance activity in our data center. Every team was notified and we powered doen the servers through cron job. The servers were powered down first then storage (CX-380). And the reverse was followed during startup. After the power shutdown, the SAN was booted up. we forgot to disable the the snapshots. They were still active. Once it came up, the sessions were not there, but snapshot was active. Tried to deactivate the snapshot, failed with the error the "Failing Command: K10SnapCopyAdmin DBid 0 Op 1051. 71 00 80 43" Tried to create a session and attach the snapshot to the session, still unable to deactivate it, neither was able to attach to any other session. Looked at powerlink: It says the command issued to the snapshot is not owned by the SP. I trespassed all the snapshot source lun to SPA, and then tried to deactivate, nothing happened. Rebooted the SP's one by one through the management console. (http:/SP-IP/setup) Then I was able to...
Read more