Summary: Trucluster creation

From: Thomas Edward Kempster (tekempster_at_fastmail.fm)
Date: 11/14/05

  • Next message: Dr. Hans Ekkehard Plesser: "Tru64 V5.1B: Next Patch Kit in Sight?" 
    Date: Mon, 14 Nov 2005 11:54:28 +0000
To: tru64-unix-managers@ornl.gov

    With many thanks to Thomas Sjolshagen

    It appears that CFS takes care of AdvFS and layers on top, so I can
    creat a new cluster without loosing my Advfs setup. Next thing is to
    try.

    Here is his reply:
    >>
    No, clu_create and clu_add_member does not cost you your file systems
    (CFS is a virtual file system which layers on top of AdvFS - the exact
    same AdvFS you're currently using on your production systems). We
    actually recommend building a single system, patch it, install all ISV
    apps + patches and *then* create the cluster (saves a *lot* of time).

    You probably have to re-tune your system after the clu_create and
    preserve the "build disk" (i.e. the basic OS disk - in your case, the
    current production root device) just in case you have to re-build or
    anything.

    // Thomas
    <<

    ........................................................................

    I have only installed Tru64 clusters on new systems before but am unsure
    of the consquences of creating a cluster from a current production
    system.

    We are in the process of creating a SAN and adding the Tru64 environment
    to the SAN, which opens up the possibility of creating more clusters.

    If I create a cluster from a working 5.1A or 5.1B system will I lose the
    AdvFS files and application data? To lose a production environment for a
    long time would be a big problem, there would be too much data to
    restore.

    I would like to create a single node cluster from the current system and
    then add another node

    Regards,

    Tom Kempster 

    -- 
http://www.fastmail.fm - Accessible with your email software
                          or over the web
  • Next message: Dr. Hans Ekkehard Plesser: "Tru64 V5.1B: Next Patch Kit in Sight?"

    Relevant Pages

    • Re: Portents of VMS death
      ... >But in the real world, if you have 2-3 nodes in your cluster, one production, ... That's not a real-world cluster. ... That implies multiple servers providing access to the same ... applications in a load-balanced way. ...
      (comp.os.vms)
    • Re: Disaster Recovery Planning
      ... > shipping to keep the DR databases in sync with the production DBs; ... > automate all the log shipping role changes (150+ databases is a bit too ... The cluster nodes were ... >> I've never seen a disaster recovery plan for SQL Server. ...
      (microsoft.public.sqlserver.server)
    • Re: Replicating Drives to use for Development Instances
      ... with the -S you can write a new Disk Signature:) ... MVP - Windows Server - Clustering ... > site B failover) and a cluster with one node at each site. ... > production and a development instance on the same system. ...
      (microsoft.public.windows.server.clustering)
    • Re: System organization preference question
      ... parts of the startup chain to the files located on that shared disk. ... This so that a cluster with multiple system disks has a central disk ... with one or more system disks being off-line during rolling upgrades. ... production -- I do typically leave the files in the default location. ...
      (comp.os.vms)
    • Re: Portents of VMS death
      ... >> in a cluster with production would get you hit ... Especially in the financial sector. ... We had two production and one ... developent cluster - attempts to combine one of the production clusters with ...
      (comp.os.vms)