SAN Disk Reservation

From: Zoran Kalenic (Zoran.Kalenic_at_lchclearnet.com)
Date: 12/06/04

  • Next message: davidstacks1964_at_netscape.net: "Oracle 9i RAC on Compaq Tru64 UNIX" 
    Date: Mon, 06 Dec 2004 15:38:21 +0000
To: tru64-unix-managers@ornl.gov

    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Please read the disclaimer at the bottom of this e-mail.
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    Hi,

    We currently have two Tru64 4.0F ES40 systems on two sites. One being the Production system and the other being the DR. Each site has an HSG80 with cross-site fibre links to each system.

    Under normal conditions, the Production system has the SAN disks assigned and utilises LSM to mirror the disks on the local and remote SANs. This all works well.

    When testing the DR site, we deport the disk group and re-assign them to the DR system. We then LSM import them onto the system and bring it up. This also works well.

    During each step, the SAN configuration only enables one host to have access to the SAN storage at any one time. I would like to change this and permanently enable both systems to have access to the disks. This is to prevent the SAN being reconfigured each time we fail over.

    My question is:

    Is there a method in place to prevent the disks being imported onto both systems at the same time? Does LSM have this prevention built in? Can the SAN do it (such as the old SCSI reservation technique) through fibre connections?

    I will provide a summary.

    Regards,

    Zoran Kalenic.

    **********************************************************************
    This email is intended for the named recipient(s) only. Its contents
    are confidential and may only be retained by the named recipient(s)
    and may only be copied or disclosed with the consent of
    LCH.Clearnet Limited. If you are not an intended recipient please
    delete this e-mail and notify postmaster@lchclearnet.com.

    The contents of this email are subject to contract in all cases,
    and LCH.Clearnet Limited makes no contractual commitment save where
    confirmed by hard copy. LCH.Clearnet Limited accepts no liability,
    including liability for negligence, in respect of any statement in
    this email.

    LCH.Clearnet Limited, Registered Office: Aldgate House,
    33 Aldgate High Street, London EC3N 1EA. Recognised as a Clearing
    House under the Financial Services & Markets Act 2000. Reg in England No.25932
    Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.com
    **********************************************************************

  • Next message: davidstacks1964_at_netscape.net: "Oracle 9i RAC on Compaq Tru64 UNIX"

    Relevant Pages

    • SUMMARY: SAN Disk Reservation
      ... LSM does provide a level of protection when importing disks to ensure disks are not imported to more than one host at a time, however, this can be overridden with a -C option. ... the Production system has the SAN disks assigned and utilises LSM to mirror the disks on the local and remote SANs. ...
      (Tru64-UNIX-Managers)
    • Re: Need experiences regarding booting from SAN
      ... I have a 7026-M80 that I am using SAN boot disks on. ... The storage is a FastT700. ... Need experiences regarding booting from SAN ...
      (AIX-L)
    • [HPADM] SUMMARY EMC SAN move (update)
      ... I guess I left out the part where EMC will be doing the SAN copy and the other necessary step on the SAN. ... assign the new disks and mirror to those disks and then break mirror, ... While the copy is going on, we edit the import scripts we ...
      (HP-UX-Admin)
    • SUMMARY: LSM for beginners
      ... Many thanks to Danielle Georgette for her concise instructions on using LSM. ... I'd actually rename the existing subdisk so that the subdisk name ... Here is a procedure for getting the disks into LSM but it assumes the ... Format disks for use with LSM using the voldisksetup command. ...
      (Tru64-UNIX-Managers)
    • Re: Correct sequence to present new SAN disks to W2K3 cluster
      ... then SAN? ... single storage group for your cluster you won't be able to do step 3 below ... Delete the resources for the new disks from the cluster, ... I'd move the resources all to a single node and pause the passive node ...
      (microsoft.public.windows.server.clustering)