Home About BC DR HA Support Training Download
You are here: Home/ Business-Continuity/ Please Login or Register

Additional documents of interest

  • Successful Business Continuity - Part 1 - Users and Groups
    This article was published in the April 2005 issue of AIX Update magazine and discusses system administration needs and requirements oriented around users and groups. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters, such as user names, group names, UID and GID numbers.
  • Successful Business Continuity - Part 2 - Machine and Host Names
    This article was published in the May 2005 issue of AIX Update magazine and discusses naming structures for machines, systems, adapters, and aliases. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.
  • Successful Business Continuity - Part 3 - Volume Names
    This article was published in the December 2005 issue of AIX Update magazine and discusses naming structures for volume groups, logical volumes, log logical volumes, directory mount points, etc. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.
  • Successful Business Continuity - Part 4 - MQ Series, Startup/Shutdown Scripts, Error Processing
    This article was published in the April 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. The topic of this article is the assignment of MQ Series queue names and aliases, resource group startup and shutdown script names (Application startup/shutdown script names), error logging, and error notification.
  • Successful Business Continuity - Part 5 - Miscellaneous topics
    This article was published in the August 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. A variety of topics is discussed in this article including automated documentation generation and management.
  • Automated Microcode Management System
    One of the most difficult administration tasks in an AIX environment is attempting to keep the firmware and microcode up-to-date. Mt Xia has devised an automated method of gathering the Microcode information, determining which microcode needs to be updated, generating reports, and uploading the required microcode updates to each individual system.
  • Calculating the size of a Virtual Processor
    This document describes the algorithms used to calculate the size of a virtual processor when using shared processors in an LPAR. The IBM documentation describes how to calculate CPU utilization, NOT how to size for configuration, this document clarifies this process. A description of the HMC input fields for the processor tab is included.
  • Basics of Partition Load Manager Setup
    This presentation was provided by Ron Barker from IBM regarding the PLM Basic setup.
  • ppt
  • pdf
  • Logical Volume Name Standards

    This document describes the standards for assigning AIX Logical Volume (LV) names. A single standard has been developed for use in standalone, High Availability, and Disaster Recovery environments. This LV naming standard provides the mechanism to assign enterprise wide unique names to all AIX LV's and will eliminate naming conflicts in the event of a manual or automated failover, or if multiple instances of an application are running on a single server.

    To assign enterprise wide unique LV names, the system administrator must first define the resource groups names. Once the resource group names have been defined, then a Volume Group (VG) must be defined based on the RG name. After the VG has been created, LV's can be assigned. A VG will typically contain several LV's, and each LV will be named based on the resource group to which it is associated.


    To define a LV name, obtain the 8 character resource group name, then add a 4 digit logical volume sequence identifier that will uniquely identify the LV, followed by the characters "lv". The 4 digit LV sequence identifier will consist of alpha-numeric characters and must always be exactly 4 characters in length. The LV name will always end with the characters "lv".

    The LV name shall consist of exactly 14 characters with the following structure:

    ApplicationCode + Environment + Function + Company + Sequence ID + LV Sequence ID + "lv"
         3 char     +    1 char   +  1 char  +  2 char +   1 char    +      4 char    + 2 char
    

    As an example, a resource group named "egaapmx0", may have a volume group named "egaapmx00vg". This volume group may have multiple LV's associated with it:

    RG Name
    Component
    LV Sequence
    Identifier
    LV Identifier LV Name
    egaapmx0 db20 lv egaapmx0db20lv
    egaapmx0 db21 lv egaapmx0db21lv
    egaapmx0 db22 lv egaapmx0db22lv


    JFS filesystems will require a logical volume for the JFS log. This must also have an enterprise wide unique name.


    JFS Log Logical Volume Name Standards

    The following is a description of the standards for assigning AIX JFS Log Logical Volume (JFS Log LV) names. A single standard has been developed for use in standalone, High Availability, and Disaster Recovery environments. This JFS Log LV naming standard provides the mechanism to assign enterprise wide unique names to all AIX JFS Log LV's and will eliminate naming conflicts in the event of a manual or automated failover, or if multiple instances of an application are running on a single server.

    To assign enterprise wide unique JFS Log LV names, the system administrator must first define the resource groups names. Once the resource group names have been defined, then a Volume Group (VG) must be defined based on the RG name. After the VG has been created, JFS Log LV's can be assigned. A VG will typically contain one JFS Log LV's, however multiple JFS Log LV's can exist.


    To define a JFS Log LV name, obtain the 8 character resource group name, then add the 4 digit logical volume sequence identifier that will uniquely identify the JFS Log LV, followed by the characters "lv". The 4 digit JFS Log LV sequence identifier will consist of the characters "jfs" followed by a single digit to uniquely identify the JFS Log LV. The JFS Log LV name will always end with the characters "lv".

    The JFS Log LV name shall consist of exactly 14 characters with the following structure:

    ApplicationCode + Environment + Function + Company + Sequence ID +  "jfs" + JFS Log Sequence ID + "lv"
         3 char     +    1 char   +  1 char  +  2 char +   1 char    + 3 char +       1 char        + 2 char
    

    As an example, a resource group named "egaapmx0", may have a volume group named "egaapmx00vg". This volume group may have multiple JFS Log LV's associated with it:

    RG Name
    Component
    JFS Log LV
    Sequence ID
    JFS Log
    LV ID
    JFS Log
    LV Name
    egaapmx0 jfs0 lv egaapmx0jfs0lv
    egaapmx0 jfs1 lv egaapmx0jfs1lv
    egaapmx0 jfs2 lv egaapmx0jfs2lv


    JFS filesystems will require a logical volume for the JFS log. This must also have an enterprise wide unique name.

    -
    Standards
    -
     

    Policies
    Guidelines
    Procedures


    LPAR Leasing
    Lease an AIX / i5 LPAR
    Reduce your costs

    www.mtxia.com

    Server Leasing
    Lease a Server off-site
    Reduce your costs

    www.mtxia.com

    Data Center Automation
    Business Continuity and DR
    Virtualization/Consolidation

    www.mtxia.com

    HMC Service
    Hardware Management Console
    Manage Remote AIX / i5 LPARs

    www.siteox.com

    Business Web Site Hosting
    $3.99 / month includes Tools,
    Shopping Cart, Site Builder

    www.siteox.com

    FREE Domain Registration
    included with Web Site Hosting
    Tools, Social Networking, Blog

    www.siteox.com

    Disaster Recovery
    Small Business Oriented
    Off-Site Facilities

    www.mtxia.com

    IBM pSeries / iSeries
    Reduce your Costs
    Off-Site Server Hosting

    www.mtxia.com