Archive for 'Solaris Cluster'

Deploying highly available zones with Solaris Cluster 3.2

I discussed my first impressions of Solaris Cluster 3.2 a while back, and have been using it in various capacities ever since. One thing that I really like about Solaris Cluster is its ability to manage resources running in zones, and fail these resources over to other zones running on the same host, or a […]

Fixing Solaris Cluster device ID (DID) mismatches

I had to replace a disk in one of my cluster nodes, and was greeted with the following message once the disk was swapped and I checked the devices for consistency: $ cldevice check cldevice: (C894318) Device ID “snode2:/dev/rdsk/c1t0d0″ does not match physical device ID for “d5″. Warning: Device “snode2:/dev/rdsk/c1t0d0″ might have been replaced. To […]

The end of the Solaris Cluster /globaldevices file system

I have been working with [Sun|Solaris] for as long as I can recall. One thing that always annoyed me was the need to have a 512MB file system devoted to /globaldevices. With Sun Cluster 3.2 update 2, this is no longer the case!: >>> Global Devices File System

Running Oracle RAC inside Solaris zones

While perusing my mailing lists this morning, I came across a comment from Ellard Roush on running Oracle RAC inside a Solaris zone: “There is an active project to support Oracle RAC running in a zone environment. This new feature will be a “Zone Cluster”, which is a virtual cluster where each virtual node is […]

Deploying highly available Oracle databases with Sun Cluster 3.2

While preparing for my Sun cluster 3.2 exam, I got a chance to play with a number of the Sun Cluster 3.2 data services. One of my favorite data services was the Oracle HA data service, which allows Sun cluster to monitor and failover databases in response to system and application failures. Configuring the Oracle […]

Running processes in fixed time intervals

While messing around with Sun Cluster 3.2, I came across hatimerun. This nifty program can be used to run a program in a fixed amount of time, and kill the program if it runs longer that the time alloted to it. If hatimerun kills a program, it will return a status code of 99. If […]

« Older Entries