<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Think really different &#187; Solaris</title>
	<atom:link href="http://unixbitch.com/category/solaris/feed/" rel="self" type="application/rss+xml" />
	<link>http://unixbitch.com</link>
	<description></description>
	<lastBuildDate>Sun, 14 Aug 2011 14:51:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>VCS Service group where to be online?</title>
		<link>http://unixbitch.com/2010/08/vcs-service-group-where-to-be-online/</link>
		<comments>http://unixbitch.com/2010/08/vcs-service-group-where-to-be-online/#comments</comments>
		<pubDate>Wed, 11 Aug 2010 05:47:13 +0000</pubDate>
		<dc:creator>sdnew</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[clustering]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[VCS]]></category>

		<guid isPermaLink="false">http://unixbitch.com/?p=533</guid>
		<description><![CDATA[When I join the team I have no knowledge on VCS, like zero knowledge and then I came to know a few stuffs like bringing online and clearing faulted resources and groups and that&#8217;s it, I didn&#8217;t even care about &#8230; <a href="http://unixbitch.com/2010/08/vcs-service-group-where-to-be-online/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>When I join the team I have no knowledge on VCS, like zero knowledge and then I came to know a few stuffs like bringing online and clearing faulted resources and groups and that&#8217;s it, I didn&#8217;t even care about the rest because usually that&#8217;s the only alerts we get that is the only thing you need to do.</p>
<p>But what if one of the system crash and when it comes up all the groups and resources went offline, how would you know on which system it should be online?</p>
<p>So I asked my Team lead and here&#8217;s what I&#8217;ve learned. There is no primary/secondary concept in VCS but you can mention the priority on which host the service group will come up with AutoStartList and SystemList and it&#8217;s more complex than I thought :D</p>
<p><strong>SystemList<br />
</strong></p>
<p>The SystemList attribute designates all systems that can run a particular service group. VCS does not allow a service group to be brought online on a system that is not in the group’s system list. By default, the order of systems in the list defines the priority of systems used in a failover. Lower numbers indicate a preference for the system as a failover target.</p>
<p>for example</p>
<p>SystemList = { SystemA, SystemB, SystemC }</p>
<p>configures SystemA to be the first choice on failover, followed by SystemB and then SystemC.</p>
<p>Note that you must define this attribute prior to setting the AutoStartList attribute.</p>
<p><strong>AutoStartList<br />
</strong></p>
<p>List of systems on which, under specific  conditions, the service group will be started with VCS (usually at  system boot). For example, if a system is a member of a failover service  group&#8217;s AutoStartList attribute, and if the service group is not  already running on another system in the cluster, the group is brought  online when the system is started.</p>
<p><a name="147099"> </a> VCS uses the AutoStartPolicy attribute to determine the system on which to bring the service group online.</p>
<p><strong>AutoStartPolicy<br />
</strong></p>
<p>Sets the policy VCS uses to determine on which system to bring a service group online if multiple systems are available.</p>
<p><a name="147110"> </a> This attribute has three options:</p>
<p><a name="147111"> </a> <em>Order</em> (default)—Systems are chosen in the order in which they are defined in the AutoStartList attribute.</p>
<p><a name="147112"> </a> <em>Load</em>—Systems are chosen in the order of their capacity, as designated in  the AvailableCapacity system attribute. System with the highest  capacity is chosen first.</p>
<p><a name="147113"> </a> <em>Priority</em>—Systems are chosen in the order of their priority in the  SystemList attribute. Systems with the lowest priority is chosen first.</p>
<blockquote><p>Example:</p>
<p>In the below example the priority on which group unix1 should be online is at system1</p>
<p>view /etc/VRTSvcs/conf/config/main.cf</p>
<p>group unix1 (<br />
SystemList = { system1 = 0,  system2 = 1 }<br />
AutoStartList = { system1 ,  system2 }<br />
)</p>
<p>system1:# hagrp -display unix1 |grep -i autos<br />
smjrskt1     AutoStart             global      1<br />
smjrskt1     AutoStartIfPartial    global      1<br />
smjrskt1     AutoStartList         global      system1      system2<br />
smjrskt1     AutoStartPolicy       global      Order</p></blockquote>
<p>I still have a lot to learn and should learn it from scratch, problem is I don&#8217;t have much resources</p>
]]></content:encoded>
			<wfw:commentRss>http://unixbitch.com/2010/08/vcs-service-group-where-to-be-online/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>History of Solaris</title>
		<link>http://unixbitch.com/2009/11/history-of-solaris/</link>
		<comments>http://unixbitch.com/2009/11/history-of-solaris/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 02:13:11 +0000</pubDate>
		<dc:creator>sdnew</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[BSD]]></category>
		<category><![CDATA[history of solaris]]></category>
		<category><![CDATA[SunOS]]></category>

		<guid isPermaLink="false">http://unixbitch.com/?p=255</guid>
		<description><![CDATA[Since I will be handling mostly Solaris servers on my next job, I try to start learning about Solaris as I really have no knowledge on it, so I try to start on the history and tried to research on &#8230; <a href="http://unixbitch.com/2009/11/history-of-solaris/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Since I will be handling mostly Solaris servers on my next job, I try to start learning about Solaris as I really have no knowledge on it, so I try to start on the history and tried to research on web that would explain it to me briefly and I found this; <a href="http://unixed.com/Resources/history_of_solaris.pdf" target="_self">http://unixed.com/Resources/history_of_solaris.pdf</a></p>
<p>There are a lot of information on the web but the link above was my favorite and I find it very well written.</p>
<p><strong>Here are some of the interesting part, at least for me</strong> :)</p>
<p>The first version of UNIX was written in assembly language on a PDP-11/20. It included the file system, fork, roff, and ed. It was used as a text-processing tool for the preparation of patents.</p>
<p>In the early 1980s, Joy left Berkeley with a master’s degree in electrical engineering, and became cofounder of Sun Microsystems (Sun stands for Stanford University Network). Sun’s implementation of BSD was called SunOS.</p>
<p><strong>SunOS was first released in 1983.</strong> &#8212;<strong> </strong><em>we have the same age :D</em><strong><br />
</strong></p>
<p>1993 Sun announced that SunOS, release 4.1.4, would be its last release of an operating system based on BSD. Sun saw the writing on the wall and moved to System V, release 4, which they named <strong>Solaris.</strong></p>
<p>As more hardware vendors, such as Sun, began to enter the picture, a proliferation of UNIX versions emerged. Although these hardware vendors had to purchase the source code from AT&amp;T and port UNIX to their hardware platforms, AT&amp;T’s policy toward licensing the UNIX brand name allowed nearly any hardware vendor willing to pay for a license to pick up UNIX. Because UNIX was a trademark, hardware vendors had to give their operating systems a unique name. Here are a few of the more popular versions of UNIX that have survived over the years:</p>
<ul>
<li>SCO UNIX. SCO Open Desktop and SCO Open Server from the Santa Cruz Operation for the Intel platform. Based on System V.</li>
<li>SunOS. Sun’s early operating system and the best-known BSD operating system.</li>
<li>Solaris. Sun’s SRV4 implementation, also referred to as SunOS 5.x.</li>
<li>HP-UX. Hewlett-Packard’s version of UNIX. HP-UX 9.x was System V, release 3, and HP-UX11i is based on the System V, release 4 OS.</li>
<li>Digital UNIX. Digital Equipment’s version of OSF/1.</li>
<li>IRIX. The Silicon Graphics version of UNIX. Early versions were BSD-based; version 6 was System V, release 4.</li>
<li>AIX. IBM’s System V-based UNIX.</li>
<li>Linux. A free UNIX operating system for the INTEL platform; it was quickly gaining a hold in the UNIX community. Versions of Linux became available on Sun, HP, and IBM systems.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://unixbitch.com/2009/11/history-of-solaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

