Re: OFA Structure issue (for gurus only)

From: <eric.san.andres_at_kellogg.com>
Date: 1997/05/19
Message-ID: <863822345.12280@dejanews.com>#1/1

In article <337a1e0f.7772491_at_news.interserv.com>,   scheuric_at_sprynet.com (Sheilah Scheurich) wrote:
>
>
> The OFA is a standard, not written in stone. If you put the hostname
> in front of this, I think you will still be using the standard. If
> you as a DBA see using the OFA standard will jepordize the integrity
> of the database, then don't do it. If a loss of system were to occur
> and for some reason you were unable to recover you system, do you
> really think that you could justify the loss of the system by saying
> you followed the standard? I think that these standards are there to
> help us as DBAs not to hinder us.
>
> -sheilah scheurich
> DBA
> scheuric_at_sprynet.com

Good Afternoon Sheilah,

  Volume Group Export/Import as I have used it, allows a set of disks belonging to the same volume group to be transferred physically to another system. And From what I understand,it can be a helpful function, whenever a CPU crashes and with all its disks safe and operational. And if that is a production system, of course, the database/s should be up ASAP. And by doing this, another system, or a clone can be setup in a snap , by just booting the server via disk,cd or tape, the operating system can be accessed and crashed system's volume group can be set for import. And I suppose this volume group comprise the sets of disks which contains the Database Data. Then we go to the import stage of the disks. The newly exported set of disks can be imported by physically transferring these disks to the other system. Of course, proper adjustment of the scsi addresses and scsi cables is implied, same is true with the proper configuration of the disks. Then , import the newly attached volume group. All the filesystems in that volume group will be added to the filesystem list of the CLONED UNIX Server. And if there are filesystems, with the same mount point. This is where the problem goes. The filesystems mount points need to be unique in order to get it mounted. You will not be able to mount two /u020 mount points at the same time, but you can mount two filesystems such as these, /u020/server1 and /u020/server2.

   Right now, our system is implementing:

   /u020
   /u031
   /u032

   ...
   ...

   for ALL the servers,

   My PROPOSITION is to have unique mount points to all the servers,    and by doing this , I'd propose the ff. structure:

   /u020/`hostname`
   /u031/`hostname`
   /u032/`hostname`

   ...
   ...

  I am just giving light to new ideas, in which big databases can capitalize on. I know a lot of systems running with a structure with non-unique mount points for most of their servers.

-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet

Received on Mon May 19 1997 - 00:00:00 CDT